Cpu Fan Service Check; Developer Drive Assembly Service Check - Lexmark X500n Service Manual

7100-XXX

CPU fan service check

Step
1 Open the RIP cage cover. Is the CPU fan
spinning?
2 Is the CPU fan cable properly connected to
J-Fan1 on the RIP board?

Developer drive assembly service check

Step Questions / actions
1 Are there any unusual noises heard around
developer motor or developer drive
assembly before error posts?
2 Does noise go away?
3 Does noise go away?
4 Turn printer off, and remove right cover. See
"Right cover removal" on page
cable properly connected to developer drive
assembly motor?
5 If waste toner bottle is removed, reinsert it.
Ensure rear cover assembly is shut.
Override top and front cover interlock
switches. For location, see
switch locations" on page
operator panel. Turn printer on. Allow printer
to run until error posts. Disconnect
connector from each developer motor, and
check for the following on each
disconnected cable connector:
Pin 2 to ground—24VDC
Pin 5 to ground—24VDC
Are voltages present?
6 Remove engine controller board shield. See
"Engine controller board removal" on
page 4-34 for steps to remove engine
controller board shield. Disconnect MCN5
from engine controller board. Check for
continuity and shorted pins on cable that
connects MCN5 to developer motors. Is
cable okay?
2-16
Service Manual
Questions / actions
4-14. Is
"Interlock
5-6. Reconnect
Yes
No issue to fix.
Connect the cable to J-
Fan1.
Yes
Replace toner cartridge
(customer-ordered supply).
Go to step 2.
Problem solved.
Problem solved.
Go to step 5.
Replace developer drive
assembly. See "Developer
drive assembly removal"
on page 4-21. Go to step 8.
Go to step 7.
No
Go to step 2.
Replace the RIP board. See
"System board removal"
on page 4-36.
No
Go to step 4.
Replace developer drive
assembly. See "Developer
drive assembly removal"
on page 4-22. Go to step 3.
Go to step 4.
Properly connect cable.
Retest printer. If error
clears, problem solved,
otherwise go to step 5.
Go to step 6.
Replace cable. Retest
printer. If error clears,
problem solved, otherwise
go to step 7.