Topics created by Lukrative

@dc42 Here is the updated Retract macro from line 14 of my original post:

M400; clear the command buffer M280 P1 S{global.retract_angle} G4 P400; wait for purge bucket to fully retract

Before adding in the M400, the M280 P1 command was being executed between lines 7 and 8. I don't know if the dwell was being executed early.

@Phaedrux yes that was immediately after running the macro and seeing the motor stall.

I don't understand why the fix works, but it works, so I'm happy (enough)!

No problem... at startup, home, just like any other axis. I can't overstress that I'm doing EXACTLY what you are doing, just in a circle instead of a line. It all works. No jams, no funny startups. G28 and/or G28 U work normally. etc, etc, etc.

Do include homeu.g in homeall.g

homeu.g

G91 ; Set relative mode G1 U-360 F9000 H1 ; Big negative move to search for home endstop G1 U6 F600 ; Back off the endstop G1 U-10 F600 H1 ; Find endstop again slowly G90 ; Set absolute mode

Jay is remapping so he can use stall detect. Which also works great, after you tune it. (Jay and I talk a lot on the Jubilee discord).

@dc42 Thanks for the explanation, that makes a lot of sense. When I have access to my machine again I'll try that out.

@droftarts Thanks for the links! They led me to take a closer look at the gcode documentation. The M563 documentation says the following:

"It is permissible for different tools to share some (or all) of their drives and heaters. So, for example, you can define two tools with identical hardware, but that just operate at different temperatures."

It seems, then, that the easiest thing is to get that expansion module and define tools 0 and 1 to use the extra drive, in the same way that they already share heater 1.

For posterity's sake, updating the firmware fixed it 🙂

@lukrative Oh, and another little tip. If you add a retraction at the end of the print, say in the slicer end gcode section, it will alleviate or even eliminate the oozing you get as the hot end cools.