Homing issue on Duet2

[droftarts]

@Hubert91 The first Z move needs to be an H2 move, so it ignores if the Z axis is not homed. Your homeall.g has this:

G1 H2 Z5 F6000 ; move Z relative to current position to avoid dragging nozzle over the bed

but your homex.g, homey.g and homez.g have

G1 Z5 ; move Z relative to current position to avoid dragging nozzle over the bed

Change them to match homeall.g. This is an error in the code the config tool is generating, I have asked @chrishamm to fix it.

PS
The ending move, to return Z to it's starting place, also needs to be an H2 move, in homex.g and homey.g. ie

G1 H2 Z-5 F6000 ; move Z relative to current position

Ian

[Hubert91]

I changed homex.g, homey.g et homez.g and put H2.

Now an independent homing can be almost carried out. The program does not store the procedure and the machine stops moving at the line:

G1 Z-5 F6000 ; move Z relative to current position

due to insufficient axes homed. Its very weird.

[droftarts]

@Hubert91 I added an extra part to the end of my post. The last Z move also needs to be an H2 move in homex.g and homey.g, to move the Z axis back down.

Ian

[Hubert91]

@droftarts It's done and does not solve the problem

[droftarts]

@Hubert91 Please post your current homex.g and homey.g

Ian

[Hubert91]

@droftarts the homeall.g does not work too.

homex.g

; increase Z
G91 ; relative positioning
G1 H2 Z5 ; move Z relative to current position to avoid dragging nozzle over the bed
G90 ; absolute positioning

; home X
var maxTravel = move.axes[0].max - move.axes[0].min + 5 ; calculate how far X can travel plus 5mm
G1 H1 X{-var.maxTravel} F3000 ; coarse home in the -X direction
G1 X5 F6000 ; move back 5mm
G1 H1 X{-var.maxTravel} F300 ; fine home in the -X direction

; decrease Z again
G91 ; relative positioning
G1 H2 Z-5 F6000 ; move Z relative to current position
G90 ; absolute positioning

homey.g

; increase Z
G91 ; relative positioning
G1 H2 Z5 ; move Z relative to current position to avoid dragging nozzle over the bed
G90 ; absolute positioning

; home Y
var maxTravel = move.axes[1].max - move.axes[1].min + 5 ; calculate how far Y can travel plus 5mm
G1 H1 Y{-var.maxTravel} F3000 ; coarse home in the -Y direction
G1 Y5 F6000 ; move back 5mm
G1 H1 Y{-var.maxTravel} F300 ; fine home in the -Y direction

; decrease Z again
G91 ; relative positioning
G1 H2 Z-5 F6000 ; move Z relative to current position
G90 ; absolute positioning

[droftarts]

@Hubert91 I can't see anything wrong with your homex.g and homey.g. What doesn't work, or what error is reported?

Same for homeall.g; what doesn't work, or what error is reported?

Ian

[Hubert91]

There is no error reported with homeall.g, and no error reported with homex,y,z since I add the "H2".
When I send G28, the printer begin the homing by moving the X axis twice, then the Y axis twice, then Z axis twice, as written in the GCode. The endstop switches work well. But after the procedure, the printer remains not homed. The X, Y and Z buttons in the console of DWC remain orange.

If I try to force the homing by setting the known position with a G92 code, the buttons move to blue color. If I move the axis after that, the printer is de-homed again.

[jay_s_uk]

@Hubert91 said in Homing issue on Duet2:

M906 I0 ; set motor current idle factor

this is your problem in config.g remove that line

[droftarts]

@Hubert91 @jay_s_uk is right; effectively the motors are turning off, and so losing position, 1 second after they are set to idle, because of these two lines:

; Motor Idle Current Reduction
M906 I0 ; set motor current idle factor
M84 S1 ; set motor current idle timeout

You need to set some motor current, so the axis can maintain position. The default is usually 30%, ie M906 I30. You also don't want to set the idle timeout too short, in case there is a pause in your gcode program. M84 S30 is generally sensible.

Ian

[Hubert91]

Thank you guys, you find the error. With more than 0%, it works. Works with 1 seconde time out but I will set as you describe.

Have a good day

[droftarts]

@Hubert91 Actually, the M906 idle current doesn't come into effect until the whole machine is idle, ie it doesn't happen in the middle of a print job, only after the print job is finished, or a macro (like homing) has finished. So the M84 time is not too important. I have mine set to 20 seconds, but M906 set to 30%.

Ian