Xerox Color 560 Fiery Crashing/Disconnecting

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Caffeine
    Trusted Tech

    Site Contributor
    250+ Posts
    • Feb 2008
    • 382

    Xerox Color 560 Fiery Crashing/Disconnecting

    Can anyone confirm that they have used, or know of, printers from the Xerox 560/570 series (with the newer B3G Fiery controller) being successfully used for long production runs successfully?

    I'm testing a 560 now, and like I mentioned, it has the newer B3G bustled Fiery, not the original that came with the 550/560.

    The print job I am testing is a 324 page color 8.5 x 11 project, but it always freezes up and stops after about 10 copies. There is no solution but to power-off-power-on. The Fiery seems to be disconnecting and I get a 127-211 error code. (Several other Xerox Fiery controlled machines have no difficulty with this project and just chug away for hours and hours non-stop happily inhaling toner like the gold dust that it basically is.)

    In my research, I've found this issue quite a bit, on a lot of different Fiery's, not just the B3G, but as I understand it, EFI usually produces a patch to correct it.

    The B3G has TWO patches in its history to address "Intermittent Fiery Disconnection" issues. But I'm still having it.

    So far I've:

    - Reinstalled the Fiery software v1.0_SP3 from scratch (the latest for this Fiery) and installed all patches, including the two for "disconnection issues" in the correct order (man that takes forever)
    - Reloaded software and reset appropriate NVM on the machine itself
    - Cleaned the contacts on the video board in the Fiery as well as the memory, and on both ends of the SCSI cable, and also swapped the SCSI cable with another working machine
    - Swapped the crossover cable with a known good one

    What I haven't tried yet:

    - Removing the main controller from the machine and cleaning the contacts on the video board there, but as it always consistantly dies on the 10th copy, I don't feel like this is a random dirty contact issue, but a software issue/bug.
    - Played with setting like printing back-to-front instead of front-to-back, etc... This often helped on older machines if there was a software "bug" or limited memory but I've not typically had this help with Fiery's.

    If anyone has any advice, that would be most welcome. This is very frustrating and ruins the 560/570 for production purposes if this is a common problem. I feel like I've tried all the usual things, and nothing has worked, so my last hope, I guess, is that it is just "something with this file" and not something I would bump into on other jobs. Unfortunately, this is the only job I can test with at the moment. However, usually when the file is the problem, due to a poorly created PDF or something, it usually doesn't work at all. It doesn't RIP successfully, print 10 copies successfully, THEN crash... haha

    Thanks very much!

    Ken
  • adriansto
    Service Manager

    Site Contributor
    VIP Subscriber
    1,000+ Posts
    • Nov 2007
    • 2329

    #2
    Re: Xerox Color 560 Fiery Crashing/Disconnecting

    Did you tried another version for machine software ?

    Comment

    • Caffeine
      Trusted Tech

      Site Contributor
      250+ Posts
      • Feb 2008
      • 382

      #3
      Re: Xerox Color 560 Fiery Crashing/Disconnecting

      Originally posted by adriansto
      Did you tried another version for machine software ?
      Part of my initial "attempts" was to update to the latest machine software. So I did that. I'm not sure how to "downgrade" on these machines, if they is something that would even be a good idea, as they don't have an AltBoot method. I'd rather use the latest version unless there is a known problem with it. I'm at 55.42.73.

      I'm pretty sure the problem is in the Fiery software, though. Sometimes, when it stops printing, on copy 10 of this particular job always, the Fiery completely crashes. Can't load WebTools or access through CWS or anything. Not positive, but that it is in the Fiery is my song suspicion.

      Comment

      Working...