@fcwilt Thanks, for pointing that out. I should have read that doc more thoroughly.
I have also found a proper solution which is to specify M558 A2 (or higher) which causes all the G30 S-2 to probe slowly on the second (and third) probes.
I'm still surprised by the difference in behaviour between G30 and G30 S-2 in my previous configuration.
You can change the log level of duetcontrolserver to debug (/opt/dsf/conf/config,json. That will cause it to log every gcode that is run.
You can view the logs with
sudo journalctl --unit duetcontrolserver
@fletcher You can probably get logs from the SBC:
sudo journalctl --unit duetcontrolserver
Further debug...
I replaced my bltouch with a multimeter set to measure frequency and duty cycle.
Reset the board by pressing the reset button
Measured 0% duty
Sent M280 P0 S90
Measured 7.35% duty at 50Hz
Send M280 P0 S180
no change in measurement
sent m280 P0 s270
no change in measurement.
reset board.
sent m280 p0 s270
measured 12% duty at 50Hz
sent m280 p0 s90
no change in measurement
Thus i think my issue is the same as this thread:
https://forum.duet3d.com/topic/27139/rrf-3-4-0beta7-5-sbc-servo-only-responding-once-after-reset
@dc42 Yep, looks good. No issues in the last 24h.
Many thanks for sorting this out!
bltouch back on io1 with your updated build works. fantastic! thanks!