Another Delta Homing Issue

[too.stroke]

@cosmowave
Absolutely, my homedelta.g is as follows:

; homedelta.g
; called to home all towers on a delta printer
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Fri Jul 30 2021 12:02:42 GMT-0700 (Pacific Daylight Time)
G91                        ; relative positioning
G1 H1 X649 Y649 Z649 F1800 ; move all towers to the high end stopping at the endstops (first pass)
G1 H2 X-5 Y-5 Z-5 F1800    ; go down a few mm
G1 H1 X10 Y10 Z10 F360     ; move all towers up once more (second pass)
G1 Z-5 F6000               ; move down a few mm so that the nozzle can be centred
G90                        ; absolute positioning
G1 X0 Y0 F6000             ; move X+Y to the centre

[cosmowave]

@too-stroke Eventually it helps, when you insert a "M400" command between line 6 and 7.

[too.stroke]

@cosmowave
I can see how the M400 can be useful however it hasn't improved my issue.
I was thinking it might be a endstop triggering prematurely, however, I watched the endstop trigger LED's on the mainboard while homing and none of the endstops triggered (visibly) prematurely when my Y axis refused to home.

[A Former User]

This post is deleted!

[dc42]

@too-stroke I think you have a bad connection between the homing switch for tower 3 and the Duet. Use the Object Model Browser in DWC, or M119, to check the reported status of the homing switch as you operate it. You will probably find that it reports as triggered when it isn't.

[too.stroke]

@Herve_Smith @cosmowave @dc42

The M400 may have actually solved the issue after all...
I'm not sure why, and need to do some more testing in the morning but I've been able to successfully home multiple times now.

I realized it didn't work initially cause I wrote m400 not M400
for now I'm just glad its working again, however I do wish I knew what caused this in the first place...

Thanks for all the help though!

[dc42]

@too-stroke said in Another Delta Homing Issue:

@Herve_Smith @cosmowave @dc42

The M400 may have actually solved the issue after all...
I'm not sure why, and need to do some more testing in the morning but I've been able to successfully home multiple times now.

I realized it didn't work initially cause I wrote m400 not M400
for now I'm just glad its working again, however I do wish I knew what caused this in the first place...

Thanks for all the help though!

M400 is not required because it is implicitly executed after any homing move. Also m400 is treated exactly the same as M400. I think you have an intermittent connection between the endstop and the Duet. With the endstop not triggered, try waggling the cable while watching the endstop states in the object model browser.

[A Former User]

This post is deleted!

[dc42]

@Herve_Smith by a "homing move" I mean any G0 or G1 command that stops when the corresponding endstop is triggered.

[A Former User]

This post is deleted!