I'm running into a weird issue with one of my UDTs I've created. I have a general alarm UDT that I use to map all of my alarms into Ignition. I then create instances of the alarm UDT as needed within an analog input UDT. I'm having an issue where on the definition side I've disabled one of the tags, but the instances show an error in configuration.
Here is my UDT definition for the specific tag:
And this is an example of an instance in error:
Any thoughts why this might be happening?
In the definition screenshot you have the Memory Tag icon for Latch Enable, and are overriding the Value Source in the member tag, but in the instance with the error the Latch Enabled tag is showing the icon for an OPC Value Source tag (Rectangle).
If OPC is the default type, and if that Bad_NodeID error says "The node id refers to a node that does not exist in the server address space" - then that tag thinks its an OPC tag for some reason and is erroring about the lack of OPC Item Path. It does contradict the "memory" string shown in the ValueSource at the bottom, but the icon and error indicate OPC.
Also, your second screenshot doesn't show the override icon.
I fixed my issue by deleting and recreating the instance of the alarm UDT within my Analog UDT.
