williamlove
Member
[For clarity and brevity I will make this example more simple than what I actually have. I'm using FactoryTalk SE ver 8, local app.]
Let's say I have a screen called Pump with one display object, a multistate indicator (with two states) that looks like a light. The light is animated by tag [PLC]Pump_1_On.
Now lets say I replace that tag name with #1 and use a parameter file with #1=[PLC]Pump_1_On. And for pump 25, I'd have #1=[PLC]Pump_25_On. But that is not very efficient.
Do I really have to have a separate parameter file for every pump? In other words if I have 150 pumps do I have to have 150 parameter files?
Or can I make the Connection be something like [PLC]Pump_[#1]_On. If that were possible, I'd only have to change the pump number in the calling command.
Or am I stuck having to have as many parameter files as I do pumps? Would using Global Objects (which I have not tried out yet) allow me to do what I want to do (which is pass a pump number when I open a screen and not have to have 150 versions of something to maintain)?
Let's say I have a screen called Pump with one display object, a multistate indicator (with two states) that looks like a light. The light is animated by tag [PLC]Pump_1_On.
Now lets say I replace that tag name with #1 and use a parameter file with #1=[PLC]Pump_1_On. And for pump 25, I'd have #1=[PLC]Pump_25_On. But that is not very efficient.
Do I really have to have a separate parameter file for every pump? In other words if I have 150 pumps do I have to have 150 parameter files?
Or can I make the Connection be something like [PLC]Pump_[#1]_On. If that were possible, I'd only have to change the pump number in the calling command.
Or am I stuck having to have as many parameter files as I do pumps? Would using Global Objects (which I have not tried out yet) allow me to do what I want to do (which is pass a pump number when I open a screen and not have to have 150 versions of something to maintain)?