taskalfa 3500i jam 0000

[Venom]

Re: taskalfa 3500i jam 0000

Those are the same bad exit sensors as used on the f4's....try using the exit sensor for the f3's and it won't fail again

[printerguy77]

Re: taskalfa 3500i jam 0000

Those are the same bad exit sensors as used on the f4's....try using the exit sensor for the f3's and it won't fail again

Hi All sorry to jump in on this thread. i am having the same issue with the Olivetti equivalent of the task alfa 3500i. it is stuck in the J0000 and it will not clear. my engineer in belfast has been fault finding this all day and i have to go and look tomorrow to try and help him. cant print off the jam history list as it is stuck on this code. and i think he may have cleared the history log anyway....( i kNOw)
should i be looking at these exit sensors first. i have been told replacing the fuser may help my cause so i am bringing one with me..

any help greatly appreciated

colin

[genesistech]

Re: taskalfa 3500i jam 0000

As you probably already know, J0000 is a non-specific jam, indicating paper present at power On. It does not indicate a specific location, just that paper was present somewhere at power On.

Usually, if a person were to print off the jam log they would see that preceding the J0000 there is a paper jam that occurred with a different code, a code that the person could look up then identify the original jam. That same person might notice that there was an error condition that occurred just before the J0000. But that person would not have that information if they fibbed about printing off the event log because they didn't know how.

J0000 is a consequence of power being turned off with jammed paper left in the machine, not a cause. From what you've said, the only thing we know for sure, is that your enduser powers off the machine each time the jam or error occurs. If you really want help, swallow your pride and go print the event log. =^..^=

:: I'm bumping this thread in hopes that someone has received updated information about this error. ::

So far, we've been to the site three times for the same issue and just got another call this morning for the same issue. This is a random error that occurs in between 2 to 160 pages thus far. The only other code on the event log is a 9610 which was well over 10k pages ago and only applies to the DP.

We have cleaned all rollers available, checked all sensors, and updated the firmware. We've checked for possible solutions from everyone's advice on this thread (such as power problems, the exit job separator being the only active switch, etc...) and we are still getting this random j0000.

Exact details as I can remember:
j0000 paper jam pops up randomly during printing or receiving faxes, not on initial power up.
There has not been paper found in any jam since j0000 besides the one below.
At an attempt to find the issue, I sent a fax and canceled immediately in order to send paper to the fax tray. Paper jammed and I got a j4713 error, but once the paper was pulled and door closed, we got the j0000 error immediately afterwards. Seemed like a false alarm but maybe that helps.
There is no dehumidifier and the lady at the front desk keeps a heater by her feet which is near the printer. Humidity seemed to be a semi-logical answer to the error, until we realized how random the errors occurred. (From in between every 2 pages to 160 pages and anywhere from 8:00am to 6:00pm.)

I can't think of anything else. But if you have questions or need more info before you can provide an answer please feel free to ask. ANY help on this issue would be greatly appreciated. Thank you for your time.

[taskalfaman]

Re: taskalfa 3500i jam 0000

HI ALL,

problem should be solved by exchanging the exit unit by a brand new one.

have fun

[allan]

Re: taskalfa 3500i jam 0000

And Blackcat freaked the begesus out of the original poster. Hehe funny as hell! Worked on those for about a year new machines only 3500i did not ever had any trouble with them except for feed tyres getting used up. Love Konica Minolta machines but have to say KM makes a mean machine. Would like to see a copy of an event log tho.

[taskalfaman]

Re: taskalfa 3500i jam 0000

And Blackcat freaked the begesus out of the original poster. Hehe funny as hell! Worked on those for about a year new machines only 3500i did not ever had any trouble with them except for feed tyres getting used up. Love Konica Minolta machines but have to say KM makes a mean machine. Would like to see a copy of an event log tho.

everyting can happen.
Suggesting KonMin has Pm to PM!!!!!
let's laugh around the world, please check another forum.

most tech coming from other brands will tell you KM is ok!!!



think positive!

[genesistech]

Re: taskalfa 3500i jam 0000

And Blackcat freaked the begesus out of the original poster. Hehe funny as hell! Worked on those for about a year new machines only 3500i did not ever had any trouble with them except for feed tyres getting used up. Love Konica Minolta machines but have to say KM makes a mean machine. Would like to see a copy of an event log tho.

