03-19-2008 12:33 PM
03-20-2008 01:52 PM
03-24-2008 02:16 PM
Justin,
Thanks for your support.
TestStand is going to launch the VB activex engine from a TestStand sequence. I do not want the TestStand Engine complied into it the VB activex application because of the need to have the VBs independent from TestStand compiling. Currently my TestStand code that does the launching not complied as an activex engine.
After the VB is launched the VB application will do a lot of testing. During this period, the testStand will be waiting in the launch sequence for the return from the TestStand launch. While it is waiting for the return from the VB application which is doing Testing, I want TestStand to also be waiting for “signaling events” from the VB activex engine.
I assume I could do this from a parallel process in teststand that waits for the events from the VB active x engine. When the signal comes, I want the parallel TestStand sequence to call another method inside the VB activex Engine to get the status. Then I want the teststand sequence calling for status to end or go to sleep.
I see examples of Labview VIs responding to events but do not call Teststand sequence (callback).
I saw discussions of TestStand call backs which are not called by
So, how can I have a parallel sequence wake up from an external event, do some processing, and then go to sleep or end while the other sequence which did the activex launch is still running?
03-25-2008 04:52 PM