Colorqube 9203 jams repeatedly in Areas 3a and 3b - sometimes restarts with all settings cleared

[Joe Arseneau]

I honestly can't answer, I don't really do hardware. If you could get a Service manual it would answer most if not all your questions.

[forzagp]

Hi, 

Thanks for your help.  I managed to get the firmware updated through ALTBOOT and am now just left with a 16-560-00 intermittent error that does not seem to impact the functionality of the machine.  

Could this be caused by a bad battery?  

I looked for a CR2032 battery and did not find one.  I did find a SNAPHAT battery (M4T28-BR12SH1) which I've ordered.  

Is the SNAPHAT battery the type of battery used for the SBC?  

Also, the battery directive document shows two of the SNAPHAT modules, I found one on a module inserted in the SBC.  Where is the other one?  Is there also a CR2032 battery somewhere?

Could this be causing the issue with the 16-560-00 error and the occasional reset to "out of the box"?

Also, when the machine goes to sleep mode, I noticed that the backlight for the LCD display is still dimly lit (but the screen is black) and that the backlight sometimes flickers.  What would cause that issue?  Everything wakes up fine if you touch the screen, but I'm wondering what might cause the flickering backlight.

Thanks

[Joe Arseneau]

Thanks.  In the way of context, I had previously updated to the same SBC SPAR version that I used for the altboot and it had completed successfully.  Would this mean that I used the right one? Yes

If so, should I try to altboot the same firmware again?  Yes, try another USB stick (Less than 8GB)

Also, after the altoot is complete and I press "0" as prompted on the sucessful completion notification page, does it take a long time to return to normal operation?  Less than 2 minutes is normal if you take the USB key out first

In other words, was the hour or so that I waited with a black screen not enough (the energy saver light was flashing the whole time).  More than enough time, something went wrong

Based on the above, should I try one more time with the same SBC firmware before going the CBC firmware route? Yes

Also, if I used the wrong firmware would it still give me the "Alboot sucess" screen? Yes

Is it common to have an issue after getting the altboot success screen? Not really, but it is one of the reasons ALTBOOTS are only to be done by trained technicians.

[forzagp]

Also, if I used the wrong firmware would it still give me the "Alboot sucess" screen?

Is it common to have an issue after getting the altboot success screen?

Thanks!

[forzagp]

Thanks.  In the way of context, I had previously updated to the same SBC SPAR version that I used for the altboot and it had completed successfully.  Would this mean that I used the right one?

If so, should I try to altboot the same firmware again?  

Also, after the altoot is complete and I press "0" as prompted on the sucessful completion notification page, does it take a long time to return to normal operation?  

In other words, was the hour or so that I waited with a black screen not enough (the energy saver light was flashing the whole time).

Based on the above, should I try one more time with the same SBC firmware before going the CBC firmware route?

Thanks for your help!

[Joe Arseneau]

It won't update an incorrect firmware, altboot isn't an update though.

Think of it this way, you can't update from Windows XP to Windows 10 directly (update)

You can put windows 10 on the same PC as was running Windows XP (altboot)

So one of 2 things occurred, it just didn't work, or you picked the wrong one.

So the first thing is to attempt another altboot using the other firmware, and if it fails too, you would try the first one again, and use a different flash drive.

[forzagp]

Hi,

I tried the altboot with the latest SPAR and the machine returned the "Altboot Complete - Please remove USB flash drive and press 0 on UI to continue".  I pressed 0 and the machine display kind of dimmed a bit and eventually went almost black (with a silhouette of the altboot complete screen).  I left it for an hour or so and it still wasn't doing anything so I turned it off and then back on.  

The machine now shows nothing on the display and the energy saver light is flashing.  Please let me know what may be the issue or what I should try.

I've been told that it will not load the wrong firmware, but I'm not absolutely certain I have the SBC and used the SBC firmware.  Please let me know if this would cause the issue or what else I should try for a fix.

Thank you.

[Joe Arseneau]

If you can get to it, just replace it, nothing special, typical CR2032.

16-560.0 would certainly not be caused by the same thing, assuming nothing is wrong hardware wise, the altboot would fix.

Clone files in these scenarios are really just a bad idea, they often will just break the system again because you effectively have cloned whatever is wrong in the current setup, go ahead and clone it, but after the altboot, wait a few days/hours and make sure the issue is resolved if possible, then if you decide to go ahead with the clone though, you would need to altboot again if it just goes back to broken.

ALTBOOT directions cannot be posted here as they are considered Xerox Internal Classification.

[forzagp]

Thank you!  I tried the firmware upgrade and the random reset to "out of box" config seems to have stopped.  Is there an error generated when the battery goes bad?  If not, should I replace the battery anyway?

I'm now getting an intermittent 16-560.0 error "Network Controller Error."   Would this be caused by the same thing?  Would the ALTBOOT fix this issue?

If I clone the settings before ALTBOOT would that save all the configurations so that the new set up would be quick and easy?

Do you have the part number for the CMOS battery?

Thanks for your help!

[Joe Arseneau]

Something in the very confined space is likely to be bent, or a dirty sensor. Can of compressed air, good eyesight and a bright flashlight would be the required tools.

CMOS could very well be the cause if it is more simplistic clearing, things like time/date, if it is extensive and essentially going back to out of the box configuration then it would have to be corrupted firmware, Linux (Custom Xerox build) doesn't wipe itself to defaults just because of a power outage CMOS battery or not.

You may get away with simply updating the firmware, but likely it would need to be wiped (called and ALTBOOT) by a technician.

Latest firmware for an SBC model (firmware starts with 061.080)

Latest firmware for a CBC model (firmware starts with 061.050)