Ricoh MP C2004/C2504 Service Manual Part 14

Table of contents:
< Previous page: Part 13 | You are viewing page: Part 14 | Next page: Part 15 >

System Maintenance

  1. Enter the SP mode.

  2. Do SP5-846-051 (Backup All Addr Book).

  3. Exit the SP mode, and then turn OFF the main power switch.

  4. Remove the SD card form the SD card slot 2 (lower).

  5. Install the SD slot cover.


5.9.3 UPLOAD

  1. Turn OFF the main power.

  2. Remove the SD slot cover at the left rear side of the machine.

  3. Install the SD card, which has already been uploaded, into the SD card slot 2 (lower).

  4. Turn ON the main power.

  5. Enter the SP mode.

  6. Do SP5-846-052 (Restore All Addr Book).

  7. Exit the SP mode, and then turn OFF the main power switch.

  8. Remove the SD card form the SD card slot 2 (lower).

  9. Install the SD slot cover.


    1. CAPTURING THE DEVICE LOGS


      1. OVERVIEW

        With this feature, you can save device logs that are stored in the machine (HDD or operation panel) or an SD card. It allows the Customer Engineer to save and retrieve error information for analysis.

        The Capturing Log feature saves device logs for the following four.

        • Controller device log including operation log

        • Engine device log

        • FCU device log

        • Operation panel log


          • In older models, a technician enabled the logging tool after a problem occurred. After that, when the problem had been reproduced, the technician was able to retrieve the device log.

          • However, this new feature saves the device logs at the time that problems occur. Then you can copy the logs to an SD card.

          • You can retrieve the device logs using a SD card without a network.

          • Analysis of the device log is effective for problems caused by the software. Analysis of the device log is not valid for the selection of defective parts or problems caused by hardware.

          • Make sure to shut down and reboot the machine once before retrieving the Debug Logs. Otherwise, the latest settings may not be collected when the debug logs are retrieved.

            Types of device logs that can be saved


            Type

            Storage Timing

            Destination (maximum storage capacity)

            Controller device log including operation log

            HDD (4 GB) or SD card connected to the service slot.

            When the data gets over 4.0 GB, the older data is deleted.

            • Saved at all times

            Type

            Storage Timing

            Destination (maximum storage capacity)

            Engine device log

            HDD or SD card connected to the service slot (Up to 300 times)

            FCU device log

            HDD or SD card connected to the service slot

            Operation panel log

            Memory in the operation panel.

            • When an engine SC occurs

            • When paper feeding/output stop because of a jam

            • When the machine doors are opened during normal operation

            • When a specified amount of FCU device log is stored in the FCU. If fax application is unavailable (e.g. not installed), the machine does not transfer the log.

            • When an error related to the operation panel occurs.


            System Maintenance

          • Device logs are not saved in the following conditions:

          • While erasing all memory

          • While data encryption equipment is installed

          • While changing the firmware configuration

          • Forced power OFF (accidentally disconnecting the outlet)

          • Engine device log while the machine is shutting down

          • When the power supply to the HDD is off because of energy saving (engine OFF mode/STR mode)

          • When one of the following SCs occurs: SC672, SC816, SC819, SC878, SC899, SC859, SC860, SC861, SC863, or SC864

          • The following logs are not saved:

          • Logs related to the energy saver mode (Engine-off, suspend-mode, or other cases) Network communication log

            Logs related to NRS IP-FAX log

            Access log for unauthorized users (guests)

          • HTTP session timeout log

          • Auto log-out log

          • IC card related log

          • Authorization for Fax


          • The default save destination is the HDD. Except when it cannot be saved to the HDD for some reason, there is no need to change from the HDD to an SD card.

          • If you want to change the save destination to an SD card, do the following.

            1. Set SP5-858-002 (Collect Machine Info: Save To) to ”1 (SD)”

            2. Execute SP5-858-003 (Collect Machine Info: Make Log Trace Dir) to make a folder for the log in the SD card.

            3. Turn the power switch OFF and ON.

          • It is recommended to use the SD card (8 GB) provided as a service part. The part number of the SD card that is registered as a service part is "B6455040".


            Security of the Operation Log

            The following operation logs related to security are not saved.

        • User ID

        • Password

        • IP address

        • Telephone number

        • Encryption key

        • Transition to SP mode


      2. RETRIEVING THE DEVICE LOGS VIA OPERATION PANEL


        • Retrieve device logs to identify the date of occurrence of the problems and to find details of the problems

        • e.g.: At around 8:00 am on March 10, an engine stall occurred. The operation panel does not respond. Turn the main power supply off / on.

        • Analysis of the device log is effective for problems caused by the software. Analysis of the device log is not valid for the selection of defective parts or problems caused by hardware.

        System Maintenance

        Procedure for Retrieving the Device Log with SD Card

        1. Insert the SD card into the slot on the side of the operation panel or the service slot.


          • It is recommended to use the SD card (2 GBs* or 8 GBs**) provided as a service part. This is because the log data can be acquired much faster than when using commercially available SD cards.

          • Format the SD card by using SD Formatter from Panasonic before copying the logs: https://www.sdcard.org/downloads/formatter_3/ (free software)

          • Insert the SD card into the machine's service slot instead of the SD slot on the side of the operation panel.

            * The part number of the SD card with 2 GBs that is registered as a service part is "B6455030".

            ** The part number of the SD card with 8 GBs that is registered as a service part is "B6455040".

        2. Turn ON the main power.

        3. Enter SP mode.

        4. Specify the date that the problem occurred in SP5-858-101 (Start Date) by setting it to the year-month-day calendar format.

          • For example, if a problem occurred on February 1, 2015, the date should be set to "20150201", as shown above.

          • Be sure to confirm the date when the problem occurred before obtaining the logs.

        5. Specify the number of days to collect the logs in SP5-858-102 (Days of Tracing).

          • "2" is set by default, which is the minimum needed for investigating the problem.

          • A value of "1" to "180" can be set.

        6. Execute SP5-858-111 (Acquire All Info & Logs) to copy all of the log types to an SD card.

          It is possible to obtain the logs separately by the following SPs.


          SP

          Collectable Information and/or Logs


          SP5-858-111

          All of the information and logs that are collected by executing the SPs from SP5-858-121 to SP5-858-145, and SMC.

          SP5-858-121

          Configuration page

          SP5-858-122

          Font page

          SP5-858-123

          Print settings list

          SP5-858-124

          Print Error log

          SP

          Collectable Information and/or Logs


          SP5-858-131

          Fax information (whether the fax destinations are included or not depends on the setting of SP5-858-103.)

          SP5-858-141

          Controller log, engine log, operation panel log, FCU, and SMC.

          SP5-858-142

          Controller log

          SP5-858-143

          Engine log

          SP5-858-144

          Operation panel log

          SP5-858-145

          FCU log

          SP5-992-001

          SMC


        7. After executing the SP for copying the information and/or logs, a confirmation screen will appear. To proceed with obtaining the information and/or logs, tap "Execute"

          image


          • The approximate time it takes to transfer the debug log is as follows. Transfer time may be affected by the type or format of the SD card.

            Controller device log (GW device log): 2 - 20 minutes Engine device log: 2 minutes

            Operation panel device log: 2 - 20 minutes

            If the estimated time is not calculated due to an error, an error code will be displayed.


            Error Code

            Description

            -1

            Other.

            Error Code

            Description

            -2

            No SD card is inserted in the service slot or in the SD slot on the side of the operation panel. In this case, insert an SD card into either of the SD slots.

            -3

            The SD card is locked. In this case, unlock the SD card, as shown below.

            image

            [A]: Unlocked, [B]: Locked


            System Maintenance

        8. Wait for the information and/or logs to be copied to the SD card.


          image

        9. After a message stating that the process has completed appears on the operation panel, confirm that the LED light next to the SD card slot is not flashing and then remove the SD card.

        10. Make sure that the SD card access LED is off, then remove the SD card.


          • The process of obtaining logs fails in the following cases:

            • When the size of the logs to obtain exceeds the amount of space available on the SD card.

            • When the SD card is removed while the logs are being copied to it.

            • When the SD card is not formatted.

          • If ‘failed’ appears on the touch panel display, turn the power off, and then recover from step 1 again.

      3. RETRIEVING THE DEVICE LOGS VIA WEB IMAGE MONITOR

