Posts made by greenlee

I can confirm after 3.4b3 improper homing of the c motor.
Additional info I haven't seen mentioned.
After a system reboot, it will work correctly on the first instance of running home all but subsequent homec or home all will move the c motor in the wrong direction.
for example in homec.g, the first instance calls for G1 H2 C-500 F5000 but appears to actually run G1 H2 C500 F5000 when observing the behavior.
to recreate, reboot ->homeall then either homec or home all will put the coupler in the wrong position.
It does appear that homeing the other axes are involved in this as after the first reboot homec works every time.

@Danal looks like a good idea. Same issue with heating as start.g as far as i can tell.

@Phaedrux start.g is a good idea but doesn't have an option to pull the heater temps out of the gcode. that I know of.
I

@Danal
the "prep the printer" macro you described is basically what I'm doing now.
Unfortunately in Cura 4.4.0 the slicer added the call for the first tool head before inserting the Start G-code, so adding anything to Start G-code that uses the Z axis limit sensor is off the table unless you first unload the previously loaded tool.

Hello all,
I am trying to figure out a way to automate Z-probe and mesh leveling using Cura 4.4.0 with an E3D tool changer.
In case your not familiar with the E3D tool changer machine, it has a microswitch Z-probe on the tool carrier assembly and needs to park any tool heads before probing the bed.
So obvious setups won't work as Cura will pre-mount the first tool used in the job and I would need to unload the tool, probe the bed and reload the same tool. The catch is, the tool is not always tool 0.
so, is there a command in RRF that would let me remember the last tool used and reload that tool letter on in startup g-code?
Any other ideas to do this?
Thanks,

did you add the enable mesh leveling to you start gcode?
G29 S1 ;enable mesh compensation