That’s the darndest thing. Just did a test with the fake bit size (I used .231" because that’s what I had in my tool database from a previous test) and wouldn’t you know it, I get dead-on exact measurements on both tabs and slots.
I still think there’s some bigger issue at play here – a bug in EstlCam? A bug in the generated g-code? A bug in how FluidNC interprets the G-Code and commands movement? I don’t know. But there’s something – I can’t accept that this is “just how it is” and that everybody with a CNC machine knows you have to play games…
