LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Non-blocking SubVI output terminals?

Solved!
Go to solution

Depending on the data and what you are trying to do you can also use control references. An example ships with LabVIEW showing you how to update a graph that's on a higher-level VI from a subVI.

0 Kudos
Message 11 of 13
(475 Views)

@smercurio_fc wrote:

Depending on the data and what you are trying to do you can also use control references. An example ships with LabVIEW showing you how to update a graph that's on a higher-level VI from a subVI.


 

See here for images of control references in action.

 

Ben

 

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 12 of 13
(451 Views)

Chiming in:  I think there are some good points to be made.

 

With LabVIEW 2011 this type of behavior IS possible.  That is you can Launch a sub-vi, continu prosessing after launching the sub.vi and get the outputs of the sub vi after the sub vi completes.  As a matter of fact Craig Davis presented example code of this behavior at the Minneapolis LabVIEW User's Group last week watch here for a link to the presentation- He did promise to post it.

 

Here is a discription of the Asynchronous Call By referance feature. And there are some examples that ship with 2011.

 

Combined with a control referance (or two) or a queue you can get just about anything you want

 

Despite all the great points the other contributors made- it is now possible to achive what the OP is asking for if I interperated correctly.


"Should be" isn't "Is" -Jay
Message 13 of 13
(443 Views)