The device logs can be retrieved via the Web Image Monitor.

  1. Access the following URL and logon as an administrator:

    http://[IP address or host name]/web/entry/df/websys/direct/getSysInfo.cgi


    image

  2. Specify the date that the problem occurred and the number of days to download the logs. If the fax destinations need to be included in the fax information, set "On" as "Obtain Fax Destination(s) Information". Then click "Download".


    image


  3. The confirmation screen will appear and the information and/or logs will start downloading. To proceed to download the information and/or logs, wait for the open-or-save dialog to appear.

    image


    System Maintenance

  4. After a while, the open-or-save dialog will appear. Specify where to download and save the file.


The device logs are saved with the following file names.


Controller log (mmesg)

/LogTrace/[the model number]/watching/[yyyymmdd_hhmmss]_[a unique value].gz

Engine device log


/LogTrace/[Machine Serial]/engine/[yyyymmdd_hhmmss].gz

Operation panel log


/LogTrace/[the model number]/opepanel/[yyyymmdd_hhmmss].tar.gz


SMC

/LogTrace/[the model number]/smc/[the model number]_[5992XXX]_[yyyymmdd]_[hhmmss].csv

Configuration page

/LogTrace/[the model number]/gps/ConfigrationPage/ConfigrationPage_ [yyyymmdd_hhmmss].csv


