230 Paper Jams - Lexmark B2650 Service Manual

230 paper jams

230 paper jam messages
Error code Description
230.03 Paper fed from the MPF never reached the sensor
(duplex).
230.05 Paper fed from the MPF never cleared the sensor
(duplex).
230.13 Paper fed from tray 1 never reached the sensor
(duplex).
230.15 Paper fed from tray 1 never cleared the sensor
(duplex).
230.23 Paper fed from tray 2 never reached the sensor
(duplex).
230.25 Paper fed from tray 2 never cleared the sensor
(duplex).
230.33 Paper fed from tray 3 never reached the sensor
(duplex).
230.35 Paper fed from tray 3 never cleared the sensor
(duplex).
230.43 Paper fed from tray 4 never reached the sensor
(duplex).
230.45 Paper fed from tray 4 never cleared the sensor
(duplex).
230.91 Paper remains detected at the sensor (duplex)
after the printer is turned on.
Sensor (duplex) jam at leading edge service check
Action
Step 1
Make sure that the paper is loaded properly. Use the
recommended paper. See
Does the problem remain?
Step 2
a
Enter the Diagnostics menu, and then navigate to:
Input tray quick print
b
Do feed tests from different trays. Check if the same error
occurs.
Does the same problem remain?
"Avoiding jams" on page
Diagnostics and troubleshooting
90
Action
See "Sensor (duplex) jam at leading edge
service check" on page
See "Sensor (duplex) jam at trailing edge service
check" on page 92.
See "Sensor (duplex) jam at leading edge
service check" on page
See "Sensor (duplex) jam at trailing edge service
check" on page 92.
See "Sensor (duplex) jam at leading edge
service check" on page
See "Sensor (duplex) jam at trailing edge service
check" on page 92.
See "Sensor (duplex) jam at leading edge
service check" on page
See "Sensor (duplex) jam at trailing edge service
check" on page 92.
See "Sensor (duplex) jam at leading edge
service check" on page
See "Sensor (duplex) jam at trailing edge service
check" on page 92.
See "Sensor (duplex) static jam service check"
on page 93.
Yes
Go to step 2.
66.
Go to step 3.
4600-830, -835, -895
90.
90.
90.
90.
90.
No
The problem is
solved.
Perform the
appropriate service
check for the specific
error.