LabVIEW
nested vi loop
Solved!
There are plenty of solutions and it really depends how th rest of the code looks like.
For example you could give a reference to an indicator on the main VI to the subVI and the update it from within the subVI via a value poperty node.
- Did you notice that your VI uses 100% of a CPU core when not doing anything, spinning as fast as the CPU allows?
- What posessed you to change the mechanical action of the OK button to "latch until released"? That is a very unusual mode.
- Shouldn't that loop in the subVI be a FOR loop? You know the number of iteration before the loop even starts.
You could use Queues, User Events, Notifers, or Global Variables to pass the data up to your main VI. This will require that your subVI runs in parallel to everything else in your main VI. I am partial to the User Events route. Another option is to use a subpanel that you can load your subVI's front panel into to show the indicator.
Now that I have had a quick look at your code...
That subVI should use a FOR loop since you know how many times it will run. And with that knowledge, you could use a progress bar on the subVI and have the subVI pop up when it start running. If you set the progress bar's maximum to be the number of iterations you will have of your loop, it will be a since graphic of the progress of your test.
@altenbach wrote:There are plenty of solutions and it really depends how th rest of the code looks like.
As I said, we really need more information about the full code design.
What else is there? (currently, th code is so sparse that the subVI is not even really needed). Must the main VI code wait until the subVI returns or does it need to do other things in the meantime? What else does the subVI do? What is the purpose of it all?
