WATS Converter - Keysight Medalist i3070 (Log Record Format, extended)

GitHub Repository

Overview

Converts Keysight Medalist i3070 test result files in the i3070 Log Record Format to WATS UUT reports. Extended variant with full test type coverage.

and any integration-specific context not covered by the README. -->

Integration Details

File Format Assumptions and Requirements

Examples: encoding (UTF-8/ASCII), line endings, required vs optional fields, field order constraints, supported file version(s) -->

• Input encoding: UTF-8

Hardcoded Values and Defaults

• Status "0" or "00" maps to Passed; any other value maps to Failed
• Block designator prefix matching ^\d+% is parsed as socket index (multi-board fixture support)
• Report text fields are truncated at 5000 characters

Converter Parameters

These parameters are configured in the WATS Client Configurator converter arguments.

Input Record Types and Regex Patterns

The converter uses TextConverterBase.SearchFields to match lines. Each entry below is one regex field registration with the associated capture groups.

Header field: UUTField.UseSubFields (parsed in InHeader state)

Format: |operator id (string)|controller (string)|testplan id (string)|testplan rev (string)|parent panel type (string)|parent panel type rev (string)}

^\{@BATCH\|([^|]*)\|([^|]*)\|([^|]*)\|([^|]*)\|([^|]*)\|([^|]*)\|([^|]*)\|([^|]*)\|(?<Station>([^|]*))\|([^|]*)\|(?<Revision>([^|]*))\|([^|]*)\|([^|]*)\|(?<PartNumber>([^|]*))$

Record: BTEST (parsed in InHeader state)

Format: |learning (bool)|known good (bool)|end datetime (int)|status qualifier (string)|board number (int)|parent panel id (string)}

^\{@BTEST\|((?<SerialNumber>[^|]*))\|(?<Status>([^|]*))\|(((?<StartDate>[^|]*)))\|((\b0*(?<ExecutionTime>[1-9][0-9]*|0)\b))\|(([^|]*))\|(([^|]*))\|(([^|]*))\|(([^|]*))\|(([^|]*))\|(([^|]*))\|(([^|]*))\|(([^|]*))$

Record: BTEST (parsed in InHeader state)

Format: For some reason some reports have 12 separators (|) and another reports har 13 separators. This may be because a the field 'parent panel type rev' is a field newly added to the format. Anyways we check for both.

^\{@BTEST\|((?<SerialNumber>[^|]*))\|(?<Status>([^|]*))\|(((?<StartDate>[^|]*)))\|((\b0*(?<ExecutionTime>[1-9][0-9]*|0)\b))\|(([^|]*))\|(([^|]*))\|(([^|]*))\|(([^|]*))\|(([^|]*))\|(([^|]*))\|(([^|]*))\|(([^|]*))\|(([^|]*))$

Record: BLOCK (parsed in InTest state)

Format: Format: {@BLOCK|block designator (string)|block status (int)}

^{@BLOCK[|](?<BlockDesignator>[^|]*)[|][^|]*$

Record: TestLIM2 (parsed in InTest state)

Format: Matches these group names: @A-RES, @A-MEA, @A-NFE, @A-NPN, @A-PFE, @A-PNP, @A-SWI, @A-DIO, @A-JUM

{@(?<Group>[^|]+)[|](?<Status>[^|]*)[|]\s*(?<Meas>[0-9+-E.]+)[|]*{@LIM2[|]\s*(?<HighLim>[0-9+-E.]+)[|]\s*(?<LowLim>[0-9+-E.]+)}

Record: TestLIM2Multi (parsed in InTest state)

Format: Matches these group names: @A-RES, @A-MEA, @A-NFE, @A-NPN, @A-PFE, @A-PNP, @A-SWI, @A-DIO, @A-JUM

{@(?<Group>[^|]+)[|](?<Status>[^|]*)[|]\s*(?<Meas>[0-9+-E.]+)[|](?<MeasName>[^}]+)[|]*{@LIM2[|]\s*(?<HighLim>[0-9+-E.]+)[|]\s*(?<LowLim>[0-9+-E.]+)}}

Record: TestLIM3 (parsed in InTest state)

Format: Matches these group names: @A-RES, @A-ZEN, @A-CAP, @A-FUS, @A-IND, @A-POT

{@(?<Group>[^|]+)[^|]*[|](?<Status>[^|]*)[|](?<Meas>[0-9+-E.]+)[|]*{@LIM3[|](?<Nominal>[0-9+-E.]+)[|](?<HighLim>[0-9+-E.]+)[|](?<LowLim>[0-9+-E.]+)}}

Record: BS-CON (parsed in InTest state)

Format: Format: {@BS-CON|test designator (string)|status (int)|shorts count (int)|opens count (int)}

{@(?<Group>BS-CON)[|](?<testName>.*)[|](?<status>[^|]*)[|](?<shortCount>\d+)[|](?<opensCount>\d+)

Record: Report (parsed in InTest state)

Format: Format: {@RPT|message (string)}

{@RPT[|](?<RepTxt>.*)}

Record: D-T (parsed in InTest state)

Format: Format: {@D-T|test status (int)|test substatus (int)|failing vector number (int)|pin count (int)|test designator (string)}

\{@(?<Group>D-T)\|(?<TestStatus>(0|1|5|7|8))*\|(?<TestSubstatus>([0-9]*))\|(?<FailingVectorNumber>([0-9]*))\|(?<PinCount>([0-9]*))\|(?<TestName>(.*))

Record: TJET (parsed in InTest state)

Format: Format: {@TJET|test status (int)|pin count (int)|test designator (string)}

\{@(?<Group>TJET)\|(?<TestStatus>(00|01|07))*\|(?<PinCount>([0-9]*))\|(?<TestName>(.*))

Record: PF (parsed in InTest state)

Format: Format: {@PF|designator (string)|test status (int)|total pins (int)}

\{@(?<Group>PF)\|(?<TestName>(.*))\|(?<TestStatus>(0|1))\|((?<totalPins>([0-9]*)))

Record: TS (parsed in InTest state)

Format: Format: {@TS|test status (int)|shorts count (int)|opens count (int)|phantoms count (int)|designator (string)}

\{@(?<Group>TS)\|(?<TestStatus>(0|1|20))*\|(?<ShortsCount>([0-9]*))\|((?<OpensCount>([0-9]*)))\|((?<PhantomsCount>([0-9]*)))\|(?<TestName>(.*))

WATS Step Type Mapping

For each matched record, ProcessMatchedLine creates the following WATS objects:

Unit Mapping (UnitMapper)

When numberFormatMode = prefix, SI prefixes are chosen dynamically based on value magnitude. The following table shows every recognized record-type prefix and its associated unit:

Known Limitations and Edge Cases

that operators should be aware of -->

Configuration Guidance

Parameters are configured in the WATS Client Configurator under the converter's Arguments XML. Example:

<Arguments>
  <!-- TODO: paste a real example Arguments XML block here -->
</Arguments>

Getting Started

• What is WATS?
• WATS Client download
• Setting up a custom converter

Download

The recommended installation method is via the MSI installer. Download the latest release from the Releases page.

Installation

Using the MSI Installer (Recommended)

1. Download the .msi file from the Releases page.
2. Run the installer - it will automatically place the converter in the correct WATS Client folder.
3. Restart the WATS Client Service.