PreBatch and PostBatch Callback Modifications

[GeekGrok]

Hello,

   In the TestStand 3.1 BathcModel.seq, the default PreBatch and PostBatch callbacks include steps that call the functions BUUT_GetNextUUTs and BUUT_ShowStatus from the modelsupport2.dll, respectively. These functions appear to generate a user interface panel that allows the user to disable test sockets, view the test status and test report, and to continue or stop testing at the end of a batch test.

   Since I plan on using the full featured operator interface supplied with TS 3.1, the displaying of the model of the second user interface panel by the Pre and Post Batch callbacks to the modelsupport2.dll, does not create a clean user interface flow, in my opinion. In addition, it appears The full-featured operator interface displays the same information (i.e. test socket status, view reports) as the panel generated by the modelsupport2.dll. (Is this a hold out from TS 2.0?)

   Thus my question is that I would like to remove the default PreBatch and PostBatch callbacks and replace the PreBatch callback with a simple message step that will set the Locals.ModelData.ContinueTesting to True (continue testing) or False (stop testing). Would I break anything by removing these modelsupport2.dll functions from these callbacks, since they don't appear to serve a purpose when used with the full-featured operator interface?

   Thank you in advance for your help.

Thank you,

Jim

Message Edited by LabView Newbie1 on 11-21-2005 07:05 AM

[RayFarmer]

Hello,

You would need to provide a bit more than just setting Locals.ModelData.ContinueTesting to True or False.

You would need to modify the Operator Interface to send the message out to stop testing for a particular execution when the user presses a button on the OI. You would have to provide such button(s) as the operator interface doesn't have a button to actual stop testing a UUT. It will have an Abort and Terminate buttons. These conditions aren't the same as continue/stop testing button provided by the dialog panel in Batch.seq.

Hope this provides some things to think about.

Regards

Ray Farmer

[GeekGrok]

Hi Ray,

    Thank you for your response! I do have a follow up question to your response regarding the need for the stop testing buttons.

     I think you might be referring to the Test/Stop/Abort/Terminate buttons on the modelsupport2.dll panel, that occurs when using the Parallel model. I probably did not specify in my initial posting that I am using a Batch model. Using batch mode, I believe all of the UUTs start and end testing at the same time, thus I thought I could get away with a simple continue or stop testing dialog at the end of the batch test. 

      Is my assumption correct, or am I still missing something here?

THanks again,

Jim

[RayFarmer]

Hi,

You will need to simulate the STOP button on the Enter UUT's Dialog so that when you get to the Step in the Process model - "Tell Test Sockets to stop"  Your process actually stops.

You will probably have to change the batch process model  so that instead of checking for Locals.ModelData.ContinueTesting you use maybe a StationGlobal that you can set / reset via the Operator Interface.

Regards

Ray Farmer