MX-354 keeps getting F2-40 errors

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

    Site Contributor
    1,000+ Posts
    • Dec 2009
    • 1020

    MX-354 keeps getting F2-40 errors

    At first I thought this was due to the generic toner my company uses,the stuff sucks. It seemed to happen when the toner would run out and the new toner installed. Twice it has blown the toner sensor in the developer unit. Developer has been changed both times and I even installed a different developer unit. We now are running oem toner in this and now today we got this code again. I am not the tech that went out today but it seemes to have happened when it ran out of toner. Anyone seen issues with this model?
  • OlliK1969
    Trusted Tech

    250+ Posts
    • Nov 2016
    • 287

    #2
    Re: MX-354 keeps getting F2-40 errors

    Hi

    Sim 25-2 : result 128 +/- 10 ??
    How old are drum-unit/main charger/dust filter ??
    Firmware 05.00.cc / 05.00.c1 ??

    Comment

    • Hansen88
      Service Manager

      Site Contributor
      1,000+ Posts
      • Dec 2009
      • 1020

      #3
      Re: MX-354 keeps getting F2-40 errors

      Firmware is latest and all maint parts have low counts on them.

      Comment

      • ZOOTECH
        Senior member of CRS

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

        #4
        Re: MX-354 keeps getting F2-40 errors

        With the toner cartridge removed and front door cheated, run SIM 25-1. If it's not in the range given above, you have an over/under toner level.
        "You can't trust your eyes, if your mind is out of focus" --

        Comment

        • Hansen88
          Service Manager

          Site Contributor
          1,000+ Posts
          • Dec 2009
          • 1020

          #5
          Re: MX-354 keeps getting F2-40 errors

          I understand about the toner level but at least two times it blew out the toner sensor. Put in new developer mix and when running 25-2 no reading. Replaced sensor twice and replaced the whole developer unit once because we didnt have another toner sensor to put in.

          Comment

          • CopierTechofOmens
            Agitating Artificer

            250+ Posts
            • Jan 2009
            • 268

            #6
            Re: MX-354 keeps getting F2-40 errors

            Is the machine pre 9/14? The main drive and toner supply clutch have been updated. If you've checked all the mechanical then its electrical. I.E. Wiring harness, PCU
            sigpic

            Comment

            • Hansen88
              Service Manager

              Site Contributor
              1,000+ Posts
              • Dec 2009
              • 1020

              #7
              Re: MX-354 keeps getting F2-40 errors

              Originally posted by CopierTechofOmens
              Is the machine pre 9/14? The main drive and toner supply clutch have been updated. If you've checked all the mechanical then its electrical. I.E. Wiring harness, PCU
              Thanks, I will look into the clutch.

              Comment

              • Hansen88
                Service Manager

                Site Contributor
                1,000+ Posts
                • Dec 2009
                • 1020

                #8
                Re: MX-354 keeps getting F2-40 errors

                Originally posted by CopierTechofOmens
                Is the machine pre 9/14? The main drive and toner supply clutch have been updated. If you've checked all the mechanical then its electrical. I.E. Wiring harness, PCU
                I looked at the manual and I dont see any clutch in the toner system. Just a toner motor. Did not see any bullitens about this either.

                Comment

                • Copycat
                  Technician
                  • Feb 2019
                  • 16

                  #9
                  Re: MX-354 keeps getting F2-40 errors

                  Hi, Check the drive unit motor, Or replace the complete drive unit , I had that happen to me once.


                  Thank you,


                  Copycat

                  Comment

                  Working...