EasyManua.ls Logo

Hologic QDR 4500 - Error Message List and Interpretation

Hologic QDR 4500
250 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
Section 6 - Fault Isolation
6-19
ERROR MESSAGE LIST
For any system error there may be one, or more, messages. The initial message is displayed when
the error occurs.
To display an additional message(s) press <Shift><F9>, and continue to
press <Shift><F9> until all messages, for that error, are seen.
Messages shown in the
Error
Message List
section below may be the first message, or a subsequent message.
Note:
All messages, for each system error, are saved in the ERRLOG file.
The top line in the message box, is the message title line. The message title line shows the
following:
Program, and version of that program, in which the error occurred. In the above example
the program, and version, is DBARCHIV Version 8.00.
LOCUS field - this field is often used to identify the device that has the problem. In the
above example, LOCUS is NONE (i.e. no LOCUS field).
Message identifier - the message identifier is the name Hologic Software Engineering
uses to identify the message. In the above example, the message identifier is
E_MSG_NO_FORM_O.
The main body of information in the message box, is the message text (in the above example, the
message text is Boundaryline Internal Software Error). In the
Error Message List
section below,
error messages are in alphabetical order (by first line of their message text). In some cases a
message identifier is also provided [in brackets].
The error messages covered in this section may indicate a hardware, or software, error. For
hardware errors a suggested action is provided.
In most cases, software errors are "sanity checks" that are used during the software development
process. During normal operation, these messages should never appear. If they do, and a
suggested action is not provided, call Hologic Technical Support. Include as much information as
possible about what was being done at the time the error occurred (including all messages for
that error, LOCUS field, message identifier, etc.).

Table of Contents

Related product manuals