3 and 4 series MPC toner add issues

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • copier tech
    Field Supervisor

    5,000+ Posts
    • Jan 2014
    • 8119

    #16
    Re: 3 and 4 series MPC toner add issues

    Originally posted by Oze
    I've had an MPC3504 that I've been struggling with as well.
    Grinding supply gears and out of magenta toner.
    Went the first time(Account is 2 hours away) and replaced magenta PCDU and a new toner supply unit...turned the dev to make sure that it wasn't seized and it worked fine.....for a day.
    Went back the next day with a new magenta dev and a s/h toner supply unit AND updated the firmware.
    It's working fine for now....it had NEVER had firmware updated.
    Let us eat, drink, and be merry, because tomorrow we may die!

    For all your firmware & service manual needs please visit us at:

    www.copierfirmware.co.uk - www.printerfirmware.co.uk

    Comment

    • MrEdge
      Technician
      • Jan 2014
      • 32

      #17
      Re: 3 and 4 series MPC toner add issues

      Hey Guys
      Anyone had this issue when the firmware is already up to date?

      Comment

      • Polarbear
        Service Manager

        1,000+ Posts
        • Feb 2012
        • 1070

        #18
        Re: 3 and 4 series MPC toner add issues

        Originally posted by MrEdge
        Hey Guys
        Anyone had this issue when the firmware is already up to date?
        Which issue?

        Binding dev gears or broken toner coil?
        Press the GREEN button!!

        Comment

        • MrEdge
          Technician
          • Jan 2014
          • 32

          #19
          Re: 3 and 4 series MPC toner add issues

          Originally posted by Polarbear
          Which issue?

          Binding dev gears or broken toner coil?
          Both.

          It appears the binding gears in the developer unit and the broken toner hopper coil occur due to toner being continuously being feed into the developer unit, it gets packed to the point where things break.......These 2 issues seem to have the same root cause but show up as these 2 different symptoms or both it you hit the jackpot!!
          To me it looks like the TD sensor data (VtRef) is somehow getting corrupted or when the new developer unit is run up the new value of VtRef is not registered as the new set point? It's just odd as we have had a few of these and mostly a new toner hopper and developer unit sorts the issue, on one occasion where we had a recall we reseated every connector on the I/O and BCU boards and that got it sorted, but not this time.
          We are vigilant on keeping the firmware up to date on our fleet as this prevents a load of service calls so this machine was running the latest versions when the fault occurred.

          Comment

          Working...