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
TFT_LVGL_UI MKS implementation has its own filament runout logic, and using that combined with relative extrusion generates issues when resuming the printing.
My main guess for the root cause of the issue is the usage of G90/G91 to lift the Z axis when going to the park position, causing the running gcode to lose its references for extrusion when resuming.
(OrcaSlicer option to used relative extrusion)
Bug Timeline
No response
Expected behavior
Printing interruption might not change current movement configuration
Actual behavior
The extruder runs backwards when resume the printing, in some cases even ejecting the filament from the extruder
Steps to Reproduce
Setup a printer with TFT_LVGL_UI
Use relative extrusion on the slicer
Start a print
Trigger the filament runout sensor
Restablish the filament sensor
Press "Resume"
Version of Marlin Firmware
Bugfix-2.1.x
Printer model
Two Trees SP5
Electronics
MKS Robin Nano V3.1
LCD/Controller
MKS TFT 3.5
Other add-ons
MKS Wifi
Bed Leveling
None
Your Slicer
Other (explain below)
Host Software
SD Card (headless)
Don't forget to include
A ZIP file containing your Configuration.h and Configuration_adv.h.
Instead of using relative movement to lift the nozzle before moving, the current Z position, which is available right above, can be used to calculate the lifted height. In this way, it is not requried to use G90/G91, which causes the side effect of also resetting the relative extrusion defined at the beggining of the gcode.
The text was updated successfully, but these errors were encountered:
Did you test the latest
bugfix-2.1.x
code?Yes, and the problem still exists.
Bug Description
TFT_LVGL_UI MKS implementation has its own filament runout logic, and using that combined with relative extrusion generates issues when resuming the printing.
My main guess for the root cause of the issue is the usage of G90/G91 to lift the Z axis when going to the park position, causing the running gcode to lose its references for extrusion when resuming.
(OrcaSlicer option to used relative extrusion)
Bug Timeline
No response
Expected behavior
Printing interruption might not change current movement configuration
Actual behavior
The extruder runs backwards when resume the printing, in some cases even ejecting the filament from the extruder
Steps to Reproduce
Version of Marlin Firmware
Bugfix-2.1.x
Printer model
Two Trees SP5
Electronics
MKS Robin Nano V3.1
LCD/Controller
MKS TFT 3.5
Other add-ons
MKS Wifi
Bed Leveling
None
Your Slicer
Other (explain below)
Host Software
SD Card (headless)
Don't forget to include
Configuration.h
andConfiguration_adv.h
.Additional information & file uploads
Configuration.zip
gcodes.zip
Suggestion
Instead of using relative movement to lift the nozzle before moving, the current Z position, which is available right above, can be used to calculate the lifted height. In this way, it is not requried to use G90/G91, which causes the side effect of also resetting the relative extrusion defined at the beggining of the gcode.
The text was updated successfully, but these errors were encountered: