04-20-2010 06:54 AM
What I'm trying to do is set up things so my recurring VIs in the form of a state machine will run continuously. They are not yet incorporated into the VI. I have one CAN device which I multiplex for 10 devices being tested and must run independently. I'm having trouble getting the user interface to work properly where I select the active device and start a burn-in when I put anything in the TimeCheck case to run continuously. How would I go about creating another parallel loop as you suggested and still keep my cluster current. Each burn-in must stop after 48 hours and I have to maintain which devices are active.
04-21-2010 09:42 AM
Hello,
You can keep your cluster current by using a local variable to update the indicator. Just be mindful of the potential to create a race condition and things will be ok.
-Zach
04-21-2010 09:58 AM
I tried a local variable in another loop, but for some reason it's not changing when I change the value in the main loops. The VI is CMM_QueuedStateMachine 5.vi in which I tried that.
Thank you.
04-21-2010 10:47 AM