One of our integrators had started on building some of the common ones as Ignition templates. Not sure if they finished them all or not. But yes, it’s certainly doable (and would be fantastic if they were released!)
Our company has done that. I started about 2 years ago ‘pulling’ apart the templates and getting them to work with AOI. Only issue with Ignition is the path to the PLC in the OPC-UA server is different for V21 and up, so i have two sets of templates, v20 and V21+
OK,
here is what we done. I will use an Ethernet VFD as an example. We took the Rockwell AOI and stripped out all the BS an nonsense, and optimized it as our own:
I created a template based on the PlantPax template for a VFD. When area around pump is pressed, template popup is called passing the template tag as a parameter
I need to add that each of the ‘tabs’ are just a container that has visibility enabled based on the menu button pressed.
Home button sets display property to 0, Info button sets a display property to 1, etc.
Each container’s visibility is based on value of the property.
0 = Home Visible
1 = Info visible
etc
Indirect template tags are used every where, where the path to the template tag is passed into this ‘popup’ as a parameter.
Our company has done this.
PAx objects are VERY tag intensive.
I know the guys had to do some weird stuff to keep the client update rates decent. Otherwise things grind to a crawl tag update wise.