12 format of traffic generation files – Teledyne LeCroy USB Protocol Suite User Manual (Voyager_Advisor T3_Mercury) User Manual
Page 330

Teledyne LeCroy Corporation
Format of Traffic Generation Files
330
USB Protocol Suite User Manual
11.12 Format of Traffic Generation Files
Whether you create a traffic generation from scratch or use the Export command, there
are a few rules about the format of the generation file that you should review. These are
presented in this section.
Traffic is generated from a text file named *.utg. Within the text file:
The data format for data fields such as Pids and Raw bits is hex.
Each packet definition consists of this set of assignments: key=value.
White space is permitted around the equal sign.
There are no restrictions on dividing packet definition to lines nor is it necessary
to define each packet in a separate line, although it is recommended.
The maximum number of characters in a line is 250.
The characters # and; indicate end‐of‐line comments (i.e. the rest of the line is
ignored)
Comments are not allowed within brackets ( ).
No keys or values are case‐sensitive.
Each packet definition starts with one of these assignments:
pid=N (where N is a string representing a valid packet identifier or an eight bit
value)
OR
frame=N (where N is an eleven bit value of the frame number or the strings auto
and keep_alive).
A bus condition definition starts with one of these assignments:
reset=N (where N is a positive integer or string)
suspend=N (where N is a positive integer)
resume=N (where N is a positive integer)
chirp=here
Subsequent assignments after a packet’s starting assignment define the values of
particular fields within the packet. If a field is not defined, it is assumed to be 0. Values
are assumed to be decimal unless they are prefixed with 0x and then are interpreted as
hexadecimal. Values within a data block assignment are always assumed to be
hexadecimal and should not be prefixed by 0x.