TSCOE4 Operator Interface

The TSCOE4 Operator Interface provides a graphical user interface for the operator or the implementer in a production environment. It permits selecting the test sequence and supports parametrization of the test. During the test sequence, the current measurement values are displayed in relation to the relevant limits and the pass/fail evaluations for each individual test. After completion of the test sequence, the global test result is visualized.

In addition, there are online statistics available to the user, which show the measurement value distribution within the current batch.

The editor which is supplied with the product makes it possible to adapt the user interface language to any new deployment location. Several languages – German, English and Chinese – have already been implemented and are available out of the box.

TSCOE4 Test Execution Functions

TSCOE4 comprises a graphical user interface, but the implementation also provides powerful interfaces for connecting automation and labelling systems. TSCOE4 is modularly structured; all modules, whether related to the graphical user interface or the automation technology, are available as source code, thereby allowing customers or LXinstruments to adapt them to changing requirements. Such changes do not require a new compilation of the core modules. TSCOE4 is a .net application and has been developed in C#.

Example: Rotary Indexing Table with TSCOE4

The following automation functions have been implemented within the scope of customer projects in the past:

  • Retrieval of the product variant to be tested from line control computers
  • Interface to rotary indexing tables, allowing verification of assembly steps, laser labelling of the DUTs and automated handling of bad parts
  • Integration with drawer adapters
  • Reliable connection to bad parts boxes, including verification of bad parts throw-out
  • Connections to laser labelling systems manufactured by Trumpf
  • Barcode readers for identifying the DUT, including automatic loading of the relevant test plan for the product
  • Readout of DUT serial numbers via the DUT firmware during test execution
  • Storage of test results in ASCII files for export to customers databases