sr3250 internal finisher

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

    50+ Posts
    • Jun 2017
    • 73

    #1

    sr3250 internal finisher

    I have one that had a jam code of 149 which is invalid main machine data setting. After that the jam code was 105 front jogger fence. The jam code happened on the same copy count. The machine would not reset. I took the covers off and looked at the finisher and did not see anything wrong visually. I reinstalled it and it started working. Has anyone ever had this issue before. I just never heard of Invalid main machine data setting before. Any suggestions? The finisher is installed on a imc3000
  • GIUBOSS
    Service Manager

    Site Contributor
    1,000+ Posts
    • Jul 2013
    • 1435

    #2
    Re: sr3250 internal finisher

    Do you have updated firmware?

    Comment

    • slimslob
      Retired

      Site Contributor
      25,000+ Posts
      • May 2013
      • 37495

      #3
      Re: sr3250 internal finisher

      Originally posted by AMS
      I have one that had a jam code of 149 which is invalid main machine data setting. After that the jam code was 105 front jogger fence. The jam code happened on the same copy count. The machine would not reset. I took the covers off and looked at the finisher and did not see anything wrong visually. I reinstalled it and it started working. Has anyone ever had this issue before. I just never heard of Invalid main machine data setting before. Any suggestions? The finisher is installed on a imc3000
      My copy of the service manual says "Main instruction data defect" for J-149. To me that says corrupted data block providing an instruction to the finisher, I.E. possible loose connection. May have been the command for the front jogger fence motor. Ergo both errors on the same copy count. Your comment that it started working after you reinstalled gives the impression that you had removed the finisher therefore disconnecting it. Disconnecting and reconnecting may have corrected a bad connection. If it happens again, check for loose connector brackets.

      Comment

      Working...