I’m working on a PLC stress test with Ignition, we’re testing out how well we can do historian on two PLC’s with varying amounts of resources allocated to Ignition. I have two PLCs, an Allen Bradley Micrologix and a Click PLC, both with 100 int tags each that I want to make a history for. For the Allen Bradley the consecutive registers for 0-99 under N7. For the Click I am not sure yet.
What is the easiest most maintainable way to create these tags (maintainable being if I want to change something for all 100 tags, I only change it one place)? My memory says this would be a time for me to create two UDT’s (on for each PLC) with one parameter a number from 0 to 99 that will correspond to the correct tag path. Inside the UDT the historian will be checked off as well.
- Is this a reasonable way to do this?
- What is the method for creating say 100 instances of the UDT with the parameter being 0 for the first, 1 for the next, etc? I cannot recall what feature was called or how to access it.
- I’ve seen lots of posts about configuring tags with scripts seems - would that be a better way of doing this? What would that methodology look like and were would that script be called? As a oneshot, inside a gateway event, any pitfalls?