Font page

  • /LogTrace/[the model number]/gps/FontPage/FontPage_PCL_[the page number]_[yyyymmdd_hhmmss].jpg

  • /LogTrace/[the model number]/gps/FontPage/FontPage_PDF_[the page number]_[yyyymmdd_hhmmss].jpg

  • /LogTrace/[the model number]/gps/FontPage/FontPage_PS_[the page number]_[yyyymmdd_hhmmss].jpg


Print settings list

  • /LogTrace/[the model number]/gps/PrintSettingList/PrintSettingList_RPGL_[yyyymmdd_hhmmss

  • /LogTrace/[the model number]/gps/PrintSettingList/PrintSettingList_RTIFF_[yyyymmdd_hhmmss

].txt

].csv

Error log

/LogTrace/[the model number]/gps/ErrorLog/[yyyymmdd_hhmmss].csv

Fax information


/LogTrace/[the model number]/faxreport/[yyyymmdd_hhmmss].csv

FCU debug log

/LogTrace/[Machine Serial]/fculog/[yyyymmdd_hhmmss].gz

System Maintenance

    1. SMC LIST CARD SAVE FUNCTION


      1. OVERVIEW


        SMC List Card Save

        The SMC List Card Save (SP Text Mode) function is used to save the SMC list as CSV files to the SD-card inserted into the operation panel SD-card slot.

        • Make sure to shut down and reboot the machine once before exporting the SMC sheet data. Otherwise, the latest settings may not be collected when the SMC is exported.

      2. PROCEDURE

        1. Turn OFF the main power.

        2. Insert the SD card into the operation panel SD-card slot, and then turn OFF the main power.

        3. Enter SP mode.

        4. Select "System SP".


          image

        5. Select SP5-992-001 (SP Text Mode).

        6. Select a detail SP number shown below to save data on the SD card.

          SP5-992-xxx (SP Text Mode)


          Detail No.

          SMC Categories to Save

          001

          All (Data List)

          002

          SP (Mode Data List)

          003

          User Program

          004

          Logging Data

          Detail No.

          SMC Categories to Save

          005

          Diagnostic Report

          006

          Non-Default

          007

          NIB Summary

          008

          Capture Log

          021

          Copier User Program

          022

          Scanner SP

          023

          Scanner User Program

          024

          SDK/J Summary

          025

          SDK/J Application Info

          026

          Printer SP

          027

          Smart Operation Panel SP

          028

          Smart Operation Panel UP


        7. Press [EXECUTE].


          image

        8. Press [EXECUTE] again to start. Press [CANCEL] to cancel the saving.

          image

          System Maintenance

        9. "It is executing it" is shown on the screen while executing.

          image

        10. Wait for 2 to 3 minutes until "Completed" is shown.


          • The SMC list saving may take from 2 to 3 minutes to complete.

          • Press [CANCEL] to abort executing.

        11. Press [Exit] to exit from SP mode.

      3. FILE NAMES OF THE SAVED SMC LISTS

        The SMC list data saved on the SD-card will be named automatically. The file naming rules are as follows.

        Example:


        image

        A:

        Machine serial number (fixed for each machine) B:

        SP number saved in this file.

        First four digits (5992) in this part are fixed. The other one or two digits are the detail SP number(s). In this case, it is one digit. Therefore, this file is of SP5-992-001 (All data list). See the upper SP table for the correspondence between SP detail numbers and the contents.

        C:

        File creation date

        Year/Month/Day ("Zero" will be omitted if each is one digit.)

        D:

        File creation time

        Hour/Minute/Second ("Zero" will be omitted if each is one digit.)

        E:

        File Extension CSV (Comma Separated Value)

        This part is fixed.


        • A folder named by the machine serial number will be created on the SD card when this function is executed.

        • This function can save the SMC list data only to an SD card inserted into the operation panel SD card slot.

      4. ERROR MESSAGES

