The document discusses troubleshooting problems with the communications bus of a Nuvera printer control system. It provides details on identifying issues by examining LED states on the main control board and remote control board during boot up. Key components that communicate over the CAN and SCSI buses include the remote control board, main control board, image input terminal, and scanner/finisher modules. Faults can be isolated by disconnecting modules one by one from the communications bus.
The document discusses troubleshooting problems with the communications bus of a Nuvera printer control system. It provides details on identifying issues by examining LED states on the main control board and remote control board during boot up. Key components that communicate over the CAN and SCSI buses include the remote control board, main control board, image input terminal, and scanner/finisher modules. Faults can be isolated by disconnecting modules one by one from the communications bus.
The document discusses troubleshooting problems with the communications bus of a Nuvera printer control system. It provides details on identifying issues by examining LED states on the main control board and remote control board during boot up. Key components that communicate over the CAN and SCSI buses include the remote control board, main control board, image input terminal, and scanner/finisher modules. Faults can be isolated by disconnecting modules one by one from the communications bus.
The document discusses troubleshooting problems with the communications bus of a Nuvera printer control system. It provides details on identifying issues by examining LED states on the main control board and remote control board during boot up. Key components that communicate over the CAN and SCSI buses include the remote control board, main control board, image input terminal, and scanner/finisher modules. Faults can be isolated by disconnecting modules one by one from the communications bus.
Download as DOC, PDF, TXT or read online from Scribd
Download as doc, pdf, or txt
You are on page 1/ 3
Troubleshooting Printer Control System Problems
The subsystems of the Nuvera communicate over a CAN and SCB bus. The RCB is the primary controller of the communications bus. The subsystems are: Finisher (MFF/BFM) PPC Xerographic (XDC, PRC, ROS) SFM IIT (RIS, DS) Each control pwb has 2 memory locations dedicated to board identification. The first memory location identifies the type of module (IOT, SFM, etc.) and the second memory location identifies the build level of the module. By polling the communications bus and reading the identification bytes for each board on the bus, the system constructs the printer “mimic” in the upper right hand corner of the DocuSP screen at each boot up. The mimic is a useful diagnostic aid as it is recreated each time the system boots. If a module is missing from the mimic, that module was not read as the CAN bus was polled during system initialization. If there is no mimic at all, it indicates a general communications bus fault (see below.) A system message of “Internal SCSI Interface Fault” indicates that the System Interface Board and the Main Control Board cannot communicate via the SCSI bus. They may be communicating via the cat5 network connection. SCSI communication failure between the two board is often the result of problems on the bus. You can troubleshoot the bus by examining the state of the LEDs on the Main Control Board and the RCB PWB.
J1 (To PPC and Xero Mod) J4 (To Main Control Board)
CR21
Reset J3 (To SFM) CR33
24v J7 (To Scanner) CR70 36v
RCB PWB Identifying Normal Run State On the Main Control Board (MCB) there are 8 LEDs, 6 red and 2 green, labeled 8 – 15 LEDs 8-13 will sequentially blink off as the system boots. LED 13 will go off approximately 2 minutes after power up indicating that the proper program code has been loaded (through the network connection) from the System Interface Board LED 14 is the heartbeat monitor and flashes when the board is functional at a low level. LED 15 flashes to indicate that the MCB program code is running properly. It usually begins flashing approximately 2 minutes 30 seconds after power on.
On the RCB there are 6 LEDs.
In a Normal Run State, the RCB 24v and 36v LEDs should be on indicating proper voltage. In interlock open will cause the 36v LED to be off. CR33 and CR70 should initially come on solid and then flash, indicating the RCB is operating normally. The Reset LED should be off. CR21 (in the upper right hand corner of the board) is typically ON for C/P models. The RCB should enter the Normal Run State approximately 30 seconds after LED 15 begins flashing on the MCB. Identifying a Faulted RCB Typically a faulted device on the bus will cause CR33 and CR70 to remain on steady on the RCB. Occasionally the MCB and the RCB will enter a perpetual reset cycle where every 2-4 minutes the MCB will start its load cycle over – as indicated by LEDs 8-13 coming back on and progressing off again. Simultaneously with the MCB reloading you will see CR33 and CR70 turn off and the RCB reset LED flash on for about 1-2 seconds and then CR33 and CR70 will come back on steady again. Use the procedure below to identify the source of the fault.
Locating the Fault on the communications Bus
First, power down the system. Using the illustration above, disconnect J1, J3 and J7 on the RCB. (Do not disconnect J4.) Then disconnect the MFF cable where it connects to the back of the interface module (by your left foot). Power on the system. At this point the bus consists of just the MCB and the RCB. The system should fully boot to a Normal Run State. The mimic should only display an IOT with no additional modules. IF… The MCB does not boot to a Normal Run State – suspect cabling problems between the System Interface Board and the MCB, a bad NVModule, or a bad MCB. The MCB does boot to a Normal Run State (even if it reboots shortly afterward) but the RCB does not – Suspect a bad RCB Both the MCB and RCB boot to a Normal Run State – The MCB and RCB are good. You must locate the faulted node on the bus. Power down the system, plug in one of the disconnected communication chains and power back up. When you plug in the faulted chain the MCB and RCB will no longer boot to a Normal Run State.
LED Timings During the Boot Sequence
Main Control PWB RCB
Time LED 8 9 10 11 12 13 14 15 24v 36v CR21 CR33 CR70 Reset
A Power On O O O O O O O O O O O O O O B + 1 second - - O O O O O O C 3 seconds - - - O O O O O O O O O O - D 10 seconds - - - O O O F O E 12 seconds - - - - O O F O F 45 seconds - - - - - O F O G 2 min (approx) - - - - - - F O H G+5 seconds - - - - - - - O O O - - O O I G+6 seconds O O O O O - J G+10 seconds - - - - - - F O K G+15 seconds - - - - - - F F L G+30 seconds (IOT Init) - - - - - - F F O O X F F -
Key: - Off O On F Flashing X See note regarding CR21 below
Notes and details on LED timings:
Timings are approximate and are based upon a properly functioning machine running 3.5.44.04 software. Timings between Points A and F appear to be consistent. The timing between F & G is not always consistent. Point F (CR12 going out) indicates the MCB is waiting to initiate an FTP session with the System Interface PWB. Point G, indicating the completion of the FTP download of MCB program code, has been observed as early as 1 minute 50 seconds and as late as 2 minute 40 seconds on the same machine. 2 minutes is the norm. If the machine has a BFM or SFM2 Insertion Module CR21 on the RCB will be off. Main Control PWB LED Description
LED Reference Name Fault mode
CR8 CPU OK LED ON CR9 SDRAM OK LED ON CR10 FLASH OK LED ON CR11 PHY Present LED ON CR12 Load Start LED ON CR13 Load Finish LED ON CR14 OS Heartbeat LED ON CR15 Apps Heartbeat LED ON
