if i understand correctly, you say that when changing the developer powder, the print are ok for 1000-2000 print?....you have do the developer initialization routine by sp?...if no, the machine back to old toner ratio concentration...anyway, check the toner supply clutch if stucked, replace the transfer belt with propely spare part (the 6503 have the belt different from martini C2!!!), clean well the drum ground assis, and try another entire corona wire unit, also from another machine.
check also the sc code stored in memory, to see eventualy shadow problem with ID, and TD sensor
check the attachment
Last edited by luca72; 09-19-2022 at 02:42 PM.
"loneliness is an invention of the white man, when we are alone we talk to everything around us, we are never alone" (Ojibwa)
Just a couple thoughts. Make sure you start the thing with door open after changing developer etc so it don't initialize. Then go through the dev initialization. Make sure your filters are new or clean, especially the intake filter on back. Next ideas are more expensive. The dev units get sloppy with wear after a couple million and blast out toner. Maybe that needs changing. You might also have something wrong with the ID sensor or drum charge sensor. Suggest you run pixel mode until you make a determination if either of these is bad.
I've proved mathematics wrong. 1 + 1 doesn't always equal 2.........
Especially when it comes to sex
I think the same comrade.
There is a lack of answer to the question and an image of the failure to prevent.
I find it too hasty that the Developer (possibly generic) has been changed 2 times... It is not so cheap as to discard so quickly without testing or adjusting the SP values.
"ALL WILL BE WELL" The battle cry that most inspires me to follow, from the DC's Comic character that I admire the most. And I feel satisfied with being better every day, and with using Gnu-Linux as my usual Operating System.Apologies for my English, it's not my mother tongue and I'm helping the translator.
I had this same problem recently and it was a fault caused by the toner and that was original. It would be a defective batch I imagine . I had to empty the toner hopper and change developer and run a sp2963 to initialize the developer and fill the hopper with another original toner from a different supplier and it worked. You have to enter service mode with the door open as previously tonerhead mentioned. Then I returned the defective toner, of course.
Come to think of it, we had same thing. Not sure if it was the case, but we sent some oem toner back as dictated by manufacturer as defective.
I've proved mathematics wrong. 1 + 1 doesn't always equal 2.........
Especially when it comes to sex
Bookmarks