@koz

So the Mini doesn't have an EEPROM?

@3dprinting #3dprinting

@Stark9837 @3dprinting Here's the funny thing: it absolutely does, you just can't write to it. Prusa's firmware builds disable the Marlin build flag that permits this. If you use a firmware build with this enabled, you can save no problem.

The reason you can't just fix this yourself is because Prusa's firmware is signed, and without a physical mod to the board, you can't flash anything whose signature won't match.

@koz

Sounds like it is about time we fork it and make firmware and changes that it needs that the community can update their printers. #Opensource off course.

@3dprinting #3dprinting

@Stark9837 @3dprinting Someone already did that: https://github.com/matthewlloyd/Llama-Mini-Firmware#readme

Unfortunately, this isn't an optimal solution because

1. It's not maintained and is quite behind now; and
2. You can't flash it anyway unless you want to physically modify the board.

However, in principle, I totally agree. Prusa's recent 'commitment' to open source feels like empty words.

@koz

Whay physical changes to the board do you need to make? Also, does it void the warranty and restrict you from returning to the original firmware?

#Prusa #PrusaMini #Mini @3dprinting #3dprinting

@Stark9837 @3dprinting Yes, this will void the warranty, but won't restrict you from returning to original firmware.

The change is described here: https://help.prusa3d.com/article/flashing-custom-firmware-mini_14

@koz

"To flash your own (or a community-made) unsigned firmware, you’ll have to break the appendix on the logic board (called the Buddy board) and move the jumper in a correct position. Breaking the appendix on the Buddy board is irreversible and voids the warranty of your printer’s electronics."

Sounds a lot like those encryption boards you get. Whick I think #Bambu went crazy with, but tehirs are part of the #PCB, so it is more difficult to bypass it. I am quite surprised that not a lot of people have just removed the hardware from the #X1C and just installed #Klipper.

Probably because then you lose the beautiful touch display and wase of use of the #AMS. Although Klipper has many good color changers.

@3dprinting #3dprinting

@jookia @koz

I welcome new licenses, and #Prusa is an excellent partner to do so because they can afford the laywers that we need to construct new licensing.

@3dprinting #3dprinting

@koz @jookia

This really isn't my specially and would love a lawyers input. But is it possible to have a license where no one may sell your product, but it is still open and communities can extend and mod it?

Yes, it sounds like most licenses on #Thingeverse and #Printables and a lot like what #Gridfinity has done. But #Prusa keeps on using licensing so that people can actually sell their product.

For example, anyone can just recreate an original i3 or #Ender3

The key is non-commercial use.

@3dprinting #3dprinting

@Stark9837 @koz @3dprinting

The short answer to this is no, because contributions cannot be merged back: Non-commercial licenses are effectively one-way.

@Stark9837 @koz @3dprinting

As a clear example of this, the Hero Me toolhead is non-commercial license but lacks support for the Anycubic Kobra. I will be publishing Anycubic Kobra support hopefully 'soon'.

However the Hero Me creator will not be able to merge these back because he wants to use this work commercially and I cannot let him do that without getting in to a complicated legal agreement.

@Stark9837 @koz @3dprinting

The long answer is you need to beware of licensing systems and contracts in general that favor one party: Prusa's lawyers are not YOUR lawyers, Prusa is not a partner to any binding agreement with the community.

Especially since Prusa can't be trusted when it comes to open source: They don't release source code already for their bootloaders, possibly the most boring part of embedded firmware.