SMC List Card Save error message:

Enables or disables the automatic reboot function when an SC error occurs.

0: The machine reboots automatically when the machine issues an SC error and logs the SC error code. If the same SC occurs again, the machine does not reboot.

1: The machine does not reboot when an SC error occurs. The reboot is not executed for the pattern A or C.


SC Logging

When an SC is generated, the "total count value when the SC is generated" and the "SC code" are logged. However, if the total count value during the SC is the same as last time, logging is not performed.

Logged data can be checked by outputting an administrative report (SMC print). The SC history is logged up to the last 10 entries, and if there are more than 10 entries, data are progressively deleted starting from the oldest.

      1. LIST OF AUTOMATIC REBOOT TARGET SC


Engine SC

Automatic reboot target SC is as follows. For details of Automatic reboot, refer to page 6-1 "SC Automatic Reboot".


SC code

Name

101-01

Lamp Error (Scanning)

101-02

Lamp Error (LED illumination adjustment)

102-00

LED Illumination Adjustment Error

120-00

Scanner Home Position Error 1

121-00

Scanner Home Position Error 2

141-00

Black level detection error

142-00

White level detection error

144-00

SBU Communication Error

151-00

Black Level Error: Side 2

SC code

Name

152-00

White Level Error: Side 2

154-00

Scanner Communication Error: Side 2

161-02

IPU error (Lsync Error: Side 2)

161-20

IPU error (DRAM initialization failure)

202-00

Polygon Motor: ON Timeout Error

203-00

Polygon Motor: OFF Timeout Error

204-00

Polygon Motor: XSCRDY Signal Error

220-01

Leading Edge: LD1 synchronization detection error: Bk

220-04

Leading Edge: LD1 synchronization detection error: Ye

230-01

FGATE ON error: Bk

230-02

FGATE ON error: Cy

230-03

FGATE ON error: Ma

230-04

FGATE ON error: Ye

231-01

FGATE OFF error: Bk

231-02

FGATE OFF error: Cy

231-03

FGATE OFF error: Ma

231-04

FGATE OFF error: Ye

240-01

LD error: Bk

240-02

LD error: Cy

240-03

LD error: Ma

240-04

LD error: Ye

272-01

LD driver communication error: Bk

272-02

LD driver communication error: Cy

272-03

LD driver communication error: Ma

272-04

LD driver communication error: Ye

Troubleshooting

SC code

Name

272-10

