feat: Implementation of MMU panel to support single-extruder-multi-material printing using the Happy Hare for any MMU/AFC

[moggieuk]

Description

The PR adds an additional "MMU" Panel -- very visual and dynamic to both control and monitor state of MMU. This works with Happy Hare for any MMU or AFC (configuration is through klipper extensions). Prerequisite moonraker support has already been incorporated.

Summary:

• There is one new "MMU" panel and 4 dialogs launched from the main panel menu.
• If an MMU is not detected then the panel isn't displayed and the only overlap with existing functionality is in the print start dialog which also tests for existence of MMU.
• The additions are all tested on mobile, tablet and widescreen on dark and light modes.
• The only "connective tissue" is on the print start dialog where I detect if this is an MMU print and use my "tool mapper" instead of spoolman which will still appear for single color prints in MMU bypass is selected.
• This integrates with current spoolman functionality. I made one very small change to the spoolman active spool chooser to allow it to be used for selection purposes without setting active spool
• Finally, the print start functionality relies on some new metadata from moonraker -- that PR has already been merged into the latest moonraker.
• All strings are tokenized and in locales/en.yaml
• I created one additional mixin (mmu.ts) as a base for Mmu components.
• If an MMU is not detected then the panel isn't displayed and the only overlap with existing functionality is in the print start dialog which also tests for existence of MMU.

The attached screenshots give a flavor of the main panel and a couple of the dialogs.

Mobile & Desktop Screenshots/Recordings

Here is a non-exhaustive selection of screenshots (some dialogs excluded):

Development and user testing has been performed on a public (Happy Hare) discord channel on: https://discord.gg/98TYYUf6f2

Are there any post-deployment tasks we need to perform?

• The functionality will only be seen if popular Happy Hare klipper extension is installed and configured. This populates printer.mmu and printer.mmu_machine printer variables.
• The latest moonraker is required for the start print mapping to function correct since new metadata has been added.

Signed-off-by

Signed-off-by: Paul Morgan [email protected]

[moggieuk]

Example mobile screen

[pedrolamas]

Hey @moggieuk, thanks for doing this!! 😀

I haven't yet reviewed anything yet (just rebased and fixed some conflicts with the latest changes), but sure looks really cool!!! 😁

[3DCoded]

+1 for this.

The MMU panel is super helpful when monitoring prints, and the new map tool dialog is also great for more complex MMU prints.

[marcelsphone]

+1

Would love to see this merged. Awesome work!

[moggieuk]

Hey @moggieuk, thanks for doing this!! 😀

I haven't yet reviewed anything yet (just rebased and fixed some conflicts with the latest changes), but sure looks really cool!!! 😁

Ok. Let me update and resolve conflicts later today. Looks like some changes to spoolman causing some problems I need to debug.

[ningpj]

Looks awesome and really appreciate all the effort and time taken to develop native Happy Hare panels

[pedrolamas]

@moggieuk I have just done a huge commit to allow the Vuex state store to be typed... while merging the changes to your branch, I cleared all the collisions, but I found a couple of problems I don't know how to fix:

src/components/widgets/mmu/MmuRecoverStateDialog.vue:281:29 - error TS2339: Property 'mmu' does not exist on type 'RootState'.

281     return this.$typedState.mmu.show_recover_state_dialog
                                ~~~

src/components/widgets/mmu/MmuRecoverStateDialog.vue:285:23 - error TS2769: No overload matches this call.
  The last overload gave the following error.
    Argument of type '"mmu/setDialogState"' is not assignable to parameter of type '"analysis/setAnalysisStatus"'.

285     this.$typedCommit('mmu/setDialogState', {
                          ~~~~~~~~~~~~~~~~~~~~

Ignore the mention to "analysis/setAnalysisStatus", that just means that "mmu/setDialogState" doesn not exist!

These 2 errors point to a non-existing mmu module in Vuex, so I guess they are incorrect... can you check on these please?

[Saberjag]

After getting the MMU panel to show up, I noticed that my Macro panel is now empty. I can still see my macro categories in settings, but no macro buttons.

[3DCoded]

@Saberjag ,

That's a bug with DynamicMacros, with a workaround described here in the "Fluidd and KS" dropdnwn.

[pedrolamas]

@Saberjag ,

That's a bug with DynamicMacros, with a workaround described here in the "Fluidd and KS" dropdnwn.

FWIW, I've just fixed the problem on the develop branch and merged the changes here, so the workaround is no longer required!

[3DCoded]

@Saberjag ,
That's a bug with DynamicMacros, with a workaround described here in the "Fluidd and KS" dropdnwn.

FWIW, I've just fixed the problem on the develop branch and merged the changes here, so the workaround is no longer required!

Thank you!

[pedrolamas]

@moggieuk I have made a few refactorings around the dialog handling, I think everything is working ok, but can I ask that you take current code for a spin and ensure I haven't broken anything?

FWIW, I don't think there is much more I will be changing, and this is starting to look to me in a good to merge state!

[moggieuk]

@moggieuk I have made a few refactorings around the dialog handling, I think everything is working ok, but can I ask that you take current code for a spin and ensure I haven't broken anything?

FWIW, I don't think there is much more I will be changing, and this is starting to look to me in a good to merge state!

Sorry, was distracted for a couple of days. I see one problem with the spoolman spool selection...
On the "MmuEditGateMapDialog" dialog if in spoolman mode you can pop up the spoolman spools dialog. Selecting a spool in that previous would pass the spool back to my dialog. This doesn't seem to be happening now.

Everything else looks fine.

[moggieuk]

oh, I also noticed the spoolman spool icon color is now absent. I will try to look to see what might have changed..

Looked like your latest merge fixed the first problem. So just the spoolman icon color not being set in MmuEditGateMapDialog

[pedrolamas]

Looked like your latest merge fixed the first problem. So just the spoolman icon color not being set in MmuEditGateMapDialog

That shouldn't make any difference, but I did just notice an incorrect boolean check on the spool id, it would fail if it was 0 - fixed it just now!

[pedrolamas]

oh, I also noticed the spoolman spool icon color is now absent. I will try to look to see what might have changed..

Should be fixed now!

[moggieuk]

Thank you. You beat me to the push ;-)

And thanks again for all your help!!