Sharp MX M316N F2-40 toner sensor range malfunction after pm, new drum and developer

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • tonerjockey
    Senior Tech

    500+ Posts
    • Apr 2014
    • 560

    #1

    Sharp MX M316N F2-40 toner sensor range malfunction after pm, new drum and developer

    Hello, the calibration seemed to take a while and fluctuate.
    3 weeks and 3000 prints later it threw F2-40. i checked sensor, developer and all looked fine. reset and ran 100 copies. toned back up by itself.
    another week later, same code.

    i am going to change the toner today and order another developer.

    am i missing anything??

    thank you a bunch.
  • tonerjockey
    Senior Tech

    500+ Posts
    • Apr 2014
    • 560

    #2
    and i just discovered that they are now using " for use in" toner, that says "made in USA"
    so i ordered a OEM developer and toner and will install that tomorrow.

    darn thing.

    have a nice day.

    Comment

    • tonerjockey
      Senior Tech

      500+ Posts
      • Apr 2014
      • 560

      #3
      ok, after several days for a one day ship, due to vendor putting my company name instead of the customers on the parts. i also realized that the customer has been telling me, it keeps jamming. and then i go there and find the F2-40 error code.
      so i took a ATC toner sensor from another machine there that recently had a different problem and put that in this one with the new developer and OEM toner.

      with luck this will resolve the issues.

      fingers crossed.

      Comment

      • bilyahn
        Service Manager

        1,000+ Posts
        • Dec 2006
        • 1470

        #4
        Good luck. I have had a lot of F2-40 problems lately due to aftermarket toners.

        Bil

        Comment

        • tonerjockey
          Senior Tech

          500+ Posts
          • Apr 2014
          • 560

          #5
          Hi bilyahn, ok, thank you. this makes me more relieved that i may have been able to resolve the problem. i told them, cross my fingers and i knocked on the wood paper cuter. then thought, with all my years sweeping developer, there really should be no mystery. but the next possible causes start to become expensive.

          Comment

          • WackyJack
            Technician

            50+ Posts
            • Feb 2021
            • 82

            #6
            Not the same model, but I recently had F2-40 codes that were being caused by the PCU PWB

            Comment

            • blackcat4866
              Master Of The Obvious

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

              #7
              It's been a long while since I worked on Sharp (there's my qualifier), but ...

              There were several models of Sharp that did not do an adequate developer stir on the first try. I always shake the developer well, and that is still not enough. I became aware of the desired stir numbers (sorry, don't remember those numbers anymore), and if I got a value outside of the desired range I would stir again, and sometimes a third time, until the number looked good.

              I think you've identified the main issue with the aftermarket toner, but without a complete developer change and vacuuming out the hopper, it will take a while to work through the residual aftermarket toner.

              I seem to recall the Panther and Andromeda series were known of low developer stir values. That shows you how long it's been since I've worked on Sharp, lol. =^..^=
              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

              Working...