It is my first time using ignition and I’m trying to create an alarm box graphic on my Valve template. I currently have 4 alarm boxes (red:critical, orange:high, yellow:medium, lilac:low) and I was trying to make them visible using a tag binding on the visible property, using the isAlarmActiveFiltered(). The problem I have is on the tagPath part - I’m not sure what format I need so that my box becomes visible whenever an alarm associated with the instance is active. My custom property on my template is ValveData which is my valve UDT. When I use the wildcard “*” it becomes visible if another instance has an alarm set too, which obviously I don’t want.
If anyone can help that’d be great, and any suggestions as to alternative ways would also be appreciated!
What version of Ignition are you in, and I assume this is in Vision not Perspective?
As an aside, UDT Type ui parameters are grossly misrepresented in the ia training videos as being useful. They were a nice idea, but they fall far short and can hinder development and can cause performance issues. I would recommend moving to passing in a tagpath to the UDT instance and using indirect bindings to the tags you want to read and write. Lots of topics on this on this forum
It’s not about its commonality (it’s likely very common for newcomers especially ones who’ve been through the IA uni - unfortunately the marketing grip on this one is strong, and we all know how marketing relates to reality…), it’s about the issues associated with using UDT Type parameters. As an analogy, it’s common for people to speed while driving, but it puts them at higher risk of many horrible things and also limits their choices, like control of steering. Same for UDT Type parameters.