Tektronix DPO4000, MSO4000 Messages , No Event , Command Error

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*/
*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 operation.
Messages The information contained in the topic tabs 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 specific 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 message tables, the associated 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 or status
to report. These have no associated SESR bit.
Table 3-3: No Event Messages
Code Message
0 No events to report; queue empty
1No 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.
Table 3-4: Command Error Messages (CME Bit 5)
Code Message
100 Command error
101 Invalid character
3-12 MSO4000 and DPO4000 Series Programmer Manual