Thanks: 0
Likes: 0
Dislikes: 0
One of our techs has this problem, it shows the wrench in the lower corner, but has no SC code associated with it.There are no SC's logged and no jams logged. The machine is working fine, just has this wrench. Reboot the machine, it goes away for a little while but comes back. Anybody seen this before?
Does the machine have any finisher on it? and does that work properly?
Yes, it has a finisher on it and it works properly.. like I said, everything is wortking great, just has this wrench with no message associated with it at all.Originally Posted by CableGuy
I'd try firmware first, just see if there's a gremlin somewhere. Then try a HDD format. Failing that, if you have the birth certificate, I'd do a memory all clear and re-input the non-default values to see if that clears it.
It's 106 miles to Chicago. We've got a full tank of gas, half a pack of cigarettes, it's dark and we're wearing sunglasses.
Hit it.
I'll have him try that. He was just hoping that someone else had seen this before and could say, yes, it's definitely this.
Not with something this mental. Closest I've had was an erroneous cover open alarm. Sorry!
It's 106 miles to Chicago. We've got a full tank of gas, half a pack of cigarettes, it's dark and we're wearing sunglasses.
Hit it.
Before this I would try rebooting then doing a colour reg check in user tools, this would indicate "Failed" and may generate the wrench if there's a line position error of some kind. Switch off auto MUSIC check and retest?
The machine seems to be carrying out some kind of check after a certain period, can he determine when? end of a run? certain number of copies?.
Does it happen when printing? If he unplugs the network cable and copies, does the fault occur? (DHCP?? / duplicate I.P??)
He could also try setting up the debug log, SP5757 / 5758 to see if this shows an error. We have had wrench / door open indications due to PSU faults.
I've this Somewhere, but can't remember! (J.S @RUK???)
......... " 3 mins later .......thinks"... The wrenchmark used to be abnormal ID sensor (dirty?) couldn't that simple, could it?
Reply With Quote
Bookmarks