Data Type Mapping

the following table maps the data types that devicehub offers to those opc ua servers recognizes at the exposed data points devicehub data type opc ua data type bin boolean bit boolean bool boolean int8 sbyte sint sbyte uint8 byte usint byte byte byte int int16 int16 int16 enum16 uint16 bcd uint16 uint uint16 uint16 uint16 word uint16 dint int32 int32 int32 dbcd uint32 dword uint32 udint uint32 uint32 uint32 int64 int64 lint int64 lbcd uint32 lword uint64 uint64 uint64 ulint uint64 fl float flt32 float float float float32 float real float double double dreal double flt64 double float64 double lreal double number double ac3 string ac7 string ac10 string ac12 string ac20 string ac30 string ac40 string attribute string auto string char string custom string date string decimal string dnp3time string dt string dtl string dt6 string hex string json string ldt string ltime string ltod string ostr string range string s5time string single string str string string string tlp string time string tod string uc10 string uc20 string uc30 string uc40 string wchar string wstring string if a device driver supports count, opc ua needs to have an array for the corresponding data type where the array size equals the count value counters and timers are defined as separate structs or data types in most plcs typically, the edge device is used to read the counter acc or timer acc values these values are likely to be of dint or udint type and should be mapped accordingly for example, if devicehub has a tag with data type bool and count 10 , opc ua must have data type defined as arrayofboolean\[10]