Contents
Cirrus Link Resources
Cirrus Link Website
Contact Us (Sales/Support)
Forum
Cirrus Link Modules Docs for Ignition 7.9.x
Inductive Resources
Ignition User Manual
Knowledge Base Articles
Inductive University
Forum
...
NEED IMAGE
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.
...
Ignition and Azure Digital Twin Twins use different terminology for similar constructs. Those definitions are below.
Ignition
'UDT parameters' are mapped to 'ADT Attributes'.Ignition 'UDT member tags' are mapped to 'ADT Measurements'‘UDT parameters’ are mapped to specific digital twin property called ‘templateParameters’.
Transform, Metric, and Hierarchy definitions in
ADTAzure Digital Twins are not used by IBAZ.
...
Azure Digital Twin only supports Booleans, Integers, Doubles, and StringsBoolean, Date, DateTime, Double, Duration, Float, Integer, Long, String, and Time. As a result, this is the list of data types in Ignition that are supported for consumption into Azure Digital Twin.
Boolean
DateTime
Double
Float
Integer
Long
Byte
Will(will be up-casted to an Integer
in ADT)
Short
Will(will be up-casted to an Integer
in ADT)
Integer
Float
Will(will be up-casted to
ana Double
in ADT)
Double
String
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 ** Nested/Hierarchical User Defined Types (UDTs)
...