I’ve been using the BitSetter for a while, and generally find it works great. However, there are some workflows where I don’t want to or can’t use it (for example, when using a spring-loaded diamond drag bit, or when using a surfacing bit that is too large for the probe). In order to use these bits, I generally uncheck the “BitSetter Enabled” checkbox in Machine Settings → Options, insert the bit I want to use, re-home the machine, and then re-zero the machine (generally by manually jogging to location and setting zeros on all axes); I then typically confirm the zero is accurate by using the rapid to current x-y and rapid to current z +5mm features. But, for some reason, when I actually load a new file and run a new job, the Z-axis zero is always off by several inches (that is, it is not the same Z I just confirmed was accurate using the rapid position setting). Only after cancelling the job, watching the machine slowly re-home itself, and then re-zeroing again, will the machine use the correct Z axis zero.
Not sure if this is just me, but it’s a real pain, given how much I love diamond drag engraving!
For reference, I’m running Carbide Motion 537 for Linux on a Raspberry Pi