Rubidium™ MG362x1A SeriesLow-Noise RF/Microwave SignalGenerators : Error Messages : Device-Specific Errors
 
Device-Specific Errors
An <error code> in the range [–399,–300] or [1, 32767] indicates that the instrument has detected an error which is not a command error, a query error, or an execution error; some device operations did not properly complete, possibly due to an abnormal hardware or firmware condition. These codes are also used for self-test response errors. The occurrence of any error in this class should cause the device-specific error bit (bit 3) in the standard event status register to be set. The meaning of positive error codes is device-dependent and may be enumerated or bit mapped; the <error message> string for positive error codes is not defined by SCPI and available to the device designer. Note that the string is not optional; if the designer does not wish to implement a string for a particular error, the null string should be sent (for example, 42,""). The occurrence of any error in this class should cause the device-specific error bit (bit 3) in the standard event status register to be set. Events that generate device-specific errors shall not generate command errors, execution errors, or query errors; see the other error definitions in this chapter.
Device-Specific Errors
Error Code
Error Description [description/explanation/examples]
–300
“Device-specific error”
This is the generic device-dependent error for devices that cannot detect more specific errors. This code indicates only that a Device-Dependent Error as defined in IEEE 488.2, 11.5.1.1.6 has occurred.
–310
“System error”
Indicates that some error, termed “system error” by the device, has occurred. This code is device-dependent.
–311
“Memory error”
Indicates that an error was detected in the device’s memory. The scope of this error is device-dependent.
–312
“PUD memory lost”
Indicates that the protected user data saved by the *PUD command has been lost.
–313
“Calibration memory lost”
Indicates that nonvolatile calibration data used by the *CAL? command has been lost.
–314
“Save/recall memory lost”
Indicates that the nonvolatile data saved by the *SAV? command has been lost.
–315
“Configuration memory lost”
Indicates that nonvolatile configuration data saved by the device has been lost. The meaning of this error is device-specific.
–330
“Self-test failed”
–350
“Queue overflow”
A specific code entered into the queue in lieu of the code that caused the error. This code indicates that there is no room in the queue and an error occurred but was not recorded.