What is the property node for the value of a "stop" button?

[Akatsuki]

I would like to know how to use 1 stop button in 2 different location. I tried to use the "value" in the property node but it did not work.

[Kenny_K]

Using the value property node should result in a boolean value (True or False).

You need to make sure that the stop button is not a latch, otherwise the property node will not work.

See the attached example for a property node from the stop button.  It is for LV8.0.

[johnsold]

Stop buttons usually have a latching action, so they reset after they are read. The Value property may be accurately representing the value of the button at the time the property node is read. Better to use a notifier or queue to transfer the value to the other loop.

Lynn

[Akatsuki]

I don't quite understand and the example uses version 8.0 (I have the 7.1).When I use the property node "value" it shows up in a dark purple color.  I would like to have it as a true/false value (green).

thank you for your time,

Regards,Noel

[Kenny_K]

Try this:  Create the property node and then create an indicator.  You will prob get a listbox that will tell you in string format what the value is. (happened to me the first time).  Then delete the indicator, change the stop button from latch to switch (right click the stop button go to mechanical action >switch when pressed) and wire a boolean indicator (like an LED) to the property node, and it should turn green.

The property node will be purple when the stop button is  alatch and green (boolean) when you have it as a switch.

Here it is in 7.1

[Akatsuki]

Thank you very much!!

[Akatsuki]

It does work, but it is a bit incovenient since the user will have to push back the "stop button" at the end of the experiment.

[Kenny_K]

This is true.  What you can do is make a simple state machine, that when you press stop, go to the next state and then reinitalize the button to default (aka when it was false), essentially "unclicking the button".

This will work for simple VIs, if you have a more complicated VI, I would go with the other post that suggested notifiers or queues.

You could even go with producer consumer type VI and you would not have to worry about it being a latch or switch.

Kenny