Duet 3 3.4 beta7+7 incorrect home and printing operation
-
Put this into the first lines of your homing macros:
if {state.status == "processing“}
M99
Note that the second line (with M99) must be inserted. -
@infiniteloop That has the wrong end quote quote. It has to be ", not that fancy one.
-
@stephen6309 Didn't note that - my Mac seems to have "corrected" that during copy/paste. The lines originate directly from my Duet macros … Thank you for putting that right.
-
I try thanks
-
adding the code in home all if sending home during printing is executed anyway.
-
the firmware must be corrected
-
@massimilianoconti would you please publish your macro homeall.g?
-
; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Sat Jan 01 2022 15:36:30 GMT+0100 (Ora standard dell’Europa centrale)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 X-310 Y-310 F1800 ; move quickly to X or Y endstop and stop there (first pass)
G1 H1 X-310 ; home X axis
G1 H1 Y-310 ; home Y axis
G1 X5 Y5 F6000 ; go back a few mm
G1 H1 X-310 F360 ; move slowly to X axis endstop once more (second pass)
G1 H1 Y-310 ; then move slowly to Y axis endstop
G90 ; absolute positioning
G1 X15 Y35 F6000 ; go to first bed probe point and home Z
G30 ; home Z by probing the bed
; Uncomment the following lines to lift Z after probing
;G91 ; relative positioning
;G1 Z5 F100 ; lift Z relative to current position
;G90original version
-
@massimilianoconti That's not the latest version, eh?
-
no is the latest version. I just rerun the tool and says Configuration Tool v3.3.10 on Thu Jan 27 2022 19:23:58
-
@massimilianoconti … OK. TBH I'm only interested in where and how my two-liner landed in the macro, so that I can check why it didn't work for you. Another question in this context: did you invoke homing when the printer was busy, or had you paused the print before?
-
then your code was put first at the beginning then at the second attempt at the end of the macro. the home I ran after the printing had started so the machine was busy. thanks for the help