@Electro0000 wrote:
I guess we 're talking about asynchrony...
Electro0000,
Are you also lolobosco?
If all of the While loops are basically executing the same code in parallel, then you certainly are talking about asynchrony. We did a project a few years ago where we were monitoring behavior by taking videos, and we needed to handle 24 stations. We wrote a single sub-VI that managed one station, then used Start Asychronous Call, with the Station Number as a parameter, and called 24 "clones" that all ran simultaneously. Worked like a charm.
Here's what you need to do to make this work:
- Design a sub-VI that will handle one "instance" ("Process"). Have a parameter ("Proceso #") that will index which process you are calling. You can use this however you need to in distinguishing your processes.
- Configure this VI to run as a Pre-Allocated Clone.Reentrant Execution.
- Do not use a Local Variable to stop the loops. Use a Notifier, a VIG, or something similar that you can trace and that won't cause any race condition.
- In a For Loop, "spawn" all of your Processes. Do you know how to configure Start Asynchronous Call functions? I like to use a Static VI Reference to "point to" the VI I'm spawning, right-click and make it a Strictly-typed Reference, drop a Property Node and wire the reference to get the VI Path, wire the Path and the Strictly-typed Reference to an Open Vi Reference. Note that you need to set the Options flag for Call and Forget (x80) or Call and Collect (x100). You might also need to include the Simultaneous Rentrant Calls (x40) flag.
- Wire the VI Reference to the appropriate Start Asynchronous function that you intend to use.
You may notice that I'm a little vague on whether or not you need the x40 option flag. In our code, we did not set it, yet our cameras all run simultaneously, in parallel, and their sub-VIs are definitely set to Pre-allocated Reentrant Clones. We stop them using a VIG.
Bob Schor
