Skip to content

Conversation

@wavexx
Copy link
Collaborator

@wavexx wavexx commented Apr 21, 2021

This change restores the minimum extruder height for filament purge
during M600 from the current 50mm back to 27mm from FW 3.9.

We do this by introducing a new option for unload_filament() to indicate
that the unload is part of an automatic swap, and in such cases avoid
raising more than absolutely necessary (this will also come in handy
to avoid the extra purge in PR #2318 during M600).

A new define MIN_Z_FOR_SWAP is introduced for this purpose.
MIN_Z_FOR_UNLOAD is still used for manual lcd unload and for M702 and
hasn't been changed.

PFW-1237

wavexx added 2 commits April 21, 2021 19:07
This change restores the minimum extruder height for filament purge
during M600 from the current 50mm back to 27mm from FW 3.9.

We do this by introducing a new option for unload_filament() to indicate
that the unload is part of an automatic swap, and in such cases avoid
raising more than absolutely necessary (this will _also_ come in handy
to avoid the extra purge in PR prusa3d#2318 during M600).

A new define MIN_Z_FOR_SWAP is introduced for this purpose.
MIN_Z_FOR_UNLOAD is still used for manual lcd unload and for M702 and
hasn't been changed.
gcode_M600_filament_change_z_shift is almost useless, since it performs
what is already been done internally by filament_unload().

However it *does* cause the carriage to raise earlier during unload
compared to making the user wait after "press for unload".

Change it so the calculated Z height matches MIN_Z_FOR_SWAP.
@DRracer DRracer merged commit 00ce16e into prusa3d:MK3 Apr 22, 2021
@wavexx wavexx deleted the reduce_m600_min_height branch May 27, 2021 15:02
wavexx added a commit to wavexx/Prusa-Firmware that referenced this pull request Jun 28, 2021
Swaps are triggered with a hot printer, and thus don't require to
perform an extra purge. This follows my own advice from PR prusa3d#3121.
wavexx added a commit to wavexx/Prusa-Firmware that referenced this pull request Mar 29, 2022
Swaps are triggered with a hot printer, and thus don't require to
perform an extra purge. This follows my own advice from PR prusa3d#3121.
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