Ricoh MP3351spf with SR3000 Booklet Maker Finisher that randomly looses communication with the finisher during a job. In one location we have replaced the machine with exact model configuration and it also has the same problem. Thought it was customers power, had them install dedicated line, same issue. Updated latest firmware, inspected bridge unit for pinched wires and checked continuity between bridge to machine and bridge to finisher. Also replaced finisher controller on one unit. On this model, the finisher plugs into the bridge unit, not the main frame. Ricoh support is scratching there head, at this point they do not have any idea what's causing it. We have not seen the problem with a 790 finisher installed so far. Three new same config machines, three differrent locations all doing the same thing. Best we can tell, problem has to do with the finisher?? Any ideas??
MP3351 with SR3000 Finisher
Collapse
X
-
Tags: booklet maker, bridge, connections, controller, exposed, finisher, firmware, issue, job, power, ricoh, sc code, scratching, unit
-
Yes
Trade like a tiger sleep like a babyComment
-
It gives an SC792 sometimes. It has paper just entering the finisher, one at registration and another at paperfeed. We did find under the Bridge a board with a metal cover that is pressing on the power wire connections so tight that it's smashing the wires flat. No wire is exposed but...we've removed that cover just incase. Didn't hear from our customer yesterday but that's pretty normal because the machine doesn't do it all the time. Hope this helps.Comment
-
Ask Ricoh TS about the custom firmware for this specific configuration. I was having a different issue with this same configuration that the machine would not recognize the finisher until the machine was warmed up and had jammed a few times first thing in the morning. After that it worked fine all day. I finally got someone in TS to send me to level 2 support and they were able to tell me about the custom firmware for this configuration. This doesn't sound like the exact problem I was having, but close enough that trying the firmware can't hurt.TotoroComment
Comment