-178 Expression data not allowed
Execution Errors
An execution error indicates that the device could not execute a syntactically correct command, either since the data
were out of the instrument's range, or due to a device condition. The EXE bit (bit 4) of the Standard Event Status
Register is set on occurrence of an execution error.
-200 Execution error
An attempt was made to RECALL the contents of an uninitialized stored setting buffer.
-201 Invalid while in local.
-211 Trigger ignored.
The GET or *TRG common command was ignored due to the device not being in the correct state
to execute the trigger.
-220 Parameter error.
A parameter is in the correct range, but conflicts with other parameters.
-221 Settings conflict.
The parameter is out of range due to the current instrument state.
-222 Data out of range.
-223 Too much data.
The arbitrary waveform memory limit has been exceeded.
-224 Illegal parameter value.
The parameter value must be selected from a finite list of possibilities.
-258 Media protected.
An attempt was made to write to protected arbitrary waveform memory.
Device-Specific Errors
An error specific to the device occurred. The DDE bit (bit 3) of the Standard Event Status Register is set.
-315 Configuration memory lost.
Device memory has been lost.
-330 Self-test failed.
-350 Queue overflow.
Error codes have been lost due to more than 10 errors being reported without being read.
Query Errors
A query error indicates that the output queue control has detected a problem. This could occur if either an attempt
was made to read data from the instrument if none was available, or when data were lost. Data could be lost when a
query causes data to be formatted for the controller to be read, and the controller sends more commands without
reading the data.
-410 Query INTERRUPTED.
Data were sent before the entire response of a previous query was read.
-420 Query UNTERMINATED.
An attempt was made to read a response before the complete program message meant to generate
that response was sent.
-430 Query DEADLOCKED.
The input buffer and output queue are full, and the controller is attempting to send more data. In
this case the output queue and input buffers will be cleared. Parsing will resume after the END
message is detected.
-440 Query UNTERMINATED after indefinite response.
A query was received in the same program message after a query requiring an indefinite response
was formatted. Essentially this means that the *IDN? common query and the :ARB:DATA? query
should not be followed by more query messages in the same program message.
Comentários a estes Manuais