No Parallel Communication; Sensor Malfunctions - Intermec EasyCoder 301 Service Manual

13.8 No Serial
Communication,
cont'd.
13.9 No Parallel
Communication
13.10 Sensor
Malfunctions
Intermec EasyCoder 301 – Service Manual Ed. 3
• No response from printer when running a custom-made pro-
gram.
- The verbosity can be controlled by means of the Direct
Protocol instructions VERBON/VERBOFF and SYSVAR(18).
In the Intermec Direct Protocol, verbosity is by default ena-
bled. Check the program for instructions that may affect the
verbosity.
- Verify that the correct communication port is selected as
standard IN/OUT channel.
Description:
The following actions are valid for the parallel "Centronics"
interface. Also see chapter 12.7.
Possible Causes and Suggested Remedies:
• Damaged interface board or cable.
- Replace the CPU board with another one which is positively
working in other printers and try again. If the CPU board
seems to be damaged, replace it. Do not attempt to repair a
damaged CPU board.
• Wrong std IN channel selected in custom-made program.
- Verify that the Centronics communication port is selected as
standard IN channel.
Description:
Label (ticket) gap or black mark not detected by the media
sensor.
Possible Causes and Suggested Remedies:
• Lost or obsolete paper feed data , for example after a headlift or
change of media.
- Perform a testfeed operation using a TESTFEED instruction
or by pressing the Feed button while turning on the power
(Test Label printing).
• Bad LSS lateral alignment.
- Check that the gaps or marks actually pass through the sensor
(lateral alignment), see chapter 7.5.
• Light path obstructed.
- Check that the entire sensor is free from paper dust or parts of
stuck labels.
• Printer set for wrong paper type.
- Check that the printer is correctly set up for the type of media
in use.
• Bad connection
- If the sensor still does not operate correctly, check the condition
of its cables and that it they are correctly connected to J7 on
the CPU board.
• Faulty sensor.
- Replace the entire sensor module as described in chapter 7.5.
Chapter 13 Troubleshooting
73