3.5b3+MB6HC+Smart Effector Probe Triggering at Standstill

[blt3dp]

This behavior seems to be software specific. I updated to 3.5 b3 to resolve the web interface continuing to report the prior filament out condition. That was resolved, but I noticed that the z probe seems to be triggering at standstill since then. Here's M122.

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.5.0-beta.3 (2023-04-14 11:28:15) running on Duet 3 MB6HC v1.0 or earlier (standalone mode)
Board ID: 08DGM-9T66A-G63SJ-6JTDL-3SD6P-TS0HA
Used output buffers: 5 of 40 (40 max)
=== RTOS ===
Static ram: 154728
Dynamic ram: 110328 of which 536 recycled
Never used RAM 80328, free system stack 146 words
Tasks: NETWORK(ready,35.5%,227) ETHERNET(nWait,0.1%,568) HEAT(nWait,0.0%,326) Move(nWait,0.0%,267) CanReceiv(nWait,0.0%,942) CanSender(nWait,0.0%,334) CanClock(delaying,0.0%,335) TMC(nWait,7.9%,59) MAIN(running,56.3%,446) IDLE(ready,0.1%,30), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:01:41 ago, cause: power up
Last software reset at 2023-05-11 08:25, reason: User, Gcodes spinning, available RAM 80328, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x04
Aux0 errors 0,0,0
MCU temperature: min 31.4, current 37.6, max 37.7
Supply voltage: min 23.8, current 23.9, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.1, current 12.2, max 12.3, under voltage events: 0
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: standstill, SG min 0, mspos 648, reads 35638, writes 19 timeouts 0
Driver 1: standstill, SG min 0, mspos 792, reads 35638, writes 19 timeouts 0
Driver 2: standstill, SG min 0, mspos 216, reads 35638, writes 19 timeouts 0
Driver 3: standstill, SG min n/a, mspos 8, reads 35643, writes 14 timeouts 0
Driver 4: standstill, SG min n/a, mspos 8, reads 35646, writes 11 timeouts 0
Driver 5: standstill, SG min n/a, mspos 8, reads 35647, writes 11 timeouts 0
Date/time: 2023-05-18 08:35:41
Slowest loop: 3.83ms; fastest: 0.07ms
=== Storage ===
Free file entries: 20
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 5.7ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, segments created 3, maxWait 17271ms, bed compensation in use: none, comp offset 0.000
no step interrupt scheduled
=== DDARing 0 ===
Scheduled moves 5, completed 5, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== DDARing 1 ===
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 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== GCodes ===
Movement locks held by null, null
HTTP is idle 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
File2 is idle in state(s) 0
Queue2 is idle in state(s) 0
Q0 segments left 0, axes/extruders owned 0x80000003
Code queue 0 is empty
Q1 segments left 0, axes/extruders owned 0x0000000
Code queue 1 is empty
=== Filament sensors ===
Extruder 0 sensor: ok
=== CAN ===
Messages queued 908, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 50 (min 50), ts 506/0/0
Tx timeouts 0,0,505,0,0,401 last cancelled message type 30 dest 127
=== Network ===
Slowest loop: 5.68ms; fastest: 0.03ms
Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8
= Ethernet =
State: active
Error counts: 0 0 0 1 0 0
Socket states: 5 2 2 2 2 0 0 0
=== Multicast handler ===
Responder is inactive, messages received 0, responses 0

And here is my config.g

; Z-Probe
M558 P5 R0.4 C"io4.in+io4.out" H5 F300 T1800              ; set Z probe type to effector and the dive height + speeds
G31 P100 X0 Y0 Z-0.05                                     ; set Z probe trigger value, offset and trigger height
M557 R110 S20                                             ; define mesh grid

Cause of this, my normal calibration doesn't work.
Is there something I can adjust to take care of it?

[dc42]

@blt3dp when the machine is at standstill:

• Is the green LED on the Smart Effector flashing?
• Is the Z probe reading in DWC changing between 0 and 1000?

[blt3dp]

@dc42

Looks like not specific to 3.5 b3 like I thought, I rolled back to MB firmware 3.4.5 and DWC 3.4.5 and it's still doing the same. The light on the smart effector is flashing. I see varying numbers in the web interface, 0, 312, 500, 625, 1000 are the ones I recall.

Edit, I also unhooked the filament sensor and commented it's line out of config.g
Edit again, it's also a v2 Smart Effector

[blt3dp]

@dc42

It's fixed, turned out it was my cabling. I must have tweaked it somehow when I installed the filament runout sensor. Crimped a whole new set for the 8 pin and is all good now.