mmu3 #19

Dutchy1969 · 2023-07-30T15:43:48Z

any chance we get a fork of the mmu3 firmware and i think 3.13 for the mk3s+ and mk4 support?

i was hoping to get rid of my mk3s+ and move it over to the mk4 i started looking at the firmware and stuff but im not smart enough for that.

grzlus · 2023-07-31T05:28:14Z

I was thinking on porting changes here to TZB firmware, but porting it MMU3 might be better idea.

I want to buy MK4 upgrade too (MK3.5 probably), but I need to find more free time for that 😀

cjbaar · 2023-07-31T14:33:50Z

I have not yet dug into the code, but the MMU3 is a complete re-write, with a total overhaul of the communication protocol. I am guessing it won't make much sense to move my changes into it, because I did a lot of re-writing of the MMU2 code. Also, they have not yet announced what the "Mk4" version of the MMU3 will be. It is my understanding that the printer itself is not a lot more in control of that the MMU does. I am also willing to bet that they still have things like max extruders hard-coded, which could make things tricky.

Once I get the new MMU (probably September) and have a chance to play with it, I will probably decide what to do with this project, and whether or not it can be adapted to the Mk4. Most likely, given that Prusa has added interaction with the printer for troubleshooting, my screen concept will be unnecessary. This would mean the shortest path to compatibility would be minor modifications to the MMU code (rotation directions, distance between filaments, etc), but probably more significant changes to the actual printer code. Also, given that they moved away from Arduino IDE as a compiler, which I am very familiar with, there will be an additional learning curve for me.

greenfox1505 · 2023-08-07T02:02:57Z

Would it make sense to re-implement an MMUx12 from scratch? Sure, a MMU3 upgrade would be ideal, but I don't know if it's necessary. Arduinos and stepper drivers are easy to get. I've got a hand full of old RAMPS boards laying around.

grzlus · 2023-10-30T21:54:41Z

I'll be upgrading to 3.5, so I'll need MK3 upgrade. I'll reuse as many files from current MMUx12, so the original firmware will be only patched to use correct rotations as we have them in the files. I'll probably abandon that firmware, as it will too much to patch changes made by Prusa and it's easier to start from scratch with firmware.

Dutchy1969 · 2023-11-10T12:52:19Z

I can’t wait to have a solution for the 4. I appreciate you guys help. I’m not smart enough for this stuff but if there is anything I can do to help you guys out to get this to work on a Mk4 you let me know.

grzlus · 2024-02-23T11:23:11Z

@Dutchy1969 I'm waiting for my order to be delivered. I'm getting MK3.5 and MMU2S to MMU3 upgrade.

In a month I should have it delivered and put together :)

grzlus · 2024-03-06T21:43:01Z

@Dutchy1969 good news, my 3.5 and MMU3 upgrade was shipped :)

sithlord48 · 2024-05-01T16:37:19Z

TLDR: For an MK3.5+ solution or one allowing the user to use the newer MK3S firmware 3.13+
This firmware must be rebased upon the MMU's 3.x series, or otherwise implement the bi directional communication so the printer can talk to the mmu in the way it expects. Devs could upgrade their MK3S to firmware 3.13 to test an Mk4 or MK3.5 is not required.

There are Two main changes for MMU3

A board that goes between the mmu and the printer
- Stabilizes the power to the mmu
- Replaces the wires that connect the mmu with a single cable. (Store: Mk3S Wire. MK3.5+ Wire)
Firmware changes to both the MMU (3.x series) and the Mk3S(3.13.x)
- Printers with firmware 3.13.0 or higher REQUIRE the MMU to use 3.x firmware
- Enables bi directional communication so the printer can now show mmu errors on the screen. and tell the mmu to retry. No more mmu light based error codes to for those mmu issues!!
- The MMU can be enabled and disabled from the printers menu
- The printer can send firmware to the MMU to upgrade its firmware when you upgrade the printers (an additional .hex for the mmu firmware is included in the mk3S+ mmu package now)

