M10, M11 chuck commands causing cycle stop

[ChrisQ]

Hi. I have a Cyclone P with a Fanuc OTC control with a Gamet power chuck fitted. I am using a bar puller running from a sub program for small batch production. The first time I ran the job everything worked fine and I was able to produce 200 parts without a hitch. I have just set up to do the job again but this time it stops intermittently after the M10 (chuck open) and the M11(chuck closed) commands with the cycle stop LED illuminated and no error on the screen, if you press cycle start it will carry on with the program. All other M codes seem to function fine and in MDI M10 and M11 function correctly with no chucking error alarm, the foot switch also functions correctly. I have checked all the wiring and plugs/sockets from sensors to the I/O board and everything seems fine. I have checked the function of the proximity switches and both are good. I have checked diagnostic param 120.3 for the FIN signal and confirmed it returns from the PMC correctly, I also watched diagnostic param 700 whilst running the bar pull routine. 700.0 enables when either chucking command is received and when the fault doesn't occur 700.2 proceeds to enable as the next line in the program is a dwell. When the fault does occur however nothing happens after 700.0 has finished. I would appreciate it if anyone has any thoughts/suggestions as to what the problem may be.

[Martin]

You could try setting Diagnostic 453 bit 0 to a 1. (diagnostic setup marker).

It will reset counters & timers.

[ChrisQ]

Hi Martin
thanks for your suggestion, sadly it didn't make any difference.

[Martin]

Hi Chris

Not sure on this then.

May be worth checking oil leve & air pressure just to be 100%.

[ChrisQ]

Hi Martin
thanks, have already done both of those.
do you know how the M codes are set and if it's possible to look at the set up,and change them?
only other thing i can think of is to wipe the controller and re-install everything but that seems a bit drastic

[ChrisQ]

Hi Martin
i have solved the problem, by tracing the problem through the diagnostics it turned out to be air pressure related. when i checked the regulator i found the gauge was not telling the truth and i had managed to set an air pressure that meant everything was happy until the air cylinder was actuated then the momentary drop in pressure was enough to cause a feed hold state and prevent the program from moving on.
Thanks for your input
Regards Chris