Bizhub 252 Ethernet Cable Error

[Bionic711]

I have recently acquired a new client who has had a Bizhub 252 for almost 3 years (they say). They have never been able to have it plugged in to do IP printing, faxing and everything else the machine is capable of doing.

this is because of a constant error code that seems to pop up every 5min 36 seconds after the machine is plugged into the Ethernet cable.

The error code displayed is as follows:

!*! ABORT !*!
code = 0x0000999a
tskname = tLPD_0
tskid = 0xfffffff0
sp = 0x28e0e1f0
build = ??? 090126

??? = something missing due to glare from the pic I took.

Shortly after the error code is displayed the machine starts a warm reboot which takes about 3 minutes.

While booted and plugged in:
Faxes, copies, prints fine like nothing is wrong.
Using PCL type language for IP printing
Static IP address assigned

I've ran different lines to switches, crossovers to computers, straight to the router. It does not matter what is plugged into the other end, as soon as something is on the line the error code cycle starts.

One of the Konica guys they have had come in before refuses to return my calls and I have no idea how to get this working. I'm pretty sure it's an error referring to something in the Flash or maybe troubled RAM but looking for some feedback to bring to a different Konica guy.

[copytechman]

Ok did you try this? Crossover cable to isolated laptop? Turning off all unneccessary protocols? Checking to see that no other print drivers are printing to that ip and causing the machine to have a brain embolism?

Regards!
A.

[JR2ALTA]

You either have an IP conflict. If so, ping the IP address -t and turn off the machine to see if you see get a reply.

In command prompt ping 192.168.1.x -t

-t simply pings the machine forever until you close the command prompt.


Or you have a Windows 7 PC. The copier is re-queueing a corrupt job. I don't know the answer to this yet. Windows 7 has odd problems with Konicas.

Before the error occurs do you see a "XX-POP-XX" icon on the bottom right of the touch panel?

I've seen machines set up with POP credentials, where the machine tries to accept incoming emails causes a malfunction

[Bionic711]

Try about 22 Win 7 machines.

Definitely not an IP address conflict, I can assure you of that. In addition, the server would pick up on the conflict and report it as a result of the arp table. So I can very well rule that out, as well as say that I personally configured the entire IP addressing scheme when I took over to correct a few issues that were in place before hand.

Any way to eliminate the corrupt job from the Konica's spooler? I saw no function on that.

Did not notice a "XX-POP-XX" message before the error, and I specifically turned off the pop email functions as well as the fax functions in order to troubleshoot the device.

I've tried the crossover idea also and still has the same error which places the error on the machine itself rather than something connected to the network.

[emujo]

I believe you mean a C252, if so does it have a Fiery attached? We would like to see the firmware versions of the MFP and the Fiery, if installed, also post the driver you are using, and version #.

MFP version can be printed out by selecting Utility/Counter..USER Settings..Printer settings..Print reports..Configuration page.

Fiery... Utility/Counter..Controller details..Print Pages...configuration.

Scan all this along with a screen print of the driver type and version# and upload all to this thread. There are some pretty smart people on here.. might be able to get you pointed in the right directions. Emujo

[Bionic711]

Fiery printer server? No. It's completely IP printing. I'll be back in their office on Friday so I will get the information about the driver and version number than and post it Friday night. Does the firmware version print with the config page?

Thanks for everyone's help in advance.

[emujo]

If you are a trained KM tech, print/scan and post the numbers from the manegment list..if not, the config page will give us the controller f/w and that should be enough to determine if you are out of date...As to the Fiery option..It could be mounted, but not turned on..easy enough way to tell is to take a look at the back of the MFP. If you see a box with a scuzzy connector running to the MFP then the Fiery is there. Might be easier if it's not...Emujo

[Bionic711]

Not a trained KM tech, but like I said the tech that installed the Bizhub they have not been able to get in contact with recently (the office workers say last 3 to 4 months. I will take a look to see if the Fiery is mounted if it is there on Friday when I head to their office.

Let you know then!

[copytechman]

As far as I know, abort codes are only one the black and white series of machines, notably the older dialta line, bh200-350 and 222-362. Otherwise you might be barking up the wrong tree. If it dies on a crossover cable, try changing the ip and then retry the crossover test (with new ip). Is it a BH250 or BH282? (a BHC252 is a colour box and doesnt do abort codes the last time I checked). What firmware is in it... the nic is attached to mfbs board on that model and would req replacement if the nic is found @ fault.

Regards!
A.

[mdavin]

Connect the machine to a laptop either via a cross over or switch, isolated from the network. If you get no abort codes than you know it is something on the network..If it still aborts than flash and update the f/w than possible swap the board. But I doubt it's a board issue.

There are a few scenarios I have found with abort codes.. One of the most common is the corrupt print spool what I found is when you print something, usually a web page that has a lot of characters the machine will abort if you are using LPR port settings but not on RAW.. If you use the cd to install the driver it is installed under LRP by default, change the port settings to RAW...
Usually when I go on a abort code service call there is always a computer on the network with a job in the queue for the machine, clearing the job gets the machine going changing the port settings seems to stop it from happening again...Another cause I have had is security port scanners will cause the machine to abort but I have only seen this twice.

So my suggestion is to verify your port settings for the installed print driver and change to RAW if need be.