The rest of the new MMU3 stuff does not matter for this project since its all printed parts. A better idler, housing lid etc.. that will not be used in this project.

For my Mk3S+ MMU2S I got the new power board and I was then able to use the 3.x firmware. Since then i have been using the " MK3S+ MMU3" profile without issue

For the MK4 / 3.5+ the only change to the MMU3 (kit) is the wire you use to hook it up to the printer.

Johnday29 · 2024-07-05T08:41:23Z

Just checking in here. Let me say your mods to the MMU2 have been a game changers for my little 3D printing business, so Big thank you to @cjbaar . That being said I have upgraded a couple of my printers to MK4 with MMU3 and must say it is night and day difference the speed and quality of prints I get, This means I really want to upgrade my MMU2 x 12 to MMU3 x 12. Has there been any progress in this area? Would be happy to contribute to make it happen. Thanks!

cjbaar · 2024-09-27T17:30:00Z

Sorry @Johnday29. I'm glad you have used the 12x successfully. I have not had any chance to look into what it will take to get this working with MMU3.

Johnday29 · 2024-09-28T14:48:48Z

Thanks for the reply. Please let me know if I can contribute to the effort to get this going with the mmu3 software. It runs so much smoother and with Mk4 compatibility it is so much faster would love a boost to the 12x 😎.

…

On Fri, Sep 27, 2024, 12:30 PM cjbaar ***@***.***> wrote: Sorry @Johnday29 <https://github.com/Johnday29>. I'm glad you have used the 12x successfully. I have not had any chance to look into what it will take to get this working with MMU3. — Reply to this email directly, view it on GitHub <#19 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AD5JNMHSDBXDAWFHTI3AIWDZYWI27AVCNFSM6AAAAAA25ISHN6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZZG42TCNBRGM> . You are receiving this because you were mentioned.Message ID: ***@***.***>

3d-gussner · 2024-09-30T17:58:55Z

@cjbaar The new MMU firmware has way less hard coded values and lot of that can be defined in https://github.com/prusa3d/Prusa-Firmware-MMU/blob/main/src/config/config.h and https://github.com/prusa3d/Prusa-Firmware/tree/MK3/Firmware/mmu2/variants and https://github.com/prusa3d/Prusa-Firmware/blob/MK3/Firmware/variants/MK3S.h#L673

Also have a look at https://prusa3d.github.io/Prusa-Firmware-Doc/Prusa-Firmware-MMU/index.html

But i doubt that you get the LCD display working as it consumes too many resources.

Here a build output of MMU3 _3.0.3

[build] AVR Memory Usage
[build] ----------------
[build] Device: atmega32u4
[build] 
[build] Program:   28370 bytes (86.6% Full)
[build] (.text + .data + .bootloader)
[build] 
[build] Data:       1669 bytes (65.2% Full)
[build] (.data + .bss + .noinit)
[build] 
[build] 
[build] 
[build]    text	   data	    bss	    dec	    hex	filename
[build]   27678	    692	    977	  29347	   72a3

cjbaar · 2024-09-30T21:13:21Z

@3d-gussner That does look halfway promising. I do see variables for the selector start position and distances. It looks like the idler creates a hard-coded array of positions, instead of just constant motor steps. This can be created, but might take some tweaking. One thing I don't see is an easy way to reverse the motor directions, since some of mine are on opposite sides than the original. Maybe if you see that, let me know.

The bigger issue, then, is on the printer side itself. Will the printer accept 12 tools? The older firmware was hard-coded to throw away any g-code above T4, and also would only display sinlge-digit numbers on the screen. Any idea what that code looks like for the Mk4 board?

cjbaar · 2024-09-30T21:22:33Z

@3d-gussner OK, according to axis.h, dirOn might actually reverse the motors

cjbaar · 2024-09-30T21:23:44Z

And, of course, there is this warning. :)

/// Max number of extruders/tools/slots
/// Beware - if you change this, the EEPROM structure will become invalid and no migration procedures have been implemented.
/// So if you really have to change this, erase your EEPROM content then.
static constexpr const uint8_t toolCount = 5U;

