WATS allow you to plug into NI TestStand with a seamless integration. By default, the WATS Client support from version 3.1 and greater running on Win XP, Win 7, Win 8/8.1 or Win 10/11.
Given that you use TestStand "out of the box"*, do the following:
- Download and install the WATS client (Not a WATS user? sign up for a free trial at www.wats.com)
- Install the WATS TestStand add-on from the WATS Client Configuration panel (ref. Installation Guide)
- Launch TestStand
- Open your client sequence file and click "Test UUTs". The UUT report should now log to the WATS server.
- Read the pdf documentation installed with the client.
* "Out of the box" meaning running default/built in process models, step types and data collection. WATS should automatically identify custom step types if they are based on the NI templates.
WATS utilize the plug-in structure introduces in TestStand version 2012 and running this version or higher will not require using the WATS Process Models.
If you are running custom models prior to TestStand 2012 they can be modified to log to WATS. See Add WATS logging to your custom process model
Example below. The client will list the TestStand versions installed.
Adding additional data to WATS
It is recommended to add additional properties like Unit Part Number, Revision and Process type (Test Operation Type) to the WATS report.
After installing the add-on, the UUT container is altered with additional properties. The most important is highlighted below.
Add Unit information to the properties highlighted above. (NI introduced "PartNumber" property in TS 2012. It is optional whether to use the default "PartNumber" or the "UUTPartNumber" (legazy support) property).
UUTOperationType is by default 10 (SW Debug), but can be updated with a proper process type (like Functional Test, ICT, etc.) either by updating the number code or by using the "Set Operation Type" step.
The process list can be edited at the server side: Edit Processes (Test/Repair Operation)
Using NI TestStand
Add miscellaneous data to the UUT header
Tracking sub units in WATS
Hello! I am working on a test sequence that will support different types of UUTs. By using precondidtions, some tests are skipped for some UUTs and I dont want these in the report. Is there a way to manage this in TS?
One way is to delete the step result entry in the result list (Locals.ResultList). You would have to do this in a separate step or as a engine callback.
You might want to consider using if/else or a Case for this instead (Flow control steps). Uncheck the Run Options>Record Result on the flow steps to skip reporting. this way you will only log result from the executed test steps.
Thank you, Tom!
I have some warnings in my WATS report (e.g "VISA Read in SimplePsuMon.vi->SimplePsuMon.vi.ProxyCaller"), that I would like filtered out. Is there a setting for this?
I think this has to be filtered in the VI before returning the Warning (error number) to TestStand. You can try to post the question at the NI TestStand forum: http://forums.ni.com/t5/NI-TestStand/bd-p/330
Hi, I'm currently working on to resolve issue about pending UUT reports. It is previously working good but encountered the issues after migrating to .224 from .226 server. The reports are not transferred to WATS right now, all are pending. Can you suggest some action. Thanks a lot.
Christiene, check you time settings at the client: https://virinco.zendesk.com/entries/22933457-Time-Synchronization
If this doesn't help, please email the client log file https://virinco.zendesk.com/entries/28627176-Where-to-find-the-wats-log-file-at-the-Client to firstname.lastname@example.org
Thank you so much Tom, so, that's need to be synchronized. But, the thing is I've tried to re-installed the client, and receive new pre UUT check failures. I'll get back to you, once figure it out. thanks
So All WATS folder was deleted on the NI user folder.. Get back to you on the UUT report. Thanks
Why when installing TS add-on the default NI models are removed? This should not be done this way.
@Marek. The default NI models are not removed but the installation change the default station model to "WATS_SequentialModel.seq". Depending on the TestStand (TS) version you are running, this is to support "ready-to-run" integration.
If you use TS 2012 or greater you can change the station model back and still log to WATS. The "WATS_SequentialModel.seq" has to run once in TS to add the WATS report plug-in option.
I hope this was clarifying.
Thank you. I was looking for this.
Please sign in to leave a comment.