Skip to content

Switching Nozzle Probe Retract #27804

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

InsanityAutomation
Copy link
Contributor

In working with the Taz Twin Nebula dual extruder switching nozzle heads, we found that with a BLTouch the nozzle would often contact the bed before the probe. We wanted to keep the probe buries in order to minimize risk to damage from a failed print, so the best solution was to retract the tool head while probing then extend it again allowing larger nozzle to probe offsets.

The other issue observed when doing so manually with gcode to servo angles was when calling a tool after having modified it angles, such as a T0 in the start script, it did not restore, so this adds a servo command when old_tool == new_tool to ensure switching nozzle guarantees nozzle position when called.

@thinkyhead
Copy link
Member

Should SWITCHING_NOZZLE_PARK_TO_PROBE be enabled by default?

thinkyhead added a commit to MarlinFirmware/Configurations that referenced this pull request May 3, 2025
@InsanityAutomation
Copy link
Contributor Author

I left it enabled by default because I see it as the "Safe" option. Pulling the nozzle back would be more likely to prevent a crash than cause one. I did this in the first place because an OEM toolhead had the nozzle pushing the bed on every probe. I don't have a strong feeling either way, but it was a conscious decision.

thinkyhead added a commit to MarlinFirmware/Configurations that referenced this pull request May 4, 2025
thinkyhead added a commit to MarlinFirmware/Configurations that referenced this pull request May 4, 2025
@thinkyhead thinkyhead merged commit 4e1e7fa into MarlinFirmware:bugfix-2.1.x May 4, 2025
66 checks passed
EvilGremlin pushed a commit to EvilGremlin/Marlin that referenced this pull request May 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants