Error and Event System

Error / Event Queue

The Error and Event Queue stores all errors and events that occurred. An entry consist of an error number, an error title and optionally an additional information to the error. The numbers titles and meanings can be found below List of all Errors and Events.

The queue implements the FIFO (first in first out) principle, always the first error that occurred is read first. If an entry is read, it is removed from the queue. If the queue is already empty, a no error string is returned. Only the error and event types that are enabled by the ESE (Event Status Enable) register, are added to the queue. The second bit of the STB indicates if there are entries left in the queue, waiting to be read.

The queue is cleared when calling *CLS.

Commands:

:SYSTem:Error[:NEXT]?

:SYSTem:Error:ALL?

:SYSTem:Error:COUNt?

List of all Errors and Events

No error

Nr.	Name	Type	Desription
`0`	No Error	`none`	this value is returned when there is no error and the error event queue is completely empty

Command Errors

Nr.	Name	Type	Desription
`-100`	command error	`Command Error`	generic error while trying to parse the incoming message
`-102`	syntax error	`Command Error`	unrecognized command or data type (e.g. a string was received when the device does not accept strings)
`-103`	invalid separator	`Command Error`	parser was excpecting a separator and encountered an illegal character
`-104`	data type error	`Command Error`	parser detected a data element different than the one allowed
`-108`	parameter not allowed	`Command Error`	more parameters were received than expected
`-109`	missing parameter	`Command Error`	fewer parameters were received than required
`-113`	undefined header	`Command Error`	command is undefined for this device although sintactically correct
`-120`	numeric data error	`Command Error`	given parameter could not be parsed to a numeric value
`-150`	string data error	`Command Error`	general error while trying to parse a string
`-158`	string data not allowed	`Command Error`	encountered a string data were no string data was allowed
`-170`	expression error	`Command Error`	expression error (e.g. parentheses not matching or illegal characters found)

Execution Errors

Nr.	Name	Type	Description
`-200`	execution error	`Execution Error`	general error while executing
`-201`	invalid channel index	`Execution Error`	Invalid channel index. Currently only one cahnnel is supported
`-202`	invalid trace index	`Execution Error`	Invalid trace index. Currently only one cahnnel is supported
`-211`	trigger ignored	`Execution Error`	triggering signal was received and recognized but was ignored (e.g. because a measurement was already running)
`-213`	init ignored	`Execution Error`	measurement initiation was ignored because another measurement was already in progress
`-220`	parameter error	`Execution Error`	a data element related error occurred
`-221`	settings conflict	`Execution Error`	a valid command could not be executed due to the current device state
`-222`	data out of range	`Execution Error`	a given parameter exceeded the allowed range
`-224`	illegal parameter value	`Execution Error`	a given parameter was not in the list of possible options that are accepted with the entered command
`-225`	out of memory	`Execution Error`	the device has insufficent memory to perform the requested operation
`-240`	analyzer not ready	`Execution Error`	Indicates that the device is not ready due to a missing connection
`-250`	mass storage error	`Execution Error`	Indicates that a mass storage error occurred. This error message will be used when the device cannot detect the more specific errors described for errors -251 through -259
`-256`	file name not found	`Execution Error`	the file name on the device media was not found
`-257`	file name error	`Execution Error`	Indicates that a legal program command or query could not be executed because the file name on the device media was not valid

Device Dependent Errors

Nr.	Name	Type	Description
`-300`	device specific error	`Device Dependent Error`	general error that is device specific
`-350`	queue overflow	`Device Dependent Error`	tried to add an element to a queue but queue is already full
`-340`	calibration error	`Device Dependent Error`	a calibration error has occurred. Do not save calibration values. Try re-calibrating the unit. It may happen when the calibration was cancelled or an overload occured.
`100`	failed to read file	`Device Dependent Error`	it was not possible to read a calibration file. Can happen if the version number is not correct, the caibration was saved with a different device or the frequencies do not match .
`101`	failed to write file	`Device Dependent Error`	it was not possible to save a calibration file. Can happen if trying to save an uncalibrated or not fully calibrated measurement.
`200`	missing shaped levels	`Device Dependent Error`	shaped levels cannot be applied because the amplitude list or the frequency list is missing or not fully defined.
`514`	not allowed	`Device Dependent Error`	Action is not allowed. Can happen in combination with locking e.g. if an Instrument is locked by another I/O session.

Query Errors

Nr.	Name	Type	Description
`-400`	query error	`Query Error`	general query error

Events

Nr.	Name	Type	Description
`-500`	power on	`Event`	off to on transition of the power source was detected
`-800`	operation complete	`Event`	all pending operations have terminated

For examples on Error Handling read the Error Handling page.