Page History

...

There are some translations that need to take place between the components and these platforms have different capabilities that result in some limitations in how an Edge Gateway can be configured. For example, UDTs in Ignition support more data types that Azure Digital Twin (ADT) does. As a result, use of data types in Ignition must be limited to those supported by Azure Digital Twin (ADT) in order for data to properly show up and be updated in Azure Data Explorer. 

*** check with Chad ***Mappings

Ignition and Azure Digital Twin use different terminology for similar constructs. Those definitions are below.

• An Ignition 'UDT Definition' is mapped to an ADT 'Asset Model'.
• An Ignition 'UDT Instance' is mapped to a ADT 'Asset'.
• Ignition 'UDT parameters' are mapped to 'ADT Attributes'.
• Ignition 'UDT member tags' are mapped to 'ADT Measurements'.
• Transform, Metric, and Hierarchy definitions in ADT are not used by IBAZ.

*** check with Chad ***Constraints and Limitations

Supported Data Types

Azure Digital Twin only supports Booleans, Integers, Doubles, and Strings. As a result, this is the list of data types in Ignition that are supported for consumption into Azure Digital Twin.

...

Any non-supported data type will be converted to a String in ADT and the measurement value for any instance will show an error with a message similar to "Long is not a valid datatype"

*** check with Chad ***User Defined Types (UDTs)

...