EXFO FTB-2 - Manual (Page 401)

SCPI-Based Errors
FTB-2 and FTB-2 Pro 391
–312 “PUD memory lost” [Indicates that the protected user data saved by the
*PUD command has been lost.]
–313 “Calibration memory
lost”
[Indicates that nonvolatile calibration data used by
the *CAL? command has been lost.]
–314 “Save/Recall memory
lost”
[Indicates that the nonvolatile data saved by the
*SAV? command has been lost.]
–315 “Configuration
memory lost”
[Indicates that nonvolatile configuration data saved
by the device has been lost. The meaning of this
error is device-specific.]
–320 “Storage fault” [Indicates that the firmware detected a fault when
using data storage. This error is not an indication of
physical damage or failure of any mass storage
element.]
–321 “Out of memory” [An internal operation needed more memory than
was available.]
–330 “Self-test failed” -----
–340 “Calibration failed” -----
–350 “Queue overflow” [A specific 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.]
–360 “Communication
error”
[This is the generic communication error for
devices that cannot detect the more specific errors
described for errors –361 through –363.]
–361 “Parity error in program
message”
[Parity bit not correct when data received for
example, on a serial port.]
–362 “Framing error in
program message”
[A stop bit was not detected when data was
received for example, on a serial port (for example,
a baud rate mismatch).]
Error
Number
Description Probable Cause