Teledyne LeCroy UWBTracer Verification Script Engine Manual - Manual (Page 17)

LeCroy Corporation Verification Script Engine Manual, version 2.2
5 Verification Script Engine Input Context Members
All verification scripts have input contexts, special structures that can be used inside of the scripts. The
application fills their members. (For more information about input contexts, please refer to the LeCroy Protocol
Analyzers File-Based Decoding User Manual, which is the LeCroyAnalyzersFileBasedDecodingManual.pdf file in
the Docs subfolder). The verification script input contexts have two sets of members:
• Trace event-independent set of members
• Trace event-dependent set of members
Note: All input context members have integer type values unless their types are explicitly specified.
If possible values for input context members are not explicitly specified, they should comply with the current
WiMedia PHY-MAC specifications.
5.1 Trace Event-independent Set of Members
This set of members is defined and can be used for any event passed to a script:
in.Level : Transaction level of the trace event (0 is frames, no other levels are currently supported).
in.Index : Index of the event in the trace file (frame number for frames, sequence number for sequences).
in.Time : Time of the event (type = list, having format = 2 sec 125 ns -> [2 , 125]. For more information, see
section 10.1 VSE Time Object.
in.Channel : Indicates on which channel the event occured. It can be one of the following constants:
_MPI: MPI channel, not decripted traffic (value = 1)
_RF: RF channel, not decrypted traffic (value = 2)
_MPI_DEC: MPI channel, decrypted traffic (value =: 3)
_RF_DEC: RF channel, decrypted traffic (value = 4) from _CHANNEL_1 (= 1) to _CHANNEL_4 (= 4)
in.WirelessChannel : Indicates wireless channel (valid only for RF channels) where the event occured.
in.Receive : Indicates PHY direction (0 = TX, 1 = RX).
in.TraceEvent : Type of trace events. (Application predefined constants are used. See list of possible events
below.)
in.Notification : Type of notifications. (Application predefined constants are used. Currently no notifications
are defined.)
in.RawFrame : Bit source of the whole frame: header + payload. (You can extract any necessary information
using the GetNBits(), NextNBits(), or PeekNBits() functions. Refer to the LeCroy Protocol Analyzers File-Based
Decoding User Manual for details about these functions.)
in.RawFrameLength : Length of the frame(in bytes of the retrieved frame: header + payload)
Page 17 of 95