LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

How do you display continuous, realtime data without sacrificing user control functionality?

Solved!
Go to solution

Hello,

 

I've created a vi (see attached) that displays a signal when the user selects the start/stop button. The user can pause the signal by selecting the same button. The "collect" and "stop collect" buttons each display a message when selected, and the "exit" button stops the vi.

 

What I would like to do: Have the user be able to start/stop the signal, and be able to call the functions from the "collect", "stop collect", and "exit" buttons, regardless what state the start/stop signal is in.

 

What is actually happening: Buttons do not function if not selected in a specific sequence. For example, clicking the "stop collect" button then the "start/stop" button, the signal will not be displayed. But reverse the order and the signal will be displayed.

 

Why does the loop that contains the signal simulator intefere with the loop that contains my event structure for my buttons? I'm using Labview 2013.

 

 

0 Kudos
Message 1 of 5
(2,406 Views)

The "stop collect" button is the one that stops your simulate signal loop. If you click it first, you don't have any signal to display. Double-click on it in the BD, you'll see.

 

Cameron

 

To err is human, but to really foul it up requires a computer.
The optimist believes we are in the best of all possible worlds - the pessimist fears this is true.
Profanity is the one language all programmers know best.
An expert is someone who has made all the possible mistakes.

To learn something about LabVIEW at no extra cost, work the online LabVIEW tutorial(s):

LabVIEW Unit 1 - Getting Started</ a>
Learn to Use LabVIEW with MyDAQ</ a>
Message 2 of 5
(2,390 Views)

I understand where it breaks, but I don't understand why, as the condition for the signal loop is not dependent upon the event structure. Shouldn't the "start/stop" control function correctly regardless of whether or not the "stop collect" control is selected first?

0 Kudos
Message 3 of 5
(2,373 Views)
Solution
Accepted by topic author curious_and_learning

No, that loop is done. In your diagram, it starts up when your program does (although you also need to hit the start/stop button to generate data), and once it is stopped, there is no way to start it again.

 

Cameron

To err is human, but to really foul it up requires a computer.
The optimist believes we are in the best of all possible worlds - the pessimist fears this is true.
Profanity is the one language all programmers know best.
An expert is someone who has made all the possible mistakes.

To learn something about LabVIEW at no extra cost, work the online LabVIEW tutorial(s):

LabVIEW Unit 1 - Getting Started</ a>
Learn to Use LabVIEW with MyDAQ</ a>
Message 4 of 5
(2,369 Views)

Thank you, camerond. I solved my issue with your input.

 

For those as inexperienced in LV as I, I've attached an example (simplified from the one I originally posted).

 

I connected the exit control to the main loop stop terminal and attached a local variable referencing the exit control to the other two loops. I set the exit control mechanical action to "switch until released."

 

 

Message 5 of 5
(2,331 Views)