LD driver communication error: Other

312-01

Charge Roller HVP_CB Output Error (K)

312-02

Charge Roller HVP_CB Output Error (C)

312-03

Charge Roller HVP_CB Output Error (M)

312-04

Charge Roller HVP_CB Output Error (Y)

324-05

Development motor: CMY: Lock

360-01

TD sensor adjustment error (K)

360-02

TD sensor adjustment error (C)

360-03

TD sensor adjustment error (M)

360-04

TD sensor adjustment error (Y)

396-05

Drum motor (CMY) Lock

441-00

Drum transfer motor: Lock

442-00

ITB Lift Error

452-00

Paper transfer contact motor error

491-00

High voltage power source: charge/development: output error

531-01

Development Intake Fan/Right Lock

531-03

Drive Cooling Fan Lock

533-03

PSU Cooling Fan Lock

533-04

Controller Box Cooling Fan Lock

534-01

Main Exhaust Fan Lock

534-02

Toner Supply Cooling Fan Lock

534-03

Ozone Exhaust Fan Lock

535-00

Paper Exit Cooling Fan Lock

540-00

Fusing Motor: Lock

542-05

Thermopile (Center) does not reload (Low Power)

SC code

Name

542-06

Thermopile (Center) does not reload (Low Power)

545-05

Fusing Central Lamp Continuously Heat (Low Power)

547-01

Zero cross error (relay-contact soldering)

547-02

Zero cross error (relay contact error)

547-03

Zero cross error (low-frequency error)

552-05

Thermopile (Center) Does Not Reload (Low Power)

552-06

Thermopile (Center) Does Not Reload (Low Power)

561-05

Pressure Roller Thermistor (Center) Disconnection (Low Power)

562-05

Pressure Roller Thermistor (Center) Does Not Reload (Low Power)

569-00

Paper Exit/ Pressure Release Motor Error Detection

571-05

Pressure Roller Thermistor (Edge) Disconnection

572-05

Pressure Roller Thermistor (Edge) Does Not Reload ( Low Power)

581-05

Pressure Roller Thermistor (Full-Bleed Edge) Disconnection (Low Power)

582-05

Pressure Roller Thermistor (Full-Bleed Edge) Does Not Reload (Low Power)

620-01

ADF Communication error 1

620-02

ADF Communication error 2

620-03

ADF Communication error 3

621-00

Finisher communication error

622-01

Paper bank 1 communication error for Paper Feed Unit PB3150 (D694)

622-11

Paper bank 1 communication error for Paper Feed Unit PB3220/PB3210 (D787)

663-01

Reset Detection: Imaging IOB: Software hangup occurs

663-02

Reset Detection: Imaging IOB: Power ON reset occurs

663-03

Reset Detection: Imaging IOB: Software reset occurs

Troubleshooting

SC code

Name

663-11

Reset Detection: Paper Transport IOB: Software hangup occurs

663-12

Reset Detection: Paper Transport IOB: Power ON reset occurs

663-13

Reset Detection: Paper Transport IOB: Software reset occurs

664-01

VODKA1 (Paper Transport Vodka) access permission error to VODKA SRAM

669-01

EEPROM OPEN: ID error

669-02

EEPROM OPEN: Channel error

669-03

EEPROM OPEN: Device error

669-04

EEPROM OPEN: Communication abort error

669-05

EEPROM OPEN: Communication timeout error

669-06

EEPROM OPEN: Operation stopped error

669-07

EEPROM OPEN: Buffer full

669-08

EEPROM OPEN: No error code

669-09

EEPROM CLOSE: ID error

669-10

EEPROM CLOSE: No error code

669-11

EEPROM Data write: ID error

669-12

EEPROM Data write: Channel error

669-13

EEPROM Data write: Device error

669-14

EEPROM Data write: Communication abort error

669-15

EEPROM Data write: Communication timeout error

669-16

EEPROM Data write: Operation stopped error

669-17

EEPROM Data write: Buffer full

669-18

EEPROM Data write: No error code

669-19

EEPROM Data read: ID error

