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
...
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 use different terminology for similar constructs. Those definitions are below.
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"
User Defined Types (UDTs)
Nested/Hierarchical User Defined Types (UDTs)
These are not supported currently in IoT Bridge. Azure Digital Twin allows Asset Models to have one or more child Asset Models. Ignition supports UDTs having children UDTs as well as UDTs referencing a parent UDT. However, these hierarchical relationships will not be maintained by IBAZ. Support for simple hierarchies as supported by Azure Digital Twin will be added in a future version of IoT Bridge.
Azure Digital Twin Limits and Quotas
Azure Digital Twin has limits and quotas on many different aspects of asset model counts, asset counts, number or attributes per model, etc. For details on those limits see
...
this document
...
.