EXFO FTB-1v2 Guide De L'utilisateur page 467

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