cjbaar · 2024-09-30T21:45:30Z

See its a quick scan of the buddy firmware showing things like this that makes me think the printer won't cooperate without a lot of changes.

enum class Tool {
    Tool1 = 0,
    Tool2 = 1,
    Tool3 = 2,
    Tool4 = 3,
    Tool5 = 4,
    None_Any = PrusaToolChanger::MARLIN_NO_TOOL_PICKED, // Park value
};

Johnday29 · 2024-09-30T22:54:30Z

While this is really mostly above my head at this point I am excited you all are looking into it. Please let me know if I can assist with anything. Thanks.

…

On Mon, Sep 30, 2024, 4:45 PM cjbaar ***@***.***> wrote: See its a quick scan of the buddy firmware showing things like this that makes me think the printer won't cooperate without a lot of changes. enum class Tool { Tool1 = 0, Tool2 = 1, Tool3 = 2, Tool4 = 3, Tool5 = 4, None_Any = PrusaToolChanger::MARLIN_NO_TOOL_PICKED, // Park value }; — Reply to this email directly, view it on GitHub <#19 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AD5JNMFAT6S2HRDGNRENI6TZZHBBDAVCNFSM6AAAAAA25ISHN6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOBUGIYDGNZSGQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

cjbaar · 2024-10-01T22:46:55Z

So.... this is interesting.
"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."

Johnday29 · 2024-10-01T23:13:28Z

Well that is Just wrong. Prusa is usually better than that.

…

On Tue, Oct 1, 2024, 5:47 PM cjbaar ***@***.***> wrote: So.... this is interesting. "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." — Reply to this email directly, view it on GitHub <#19 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AD5JNMABCPJ5ZWSOU3YHM5TZZMQ7LAVCNFSM6AAAAAA25ISHN6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOBXGIYTMNBXGE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

cjbaar · 2024-10-03T17:38:29Z

OK, I've got some good news, some great news, and some possibly discouraging news.

I have a working prototype of the MMU3 (x12) on the Mk4. It requires re-compiling the code with custom values in config.h, but no other code changes. It will work as a standard MMU3 with all the new interactive features, meaning the printer will display error codes. The mini OLED screen is no longer active. I prefer my use of the screen and buttons, but putting that into the new code would not be beneficial at this point.
The Mk4 firmware, as-is (6.1.3) forwards ALL T-codes from the sliced file. This means the 12x works without any modification to the printer or its firmware (other than Nextruder sensor updates required for the MMU3).
I cannot get this to work with my older MMU control board, even though it seems identical to the new one. I think this is probably more bootloader or eeprom-related, but I cannot solve it right now. This means that you would probably need a brand new MMU3 board... whatever that difference is. Your results may vary.

I will post more once I have completed further testing. Of course, all of this also depends on Prusa not making any major modifications that block any of it... like suddenly cutting out extra T-codes (like the Mk3 did). I also don't know what will happen once the Prusa firmware becomes in charge of uploading the MMU firmware, which is supposed to occur in the near future. We will have to see if the printer firmware at that point will allow custom-loaded MMU configs.

cjbaar · 2024-10-03T17:39:51Z

@3d-gussner How are you getting that build output you show above? I am using the python build script, as described in the instructions. I only ever get "SUCCESS" or "FAILURE" as an output, which clearly isn't helpful when its the latter.

3d-gussner · 2024-10-04T05:18:29Z

@3d-gussner How are you getting that build output you show above? I am using the python build script, as described in the instructions. I only ever get "SUCCESS" or "FAILURE" as an output, which clearly isn't helpful when its the latter.

I use VScode and some extensions like cmake, cmake integration.

After installing VScode and at least these two extensions execute ./utils/bootstrap.py to ensure that you have all .dependencies.
You should then see in the bottom line CMake: [Release]: Ready <wrench+driver_icon> [avr-gcc] . Press on Build

Building with cmake will output more information.

The build.py scripts intentionally only output SUCCESS or FAILURE to make it easy for beginners.

