Canon IR105 jams on tray 1,2,3

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • AlexSV
    Technician
    • Feb 2013
    • 17

    #1

    Canon IR105 jams on tray 1,2,3

    Tray 1,2,3 get wrecked continuously. Tape 4 works normal. All the rollers are new. The belt from the motor 2 is new. Firmware is updated. Any ideas?

  • HELIO240
    Trusted Tech
    • Jan 2011
    • 137

    #2
    Re: Canon IR105 jams on tray 1,2,3

    Which code jam? This information is necessary.
    Service mode / copier /display / jam.

    Comment

    • AlexSV
      Technician
      • Feb 2013
      • 17

      #3
      Re: Canon IR105 jams on tray 1,2,3

      jam code 0101

      Comment

      • Canuck
        Tech Specialist

        1,000+ Posts
        • Nov 2007
        • 1713

        #4
        Re: Canon IR105 jams on tray 1,2,3

        0101 is right deck pickup up sensor. service mode function/sens-adj run op-sens. They should all pass. If you get this jam code regardless of paper source(check table) then the paper is passing by the sensor without it being detected. Make sure that the prism on the right door and under metal plate on pickup assembly(the one you remove to replace rollers) is clean and ok. Also make sure that the transmitter and receiver in the right pickup assembly are clean and properly aimed

        Comment

        • AlexSV
          Technician
          • Feb 2013
          • 17

          #5
          Re: Canon IR105 jams on tray 1,2,3

          Originally posted by Canuck
          0101 is right deck pickup up sensor. service mode function/sens-adj run op-sens. They should all pass. If you get this jam code regardless of paper source(check table) then the paper is passing by the sensor without it being detected. Make sure that the prism on the right door and under metal plate on pickup assembly(the one you remove to replace rollers) is clean and ok. Also make sure that the transmitter and receiver in the right pickup assembly are clean and properly aimed

          Everything is done .. The problem is not resolved

          Comment

          Working...