Tektronix MSO54, Programmer'S Manual

Page: 929 / 1026

Status and Events
/* Acquire waveform data */
ACQUIRE:STATE ON
/* Set up the measurement parameters */
MEASUREMENT:IMMED:TYPE AMPLITUDE
MEASUREMENT:IMMED:SOURCE CH1
/* Wait until the acquisition is complete before taking
the measurement */
While BUSY? keep looping
/* Take amplitude measurement */
MEASUREMENT:IMMED:VALUE?
This sequence lets you create your own wait loop rather than using the *WAI
command. The BUSY? query helps you avoid time-outs caused by writing too
many commands to the input buffer. The controller is still tied up though, and
the repeated BUSY? query will result in bus traf
fi c.
Reference waveforms Measurements on references also support OPC when used in conjunction with a
:RECALL:WAVEFORM command.
/* Add a reference slot on which to measure */
:REF:ADDNEW "REF1"
/* Set up the measurement parameters on the reference */
:MEASUrement:MEAS1:TYPE AMPLITUDE
:MEASUrement:MEAS1:SOURCE REF1
/* Load the new waveform file */
:RECALL:WAVEFORM "E:\waveform.wfm”,REF1
*OPC?
/* Wait for read from Output Queue. */
/* Take amplitude measurement */
:MEASUrement:MEAS1:RESUlts:CURRentacq:MEAN?
Messages
The information contained in the topics above covers all the programming
interface messages the oscilloscope generates in response to commands and
queries.
For most messages, a secondary message from the oscilloscope gives detail about
the cause of the error or the meaning of the message. This message is part of the
message string and is separated from the main message by a semicolon.
Each message is the result of an event. Each type of event sets a speci fi c bit in the
SESR and is controlled by the equivalent bit in the DESER. Thus, each message
MSO54, MSO56, MSO58, MSO58LP Programmer 3-13