Can't print anymore after failed print  

  RSS
Ingo Richter
(@ingorichter)
Active Member

It's frustrating right now! I've spent countless hours, and I'm sick of having to deal with something like that.

The situation: Every time a print fails, and I have to stop it, and I can't start a successful print anymore. The printer will heat up, do the bed leveling, and then reset. Every time!!! The only solution is to do a factory reset and go through the calibration process again. That is ridiculous and a massive waste of my time.

I have the latest firmware 3.7.1 on my MK3S/MMU2, and I've produced some beautiful prints. But once it fails it will never work again. I've used different SD-Cards and print from my computer. All end up with the same frustrating result.
Does anybody have an idea what's going on and if there is a way to avoid the factory reset to get the print back into a working state?

Posted : 17/06/2019 2:39 am
Greybeard3D
(@greybeard3d)
Estimable Member

I understand your frustration but it sounds like something is faulty. You should work with support to resolve your faulty hardware issue.

Posted : 17/06/2019 5:07 pm
--
 -2
(@-2)
Illustrious Member

I feel your pain, but there's a lot going on that might be the problem.

A reset when the heaters turn on is common when one of the heaters has a problem, like a short in the wiring.  Usually, a factory reset won't fix this.  But there have been stranger problems.

Have you tried printing one of the sample gcodes included with the printer?  This will rule out odd slicer settings that might be causing problems.

Have you turned off the MMU and printed one-color to check if the problem is the printer or the MMU?

 

It is always wise to get more than one opinion... as for trusting Prusa? No way man....
Posted : 17/06/2019 5:13 pm
Ingo Richter
(@ingorichter)
Active Member

Thanks for all your suggestions. I disconnected the MMU2 yesterday and was able to print repeatedly even after a failed build. I don't know what the MMU was doing when there was a failed print, but it looks like something stays behind in the EEPROM and trips it up when starting the next print. I might also be wrong with this assessment...

I'm going to contact support and ask them for a solution. Perhaps they've heard about this issue before.

Posted : 18/06/2019 10:38 pm
Share:

Please Login or Register