MP501 after running 100 copies it hesitates and is light or blank

[tonerhead]

Re: MP501 after running 100 copies it hesitates and is light or blank

I have never set up an mp501, but in the past I set up some of the kyocera equivalents. When you first set those up, the dev initialization is nearly 10 minutes. I remember setting up my first, 10 minutes had gone by and I was freaking out. I called our setup guy and he said that is normal. Maybe someone panicked early at setup. I'm not sure on the Ricoh version, but on the kyo version, if the dev setup didn't work the first time, you could run a second time and it would work. I would try to run an SP3900-1 at this point, it will not hurt anything. It says in manual that you are to run this anyway with a new dev unit. Kyo has a similar command in sims. On the kyo's I remember 1-2 times where initialization failed and you would just re-initialize again, then ok.

Kyo btw rates the drums at 300k. They are an A-Si drum (glass) very tough and durable. We had several kyos that ran past 300k easy.

[sandmanmac]

Re: MP501 after running 100 copies it hesitates and is light or blank

I have never set up an mp501, but in the past I set up some of the kyocera equivalents. When you first set those up, the dev initialization is nearly 10 minutes. I remember setting up my first, 10 minutes had gone by and I was freaking out. I called our setup guy and he said that is normal. Maybe someone panicked early at setup. I'm not sure on the Ricoh version, but on the kyo version, if the dev setup didn't work the first time, you could run a second time and it would work. I would try to run an SP3900-1 at this point, it will not hurt anything. It says in manual that you are to run this anyway with a new dev unit. Kyo has a similar command in sims. On the kyo's I remember 1-2 times where initialization failed and you would just re-initialize again, then ok.

Kyo btw rates the drums at 300k. They are an A-Si drum (glass) very tough and durable. We had several kyos that ran past 300k easy.

Thanks for the excellent info!

I think that I tried running that on the machine when I was last there - although not knowing what "toner Install mode" actually meant at the time.
I just did ran it on the (replacement) machine that I picked up for the customer. It seems to be the same as the 'add extra toner' option in user tools (on the Ricoh version at least) that I did run several times. It goes into the same 'loading toner' state for several minutes.

I plan on visiting them early next week to deliver the replacement machine, but I'll definitely give this a try first to see if there's any change and post the results.

Enjoy your weekend, all !!

[slimslob]

Re: MP501 after running 100 copies it hesitates and is light or blank

I have never set up an mp501, but in the past I set up some of the kyocera equivalents. When you first set those up, the dev initialization is nearly 10 minutes. I remember setting up my first, 10 minutes had gone by and I was freaking out. I called our setup guy and he said that is normal. Maybe someone panicked early at setup. I'm not sure on the Ricoh version, but on the kyo version, if the dev setup didn't work the first time, you could run a second time and it would work. I would try to run an SP3900-1 at this point, it will not hurt anything. It says in manual that you are to run this anyway with a new dev unit. Kyo has a similar command in sims. On the kyo's I remember 1-2 times where initialization failed and you would just re-initialize again, then ok.

Kyo btw rates the drums at 300k. They are an A-Si drum (glass) very tough and durable. We had several kyos that ran past 300k easy.

Reminds of the Init Toner Replenish: K) on the 04s. If you didn't do it correctly, you were asking for trouble. And then there was the Toner Bank Setup on the Pro1357 series. Basically priming the toner supply system.

[blackcat4866]

Re: MP501 after running 100 copies it hesitates and is light or blank

OK, now that I know model Kyocera Polaris (ECOSYS M3550cidn), I may be able to add a little:

These machines are monocomponent developing, and the developing unit comes empty, so the replenishing mode dumps about 1/3 of a cartridge of monocomponent toner directly into the developing unit. 10 to 15minutes is entirely normal for this process. It's very common to run out of toner during this process, and have to install another cartridge.

The toner sensor is on the left side of the developing unit. Is it possible that it was not correctly plugged into the DRPWB? The most likely explanation is that the connection is broken somewhere between the the TS and the Controller PWB.

toner_sensor_item7.jpg

The toner sensor (TS or TSENS) connects to the drum PWB (DRPWB), then to the C-LPWB (YC3-2), then to the CONPWB (YC2).

=^..^=

[sandmanmac]

Re: MP501 after running 100 copies it hesitates and is light or blank

The toner sensor is on the left side of the developing unit. Is it possible that it was not correctly plugged into the DRPWB? The most likely explanation is that the connection is broken somewhere between the the TS and the Controller PWB.

[ATTACH=CONFIG]52602[/ATTACH]

The toner sensor (TS or TSENS) connects to the drum PWB (DRPWB), then to the C-LPWB (YC3-2), then to the CONPWB (YC2).

=^..^=

Thanks for this info Cat. Helpful!
I did swap the entire drum unit, thinking there may be an issue with the connector board, but it made no difference.
Once I get it back here, I'll do a little deeper dive into it

[sandmanmac]

Re: MP501 after running 100 copies it hesitates and is light or blank

Well, I finally got around to spending some time on this trouble unit after replacing my clients box, and it's resolved. Finally!
Turns out it was the IOB board.
Again, there were absolutely no errors, the machine would not go low toner even when the dev tank ran empty.
After replacing the IOB, I disconnected the dev unit before rebooting, and my first sign of success was when the error came on the screen that the dev unit was not properly connected (That never happened before either).
Once I reconnected it, I ran the add additional toner in Maintenance mode to fill up the tank, and it fed the dev unit, and continues to do so.
It May be or may not be the problem that the original poster's machine has, but hopefully someone in the future can benefit from the suffering I've gone through with this unit.
Thanks for the tips along the way!