Hope that helps

Johnday29 · 2024-10-05T22:35:24Z

Can't wait, I'm very excited!! Thanks for the hard work.

…

On Fri, Oct 4, 2024, 12:18 AM 3d-gussner ***@***.***> wrote: @3d-gussner <https://github.com/3d-gussner> How are you getting that build output you show above? I am using the python build script, as described in the instructions. I only ever get "SUCCESS" or "FAILURE" as an output, which clearly isn't helpful when its the latter. I use VScode and some extensions like cmake, cmake integration. After installing VScode and at least these two extensions execute ./utils/bootstrap.py to ensure that you have all .dependencies. You should then see in the bottom line CMake: [Release]: Ready <wrench+driver_icon> [avr-gcc] . Press on Build Building with cmake will output more information. The build.py scripts intentionally only output SUCCESS or FAILURE to make it easy for beginners. Hope that helps — Reply to this email directly, view it on GitHub <#19 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AD5JNMBDQYUOLNYEGISMR43ZZYQLXAVCNFSM6AAAAAA25ISHN6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJSHA2DEMZQHE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

cjbaar · 2024-10-18T19:22:29Z

It is done. Works for now. New STL files uploaded for v3.3

Dutchy1969 · 2024-10-18T19:29:26Z

Man congratulations this is AWESOME, I currently don't have a mk4/mmu3 setup I switched to the XL but it's way overkill for what I do. I might just sell it off and go back to a mk4 with now a MMu3/12 thank you so much!!!!!

Does works for now mean it works with the older MMu boards as well or would it need a new board

cjbaar · 2024-10-18T19:39:49Z

@Dutchy1969 I still have some questions around the board. I could not get my older one to communicate. The firmware loads, and the MMU is operational (homes, buttons move/load) ... but the printer doesn't see it. I cannot figure out why, and so far Prusa support wasn't much help. The boards have not changed, but I cannot tell what is keeping the previous board from working.

sithlord48 · 2024-10-19T00:33:18Z

do you have the new adapter w/ power stablizer in it ?

A board that goes between the mmu and the printer

Stabilizes the power to the mmu
Replaces the wires that connect the mmu with a single cable. (Store: Mk3S Wire. MK3.5+ Wire)

cjbaar · 2024-10-19T12:37:18Z

@sithlord48 Yes, I am using the power board with testing both boards

sithlord48 · 2024-10-19T13:15:29Z

Is there a way to tell the Old and New board apart ?
Do we know how many "revisions" there could be ? Or anyidea what we do to make the old board the new board ?

cjbaar · 2024-10-19T14:29:10Z

Yes. My older board says "Rev 0.3" and the new one "Rev 0.4.4". Both are "sheep edition." I don't think there were any major changes in hardware that should affect this, but I am not clear. Also not sure if (or how) the boot loader might affect this. The "older" one is running and moving, but just doesn't answer the printer somehow. I am not sure how to go about debugging that.

Biertram · 2024-10-27T20:34:02Z

Hi cjbaar,
I thank you for this update. It is godsend.

Currently I am running a MK3S+ with an MMU2 and the 1.4 12xMMU-Body.
As the MK3 firmwares require exactly V3.0.2 on the MMU2, I applied most of your config.h to that version and for now the communication seems fine. Both through the MK3 menu and the USB-Terminal (Octoprint in this case).

I did have to modify the Tcodes.ccp in the MK3 firmware though, as it had a check to see if the Tcode is between 0 and 4.

I started to unmothball my MK3 about three weeks ago and tried to get it running with the new firmware and there was still some fiddling left for me to get the parameters in the config.h right. So thank you again for this update. It really helped a lot.

cjbaar · 2024-10-27T21:53:04Z

@Biertram Glad to hear it. I have not tested it on the Mk3, so glad you had success with it. The Mk3 firmware continuing to block T codes is very annoying, since it is such a simple change.

3d-gussner · 2024-10-28T07:27:56Z

@Biertram 👍 Could you share your changes you have made to the Prusa-Firmware?

