Tool change crashing into bitsetter button and doesn't reverse off the bitsetter button

CNC Machines Shapeoko 4
1

I have never run into this before and now this has happened twice ruining 2 bits. I’m running CM version 652 on my Shapeoko 4 STD. It is not the first time running a program on CM 652.
When starting my program and my S4 STD calls for the initial tool change, the router with the bit installed in the collet travels down to the bitsetter button centered directly over the center of the button as always. However, on 2 separate occasions when the installed bit touched the bitsetter button, it did not stop and reverse. Instead, the bit pushed the button and held there with the button bottomed out. Had to power off my CNC to get it off the button. This ruined 2 of my bits (one 1/8" dia end mill flute tips chipped and one 30 degree Vee bit point broke off.) Just to see if it repeats, I tried repeating the steps using my broken bits. This did not happen again with these attempts. I do not know what could cause this, (a machine controller issue, an intermittent bitsetter problem, or a CM glitch).

All previous CM versions I’ve used running numerous programs never had this problem including this CM 652 until this occurrence happened today.

What is going on here? Can Carbide contact me to iron this out? I don’t need to be running any programs not knowing if this will happen again.

2

Sounds like there’s a problem with detecting that the BitSetter button is pressed, and it is intermittent. My first guess would be a wiring problem. It’s also possible the switch inside the BitSetter is going bad.

Check all the connectors. Make sure all the wires in the connectors are firmly seated and connected, the connectors are completely seated. If any of the connectors are discolored, that could indicate arcing.

If you want to talk to C3D support, you should reach out to them, rather than hoping that see this post - mailto:support@carbide3d.com.

2 Likes
3

If you open CM, connect but do not initialize you can go to debug and check all the sensors including the BitSetter. Just press the BitSetter button down and see if it changes state. If it does not then do as @mhotchin suggests and check your connections.