When working with UDTs if I export a UDT to csv format and then import that same file the engineering limits are retained but the engineering limit enforcement reverts to “None” for all items.
It would be nice if that value could be retained throughout the export and import process.
On this subject:
-
I create a tag (Tag1) in the designer without engineering-limits
-
Export this tag in xml-format.
<Tags MinVersion="8.0.0" locale="en_US">
<Tag name="Tag1" type="AtomicTag">
<Property name="valueSource">memory</Property>
<Property name="engHigh"/>
<Property name="defaultValue">0</Property>
<Property name="value">0</Property>
<Property name="engLow"/>
</Tag>
</Tags>
- Modify the exported tag-name to Tag2
<Tags MinVersion="8.0.0" locale="en_US">
<Tag name="Tag2" type="AtomicTag">
<Property name="valueSource">memory</Property>
<Property name="engHigh"/>
<Property name="defaultValue">0</Property>
<Property name="value">0</Property>
<Property name="engLow"/>
</Tag>
</Tags>
- Import the tag -> the tags are different!
The imported tag has engineering-limits set to 0 (Low and High)
Why is the result of exporting and importing not the same?
And how can we avoid engineering-limits when importing (OPC-)tags?
What version of Ignition? Might be a bug.
You should open a support ticket. Any format other than JSON are red-headed stepchildren in modern Ignition, and may not be getting the QA they should.