@cjbaar I was searching in the Prusa-Firmware repository Pull Requests and frankly it looks like your changes or your branch have been deleted and I can't see the differences any more.

cjbaar · 2024-10-28T15:04:34Z

Yeah, I am sure they deleted that PR long ago. It was actually at 3.9.x, IIRC. Here is my fork of 3.11: https://github.com/cjbaar/Prusa-Firmware

Biertram · 2024-10-28T18:09:26Z

@3d-gussner Sure.

Let me preface this with the info that I am not a software engineer, I just know enough to get myself into trouble.

I currently run my MK3 on the firmware build MK3S_MK3S+_FW_3.14.1_ENGLISH.
Originally this version is meant to run with MMU2 V3.0.3. I faintly remember, that there was some trouble with getting it to work, so I tried to roll back the MMU2 to V3.0.2, which wasn't accepted by the version check of the MK3S+ firmware.

So these are the changes I made:
Tcodes.cpp:
L14-16:
inline bool IsInvalidTCode(char *const s, uint8_t i) {
return ((s[i] < '0' || s[i] > '11') && s[i] != '?' && s[i] != 'x' && s[i] != 'c'); //T-Code set from 4 to 11 for 12 filaments
}

MK3S.h
L673;
#define MMU_FILAMENT_COUNT 12

mmu2_supported_version.h
L8:
static constexpr uint8_t mmuVersionPatch = 2; ///Default = 3

errors_list.h
L295:
static_assert(MSG_DESC_FW_UPDATE_NEEDED[szFWUN - 3] == ('1' + mmuVersionPatch)); ///Default = ('0' + mmuVersionPatch)

In the MMU2 V3.0.2 I applied cjbaar's config, except for the stepsPerUnit on the Pulley configuration (config.h L118):
Here I kept .stepsPerUnit = (200 * 8 / 19.147274), instead of .stepsPerUnit = (200 * 8 / 37.384921), as the former worked quite well for me.

cjbaar · 2024-10-28T18:17:50Z

@Biertram Nice job

Biertram · 2024-10-28T19:11:23Z

Thank you.

I don't quite remember what the issue with V3.0.3 was, but maybe going back to V3.0.2 might fix your communication issues as well.

I just tried flashing my MMU with my V3.0.3 version, but this time it worked... Strange...
I did change the version number to go with the check in my MK3S though, so I didn't have to reflash it as well.

Edit: Would a copy of my memory dump be of any help to you?

cjbaar · 2024-10-28T21:06:07Z

@3d-gussner So it looks my communication issues are the result of a bad resistor on the board. The TX line (R2) should be 22ohm, but is measuring well over 1K. For whatever reason, the Mk3 works fine with this, but the Mk4 drops bytes.

3d-gussner · 2024-10-29T06:26:37Z

@Biertram Thanks for sharing.

3d-gussner · 2024-10-29T06:45:36Z

@cjbaar I looked at my rev 0.3 board and R2 is labeled as 022 the same as R1 next to it. This matches also the schematics
With my cheap multi-meter (set to 2000 Ohm or 200 Ohm) I measure 23 - 26 Ohm on both R2 and R1 when disconnected from the printer. Never tried to use this board on the MK4 to see if there is a difference.

Replacing the tiny 0603 R2 resistor isn't fun.

How do you connect the rev 0.3 board to the MK3S? Using the MMU2S cables or new PD board and matching cables which are part of the MMU2S to MMU3 upgrade?

Not sure but the PD board also has some components on the TX RX lines and these may have "tighter" tolerances what is expected.

3d-gussner · 2024-10-29T07:24:10Z

@Biertram memory dumps are really hard to read and it doesn't make sense in this case.

Here I kept .stepsPerUnit = (200 * 8 / 19.147274), instead of .stepsPerUnit = (200 * 8 / 37.384921), as the former worked quite well for me.

This value should be changed as the pulley diameter is different than the stock one.

Biertram · 2024-10-29T10:59:45Z

Oh right... I confused pulley diameter and selector angle when I did the configuration...

