Multi-threaded undercutting of dual locks in TestSTand 3.0

[TonyJ]

Group,

    I have a test sequence that is running 16 threads to test radios.  About midway into my testing one of the threads will some how take priority and will not wait for another thread to finish its testing.  The first time a thread executes a series of tests all is fine.  But when the second or later thread attempts to run the same code it is always stops waiting for the thread that is one dual lock ahead of it.  Let me setup the condition.  Assume Thread 1 is just finished with Lock Audio and Thread 2 begins executing Lock Audio.  At some point in the middle of the dual locks sequence, Thread 1 takes priority and begins running its test leaving Thread 2 having not finished its set of tests within the dual locks.  In fact, thread 2 is unable to do anything until thread one has gone completely through its entire sequence file.  How can one thread countermand the previous thread.  Example of testing below:

Lock Audio

Lock PortAA

   Take a measurement

UnLock PortAA

Lock PortAA

   Take a measurement

UnLock PortAA

UnLock Audio

Lock VolumeMax

Lock PortAA

   Take a measurement

UnLock PortAA

Lock PortAA

    Take a measurement

Unlock PortAA

UnLock VolumeMax

..........etc..............

[James_Grey]

Did you mean to have an unlock audio in the middle? It seems odd that Port AA is sometimes used under the audio lock and sometimes not. It makes me think you might not really be locking/unlocking the locks that you intended to.

[James_Grey]

If all your locks are correct, maybe it would help to post screenshots of your sequence with arrows drawn that point out exactly where the unexpected thread release occurs.