Sindoh A610 Series, Руководство по обслуживанию

Страница: 168 / 218

164
310 Printhead lost Hsync Occurs when printer head cannot detect Hsync properly
3. Check the harness between system card and
printer head
4.
If the problem is not solved, replace the print
head
311 Mirror motor lock
failure Occurs
when print head’s internal mirror motor does not
reach target speed within the configured time
1. Check the harness between system card and
printer head
2.
If the problem is not solved, replace the print
head
Error Description Action
320 Main motor lock
failure Occurs when driving motor does not reach target speed
within the configured time
1. Check the harness between system card and
driving motor unit
2.
If the problem is not solved, replace the driving
motor unit
330 Fan motor lock
failure Occurs when fan motor does not reach target speed
within the configured time
1. Check the harness between system card and fan
unit
2.
If the problem is not solved, replace the fan unit
331 Sub Fan motor lock
failure Occurs when drum fan motor fails to reach target speed
in set time
1. Check the harness between system card and fan
unit
2. If the problem is not solved, replace the fan unit
332 Dev Fan motor lock
failure Occurs when Dev fan motor fails to reach target speed in
set time
1. Check the harness between system card and fan
unit
2. If the problem is not solved, replace the fan unit
340 Option Tray Lost link
Error Occurs
when there’s a communication problem between
option tray
1. Check the harness between system card and
option tray
2. If the problem is not solved, replace the option
tray board
Service Error Code (9xx)
Error Description Action
910 Software Assert System stopped due to software error while running
1. Check if problem recurs after POR.
2. Replace system card if problem recurs.
912 Software
Segmentation Fault System stopped due to false memory access while
software was running.
1. Check if problem recurs after POR.
2. Replace system card if problem recurs.
920 DB recovery
success DB has been successfully restored after DB damage.
1. Wait to reboot