Hi. I’m getting very frustrated by a recurring issue that I hope can be blamed on user error.
Steps to reproduce:
enable bitsetter
run a job using multiple tools
turn machine off
turn machine on
connect to machine
disable bitsetter
initialize machine
zero to top surface using bitzero
run program
enjoy machine reaching for the sky and raising z past the machine limits
Is there a correct procedure for disabling the bitsetter? I can’t use it with certain tools so I frequently have to disable it and then re-enable it. Every time I disable it though, the machine always does the above.
After disabling the BitSetter it is necessary to either re-set zero, or to re-initialize the machine — when using the BitSetter Z position is set as a relative offset based on tool length from the machine origin, but that’s not valid when it’s disabled.
I disable the bitsetter and then rezero z using the bitzero. Then I check to make sure that my z is correct using the Z+6 jog. Shouldn’t disabling the bitsetter and rezeroing z clear any tool length offsets?
I had this issue but found that I had somehow changed the thickness of my stock and the z access was unable to clear the stock or what it thought the stock thickness was
Changed my stock to .75” and it worked fine
Yes, it does, but that then re-establishes Z which will be wrong w/o the applied tool length offset — reinitializing is best, but re-setting Z zero should suffice.
There’s a bug with disabling bitsetter and the Z-offsets not being properly cleared in Motion. Until we get this fixed, here’s the workaround:
After disabling BitSetter, I recommend closing Carbide Motion, power cycling the CNC, and restarting Carbide Motion. That should prevent a crash from occuring.
