@mrac1 OKAY! Back to this.. Finally updated, and Calling the macro generates a popup window, but doesn't pause the print, or move the print head out of the way, etc. So, the Macro is calling, but it's not doing anything other than generating an OK button. Thoughts?

My Macro Script (Super simple):

M400 ; Wait for moves to complete
G1 X10 Y10 F3000 ; Move nozzle to the front
M291 P"Change Filament" ; Display message
G1 R1 ; go back to the last print move

@phaedrux Fair enough! it was a big jump heh 1.18 was just so lovely, and my printer was busy... was just a little panicked at the sudden state of borkedness =P

SOLVED! See Below!

Hey all, Just updated to 1.21 from 1.18. Having issues with Homing (yes it's a corexy!, and yes I put an S2 after my G1 Z lines). Machine attempts to home, but the endstops no longer seem to trigger properly. The LEDs turn off when the endstop is hit on the board itself, but the printer keeps moving =~~

Also, confirmed w/ M119 that they're being seen when triggered...

Not sure what I need to do, but i'm losing the battle! Help!

/code
G91 ; relative mode
G1 Z10 S2 ; Lift Z 10mm CYA!
G1 S1 X-382 Y-382 F3000 ; course home X or Y
G1 S1 X-382 ; course home X
G1 S1 Y-382 ; course home Y
G1 X4 Y4 F600 S2 ; move away from the endstops
G1 S1 X-10 ; fine home X
G1 S1 Y-10 ; fine home Y~~

-VG

NEVERMIND! Somehow, the Firmware update reversed the direction of my X and Y motors o.O; SUPER STRANGE AND SLIGHTLY FRUSTRATING!

gonna do it in the morning… want to finish this print I started =\

1.18.1. Time to update!

M291
Error: unsupported command: M291

First test print going now… I shall report my failures and or victories! Thanks guys!

nevermind, answered my own question, that's where it knows when to stop and start printing! got it!

@vonGreezly:

@mrac1:

Ok, you need a macro on the duet which controls your filament change. You create this directly via DWC in the macro area. Take my macro out of the thread as inspiration. Name it eg. "ColorChange"

In S3D use the "Variable Settings Wizard" (Menue "Tools") to generate a second (third… and so on) processes depending on the layer height.
Rename this process to something like "Color2" (Color3, Color4...) (doubleclick on the process and change the name in the first line of the fff settings)

In the postprocessing area insert:

{REPLACE "; process Color2" "M98 P/macros/ColorChange"}
{REPLACE "; process Color3" "M98 P/macros/ColorChange"}
{REPLACE "; process Color4" "M98 P/macros/ColorChange"}

Color2 is the name of the process
M98 is the Gcode to call the macro
/macros/ is the path to the macro on the duet
ColorChange is the name of the macro

This is all you need, pretty simple. You can leave the Replace lines in the postprocessing also for single color prints, because they do nothing without a renamend process.

Thank you so much! I'm going to try and implement this right now!

Quick question! Is it not possible to do this from ONE process (and just have multiple pauses?) or do I need to print using multiple processes to make this work? (whatever works is fine, just curious!)

-VG

@mrac1:

Ok, you need a macro on the duet which controls your filament change. You create this directly via DWC in the macro area. Take my macro out of the thread as inspiration. Name it eg. "ColorChange"

In S3D use the "Variable Settings Wizard" (Menue "Tools") to generate a second (third… and so on) processes depending on the layer height.
Rename this process to something like "Color2" (Color3, Color4...) (doubleclick on the process and change the name in the first line of the fff settings)

In the postprocessing area insert:

{REPLACE "; process Color2" "M98 P/macros/ColorChange"}
{REPLACE "; process Color3" "M98 P/macros/ColorChange"}
{REPLACE "; process Color4" "M98 P/macros/ColorChange"}

Color2 is the name of the process
M98 is the Gcode to call the macro
/macros/ is the path to the macro on the duet
ColorChange is the name of the macro

This is all you need, pretty simple. You can leave the Replace lines in the postprocessing also for single color prints, because they do nothing without a renamend process.

Thank you so much! I'm going to try and implement this right now!