LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Called vi from a main one does not stop

Solved!
Go to solution

Hi all,

I am trying to call a vi from a main one, I succedded to call the vi but I could not stop the main vi and the called vi does not stop and dissappeared. Where did I do wrong?

Egemen
0 Kudos
Message 1 of 7
(3,161 Views)

Please post your subvi as well.


CLA CTAChampionI'm attending the GLA Summit!
Subscribe to the Test Automation user group: UK Test Automation Group
0 Kudos
Message 2 of 7
(3,159 Views)

sorry for that. I have forgotten to post it. here it is.

Egemen
0 Kudos
Message 3 of 7
(3,157 Views)
Solution
Accepted by topic author newbieeng

LabVIEW follows a dataflow model for running VIs. A block diagram node executes when it receives all required inputs. When a node executes, it produces output data and passes the data to the next node in the dataflow path. The movement of data through the nodes determines the execution order of the VIs and functions on the block diagram. Source 

 

Once you have called your subVI, your main VI is waiting for it to finish before it can move to the next state in the state machine which is why it won't stop.  If you want to run a separate VI, you can call one asynchronously

0 Kudos
Message 4 of 7
(3,147 Views)

Its because you are back in the same case before you issue a stop command.

So basically your vi finishes execution and because click and run state is selected it runs again. So you need to make sure that you receive data back from the subvi and then based on that set the next state.


CLA CTAChampionI'm attending the GLA Summit!
Subscribe to the Test Automation user group: UK Test Automation Group
0 Kudos
Message 5 of 7
(3,142 Views)

@LewG wrote:

LabVIEW follows a dataflow model for running VIs. A block diagram node executes when it receives all required inputs. When a node executes, it produces output data and passes the data to the next node in the dataflow path. The movement of data through the nodes determines the execution order of the VIs and functions on the block diagram. Source 

 

Once you have called your subVI, your main VI is waiting for it to finish before it can move to the next state in the state machine which is why it won't stop.  If you want to run a separate VI, you can call one asynchronously


Actually all I want to do is to regulate my main vi to prevent it run immediately in execution mode to adjust parameter. I opened a thread about it here. When I build a standalone application and run it into another PC without labview, it runs immediately. It causes problems because there are alot of parameters on it to be adjusted before running. So I am trying to find a solution to adjust this vi in this way. Could you show me a way to do this? I do not know about asynchronously calling of vis so I will read articles about it.
.

 

Egemen
0 Kudos
Message 6 of 7
(3,140 Views)

@.aCe. wrote:

Its because you are back in the same case before you issue a stop command.

So basically your vi finishes execution and because click and run state is selected it runs again. So you need to make sure that you receive data back from the subvi and then based on that set the next state.


I get your suggestions and modify the vi. It works well. Thank you all.

Egemen
0 Kudos
Message 7 of 7
(3,131 Views)