Could not resume paused print
I was printing a part but I noticed the infill was not complete enough so I thought extruder idler tension may need a push. So I paused the print and turned the two tensioning screws a bit more.
When resuming the print I noticed the target hotend temperature was 0 and the LCD status line was saying "heating..." forever.
I could not resume that print and I had to restart it.
Using firmware 3.1.1 on a brand new MK3.
Is there anything I could have done to trigger that problem (or to exit from that situation once it happened).
It looks firmware error to me so far.
Thanks,
misan
Re: Could not resume paused print
Change filament it requires you to take out and re insert the filament. But does allow restart after pausing with the extruder out of the way.
Regards Joan
I try to make safe suggestions,You should understand the context and ensure you are happy that they are safe before attempting to apply my suggestions, what you do, is YOUR responsibility. Location Halifax UK
Re: Could not resume paused print
Same problem. Pause pretty much kills the print and never recovers. It says heating and never recovers.
Re: Could not resume paused print
Has anyone put together a troubleshooting guide with all of the things people have experienced? Being new at 3D printing it would be great to have a list of everything to check on a certain situation.... ie... X,Y,Z axis and live Z, PINDA probe, thermistor sensor and more.
When I get my MK3 I'm going to go slower at putting it together. At each step before I start I want to research all the issues since MK3's have shipped and include changes in all of the build.
Was just wondering if there's something like this that I could add to. Once it's compiled maybe put something together like the "shipping tracking sheet". Everyone could have inputs and new people could reference the link for initial troubleshooting.
Re: Could not resume paused print
It looks firmware error to me so far.
Yes, it's a known bug that has been confirmed by many, spanning back several versions of firmware. Would love to see this fixed. Seems like a simple one.