Hello all,
Any bit of information or help is greatly appreciated!
I have inherited a (previously working) Docucolor 242 w/ Bustled Fiery X3eTY controller (self contained unit hanging off back of copier) Part No 45057733 / ERB087880
When I first set up the printer I had network scanning working fine, printing from windows clients via AD PS, etc. However one day it just stopped scanning (scan would complete but file would never make it to shared folder on smb share). After troubleshooting and making sure all patches were applied, still nothing. So i grabbed my trusty crash cart and off I went to boot up the Fiery and see what she loads into. Well low and behold with the DIP switches in their "DOWN" (read 0) position she posts just fine (00 on the diag readout) then hangs during "Unpacking Linux Kernel".
After doing some more troubleshooting (RAM swap/reseat, CMOS reset, gentle words of encouragement) I did notice a ruptured cap on the MB. The implications of this, anyones guess, however, she is posting so...
Next thought was ok I will reload the system software (I have the 3 CDs that came with the machine, System Software v2.0), well rather than overwriting the HDD I threw in a new one (BIOS recognized it fine), hooked up my crossover to my testing laptop and the fiery and the installer times out as the fiery never responds.
Now for the questions:
1) Is there a specific ip range the fiery is looking at to find laptop, right now it is just auto-assigning an ip in the private range (169.254.x.x/16), the installer knew I was using a crossover bc I tried a thru cable and it said no dice, use a crossover
2) The actual Fiery (PCI wanna-be?) interface card seems to be fine, the chipset is :60161A DE82 V3.0 10/06/08 P", part no 45055230. I have a beat on a whole new OEM Fiery bustled box, but it is for a Konica Minolta (part no A006212 EFI P/N 45052786 listed as "IC-406/FIERY X3eTY 30C -KM US/EUR" and they only want $50 for it. That is cheaper than I could have the motherboard cap replaced for IF I could swap out the interface card and reformat the HDD/reload the Docucolor system software from my CDs. Is this plan feasible?
3) Does the Fiery need to be connected to the copier to loaded the system software? I feel like there is some troubleshooting I am missing here. One thing to mention is right now the Fiery is on my bench, would this cause the hang in loading? When I was first troubleshooting and doing update I remember taking the crash cart to the copier and still receiving the hang, however I would need to hook it up again to be sure.
4) I have made the assumption that the system software is an embedded package, ie standalone (Linux based on what is on there now) application that will load onto the Fiery HDD. Is this accurate? I assume so since the CD is trying to emulate an ethernet boot environment.
Any help/guidance would be greatly appreciated as when the unit was working, it worked great! We are getting by on some older hardware in the interim, but the 242 is so much faster! I dont have a huge budget and there is no service agreement on the machine either. (Mgt doesn't want to spend the money unless we know its worthwhile/ie working!).
Thanks in advance,
-Aaron