If we implement a TagChangeListener interface and subscribe to tags using
context.getTagManager().subscribeAsync(tagPath, this),
do the tagChangedEvents share threads with the 3 thread limit of tag change scripts? I know it has been brought up before to move scripts that may take longer than 10 ms into GatewayTagChangeScripts, but we are doing this script work inside of our custom modules.
You actually have to be even more careful in this case. For each Tag Provider these callbacks are queued and delivered on a single thread.
Hmm. Good to know.
I have X number of devices using the same number of tags, but they can be dynamically added using our user interface and module.
We want to monitor a number of tags on the UDT instances created, but we want to monitor them from an Ignition module. If TagChangeListeners are sharing a thread, what is a better way to do it from within the module?
I would use the listener, but just have it package the event content into a new object, and place your own runnable for it on your own thread pool executor.