Agilent Technologies 4339B, Operation Manual

Page: 279 / 287

4339B GPIB Errors
-211 Trigger ignored
A GET , *TRG , or triggering signal was received and recognized by the 4339B but was ignored
because of 4339B timing considerations; for example , the 4339B was not ready to respond.
-213 Init ignored
A request for a measurement initiation was ignored as another measurement was already in
progress .
-221 Settings conict
A legal program data element was analyzed syntax but could not be executed due to the
current device state (see IEEE 488.2, 6.4.5.3 and 11.5.1.1.5).
-222 Data out of range
A legal program data element was analyzed syntax but could not be executed because the
interpreted value was outside the legal range as dened by the 4339B (see IEEE 488.2,
11.5.1.1.5).
-223 T oo much data
A legal program data element of block, expression, or string type was received that contained
more data than the 4339B could handle due to memory or related device-specic requirements .
-230 Data corrupt or stale
P ossibly invalid data; new reading started but not completed since last access .
-241 Hardware missing
A legal program command or query could not be executed because of missing 4339B hardware;
for example , an option was not installed.
-310 System error
Some error , termed \system error" by the 4339B, has occurred.
-311 Memory error
An error was detected in the 4339B 's memory .
-313 Calibration memory lost
The nonvolatile calibration data has been lost. When this error occurs during power-on test,
the 4339B stops operation and asserts the /ALARM signal on the handler interface . When this
error occurs during self-test, the 4339B continues operation and asserts the /ALARM signal.
Contact your nearest Agilent T echnologies oce .
-350 Queue overow
A specic code entered into the queue in lieu of the code that caused the error . This code
indicates that there is no room in the queue and an error occurred but was not recorded.
Messages-7