You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Minor annoyance: After turning on the printer, the Z axis moves up twice while I'm changing the filament: once when unloading, once when loading. The second one isn't really necessary, and can result in the Z axis topping out if it's already near the top.
Again, not a big deal but hopefully an easy fix. And it only seems to happen after turning the power on. I thought performing an auto-home after startup would be a viable workaround (assumption: firmware doesn't know actual Z height until homed) but it does it in that case too.
How to reproduce
Power on the printer
Select "unload filament" (printhead heats up)
Press knob to eject filament (printhead moves up and ejects filament)
Insert new filament (printhead pulls in filament, then moves up again)
Expected behavior
Power on the printer
Select "unload filament" (printhead heats up)
Press knob to eject filament (printhead moves up and ejects filament)
Insert new filament (printhead pulls in filament, with no additional Z movement)
Files
No response
The text was updated successfully, but these errors were encountered:
Printer model
MK3S/+
MMU model
No-MMU
Firmware versions
3.14.1
Upgrades and modifications
none
Printing from...
SD Card
Describe the bug
Minor annoyance: After turning on the printer, the Z axis moves up twice while I'm changing the filament: once when unloading, once when loading. The second one isn't really necessary, and can result in the Z axis topping out if it's already near the top.
Again, not a big deal but hopefully an easy fix. And it only seems to happen after turning the power on. I thought performing an auto-home after startup would be a viable workaround (assumption: firmware doesn't know actual Z height until homed) but it does it in that case too.
How to reproduce
Expected behavior
Files
No response
The text was updated successfully, but these errors were encountered: