Rigol DSA1030, User Manual

Page: 225 / 287

Troubleshooting RIGOL
User’s Guide for DSA1000 Series 5-3
5.2 Messages
Messages fall into three types on the basis of the tips purpose: Information Message,
Error Message, and Status Message. To get accurate measurements and specific
working status of the analyzer, you should be familiar with these messages.
1.
Information Message: to give a clue that the current task has finished or the
analyzer has entered a specified state. The messages are always marked with an
icon and displayed on the screen for several seconds and then hidden
automatically, or you can press any key to clear the display of this massage.
Message number: 1 - 199.
2. Error Message: to warn you that the current operation cannot be executed and
has been ignored or paused for some reason. These messages are always marked
with an icon and displayed on the screen for several seconds and then hidden
automatically, or you can press any key to clear the display of this error massage.
Error Messages based on the cause of the error are divided into Command Error,
Execution Error, Device Specific Error, or Query Error. Each of the errors
corresponds to a specific bit pattern in the Standard Event Status Register (see
IEEE 488.2,11.5.1). When you find there is an error generated in the Standard
Event Status Register, send command :SYSTem:ERRor? in Remote Mode to get
the information on this error and find the cause of it.
(1)
Command Error: indicates a command error is detected by the Parser while
in Remote control (see IEEE488.2,6.1.6), possible reasons are:

The Parser detects a syntax error; (see IEEE488.2,7.1.2.2)

An unrecognized header or a parameter that is of the wrong type for its
associated header is received. (see IEEE488.2,10)
Message number: -199 to -100.
(2) Execution Error: indicates an execution error is detected by the Execution
Control Block, possible reasons are:

A parameter following a header was evaluated by the device as outside
of its legal input range or is otherwise inconsistent with the device’s
capabilities.

A valid program message could not be properly executed due to some