Thanks: 0
Likes: 0
Dislikes: 0
Hey all
I have a KM3050 printing garble. I have gone and reloaded drivers, swopped network cables and plugged into another port. The client calls today and says its doing the same thing. Went back and updated firmware. A few hours later and the same thing happens.
Any thoughts?
cheers
How about other pc when send print to copier and how about try to use other file to send print ?Originally Posted by RTFM
I have seen where a machine will misfeed or jam and when the customer opens the doors and clears it, it prints garble when the doors are shut back.
Are there jams being registered. When that happens about all they can do is clear the print cue and start again. Of course you need to correct the source of the jamming.
"Some days you get the bear, some days the bear gets you."
Cdr. William Riker
Disable your fonts in your print drivers under printing preferances, close out go back in under advanced and double check under your imaging tabs that your disable held.
Like Pang said, I'd start by printing from my laptop. If that was successful I'd use one of the customers workstations and print to file, then send the file from my laptop. If I got garble then I'd know it was a driver or network issue. If it came out properly I'd say there was a network issue.
Could this be something as simple as PCL emulation selected in the driver, and KPDL selected on the printer? Or vice versa? I would go to the printer webpage and confirm that the emulation on the printer is set to Auto. The printer can then select the proper emulation itself.
If you'd like a serious answer to your request:
1) demonstrate that you've read the manual
2) demonstrate that you made some attempt to fix it.
3) if you're going to ask about jams include the jam code.
4) if you're going to ask about an error code include the error code.
5) You are the person onsite. Only you can make observations.
blackcat: Master Of The Obvious =^..^=
STILL GARBLE
Thanks for your quick response guys, and I have tried all of your ideas to no avail.
What I failed to mention is that the machine will start printing these garbled pages even though nobody has sent a print job.
What I have done now is to plug in my laptop via crossover and have the client printing from it using a usb stick.
If all is good then I can tell that the machine is o.k and trouble shoot the network. Make sense??
That sounds like a good start. Do these "phantom" print jobs show up in the print job log? That might give you some info. Is there a wireless router involved? Duplicate IP's? EMI? There's still lotsa variables.
Yep they do, and I have only one P.C. printing to it now. So I thought my laptop test would tell me if i'm having m/c issues.
No wireless and no duplicate IP's. As for EMI- cannot be sure, I found a noisy cooling fan but sorted that and there was a rattle on the back cover but fixed that as well, I know the KM6230's had that issue.
Again, I thought plugging in via crossover should cancel any variables....we shall see. Exciting Stuff! NOT!
Thanx for the input.
I've had something similar happen on HP LJ4200. The machine would either get a 49.xxxx code or a PostScript error everytime the machine was turned On. In this case there was a corrupt job stuck in the print queue that would just not go away. I advised the IT guy to stop the spooler and clear the print queue, then re-start the spooler.
Who knows where these corrupt print jobs come from...
I have personally created quite a few PostScript errors experimenting with scripts in the print jobs header. Often it take a few attempts to get the syntax just so.
If you'd like a serious answer to your request:
1) demonstrate that you've read the manual
2) demonstrate that you made some attempt to fix it.
3) if you're going to ask about jams include the jam code.
4) if you're going to ask about an error code include the error code.
5) You are the person onsite. Only you can make observations.
blackcat: Master Of The Obvious =^..^=
give the 3050 a new ip address set PDL to pcl5
than test it, this will insure you do not have someone sending print jobs with a different driver with the same ip address
Reply With Quote
Bookmarks