Hi everyone,I’m currently using
Probe Basic UI on a
3-axis milling machine. Tool setting and probing are working perfectly — kudos to everyone who made that process so smooth.However, I ran into a potential issue. I noticed that the
.ngc file generated from Fusion360 only prompts for a tool change (e.g.
) without performing any actual tool change or probing routine. That’s risky — I almost started a job without realizing it wouldn’t automatically run the tool-length probing cycle after each change.I’d like to make the workflow safer and more automated. Ideally:
- Whenever a tool change (
) is called, the machine should automatically go to the tool probe and measure the tool length before continuing.
- No manual pause/resume or separate probe command should be required — it should just happen as part of the
sequence.
Would this be best handled by:
- A custom M6 remap in the HAL/INI file, or
- A modified Fusion360 post processor (.cps) that inserts probing commands automatically after each tool change?
Also, I noticed another small issue:
The spindle starts cutting immediately after the
command, without waiting for it to reach full speed. I know I can tweak ramp or lead-in settings in Fusion, but I’d prefer a
permanent spindle-speed wait in the HAL or remap (something like a delay or “wait-for-at-speed” check).For testing, I’ve been running with the spindle
disabled and using a
pencil in place of the endmill — so nothing dangerous, just making sure all the logic works before real cutting.Any guidance or examples of how others have integrated automatic tool probing and spindle speed waits into Probe Basic or LinuxCNC would be much appreciated!Thanks in advance
