4.1.0 Firmware for Original Prusa MINI  

RE: 4.1.0 Firmware for Original Prusa MINI

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.

RE: 4.1.0 Firmware for Original Prusa MINI

Try zipping the file and adding the zipfile. 

Regards joan

RE: 4.1.0 Firmware for Original Prusa MINI

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.

RE: 4.1.0 Firmware for Original Prusa MINI

@zoltan

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

RE: 4.1.0 Firmware for Original Prusa MINI

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.

RE: 4.1.0 Firmware for Original Prusa MINI

@stephen-c32

Great, so we know which code is guilty.

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

RE: 4.1.0 Firmware for Original Prusa MINI

@zoltan

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

RE: 4.1.0 Firmware for Original Prusa MINI

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.

RE: 4.1.0 Firmware for Original Prusa MINI

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.

Alternative method to flashing Mini firmware?

Hey guys, 

I have a Prusa Mini and the USB-A port has died and NO USB thumb drives are recognized when plugged into this port on the Mini... I would like to note that ALL the USB thumb drives I was using on the Mini work just fine in my desktop PC and I have reformatted several of them with FAT 32 as specified (I've covered ALL the obvious things that could go wrong).

I am able to get a Raspberry Pi4b to operate fine over the micro-USB port and was wanting to flash this firmware through an Octoprint plugin called "Firmware Updater" that has worked on others Prusa MK3's... has anyone been able to get this to work for the Mini? If so, what are the settings supposed to look like inside the firmware updater plugin.

I'm hoping this firmware update will resurrect my USB-A port as it was working just fine. 

Thanks for your assistance. 

RE: re

@dakar

does your printer work? Are you able to print anything via USB stick?

Do you have any guess what made your USB going south?

Can you describe in details what happened? Did your USB die before you started to update via octoprint, or vice versa?

FW update via micro USB does not work.