Thanks Thanks:  0
Likes Likes:  0
Dislikes Dislikes:  0
Results 1 to 9 of 9

Thread: Bizhub 500 B&W

  1. #1
    Trusted Tech 50+ Posts poz31's Avatar
    Join Date
    Aug 2006
    Posts
    87
    Rep Power
    36

    Question Bizhub 500 B&W

    I’m working on a Bizhub 500 B&W…. Replaced developer ‘cuase the developer was grey and copies were coming light….
    After the TCR adjustment the result was not good (NG) and started throwing C 2803
    (TCR output abnormality. When the output ripple voltage of the TCR sensor (TCRS) is less than 0.5 V)..
    Tried to reset (main Switch and utility) copier resets and goes back to the code c2803
    Is there another step to replaced developer?
    (Throw old, replace with new, ran TRC adjustment)????

    Any help on this problem?

  2. #2
    Senior Tech 250+ Posts
    Join Date
    Feb 2008
    Posts
    437
    Rep Power
    38
    I haven't done too many dev changes on this box yet. But, if memory serves me, a lot of techs have been saying this model is especially picky about doing a dev change without a drum at the same time. I know I've gotten it to work in the past without, but it sounds like it's a rare occurence in the field.

    Got a drum?

  3. #3
    Field Supervisor 500+ Posts
    Bizhub 500 B&W

    minimerlin's Avatar
    Join Date
    Nov 2007
    Location
    Scottish Highlands
    Posts
    851
    Rep Power
    44

    Question

    Quote Originally Posted by poz31 View Post
    I’m working on a Bizhub 500 B&W…. Replaced developer ‘cuase the developer was grey and copies were coming light….
    After the TCR adjustment the result was not good (NG) and started throwing C 2803
    (TCR output abnormality. When the output ripple voltage of the TCR sensor (TCRS) is less than 0.5 V)..
    Tried to reset (main Switch and utility) copier resets and goes back to the code c2803
    Is there another step to replaced developer?
    (Throw old, replace with new, ran TRC adjustment)????

    Any help on this problem?
    Did you by any chance vacum out the dev tank...with the sensor still in it? If you did it is toast!!
    Last edited by minimerlin; 09-29-2009 at 09:38 PM. Reason: quote went weird!

  4. #4
    ALIEN OVERLORD 2,500+ Posts fixthecopier's Avatar
    Join Date
    Apr 2008
    Location
    The Republic of Pineland
    Posts
    4,716
    Rep Power
    134
    If the drum had a large count, that could be part of the problem.
    The greatest enemy of knowledge isn't ignorance, it is the illusion of knowledge. Stephen Hawking

  5. #5
    Trusted Tech 50+ Posts HuronMan's Avatar
    Join Date
    Jul 2009
    Location
    Limbo
    Posts
    68
    Rep Power
    30
    Quote Originally Posted by minimerlin View Post
    Did you by any chance vacum out the dev tank...with the sensor still in it? If you did it is toast!!
    Had a tech call me the other day who did this. He popped the sensor vacuuming the unit. Take that thing off if ya need to vac.

  6. #6
    freefall
    Guest
    Were there any 2803s b4 the dev change ? If there were then the reason for the grey developer is that the toner bottle drive assy is screwed up . try output mode 56 sub 1 to see if the motor rotates . We've had 500s and 501s with bad toner bottles, dirty bottle position sensors and whole toner drive assys go bad. These units have awful toner drive units. Last week I replaced 2 myself. Goodluck

  7. #7
    Copy/Print/Network Tech 100+ Posts Kmdurrin's Avatar
    Join Date
    Dec 2008
    Location
    Missoula,MT
    Posts
    132
    Rep Power
    33
    Check the developer drive belt (it can come loose and throw this code when the agitator stops turning). I've also had this code when the M4 drive motor went bad.
    Parts: Its what your copier craves!

  8. #8
    Trusted Tech 50+ Posts poz31's Avatar
    Join Date
    Aug 2006
    Posts
    87
    Rep Power
    36
    OK…so finally I went back to this copier
    Before I did anything I checked up the developer unit…..I found that the actual developer was gone….
    Drum was clean…no toner or developer drop on the transport area……and developer was found on the cleaning area ( cleaning blade) all the way to the hopper tank…
    Mmmmm weird never have seen something like this especially since the developer was nowhere to be found but on the tonner hopper……….
    Weird indeed... The developer (not just toner) is been recycle ….
    That is probably why is throwing the TRC failure code….

    Now my question is what or why a developer is been transported to the toner hopper (as if it was toner)
    By the way last time a changed a new developer from a new bag….
    Any input will be appreciated

  9. #9
    Field Supervisor 500+ Posts
    Bizhub 500 B&W

    minimerlin's Avatar
    Join Date
    Nov 2007
    Location
    Scottish Highlands
    Posts
    851
    Rep Power
    44
    Sounds like you have a problem with bias/charge, dev is getting dragged over to the drum.

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Get the Android App
click or scan for the Copytechnet Mobile App

-= -= -= -= -=


IDrive Remote Backup

Lunarpages Internet Solutions

Advertise on Copytechnet

Your Link Here