11-15-2013 07:31 AM
Refer the image below - a simple timed loop should run when the Run button is pressed. What happens is that the parallel vi runs (see arrow) but the vi inside the loop doesn't. Both vi's shown run forever (i.e. the timed loop is only used to specify the CPU).
When I press the Abort Execution button, strangely it can then be seen that the execution highlighting runs into and through the timed loop and probe 50 is updated.
This sorted itself out after I closed the project and opened it again so its not a critical issue - was simply wondering what could cause this?
11-15-2013 10:24 AM
That program looks kinda weird.
First of all, avoid to use flat sequence structures whenever you can, or use it only when you are going to initialize something, or when your program has an specific sequence.
I think you have a problem the way you are conecting the subvis. Remember that in LabVIEW, the flow of the data will determine the order of execution, and in your case, the conections looks kinda weird.
I have a question; Do the subvis need to run simultainously?, or what do you need to do exactly
11-15-2013 12:27 PM
Not so weird actually. Both vi's run simultaneously using a copy of the same class object (class contains queues, dvr's etc for communication between the two).
Your comment about the sequence: If you know of another way to specify the CPU core to run on then post it here. Sure I could have used a timed loop instead of a timed sequence but in this case it is equivalent and actually simpler than a timed loop.