Do tags that are disabled incur a load on the Ignition gateway?
IE we have some UDTs in Ignition that contain instances of other UDTs. The outer, or parent UDT, is looking at a one UDT Tag in the PLC (Rockwell), and the inner or child UDT's will be looking at completely different UDT Tags in the PLC. Sometimes that child UDT won't have the tag to look at in the PLC, in cases like that we would like to disable the child UDT in the parent UDT. With that child UDT disabled does that help the tag side of things on Ignition or does it not buy us anything?
Yeah, it helps a little, because if an OPC tag is enabled then Ignition is always going to be trying to subscribe to it until it gets a good subscription. If it doesn't exist in the PLC that will never happen, and you'll have subscription related operations continually failing in the background.
Thanks Kevin. I did see that the Tag count on the PLC will fluctuate with those tags enabled/disabled. I just wasn't sure about the Ignition back end side of things.
Looks like my advice seeking is related to this thread (even if a bit old) and I did not went to create a new thread (or should I?).
What's the case about when using UDT Definitions created in ignition's Tag Browser?
I have a lot of UDT definitions all of them with at least one parameter ex:{OPCserver},{Nr} and tags inside are OPC and some Expression types. Complex UDTs contain instances (child) of other generic UDTs.
All my connections to PLCs are via OPC-UA
I designed UDTs as unified data models and because we have to deal with various devices built by various teams and companies, not all similar devices have all functionalities available.
The OPC Item Path I always (95% of cases) define at the UDT instance level because of this.
I disable unused tags and leave OPCitemPaths empty when dealing with unavailable options.
For child UDT instances inside UDTs, when not needed, I only disable the child UDT instance itself and looks like it propagates to all hierarchically child tags under it. Looks like it's enough?
This approach also disables history taht is defined at UDTdefinitionLevel. Hope it's a safe approach.
My project is already in operation but still under development, and already have 30K tags scattered on two IO servers and growind towards 150K.
What load takes on the server these disabled tags and entire child UDTs?
80+% of my tags are structured on folders and UDTinstances and about 20% of tags inside are always disabled but never the same ones so it would be hard to biuld distinct UDTdefinitions for all scenarios.
Just to mention, that in perspective I constantly check if a tag or a childUDTinstance is .Enabled or not, to display or hide the appropriate function of that process. (of course together with forced invalid paths for entirely disabled embedded views)