Product Reference Guide
63
Chapter 5
Problem Isolation
The troubleshooting references provided in this section should be used in the event of a
suspected functional problem. This information will assist you in identifying and resolving
any problems.
The scanner/scale has a number of features that indicate when a scanner, EAS deactivation
system, or scale problem occurs. The unit may:
• emit a series of tones
• light the Health & Status Indicator (FRU status) display
• flash its indicator LEDs
• display error codes on the Remote Display (if installed)
Three error reporting modes are used: Power-Up Selftest, Operational tests and Diagnostic
tests. These test sequences are explained on the following pages.
Power-Up Selftest
The Power-up Selftest is a pre-operational series of tests that must be successfully
completed before the scanner indicates readiness for operation. This pre-operational period
is the time between power-up and normal operation during which the software, firmware
and hardware are being tested. These tests ensure that all subsystems are fully functional
before turning on. Refer to the
Section 3 subsection titled, Operational Modes for a more
detailed description of this and other scanner and scale modes.
Operational Tests
These are the tests that run continually during Normal Operation and Sleep Mode. Firmware
checks all subsystems, accessory connections and the POS interface to verify everything is
operating normally. If a problem is detected at any time, a long, low tone is sounded, an
error code is shown on the Health & Status Indicator, and operation may be halted. If you
press the Scanner Control Button at that time, a series of tones will be sounded that matches
the error code displayed.
Diagnostic Tests
See Chapter 2, Diagnostic Modes, for details about running diagnostic tests for the
scanner and/or scale. If a problem is discovered during diagnostics, the scanner will provide
feedback about the source of the problem. The remainder of this section describes these
failure indications and includes troubleshooting flowcharts to help isolate the problem.