Status and Events
/* Acquire wave
form 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
*/
*OPC?
Wait for read from Output Queue.
/* Take amplitude measurement * /
MEASUREMENT:IMMED:VALUE
This is the simplest approach. It requires no status handling or loops. However,
you must set the controller time-out for longer than the acquisition o peration.
Messages
Overview. The information contained in the topic tabs above covers all the
programming interface messages the instrument generates in response to
comm
ands and queries.
For m ost messages, a secondary message from the instrument gives more detail
abou
t 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.
Eac
h message is the result of an event. Each type of event sets a specifi c bit in the
SESR and is controlled by the equivalent bit in the DESER. Thus, each message
is associated with a specific SESR bit. In the m essage tables, the a ssociated SESR
bit is specified in the table title, with exceptions noted with the error message text.
No Event. The following table shows the messages when the system has no events
o
r status to report. These have no associated SESR bit.
Ta ble 3-3: No Event Messages
Code Message
0 No events to report; queue empty
1
No events to report; new events pending *ESR?
Command Error. The following table shows the command error messages
generated by improper syntax. Check that the command is properly formed and
that it follows the rules in the section on command Syntax.
DPO7000, DPO70000/B and DSA7000/B Series Programmer Manual 3-11