Notifications
Clear all

Resume after pause problem  

  RSS
NarlyB
(@narlyb-2)
Active Member
Resume after pause problem

I paused the printer for really loud harmonic noise to check Y axis lube.

On resume the print head was a bit to low and the filament was not able to feed. The nozzle started to scrape the previous layer. 

The extruder was making that skip sound and the filament was not extruding.

The printer did not throw an error.

The print was a fail

Verified filament extrudes by forcing a filament change.

Has anyone experience this.  This was my second print on this printer.

Posted : 22/02/2025 4:30 pm
1 people liked
j3llyh34d
(@j3llyh34d)
Active Member
RE:

I've also seen issues with resume.  In my case it attempted to resume ~4mm above where it should.  

That bug is my only failed print in 100+ hours printing over the last week.

Mini+, MK4+MMU3, MK4S, Core One, XL.

Posted : 23/02/2025 3:39 pm
LordMelkor
(@lordmelkor)
Eminent Member
RE:

I'm having the opposite issue... on resume the nozzle isn't going low enough, so the filament doesn't adhere properly. Was able to replicate--same object paused at different heights. when I went to resume it missed by ~1 layer, causing failure.

Posted : 23/02/2025 6:13 pm
LordMelkor
(@lordmelkor)
Eminent Member
RE: Resume after pause problem

Posted : 23/02/2025 6:19 pm
AlanB
(@alanb)
Member
RE: Resume after pause problem

I just experienced a resume after pause problem on my CORE One. Current 6.3.0 firmware. Momentary pause to pull a bit of junk off the printhead sock, on resume the motions were loud and jerky, and the print was failing. It appeared the acceleration had gone much too high, motions were no longer smooth and quiet. Lost 2 hours of print time and material. 2.9.0 PrusaSlicer. Will avoid pause until this is addressed. I've had pause work, so apparently there is some race condition where parameters get lost.

 

Posted : 20/03/2025 7:16 pm
WarezMonkey
(@warezmonkey)
Trusted Member
RE: Resume after pause problem

I am pretty sure this is the same issue: it has been reported in other posts and in github. Prusa is already bundling a fix into the next firmware: https://github.com/prusa3d/Prusa-Firmware-Buddy/issues/4505#issue-2889065150

 

Posted : 21/03/2025 5:47 pm
Share: