G28 Delta towers crash
-
Please post your homedelta.g file too.
What firmware version are you using?
-
Hi David, I am using the firmware:
Duet WiFi 1.02 or later (duetwifi102)
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 2.05.1 (2020-02-09b1)
Duet WiFi Server Version: 1.23 -
; homedelta.g
; called to home all towers on a delta printer
;
; generated by RepRapFirmware Configuration Tool v2.1.8 on Sat May 16 2020 12:10:05 GMT+0100 (British Summer Time)
G91 ; relative positioning
G1 H1 X265 Y265 Z265 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 -
@rodek wouldn't that persume they are active when high?
-
I didn't see anything wrong with your configuration and homing files.
I suspect that you have swapped a couple of motor or endstop cables over. Use G91 followed by G1 H2 Xnnn moves to identify which tower has the X motor. Then check that when you trigger the endstop on that tower, M119 shows that it is the X endstop that is triggered. Repeat for Y and Z.
-
@dc42 Cheers David, the endstops seem to trigger and are confirmed under endstop status under machine specific tab.
-
does it matter which tower is the x , y and z on a delta as long as it goes in a clockwise direction?
-
I assume it does matter in the way the endstops correlate to the towers.
It may just be best practice to call the left tower "X", the right one "Y", and the back one "Z", but it really does help in preventing (or at least resolving) this type of issues.
-
@chris said in G28 Delta towers crash:
@dc42 Cheers David, the endstops seem to trigger and are confirmed under endstop status under machine specific tab.
What I was trying to as was: Is the endstop that shows as X when triggered on the same tower as the motor that moves when you command X movement with a G1 H2 Xnnn move?
Instances of the behaviour you describe are typically caused by the motor and the corresponding endstop (e.g. X motor and X endstop) not being on the same tower.
-
@dc42 Cheers david X and Y limit switches got swapped