Chapter 7: traffic generation, 1 traffic generation keys, 7 traffic generation – Teledyne LeCroy FireInspector - Users Manual User Manual
Page 101: Traffic generation keys, Hapter, Raffic, Eneration

91
CATC F
IRE
I
NSPECTOR
2.01
C
HAPTER
7
User’s ManualTraffic Generation
C
HAPTER
7: T
RAFFIC
G
ENERATION
FireInspector uses traffic generation (.txg) files to generate traffic on the 1394 bus. Traffic
generation files are text files that can be created by hand using traffic generation keys to
define packet fields, or by exporting a traffic recording (.fdb) file to generator text (.txg) file
format. Additionally, you can access several convenient editing utilities via the Trace file
pop-up menus.
Several sample traffic generation files are included with the FireInspector software
installation.
7.1 Traffic Generation Keys
Traffic generation keys are used to define packets in a traffic generation (.txg) text file.
Each packet definition consists of a set of assignments like this:
key = value
White space is permitted around the equal sign.
It is not necessary to define each packet on a separate line; however, it is not recommended
to have the end of one packet and the beginning of another both on the same line, as the
editing of the packets will not work properly in this case.
The hash mark (#) and semicolon (;) characters indicate end-of-line comments, and
anything to the right of these characters is ignored.
All keys and values are case insensitive.
Each packet definition starts with one of the following assignments:
•
tcode=N
(where N is a valid tcode value as defined by the 1394 standard)
•
phy_packet=N
(where N is a quadlet written in hexadecimal, e.g., 0x12345678)
•
control=N
(where N is a control packet type)
Subsequent assignments define the values of particular fields within the packet. If a field is
not defined, it is assumed to have a value of zero. If a field is not valid for a packet, the error
is displayed and file loading is aborted.
Values are assumed to be in decimal unless they are prefixed by '0x', in which case they are
interpreted as hexadecimal. Values within a data block assignment are always assumed to
be hexadecimal and should not be prefixed by '0x'.
Each packet can have a marker key with a text string value. For example:
marker=This packet starts movie transfer over the bus.
Packets containing this key are marked in the Trace file by a red bar on the left edge of the
packet number field. When the mouse pointer is positioned over the bar, the marker text is
shown as a tool tip.