Agilent 664xA: troubleshooting and error codes
The ServiceForge knowledge base holds 3 documented symptoms for the Agilent 664xA, with 3 ranked causes, 1 diagnostic checks with test points and expected values, and 42 error codes. Each symptom below shows its causes and the first check; the rest is one connection away. Connect ServiceForge to your AI
Symptoms
ADDR ERROR displayed when setting GPIB address
Display shows ADDR ERROR when attempting to enter a forbidden or invalid GPIB address
Ranked causes
- 1. Invalid GPIB address value entered (common)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Output connections touch causing arcing high voltage
Severe arcing may occur at output connections if they touch, resulting in burns, ignition or welding of parts
Ranked causes
- 1. Output connections inadvertently touching during remote programming (occasional)
Verify output connections are properly isolated and cannot make contact
- Test point
- Output connections
- Expected
- Connections isolated, no contact risk
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Query DEADLOCKED error returned
System returns Query DEADLOCKED error when too many queries are requested in a single string
Ranked causes
- 1. Too many queries in a single command string (common)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Error codes
| Code | Meaning | Trigger | Severity |
|---|---|---|---|
0 | NO ERROR | When error queue is empty or all errors have been read | info |
-100 | Command error | Generic command error received from system | error |
-101 | Invalid character | Invalid character in command | error |
-102 | Syntax error | Unrecognized command or data type in command message | error |
-103 | Invalid separator | Illegal character encountered in place of separator | error |
-104 | Data type error | Wrong data type provided for command parameter | error |
-105 | GET not allowed | <GET> function used inside a program message | error |
-108 | Parameter not allowed | Too many parameters supplied to command | error |
-109 | Missing parameter | Too few parameters supplied to command | error |
-112 | Program mnemonic too long | Command mnemonic exceeds 12 characters | error |
-113 | Undefined header | Command syntactically correct but not defined for this device | error |
-121 | Invalid character in number | Non-numeric character in numeric field (e.g. alpha in decimal data) | error |
-123 | Exponent too large | Numeric exponent exceeds magnitude of 32000 | error |
-124 | Too many digits | Number received contains more than 255 digits | error |
-128 | Numeric data not allowed | Numeric data provided where non-numeric expected | error |
-131 | Invalid suffix | Unrecognized suffix or suffix not appropriate for parameter | error |
-138 | Suffix not allowed | Numeric element with disallowed suffix | error |
-141 | Invalid character data | Bad or unrecognized character | error |
-144 | Character data too long | Character string exceeds 12 characters | error |
-148 | Character data not allowed | Character data in invalid position | error |
-150 | String data error | Generic string data error | error |
-151 | Invalid string data | END received before closing quote | error |
-158 | String data not allowed | String data where not accepted | error |
-160 | Block data error | Generic block data error | error |
-161 | Invalid block data | END received before length satisfied | error |
-168 | Block data not allowed | Block data in invalid position | error |
-220 | Parameter error | Generic parameter error condition | error |
-221 | Settings conflict | Uncoupled parameters have conflicting values | warning |
-222 | Data out of range | Parameter value outside device operating range | error |
-223 | Too much data | Out of memory condition | error |
-240 | Hardware error | Device-dependent hardware failure | error |
-241 | Hardware missing | Required hardware not present or detected | error |
-310 | System error | Device-dependent system error | error |
-313 | Calibration memory lost | Out of calibration due to memory failure | error |
-330 | Self-test failed | Device self-test execution failure | error |
-350 | Queue overflow | Errors lost due to too many in queue | warning |
-350 | TOO MANY ERRORS | More errors accumulated than the queue can hold | critical |
-400 | Query error | Generic query error condition | error |
-410 | Query INTERRUPTED | DAB or GET before response complete | error |
-420 | Query UNTERMINATED | Addressed to talk, incomplete message received | error |
-430 | Query DEADLOCKED error | Too many query statements requested in a single command string | error |
-440 | Query UNTERMINATED | Query received after query for indefinite response | error |
Likely causes and actions for each code are in ServiceForge. Connect ServiceForge to your AI
Community
0 fixes logged by technicians through their AI, with outcomes, for this model.
ServiceForge knowledge base record. Field-unverified unless technicians confirmed it. A teaching summary of the record, not a service manual. Export 2026-10-14.