I just installed a new Carbide router to replace my old, worn out one. (can’t afford upgrade right now) I was able to run 2 toolpaths on it (using 2 different bits) and the bitsetter worked fine doing the 2 toolpaths. When I changed bits for the final toolpath, I changed tools, clicked resume, and it headed over to the bitsetter. It starts going down (maye 1/4") then stops, then I get “probing cycle failed”. When I click ok on the error, Motion goes back to the initialization screen. I thought maybe something in my new installation was restricting the z axis, so I double checked everything, even unhooking the vac system. I tried rebooting everything, unplugging, etc but no luck.
Any ideas? Has my z axis sensor gone bad?
I appreciate any help you guys can give me. Although I did get my replacement router pretty quickly, I would really like to finish this project!
Edit: I thought of a temporary fix… disabled the bitsetter in Motion’s settings. The Z axis does go up and down on command, so I am going to try finish this project.
If you have a BitZero where is your magnet/clip. The BitZero and BitSetter are interconnected and if the magnet/clip is grounded you get the behavior you describe.
To confirm this open CM and connect but do not initialize. Go to Settings and see if there are active inputs. There should be none unless the gantry is in the home position. If it is move it slightly away from home and check for active inputs.
Double check that the BitSetter changes state when you manually press the plunger.
The magnet is still in place on the BitSetter. The z axis doesn’t get close to the magnet at all… probably only goes down about 1/4" before stopping. The BitSetter worked on the 2 previously run tool changes in my project . was on the last toolpath when this happened. Under active input it says “probe”. The red light comes on the bitsetter when I manually press the magnet, but it doesn’t change what is in the settings
The magnet is for use with the BitZero. If the magnet is grounded that is what is causing your problem. Move the magnet away from anything metal so it is not grounded and see if your inputs change.
The magnet should not be touching the BitSetter or anything else that is grounded. As stated earlier the BitSetter and BitZero are interconnected and can interfere with each other.
This was it!!! I had a disconnect after running the project, and the only way I can connect again is to shut the machine off and back on. I must’ve bumped the BitZero magnet into the base, as I noticed the red light was on. I moved it away, and continued with the reset. After getting the message from you, I initiated the machine, and it worked!!!
Live and learn. I live in Deep East Texas where the humidity is usually about 80%. With this cold snap every time I touch a light switch I get a shock. I hate that but soon it will warm up and the humidity will go back and the static will end. Folks that live further north in the areas below freezing have to put up with the static much more then I do.
You are right about a disconnect. You have to power off and back on to get CM to reconnect. Here on the forum are a lot of posts about mitigating static and mostly it is running ground wires through your dust collection system. Moving air, making chips and moving router=STATIC. STATIC=DISCONNECT.
Glad you got your problem fixed. By learning this way you will not have to relearn this lesson should it happen in the future. Good Luck!!!