User Manual

29
CATC SCRIPTING LANGUAGE 1.0 CHAPTER 10
Reference Manual Transaction and Packet Context Fields
CHAPTER 10: TRANSACTION AND
P
ACKET CONTEXT FIELDS
This chapter describes the transaction and packet context fields (symbols) that are
defined in FireInspector. These fields define the output context for each built-in
transaction or packet type. These output contexts are then used as input to script
decoders. A script decoder declares the transaction types that it wishes to examine
by using the InputType module variable (for more information, see
“InputType” on page 66).
Transaction Context Fields
The transaction context fields are listed by type of transaction.
1394 Transactions
These transactions require the module data
InputType = "1394 Transaction".
data_len: Integer. Length of data payload in bytes. Taken from the packet
header.
Tcode: Integer. Tcode value of the transaction’s request packet.
Requester: Integer. Node ID of the transaction initiator.
Responder: Integer. Node ID of the transaction target.
Rcode: Integer. The result of the transaction. This could be the rcode field from
a response packet or from the ack value of the request packet. The meaning of the
values are the same as for a packet rcode.
Payload: Raw bytes. The data payload.
address: Raw bytes. The 48-bit address.
BusResetOccurred: Integer. A non-zero value means that a 1394 bus reset
occurred since the last 1394 transaction; otherwise, the value is zero.
IPv4 over 1394 Transactions
These transactions require the module data InputType = "IPv4 / 1394".
Data: Raw bytes. The data payload of the transaction.
DataLength: Integer. The length of the payload in bytes.
Source_Node: Integer. The 1394 node ID of the source node.