Status and Events
/* Wait until th
e acquis ition is complete */
*OPC?
/* 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
Messages
The information contained in the tables below 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 t he main message by a semicolon.
Each mess age is the result of an event. Each type of event s ets a specifi c bit in the
SESR and is controlled by the equivalent bit in the DESER. Thus, each m essage
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
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.
Table 3-4: Command Error Messages (CME Bit 5)
Code Message
100
Command error
101 Invalid character
102
Syntax error
103 Invalid separator
104 Data type error
105
GET not allowed
3-12 MSO2000B, DPO2000B, MSO2000 and DPO2000 Series Oscilloscopes Programmer Manual
To Next Page
Loading...
Need help?
General
