Fun discovery of the day: PrusaSlicer (at least for the Mini) actually _enforces_ the machine limits by emitting appropriate G-code when slicing. Among other things, this means that if you want, say, higher accelerations, you can just request them.
This is probably because the Mini can't save anything to EEPROM, which means any change to presets requires a firmware upgrade.
@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.
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.
@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.
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?
@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
"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.
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.
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.
The short answer to this is no, because contributions cannot be merged back: Non-commercial licenses are effectively one-way.
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.
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.
If Prusa is serious about balancing open source and capitalism they need to create a foundation that escrows source code that is legally bound to publish it after X years have passed. Prusa will then get a small edge and we will reap the benefits. Everyone's happy.
But I get the feeling they want exclusive rights over their code FOREVER, well past the date it is useful as a trade secret. This is not an acceptable compromise.
I actually had a falling out with the #HeroMe developer. He actually took the product over from someone else when it was open. And now, "to help support development," he wants monthly subscriptions.
Bullshit. He doesn't put out enough to justify a permanent subscription. Also, once you build it, why do you even need a subscription and support. It is not as complicated as a printer or #Voron where you need constant support.
Furthermore, he bombards you with "free" files. A folder with 100s of files, pretending he supports every single printer.
Then you buy the instructions because you are overwhelemed and then on the third page it shows all the printers which are unsopported.
You need to pay to see if your printer is not supported. I bought it and publicly shared that page, and he copyright striked me, and his followers attacked me online as if it is some cult.
He is a money grabber. Some of the pay-wall information should be free.
The NC license also means actual commerical printers can't implement this as a baseline toolhead. So we will continue getting bad toolheads forever. Yay!
Also, do we have any news regarding the #Prusa #MMU3 at all? Like we heard some stuff and got a nice trailer for the #MK4 when it was lanuched. But we still don't know anythjng of the MMU3 and based of the MMU and MMU2, it was utter disappointments.
I think I am just going for the #EnragedRabitCarrotFeeder
@Stark9837 @LordofCandy @koz @3dprinting J. Průša mentioned it briefly in the summer update on June 15. (two paragraphs near the end)
https://blog.prusa3d.com/prusa-summer-update-mk4-xl-mmu3-assembly-kits-and-more_79420/
A couple of incredibly busy weeks are behind us. I went on a tour around the North America (which was amazing!) and meanwhile, the team back at the HQ managed to wrap up a ton of things - both figuratively and literally....
@OttersDangerDen @Stark9837 @LordofCandy @koz @3dprinting I got a good pic of it. Much simpler construction, and uses a linear rail so less complex parts.
Didn't look at the filament sensor part, I may adapt the ERCF one I brought to MRRF.
@reprapryn @OttersDangerDen @LordofCandy @koz
Here, it is directly from the manual
Source: https://github.com/EtteGit/EnragedRabbitProject/blob/main/Documentation/ERCF_Manual.pdf
@reprapryn @OttersDangerDen @LordofCandy @koz
Here is the repository for those interested: https://github.com/EtteGit/EnragedRabbitProject
@Stark9837 @OttersDangerDen @LordofCandy @koz @3dprinting little bit different. It's the part in the selector carriage used as an antijam sensor and presence sensor.
The head filament sense sensor you don't actually need and ERCF and others new versions aren't using it anymore. The selector sensor is necessary though.
Koz Ross
Stark
Jookia
Andy
Kernel Bob 
OttersDangerDen
Rep Rap Ryn :3
