Support Forum: Neosoft DQMH TestStandifier

[Anthony11121]

It is a singleton. I created a new DQMH singleton using the latest version of DQMH and generated the TestStandifier outputs. It does now display the running module in the tester as expected. I must have had a problem with the old module I was trying to use. Thank you for the quick response.

[Anthony11121]

I have created a TestStand sequence that calls TestStandifier-created sub-sequences for my DQMH module. I am calling Launch Tester in the Setup section and Stop Tester in the Cleanup section. When I do repeated executions of the test sequence, there is a new tester launched in a new thread and old testers are still running in other threads until I close LabVIEW.

What is the proper way to launch and close testers? Is there a way to kill the thread of the tester in a cleanup step?

[CyGa]

Hi Anthony,

You should have a stop tester seqeunce call to actually close the tester.

What may happen is that TS is caching the tester and it stays open (but idle) until you unload modules (TS Seq Editor menu -> File -> Unload all modules).

[Anthony11121]

The Stop Tester sequence call does close the tester panel, however, when I run another test and a new tester opens, the new tester does not show the started module or any status updates because there are old testers apparently still executing in the background. I was hoping that Close Tester would have closed the tester completely so that a new tester would work the same as the first one.

[CyGa]

It is supposed to close it !

The TSifier specifically script a VI which finds the tester and makes use of user32.dll to simulate closing the window (like if a user clicks on the Windows' window red X button). The call is made twice : one to stop the etster, and the second to actually close the window and so making it leaving the memory.

Unless the tester was modified to alter the default behavior, it should work. At least it works on many projects already (ours) and until today nobody reported this kind of behavior.

Did you modify the tester default behavior ?

Would you be able to share your code ?