669-20

EEPROM Data read: Channel error

SC code

Name

669-21

EEPROM Data read: Device error

669-22

EEPROM Data read: Communication abort error

669-23

EEPROM Data read: Communication timeout error

669-24

EEPROM Data read: Operation stopped error

669-25

EEPROM Data read: Buffer full

669-26

EEPROM Data read: No error code

669-36

Verification error

669-37

Error Detection

681-01

Toner bottle: IDChip Communication error: Invalid device ID :K

681-02

Toner bottle: IDChip Communication error: Invalid device ID :M

681-03

Toner bottle: IDChip Communication error: Invalid device ID :C

681-04

Toner bottle: IDChip Communication error: Invalid device ID :Y

681-06

Toner bottle: IDChip Communication error: Channel error :K

681-07

Toner bottle: IDChip Communication error: Channel error :M

681-08

Toner bottle: IDChip Communication error: Channel error :C

681-09

Toner bottle: IDChip Communication error: Channel error :Y

681-11

Toner bottle: IDChip Communication error: Device Error :K

681-12

Toner bottle: IDChip Communication error: Device Error :M

681-13

Toner bottle: IDChip Communication error: Device Error :C

681-14

Toner bottle: IDChip Communication error: Device Error :Y

681-16

Toner bottle: IDChip Communication error: Communication error (interrupted) :K

681-17

Toner bottle: IDChip Communication error: Communication error (interrupted) :M

681-18

Toner bottle: IDChip Communication error: Communication error (interrupted) :C

Troubleshooting

SC code

Name

681-19

Toner bottle: IDChip Communication error: Communication error (interrupted) :Y

681-21

Toner bottle: IDChip Communication error: Communication timeout :K

681-22

Toner bottle: IDChip Communication error: Communication timeout :M

681-23

Toner bottle: IDChip Communication error: Communication timeout :C

681-24

Toner bottle: IDChip Communication error: Communication timeout :Y

681-26

Toner bottle: IDChip Communication error: Device stops (logically) :K

681-27

Toner bottle: IDChip Communication error: Device stops (logically) :M

681-28

Toner bottle: IDChip Communication error: Device stops (logically) :C

681-29

Toner bottle: IDChip Communication error: Device stops (logically) :Y

681-31

Toner bottle: IDChip Communication error: Full of buffer (request) :K

681-32

Toner bottle: IDChip Communication error: Full of buffer (request) :M

681-33

Toner bottle: IDChip Communication error: Full of buffer (request) :C

681-34

Toner bottle: IDChip Communication error: Full of buffer (request) :Y

681-36

Toner bottle: IDChip Communication error: Verification error:K

681-37

Toner bottle: IDChip Communication error: Verification error:M

681-38

Toner bottle: IDChip Communication error: Verification error:C

681-39

Toner bottle: IDChip Communication error: Verification error:Y

682-01

TD sensor communication error: Invalid device ID :K

682-02

TD sensor communication error: Invalid device ID :M

682-03

TD sensor communication error: Invalid device ID :C

682-04

TD sensor communication error: Invalid device ID :Y

682-06

TD sensor communication error: Channel error :K

682-07

TD sensor communication error: Channel error :M

682-08

TD sensor communication error: Channel error :C

SC code

Name

682-09

TD sensor communication error: Channel error :Y

682-11

TD sensor communication error: Device Error :K

682-12

TD sensor communication error: Device Error :M

682-13

TD sensor communication error: Device Error :C

682-14

TD sensor communication error: Device Error :Y

682-16

TD sensor communication error: Communication error (interrupted) :K

682-17

TD sensor communication error: Communication error (interrupted) :M

682-18

TD sensor communication error: Communication error (interrupted) :C

682-19

TD sensor communication error: Communication error (interrupted) :Y

682-21

TD sensor communication error: Communication timeout :K

682-22

TD sensor communication error: Communication timeout :M

682-23

TD sensor communication error: Communication timeout :C

682-24

TD sensor communication error: Communication timeout :Y

682-26

