Sc-390 on gestentner DSM 620d
Collapse
X
-
pradeesh001
Comment
-
Re: Sc-390 on gestentner DSM 620d
Well, as you didn't have the fault before you started but you did afterwards, I'd go with an original drum, blade and replacing the dev again, just to rule all of that out.
I'd like to add that we use compatible drums and blades for these machines too, so I'm not having a pop about that!Comment
-
Re: Sc-390 on gestentner DSM 620d
Alright this is all i did .starting from binging customer call for machine was making noise .i went out and saw the gearing system in dv assembly was bad that was causing the noise and making light copies .we replace all five gear and developer . and then machine start popping the Sc390 code .then we replace TD sensor .it still popping the same code .i took the whole drum assembly to an other machine it is popping the same code there as well .if someone has any info about this issue please share what might be causing this.
any information will be appreciated
thanks a lot guysComment
-
pradeesh001
Re: Sc-390 on gestentner DSM 620d
Causes of sc-390
* lack of developer quantity
* if agitators are not rotating properly
* td sensor or sensor connector
* td sensor connecting jack on machine
* mother board
but in your case pls check first 3 reasons
regards
pradeeshComment
-
Re: Sc-390 on gestentner DSM 620d
It sounds like the PCU's just had it. They do expire after a while.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.Comment
-
Re: Sc-390 on gestentner DSM 620d
i meet this threat in aficio 1022 the image have back ground very dirty... first i make free run 100 copies i suspect in toner i exhausted all toner until t toner signal appear i realized that vt and vts is 0 and when i make dev initialization sc 390 appeared .then switch machine on. sc 390 will dis appear . then yo will get faint image make required maintenance image will be fine...Comment
-
Re: Sc-390 on gestentner DSM 620d
we encountered this problem and symptom with the same model. we isolated the problem by replacing the developer, initialized it without the toner cartridge. made a copy until the machine asked for toner.Then we inserted the old duplicate toner. When the toner is already loaded we copied some documents but then Error SC 390 pops. So you have to make sure when you change the developer don't use that old toner replace it with orig. As you have said, you tried the pcu on another machine but the same problem so it means the culprit is inside the dev't unit.This is an issue of developer and toner.Nobody is perfect..Comment
Comment