Konica C224e - 4 Sharkfins / Bars

[hot_tracks]

We have a Bizhub C224e which had the battery on the board go dead. The machine lost all counters as well.

The battery has been replaced but on bootup the machine gets stuck on four sharfins/ bars with the orange status light blinking and a thin orange bar at the top of the screen (not a screen failure). Have tried doing the NVRAM reset and some other steps suggested on this forum as well as a trouble reset.

Have been in touch with the local KM service technicians who have checked it but there is nothing further they are able to do and have said that advanced support for this machine is no longer available from KM.

I was wondering if there was anything else I could try or if I should go ahead and scrap the machine.

[Duplicator]

Yes there is. If you hold down the power button then turn the main gray power switch on, do you get the diagnostic mode? If not, what is displayed on the screen, is the activity light on, and what color is the power button? Depending on what these display, it lines up with a diagnostic chart from Konica.

Although truthfully....it's an old machine at this point. Depends on much time you really want to put into it....

[hot_tracks]

Yes, able to get to diagnostics (power button blue / activity light blinking) and service mode. It's when I try to start it up normally it gets stuck on the screen with the 4 bars and orange light blinking. Some photos attached if they help. The machine is in really great condition with low usage so feel a bit bad to scrap it without trying all options first.

2024-11-01 17.04.41.jpg





























2024-11-01 20.25.01.jpg

[blackcat4866]

What do those NG1 and NG2 errors point to? The CCD?

[copier tech]

Start by updating the firmware.

www.printerfirmware.co.uk

[hot_tracks]

Yes, the CCD IRC Internal Check and the CCD IRC to Memory. I found this in the service manual which looks like it relates to the error.

Screenshot_110124_101917_PM.jpg

Screenshot_110124_103739_PM.jpg

[Duplicator]

Do you have a dual scan document feeder? If so you may have the bad image cable issue. One thing you could try would be to remove the dual scan board with the ADF disabled in service mode to see if it boots. You could also try problem unit isolation. If you hold reset and start the copier and then enter service mode at the trouble reset screen you can enable problem unit isolation for the scanner or dual scan board (or both). Machine may boot after that.

[hot_tracks]

Yes, an ADF is installed. Will try what you have suggested.

[hot_tracks]

I have tried all the steps you suggested including the problem unit isolation. Unfortunately no luck and since KM is unwilling to support us any further looks like we will have to scrap the unit.

Thank you for all your help, it's greatly appreciated.

[Duplicator]

I have tried all the steps you suggested including the problem unit isolation. Unfortunately no luck and since KM is unwilling to support us any further looks like we will have to scrap the unit.

Thank you for all your help, it's greatly appreciated.

Well, if that didn't work the only thing I can think of to try is to replace the CCD assembly under the scanner glass. However, that's going to be tricky to find unless your local dealer parts out and keeps parts from their old machines. Sounds like they don't want anything to do with it though.

No problem.

[jotunn]

looks like we will have to scrap the unit

Not too early?

1. The thin orange line looks like a remote panel connection indicator - which is quite strange.

image.png

2. Four bars/sharkfins are displayed at firmware initialization stage, if the machine hangs at this stage it means problems with loading or executing some part of the copier firmware.

3. The battery was completely dead, which means that NVRAM (containing some of the machine's settings) was erased - but before the battery was completely dead, the machine regularly backed up this data to eMMC, and there is a high probability that this data was corrupted. So now, after changing the battery and initialising, the machine has restored this corrupted data from the backup. Problems 1 and 2 may be related to this.

4. NG1 and NG2 may be related with 2 - but this is the last thing you need to worry about.

At this point, it is likely that all problems come from corrupted data/firmware on the eMMC.
Just in case, try to disconnect HDD and check machine behaviour.

Then first of all I would try to access service mode once again, for example via trouble reset procedure. If possible I would try to review/reset all the settings in service mode [System 1]->[Initialization]->[Clear ALL Data]
With lack of possibility to enter CE mode, maybe I would try initialization with firmware once again, to gain access to service mode and again review/reset settings.

[femaster]

With lack of possibility to enter CE mode, maybe I would try initialization with firmware once again, to gain access to service mode and again review/reset settings.

If what you are referring to here is the reset firmware (initialization), I'd expand upon that and say to run it 3 times in a row. There is some magical stuff that happens when you run it 3 times in a row, without allowing the copier to fully reboot in between. As in, boot from the rest firmware 3 times in a row without removing the USB stick. I'm not sure what exactly this does, but a KM Support Technician had us do it for some sort of an issue that the standard reset / initialize didn't fix, but the three in a row fix things right up.

[hot_tracks]

Thank you for all the input. I have run the reset tool (A145FW.TAR) thrice as suggested and it now comes back to the D390 error (which had happened before as well). If I click on recover data it goes back to the same 4 shark fins / bars with orange light blinking.

Since the battery had gone dead Jotunn's explanation regarding the NVRAM to eMMC data backup being corrupted makes the most sense. I have also tried disconnecting HDD, Clear All Data, etc.

When I use the reset tool, I get the Japanese CE login screen (after [Stop] -> 00 [Stop] -> 01]) where the default password does not work (9272 four times, 12345678 etc). If I restart the machine in trouble reset mode the English CE Menu comes up where I can enter the CE menu with default password and gain access.

[tsbservice]

Thank you for all the input. I have run the reset tool (A145FW.TAR) thrice as suggested and it now comes back to the D390 error (which had happened before as well). If I click on recover data it goes back to the same 4 shark fins / bars with orange light blinking.

Since the battery had gone dead Jotunn's explanation regarding the NVRAM to eMMC data backup being corrupted makes the most sense. I have also tried disconnecting HDD, Clear All Data, etc.

When I use the reset tool, I get the Japanese CE login screen (after [Stop] -> 00 [Stop] -> 01]) where the default password does not work (9272 four times, 12345678 etc). If I restart the machine in trouble reset mode the English CE Menu comes up where I can enter the CE menu with default password and gain access.

I would replace SSDB with new one.

[Duplicator]

Thank you for all the input. I have run the reset tool (A145FW.TAR) thrice as suggested and it now comes back to the D390 error (which had happened before as well). If I click on recover data it goes back to the same 4 shark fins / bars with orange light blinking.

Since the battery had gone dead Jotunn's explanation regarding the NVRAM to eMMC data backup being corrupted makes the most sense. I have also tried disconnecting HDD, Clear All Data, etc.

When I use the reset tool, I get the Japanese CE login screen (after [Stop] -> 00 [Stop] -> 01]) where the default password does not work (9272 four times, 12345678 etc). If I restart the machine in trouble reset mode the English CE Menu comes up where I can enter the CE menu with default password and gain access.

Oh good an easier problem we can fix! C-D390 is the settings mismatch error. It tries to match the settings (NVRAM) on the EEPROM to the backup on the SSD. If the SSD copy is corrupt when you click recover data it will dump it back in. At this point we need to run the reset tool and replace the SSD one after the other. You should end up with a blank NVRAM and a blank SSD. You will need a copy of the firmware on a flash drive to restore the firmware onto the SSD.