10-13-2006 01:38 PM
10-14-2006 05:22 AM
Hi,
The easies way is to put you labview step in it's own sequence and then call that sequence via a SequenceCall steptype. You can then set the sequencecall step to run in a seperate Execution or Thread.
In you main sequence you can add a wait step to wait for that new execution / new thread to complete before closing the main executions.
Hope this helps
Regards
Ray Farmer
10-16-2006 02:43 PM
10-17-2006 02:31 PM
Hello,
I know how to run a sequence in a separate thread, but the tricky part is to constantly update the controls of the second thread while its running in parallel with thread 1. Thread 2 will be running in a loop to monitor a Digital Card. If an unexpected digital output occurs, thread 2 should set a flag and exit execution. Then thread 1 will use that flag to perform a particular task.
I hope this is a better explanation of what I am trying to do.
Regards,
Ayman
10-18-2006 05:15 PM
10-19-2006 09:11 AM
10-19-2006 03:25 PM
Hi,
Are you expecting to change the values sent to your VI from the data you input in the MessagePopups in the For / next loop.
You will have to pass the SequenceContext to you VI so that you can use the activeX invoke Node and use the GetValNumber() method to pick up the new values from the FileGlobals.
One other thing. If you use the 'Run VI Asynchronously' method then you dont have to put it in a SequenceCall, which has then been set to run in a new thread.
Regards
Ray Farmer
10-20-2006 10:45 AM
10-20-2006 11:26 AM
Thanks Ray,
I used sequence context then invoke node with method GetValNumber, and that worked perfect.
Ayman