AdvancedHMI Software
General Category => Tips & Tricks => Topic started by: Archie on May 28, 2018, 02:40:56 PM
-
As of version 3.99y Beta 11, it is now possible to read and write complete UDTs into an equivalent class. To use this, you must create classes and map the data types from CLX to .NET equivalents. The following link has a chart that shows the data type equivalents:
https://advancedhmi.com/documentation/index.php?title=WriteUDT
An example would be the UDT shown in the attached picture. An equivalent class for this UDT would be:
Public Class DateTimeUDT
Public Year As Integer
Public Month As Integer
Public Day As Integer
Public Hour As Integer
Public Minute As Integer
Public Second As Integer
Public Microseconds As Integer
End Class
Then to read the value of the UDT:
Dim MyUDT as DateTimeUDT = EthernetIpForCLXCom1.ReadUDT("MyUDT",GetType(DateTimeUDT))
NOTE : Creating a class with public fields is considered bad OOP practice. But in order to map arrays, it was necessary to bend that rule a little to make the ReadUDT possible.
-
Definitely good news, thank you Archie.
-
As of 3.99y Beta 30, there has been a change in ReadUDT to use generics. The new format is like this:
Dim MyUDT As DateTimeUDT = EthernetIPforCLXCom1.ReadUDT(Of DateTimeUDT)("MyUDT")
-
As of version 3.99y Beta 11, it is now possible to read and write complete UDTs into an equivalent class. To use this, you must create classes and map the data types from CLX to .NET equivalents. The following link has a chart that shows the data type equivalents:
https://advancedhmi.com/documentation/index.php?title=WriteUDT
According to this SINT = SByte. But what about USINT? Can I delcare it as Byte and read/write it with ReadUDT/WriteUDT?
-
According to this SINT = SByte. But what about USINT? Can I delcare it as Byte and read/write it with ReadUDT/WriteUDT?
Unsigned tag types are not yet supported, but I will look into getting this implemented in the next beta version.
-
According to this SINT = SByte. But what about USINT? Can I delcare it as Byte and read/write it with ReadUDT/WriteUDT?
Unsigned tag types are not yet supported, but I will look into getting this implemented in the next beta version.
Unsigned types were added to the 5580/5380 platform only, v32 and above. Also, Micro800 series. I'm sure you already know but data types for reference (forgive the extra nonsense):
0xc6: (1, "USINT", '<B'),
0xc7: (2, "UINT", '<H'),
0xc8: (4, "UDINT", '<I'),
0xc9: (8, "LWORD", '<Q'),
0xcb: (8, "LREAL", '<d'),
Edit: Maybe you are already supporting those types and you were referring to adding support for read/write UDT specifically. My bad if that statement is true...
-
According to this SINT = SByte. But what about USINT? Can I delcare it as Byte and read/write it with ReadUDT/WriteUDT?
Unsigned tag types are not yet supported, but I will look into getting this implemented in the next beta version.
Unsigned types were added to the 5580/5380 platform only, v32 and above. Also, Micro800 series. I'm sure you already know but data types for reference (forgive the extra nonsense):
0xc6: (1, "USINT", '<B'),
0xc7: (2, "UINT", '<H'),
0xc8: (4, "UDINT", '<I'),
0xc9: (8, "LWORD", '<Q'),
0xcb: (8, "LREAL", '<d'),
Edit: Maybe you are already supporting those types and you were referring to adding support for read/write UDT specifically. My bad if that statement is true...
I thought it needed to be implemented for both reading individual tags and parsing when Reading/writing UDTs, but after looking I see support for those new tag types were already implemented when reading them individually. So only parsing the UDT byte steam into equivalent classes needs to be implemented.
-
According to this SINT = SByte. But what about USINT? Can I delcare it as Byte and read/write it with ReadUDT/WriteUDT?
Unsigned tag types are not yet supported, but I will look into getting this implemented in the next beta version.
Unsigned types were added to the 5580/5380 platform only, v32 and above. Also, Micro800 series. I'm sure you already know but data types for reference (forgive the extra nonsense):
0xc6: (1, "USINT", '<B'),
0xc7: (2, "UINT", '<H'),
0xc8: (4, "UDINT", '<I'),
0xc9: (8, "LWORD", '<Q'),
0xcb: (8, "LREAL", '<d'),
Edit: Maybe you are already supporting those types and you were referring to adding support for read/write UDT specifically. My bad if that statement is true...
I thought it needed to be implemented for both reading individual tags and parsing when Reading/writing UDTs, but after looking I see support for those new tag types were already implemented when reading them individually. So only parsing the UDT byte steam into equivalent classes needs to be implemented.
After I had posted, I thought I remembered us discussing this when v32 first came out. I remember borrowing hardware to test this in python.
-
I need read a Array of UDT with size 10, in C#.
I have a error in command .ReadUDT. See attachments.
public struct UDT
{
public Int32 Yr;
public Int32 Mo;
public Int32 Da;
public Int32 Hr;
public Int32 Min;
public Int32 Sec;
public Int32 uSec;
}
UDT[] Dates = new UDT[10];
Dates = CLXCom.ReadUDT("Dates",10);
-
Your code should probably be more similar to this:
public struct TimeUDT
{
public int Yr;
public int Mo;
public int Da;
public int Hr;
public int Min;
public int Sec;
public int uSec;
}
private void MainForm_Load(object sender, EventArgs e)
{
var Dates = CLXCom.ReadUDT<TimeUDT>("Dates[0]", 10);
}