-300 through -399 Error Message Descriptions

Last updated: January 16, 2009

Description

A device-specific error indicates that the instrument has detected an error that occurred because some operations did not properly complete, possibly due to an abnormal hardware or firmware condition. For example, an attempt by the user to set an out of range value will generate a device specific error. When one of these errors is generated, the device specific error bit in the event status register is set.

Error Message	Description
-300 Device specific error	This event bit (Bit 3) indicates that a device operation did not properly complete due to some condition, such as overrange see IEEE 488.2, 11.5.1.1.6.
-311 Memory error	Indicates some physical fault in the devices memory, such as a parity error.
-312 PUD memory lost	Indicates protected user data saved by the *PUD command has been lost, see IEEE 488.2, 10.27.
-313 Calibration memory lost	Indicates that nonvolatile calibration data used by the *CAL? command has been lost, see IEEE 488.2, 10.2.
-314 Save/recall memory lost	Indicates that the nonvolatile data saved by the *SAV command has been lost, see IEEE 488.2, 10.33.
-315 Configuration memory lost	Indicates that nonvolatile configuration data saved by the device has been lost.
-320 Storage fault	Indicates that the firmware detected a fault when using data storage. This is not an indication of physical damage or failure of any mass storage element.
-321 Out of memory	An internal operation needed more memory than was available
-330 Self test failed	Indicates a problem with the device that is not covered by a specific error message. The device may require service.
-340 Calibration failed	Indicates a problem during calibration of the device that is not covered by a specific error.
-350 Queue overflow	Indicates that there is no room in the queue and an error occurred but was not recorded. This code is entered into the queue in lieu of the code that caused the error.
-360 Communication error	This is the generic communication error for devices that cannot detect the more specific errors described for error -361 through -363.
-361 Parity error in program message	Parity bit not correct when data received for example, on a serial port.
-362 Framing error in program message	A stop bit was not detected when data was received for example, on a serial port (for example, a baud rate mismatch).
-363 Input buffer overrun	Software or hardware input buffer on serial port overflows with data caused by improper or nonexistent pacing.