Unigraf UCD-240, User Manual

Page: 74 / 78

UCD Console for UCD-340 User Manual | Unigraf Oy
74.
• A statement consists of a key and an associated value.
• The key and value must be on the same line of text.
•
There must be an equal sign (‘=’) between key and value.
•
There must be a semi-colon character (‘;’) after the value.
• If either key or value contain spaces, it must be enclosed with single-quote marks
(‘).
•
White-space characters that are not part of key nor value are ignored, and therefore
can be used to format the script to be more readable.
Below are some examples of valid script lines. The first line assigns a filename into a
configuration item, and the second one assigns a numeric value. You can find the used
configuration item definitions elsewhere in this document.
·····TSI_LOG_FILE·=·’C:\My·TSI·Logs\Log.txt’;···
·····TSI_W_SCRI_DELAY·=·1000;
Important: The (‘·’) characters are white-space characters, such as spaces or tabs.
Writing a script for TSI_TST_Init
The intention of an initialization script is to create a known environment for the rest of the
test sequence and make test station configuration easier. If there is a need to distribute a
TestStand test sequence to multiple stations, it can be very useful to put the initialization
script into a file, and refer to that file from the TestStand test sequence. This way, each test
station can be configured to use the appropriate hardware by modifying the script file with
notepad, or some other simple text editor utility, while the TestStand test sequence itself
remains unchanged.
The script provided for TSI_TST_Init through the iSetupScript pointer is used to define
aliases for the devices used in the test sequence.
MyDevice = ‘UCD-323 [1234C5678]: DisplayPort Reference Source’;
The above script would define an alias “ MyDevice ”. The alias is later used to identify the
device by providing it through the Device string pointer parameters available in the
TSI_TST_RunTest and TSI_TST_RunScript functions. The “ MyDevice ” alias will refer to
the device given in the value field – (In this case a UCD-323 device with S/N 1234C5678
being used as a DisplayPort source). Please notice that defining a device alias will also open
the device. As a result, it is not possible to define multiple aliases that would require use the
same physical hardware.
In addition to selecting a device, it is necessary to also select which interfaces are going to
be used. TSI offers selection of an input, and an output. An input and output can be used
simultaneously, provided this is supported by the hardware. Currently, this is supported by
UCD-400 alone at the moment of writing this document. Below is a script that selects both,
an input and an output:
MyDevice = ‘UCD-400 [1234C5678]: DisplayPort Reference Sink and Source’;
.output=’DP-1’;
.input=’DP-1’;
An output is is selected with a special key “ .output ”, and input is selected with another
special key “ .input ”. The values are expected to contain the name of input or output being
selected for use. The “ .input ” and “ .output ” selectors apply to the previous device alias
definition. Please do remember that available inputs and/or outputs depend on the type of
hardware being used. These special keys (“.output” and “.input”) are available for use in a
script that is provided for TSI_TST_Init, and can’t be used in other scripts.
It is also possible to define multiple device aliases: Consider a case where two UCD-323
devices are being used, for example, to test a repeater device. One of the UCD-323 devices
would be used as a source device, with the other one acting a sink device. A following script
might be used in this case: