[jflongo]

Hello All:

My 2016 Series III 1100 PCNC has experienced an intermittent problem over the past 4 years. Without warning, the spindle will shutdown during a program run. The program continues running and the axes are all active so if i'm not present, a gouge of the part and tool breakage occur. If i am present, i can press the spacebar and halt axes movement or stop the program before a crash occurs. Usually, what i see in the control cabinet is a fault display on the VFD window with a blinking 'hf25' but the fault code can vary. Opening the spindle door and waiting 15 sec clears the fault and i can resume the program.

I've checked continuity through the spindle door switch with a multimeter and it seems okay. I see the same failures with two different DB25 cables. This problem occurred for the first time 4 years ago and then disappeared. Recently, it has re-emerged and is becoming more frequent...occurring nearly every time i run a program. My workload and program complexity is increasing so resolving this problem is now a higher priority for me.

Has anyone else experienced this problem or have ideas about the cause or a starting point for troubleshooting? Thanks in advance for your time and assistance.

Joe
Iowa City, IA
12 May 2025

[fogassa]

Hello All:

My 2016 Series III 1100 PCNC has experienced an intermittent problem over the past 4 years. Without warning, the spindle will shutdown during a program run. The program continues running and the axes are all active so if i'm not present, a gouge of the part and tool breakage occur. If i am present, i can press the spacebar and halt axes movement or stop the program before a crash occurs. Usually, what i see in the control cabinet is a fault display on the VFD window with a blinking 'hf25' but the fault code can vary. Opening the spindle door and waiting 15 sec clears the fault and i can resume the program.

I've checked continuity through the spindle door switch with a multimeter and it seems okay. I see the same failures with two different DB25 cables. This problem occurred for the first time 4 years ago and then disappeared. Recently, it has re-emerged and is becoming more frequent...occurring nearly every time i run a program. My workload and program complexity is increasing so resolving this problem is now a higher priority for me.

Has anyone else experienced this problem or have ideas about the cause or a starting point for troubleshooting? Thanks in advance for your time and assistance.

Joe
Iowa City, IA
12 May 2025

Could be a broken wire, oxidized connector and maybe the switch with oxidized internal contacts. I don´t have the same machine but I´ve see it happen before with a oxidized switch contatcts.

[popspipes]

I would check all the wire connections, my 1100 had several that the screws werent tight, worth a check as they are not noted for tightning wires or torquing screws.