The original value didn't give me any trouble yet. But I'll change it to 37.384921 to account for the diameter.

3d-gussner · 2024-10-29T12:04:20Z

@Biertram The new MMU firmware is more forgiving on how much filament has been pushed/pulled. It relies more on the states of the FINDA and FSensor than the actual length pushed or pulled. You may be lucky in the previous configuration that the FINDA and FSensor triggered in the thresholds.

cjbaar · 2024-10-29T14:51:08Z

@3d-gussner > How do you connect the rev 0.3 board to the MK3S? Using the MMU2S cables or new PD board and matching cables which are part of the MMU2S to MMU3 upgrade?

Excellent point. I am connecting to the Mk3 with the legacy connectors, so it is probably the PD board that has issues with the faulty resistor. It's not a big deal for me, as I currently don't plan to upgrade my Mk3, but wanted to make sure it wasn't an issue for others trying to upgrade. Thanks for the input.

3d-gussner · 2024-10-30T08:00:52Z

How do you connect the rev 0.3 board to the MK3S? Using the MMU2S cables or new PD board and matching cables which are part of the MMU2S to MMU3 upgrade?

I used the MMU2S cables to connect the rev 0.3 board to the MK3S and it works.
As I have the new MK3S to MMU3 PD board cable I use that one as the PD board improves the Power Delivery.

I have been looking for the differences of the rev 0.3 vs 0.4.4 and I found that the F2 fuse is different

0.3 has a 750mA b0075
0.4.4. has a 1.5A b150 24

Guess that the bigger fuse improved the usage of the MMU2/S on the 12V MK2.5/S printers

Excellent point. I am connecting to the Mk3 with the legacy connectors, so it is probably the PD board that has issues with the faulty resistor.

I measured the resistance with my multi-meter between the MMU connector TX / RX pins and MK3.5/S, MK3.9/S and MK4/S Connector TX / RX pins on the PD board and get ~330Ohm.

This means

MMU <-----------> MK3S no PD
TX  -> 22 Ohm  -> RX
RX  <- 22 Ohm --- TX

MMU <----------> PD board <-> MK3S with PD
TX  -> 22 Ohm -> 330 Ohm ---> RX
RX  <- 22 Ohm <- 330 Ohm ---- TX

3d-gussner · 2024-11-06T15:25:13Z

Check if that is working for you https://github.com/3d-gussner/Prusa-Firmware/tree/MK3_MMU3_12x
I don't have the MMU12x but like the idea and spend some free time on that.

Prusaprinter44 · 2024-11-11T17:37:06Z

Check if that is working for you https://github.com/3d-gussner/Prusa-Firmware/tree/MK3_MMU3_12x I don't have the MMU12x but like the idea and spend some free time on that.

Does this link have the hex file for the firmware on the mk3s and the new mmu12 firmware? I am having a hard time finding the files.

Prusaprinter44 · 2024-11-11T18:45:45Z

@3d-gussner Sure.

Let me preface this with the info that I am not a software engineer, I just know enough to get myself into trouble.

I currently run my MK3 on the firmware build MK3S_MK3S+_FW_3.14.1_ENGLISH. Originally this version is meant to run with MMU2 V3.0.3. I faintly remember, that there was some trouble with getting it to work, so I tried to roll back the MMU2 to V3.0.2, which wasn't accepted by the version check of the MK3S+ firmware.

