Last week I upgraded a KM-3050 to 220C1 Firmware now I'm getting CF B31,B32,B33 & C0640. I cleaned and reinstalled the new white Dimm, formatted HDD and ran Scandisk. I did learn from the hotline that upgrading from USB only changes the files that had a change made to them, although when upgading from compact flash will overwright all files regardless and is a better way to go about fragmented firmware. Next I am going I am going to try compact flash formatted to FAT. Is there any known fixes for this lock-up\coding problem problem Thank's
Sky: i encounter this issue last week & i downgraded to older version then upgraded to the latest one and the problem went away.the entire procedure was done with a 1 gig cf card...good luck...
DUMMIETEK...keep blood pressure...117/72... This message has been edited. Last edited by: DUMMIETEK,
I did learn from the hotline that upgrading from USB only changes the files that had a change made to them, although when upgading from compact flash will overwright all files regardless and is a better way to go about fragmented firmware.
From what I've seen of the update scripts, updating firmware from CF and USB are nearly identical, only differing in the mount points. It doesn't look like the updater compares the versions of the current firmware and what is about to be written, either. All it does is verify the file exists, compare its checksum against what's in VERDEF, and a test copy before it writes it to flash.
I just updated a 5050 to 2.20C1 last week and haven't had any problems. Hopefully re-flashing firmware will fix it. C0640 is HDD problem while CFB30-32 are Panel Communication problems, so I'd probably try swapping the Panel flash DIMM next if you have one handy.
Posts: 227 | Location: hanford, ca | Registered: June 22, 2007
aragul, Interesting doing the firmware again in my case did not work, on Friday I'm doing both Dimm's & Main Brd Memory.If that does not work HDD. If I did not mention in my first post the first call was for locking up OP Panel, with that said the PDF with the firmware mentions a fix for panel lockup. I also had the thaught in the back of my head that the original Yellow Dimm became a problem because of size and fit, not the Dimm going bad my machine has white. But Dimm can be bad also and that is the direction the codes are pointing towards. Thank's for your post
Dimm did not work both OP. & Main. Firmware during install locks up also in the middle then times out and gives main Brd. error and the rest are incomplete. From my understanding I might be wrong again, but that excludes the HDD and memory. On Tuesday I'm doing Main PCB and I believe that comes with memory on it, and no Dimm so at that point I'll be down to one HDD. The customer hates me and I don't care more like me then don't.
I've got a 4050 giving me relentless CFB31 codes as well. goes through "program loading" but times out with a CFB31 code. Tried: main board, memory dimms, firmware dimms (both main and op panel), flashing firmware, downgrade firmware then upgrade again ALL TO NO AVAIL. I'm so sick of these Falcon III software problems! In the past, I would have arranged for a service loaner and got our Regional Tech rep out here to reconcile this problem... Now we don't get Factory support from Kyocera. I guess we'll have to eat the cost of a new SHARP to place here and let the customer have a bad impression of Kyocera! Seems to be the consensus of many of our customers that are having problems with Kyocera that we no longer get factory support for!!! Kyocera is shooting themselves in the foot if you ask me!
Dummie, Heading back there in just a minute with a new HD as a last stitch effort before arranging a service loaner and bringing their machine in. Problem is: I'm not sure what I can do with it here in my shop!
Skytshot, there is no fax system installed. I'll report back with any progress or lack thereof!
Gentlemen, Replacing the Hard Drive was the only other thing I could think of to try yesterday so I ordered it from Kyocera (now that we have another account set up with them) and requested Overnight delivery so I could try it today. I'm pleased to announce that it DID FIX THE PROBLEM!!! All is good in Greenville, SC.
congrats Dan great fix, i think...i wrote a post on this issue in the past regarding bad sectors on the HD triggering codes,thats why i decided to ask u. i feels good to know u got that one to bite the dust. great piece of work...
Thanks for the kudos but although I was able to frantically troubleshoot down to it on my own, I need to share the kudos with you since you did try to warn us in a previous post about the hard drives... I just never did come across that one until you just prompted me to look for it tonight. I did try searching for clues on this one a couple of days ago. but I couldn't find anything in DNET except for this thread (because I was search specifically for the CFB31 code). I wish I would have come across your post On hard drive being main problem before... I would have made sure we had them in stock. But I've already asked our Warehouse parts manager to keep one in stock after today!
Skyshot, I wouldn't rule out the main board you have, but my money would be on the HD. I wouldn't go until you had one. Take the main board too though... wouldn't hurt to have one on hand in case the HD doesn't fix.
Dan great info the problem troubleshooting this one - the codes don't point towards the HD directly rather the communication between main & HD "more so the main" commen sense would tell you if your getting CF B codes out the ass and only one C0640 you would point to main vrs. HD so it was a roll of the dice. I couldn't prove it with a meter, so it was an educated guess one I came to the conclusion with input from the hotline and my field rep.We got the customer a loaner on Friday and I as like you do not have the HD in stock. I'll know more tommorrow. On a side note I took off today for a 1 PM. appointment to have my oil tank Repl. they didn't get to my house till 4 PM and then the tank did not fit in the basement. Waste of a day! So if the customer gives me grief I'll just smile.Thank's for the help D-Net I don't think my oil company has a website like this.This message has been edited. Last edited by: Skyshot1,
Dan I did the main pcb today and everything looks good the firware went through with no lock ups or codes. When you did your main pcb did it lock-up and code right away or did it take a day or two? I'm thinking should I pull the loaner or let it stay till next week.
When my tech replaced the main board... it still coded right away. That's when I took over and started troubleshooting and tried all the rest of the aforementioned details. So between you and me, we can sufficiently speculate that either a main board or an HD can cause the exact side effects! Great... I'll have our parts manager be sure to keep a main board in stock as well. Anyone having this problem will need to take both parts with them in order to fix on the first visit.