That's the one thing I haven't stored in my PLC are descriptions on trips/interlocks. Considering I have 32 strings in an array, it gets heavy and hogs memory quickly on larger systems. In WW I always extracted them from rung/tag descriptions directly out of an L5X, then stored them in XML files. Haven't had to do one in FactoryTalk yet, but would probably do some sort of separate string arrays in the PLC for it. In Ignition, I initially extract them out of the L5X like I do with WW, but then just store them in a string array.
What does this have to do with importing into Logix/Studio?
Ah, though you were trying to go the other way. (I can't do that yet....)
1 Like
This is what I use to do. I even had memory tags that stored the engineering unit and display format for each analogue, and maybe min/max? Since you can't bind to tag props (what little they have) from a tag very painful. Making a single template for an analogue value to use the display format tag was super fun, stacking a zillion objects on top of each other each with a different display format set
those were the days..