Can i do freeze a signal ( DI or DO) from graphics push button directly to controller hardware.
So that i can avoid hardware push button.
In that case which push button need to use. using control builder M professional 800xA 5.1 version.
freeze a signal ( DI or DO) from graphics push button
-
- Posts: 27
- Joined: Mon Dec 30, 2013 5:23 am
-
- Posts: 894
- Joined: Sun Apr 11, 2010 3:00 am
- Location: Russia
Re: freeze a signal ( DI or DO) from graphics push button
This is called "Forced". Available from the faceplate of standard function blocks (in SignalLib library).
-
- Posts: 27
- Joined: Mon Dec 30, 2013 5:23 am
Re: freeze a signal ( DI or DO) from graphics push button
ple send the procudure
-
- Posts: 27
- Joined: Mon Dec 30, 2013 5:23 am
Re: freeze a signal ( DI or DO) from graphics push button
Suppose i have a selector switch to give a selection like local mode selection. by using the selector switch if i on/off the switch then it make true or false the hardware input.
now how can i do this by process graphics -2. need procudure
now how can i do this by process graphics -2. need procudure
-
- Posts: 894
- Joined: Sun Apr 11, 2010 3:00 am
- Location: Russia
Re: freeze a signal ( DI or DO) from graphics push button
What kind of procedure should be? This switch is located right on the object faceplate - buttons Set/Reset Force state.
When you click "Set Force" from (e.g.) SignalInBool faceplate the last channel value (from "In" IO) will be copied to the "Out" output and buttons "Activate"/"Deactivate" will be enabled for the operator intervention to the process. Further changes of the IOValue in "Forced" mode will be omitted.
However, if you need to set the "Manual" mode from a logical input the "SignalInBool" block is not suitable for this.
Then it better to make your own functional block that provides "manual mode" activation from the logic or check for the library solutions (such as Pulp & Paper library).
But as you said
The manual mode is not directly controls the IO - it is rely on the process and safety interlocks and thus it is not always send/receive an operator-entered value to/from the logic/channel.
When you click "Set Force" from (e.g.) SignalInBool faceplate the last channel value (from "In" IO) will be copied to the "Out" output and buttons "Activate"/"Deactivate" will be enabled for the operator intervention to the process. Further changes of the IOValue in "Forced" mode will be omitted.
However, if you need to set the "Manual" mode from a logical input the "SignalInBool" block is not suitable for this.
Then it better to make your own functional block that provides "manual mode" activation from the logic or check for the library solutions (such as Pulp & Paper library).
But as you said
it is assuming you need the "force" mode.azgor_03 wrote:an i do freeze a signal ( DI or DO) from graphics push button directly to controller hardware.
The manual mode is not directly controls the IO - it is rely on the process and safety interlocks and thus it is not always send/receive an operator-entered value to/from the logic/channel.