Working with ender 3v2, using latest bugfix branch when cancelling a print, moving Z axis will also move the filament (it moved the extruder in the same amount).
Another move of Z axis will not do it again.
This happened in 2.0.7, later i reverted to creality's firmware, but now after installing bltouch i put bugfix 2.0.x and i see this hasn't been solved.
Expected behavior:
Only the Z axis should move
Actual behavior:
Z axis move and extruder moved as well
Very problematic as this can harm printers, the nozzle might not be hot enough, it can also cause jam inside the bowden tube (which it did for me) and it can make a mess of the spooler as it throws out the filament very quickly
How do you observe E moving? Maybe it is just oozing while everything is hot?
@sjasonsmith sorry for not being clear on this, the extruder actually moves back, minus of the same amout I guess, it retracts in the same amount.. I see the filament shooting out.. I can take a video of this happening if needed.. Just start a print, cancel it and it will happen
Same exact behavior for me. For me the extruder retracts like crazy when moving Z up (There is a knob and it turns counterclockwise, its not oozing)
@liamkesatoran I tested today, If you home x/y (octoprint) before moving Z then it won't take out the filament..
@pixelicous i think a video will be good in this case
@boelle @sjasonsmith Attached video - https://youtu.be/LNKouvYJv7E
I tried homing / moving Z from lcd menu, this resulted in the same thing..
So only homing/moving from octo worked after cancel, I didn't try homing from octoprint but moving Z from lcd menu
@sjasonsmith Thanks for labelling this, hopefully somebody will pick this up.. it can be very problematic.. would have helped myself if i knew where to look, never code anything on marlin firmware
I am also having this same issue. More than glad to help troubleshoot if you need anything.
It would help if you can try an older version such as 2.0.6.1, to determine whether this problem is new.
It only happen with printing started / cancelled using OctoPrint?
If you start/stop the print from the LCD, do you get the same behaviour?
If you start/stop the print from the Octoprint and try to move using Octoprint interface, do you get the same behaviour?
@pixelicous can you do a simple test with this branch? https://github.com/rhapsodyv/Marlin/tree/dwin-move-axis-fix It just a "try".
Could you also check what is coded in the Octoprint Setup for "GCODE Scripts" for when a print is cancelled?