An error message is displayed against a red background in the instrument message/warning area in the lower left part of the screen. Pushing a front panel key or executing :DISP:CCL command clears the error message. Errors caused by the operation of a front panel key simply appears on the display. They are not stored in the error queue with some exceptions.
An error with a positive error number is uniquely defined for this instrument. On the other hand, an error with a negative error number is basically defined for common GPIB devices in IEEE488.2.
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
|
No. |
Message |
Description |
|
6 |
Additional standards needed |
Before the completion of all the data measurement required for calculating the calibration/compensation coefficients, a GPIB command requiring any of the measurement data was sent. For example, when only the OPEN and SHORT measurements of the calibration kit have been completed, the :CORR1:COLL:SAVE command, which performs calculation of the calibration coefficients, was sent. Measure all the required data. |
|
No. |
Message |
Description |
|
-168 |
Block data not allowed |
A block data element was received where the E4982A does not accept any block data element. |
|
No. |
Message |
Description |
|
7 |
Calibration required |
Though the calibration was not turned ON, a GPIB command was sent that is valid only when the calibration is turned ON. For example, the :CORR2:COLL command, which obtains the data for calculating the compensation coefficients, was executed. Turn ON the calibration. |
|
62 |
Can't execute data examination |
The data for statistical analysis has been acquired, but change was made to the settings during the data acquisition, so statistical analysis cannot be executed. Acquire the data for statistical analysis with the current settings. |
|
-148 |
Character data not allowed |
A character data element (that did not violate the standard) was received where the E4982A does not accept any character data element. |
|
-100 |
Command error |
A comprehensive syntax error occurred for which the E4982A could not detect further details. This error code simply indicates the occurrence of a command error that is defined in IEEE488.2,11.5.1.1.4. |
|
11 |
Compensation required |
Although compensation was not turned ON, a GPIB command that is valid only when compensation is turned ON was sent. For example, the :DATA:CMP{1-3} command, which reads out the compensation coefficients, was executed when compensation was turned OFF. Turn ON the compensation. |
|
No. |
Message |
Description |
|
-230 |
Data corrupt or stale |
The data may be invalid or a newly initiated operation has not been completed since the latest access. |
|
-222 |
Data out of range |
A data element (that did not violate the standard) out of the defined range of the E4982A was received. |
|
-104 |
Data type error |
The parser recognized impossible data elements. For example, numeric value or string data was expected, but block data was sent. |
|
No. |
Message |
Description |
|
-200 |
Execution error |
This occurs when the operation is aborted due to an internal error. |
|
-123 |
Exponent too large |
The absolute value of the exponent exceed 32,000. (Refer to IEEE488.2,7.7.2.4.1.) |
|
-178 |
Expression data not allowed |
An equation data element was received where the E4982A does not accept any equation data element. |
|
-170 |
Expression error |
An error not included in error numbers between -171 and -179 occurred during the syntax analysis of equation data. |
|
No. |
Message |
Description |
|
1300 |
Failed to read file |
This occurs when it fails to read the file such as the state file. |
|
1301 |
Failed to write file |
This occurs when it fails to store the file. |
|
-256 |
File name not found |
The specified filename was not found and, as a result, the command was not executed correctly. For example, you attempted to read a file that does not exist on the disk. |
|
No. |
Message |
Description |
|
-105 |
GET not allowed |
A group execution trigger (GET) was received in a program message. (Refer to IEEE488.2, 7.7.) |
|
No. |
Message |
Description |
|
-224 |
Illegal parameter value |
The value of the parameter is illegal. |
|
-213 |
Init ignored |
Another measurement was being executed and the measurement start request (:INIT command) was ignored. |
|
-161 |
Invalid block data |
Block data was expected but the sent block data was invalid for some reasons. (Refer to IEEE488.2, 7.7.6.2.) For example, the END message was received before the length of the block data was reached. |
|
-101 |
Invalid character |
Invalid characters exist in the program message string. For example, for a correct program message, ":CALC:PAR1:FORM LS", an ampersand (&) is inserted by mistake as ":CALC:PAR1:FORM&LS". |
|
-121 |
Invalid character in number |
An invalid character for the data type of the syntax analysis target was received. For example, alphabetical characters exist in a decimal value, or "9" exist in octal data. |
|
6000 |
Invalid equation expression |
This occurs when the equation of the user define parameter has syntax error. |
|
-171 |
Invalid expression |
The equation data element is invalid. (Refer to IEEE488.2,7.7.7.2.) For example, parentheses are not paired or a character violates the standard. |
|
106 |
Invalid File Name |
When executing the save/recall file command, a file name string was invalid. For example, when executing the save command, no extension for the file was specified. Specify a valid file name. |
|
-103 |
Invalid separator |
The parser (syntax analysis program) expected a separator, but a character other than a separator was sent. For example, although the correct way is using ";" to separate two sent program messages such as ":CALC:PAR1:FORM LS;*OPC?", the semicolon (;) needed to separate the program messages is missing, as in ":CALC:PAR1:FORM LS *OPC?". |
|
-151 |
Invalid string data |
Character string data was expected but the sent string data was invalid for some reason. (Refer to IEEE488.2,7.7.5.2.) For example, the END message was received before the end quotation mark character appeared. |
|
-131 |
Invalid suffix |
The suffix does not meet the syntax defined in IEEE488.2,7.7.3.2 or is inappropriate for the E4982A. |
|
No. |
Message |
Description |
|
-109 |
Missing parameter |
The number of parameters is less than that the command requires. For example, although the "SOUR:LIST:TABL" command requires one parameter such as ":SOUR:LIST:TABL 3", no parameter is added, as in ":SOUR:LIST:TABL" |
|
No. |
Message |
Description |
|
0 |
(No error) |
No error has occured. This message is not displayed on the LCD. It is returned as the error number if no error has occurred in the instrument when the ":SYST:ERR?" command is sent through GPIB. |
|
61 |
No data available on memory |
Although no data for statistical analysis has been acquired, the "CALC:EXAM:GET?" command that executes statistical analysis and acquires the result was sent. Acquire the data for statistical analysis. |
|
-120 |
Numeric data error |
Numeric data (including numeric data without a decimal point) causes an error. A numeric value error other than -121 to -129 occurred. |
|
-128 |
Numeric data not allowed |
A numeric value data element (that did not violate the standard) was received where the E4982A does not accept any numeric value data element. |
|
No. |
Message |
Description |
|
-321 |
Out of memory |
An internal operation needed more memory than was available. |
|
No. |
Message |
Description |
|
-108 |
Parameter not allowed |
The number of parameters is larger than that the command requires. For example, although the :SOUR:LIST:TABL command requires one parameter such as ":SOUR:LIST:TABL 3", two parameters were added, as in ":SOUR:LIST:TABL 3,5". |
|
120 |
PLL unlock |
Phase lock loop was not locked. If you entered the external reference signal, check to see if it is correct. If you entered the correct signal or you did not enter it, the instrument needs adjustment or repair. Contact your local Keysight Technologies sales office or the company you purchased this instrument from. |
|
198 |
Power ON test failed |
In the power-ON self test, a fault was detected. Contact your local Keysight Technologies sales office or the company you purchased this instrument from. |
|
-112 |
Program mnemonic too long |
The length of the header exceeds 12 characters. (Refer to IEEE488.2,7.6.1.4.1.) |
|
No. |
Message |
Description |
|
-430 |
Query DEADLOCKED |
Status that causes a "DEADLOCKED" query error. (Refer IEEE488.2,6.3.1.7.) This error occurs, for example, when both input and output buffers before full and the E4982A cannot continue processing. |
|
-400 |
Query error |
A comprehensive Query error occurred for which the E4982A could not detect further details. This code simply indicates the occurrence of a query error that is defined in IEEE488.2,11.5.1.1.7 and 6.3. |
|
-410 |
Query INTERRUPTED |
Status that causes an "INTERRUPTED" query error. (Refer to IEEE488.1,6.3.2.3.) This error occurs, for example, when data bye (DAB) or GET is received after Query has been initiated but before the response has been completely sent. |
|
-420 |
Query UNTERMINATED |
Status that causes an "UNTERMINATED" query error. (Refer to IEEE488.2,6.3.2.) This error occurs, for example, when the E4982A is specified as a talker and an incomplete program message is received. |
|
-440 |
Query UNTERMINATED after indefinite response |
In a certain program message, after a Query that requested an ambiguous response was executed, another Query was received. (Refer to IEEE488.2,6.5.7.5.7.) |
|
No. |
Message |
Description |
|
105 |
Recall error |
An error occurred while reading out (recalling) a file. For example, you attempted to read out a file with invalid contents, such as an instrument file with extension ".sta" that was saved using an instrument other than the E4982A. Check to see if the contents of the file is valid. |
|
No. |
Message |
Description |
|
104 |
Save error |
When saving a file, anomalies in the storage media were detected. For example, if you attempt to save a file when there is not enough space on the disk. |
|
-221 |
Setting conflict |
A program data element complying with the syntax standard was analyzed but the E4982A could not execute it at the time. |
|
-150 |
String data error |
An error not included in error numbers between -151 and -159 occurred during the syntax analysis of a string data element. |
|
-158 |
String data not allowed |
A string data element was received where the E4982A does not accept any string data element. For example, a parameter that should not be enclosed with double quotation marks (") such as ABC is sent with them, as in "ABC" |
|
-138 |
Suffix not allowed |
A suffix is added to a numeric value element to which no suffix can be added. |
|
-134 |
Suffix too long |
The suffix contains the notation of 12 characters or more. (Refer to IEEE488.2,7.7.3.4.) |
|
-102 |
Syntax error |
There is a command or data type that cannot be recognized. For example, for a correct program message, ":SYST:PRES", an extra colon (:) is inserted by mistake, as in ":SYST::PRES". |
|
-310 |
System error |
One of the "system errors" defined for the E4982A occurred. |
|
No. |
Message |
Description |
|
-124 |
Too many digits |
The number of digits of the mantissa of the decimal value data element exceeds 255, aside from preceding 0. (Refer to IEEE488.27.7.2.4.1.) |
|
-223 |
Too much data |
The received block, equation, or string type program data complied with the standard but its amount exceeded the limit that the E4982A can deal with due to memory or device-specific conditions related to memory. |
|
-211 |
Trigger ignored |
A trigger command or trigger signal was received and recognized by the E4982A but was ignored due to the timing relationship with the E4982A (for example, when the E4982A's trigger system is not in Waiting for Trigger state). |
|
No. |
Message |
Description |
|
-113 |
Undefined header |
A header not defined for the E4982A was received. For example, "*XYZ", which is not defined for the E4982A, was received. |