PDA

View Full Version : C-C151 code after repeated 0X1FFF errors and FW update


Custom Search


blazebusiness
10-26-2022, 12:53 AM
Konica c258 was intermittantly jamming and logging 0X1FFF errors (restart error) in detail codes.

Updated the firmware and got a C-C155 code.

FW update for the finisher had failed and loaded to 90% before displaying N.G. Repeated attempts to load finisher FW results in NG.
I have also tried updating the finisher on its own

Unplugged finisher and copier starts normally. Plug in finisher and get a C-C155 code.

Any ideas appreciated.

Markks
10-26-2022, 01:46 AM
Konica c258 was intermittantly jamming and logging 0X1FFF errors (restart error) in detail codes.

Updated the firmware and got a C-C155 code.

FW update for the finisher had failed and loaded to 90% before displaying N.G. Repeated attempts to load finisher FW results in NG.
I have also tried updating the finisher on its own

Unplugged finisher and copier starts normally. Plug in finisher and get a C-C155 code.

Any ideas appreciated.

What model finisher? It may be the wrong one for the c258. the c258, c308 and c368 takes the FS-534/FS-534SD or the FS-533. The c458, c558 and the c658 takes FS-536/FS-536SD, FS-537/FS-537SD , FS-533 can be put on the c458 & c558.
I once had a C558 that was sent out with a FS-534 and it worked fine until a tech flashed it with FS-536 firmware. the only way we could recover was to roll the finisher over to a c368 and flash it back with FS-534 firmware .

blazebusiness
10-26-2022, 03:13 PM
What model finisher? It may be the wrong one for the c258. the c258, c308 and c368 takes the FS-534/FS-534SD or the FS-533. The c458, c558 and the c658 takes FS-536/FS-536SD, FS-537/FS-537SD , FS-533 can be put on the c458 & c558.
I once had a C558 that was sent out with a FS-534 and it worked fine until a tech flashed it with FS-536 firmware. the only way we could recover was to roll the finisher over to a c368 and flash it back with FS-534 firmware .

I suspect that is indeed the issue. Thanks for the reply. I'll quickly resolve that finisher issue but still not sure what's causing the constant 0X1FFF errors.

tsbservice
10-26-2022, 04:04 PM
What model finisher? It may be the wrong one for the c258. the c258, c308 and c368 takes the FS-534/FS-534SD or the FS-533. The c458, c558 and the c658 takes FS-536/FS-536SD, FS-537/FS-537SD , FS-533 can be put on the c458 & c558.
I once had a C558 that was sent out with a FS-534 and it worked fine until a tech flashed it with FS-536 firmware. the only way we could recover was to roll the finisher over to a c368 and flash it back with FS-534 firmware .

Yep, FS536 is not compatible with bizhub C258 :)



I suspect that is indeed the issue. Thanks for the reply. I'll quickly resolve that finisher issue but still not sure what's causing the constant 0X1FFF errors.

Maybe wrong model finisher :)

blazebusiness
10-26-2022, 06:05 PM
Yep, FS536 is not compatible with bizhub C258 :)




Maybe wrong model finisher :)


That makes sense to me, perhaps when the finisher issue is resolved then the 0X1FFF errors will also be dealt with.

Markks
10-29-2022, 01:02 AM
That makes sense to me, perhaps when the finisher issue is resolved then the 0X1FFF errors will also be dealt with.

Its a good possibility that correcting the finisher will resolve your issue. I did find this you can try if correcting finisher doesn't work.

ErrorCFA17 occurs during copying or printing.

Note: The following code may also be recorded:


40C3/5 CTL PF Tx Time Out, 0x1FFF, 0x8E1B, etc.



Root Cause
Thread error caused by buffer sequence error

Workaround/Fix
1. Reseat all connectors on the MFP board, the Memory Module(s) (if any), the DSIPB (if any), and the HDD.
2. Run Self Diagnostic Full [Menu -> Counter -> Stop, 0, 0, Stop, 0, 1 -> CE Password: -> State Confirmation].
3. Perform System Error Clear [Menu -> Counter -> Stop, 0, 0, Stop, 0, 1 -> CE Password: -> System 1 -> Initialization].
4. Reload the firmware. (Refer to Field Service Manual for details on Rewriting of firmware.)
5. Run Self Diagnostic Full [Menu -> Counter -> Stop, 0, 0, Stop, 0, 1 -> CE Password -> State Confirmation].

