Hi,
I plan to use the same HMI project for similar machines. These machines have different modbus mapping but will have similar features.
To avoid fixing binding for each component level, when tag is deleted and replace.
I believe it is best to use reference tag as place holder.
Is there an easy way to batch edit reference tags to change each source path? instead of editing each tag individually?
Thank you.
Why do you need reference tags? You are not required to make Ignition tags with any relationship to the underlying OPC item path. Just make a unique folder of tags for each machine. Use folder names that make sense for your hierarchy of divisions/facilities/lines/machines (or desired fragments thereof). Within the folder, use the same names for the tags in each machine. Set the opc item path appropriately for each tag in that machine. Where there are patterns to OPC item paths, you can (but aren't required to) use UDTs to automate tag creation.
In your user interface pages/views/windows/templates, define a tagpath property to be filled in by your menu or other navigation. The tagpath would hold the folder name for a machine, and would be used in indirect bindings within your UI to point at the right data to display/edit.
One problem I am trying to solve. I got lots of tags.
Project to Project the tag names are the same, the folder where these tag can be found are the same.
But the underlying opc item path of these are different on different projects.
Presumably there's some organization in your PLCs? Use UDTs to apply the per-project PLC organization and yield a common folder-like set of named tags.
If you don't have any repeating organization in your PLCs, then you will have to map each OPC tag separately anyways, so you may as well map them to tags into folders with common naming.
In either case, design your UI components to accept a tag path parameter pointing at a folder, and append the static name parts in their indirect bindings.
i think, I am following with what you saying.
create a UDT such that, it will take opc items and convert them to desired member tags (voltageTag).
On Tag browser, use the wizard on the desired folder hierarchy to create the Tags.
The resulting tags will always have an instance folder before the actual tag. Therefore these tags will be identified from their instance folder, right?
Example:
udtInstance1/voltageTag,
udtInstance2/voltageTag,
and so on.
Then, Create a view with custom parameter, that accepts a tag "path prefix"? is this what you were saying?
instead of creating custom param that accepts 1 digit, to be interpolate to a path in the indirect tag binding.