Multi color printing with Prusa's MMU V2 & Duet?

gavatron3000

theres a link in the document above

Scachi

@gavatron3000 said in Multi color printing with Prusa's MMU V2 & Duet?:

theres a link in the document above

Thank you.

gavatron3000

@dc42 regarding triggers, are they meant to go off with immediate effect?

in my document above for loading the MMU2 they work and function as intended but it seems they are delayed until the tool change has completed. is this expected behaviour? id prefer being able to set it off immediately

dc42

The movement system is locked during a tool change, therefore if the trigger macro has any movement commands or other commands that affect motion, those commands will wait until the tool change is complete.

gavatron3000

The triggers in question are like this

M400
M291 "message and wait till ok is pressed"

Should I just remove the m400?

NicoLab28

@gavatron3000 said in Multi color printing with Prusa's MMU V2 & Duet?:

in my document above for loading the MMU2 they work and function as intended but it seems they are delayed until the tool change has completed. is this expected behaviour? id prefer being able to set it off immediately

You're saying that you have the same problem as me, (my post "M581 M582 M291, What am I doing wrong?") To know that the dialog comes at the end of the tool change.
Too late, because the script continued to execute, after the error, which should have been blocking.

gavatron3000

I'm going to try removing the V1 from the M291 as well as the M400 too. But I can't test this until tomorrow

dc42

M400 means wait until all queued motion has completed. So if you send it when a tool change is on progress, it will wait until it has completed.

gavatron3000

I'm hoping that if I remove the m400 and only have a M291 message within the trigger macro that it will pause the tool change if the condition is met.
I'll test shortly when I get a chance

gavatron3000

@dc42 said in Multi color printing with Prusa's MMU V2 & Duet?:

The movement system is locked during a tool change, therefore if the trigger macro has any movement commands or other commands that affect motion, those commands will wait until the tool change is complete.

ok so i removed all the movement commands and M400 from the trigger but to no avail. is it possible allow the triggers in the future to interrupt the tool change and pause when conditions arent met? and then resumed when prompted? that would make this MMU2 work perfectly then

Wyvern

The MMU is interesting, but using Duet components are you not able to use purge blocks and such?

gavatron3000

Purge blocks and the like are generated by the slicer or post processing scripts

Wyvern

Ah. Thanks.
Would be great for TPU printing as supports with TPU are useless- just use pla.

Computiger

@gavatron3000 said in Multi color printing with Prusa's MMU V2 & Duet?:

https://docs.google.com/document/d/13r_6BTYTO-xlD6cQeNwOx4qeCEYYGrxOcHc0mC-tT8Q/edit?usp=drivesdk

Hmm...

I didn´t understand as I have to.
Can somebody tell me where I have to plug in the Pinda probe. For now I putted him to E0 Endstop, but I can´t home the selector (drive U).

In the description I have to plug him to V but

Here some details of config.g

; Endstops
M574 X1 Y1 S1 ; Set active high endstops
M574 U1 V1 W1 S3 ; Set additional axes as sensorless endstops
M574 Z1 S2 ; Set endstops controlled by probe

;Drives
M569 P4 S0 ; Drive 4 goes backwards V
M569 P5 S1 ; Drive 5 goes forwards U
M569 P6 S0 ; Drive 6 goes backwards W
M584 X0 Y1 Z2 E3 V4 U7 W6 ; Apply custom drive mapping

gavatron3000

@computiger said in Multi color printing with Prusa's MMU V2 & Duet?:

@gavatron3000 said in Multi color printing with Prusa's MMU V2 & Duet?:

https://docs.google.com/document/d/13r_6BTYTO-xlD6cQeNwOx4qeCEYYGrxOcHc0mC-tT8Q/edit?usp=drivesdk

Hmm...

I didn´t understand as I have to.
Can somebody tell me where I have to plug in the Pinda probe. For now I putted him to E0 Endstop, but I can´t home the selector (drive U).

In the description I have to plug him to V but

Here some details of config.g

; Endstops
M574 X1 Y1 S1 ; Set active high endstops
M574 U1 V1 W1 S3 ; Set additional axes as sensorless endstops
M574 Z1 S2 ; Set endstops controlled by probe

;Drives
M569 P4 S0 ; Drive 4 goes backwards V
M569 P5 S1 ; Drive 5 goes forwards U
M569 P6 S0 ; Drive 6 goes backwards W
M584 X0 Y1 Z2 E3 V4 U7 W6 ; Apply custom drive mapping

the pinda is used as the V axis endstop in certain situations during loading so it must be plugged into that axis endstop input. U axis uses sensorless homing

nikscha

@gavatron3000 said in Multi color printing with Prusa's MMU V2 & Duet?:

I don't use the cutter, for me I didn't think it's necessary as the ramming before retraction forms the tip anyways. Abs just works but pla is more difficult. Make sure you use the correct I.D PTFE tube in the Hotend as well. 1.8mm to 1.85mm. capricorn tubing isnt narrow enough either, ive tried.

I almost forgot! I'm adding some modded STL and scad files soon so the filament change will function perfectly as the filament ejection will snag on T4 without a small mod to the selector and main body of the mmu2

Hey there,
first of all, awesome work!
Second, where are the stl's you mentioned here? Are they important?
Thanks in advance!

gavatron3000

the stl's arent a requirement, but they only help in the situation when T4 is out of filament and the 50cm or so of left over filament is ejected out the front of the machine if you know what i mean. with the standard selector it will foul in this situation. i havent finished this yet as a filament runout on T4 is very low percentage of my issues but i will do this eventually

nikscha

@gavatron3000 thanks a lot for all the prep work! Working on my unit right now but my steppers get way too hot
Are you using original parts from prusa? Are there any changes to your macros?

trublu89

I think I got everything finally setup correctly. I am a bit confused on setting up prusa slic3r to tell it to use the macros.

Danal

Tell the slicer that you have multiple extruders. The slicer imbeds tool change commands. The firmware moves the filaments around in the MMU when it sees a "tool change".

I think. I have actual multi-tool printers and that's the way it works for them. Slicer asks for a different tool, and all the moves to make that happen are in the free/pre/post macros in Duet.