Prusa-Firmware icon indicating copy to clipboard operation
Prusa-Firmware copied to clipboard

[BUG] First layer is off when a print is started after a cancelled one on 3.13.2 revo MK3s+

Open adrienafl opened this issue 1 year ago • 5 comments

Printer type - MK3S Printer firmware version - 3.13.2

SD card or USB/Octoprint Octoprint

Describe the bug When starting a print just after cancelling one (from the printer), the printer prints too high which makes the first layer wrong. Mesh bed leveling looks good, the print head doesn't seem too high during this phase. This issue is gone after restarting the printer but comes back right after cancelling a print

To Reproduce

  • Start a print from octopi
  • Cancel it from the printer
  • restart it from octopi

Expected behavior First layer should be right

Video Please attach a video. It usually helps to solve the problem.

adrienafl avatar Feb 25 '24 17:02 adrienafl

Rolled back to 3.13.1, issue is gone

adrienafl avatar Feb 26 '24 09:02 adrienafl

@adrienafl Just verified that it is working with 3.13.3 and previous versions. Do you have in OctoPrint -> Settings -> GCODE Scripts

  • After print job is cancelled M603
  • After print job is paused M601
  • Before print job is resumed M602

3d-gussner avatar Mar 08 '24 09:03 3d-gussner

Only thing I have is : After print job is cancelled

; disable motors
M84

;disable all heaters
{% snippet 'disable_hotends' %}
{% snippet 'disable_bed' %}
;disable fan
M106 S0

How would I only have the issue with 3.13.3 and not 3.13.1 ? From what I've seen it looked like the printer wasn't taking in account my Z fin adjustment settings when starting a new print after one cancelled

adrienafl avatar Mar 08 '24 10:03 adrienafl

I just observed this same behavior in 3.13.3 on my MK3S. First layer calibration looks good and runs correctly. As soon as I go to print It commands the nozzle high. The LCD said it was commanding a height of 0.4 instead of 0.2.

I tested with the print twice before resetting and it happened consistently. Hard resetting the printer via the button allows this to run correctly again.

eltron247 avatar Apr 10 '24 18:04 eltron247

I rolled back to 3.13.1 and issue is gone. I'll upgrade to MK3.5 soon so I didn't want to investigate furtger

adrienafl avatar Apr 10 '24 19:04 adrienafl

This issue has been flagged as stale because it has been open for 60 days with no activity. The issue will be closed in 7 days unless someone removes the "stale" label or adds a comment.

github-actions[bot] avatar Jun 10 '24 01:06 github-actions[bot]

This issue has been closed due to lack of recent activity. Please consider opening a new one if needed.

github-actions[bot] avatar Jun 17 '24 01:06 github-actions[bot]