Pi6500Pro gone deaf

[jsolo]

Our Fiery Pi6500pro / Minolta Di650 has stopped receiving jobs from the lan. The Pi6500pro just sits there idle with a solid green status light. The network router sees the pi6500pro and has given it an ip. All of our workstations can ping the ip with zero losses. The Pi6500ip passes diagnostics and is confgured for tcp/ip on ethernet (we run windows xp pro & ethernet). But print jobs just time out at the workstations. This was all working fine together and then one morning it just stopped working. Has the Pi6500pro gone deaf? Our other network printers are all still working fine. I don't get it - don't know what to check next. Any suggestions?

Thanks.

[dudley]

I would guess that you probably are printing to port 9100 raw and the Fiery controller has port 9100 turned off. If you print out a configuration page it will list the network settings and I think port 9100 setting is under services. I don't do black and white copiers so not sure how to get the fiery to print the confige page on that copier but if you find the menu screen then print pages then configuration that should do it

[jsolo]

Thanks for the post. I'm unable to print any reports (configuration, fonts, etc.). The Pi6500pro displays a 'sending report' message and then seems to time out and then displays 'canceling rip job' The unit hangs up there - it'll cancel the same job for days - until its power cycled. All the time the Di650 panel displays the controller icon, controller at idle. At this point I'm suspecting corrupt software on the Pi6500pro. I have a set of Fiery x-3 cd's but I'm not sure about what to do next. Any input is welcome.

[dudley]

If you have command workstation loaded on a computer I would see if you can "clear server" under the 3rd tab (I think)at the top. This should kill any jobs. If you don't have command workstation then from the idle screen see if you can "run setup" and then scroll down till you get to clear server, toggle to yes then ok, the server will ask again then say ok and it will clear server and reboot.

Sounds like a corrupt print job.

[jsolo]

I do have Command Workstation on two pc's, and neither one of them can find or connect to the Pi6500pro either via 'find' or inputting the ip (although both can connect to our Fiery S-300/C500). At the Pi6500pro, I got to 'clear server' first thing this morning and eight hours later it's still clearing the server. This thing needs a lobotomy!

[dudley]

I would have to agree, time for a reload but unfortunately I haven't dealt with version of Fiery so I can't give you the reload procedure. It may also be time for a new drive as it may have bad sectors.

[jsolo]

OK. Thanks much!

Would appreciate any help on reloading the firmware from the community...

[Sean486]

Unfortunately you have a hard Fiery to reload. It has been a while since I have done one of these but this is how I remember it.

You have to get the system software and copy it to the root of the C: drive. There will be a boot file and a sys file. Then you have to connect to it using a Parallel cable. Set the Fiery driver to Lpt1 and make it the default printer, making sure that there are no other devices on LPT1. Then power off the controller. Open a DOS window and type in copy /b filename lpt1. You do the boot file 1st. As soon as you send the file power on the controller. It think it is simply done by the copiers main power switch. It will spool the file to the controller forcing a service boot, follow the menus for loading the software. The menu will take you to point where it is waiting for input from the parallel port. Go to your DOS window and do the Copy /b filename lpt1 (this time sending the system code file) and it will go into a load sequence, after about 45 minutes it will be ready. Unless your HDD went bad, in which case it won't reload. If that is the case replace the HDD with a laptop sized ide HDD then try the procedure again.

I might be able find documentation on it if you need it.