So these are the changes I made: Tcodes.cpp: L14-16: inline bool IsInvalidTCode(char *const s, uint8_t i) { return ((s[i] < '0' || s[i] > '11') && s[i] != '?' && s[i] != 'x' && s[i] != 'c'); //T-Code set from 4 to 11 for 12 filaments }

MK3S.h L673; #define MMU_FILAMENT_COUNT 12

mmu2_supported_version.h L8: static constexpr uint8_t mmuVersionPatch = 2; ///Default = 3

errors_list.h L295: static_assert(MSG_DESC_FW_UPDATE_NEEDED[szFWUN - 3] == ('1' + mmuVersionPatch)); ///Default = ('0' + mmuVersionPatch)

In the MMU2 V3.0.2 I applied cjbaar's config, except for the stepsPerUnit on the Pulley configuration (config.h L118): Here I kept .stepsPerUnit = (200 * 8 / 19.147274), instead of .stepsPerUnit = (200 * 8 / 37.384921), as the former worked quite well for me.

Are you currently running the mk3s with the new mmu12/mmu3 update?

3d-gussner · 2024-11-12T06:05:39Z

@Prusaprinter44

Does this link have the hex file for the firmware on the mk3s and the new mmu12 firmware? I am having a hard time finding the files.

No there is no hex file. That is just the source code and I think it would make sense if @cjbaar looks into that, compiles it and publishes it here. It is his project, just trying to help.

Are you currently running the mk3s with the new mmu12/mmu3 update?

No I don't run the MMU3_12x at the moment.

Biertram · 2024-11-12T09:51:03Z

I run the MK3s with the MMU2.
If I understand it correctly the MMU2 and 3 use the same firmware.

Above I noted my changes to the MK3S firmware I did myself, to get the MMU and the MK3S working together. Unfortunately there are few more changes to it, for proper display of the menus and such, which I didn't change as they didn't bother me.
So it might be a quite a bit more work for cjbaar if he wanted to publish that as well.

3d-gussner · 2024-11-12T13:03:11Z

@Biertram Look at my fork https://github.com/3d-gussner/Prusa-Firmware/tree/MK3_MMU3_12x This should have all LCD fixes included

3d-gussner · 2024-11-12T13:07:44Z

@Biertram

If I understand it correctly the MMU2 and 3 use the same firmware.

Yes MMU2S and MMU3 firmware are the same.
Only difference between these two is the hardware, plastic parts and the PID control board + cable. See https://www.prusa3d.com/en/product/original-prusa-mmu2s-to-mmu3-upgrade-for-mk3s-4/
Some MMU2S may need adjustments via M707 M708 gocde commands to work correctly.

cjbaar · 2024-11-12T15:32:11Z

I have a hex file in the firmware directory of this repo for the MMU3, which would be the same for either the Mk3 or the Mk4. I have renamed it "cjb_fw_mmu3_3.0.3-x12.hex" to avoid confusion on the printer side. However, I am not currently working on any Mk3 firmware that supports this.

3d-gussner · 2024-11-29T15:17:33Z

@cjbaar I published the firmware 3.14.1 for the MMU12x on my github fork https://github.com/3d-gussner/Prusa-Firmware/releases/tag/c3.14.1_MMU12x

Feel free to copy the repo or link to that release.

jasonmatthews41 · 2024-12-21T02:41:35Z

I just have to say, I downloaded and flashed everything you created for the MMU12. I originally bought the MMU3 from Prusa, never got around to using it. I immediately dismantled it, and built this MMU12. Right out of the gate, it worked flawlessly. I just want to say thank you so very much!

cjbaar · 2024-12-21T14:28:26Z

That's great, @jasonmatthews41. Thanks for the feedback. I made several physical changes on the old design that I personally felt made things easier to work with, but for the MMU3 firmware, most of the reliability credit goes to Prusa.

jasonmatthews41 · 2024-12-24T16:03:10Z

Oh... BTW, @cjbaar, I don't know if you've mentioned any of this? But it works just fine with the MK4S. You absolutely do need to use the silicone sock for the heater block. With rapid changes, it struggles with the MK4S overkill cooling fan. I went through 2 heaters, and a thermistor, before realizing the MK4S already has issues with thermal over temp, due to it's fan. It's 5 times worse with the MMU.

Dutchy1969 · 2025-01-27T01:09:53Z

@cjbaar
Guess who’s back?? I was able to find a dirt cheap mk4 which has been upgraded now to a mk4s and just completed upgrading the mmu12 from the mk3 to the mk4s

I would like to thank especially you (and others that contributed) for making this work on the mk4

And special thanks to @VSCustoms for introducing me almost 2 years ago to this project.

ino89 · 2025-01-28T11:20:19Z

@cjbaar Guess who’s back?? I was able to find a dirt cheap mk4 which has been upgraded now to a mk4s and just completed upgrading the mmu12 from the mk3 to the mk4s

I would like to thank especially you (and others that contributed) for making this work on the mk4

And special thanks to @VSCustoms for introducing me almost 2 years ago to this project.

is the display with filament loading supported for MMU with 12?

cjbaar · 2025-01-28T14:49:20Z

No. The ground-up rewrite of the MMU3 by the Prusa team means that I don't need to change firmware anymore. I only supply a different config.h file with new parameters. Also the standard firmware communicates more verbose message to the printer screen.

mmu3 #19

mmu3 #19

Comments

Dutchy1969 commented Jul 30, 2023

grzlus commented Jul 31, 2023

cjbaar commented Jul 31, 2023

greenfox1505 commented Aug 7, 2023

grzlus commented Oct 30, 2023

Dutchy1969 commented Nov 10, 2023

grzlus commented Feb 23, 2024

grzlus commented Mar 6, 2024

sithlord48 commented May 1, 2024 • edited Loading

Johnday29 commented Jul 5, 2024

cjbaar commented Sep 27, 2024

Johnday29 commented Sep 28, 2024 via email

3d-gussner commented Sep 30, 2024

cjbaar commented Sep 30, 2024

cjbaar commented Sep 30, 2024

cjbaar commented Sep 30, 2024

cjbaar commented Sep 30, 2024

Johnday29 commented Sep 30, 2024 via email

cjbaar commented Oct 1, 2024

Johnday29 commented Oct 1, 2024 via email

cjbaar commented Oct 3, 2024

cjbaar commented Oct 3, 2024

3d-gussner commented Oct 4, 2024

Johnday29 commented Oct 5, 2024 via email

cjbaar commented Oct 18, 2024

Dutchy1969 commented Oct 18, 2024 • edited Loading

cjbaar commented Oct 18, 2024

sithlord48 commented Oct 19, 2024

cjbaar commented Oct 19, 2024

sithlord48 commented Oct 19, 2024

cjbaar commented Oct 19, 2024

Biertram commented Oct 27, 2024 • edited Loading

cjbaar commented Oct 27, 2024

3d-gussner commented Oct 28, 2024

cjbaar commented Oct 28, 2024

Biertram commented Oct 28, 2024

cjbaar commented Oct 28, 2024

Biertram commented Oct 28, 2024 • edited Loading

cjbaar commented Oct 28, 2024 • edited Loading

3d-gussner commented Oct 29, 2024

3d-gussner commented Oct 29, 2024

3d-gussner commented Oct 29, 2024

Biertram commented Oct 29, 2024

3d-gussner commented Oct 29, 2024

cjbaar commented Oct 29, 2024

3d-gussner commented Oct 30, 2024

3d-gussner commented Nov 6, 2024

Prusaprinter44 commented Nov 11, 2024

Prusaprinter44 commented Nov 11, 2024

3d-gussner commented Nov 12, 2024

Biertram commented Nov 12, 2024 • edited Loading

3d-gussner commented Nov 12, 2024

3d-gussner commented Nov 12, 2024

cjbaar commented Nov 12, 2024

3d-gussner commented Nov 29, 2024

jasonmatthews41 commented Dec 21, 2024

cjbaar commented Dec 21, 2024

jasonmatthews41 commented Dec 24, 2024

Dutchy1969 commented Jan 27, 2025

ino89 commented Jan 28, 2025

cjbaar commented Jan 28, 2025

sithlord48 commented May 1, 2024 •

edited

Loading

Dutchy1969 commented Oct 18, 2024 •

edited

Loading

Biertram commented Oct 27, 2024 •

edited

Loading

Biertram commented Oct 28, 2024 •

edited

Loading

cjbaar commented Oct 28, 2024 •

edited

Loading

Biertram commented Nov 12, 2024 •

edited

Loading