This FN18 was on a 4141 at the customers office. Brought it to the shop and put it on a 4110 with a rb11 pass unit which is different than what the 4141 uses.It does exactly 11 sets and then stops in the middle of the 12th set every time. It gives a code PDPPD2_s which is sensor in the pass unit. This is the same code it was giving at the customers. I replaced the sensors in the pass unit,but does same thing on shop machine. We replaced the saddle stitch control board and most sensors in the finnisher. We installed the latest firmware for the machine and the firmware listed for just the finnisher.I am at a loss on this one. Also I turned off misfeed detection and I guess with saddlestitch that does not work because I could not get anything out of machine.
-
-
Re: FN18 saddle stitch jamming
I have seen this caused by the punch unit, usually the sensors. -
Re: FN18 saddle stitch jamming
This code says the paper is still at the last sensor in the paper pass unit.
Check the level and height of the finisher.
I have seen this happen when the finisher is not at the proper height or is not level front to rear.
Are the mylars on the exit of the copier installed properly?Comment
-
Re: FN18 saddle stitch jamming
Are you running saddle job or regular staple job when it does it? Does it jam on sort/nonsort jobs ? This might help narrow it down. It will help to know if it jams on all output types or just one type of job.Comment
-
Re: FN18 saddle stitch jamming
It only jams when saddlestitching. It gives the same jam code of the paper pass unit on the customers machine and on our shop machine. The biggest thing I think is that it jams everytime at 11 sets. The machine just stops as the 12th set is ready to be folded. Remove the jams and run again-it jams after the 11th set comes out and just before the 12th would be folded.I talked to sharp techsupport,they had nothing at all.Comment
-
Re: FN18 saddle stitch jamming
I believe the problem could be one of these.
1. The Main Finisher Controller PCB. You replaced the Saddle Controller PCB which is unrelated and does not communicate with the transport unit MXRB20 or your shop MXRB11. The Transport Unit is powered and controlled by the finisher Main Controller PCB. An earth or timing problem within the controller will cause an issue that can be replicated on the same job or counter. Ensure the bottom metal rail is fitted to help with earthing. The Main controller has had a few part updates over time.
2. The PDPPD2 sensor spring is weak. After running several sheets, the timing becomes incorrect due to the poor sensor return speed. Add an extra turn to the spring to make it faster response timing.
Comment
-
Re: FN18 saddle stitch jamming
Thanks, I was thinking the the finnisher main control board,mainly because it is about the only things left. But your explanation is more based on facts and theory instead of mine based on onl thing left. Since the finnisher is mounted to the machine and does not pull out there is not a bottom rail. It would be easy enough to connect a ground wire between the two. I will also add a wrap to the spring on the pass unit at the customers. Thanks for your reply and your explanation.Comment
-
Re: FN18 saddle stitch jamming
Still must have the bottom rail fitted. Look at the installation manual. Its used for earthing & straight positioning, despite the fact that model finisher does not slide away from the main unit.Comment
-
Re: FN18 saddle stitch jamming
I second the extra wrap on the spring for the switch, try that first before spending money on boards.Comment
-
Re: FN18 saddle stitch jamming
Well we replaced the finnisher main control board, the saddle stitch board has been replaced also. Has same exact problem on two different machines. After the 11th set comes out the machine will stop in the middle of the 12th. Every timeit stops in the middle of the 12th set. I know it is not the machine or paper pass unit because it does this on both pachines exactly the same. I outfitted the grounding alignment bar.I dont know what else is left.Comment
-
Re: FN18 saddle stitch jamming
That is very interesting.
Have you tried varying sizes of booklets, example, a 6 sheet booklet compared to a 15 sheet booklet set?
Have you tried just half-fold mode as a copy for more than 12 sets?
Does this happen on a copy, print or both?
Are the successful booklets stapled & folded correctly? Is there any shift in the fold position through 1-11 sets?
The upper staple unit definitely works without any issues?
Is there any chance you can advise the firmware for the finisher and printer? I know you said it's up to date, but it might help.Comment
-
Re: FN18 saddle stitch jamming
The finnisher firmware is 01.08.02.00 and the 4110 copier that is is attatched to in our shop is the latest firmware available which was on 4-26-19 08.20.r1.mo I tried differing sizes of booklets and different paper sizes. All the same. Cust is using legal paper and just half floding so now that is how I am testing. Cust was printing,I am copying. They all come out fine-no shifting or any odd issues. I tried taking the sensor away from the exit actuator on the saddle exit tray just for something to try-ng Also I set to 10 sets and after that job started I put originals back in and set to make another 10 sets. It still stopped on the 12th set. Customer is a church,I thought if they could at least do 10 at a time and stack up the jobs that would at least let them get their booklets done but does not work either. I will try the upper staple unit,I have not checked if it does same thing.I just tested the upper stapler, it runs as many sets as you want,so the problem is only with the saddle unit.Comment
-
Re: FN18 saddle stitch jamming
I would try cloning the customers machine and then resetting it to factory settings.
You can then push the cloned file back into the machine so you don't loose any settings.Comment
-
Re: FN18 saddle stitch jamming
We finally fixed this unit. It was a bad FSPPD verticle path sensor. when that sensor is bad you get the jam code for PDPPD2-S paper pass 2 sensor and it will do 11 sets then jam on the 12th every time. Does not even make sense that it would work at all with that sensor not working.Comment
Comment