Sensor Malfunctions; Label Stop Sensor (Lss) - Intermec EasyCoder PX4i Service Manual

17.12 Sensor Malfunctions

Label Stop Sensor (LSS)

EasyCoder PX4i and PX6 Service Manual
Description:
Label (ticket) gap or black mark not detected by the label stop sensor (LSS)
or wrong amount of media feed.
Possible Causes and Suggested Remedies:
• Lost or obsolete media feed data, for example after a headlift, change
of media, or replacement of the sensor.
- In Fingerprint, perform a TESTFEED operation, for example by
simultaneously pressing <Shift> and <Feed> or selecting the Testfeed
option in the Setup Mode.
- In IPL, adjust the media feed by pressing the Feed/Pause button.
• Bad LSS lateral alignment.
- Check that the gaps or marks actually pass between the upper and
lower parts the label stop sensor (lateral alignment), see Chapter 7.5.
- Check that both parts of the LSS are adjusted to the same lateral posi-
tion, see Chapter 7.5.
• Light path obstructed.
- Check that both the upper and lower sensors are free from dust and
the slots in the upper and lower guide plates are free from stuck
labels, or other matters that may interfere with the path of light.
• Printer set for wrong media type.
- Set up the printer for the correct media type.
• Media feed detection using PRSTAT (Fingerprint only).
- PRSTAT AND 8 only checks for out-of-media conditions once as
opposed to the normal error checking (errors 1005 and 1031) that
checks for out-of-media conditions almost continuously. Thus, when
using PRSTAT, a dark spot or a bad media angle can give an incorrect
out-of-media indication, especially when using tickets (w. mark).
• Bad connection
- Check the LSS cables and make sure that they are correctly connected
to J54 and J55 on the CPU board, see Chapter 13.3.
• Faulty sensor or diode.
- Replace LSS as described in Chapter 7.5.
• CPU board not confi gured for the right type of printer.
- Reconfi gure the CPU board as described in Chapter 15.8.
Note: The LSS Test option in the Setup Mode is useful for identifying LSS
troubles. Refer to Chapter 8.5.
Chapter 17 — Troubleshooting
231