Hi all,
I've dabbled with Red Lion HMI's in the past but I'm now about to use one in a larger scale application for the first time. Hoping some of the Red Lion gurus can point me in the right direction on something...
One thing I like about FTView is the ability to create a generic faceplate for things like drive controls or valve controls. I can either do it using global objects, or just a popup which I call with a parameter file to pick the correct instance. For example, I have a valve UDT in the PLC, which has elements like Valve.OpenPB, Valve.ClosePB, and so on. My valve control global object/popup just has an Open PB addressed to #1.OpenPB, a Close PB addressed to #1.ClosePB, and so on. Then when I call the global object/popup, I point it to the particular valve UDT I'm interested in, and it automatically assigns the Open PB to Valve_I_Just_Called.OpenPB, the Close PB to Valve_I_Just_Called.ClosePB and so on. I only have to build one object/display, and I can use it for as many valves as I want.
I'm certain that Red Lion can do something similar to achieve the same end, but I'm just not sure what the most efficient "Red Lion" way of doing it is. Can anyone point me in the direction I should be looking, or give examples of how you've done it in the past?
Using Red Lion Graphite HMI with AB 5370 Compact Logix
I've dabbled with Red Lion HMI's in the past but I'm now about to use one in a larger scale application for the first time. Hoping some of the Red Lion gurus can point me in the right direction on something...
One thing I like about FTView is the ability to create a generic faceplate for things like drive controls or valve controls. I can either do it using global objects, or just a popup which I call with a parameter file to pick the correct instance. For example, I have a valve UDT in the PLC, which has elements like Valve.OpenPB, Valve.ClosePB, and so on. My valve control global object/popup just has an Open PB addressed to #1.OpenPB, a Close PB addressed to #1.ClosePB, and so on. Then when I call the global object/popup, I point it to the particular valve UDT I'm interested in, and it automatically assigns the Open PB to Valve_I_Just_Called.OpenPB, the Close PB to Valve_I_Just_Called.ClosePB and so on. I only have to build one object/display, and I can use it for as many valves as I want.
I'm certain that Red Lion can do something similar to achieve the same end, but I'm just not sure what the most efficient "Red Lion" way of doing it is. Can anyone point me in the direction I should be looking, or give examples of how you've done it in the past?
Using Red Lion Graphite HMI with AB 5370 Compact Logix