Unigraf UCD-240, Руководство пользователя, Страница: 57 / 78

UCD Console for UCD-340 User Manual | Unigraf Oy
57.
Extended scripting engine
The Extended TSI Scripting Engine is an executable scripting language program, tsi.exe,
built on top of the Extended TSI API.
The program can be run from the Windows command line or from scripting languages such
as python.
All input characters from the command line and files need to be ASCII characters.
The "#" is used for comments. All input on a line after a "#" will be ignored. This means you
must not try to print this symbol. One should also not use the ";" withing text to be printed as
it is used as a delimiter for expressions.
Getting started
To run TSI.exe , two (text format) files are generally used: init.tsi (required) and macros.tsi
(optional). These need to be in the same directory (the working directory) from which TSI.exe
is run.
You need to be aware that changing the state of a device via Configuration Items, CI’s, can
take time and scripting commands calls are asynchronous: So make ample use of the
-waiton
command (see 1.2.4 Running TSI.EXE).
Defining test equipment devices
init.tsi contains the device names (or aliases) and are of the form:
DeviceName = 1813C261 source_sink dp;
Here DeviceName is the name you use when opening it, 1813C261 is the device serial
number, source_sink specifies the sink and source capability and dp states that the device
uses display port technology (see section 1.2.7 Devices).
inti.tsi may be created from the command line as follows:
tsi.exe -l > init.tsi
init.tsi will contain device definitions of the form (one definition per line):
Dev0 = 1823c395 sink usbc;
Dev1 = 1823c395 source usbc;
The names can be edited for convenience:
MyUDC340sink = 1823c395 sink usbc;
MyUDC340source = 1823c395 source usbc;
Commands
Commands are of the form KVE (KeyValueExpression):
Key = Value.Expression;