Have 5500 with fiery giving intermittent F9-00 code, a communication error between fiery and copier. The problem is intermittent. So far I have updated the Fiery OS to latest version also the copier has been updated to latest firmware version....... new interface cable between the 2, new interface card in fiery, new MFP board on copier ..... etc etc Has anyone heard of this.... Contacted Sharp support and was simple told we will look into it for you....never heard anything back......
-
-
Welcome to my nightmare. I too have many C-Dragons in the field with Fiery's, and have had a few calls for F9-00.
No-one has come to any fix for it, but to let you know, I have replaced the HDD's on some of them, and the issue never returned. I think you have gone abit overboard with the MFP & Fiery card, but it was worth a shot I suppose. Here in Australia, there are no PEX patches for that code, so it cannot be software related.
I'd change the HDD in the Fiery as next thing to try.
Good luck. -
The reason why I tried a new HDD, was on the Whale machines, the same code was usually caused by a faulty HDD or print controller board. Mostly the HDD fixed the issue immediately, so that was my main reasoning behind a new HDD in the PEX unit.
Just in case you wanted to know.
Comment
-
I'm not very familiar with the Sharp brand of copiers, but I do know Fiery's quite well.
I have seen a similar issue on another brand of copier with a Fiery attached and the problem boiled down to unused protocols being left on in the Fiery system.
If you aren't using AppleTalk (and you don't need to with the introduction of Mac OSX) then turn that off as this is usually the offender.
Like I said, not familiar with the Sharps, but thought this info might help as there is no requirement of changing parts.Please don't ask me for firmware or service manuals as refusal often offends.Comment
-
Thanx Owl, didnt know that one. As I am mainly a hardware tech, I usually dont play around with those settings unless required. Its good to know. I'll try it out next time.
Cheers mate.Comment
-
Hello All
Thanks for the tips as I am returning to the site tomorrow. It's a 889km or 554 mile trip to the remote location and I have armed myself with any/all parts that may be required. Including the hard drive mentioned and will let you guys know of the out come. It's a bitch as it may happen once or twice a week.Comment
-
Thanks for all the info guys. I replaced the HDD re-uped the software and turned of any unused protocols and the machine has not thrown the code since. It turned out to the HDD as I have tested on another machine in our showroom since and the intermittent code followed the drive.Comment
-
Haha, I knew it
.
sweet bro.... nice fix.Comment
Comment