How to Create Linked Symbols and Faceplates in Ignition?

Ignition
, , ,
1

Hi everyone,

I am a new learner of Ignition SCADA and I'm currently exploring how to build reusable components.

I would like to learn:

  • How can I create linked symbols (reusable graphics/components) in Ignition?
  • How do I create faceplates for equipment such as pumps, valves, and motors?
  • What is the best practice for passing tag paths and parameters to these reusable components?
  • Are there any step-by-step tutorials or sample projects that explain this process?

Any guidance, documentation, or example projects would be greatly appreciated.

Thank you!

2

Best place to start is by watching the videos at Inductive University(it's free).

In general, creating re-usable templates comes down to using indirect bindings in the template, and having a standardized folder/UDT structure for the device type in your Ignition tags. With these done correctly, you can have a single faceplate that can be used for several models or variations of devices of the same type.

One thing to be aware of is the differences in terminology between Perspective and Vision. Vision has 'Templates' and Perspective has 'Embedded Views'. They are functionally very similar with slight differences.

3

Highly suggest every relevant view in your system take a consistent tagPath parameter which is the root of whatever node (device, component, system, etc.) it is intended to indirect.

I've also found it's also helpful to have views in Perspective largely match the UDT structure to the extent possible, such that if you have an instance of a device UDT=Devices/Manufacturer/Model it will map to a viewPath=viewType/Manufacturer/Model.

4

I do things differently to this. In general, a motor from different manufacturers will have a very high percentage of the exact same tags across all of them. The only real changes are what detailed info you get back from them. I have a single template View pnid symbol for a pump and motor that is used for motors from any manufacturer, given the basic info shown on the device symbol will be the same (for me at least) e.g. status, mode, (speed if relevant), alarms active.

I also have a single popup used for all devices, not just motors/pumps, which contains the skeleton: the title/header, tab navigation bar, etc.. The contents of some of the tabs are what change, based on the UDT definition. There are fixed tabs as well for things that are common across all devices like alarms, interlocks, trends.