Unigraf UCD-240, Руководство пользователя

Страница: 46 / 78

UCD Console for UCD-340 User Manual | Unigraf Oy
46.
TSI PROGRAMMING
This section defines mechanisms used in TSI that might not be otherwise clear from the
otherparts of the reference manual. The intent is to clarify the operation of the more complex
partsby providing additional descriptions and details on intended uses. For full details of the
TSI, please refer to the TSI Manual which can be found from the USB Flash Drive delivered
with the device.
Operator feedback during test execution
Some of the new TSI tests may require operator feedback and/or operator actions during test
execution. This section describes the implementation details in TSI that are used to carry out
the operator communications. The provided solution only prompts operator to carry out
operations on the DUT side, but the intention of this mechanism is to enable test system
manufacturers to fully automate test execution even when the test requires an operation to be
performed on the DUT side.
Operator feedback implementation in TSI
TSI is planned to support more than one way of operator intervention / feedback mechanisms.
The CI named TSI_TS_OFMODE is reserved to select which method is used. Currently, the
only method supported is TSI_OFMODE_RUN_EXTERNAL. In this mode, TSI will run an
external application. A default command line application is distributed with TSI, along with
its source code. TSI itself can be the external application (see Error: Reference source not
found Running Tests).
Selecting which application TSI will run
By default, TSI will use its own operator feedback application for all operator feedback
requests. However, it is possible to define separate applications for each operator feedback
request type. The definition is controlled by two separate CI’s. The first of these is
“TSI_TS_OF_REQ_ID”, which defines the request ID related to the application setting. The
default setting is -1, which means that the application setting applies to all request ID’s. The
second CI is “TSI_TS_OF_EXT_APP”, which contains the path and name of the executable
file to be started as a NULL terminated string. These definitions are in the device scope, so
each test device will have its own set of application definitions.
In short, to use a single application for all operator feedback requests:
1. Write -1 to “TSI_TS_OF_REQ_ID” CI.
2. Write a null terminated string containing full path and name of your application to
“TSI_TS_OF_EXT_APP” CI.
To configure an application for any operator feedback request (this step can be repeated to
create multiple settings) :
1. Write the request ID to “TSI_TS_OF_REQ_ID”.
2. Write a null terminated string containing full path and name of your application to
“TSI_TS_OF_EXT_APP” CI.