TD sensor communication error: Device stops (logically) :K

682-27

TD sensor communication error: Device stops (logically) :M

682-28

TD sensor communication error: Device stops (logically) :C

682-29

TD sensor communication error: Device stops (logically) :Y

682-31

TD sensor communication error: Full of buffer (request) :K

682-32

TD sensor communication error: Full of buffer (request) :M

682-33

TD sensor communication error: Full of buffer (request) :C

682-34

TD sensor communication error: Full of buffer (request) :Y

682-36

TD sensor communication error: Verification error:K

682-37

TD sensor communication error: Verification error:M

682-38

TD sensor communication error: Verification error:C

682-39

TD sensor communication error: Verification error:Y

Troubleshooting

SC code

Name

687-00

PER Not Received Error

700-01

SPDF: Base Plate Lift Motor Error

700-02

SPDF: Original Pick-up Error

700-04

SPDF: Paper Feed Motor Error

700-05

SPDF: Pullout Motor Error

700-06

SPDF: Intermediate Motor Error

700-07

SPDF: Scanning Motor Error

700-09

SPDF: Paper Exit Motor Error

701-03

SPDF: Paper Feed Motor Driver Error

701-08

SPDF: Paper Exit Motor Driver Error

702-01

ARDF: Protection Device Intercept Error 1

702-02

ARDF: Protection Device Intercept Error 2

702-03

ARDF: Protection Device Intercept Error 3

702-04

SPDF: Protection Device Intercept Error 4

702-05

SPDF: Protection Device Intercept Error 5

780-01

Bank 1 (Upper optional paper tray) Protection Device Intercept Error

781-01

Bank 2 (Lower optional paper tray) Protection Device Intercept Error

791-00

No bridge unit when finisher is present

995-01

CPM setting error 1

995-02

CPM setting error 2

995-03

CPM setting error 3

995-04

CPM setting error 4

Troubleshooting

Controller SC

Automatic reboot target SC is as follows. For details of Automatic reboot, refer to page 6-1 "SC Automatic Reboot".


SC code

Name

632-00

Counter device error 1

633-00

Counter device error 2

634-00

Counter device error 3

635-00

Counter device error 4

636-01

IC Card Error (Expanded authentication module error)

636-02

IC Card Error (Version error)

637-01

Tracking Information Notification Error (Tracking application error)

637-02

Tracking Information Notification Error (Management server error)

641-00

Communication error between BCU and Controller board

641-01

Communication error between BCU and Controller board: Timout

641-02

Communication error between BCU and Controller board: retry over

641-03

Communication error between BCU and Controller board: download error

641-04

Communication error between BCU and Controller board: UART error

670-01

Engine does not start up during the staring up

670-02

Engine does not start up after the staring up

670-03

IPU power does not start up

670-04

Communication is not linked up

816-00

Energy save I/O subsystem error

816-01

Subsystem error

816-02

Sysarch (LPUX_GET_PORT_INFO) error

816-03

Transition to STR was denied.

SC code

Name

816-04

Interrupt in kernel communication driver

816-05

Preparation for transition to STR failed.

816-07

Sysarch (LPUX_GET_PORT_INFO) error

816-08

Sysarch (LPUX_ENGINE_TIMERCTRL) error

816-09

Sysarch (LPUX_RETURN_FACTOR_STR) error

816-10 to 12

Sysarch (LPUX_GET_PORT_INFO) error

816-13

open() error

816-14

Memory address error

816-15 to 18

open() error

816-19

Double open() error

816-20

open() error

816-22

Parameter error

816-23

read() error

816-24

read() error

816-25

write () error

816-26

write() communication retry error

816-27

write() communication retry error

816-28

write() communication retry error

816-29

read() communication retry error

816-30

read() communication retry error

816-35

read() error

816-36 to 94

Subsystem error

818-00

Watchdog timer error

821-00

Self-diagnostics error: ASIC

823-00

Self-diagnostics error: NIC

< Previous page: Part 13 | You are viewing page: Part 14 | Next page: Part 15 >