Hi team,
The “Prompt for first tool” option that existed in gSender 1.6.1 stable
is missing from Edge-4. This was a really useful feature and its absence
is a step backward for users with bitsetters.
WHAT IT DID:
When starting a job, instead of always running the full tool change wizard
or always skipping, it asked the operator: “Do you want to probe the first
tool?” This gave operators the choice to:
- Skip the probe if the same bit is still loaded from a previous run
- Probe if it’s a new bit or a new session
WHY IT MATTERS:
When running the same file multiple times (e.g. batch production of
identical parts), the bit doesn’t change between runs. Having to probe
the bitsetter every single time wastes 30-60 seconds per run and adds
unnecessary wear to the bitsetter button.
With “Prompt for first tool” the operator could skip the probe on
repeat runs and only probe when something actually changed.
CURRENT WORKAROUND:
Use a manually-run macro (Macro 1) at session start to establish the
tool reference, then the Code strategy handles mid-job tool changes.
This works but requires the operator to remember to run the macro
manually - it’s not integrated into the job start workflow.
SUGGESTION:
Restore “Prompt for first tool” as a First tool behaviour option in
the Tool Changing settings, or add an equivalent “Skip if already
probed this session” option.
Machine: Shapeoko 5 Pro 4x4
Controller: Grbl 1.1h
gSender version: Edge 1.6.0-Edge-4
OS: macOS Apple Silicon (arm64)