When implementing WATS into your test equipment and manufacturing processes through the use of UUT and UUR reports, WATS offers a great tool for traceability. Since data can be logged from any geographical location and from any source, you can trace every unit throughout the manufacturing.
Replace Units during repair
WATS also supports “box build” or “consist of” information meaning that when you test e.g. a module containing one or multiple sub units (boards), you can enter their inventory information (Serial Number, Part Number, Revision) as part of the report.
A unit tested in WATS and later installed in a module, will be marked as a sub unit. This also applies when performing repair or rework operations.
Example above shows a unit failing and being reworked as a Unit. When added to a parent, it becomes a sub unit (level highlighted in yellow above).
Example above shows a unit (highlighted in blue above) that passes all tests as a unit, but later the parent fails the Functional Test. The Unit is then repaired as a Subunit (highlighted in red above), then tested again as Unit. When Passed, it is assembled with a different parent (SN starting with 14337...).
Example 4 illustrates how to drill down from top level units to the "lowest" linked unit in the hierarchy.
If a module containing sub unit(s) fails in a test, the sub unit(s) will be listed in the web based reporting tool and allow the operator to tag a repair to both the unit (parent) and the sub unit. This information can then later be analysed in the reporting tool as shown below.
Example below illustrate units that are repaired as sub units. By increasing test-ability at the unit level, these error may be found earlier in the process.
When using TestStand, use the "MiscUUTResult>UUT_Part_Info" container and add one or several sub parts (Type/description, Part Number, Serial Number, Revision). The "IdentifyUUT.vi" has predefined Indicators that match the UUT Container datatype. Open the "IdentifyUUT.vi" from the processmodel, open the diagram and copy/reuse the indicators collected in the "MISC UUT RESULT" frame.
See also <TestStand Examples>\WATS\Log misc UUT info
When using LabVIEW (stand alone), use the "WATS_TDM_UUTPartInfo.vi" fuction. and similar properties on the UUT Header in the API.
When running the Repair GUI in WATS Operator Interface, linking a UUR to a UUT that contains sub units will automatically list the sub units.
is there any way of storing more data inside MiscUUTResult.UUT_Part_Info than only part type, number, serial number and revision number?
@Piotr What kind of data? You can also use https://virinco.zendesk.com/hc/en-us/articles/207933206-Add-miscellaneous-data-to-the-UUT-header to store data like firmware versions atc.
I thought about dates stored as a string and additional numeric info. Storing it inside miscellaneous data seems like a good idea, thanks!
Can the sub board info be stored after the IdentifyUUT.vi has run?
In my case, I have to start the box build module test, and read the sub-board info to populate to the report header.
Can I added in PostUUT?
Please sign in to leave a comment.