Persistent F2-64 Error on MX-4101N

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • CES_Imaging
    Technician

    50+ Posts
    • Nov 2012
    • 65

    #1

    Persistent F2-64 Error on MX-4101N

    We have a Sharp at a customer site with a persistent F2-64 error. It seems to occur as the machine is going through its toner replenishment cycle. The developer seems to be receiving toner, so I do not think it is the toner motor. We have replaced the PCU PWB, this did not fix the error.

    Any luck getting rid of it?
  • harleyrider
    Trusted Tech

    250+ Posts
    • Oct 2011
    • 348

    #2
    Re: Persistent F2-64 Error on MX-4101N

    toner sensor- dv unit?

    Comment

    • ZOOTECH
      Senior member of CRS

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

      #3
      Re: Persistent F2-64 Error on MX-4101N

      Clogged toner delivery pipe?
      "You can't trust your eyes, if your mind is out of focus" --

      Comment

      • blackcat4866
        Master Of The Obvious

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

        #4
        Re: Persistent F2-64 Error on MX-4101N

        Most of the time I just take the toner cartridge out back (out of sight) and beat on it. =^..^=
        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

        • divad2k1
          Trusted Tech

          100+ Posts
          • Sep 2010
          • 147

          #5
          Re: Persistent F2-64 Error on MX-4101N

          One of the above !

          Comment

          • mojorolla
            The Wolf

            2,500+ Posts
            • Jan 2010
            • 2570

            #6
            Re: Persistent F2-64 Error on MX-4101N

            Pull the toner cart and run SIM 25-1. The top set of numbers indicate how much toner is in each developer unit. The lower the number, the more toner is in the DV unit. If the number is very low 20-30 dv material will be needed to be replaced. If it is above 200, there is not enough toner and the machine pulls dv; again dv material will be needed.
            Off the top of my head, if the reading is below 73 or above 200, those codes appear.
            As mentioned above, check the feed pipe is not packed or the toner cart is not sticking. Two very common issues with Sharp.
            Also make sure the customer is storing the backup toner flat. We had a customer storing it on end which caused several F2 codes.


            Failing to plan is planning to fail!!!

            Comment

            • JustManuals
              Field Supervisor

              5,000+ Posts
              • Jan 2006
              • 9838

              #7
              Re: Persistent F2-64 Error on MX-4101N

              This Parts & Service Manual can now be purchased for $12.77 and downloaded immediately after payment from:





              Paul@justmanuals.com

              Comment

              • CES_Imaging
                Technician

                50+ Posts
                • Nov 2012
                • 65

                #8
                Re: Persistent F2-64 Error on MX-4101N

                I'm headed out to the customer this morning. I'll let you know what happens.

                I know it isn't the DV sensor, as we tried replacing the DV unit.

                Comment

                • teklife256
                  Trusted Tech

                  100+ Posts
                  • Sep 2012
                  • 164

                  #9
                  Re: Persistent F2-64 Error on MX-4101N

                  This error came up on a similar machine a couple months back. If I recall correctly I shook the toner and cleared code.

                  Were you able to come come up with a solution?

                  Comment

                  Working...