[Error Code] mx-fn10 finisher with FGMJ JAMS?????

[Guest]

Hi all just wondering if any body has come up with the same problem and had a fix! mx4111n with a mx-fn10 finisher first sheet would come through and side jogger will push paper over than when the next sheet comes through than it throws a jam,going into sim 22-3 jams log it shows FGMJ but i cannot find this error code nor is it listed on any sharp service bulletins.I dont know if some how its gone out of timing as i haven't come across this problem before.Only way to get around it to get the customer going was to disconnect the finisher and remove centre paper transport section and plate so paper exit shift doesn't chatter and throw a code.Cheers!

• 
  
  

• 
  
  

[spanky]

Re: mx-fn10 finisher with FGMJ JAMS?????

The following was copied from the newest service manual for the MX-4111N.

FGMJ

Gripper motor JAM Driving the grippermotor is started.
CAUSE:

Change from FGHPS ON to OFF isnot detected within the specifiedtime during the gripper operation.
Change from FGHPS OFF to ON isnot detected within the specified

time during the gripper operation.

[Dustin(WOP)]

Check your bulletins again...there is a sim you can run and change the gripping speed. If memory serves me correctly sim 3-6 value N change to 35 from 50(default)
Good luck!!!

[ricohrice]

Re: mx-fn10 finisher with FGMJ JAMS?????

Take the paper pass and plate out of the machine and check the jewel sensor, make sure it's there and not sticking anywhere, I've seen them stick to the duplex guide above the paper pass.

hope this helps

[waldo]

Re: mx-fn10 finisher with FGMJ JAMS?????

Well this turned out to be a bit weird,first i checked to see if it was out of timing (staple unit) and it all checked out ok but what i found was the side staple cartridge wasn't sitting in propley which had caused the grippers not to operate as they should i dont know why and i cannot explain it but when i refitted the staples holder back in it tested ok.

[Sharpshooter]

Re: mx-fn10 finisher with FGMJ JAMS?????

There is a firmware update for this problem!!!