Teledyne LeCroy IBTracer 4X - IBTracer Verification Script Engine Users Manual - Manual (Page 14)

Computer Access Technology Corporation IBTracer Verification Script Engine Manual, version 1.0
Page 14 of 35
in.LinkStateCurr
- current link state(Opcode)
6. Verification Script Engine Output Context members
All verification scripts have output contexts –special structures whose members are set by the
script and can be used inside of the application ( For more details about output contexts – please refer
to the CATC Script Language(CSL) Manual ). The verification script output contexts have only one
member:
out.Result
- the result of the whole verification program defined in the verification script.
This member is supposed to have 3 values:
_VERIFICATION_PROGRESS,( is set by default when script starts running )
_VERIFICATION_PASSED,
_VERIFICATION_FAILED
The last two values should be set if you decide that recorded trace does ( or not ) satisfy the
imposed verification conditions. In both cases the verification script will stop running.
If you don't specify any of those values - the result of script execution will be set as
VERIFICATION_FAILED at exit.
7. Verification Script Engine events
VSE defines a large group of trace “events” – packets or special notifications – that can be
passed to a verification script for evaluation or retrieving and displaying some contained information.
The information about the type of event can be seen in in.TraceEvent. Please refer to the topic
“Sending functions” in this manual for details about how to send events to scripts.
7.1
Packet events.
The table below shows current list of packet events and value of in.TraceEvent:
Packet
in.TraceEvent
TS1 _PKT_TS1
TS2 _PKT_TS2
Link Packet _PKT_LINK
MAD packets _PKT_MAD
Reliable Connection packets _PKT_RC
Reliable Datagram packets _PKT_RD
Unreliable Connection packets _PKT_UC
Unreliable Datagram packets _PKT_UD