What is the right way to use variables controlled by the two buttons and programming?

First of all, I apologize if this has been discussed before.  I know not how to phrase succinctly the application, so maybe I just missed the search terms.

We have several pieces of the Labview software in the laboratory that automatically control things like the taps and heaters.  Sometimes we also manually control these same things.  I'm moving old NI PCI (and older versions of Labview) maps to a variable and based on compactRIO system shared network.  However, I'm still not on best practices to achieve.  I need to be able to have a script running at any time control panel so that I can access, for example, a valve controller (which is just a Boolean), and I need power open and close the valve by programming other scripts.  I need, of course, the control panel to track the State of the valve until it opens another script, the Panel indicates that it is open, and the next push on the control panel it will close.

Historically, this has been processed using structures business to move from a "computer control" and "hands-on" with global variables that define the State of the valves.  Of course, this is not recommended.

So far, I've played with the help of two variables, a status of valve and the other for the State of button.  The Panel configuration then loops, reads the status of the valve and puts the State of button if the State of the valve has changed.  I can do this with registers at offset or with the structures of the event, but anyway, it gets very crowded and seems inefficient.  Is there a good way to do this in Labview?  It seems this is a common problem, so I hope there is an easy and elegant solution that I've missed.

Variable published use shared network.  Your scenario and your manual of the interface and change the variable and then shared your cRIO reads fair value and writes the appropriate values.

Now for a cool part.  On your manual interface, right-click on your heart control that you want to use to control the shared variable and go to properties.  There should be a data binding tab in the Properties dialog box.  You can bind a control/indicator to a published network shared variable.  So this button will always be attributed to the current state.

Your script should just read the shared variable before resuming to verify that it is in the correct state.

Tags: NI Software

Similar Questions

Maybe you are looking for