MX-M5001N

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • mikeg1265
    Technician
    • May 2014
    • 10

    #1

    MX-M5001N

    Hello,

    I have an MX-M5001N throwing an Error Code C4-00 which is a PTC error. We recently changed the drum, blade, fuser, and Primary Transfer Belt. The error started to appear after the PTB was installed. I changed the the PTC unit at the same time I installed the PTB. I can't seem to figure out why it's throwing C4-00, I've inspected the belt and PTC unit but I can't find anything wrong. If I clear the error code the copier works fine for a few days and then throws the code again. I've worked on a lot of Sharps but this one has me stumped.

    Mike G.
  • ZOOTECH
    Senior member of CRS

    Site Contributor
    2,500+ Posts
    • Jul 2007
    • 3374

    #2
    Re: MX-M5001N

    Originally posted by mikeg1265
    Hello,

    I have an MX-M5001N throwing an Error Code C4-00 which is a PTC error. We recently changed the drum, blade, fuser, and Primary Transfer Belt. The error started to appear after the PTB was installed. I changed the the PTC unit at the same time I installed the PTB. I can't seem to figure out why it's throwing C4-00, I've inspected the belt and PTC unit but I can't find anything wrong. If I clear the error code the copier works fine for a few days and then throws the code again. I've worked on a lot of Sharps but this one has me stumped.

    Mike G.
    I seem to remember there was a problem with the environment (humidity/heat) that was causing this code, so maybe one of those sensors is bad.
    "You can't trust your eyes, if your mind is out of focus" --

    Comment

    • harleyrider
      Trusted Tech

      250+ Posts
      • Oct 2011
      • 348

      #3
      Re: MX-M5001N

      there are several bulletins on this error. Sharp did change the ptc ass'y. Maybe you have the old style. A couple other bulletins are for noise C4 code also.

      Comment

      • lky1978
        Trusted Tech

        250+ Posts
        • Mar 2009
        • 475

        #4
        have you clear the ptc counter?

        Comment

        • mikeg1265
          Technician
          • May 2014
          • 10

          #5
          Re: MX-M5001N

          Originally posted by harleyrider
          there are several bulletins on this error. Sharp did change the ptc ass'y. Maybe you have the old style. A couple other bulletins are for noise C4 code also.


          Ahhhhhhh, now that's an idea. I wondered if the style was a little different. I'm gonna try putting the old PTC back in.

          Comment

          • Akitu
            Legendary Frost Spec Tech

            Site Contributor
            2,500+ Posts
            • Oct 2010
            • 2595

            #6
            Re: MX-M5001N

            I'm not looking at the bulletin right now, but I'm pretty sure the changes were mostly elongating the spring for better contact and less C4-00 codes.

            Someone please correct me if I'm wrong.
            Cthulhu for president! Why settle for the lesser evil?

            Comment

            • CorbinDallas
              Technician

              50+ Posts
              • Mar 2012
              • 56

              #7
              Re: MX-M5001N

              FYI: Incase you did not know. You can disable C4-00 by setting Simulation 55-1, soft-switch 8 bit 3 to "1" (until you get it figured out)

              Comment

              • hellcat
                Trusted Tech

                100+ Posts
                • Jan 2012
                • 123

                #8
                C4-00 Error Code in the display.
                Cause:
                There may be a loose connector to the PTC unit on the rear frame. This wire is coming
                from CN2 on the Secondary Transfer PWB to the PTC on the rear frame.
                Solution:
                Slightly crimp the connector that is plugging in
                to the PTC unit. If this connector is not a
                tight fit there could be intermittent C4-00 error codes.

                Comment

                Working...