Filter
Top Products
Agilent E1441A Error Messages 141
Appendix B
Appendix B
Agilent E1441A Error Messages
Errors are retrieved in first-in-first-out (FIFO) order. The first error returned
(SYST:ERR? command) is the first error that was stored. When you have
read all errors from the queue, the next execution of SYST:ERR? returns
+0, "No error". Since no indication is given that an operation has caused an
error, your application program should query the error queue regularly.
If more than 20 errors have occurred, the last error stored in the queue (the
most recent error) is replaced with -350, “Too many errors”. No additional
errors are stored until you remove errors from the queue. If no errors have
occurred when you read the error queue, the function generator responds
with +0, “No error”.
The error queue is cleared when power has been off or after a *CLS (clear
status) command has been executed. The *RST (reset) command does not
clear the error queue.
SYSTem:ERRor?
Reads one error from the error queue
Errors have the following format (the error string may contain
up to 80 characters):
-113,"Undefined header"
Execution Errors
-101 Invalid character
An invalid character was found in the command string. You may have
inserted a character such as #, $, or % in the command header or within a
parameter. Example: TRIG:SOUR BUS#
-102 Syntax error
Invalid syntax was found in the command string. You may have inserted a
blank space before or after a colon (or before a comma) in the command
header. Example: APPL:SIN ,1
-103 Invalid separator
An invalid separator was found in the command string. You may have used
a comma instead of a colon, semicolon, or blank space – or you may have
used a blank space instead of a comma. Example: TRIG:SOUR,BUS
or APPL:SIN 1 1000
-105 GET not allowed
A Group Execute Trigger (GET) is not allowed within a command string.