Cant test the punch motor on MX5070

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

    50+ Posts
    • Aug 2012
    • 55

    #1

    [Error Code] Cant test the punch motor on MX5070

    I have a MX5070 that has a FN27 internal finisher with the punch option that is randomly throwing a F1-34 punch error. Power cycle fixes it and then it shows up a couple days later. Two other problems are happening with this. 1. it does not always log the error on the 23-2. in fact the last 3 are not on the list. 2. there is no way to test the punch motor in this model. the guy at tech support didnt believe me until he looked for himself. I remember this error coming up on previous models and replacing wiring harness, motor and HP sensor as per their tech bulletins. Sometimes this did not fix the error. Have any of you run into this issue? any feedback is greatly appreciated. I have been having a lot of error codes on these models that don't make sense.
  • spanky
    Trusted Tech

    250+ Posts
    • Sep 2012
    • 468

    #2
    Re: Cant test the punch motor on MX5070

    I have found on other punch units that I can lubricate where the punch head slides from back to front on the punch frame will correct most of these errors.

    Comment

    • r3d343420
      Technician

      50+ Posts
      • Aug 2012
      • 55

      #3
      Re: Cant test the punch motor on MX5070

      I have tried that also. currently i have the punch installed on a machine in our demo room and wrote a script that would throw a 50 page print job to it 5 times a day. its day 3 now and i have not had any errors. starting to think it may be something other than the punch unit itself.

      Comment

      • MHeon71
        Trusted Tech

        Site Contributor
        VIP Subscriber
        250+ Posts
        • Oct 2008
        • 487

        #4
        Re: Cant test the punch motor on MX5070

        Maybe try firmware, they just updated at the end of the month. There is a Sim that may only log a trouble code once, until a different trouble code pops up. It should be in TC 26-?

        Comment

        Working...