4.1.0 Firmware for Original Prusa MINI  

Page 4 / 4
Active Member

Have you flashed this version "Buddy_4.2.1-final+2072.bbf" ?

Or have you flashed an official release? I have the feeling, that official releases do generate this problem.

I attach the file I have flashed for your reference.

Good luck.

Edit: Can't upload the file 🙁 no matter what I try, sorry.

This post was modified 4 weeks ago 3 times by a.schwinn
Posted : 28/09/2020 7:58 pm
Veteran Member Moderator

Try zipping the file and adding the zipfile. 

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...
Posted : 29/09/2020 1:18 am
Active Member

4.1.0 and the updates that have followed have been extremely successful and helpful for me.   I've had no negative issues, and the Load/Unload changes in particular are a vast improvement.

Posted : 29/09/2020 2:12 am
Eminent Member


If I comment out () the M92 line, 4.2.1 works fine. 

Posted : 29/09/2020 2:14 pm
Active Member
Posted by: @joantabb

Try zipping the file and adding the zipfile. 

Regards joan

This was the first attempt I did. I even renamed the extension to e.g. piz and that did not work.
But anyway, the strange thing this evening was that the behavior occurred again. So there seems to be a interaction between the firmware and the g-code. The difference this time was that I used a resolution of 0.1mm and 100% infill. But maybe this is misleading and the root cause is a more tricky one.

Posted : 30/09/2020 8:26 pm
Member Moderator


Great, so we know which code is guilty.

This one is already reported on github, so let us see what is there.

even an old man can learn new things 🙂
Standard I3 mk3s, FW 3.9.1, no closed box, sketchup , fusion 360, PrusaSlicer, Windows 10
PRUSA MINI FW 4.2.1, technical background...
Posted : 01/10/2020 11:43 pm
Active Member


Not really, the code I printed this week has no M92 command, I checked it.

Posted : 02/10/2020 1:03 pm
Reputable Member

I can't imagine why M92 would cause all the issues reported. I think it is more likely a buffering issue, adding/removing code causing different execution paths and some memory to be corrupted. M92 just happens to be a common command people add, it is natural to think whatever was added is the cause, but I think in this case it is a red herring.

Prusa Slicer generates some very long comment lines in the Gcode, I have wondered if those are handled properly. Does Octoprint strip out comment lines? Might explain why the printing from USB and Octoprint behave differently.

Posted : 03/10/2020 9:41 am
Active Member

I totally agree with that opinion. That is the most reasonable explanation to me, based on the experience that some prints show this issue and others not.

I hope Prusa will soon sort this out, because I am really disappointed at the moment about Prusa that we still have this issue, although I know that such a bug is hard to find.

Posted : 03/10/2020 10:25 am
Page 4 / 4

Please Login or Register