How to copy custom filament profiles from single mode to mmu2s mode
 
Notifications
Clear all

How to copy custom filament profiles from single mode to mmu2s mode  

  RSS
tdukes
(@tdukes)
Active Member
How to copy custom filament profiles from single mode to mmu2s mode

I do not see my filament settings I use in single mode when I switch to MMU2S mode. How do I copy them over?

I tried to re-create one and PS told me the preset already existed.

TIA

Opublikowany : 24/03/2020 3:41 pm
Neophyl
(@neophyl)
Illustrious Member
RE: How to copy custom filament profiles from single mode to mmu2s mode

They all need different names if you do copy them. One reason you may not see the one you have is dependencies. check the dependencies screen on the filament profile. There’s often entries limiting what printers can use them. 

Opublikowany : 24/03/2020 4:55 pm
JoanTabb
(@joantabb)
Veteran Member Moderator
RE: How to copy custom filament profiles from single mode to mmu2s mode

use a different Profile name!

I try to make safe suggestions,You should understand the context and ensure you are happy that they are safe before attempting to apply my suggestions, what you do, is YOUR responsibility. Location Halifax UK

Opublikowany : 24/03/2020 5:06 pm
tdukes
(@tdukes)
Active Member
Topic starter answered:
RE: How to copy custom filament profiles from single mode to mmu2s mode

@neophyl

Thanks!! I checked the dependencies like you said. They were set to ALL.

I changed the green flag to red and they now appear.

Opublikowany : 24/03/2020 5:20 pm
Neophyl
(@neophyl)
Illustrious Member
RE: How to copy custom filament profiles from single mode to mmu2s mode

Ah then that would mean its likely falling foul of the new Vendor spaces changes that they have put into 2.2.0.  The old version just used the dependencies to control what does and does not appear.  Theres a new system internally that uses vendors too (as well as the old dependencies).  If you look on the dependency page you should see a new button called something like "detach from Vendor".  This will clear the Vendor settings from your saved copy.  That should allow it to be used with any printer (as long as the old dependencies filter line would also allow it).

Opublikowany : 25/03/2020 7:18 am
tdukes
(@tdukes)
Active Member
Topic starter answered:
RE: How to copy custom filament profiles from single mode to mmu2s mode

@neophyl

Thanks,

Oddly, what I did above worked for PS 2.2.0 on my laptop. Not even seeing the flag on my desktop PC. All I'm seeing is 'Detach from Preset'. Tried that but it didn't work.

I did previously install an alpha version of 2.2 on my laptop but uninstalled it when I had trouble with custom profiles. Not sure that would have anything to do with it or not.

I'm not running a Prusa printer. I used the MK3S printer to setup my Ender 3 Pro (before Prusa supported Creality). Also need it because of he MMU2S I have connected.

Opublikowany : 25/03/2020 11:42 am
tdukes
(@tdukes)
Active Member
Topic starter answered:
RE: How to copy custom filament profiles from single mode to mmu2s mode

OK, I think I figured it out.

If I select the single mode printer, where I can see my filament, I can lock the Compatible Printers Condition setting and they are visible when I switch the printer to MMU2S mode.

Opublikowany : 25/03/2020 12:12 pm
Kmueller6290
(@kmueller6290)
New Member
Filament Profile Changes

So I just finished messing around with a few settings and I was able to get all of my filament profiles to show for all my loaded printers.

Go to the printer that has your custom filament profiles, then;

Filament Settings>"Dependencies" (left tab)> "Detach from System Preset"> Accept the prompt> Click the lock next to "Compatible printer presets"> Check the box for "Compatible Printers"> Check the box for "Compatible Print Profiles".

 

The only oddity I still have is that if I change the color swab and hit the lock button it changes the color. But if I leave the box unlocked it stays. Easy enough to just leave the box unlocked

Opublikowany : 14/10/2021 12:16 pm
Share: