Real time not supported Boolean mechanical Action Latch Until Released.
If Someone has a suggestion how I can made a button with this feautre on Real time, it will very helpful.
make it a switch. When switch is TRUE then do whatever you want to do and reset the switch to FALSE using a local variable. (Or use the BooleanCrossing function to detect edges of the boolean signal.)
Why do you insist on latching behaviour of a switch on a target (probably) without an UI?
Thank you so much for your help.
I did what you tould me but it does not work because the principal problem is the mechanical action. I need to hold true value when I hold pressing the button and when I am not pressing the button has to change to false.
have you tried the "switch when pressed" mode?
Are we talking about a button on an UI - or do we talk about a real hardware button?
What kind of RT do you use?
RealTime system means you do not have a GUI, at least not in a deployed system. So options include using a mechanical switch with a digital input or making a GUI that runs on a Windows system and sends commands and data via an Ethernet connection.
I am using a switch pressd modue. I working with a button on an UI of Labview.
I am using CompactRIo (CRIO 9035).
All the time, I am working on CompactRio because the button have to be working on CompactRIO. Then, The button I am uploading on CRIo and I want to change the value on the console that is connected on CompactRIo.
I can not run a mechanical switch on Windows and sends the commands via an Ethernet because the button has to be running on the CompactRio because there is a screen connected on the CompactRIo where I can change the value of Button.
RealTime system means you do not have a GUI, at least not in a deployed system.
Did you forget about the Linux RT with HMI? I love those little things and have a USB keyboard, mouse, and monitor hooked up all the time for controlling running tests without needing an industrial PC connected to it.
In these cases I do as Gerd mentions, make the boolean a switch, then reset it with a local variable when you want. Then this same UI can be used as a remote front panel, a HMI connected to the cRIO/cDAQ, or with a web page in a browser on any phone tablet or PC on the same network. In this case value change event structures can even work too, no need to poll controls on RT if the embedded UI is enabled. If it isn't then it is back to polling buttons once in a while.