blazebusiness
10-30-2022, 12:38 AM
Its a good possibility that correcting the finisher will resolve your issue. I did find this you can try if correcting finisher doesn't work.

ErrorCFA17 occurs during copying or printing.

Note: The following code may also be recorded:


40C3/5 CTL PF Tx Time Out, 0x1FFF, 0x8E1B, etc.



Root Cause
Thread error caused by buffer sequence error

Workaround/Fix
1. Reseat all connectors on the MFP board, the Memory Module(s) (if any), the DSIPB (if any), and the HDD.
2. Run Self Diagnostic Full [Menu -> Counter -> Stop, 0, 0, Stop, 0, 1 -> CE Password: -> State Confirmation].
3. Perform System Error Clear [Menu -> Counter -> Stop, 0, 0, Stop, 0, 1 -> CE Password: -> System 1 -> Initialization].
4. Reload the firmware. (Refer to Field Service Manual for details on Rewriting of firmware.)
5. Run Self Diagnostic Full [Menu -> Counter -> Stop, 0, 0, Stop, 0, 1 -> CE Password -> State Confirmation].



Appreciate all the replies........ thanks to all of you.

Update on progress:

The machine did indeed have the correct FS-534 model finisher installed after all, and replacing that finisher with a different one resolved the issues with the finisher code and the FW update N.G. issue.

The repeated 0X1FFF errors we have narrowed down to an issue with the Magenta TCR. When they print greyscale, no errors. When they print color, it sometimes prints and sometimes fails and gives the 0X1FFF error, in service mode the only error that corresponds to each occurence is a magenta tcr error code displayed on service mode>counter> page 5/11 as "2553/54/5A/62 TCR SENSOR M".

Level history 1 shows around 7-8% tcr for other colors but 11.25% for magenta. On the Konica 8 series machines it causes the display of that generic 0X1FFF error restart code when printing instead of displaying the actual error code of C-2553 and then restarting machine in the middle of a job.

Total meter on copier is just 32,000 and all parts & consumables are oem. Trying to decide whether or not to replace the M dv unit. Based on the meter count, seems way too soon for that to be the issue.

rrrohan
10-31-2022, 01:09 AM
i got that error after putting a FS534 on a C308 and forgetting to deselect finisher from firmware update

DK-tech
10-31-2022, 01:36 PM
i got that error after putting a FS534 on a C308 and forgetting to deselect finisher from firmware update

FS-534 IS the correct finisher for C308 so why would you deselect it in fw?

rrrohan
11-01-2022, 01:19 AM
FS-534 IS the correct finisher for C308 so why would you deselect it in fw?

sorry i meant C458

blazebusiness
11-04-2022, 04:48 PM
Appreciate all the replies........ thanks to all of you.

Update on progress:

The machine did indeed have the correct FS-534 model finisher installed after all, and replacing that finisher with a different one resolved the issues with the finisher code and the FW update N.G. issue.

The repeated 0X1FFF errors we have narrowed down to an issue with the Magenta TCR. When they print greyscale, no errors. When they print color, it sometimes prints and sometimes fails and gives the 0X1FFF error, in service mode the only error that corresponds to each occurence is a magenta tcr error code displayed on service mode>counter> page 5/11 as "2553/54/5A/62 TCR SENSOR M".

Level history 1 shows around 7-8% tcr for other colors but 11.25% for magenta. On the Konica 8 series machines it causes the display of that generic 0X1FFF error restart code when printing instead of displaying the actual error code of C-2553 and then restarting machine in the middle of a job.

Total meter on copier is just 32,000 and all parts & consumables are oem. Trying to decide whether or not to replace the M dv unit. Based on the meter count, seems way too soon for that to be the issue.

To close out this thread, adding some magenta toner by hand, to get the TCR ratio closer to 7-8% and then running the stabilizer and gradiation adjustments has resolved the 0X1FFF errors / C-2553 codes.

Thanks very much to all who replied.

Custom Search