LPF finisher jamming 012-103

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • MPrints
    Junior Member

    Site Contributor
    • Sep 2012
    • 9

    #1

    LPF finisher jamming 012-103

    I have a 700i with a LPF finisher. This machine is very clean and low use but most likely sat a while before it came to me from a municipality office. We set it up and it ran a few small jobs fine then it started this: copying (punch mode off) the finisher jams right after the punch unit with a 012-103 code or a 012-171 code depending on 8.5x11 or 11x17 paper. the paper stops right before the 3C drive roller.
    I have used component control to check the sensors 012-107 and 012-105 they change value when blocked by paper. When I check the 012-013 motor and the 012-019 motor they sometimes start spinning, sometimes dont. If they dont start they make a high pitched noise. The 012-066 motor checks fine.
    I have another LPF on a 242 and comparing them I notice when you clear a jam and the finisher goes through its reset cycle, the 242 LPF spins every shaft/roller in the paper path. The LPF I am having trouble with, the 3C and the 3F shafts do not spin during the reset cycle, which is the area of the two suspect motors. I thought it suspicious that two motors acted bad in the exact same way, thought maybe that indicated a problem elsewhere.
    Hopefully one of you guys might recognize something or suggest something else to check.
    I read through the tech tips that come up under these error codes I didnt see one that fit.
    Trying to figure this out myself because I am in a rural area and service gets costly due to travel.

    Thank you!
    Craig
    craig@mprints-printing.com
    903-569-5993
  • JrTech
    Trusted Tech

    100+ Posts
    • Jun 2013
    • 217

    #2
    Re: LPF finisher jamming 012-103

    The sensor that is causing your issues is the Booklet In Sensor. This can be a tricky issue and drive you a little batty. Below is the US part number and location in the manual if you have the EDOC. If you are in the EDOC you have to look in the 700 series with D3/D4/D5 Service Documentation (7th one if you have the suite)

    PL 17.137
    Part #5
    130E87370

    Hope this helps

    Comment

    • MPrints
      Junior Member

      Site Contributor
      • Sep 2012
      • 9

      #3
      Re: LPF finisher jamming 012-103

      I tested the booklet in sensor with CC (013-135) and it passes
      It seems this sensor wouldnt be involved because paper isnt entering the booklet section. It's jamming in the upper section that feeds to the top tray or stacking tray. On this Light Production finisher the paper path turns up to the top trays or down to the booklet maker.

      Comment

      • paul_gmb
        Technician
        • May 2014
        • 33

        #4
        Re: LPF finisher jamming 012-103

        Originally posted by MPrints
        I tested the booklet in sensor with CC (013-135) and it passes
        It seems this sensor wouldnt be involved because paper isnt entering the booklet section. It's jamming in the upper section that feeds to the top tray or stacking tray. On this Light Production finisher the paper path turns up to the top trays or down to the booklet maker.
        I;m digging in the "grave". Have you solved your issue ?

        I am having the exact same one. I am suspecting the punching unit which the paper pases through.

        I will test with the stacker tray, as it has the same trajectory and see what error codes thislights up.

        Comment

        • MPrints
          Junior Member

          Site Contributor
          • Sep 2012
          • 9

          #5
          Re: LPF finisher jamming 012-103

          Originally posted by paul_gmb
          I;m digging in the "grave". Have you solved your issue ?

          I am having the exact same one. I am suspecting the punching unit which the paper pases through.

          I will test with the stacker tray, as it has the same trajectory and see what error codes thislights up.
          Paul I am sorry to say I did not solve it, due to time constraints I swapped out the finisher and now have a spare

          Comment

          Working...