Timing on the paper feed assembly (Konica 7145 copier)

[eurosears]

So, basically you are saying, it is not necessary to clean the toner supply unit when adding new developer and doing the l-detect?

[copytechman]

Not for me it hasn't been as of yet..
A.

[eurosears]

Before changing the developer I run another L-detect check using the new sensor but the old developer/toner mix. The L-detect started running but then I got error 0005. Should I worry about it or is it the old developer/toner mix that's throwing it off? I ran two consecutive L-detect procedures successfully using the old sensor but the same developer/toner mixture.

I changed back to the old sensor (didn't change the developer yet) and now I have 0006. I though that maybe the sensor on the drum is dirty (again?) but then when I took out the drum it was all black. This may have something to do with the fact that I just cleaned the corona. So now I am getting the 26-1 error, maybe because the auto toner supply has not delivered enough toner into the developer.

Can you tell me the switch to turn off any 26 codes so that I can run a few copies to clean the drum a little?
Thank you

UPDATE: Ok, I removed the old sensor and put the new one back in and it ran, I made a few copies and tuned off the copier. I don't what was wrong, software glitch? I turned the copier on and I ran the L-detect, it ran for a while and then game me error 0005 (still using old developer/toner mixture). So how do I deal with this error? Based on what I have learned this error indicates bad developer. So this makes sense, should I just ignore it before changing the developer?. BTW how can I print a page of all the error codes I may be getting while doing L-detect. I can see only 0005 now
SHould I change the developer now or run/test more things? I promised myself that if the developer change is not going to work the copier is going to be disassembled

[copytechman]

Run the l-detect with the new dev and tds sensor and t-shoot from there.. you need a good starting point.

Regards!
A.

[eurosears]

So you think that the 0005 error is related to the bad developer?

[copytechman]

Or worn developer, yes.

A.

[eurosears]

Ok, I did add the new developer and I ran the L-detect, it came out OK, value was at 66.
Now, when I did that I had the switch for Ldetect turned off (16-3 I believe).
After, this I also reseted the counter for the developer and turn on the switch for L-detect
WHen I started the printed it tells me please adjust L detect
WHat's this, I just did that. Should I just turn off this message using a switch?
I haven't made any copies yet.

[copytechman]

Based on what I have read about that soft sw, I think it should have been turned back on before running the l-detect. It might be too late now but maybe not... try running the l-detect again with that message displayed.. and see if it goes away on it's own or not.. I think it should.. Otherwise I guess you'll have to turn it back off again.. I've not ever changed the default state of that switch. But my understanding is that if you run l-detect with it displayed it should go away by running the l-detect.... others can chime in if i'm wrong..

Regards.
A.

[eurosears]

But I ran the L detect already once. Is it again to run it once more? It's true that I haven't done any copies, but didn't toner already mix with the developer?
Have you ever run l detect twice on new developer and you got the same value (e.g., 66) at the end?

Also, maybe I can just turn that message off using that 16-3 swtich. Will this affect the operation of my copier or not. If not, that maybe better not to do that second l detect and just turn off the L detect message?

[minimerlin]

Ok, I did add the new developer and I ran the L-detect, it came out OK, value was at 66.
Now, when I did that I had the switch for Ldetect turned off (16-3 I believe).
After, this I also reseted the counter for the developer and turn on the switch for L-detect
WHen I started the printed it tells me please adjust L detect
WHat's this, I just did that. Should I just turn off this message using a switch?
I haven't made any copies yet.

You must reset the developer count BEFORE you do the L detect adjust.

[eurosears]

SHut, I did that after.
Do you think I can do another l detect safely since I haven't made any copies yet or is the developer mixed with toner already?
What about just turning off the 16-3 switch?

[pepper38_cnd]

It does not matter about the counter the real Developer counter the one that shows up on page 1 of management list is reset when L Detect is performed, like I said in a previous post in a different thread you should not have messed with soft switches you knew you had a bad TDS you should have just replaced it along with the developer and been OK. Having said that, put all the switches you have messed with back to factory settings. If you have not made any prints. Reboot the machine, if you get an error code power off and boot into 36 mode and do L Detect, if you don't get a code enter service mode the soft way and do L Detect. If you haven't totally messed up the toner system with your other attempts, you may be OK, but I wouldn't bet any money on it. If you have already made prints, then I hope you bought more than one package of developer...

[eurosears]

Well, the toner entered the developer during the l detect so I decided not to do it again.
I turned off the L detect for now using the switch and I will make as many copies as I can before changing the developer (do you guys think I may run into problems with toner auto supply again>?)
It appears though that the copier is fixed. No errors anymore so that a good sign.
I wish I knew I had to turn on the switch and to do the counter reset before the L detect but, well, I guess it is part of the learning process.

The only thing is that I still have the lines on the drum which mostly disappear with the second consecutive copy. However, when I turn the copier on the drum is almost completely covered with toner and have to do like 4 copies to clean that up. Any hints? I cleaned the corona very well and that didn't change a thing. I think it may have something to do with my cleaning that toner sensor on the drum last time. I cleaned the area across the blade, so I wonder if that's it. Will these lines disappear with time (after some toner settles in that area that I cleaned before)?
Any other hints?

[copytechman]

Hard to say, @ this point IF the drum is still ok then I'd likely replace the corona wires and clean the grid.. Sometimes just cleaning the wires isn't enough.

Regards.
A.

[eurosears]

Thanx for all the help guys, looks like the copier works ok. Once I get the developer I will change it in the correct way. For now, I will make copies and see what happens.