Topics created by ProfChris

@ProfChris Thanks, I've amended the text to:

If the reset button is stuck in (rare), or has been mounted so it is pushed in by an enclosure (also check connected PanelDue/12864 displays for this, by disconnecting them), the Duet will get stuck in a boot loop, which will cause the DIAG LED to be on permanently. Check there is clearance around the reset button, or use some tweezers to gently pull the button out.

Ian

Thanks for updating the documentation.
I have now got sensorless homing working fine on the four motor Z axis. I was hoping that I might be able to say that I followed a "process" which might help others along the path, but I'm not sure that was the case.
The process was roughly:
1: establish a clear stealthchop mode using M569 D3 V100...
2: establish the minimum % of motor current which would reliably move the axis; here 30%;
3: establish a speed at which a stall was reliably detected at the end of travel circa 60% of max speed.
This worked and I did not need to modify the acceleration - I had that available if the axis stalled on starting to move (which in hindsight is easy to correct).
Even though at the outset the process appeared a bit random, I'm glad that I persevered with this as there is considerable satisfaction in seeing the axes move smoothly and reliably to the end point with no judder or collision bang. It simplifies the wiring as well.

@dc42 Thanks for the reply. I thought that that was probably the case

https://docs.duet3d.com/en/User_manual/Tuning/Macros#daemong