Ignition UDT definition with several tags, one of which is a boolean used for triggering the other tags to poll when transitioning from false to true.
One shot driven tag group created with the driving expression set to the UDT data type trigger tag, with the driving comparison set to equals true (1.0).
Multiple instances of the UDT created using parameters in conjunction with a common namespace from the PLC for easy duplication.
For any UDT instances, the tags associated to the tag group do not update on the trigger firing. When I update the driving expression of the tag group to a specific instance of a trigger tag, it works. I was hoping to create one tag group per UDT, but it appears I may need a tag group per UDT instance, which will greatly increase the number of tag groups. Is this correct or am I misconfiguring something?
This will not work. The UDT Definition has no data to provide. As you noted it works with a "specific instance of a trigger tag".
You would need a different Tag Group for each independent execution trigger.
Tag Group is a property assigned to each tag in the UDT instance. The logic of that group will be applied to all of the tags. If every instance uses "One-Shot Trigger Group" , they will always be executing together. If each UDT instance needs to fire independently then each has a different execution trigger.
So I'm a little bit curious as I see that recently "Data Types" got added to the driving tag selector in the tag group editor. Can you speak to why this would be added if it serves no purpose? Or am I just misunderstanding?
As far as I know the root "Tags" folder shows all items within the Provider being used, I would always expect UDTs to be in the that folder regardless of where I am viewing it.
I don't know of a use for targeting definitions in this specific context, other than perhaps targeting default setpoint values, but the folder is used in several contexts.
