@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!
@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.
For extra fun, it seems M558 resets the X and Y values (but not Z) of the probe offset set in G31.
4/1/2022, 7:36:56 PM G31
Z probe 0: current reading 0, threshold 500, trigger height 0.700, offsets X0.0 Y0.0 U0.0
4/1/2022, 7:36:38 PM M558 P9 C"^io1.in" B1 H5 F60 T6000
4/1/2022, 7:36:25 PM M558
Z Probe 0: type 9, input pin io1.in, output pin nil, dive height 5.0mm, probe speeds 60,60mm/min, travel speed 6000mm/min, recovery time 0.00 sec, heaters suspended, max taps 1, max diff 0.03
4/1/2022, 7:36:13 PM G31
Z probe 0: current reading 0, threshold 500, trigger height 0.700, offsets X56.0 Y16.0 U0.0
4/1/2022, 7:36:10 PM g31 x56 y16
I hvae a bltouch configured and working with
M558 P9 C"^io1.in" B1 H5 F600:60 T6000
When homing Z i use G30 and as expected the probing is done once quickly and then more slowly in the second pass.
With my calibration macros i use G30 S-2 to set the probe z offset with this it only probes with the faster speed.
I am working around the problem by reconfiguring the probing speeds to F60 in the calibration macros.
Is this behaviour expected or a bug?
RepRapFirmware for Duet 3 Mini 5+ version 3.4.0 (2022-03-15 18:59:15) running on Duet 3 Mini5plus WiFi (SBC mode)
If your misbehaving servo is using io1.out on the mini5+ you should try the firmware build in the thread for my issue.
bltouch back on io1 with your updated build works. fantastic! thanks!
Ah! I will sacrifice one of the runout sensors to put it on io3 and give it a go, thanks.
With 3.4b6
Reset the board by pressing the reset button
Measured 0% duty
Sent M280 P0 S90
Measured 7.35% duty at 50Hz
Sent M280 P0 S180
measured 12% duty at 50Hz
Send M280 P0 S270
measured 12% duty at 50Hz
Sent M280 P0 S90
Measured 7.35% duty at 50Hz
So updating servo positions multiple times in 3.4b6 works
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
In 3.4rc1 the probe now deploys but doesn't retract after probing.
Machine was completely powered off after the update.
M122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.4.0rc1 (2022-02-09 10:27:22) running on Duet 3 Mini5plus WiFi (SBC mode)
Board ID: W4ZW4-V296U-D65J0-40KM0-LR03Z-H6928
Used output buffers: 1 of 40 (14 max)
=== RTOS ===
Static ram: 103652
Dynamic ram: 102128 of which 0 recycled
Never used RAM 35788, free system stack 134 words
Tasks: SBC(ready,3.9%,504) HEAT(notifyWait,0.0%,356) Move(notifyWait,0.0%,292) CanReceiv(notifyWait,0.0%,942) CanSender(notifyWait,0.0%,356) CanClock(delaying,0.0%,339) TMC(notifyWait,1.1%,114) MAIN(running,93.8%,558) IDLE(ready,0.4%,29) AIN(delaying,0.8%,264), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:08:35 ago, cause: software
Last software reset at 2022-02-09 18:36, reason: User, GCodes spinning, available RAM 36076, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task SBC Freestk 0 n/a
Error status: 0x00
MCU revision 3, ADC conversions started 515901, completed 515899, timed out 0, errs 0
Step timer max interval 1489
MCU temperature: min 27.5, current 37.5, max 37.8
Supply voltage: min 0.5, current 24.3, max 24.3, under voltage events: 1, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: pos 3760, standstill, SG min 0, read errors 0, write errors 2, ifcnt 13, reads 44146, writes 25, timeouts 0, DMA errors 0, CC errors 0
Driver 1: pos -1280, standstill, SG min 0, read errors 0, write errors 2, ifcnt 10, reads 44148, writes 23, timeouts 0, DMA errors 0, CC errors 0
Driver 2: pos 3560, standstill, SG min 0, read errors 0, write errors 2, ifcnt 10, reads 44147, writes 23, timeouts 0, DMA errors 0, CC errors 0
Driver 3: pos 17104, standstill, SG min 0, read errors 0, write errors 2, ifcnt 15, reads 44140, writes 29, timeouts 0, DMA errors 0, CC errors 0
Driver 4: pos 0, standstill, SG min 0, read errors 0, write errors 2, ifcnt 15, reads 44142, writes 29, timeouts 0, DMA errors 0, CC errors 0
Driver 5: pos 0, standstill, SG min 0, read errors 0, write errors 2, ifcnt 15, reads 44142, writes 29, timeouts 0, DMA errors 0, CC errors 0
Driver 6: pos 0, standstill, SG min 0, read errors 0, write errors 2, ifcnt 15, reads 44140, writes 29, timeouts 0, DMA errors 0, CC errors 0
Date/time: 2022-02-09 18:46:07
Cache data hit count 1160425780
Slowest loop: 60.47ms; fastest: 0.08ms
=== Storage ===
Free file entries: 10
SD card 0 not detected, interface speed: 0.0MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 6, maxWait 48307ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 39, completed 39, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 1], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP* is doing "M122" in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger* is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== Filament sensors ===
Extruder 0 sensor: ok
=== CAN ===
Messages queued 4633, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 18 (min 18), ts 2578/0/0
Tx timeouts 0,0,2577,0,0,2054 last cancelled message type 4514 dest 127
=== SBC interface ===
Transfer state: 4, failed transfers: 0, checksum errors: 0
RX/TX seq numbers: 20857/20857
SPI underruns 0, overruns 0
State: 5, disconnects: 0, timeouts: 0, IAP RAM available 0x0f624
Buffer RX/TX: 0/0-0, open files: 0
=== Duet Control Server ===
Duet Control Server v3.4-rc1
Code buffer space: 4096
Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0
Full transfers per second: 40.50, max time between full transfers: 47.1ms, max pin wait times: 46.5ms/6.9ms
Codes per second: 0.45
Maximum length of RX/TX data transfers: 3592/1136