No test report using Test UUTs with Operator Interface

[BillHH]

Using TestStand 2.0 and running a test sequence with the provided CVI Operator Interface, an on-screen test report is not genertated after the test is completed when the test is started by clicking on 'Test UUTs'.  After the test result (PASS/FAIL) dialog box is shown, the report box section of the GUI is empty.  Clicking 'Ok' on the test result box prompts for the next UUT serial number and there is no report shown still.  A report is generated to the specified location ok, but the test operator does not know what would have failed in a test.

[RayFarmer]

Hi,

I dont think it produces a report in the report window until you have finished testing all UUTs. Then it will display the last one.

I think the step that writes it to the window is after the PostUUTLoop step. If this is correct, then you would have to modify the Process Model.

Regards

Ray Farmer

[S.Can]

Hi BillHH,

Did you fixed your problem?

Can you show your product, so i can used it as a example. Because i make approximately the same thing.

[BillHH]

Sean,

This is how the Process Model works unless you modify it.  For the time being if there is a UUT failure, we are having the operator click 'Stop' on the test result dialog box to get the test report printout on screen.  Then the operator needs to click retest.  It is a matter of operator training for the time being.  In future implemenataions I will look at editing the Process Model.

[RayFarmer]

Hi,

In the Process Model sequence file under Test UUTs is a step which is performed outside the UUTLoop called 'Read Entire Report', its this step that write the report to the Report window.

You would have to do this step after the Write UUT Report step which is inside the UUT Loop.

Hope this helps

Ray Farmer