| A | B | Неисправность | Причина | Примечание |
|---|
| | Fujiko-ODA The true disposal method is indicated as a machine. -- Especially a different portion from the disposal method of a former machine is. system fail/sub system fail (I have a person in charge indicate Fail which requires hard / mechanism part exchange) | Fujiko-ODA True detection conditions are indicated as a machine. -- Especially the portion the detection conditions of a former machine are indicated to be as they are is. It is cautious of system fail/sub system fail |
| 001 | 300 | Top Cover Open | | Top or Top+Rear Cover Open is detected |
| 001 | 301 | Rear Cover Open | | Only Rear Cover Open is detected |
| 001 | 302 | OCT Cover Open | | OCT Cover Open is detected |
| 001 | 306 | Imari: Left Hand Dup Cover
GINGA: Duplex Cover Open
Topo: Duplex Cover Open | If not repaired in Duplex Cover Close, a sensor check is carried out, and it is Duplex Cover exchange after that | Duplex Cover Open is detected |
| 001 | 398 | Top Cover Open | If not repaired in power supply OFF/ON, it is LV Fan exchange | When LV FAN does not turn at regular number of rotations |
| 003 | 205 | (Copy/Scan/Print improper Fail)
BILLING FAIL (By PWB exchange)
Imari: Three billing counter disagreement | Power OFF/ON, and the following is performed when a trouble continues
Diag (DC132) disposal is performed and a Billing value is arranged
When after disposal occurs, ESS PWB (PL13.1) is exchanged | When all the billing counters currently held to two or more places differ
"SubSystemFail" - ChainLink corrected the classification of Fault in unknown Imari |
| 003 | 206 | "Copy/Scan/Print improper Fail"
BILLING FAIL
Imari: Billing counter automatic restoration cannot be carried out, but it is at the one billing restoration time | Power OFF/ON, and the following is performed when a trouble continues.
SEEPROM of ESS PWB, or the abnormalities of NVM.
Or the abnormalities in EEPROM of MCU PWB.
When a NVM battery is not faulty, ESS PWB (PL13.1) or MCU PWB (PL13.1) is exchanged | When uncorrectable at the time of the correction at the time of one billing counter disagreement
"SubSystemFail" - ChainLink corrected the classification of Fault in unknown Imari |
| 003 | 346 | Imari: (IOT) The Scope-FD transmitting error which Controller detects (parity error) | Power OFF/ON, and the following is performed when a trouble continues
(1) Check connection of MCU PWB connection harness
(2) Poor soft adjustment Re-installation of software is carried out
(3) When also generating the above-mentioned correspondence, exchange MCU PWB (PL13.1) | Since ACK was unreceivable by two resendings, it is communication generating (the parity error was detected by HARDWARE by the side of IOT)
* It changed from -- 340 ChainLinkj of SubSystemFail of Imari must be [ 340 ] from 350 |
| 003 | 347 | Imari: (IOT) The Scope-FD transmitting error which Controller detects | Since ACK was unreceivable by two resendings, it is communication generating (HARDWARE by the side of IOT, the error was detected)
* It changed from -- 340 ChainLinkj of SubSystemFail of Imari must be [ 340 ] from 350 |
| 003 | 348 | Topo: (IOT) Transmitting error which Controller detects. It is inaccurate command detection at the time of transmission | | |
| 003 | 349 | Topo: (IOT) Transmitting error which Controller detects. Transmitting undershirt run | | |
| 003 | 350 | Topo: (IOT) The other various transmitting error which Controller detects | | |
| 003 | 354 | Imari: (IOT) The Scope-FD reception error which Controller detects (parity error)
Hana: It Parity-error-generates during status reception from IOT | Power OFF/ON, and the following is performed when a trouble continues
(1) Check connection of MCU PWB connection harness
(2) Poor soft adjustment Re-installation of software is carried out
(3) When also generating the above-mentioned correspondence, exchange MCU PWB (PL13.1) | It generates, when NAK which notifies communication generating is received (the parity error was detected by HARDWARE which the UART itself has)
* It changed from -- 340 ChainLinkj of SubSystemFail of Imari must be [ 340 ] from 350 |
| 003 | 356 | Imari: (IOT) The Scope-FD reception error which Controller detects (overrun error)
Hana: It Overrun-error-generates during status reception from IOT | It generates, when NAK which notifies communication generating is received (the overrun error was detected by HARDWARE which the UART itself has)
* It changed from -- 340 ChainLinkj of SubSystemFail of Imari must be [ 340 ] from 350 |
| 003 | 360 | IOT-ESS initialization error | Initialization Fail of IOT Driver
This ChainLink is set when "communication establishment with IOT is not completed" in initialization (iotifInit) of an IOT driver |
| 003 | 362 | It PAGE-SYNC-generates before the completion of (image output) video output preparation | Power OFF/ON, and the following is performed when a trouble continues
1. Exchange the harness which connects ESS and IOT
2. Exchange of ESS PWB | PageSync is active before writing in at the time of an IOT output until it becomes FIFO full about output data |
| 003 | 363 | It is a PAGE-SYNC end error during a (image output) video output | PageSync was generated before outputting the size specified at the time of an IOT output |
| 003 | 364 | (Image output) DMA transfer error | Power OFF/ON, and the following is performed when a trouble continues
1. When exchange (PL13.1)
2. DC355 Diag diagnosis of RAM is performed and a trouble continues, it is exchange (PL13.1) of HDD
3. ESS PWB (PL13.1) | Although the data specified at the time of compression/extension was inputted, it generates, when compression/extension is not completed
ID=153 and duplication -- It also leaves this, although "Video DMA Fail" (3-364) is overlapped |
| 003 | 367 | An error of others from Decompress (extension) | Power OFF/ON, and the following is performed when a trouble continues
1. Exchange the harness which connects ESS and IOT
2. When Not Restoring by IOT-PWB Exchange, it is Exchange of Following 2.ESS PWB | - Unjust detection of LINE SYNC (Ginga)
1) V-SYNC inaccurate during an IOT output and the H-SYNC signal were generated
2) Overrun of data generates generating (it generates in the parameter setting mistake to Panther4) 2 only during debugging. 1) The error factor of the main |
| 003 | 368 | GINGA: (Image output) PCI Bus Error | Power OFF/ON, and the following is performed when a trouble continues
1. Exchange of ESS PWB | - In the fault of a PCI bus, abnormalities occurred in access of PCI |
| 003 | 370 | Marker code detection error | Power OFF/ON, and the following is performed when a trouble continues
When only a specific document is generated
- A possibility of being the fault of S/W is high
1. It may be outputted by changing printing mode (standard/high-definition/-- highly minute)
2. It may be outputted by changing RAM size
A. Change the RAM size to install
B. Change the operating size of RAM. (Setting change of a port, receiving buffer size, etc. are changed.) When generating by almost all documents in O unspecified.
- A possibility of being the fault of HW is quantity | When it elongated by the size specified at the time of extension, an end code (FF02) was not found in compression data |
| 003 | 371 | GINGA; Establishment of the communication between ESS and IOT which Controller detects was not completed | Power OFF/ON, and the following is performed when a trouble continues
1. Exchange the harness which connects ESS and IOT
2. Exchange of Exchange 3.MCU PWB of ESS PWB | - The ACK packet from the IOT side was unreceivable to within a time to the synchronous packet which transmitted from the Controller side |
| 003 | 372 | The DLL transmitting error which GINGA:Controller detects (inaccurate parameter directions) | Power OFF/ON, and the following is performed when a trouble continues
1. Exchange of ESS PWB | - Detect unjust directions of unjust directions of unjust directions of unjust directions of an IOT port number, and timeout time, and a pointer, and transmission size |
| 003 | 600 | Imari: Billing Master Counter restoration | Only registration to History | When automatic restoration of Cont NV-E is performed. (Counter necessity) |
| 003 | 601 | Imari: Billing Master Counter 1 restoration | When automatic restoration of Cont NV-S is performed. (Counter necessity) |
| 003 | 602 | Imari: Billing Master Counter 2 restoration | When automatic restoration of IOTdc NV-E is performed. (Counter necessity) |
| 003 | 747 | The print parameter directed [ in which were directed and the error was print-parameter-made ] is unusual | A print parameter is changed and re-printed | The directed print parameter is unusual
UI Cont receives this notice of error from PFlite at the time of initialization and execution, and notifies to UI at it.
It is not Sub System Fail. In Imari, it treats as "Job Fail"
(Print log) print parameter trouble occurred.
Directions specified by the job at the time of print execution of a confidential print (paper tray) |
| 003 | 946 | Tray 1 Out Of Place | If it is the same as that of user disposal and is NG, they are a tray detection sensor or tray exchange | Unentered
Feeder Status
* Offer HID 980420 information by Centre Ware |
| 003 | 947 | Tray 2 Out Of Place |
| 003 | 948 | Tray 3 Out Of Place |
| 003 | 949 | Tray 4 Out Of Place |
| 003 | 950 | Tray 1 Empty | When a trouble continues by supply of a paper, Sensor is checked with reference to general-purpose Sensor FIP | Unentered
Feeder Status
* Offer HID 980420 information by Centre Ware |
| 003 | 951 | Tray 2 Empty |
| 003 | 952 | Tray 3 Empty |
| 003 | 953 | Tray 4 Empty |
| 003 | 954 | Tray SMH Empty | When a trouble continues by supply of a paper, Sensor is checked with reference to general-purpose Sensor FIP | It ..(ed) and those of a tray without a paper were detected
Feeder Status
* Are there HID 980420 *HID 980508 which it will be at what time |
| 003 | 955 | Since the inner shot has fallen out, paper cannot be fed | The same as that of user disposal | Unentered |
| 003 | 958 | Size mismatch Imari: SMH size -- incongruent | The right paper is set | It ..(ed) and the paper which carried out print directions differed from the paper in a tray
Job
* HID 980515
It stops at normal output 1 |
| 003 | 959 | size mismatch Tray 1 size -- incongruent | which sets the right paper.
When a trouble continues, Sensor is checked with reference to general-purpose Sensor FIP | The paper which carried out print directions differed from the paper in a tray 1 |
| 003 | 960 | size mismatch Tray 2 size -- incongruent | The paper which carried out print directions differed from the paper in a tray 2 |
| 003 | 961 | size mismatch Tray 3 size -- incongruent | The paper which carried out print directions differed from the paper in a tray 3 |
| 003 | 962 | size mismatch Tray 4 size -- incongruent | The paper which carried out print directions differed from the paper in a tray 4 |
| 003 | 965 | ATS/APS No Paper
APS/ATS NG (No Paper) | The paper directed on a print has no paper |
| 003 | 966 | ATS/APS No Destination Error
ATS/APS NG (except No Paper) | A setup is changed. When a trouble continues, Sensor is checked with reference to general-purpose Sensor FIP | The paper directed on a print is undetectable |
| 003 | 985 | The stop check of SMH | Paper size / the direction of a paper / paper kind is checked, and a discharge key is pushed | It ..(ed) with a certain obstacle and the run from a tray was interrupted |
| 004 | 362 | NVM R/W Fail(U6-4) | If not repaired in power supply OFF/ON, it is NVM tip exchange | At the time of Write Check NG generating at the time of NVM (EEPROM) writing
Or the right value is not acquired in NVM R/W |
| 004 | 363 | comm: Drum K Motor Drive Fail(U1-4) | The Imari service manual, the Chapter 2 troubleshooting, 004 to 363 reference
Fuhjin | |
| 004 | 922 | No Toner K | The same as that of user disposal | CRU life operation was set as the stop by the panel, and after IOT detected Toner Warning, data transmission was performed by 100 sheets
XXXXX displays a color. When two or more color exchange is required, it is displayed as "toner cart ..."
* HID980619 |
| 006 | 355 | Poor ROS MOT rotation | | ROS Motor Abnormality was detected
Since LouiseSE and the resource value were doubled, it adds newly |
| 007 | 311 | MSI Down Broken
MSI Unit was separated after the power supply injection | | MSI Unit Fail was detected
Local Fail |
| 007 | 313 | Tray Module communication FailGINGA/Topo: Tray3/Tray4 module was separated.
Topo: Only the option tray 4 is applied | The abnormalities in communication with an option tray (trays 2-4, TTM 3 and 4) occurred. Connection is checked. When there are no abnormalities in connection, it is tray exchange Power Off - On.
Topo: Only the option tray 4 is applied | When it judges that the reply from communication with RemoteCPU is an error
Ginga: When the abnormalities in communication with an option tray (1TM/3TM) are detected
Topo: Only the option tray 4 is applied |
| 007 | 950 | GINGA: Tray1 size mismatch (subscanning length error) | The same as that of user disposal | As a result of measuring and acting as paper length by the Reg sensor, it detects differing from the paper length set up (specification) |
| 007 | 951 | GINGA: Tray2 size mismatch (subscanning length error) |
| 007 | 952 | GINGA: Tray2 size mismatch (subscanning length error) |
| 007 | 953 | GINGA: Tray3 size mismatch (subscanning length error) |
| 007 | 954 | SMH size mismatch (scanning [ sub] length error) Imari-MF: Subscanning length / main scanning width error | As a result of measuring and acting as paper length by the Reg sensor, it detects differing from the paper length set up (specification)
Imari: It adds by IOT related subcommittee #23.
The error which IOT dc notifies to IOT sc.
Subscanning length is inspected after a Feed start, when short, it is begun to put on a paper (it points out printing and discharging to the middle), and when long, it becomes jam (Regi Sensor On Jam). |
| 007 | 969 | From the tray of the quality of paper which Topo:APS-quality-of-paper-Mismatch(es) and is different to printing (it indicates by the message and becomes a Confirm screen) | | By the message which tells "whether it prints in the paper of which tray", since the misapprehension "it will be correctly printed if a paper to print on Tray N is set" is caused, are cautious of the contents of a message |
Коды ошибок принтеров Oki B6200 / B6300