94
Chapter 3
Measurement Synchronization with LXI-B
Using the LXI Event Log
the procedure in
“Configuring an LXI State Trigger” on page 93
has
been completed, receiving a “LAN0” event will cause myState.state to
be recalled. Then, receiving a “LAN1” event will cause
anotherState.state to be recalled. Stringing state files in this manner
allows the instrument to step through a number of states in response to
peer to peer messages.
To verify that an LXI State Trigger has been configured correctly, follow
the procedure in
“Verifying an LXI Trigger using LXI Interactive”
. To
monitor the instrument’s response, however, the expected parameter
changes must either be observed from the front panel or queried via
SCPI.
Using the LXI Event Log
The final piece to the LXI puzzle is the LXI Event Log. The event log
records all of the enabled LXI Event and Instrument Event activity and
associates each action with an IEEE 1588 timestamp. Instrument
Events are enabled by default, and will therefore appear in the log.
Since many instrument events occur during every sweep, logging all of
them may flood the event log. They may be disabled by sending the
SCPI command
:LXI:EVENt:STATus:ENABled “instrumentEvent”,0
where the parameter “instrumentEvent” may be any event listed in
Table 1. Note that the event must be re-enabled before being used as
the source of an LXI Output LAN Event.
To view the LXI Event Log from the front panel, press the hard key
System and then the softkeys Show, LXI, LXI Event Log. Once the
Event Log is displayed, the arrow keys may be used to scroll through
the list. The Event Log may also be queried via SCPI.