Here's a copy of the Event Log as requested.

Event Log.pdf

[blackcat4866]

Re: taskalfa 3500i jam 0000

The thing to do, is to get the machine into the J0000 condition, then (if possible) enter service mode U031 sensor check, to see which sensor doesn't change state. It's fully possible that the J0000 is really just an engine PWB logic lockup.

The case I had was an Alphard II, and the J0000 would not clear. It turned out to be a poorly fitted connector to the back of the right door modular connector-machine side. The harness was about 10mm too short to plug in properly.

Another possibility is that electric heater overloading the circuit. Bring along your power quality analyzer, and make sure the heater and MFP are On during your snapshot.

I've seen an unexpected frequency of failed Sharp "73" photointerrupters. And it's not always in the hot areas near the fuser. I don't have an adequate explanation for all the failed sensors.

[genesistech]

Re: taskalfa 3500i jam 0000

Thank you for the quick replies. I think Blackcat nailed it with the heater next to the copier in the same surge protector. Time will tell. Thanks again all!

[genesistech]

Re: taskalfa 3500i jam 0000

Update : (Looking for any new ideas here)

We removed the space heater from the environment and switched out the surge protector to negate the power issue. Still getting Jam Code 0000.

When started inspecting the fuser with more detail since the J0000 always points us to the A1 gate on the fuser. On closer inspection, realized that the gate was getting stuck and decided to order a new fuser. Installed and tested, left it and before we got back to the shop the error had popped again.

Since customers were now irate, removed the unit and replaced with a loaner. Started running hundreds of prints without replicating the error. Decided to plug it on the network and the error code popped immediately. Didn't even have time to change IP or install, just plugged it in and error. Couple of things to consider:

When we plugged it into the network, we were in low power mode.
Now, the error code will not clear, whereas it was easily removed previously.

We've tried U906, reboots, and leaving it off for several minutes.
Removing and replacing fuser.
Checked all connections on the main PWB.

If anyone has any suggestions or leads to what is causing the error or how to permanently remove the error, please let me know. I know it's a stretch but we're trying to avoid replacing the main PWB immediately. Thank you in advance for taking the time to read and respond.

[allan]

Re: taskalfa 3500i jam 0000

Here's a copy of the Event Log as requested.

[ATTACH]27645[/ATTACH]

Thanks that looks like a happy machine.

[allan]

Re: taskalfa 3500i jam 0000

everyting can happen.
Suggesting KonMin has Pm to PM!!!!!
let's laugh around the world, please check another forum.

most tech coming from other brands will tell you KM is ok!!!



think positive!

Go back to the post and read again. That was a compliment to KM.

[genesistech]

Re: taskalfa 3500i jam 0000

I wanted to give an update to this thread since it seems that we have finally solved the issue. Hopefully this helps someone in the future if they happen across this same issue.

After digging through the machine and tearing it nearly completely down, we went back to the low power instance. Once we finally got the jam code to clear, we put it in low power mode and turned it back on to find the error pop immediately. Going back to issues with the fuser and exit area, we considered the fact that a sensor was not getting enough power when turning back on.

So after tearing out the whole exit unit and switching out sensors, we finally found it to be the exit feed sensor (exact part: sensor opt, part #: NX115300). That little guy has caused me weeks of trouble and I wanted to make sure that I gave it a couple of days before confirming on here that we finally found the culprit.

Thanks for all the help and advice, and good luck to anyone else with these troublesome code 0000's!

[blackcat4866]

Re: taskalfa 3500i jam 0000

Congratulations on your success. =^..^=

[buzz]

Re: taskalfa 3500i jam 0000

I wanted to add to this in the event someone may have a similar issue.

I had a customer with a 3550ci, for weeks been giving Jam error 0000. Customer said they would reset by opening and closing the conveying door.

Upon arrival I reset the machine, made copies, and voila, a J0000 appeared.

Found MPT Feed Jam Sensor (MPFS) part number: 7NXGP1A173LCH01 always enabled in U031.

I pulled the same photosensor off of a 6500i MPT assy and it solved the issue.