Batchmodel stop button

[Tonnie]

Hello 

For my project i am using Teststand 2014 and C# and us the batch model for the first time. My starting point is the batchUUT.seq example.

This example has a UUT imformation window with a STOP button. In my project I now set the ContinueTesting variable in the PreBatch callback to false. But this doesn't work all the time. Somtimes i get an error saying that is didn't relaesed the seq in cach.. 

My question is, is the a good example how to stop the batch models in C#

[DGuest]

Hi Tonnie,

Thank you for getting in contact.

I have run the example you are using in TestStand 2014 and not experienced any problems with the STOP button.

Would it be possible to confirm a few details?

1. Have you got a specific error message or a screenshot you can attach to this forum?

2. What have you changed specifically for your project?

3. What are you trying to achieve?

I look forward to hearing from you,

Many Thanks, 

David Guest

Technical Support Engineer

Platforms & Systems

National Instruments

www.ni.com/support 

[Tonnie]

Hello

I don't see the error all the time but when i see the error again i will post it here

Thanks for your assistance

[DGuest]

Hi Tonnie,

Thank you for letting me know.

Could you also tell me changes you have made to the BatchUUT.seq file?

Thanks,

David

[Tonnie]

Hello

First of all we use the WATS batch model as a process model. In the PreBatch Callback, the steps "Tell dialog to get Next UUTs" and "Wait for Dialog" or the NI batch model are skipped by Virinco (WATS). WATS has added there its own dialog box, and every thing works fine.

What we want to do is replace that WATS dialog box and use or own dialog box. I only need the option to enable/disable a testsocket and STOP or GO button. What i want to know is what i need to do when someone presses the STOP button. I now change the parameter "Parameters.ContinueTesting" to false, and the test stops but is this enough ore do i have to do more (stopping threats ore something ???)?

[DGuest · Accepted solution]

Hi,

Sorry for the delay, I was away for the past couple of weeks.

I am unfamiliar with the specifics of the WATS model and how they have specifically changed the process model. However, from my understanding of the PreBatch Callback, The CVI DLL code sets the Runstate.Parameters.ContinueTesting and also sends a message to queue the "stop". This all happens before TestStand checks the value for the Continue testing. 

The "Wait for Dialog" sequence works from a message queue which is generated from a combination of user interaction and CVI code. If a message of " " is sent, that sends the "STOP". When TS is monitoring the queue, if there is a specific message it will do the specific action. If there is an empty element then it will "Finish".

Therefore, to change this completely you would need to look into the CVI code underlying the model. 

Hopefully, this helps, if you need more information specific to the WATS model, I suggest contacting their support.

Many Thanks,

David