Bizhub 200 C2557 after dev unit change.

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • wseyller
    Service Manager

    1,000+ Posts
    • Sep 2012
    • 1129

    #1

    Bizhub 200 C2557 after dev unit change.

    Error C2557. I changed the developer unit, developer, and the drum all at once. Counters cleared correctly. F8 I noticed was taking longer than usual and it didn't sound like it was doing much. Got C255C error.

    After trouble reset it always codes right away C2557

    On phone with KMBS rep. We tried different ATDC SET settings no luck. I notice that when running F8 the toner bottle doesn't turn.

    Only errors in service history is the C2557 (about 15 of them) and the C255C.

    KMBS rep recommended PWB-A board.

    Want to see what everyone's thoughts are. I am 100% sure I did the replace of these parts correctly as I have much experience doing these and know how picky they are.

    Some history: The drum I just replaced was at 20% when I arrived. I changed this drum and dev back in Feb when it coded C2557. A year before that I changed dev unit, dev, and drum after it had coded C2557.
  • Copier Addict
    Aging Tech

    Site Contributor
    10,000+ Posts
    • Jul 2013
    • 14628

    #2
    Re: Bizhub 200 C2557 after dev unit change.

    The first place I would start is an ATDC sensor. I know you said you replaced the dev unit, but it could still be bad. Then try the PWB-A.

    I have been working on these machines since they came out and last week was the first time I have experienced an issue doing an F-8. I cleared the counters, checked to make sure they had cleared, ran the F-8 and got a C-2557. I again checked the counters and the drum counter had magically gone back to it's pre-cleared state. I cleared it again, ran F-8 and all was well.
    I know this has nothing to do with your issue, I just thought I would share. lol

    Comment

    • wseyller
      Service Manager

      1,000+ Posts
      • Sep 2012
      • 1129

      #3
      Yes I always check the counter again before F8. I know the same issues.

      But let me ask. Would a bad sensor cause the bottle to never turn during F8. There are no other error codes listed.

      Sent from my DROID BIONIC using Tapatalk

      Comment

      • Copier Addict
        Aging Tech

        Site Contributor
        10,000+ Posts
        • Jul 2013
        • 14628

        #4
        Re: Bizhub 200 C2557 after dev unit change.

        As far as I know the bottle shouldn't turn during F-8. Plus, if the sub-hopper is already full, it doesn't need to turn.
        The dev comes with optimum t/c ratio so no toner is adding during an F-8

        Comment

        • wseyller
          Service Manager

          1,000+ Posts
          • Sep 2012
          • 1129

          #5
          Ah didn't realize it came that way.

          Sent from my DROID BIONIC using Tapatalk

          Comment

          • fixthecopier
            ALIEN OVERLORD

            2,500+ Posts
            • Apr 2008
            • 4713

            #6
            Re: Bizhub 200 C2557 after dev unit change.

            I wish you well. Last month i had a 350 that started doing that. We literally rebuilt the whole thing. Every board, hopper, erase lamp, power supply. Nothing worked. The machine was due to be replaced, and the new one was delivered while service manager was changing power supply. We sent it back to lease company, still broke. Would love to know what fixes it.
            The greatest enemy of knowledge isn't ignorance, it is the illusion of knowledge. Stephen Hawking

            Comment

            • Hansoon
              Field Supervisor

              Site Contributor
              2,500+ Posts
              • Sep 2007
              • 3380

              #7
              Re: Bizhub 200 C2557 after dev unit change.

              "
              Solution ID TAUS0808236EN* Solution Usage 0
              Description
              What can cause the machine to intermittently display a C-2557 code even after the Imaging Unit and PWB-A have been replaced?
              Solution
              The machinemay intermittently display a C-2557 code even after the Imaging Unit and PWB-A have been replaced if the cooling fan M5 is starting to fail.
              Please replace cooling fan M5 (p/n 9313-1100-33).
              SPECIAL NOTE: Solution contribution by Dave Bruni, Workgroup/SSD
              "

              Hans
              “Sent from my Intel 80286 using MS-DOS 2.0”

              Comment

              • wseyller
                Service Manager

                1,000+ Posts
                • Sep 2012
                • 1129

                #8
                Nice find Hansoon. That will be one of the parts I grab from a spare parts machine.

                Sent from my DROID BIONIC using Tapatalk

                Comment

                • rrrohan
                  Service Manager

                  Site Contributor
                  1,000+ Posts
                  • Sep 2011
                  • 1977

                  #9
                  Had this during training today. Techj didn't screw in the 2 screws after removing drum and dev

                  Comment

                  • EarthKmTech
                    Step aside, noob

                    1,000+ Posts
                    • May 2009
                    • 2139

                    #10
                    Re: Bizhub 200 C2557 after dev unit change.

                    Have you checked the toner adding solenoid as per my post;
                    http://www.copytechnet.com/forums/ko...highlight=2557

                    When it gets stuck open you will get 2557's intermittently as toner is added uncontrollably. Even if it isnt stuck open, operate it and see if the foam is sticky in the open position. if it does not release instantly you have a problem.

                    Comment

                    • wseyller
                      Service Manager

                      1,000+ Posts
                      • Sep 2012
                      • 1129

                      #11
                      OK I have it fixed I believe. I tried a 2nd IU and it does not code out right away. This was the same behavior as the 1st. But after running F8 you get C255C. Then after that it always codes right way with C2557 after trouble reset. So I replaced the pwb-a board but it still codes out right away after trouble reset. I then try the M5 cooling fan as well but no change. Then I try a 3rd IU and it then worked with no problem. Im wondering if the board was damaging the TCR sensor.

                      Sent from my DROID BIONIC using Tapatalk

                      Comment

                      • blackcat4866
                        Master Of The Obvious

                        Site Contributor
                        10,000+ Posts
                        • Jul 2007
                        • 23003

                        #12
                        Re: Bizhub 200 C2557 after dev unit change.

                        That was a costly fix on an old POS. =^..^=
                        If you'd like a serious answer to your request:
                        1) demonstrate that you've read the manual
                        2) demonstrate that you made some attempt to fix it.
                        3) if you're going to ask about jams include the jam code.
                        4) if you're going to ask about an error code include the error code.
                        5) You are the person onsite. Only you can make observations.

                        blackcat: Master Of The Obvious =^..^=

                        Comment

                        • richwalker
                          Technician
                          • Mar 2013
                          • 30

                          #13
                          Re: Bizhub 200 C2557 after dev unit change.

                          Originally posted by EarthKmTech
                          Have you checked the toner adding solenoid as per my post;
                          http://www.copytechnet.com/forums/ko...highlight=2557

                          When it gets stuck open you will get 2557's intermittently as toner is added uncontrollably. Even if it isnt stuck open, operate it and see if the foam is sticky in the open position. if it does not release instantly you have a problem.
                          I agree with EarthKMTech, check the toner adding solenoid to ensure it's not sticking in the open position. If it is, then clean it and replace developer and run F8 again.

                          Richwalker.

                          Comment

                          • wseyller
                            Service Manager

                            1,000+ Posts
                            • Sep 2012
                            • 1129

                            #14
                            Well the problem came back. Going the shop now the get the more parts that were suggested.

                            Sent from my DROID BIONIC using Tapatalk

                            Comment

                            • wseyller
                              Service Manager

                              1,000+ Posts
                              • Sep 2012
                              • 1129

                              #15
                              EarthKMTech hit the nail on the head. That solenoid was stuck open. I removed it and cleaned. Replaced dev and run F8. Feel confident that should do it hopefully.

                              Sent from my DROID BIONIC using Tapatalk

                              Comment

                              Working...