Messages - Thermo Scientific VF-F20-A Operating Manual

8.2

Messages

Message and Code
Unexpected module behavior. Code XX
Module malfunction detected.
Code XX
Code 15. Command rejected - device is
busy.
Code 34. Leak detected.
Code 53. Module software malfunction
occurred. Diagnostic information
available. Please send daily audit trail
to service support.
Integral Fraction Collector FT (VF-F20-A) Operating Manual
The table lists the most frequently observed messages for the device
and provides troubleshooting assistance.
Each message consists of a code number and a text. The code number is
the unique identifier for the problem while the wording may change.
Note the following:
•
To facilitate finding a message, the table lists the messages sorted by
code.
•
If you cannot find the code you are looking for, check the message
text. Two messages (Unexpected module behavior and Module
malfunction detected) can have different codes and therefore,
appear at the beginning of the table.
TIP If you are unable to resolve the problem following the instructions in
this manual, or if you encounter a message not listed in the table, write
down the code and wording of the message and contact Thermo Fisher
Scientific Technical Support for assistance.
Description and Remedial Action
XX = Two-digit to four-digit code number.
When the message appears, write down the message code and turn off
the module. Wait for 5 seconds and turn on the module again.
TIP If the message appears again, contact Technical Support.
XX = Two-digit to four-digit code number.
When the message appears, write down the message code. Turn off
the module and contact Technical Support.
Device not ready to accept command.
Wait for current operation to complete and repeat command.
When this error code is reported, it means leak detected by the front
leak sensor located at the front and right-hand bottom side of the
device. Find and eliminate the source for the leakage
( page 212).
A firmware failure occurred during operation of the module and an
exception log has been created about the processes during the
firmware failure. For details, see
Troubleshooting
General Information about
( page 203).
•
8 Troubleshooting
(Operating Issues
Page 205