Ignition & Rockwell PlantPAx v5.0

[pturmel]

3b) Yes. That is what I recommended be done before I added the Client driver type to my EtherNet/IP module. See this old comment:

Cannot read some tags inside Rockwell AOI

Well, I usually use three UDTs for my AOIs. The AOI gets the base name (xyz, perhaps) for its functionality. The others: xyz_fbk This is the collection of values that present the process variables, indicators, trigger integers, etc. Subscribed in Ignition with a fast pace, or mapped through my E/IP module from a PLC output buffer. xyz_cmd This is the collection of setpoints and command bits and handshake short integers. Subscribed as needed (slow/leased is fine), but usually mapped t…

Many users reported huge performance gains with that approach, with the IA driver.

3c) My driver reads entire UDTs or AOIs when any two items are to be read at the same pace and the UDT fits in the buffer. IA's driver uses additional merging criteria. But yes, reduce request count, reduce request complexity, and aim for nearly-full buffers per request.

4. Eh, no, that sounds like a nightmare for UI design. You should have UI components that only need a tag path string parameter to satisfy all of the indirect binding requirements within. And an Ignition tag hierarchy that meshes with that.