Enhancement - tool change workflow improvements

[repentsinner]

Hi, it would be great if the tool change workflow could be improved in the following ways:

• Capture a tool change location in machine coordinates that gSender goes to prior to the change, similar to the location of the tool length probe. Retracting to safe and going to the same location should be the first step of any M6 override command
• Allow the various tool change strategies to be executed outside of a job, either during setup, diagnostics, or just to learn how the different strategies work
• Document the different strategies more completely directly in the UI
  • Ignore should likely warn that if a gcode program has an M6 in it and it is ignored, cutting results after the change are likely to be undefined.
  • Pause notes that if you move the bit, it needs to be moved back before resuming? This seems crazy from an expectation perspective (software is good at remembering coordinates, humans are not), and behavior does not seem to reflect this. Is this documentation out of date?
  • Standard re-zero makes note of a 'guided process', but prior to running it there is no way of knowing what that process is. There is so much space in the UI to directly describe the process, instead of hoping that a user is going to find a manual.
  • Flexible re-zero seems less flexible than Standard re-zero. Saved tool offsets on hobby-grade CNC? Where are these offsets saved?
  • Fixed tool sensor is sort of described, and I have a bitsetter, but the machine went rogue and did not successfully recover the pre-change position when trying to execute this once so now I don't trust it. See desire above to allow the tool change strategies to be executed outside of a job so we can debug what the heck they are doing.
  • Note that if on the tool change page of the settings dialog and you navigate to a different page and back, a bunch of the help text is inexplicably removed.

Version 1.4.7 on MacOS talking to grbl (shapeoko 5 pro).

Thanks for considering!

[ShadyMCShadesen]

I have the same issue with the bitsetter and the option "fixed tool length sensor" At the moment after changing to a longer bit it moves to the Z height (set in fixed tool length sensor settings) and then wants to move to its last position (Z) but thinks it's anywhere upwards outside of the machine space (soft limit triggered) By changing to a shorter bit the opposite happens, it moves to the set Z height and the moves downwards again. I don't understand why it wants to go to a different Z height at all.

Also at the beginning of the wizard, it moves to machine coordinate Z -10 for the travel to the bitsetter... Why not at -1 (the position it has after homing) for best height