fanuc 16t

[Sprew]

This control is on a swiss 5 axis. Just had the machine installed. Looked like xb axis was on a limit switch. E stop on start up. Physically moved that axis to releive the e stop. Problem: can only zero return two axis. The others say overtavel even though they are in the middle of their stroke. Do I need to reload parameters or ? I beleive one of the axis was homing but now it is not. I think you can designate a are of stoke not to go but dont know if that interferes with zero return. Thanks for any information.

[dcoupar]

Turn off the control. Hold down P and CAN keys and power up control. Do not let go of P and CAN keys until the control is fully powered up. Reset ESTOP and you should be able to zero return the machine.

[Sprew]

Thanks for the reply Dave. I hesitated, not knowing exactly what impact the CAN + P on boot would have. But I decided to give it a try. First off, the P key requires a Shift + G I think. Its a shift function anyways. But I did not hold the shift down as well, just the "G" + CAN.

Well now I cannot zero return any axis. But all axes are responding the same with the error message "impossible area".

I dont know if I am getting closer, or further away. What occured with the CAN + P on boot.

Thanks for your help

Mike

[dcoupar]

My apologies, P-CAN has always worked, but thinking back, I've never tried it on a keyboard where P was a shifted character.

[Sprew]

No worries Dave. P + can is used to overide an overtavel. It is NOT shift sensitive. So it works the same.

Darkest before the Dawn. Finally got it fixed today. For archival sake, this is what I did.

First needed to write enable. On the 16t it was 1;MDI mode 2;offset/settings 3; 1 + input to enabel parameter write.

Then, system, softkey to Keeprelays, change bit 0 of K01 to 1. This enables jogging. Jogged each axis right on top of the proximity switch. Turn write protect back to 0. Shut down. Boot with P + Can, clear alarms. Zero Return.

It didnt work exactly that smoothly, but that was the flow. It took alot of reboots.

Thanks so much for you help on this issue and hope it might help someone else in the future. It was kind of a wierd problem, but the solution may help in another situation.

Mike