To simplify integration to other 3rd party test systems, we introduce Wats Standard Text Format.
When you install the WATS Client, a folder named “WatsStandardTextFormat” is created at C:\ProgramData\Virinco\WATS. This is the input folder for the WATS Standard Text Converter built into the WATS Client. If a file with .txt extension that uses the Wats Standard Text Format is saved to the directory, the WATS Client will automatically read and import the file into WATS.
The format of the Wats Standard Text Format is a tab delimited ASCII file (*.txt). Each line in the file represents an entry containing any number of data fields.
The file consists of three main parts; a Header data part, a Step data part and a Footer data part. The Header data part is further split into two sub parts; a list of predefined headers followed by an optional section of miscellaneous UUT data.
The WATS Client can read one UUT report per file or multiple UUT reports in one file. Use the Data Markers to organize the data.
Converter parameters are used as default values for when the file is missing data or for setting options on the converter. This converter supports:
- operationTypeCode: Process code for the test operation. Default 10 (SW Debug).
- testModeType: See Converter Method below. Default Active.
- operator: Name of the operator performing the test. Default sysoper.
- stationName: Name of the station performing the test. Default is name of the PC.
- sequenceName: Name of the sequence on the first step. Default SeqName.
- sequenceVersion: Version number or name of the sequence on the first step. Default 0.0.0.
- cultureCode: How to read numbers and dates. Default en-US.
- fileEncoding: Code page to read the file with. Default 1252 (Windows Western).
- validationMode: When text is too long or contains invalid character, the converter can either throw error (ThrowExceptions) or remove the extra or invalid character (AutoTruncate). Default ThrowExceptions.
The WATS API supports two methods for importing data: Active and Import. When operating in Active mode, the result of a step, sequence and test is set automatically using the measure, compare operator and the limit(s). In Import mode, the status (pass/fail) must be set manually.
When in Active mode, the Wats Standard Text Format converter use a combination of Active and Import: if status is given in the data, it will be used; if not, limits are used.
When in Import mode, status must be set manually.
Inside the InputPath folder two folders are created: Done and Error. When a file with the correct file type (.txt in this case) is added to the InputPath folder, it is picked up by the WATS Standard Text Converter.
- If the PostProcessAction is "Delete" (default):
- After the system has imported the data in the file, it is deleted if the import succeeded, or moved to the Error folder if it did not.
- If the PostProcessAction is "Move":
- After the system has imported the data in the file, it is moved to one of the two folders, Done if the import succeeded, Error if it did not.
- If the PostProcessAction is "Zip":
- After the system has imported the data in the file, it is moved to a zipped folder inside Done if the import succeeded, or moved normally to Error if it did not.
A file called wats.log has data about the files that is picked up by the WATS Client and imported through the converter.
Where to find the wats.log
Description & Example
Please see the attached PDF for detailed description, and TXT file for example.
The NOTE: All columns must be available in the file. The importance (Recommended/ Optional) applies for the data in the column.
I take this to mean pad out for optimal columns with extra TAB ?
NumericLimitTest<TAB>VCC_1V8A<TAB>1.84<TAB>1.75<TAB>1.90<TAB>GTLT<TAB>Volts<TAB>Passed<TAB><TAB><TAB><TAB><TAB><TAB><\n\r> is what is needed ? so always 13 tabs.
If writing a WSTF format file within LabVIEW I assume "\t" format will provide the correct ascii for a TAB ?
The documentation contained an error and is updated.
When adding a sub-unit, the order is Description, Partnumber, Serialnumber and Revision
I am not able to get the test socket index to the "predefined headers"-field in report. It goes to the misc UUT info part of the report. Attached snapshot from the header field.
This was fixed in 220.127.116.11
Please sign in to leave a comment.