LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

SubVi Button Control


nicholas03 wrote:
I trying to understand if the Buttons should be saved as VI's, Type Defs or Controls.

I don't understand at all what you mean by that sentence.

 

From what I can tell, you use standard buttons and just change the boolean text at runtime. There is no need to save these seperate from the main VI.

Message 11 of 14
(871 Views)

Lets say I have more than one button but my problem is that the boolean text is unable to change in sync with the button pressed. For example, I press button 1 (Idle) and changes Button 1 and Button 2 to (Waiting for Gel).  with the Vi you posted earlier.  I was hoping to learn how to change the boolean text in the first thread. Anyways, all I am trying to do is make the buttons change independently.

The attatched Vi is an example I made that changes one button that I want. I do not know how to make 8 act in the same way, independent of eachother.

0 Kudos
Message 12 of 14
(860 Views)

Perhaps our problem would be easier to spell out with this flow chart. I am trying to keep the program as simply as possible by making SubVis.  What I describe as a button is really supposed to be a small part of the whole system. It mearly works as a switch to turn the data flow on and start building arrays.

 

Message Edited by nicholas03 on 01-26-2009 07:31 PM
0 Kudos
Message 13 of 14
(804 Views)

nicholas03,

 

When adding buttons, you need to create code to compensate for each additional button. This can be done by adding event cases for each button and using a case structure to define which button's boolean text will be modified. Just be sure that you keep track of the current text in each text like the way it was done in your example 5.vi so that you can continue updating in the correct order.

 

I have attached another method that you could use as well.

Will
CLA, CLED, CTD, CPI
LabVIEW Champion
Choose Movement Consulting
choose-mc.com
0 Kudos
Message 14 of 14
(781 Views)