PrusaSlicer VS mk3-32u2-firmware

I do this with my Prusa MK3S with MMU2S. It cannot be done without this fix in PrusaSlicer, however (which hasn't been merged into a release).

If you’d like to support my request https://github.com/prusa3d/PrusaSlicer/issues/11102 and leave a comment or a 👍. Any support is welcome and helps to get this feature implemented in PrusaSlicer. Thank you in advance!

That's it. I haven't seen many mentions of global variables other than This GitHub page from March so I hope this helps people.

Example: "The feature was ported from BambuStudio, thanks to @bambulab for the initial implementation." https://github.com/prusa3d/PrusaSlicer/releases/tag/version_2.6.0-beta4

It may be worth filing a feature request issue for your use case with the PrusaSlicer project.

There is an issue with PrusaSlicer that needs to be fixed to make it work for true multi-material printing. At this time, the nozzle can jam when switching from a high temperature to a lower temperature filament, because the purge is attempted at the lower temperature, which can cause the nozzle to jam. I fixed it in this PR (so that purging happens at the higher of the two temperatures) but it never got merged into the current release, and given the PR backlog, I doubt it ever will. In any case, that fix converts the MMU into a true multi-material printer. I can now print PLA with PETG supports, for example. Or mix PLA with PLA+. I have to use my own PrusaSlicer build to do this, however.

Hi, I have a project based on https://github.com/prusa3d/PrusaSlicer/tree/master that I want to create a .app for to try on another laptop. however i just can't figure out how. it seems like xcode build will do that for you, however upon using cmake with -GXcode it does create a project and I can debug/run my app with it. but there is no .app within the file structure.

If anyone is having issues it such a simple fix with a Arduino Uno and these instructions: https://github.com/PrusaOwners/mk3-32u2-firmware

Note: The Einsy boards sold by Prusa have defective firmware on the usb-to-serial chip that make the boards unusable with Klipper (boards sold by Ultimaker do not have this issue). See https://github.com/PrusaOwners/mk3-32u2-firmware for a fixed usb-to-serial firmware.

Yes and no. It was worth it for tinkering and learning. My Prusa is now barely recognizable as one because i went on a quest for speed after getting into klipper and input shaper. I have retained almost all of the Prusa features through some nice configs. But the machine is way less reliable. A word of warning would be that you have to flash a new firmware to the usb-to-serial chip of the Einsy Rambo of the mk3 to reliably use Klipper, which needs additional hardware.

You can totally run klipper with an ATMega board but it's a bit involved getting to work on the prusa enisy rambo board as you have to change the usb <-> serial controller firmware as described here https://github.com/PrusaOwners/mk3-32u2-firmware

According to this the pins on the right from top to bottom are VCC MOSI GND

I've had my Ender 3 V2 for a while now and want to upgrade to something nicer. I have my eye on the Prusa MK3S+, but I've seen something about the USB to serial firmware shipped on the board being either slow or defective. I've also seen a (single) more recent comment about how newer boards don't have this issue. Does anyone have insight on this? I know there is a fix, but I'm not sure it's necessary any longer.

But it seems it work if you flash your own firmware. Bit of effort though. https://github.com/PrusaOwners/mk3-32u2-firmware

Add to that, connecting the Pi GPIO to the Einsy headers (like with a Zero) works, it's less reliable than over USB. USB isn't without issue, although there is a fix available.