[3.6.0-rc.3] sticky probe with 1HCL board

dc42

@ironhydroxide further to my previous message, please execute the following commands both before the probe has stuck and after it has stuck, in each case with the probe not triggered and then with the probe triggered, and report the outputs:

M122 B50 P1007 A{0x40002800} R16
M122 B50 P1007 A{0x41008000} R16

ironhydroxide

@dc42 it's a "simple switch" In that it's a conductive blade on an electrically isolated spindle,
And yes, it's a new system I'm working through feasibility on using the Duet for our fleet of machines.

The tube is connected to the probe ground pin,
The spindle is connected to the input pin, inverted input, with pullup enabled.

When the two connect, the voltage drops and the probe is triggered.

I'll add those commands to my macro and test.

ironhydroxide

@dc42 I added:

M118 P0 S{"PreTrigger: "^sensors.probes[0].value[0]} L2
M122 B50 P1007 A{0x40002800} R16
M122 B50 P1007 A{0x41008000} R16

just before calling G30 in my probe macro,
Then after probe position is "accepted" (probe should still be triggered as Z hasn't moved since G30)

M118 P0 S{"ProbeTriggered: "^sensors.probes[0].value[0]} L2
M122 B50 P1007 A{0x40002800} R16
M122 B50 P1007 A{0x41008000} R16

and then ran the test again.
I noticed the system shut down much more often due to my probe macro not accepting probe points close enough together, than previous tests. Not sure why a log and diagnostic output command could cause that, as I'd think it wouldn't affect anything in the movement or probe interrupt....
I also noticed while running, that the outputs when the probe shouldn't be triggered (pre trigger) often showed probe status of 1000, but didn't error on the G30 command that runs right after, but also often showed status of 0...
And as for the inverse, on the output that should be "triggered" the probe was often reported with status 0, and ONLY reported status 1000 once. though this one I can see that maybe the blade removed enough material to no longer be in contact with the tube in the time between the probe cycle finishing, and my log command running..... though I'd assume that to be microseconds, not milliseconds.

after 3 shutdowns due to my macro, the probe stuck on the 4th running.
I confirmed probe stuck, then ran in the console

M118 P0 S{"Probe Stuck, Probe definitely not triggered: "^sensors.probes[0].value[0]} L2
M122 B50 P1007 A{0x40002800} R16
M122 B50 P1007 A{0x41008000} R16

then lowered my z by 0.05 (definitely contacting my tubing, ie triggered) and ran

M118 P0 S{"Probe Stuck, Probe definitely triggered: "^sensors.probes[0].value[0]} L2
M122 B50 P1007 A{0x40002800} R16
M122 B50 P1007 A{0x41008000} R16

3.6.0-rc3-M122.txt

3.6.0-rc3-M122.xlsx

in the excel, the really low encoder tick points and low probe positions are where I restarted the macro, and it has to go through the findzero macro.

as for the outputs. Directly before probe stuck I got this, (pulled from the log file attached above)

2025-05-09 07:57:09 [info] ProbeTriggered: 0
2025-05-09 07:57:09 [debug] Address 0x40002800: 00000002 00000000 00000000 00002008 00002008 00000000 00000000 0000b000 00b00000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
2025-05-09 07:57:09 [debug] Address 0x41008000: c8040422 c8040422 c8040422 c8040422 08142401 08142401 08142401 08142401 089d3701 00000000 00000000 00000000 01011100 00022022 88002022 07000066
2025-05-09 07:57:10 [info] PreTrigger: 0
2025-05-09 07:57:10 [debug] Address 0x40002800: 00000002 00000000 00000000 00002008 00002008 00000000 00000000 0000b000 00b00000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
2025-05-09 07:57:10 [debug] Address 0x41008000: c8040422 c8040422 c8040422 c8040422 08142401 08142401 08142401 08142401 0a953f01 00000000 00000000 00000000 01011100 00022022 88002022 07000066
........
2025-05-09 07:57:43 [info] PreTrigger: 1000
2025-05-09 07:57:43 [debug] Address 0x40002800: 00000002 00000000 00000000 00002008 00002008 00000000 00000000 0000b000 00b00000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
2025-05-09 07:57:43 [debug] Address 0x41008000: c8040422 c8040422 c8040422 c8040422 00142401 00142401 00142401 00142401 00953f01 00000000 00000000 00000000 01011100 00022022 88002022 07000066

And after stuck here's the outputs of the untriggered, and triggered (of course, in the file above as well)

2025-05-09 07:59:06 [info] Probe Stuck, Probe definitely not triggered 1000
2025-05-09 07:59:06 [debug] Address 0x40002800: 00000002 00000000 00000000 00002008 00002008 00000000 00000000 0000b000 00b00000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
2025-05-09 07:59:06 [debug] Address 0x41008000: c8040422 c8040422 c8040422 c8040422 48142401 48142401 48142401 48142401 4a9d3f01 00000000 00000000 00000000 01011100 00022022 88002022 07000066
2025-05-09 08:00:02 [info] Probe Stuck, Probe definitely triggered 1000
2025-05-09 08:00:02 [debug] Address 0x40002800: 00000002 00000000 00000000 00002008 00002008 00000000 00000000 0000b000 00b00000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
2025-05-09 08:00:02 [debug] Address 0x41008000: c8040422 c8040422 c8040422 c8040422 40142401 40142401 40142401 40142401 419d3f01 00000000 00000000 00000000 01011100 00022022 88002022 07000066

dc42

@ironhydroxide thank you for your reports.

I am having difficulty interpreting them. Your config.g file uses this M558 line:

M558 P8 C"!50.io1.in" H1:0.00254 F2.425:0.0363255 T100 K0 A10 S0.00127 B0 ; configure blade probe

which indicates that your probe is connected to pin io1.in on the EXP1HCL board at address 50. In the M122 responses that use address 0x41008000 the 9th word after the colon shows the input state of all pins of Port A. Pin io1.in is connected to Port A pin 13, so bit 13 of that word should show the state of the probe inputs. That's the bit worth 0x00002000. In your reports that word has values 089d3701, 0a953f01, 00953f01, 4a9d3f01 and 419d3f01. In all cases that bit is set, indicating that the input pin is high.

Is the probe still connected to pin io1.in of board 50?

ironhydroxide

@dc42 Yes, It is still connected to the board 50 io1.in pin. inverted with pullup.
If I understand correctly that would indicate that the probing setup is not actually dragging the input pin down below the trigger point (i'd guess 1.65v, due to the trigger being set at 500 of 1000) at the moment the request is sent.

Maybe I need to setup a scope on this probe input and confirm that it is in fact getting dragged down, and how that signal might look. If it's noisy when near the tube it might trigger before, or long after the initial touch on the tube.

I have been assuming that it has due to the blade being in contact with the tube, and the probe cycle completing,

ironhydroxide

@dc42 I left the machine in the stuck probe status, so I was able to retest, confirming with a multimeter that the probe was and was not triggered (3v and 0v)

5/9/2025, 9:58:11 AM: M118 P0 S{"Probe Stuck, Probe definitely not triggered "^sensors.probes[0].value[0]} L2 M122 B50 P1007 A{0x40002800} R16 M122 B50 P1007 A{0x41008000} R16: Probe Stuck, Probe definitely not triggered 1000

Address 0x40002800: 00000002 00000000 00000000 00002008 00002008 00000000 00000000 0000b000 00b00000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Address 0x41008000: c8040422 c8040422 c8040422 c8040422 00142401 00142401 00142401 00142401 00953701 00000000 00000000 00000000 01011100 00022022 88002022 07000066
5/9/2025, 9:59:03 AM: M118 P0 S{"Probe Stuck, Probe definitely Triggered"^sensors.probes[0].value[0]} L2 M122 B50 P1007 A{0x40002800} R16 M122 B50 P1007 A{0x41008000} R16: Probe Stuck, Probe definitely Triggered1000

Address 0x40002800: 00000002 00000000 00000000 00002008 00002008 00000000 00000000 0000b000 00b00000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Address 0x41008000: c8040422 c8040422 c8040422 c8040422 40142401 40142401 40142401 40142401 42951701 00000000 00000000 00000000 01011100 00022022 88002022 07000066

Then reset the sticky probe, and did the same. confirming the first time it's not triggered, and triggered the second, with a multimeter.

5/9/2025, 10:03:36 AM: M118 P0 S{"Probe Stuck, Probe definitely not Triggered"^sensors.probes[0].value[0]} L2 M122 B50 P1007 A{0x40002800} R16 M122 B50 P1007 A{0x41008000} R16: Probe Stuck, Probe definitely not Triggered0

Address 0x40002800: 00000002 00000000 00000000 00002008 00002008 00000000 00000000 0000b000 00b00000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Address 0x41008000: c8040422 c8040422 c8040422 c8040422 00142401 00142401 00142401 00142401 02953701 00000000 00000000 00000000 01011100 00022022 88002022 07000066
5/9/2025, 10:04:04 AM: M118 P0 S{"Probe Stuck, Probe definitely Triggered"^sensors.probes[0].value[0]} L2 M122 B50 P1007 A{0x40002800} R16 M122 B50 P1007 A{0x41008000} R16: Probe Stuck, Probe definitely Triggered1000

Address 0x40002800: 00000002 00000000 00000000 00002008 00002008 00000000 00000000 0000b000 00b00000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Address 0x41008000: c8040422 c8040422 c8040422 c8040422 00142401 00142401 00142401 00142401 009d1f01 00000000 00000000 00000000 01011100 00022022 88002022 07000066

dc42

@ironhydroxide said in [3.6.0-rc.3] sticky probe with 1HCL board:

Yes, It is still connected to the board 50 io1.in pin. inverted with pullup.

Don't enable the pullup in the M558 command. There is a permanent pullup resistor on that pin. It has quite a high value, so you may wish to add an external pullup to +3.3V or +5V. Enabling the internal pullup as well reduces the noise immunity because of the series resistor on the board.

The responses that you posted most recently look better, the 5th digit changes between 1 and 3 depending on whether the probe is triggered or not.

ironhydroxide

@dc42 said in [3.6.0-rc.3] sticky probe with 1HCL board:

Don't enable the pullup in the M558 command. There is a permanent pullup resistor on that pin.

AH, good to know.

In the full run I see that hex digit swap between 1 and 3, but it's more often 3 than 1 (should alternate if it is working 100% of the time correctly).
I'll drop the pullup and do some more tests.

dc42

@ironhydroxide please can you run one further test and post the responses:

Get the probe into the "stuck" state (make quite sure that it really is stuck)
Send m122 b50 p1007 a{0x40002800} R16 as before
Send m122 b50 p1007 a{0x4000280c} v{0x00002000}
Change the state of the input (it doesn't matter if you change it more than once)
Send m122 b50 p1007 a{0x40002800} R16 as before

ironhydroxide

@dc42 Here's the output of those.
Step2 didn't give me an output... is that what was intended?

from the console

5/12/2025, 8:04:01 AM: M118 P0 S{"Stuck Probe Confirmed"} L2: Stuck Probe Confirmed
5/12/2025, 8:04:08 AM: m122 b50 p1007 a{0x40002800} R16
5/12/2025, 8:04:09 AM: : Address 0x40002800: 00000002 00000000 00000000 00002008 00002008 00000000 00000000 0000b000 00b00000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
5/12/2025, 8:04:30 AM: m122 b50 p1007 a{0x4000280c} v{0x00002000}
5/12/2025, 8:05:26 AM: M118 P0 S{"Before changing probe state"} L2 m122 b50 p1007 a{0x40002800} R16: Before changing probe state

Address 0x40002800: 00000002 00000000 00000000 00000008 00000008 00000000 00000000 0000b000 00b00000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
5/12/2025, 8:06:14 AM: M118 P0 S{"After changing probe state"} L2 m122 b50 p1007 a{0x40002800} R16: After changing probe state

Address 0x40002800: 00000002 00000000 00000000 00000008 00000008 00002000 00000000 0000b000 00b00000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
5/12/2025, 8:06:49 AM: M118 P0 S{"After changing probe 2nd time probe not triggered"} L2 m122 b50 p1007 a{0x40002800} R16: After changing probe 2nd time probe not triggered

Address 0x40002800: 00000002 00000000 00000000 00000008 00000008 00002000 00000000 0000b000 00b00000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
5/12/2025, 8:07:18 AM: M118 P0 S{"After changing probe 3rd time probe triggered"} L2 m122 b50 p1007 a{0x40002800} R16: After changing probe 3rd time probe triggered

Address 0x40002800: 00000002 00000000 00000000 00000008 00000008 00002000 00000000 0000b000 00b00000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

end of the eventlog

2025-05-12 08:04:00 [info] Stuck Probe Confirmed
2025-05-12 08:04:07 [debug] Address 0x40002800: 00000002 00000000 00000000 00002008 00002008 00000000 00000000 0000b000 00b00000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
2025-05-12 08:05:25 [info] Before changing probe state
2025-05-12 08:05:25 [debug] Address 0x40002800: 00000002 00000000 00000000 00000008 00000008 00000000 00000000 0000b000 00b00000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
2025-05-12 08:06:14 [info] After changing probe state
2025-05-12 08:06:14 [debug] Address 0x40002800: 00000002 00000000 00000000 00000008 00000008 00002000 00000000 0000b000 00b00000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
2025-05-12 08:06:48 [info] After changing probe 2nd time probe not triggered
2025-05-12 08:06:48 [debug] Address 0x40002800: 00000002 00000000 00000000 00000008 00000008 00002000 00000000 0000b000 00b00000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
2025-05-12 08:07:17 [info] After changing probe 3rd time probe triggered
2025-05-12 08:07:17 [debug] Address 0x40002800: 00000002 00000000 00000000 00000008 00000008 00002000 00000000 0000b000 00b00000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

Full files here
eventlog.txt
eventlog.xlsx

dc42

@ironhydroxide thanks. if you mean that step "3. Send m122 b50 p1007 a{0x4000280c} v{0x00002000}" didn't produce any output, that's expected.

ironhydroxide

@dc42 doh, yeah, step 3

dc42

@ironhydroxide if you haven't reset the board yet please try sending this:

m122 b50 p1007 a{0x40002810} v{0x00002000}

and see whether the probe works after that, or is still stuck.

ironhydroxide

@dc42 Sadly reset the board already, but will go through the steps again adding that.

dc42

@ironhydroxide also please post the report from M122 B50 after the probe is stuck.

dc42

@ironhydroxide PS - one more check please. Normally, when the probe state changes, the green LED on the 1HCL next to the red blinking LED should flash. Please check this. Does the green LED still flash when the probe input changes state but the status appears stuck?

ironhydroxide

@dc42 OK,

Ran the test again. Watched the LED labeled ACI flash during normal probe moves (before stuck)

When stuck and manually triggering the probe the LED labeled ACI does not flash or turn on/off.

Did M122 and M122 B50.0 once stuck,
after the 3rd step above,
and after the latest commands you gave me.

The Probe is once again functional after the latest command, confirmed by running a probe, as well as watching the ACI LED.

5/12/2025, 11:03:03 AM: M118 P0 S{"Stuck Probe Confirmed"} L2: Stuck Probe Confirmed
5/12/2025, 11:03:09 AM: M122 B50.0: Diagnostics for board 50:
Duet EXP1HCL rev 1.0a or earlier firmware version 3.6.0-rc.3 (2025-04-29 14:20:58)
Bootloader ID: SAME5x bootloader version 2.4 (2021-12-10)
All averaging filters OK
Never used RAM 51300, free system stack 154 words
Tasks: EncCal(1,nWait 6,0.0%,469) Move(3,nWait 7,0.0%,119) CLSend(3,nWait 6,0.0%,149) TMC(2,nWait 6,64.5%,313) HEAT(2,nWait 6,0.0%,107) CanAsync(5,nWait 4,0.0%,66) CanRecv(3,nWait 1,0.0%,31) CanClock(5,nWait 1,0.0%,63) MAIN(1,running,34.5%,249) IDLE(0,ready,0.0%,29) AIN(2,nWait 2,0.9%,255), total 100.0%
Owned mutexes:
Last reset 02:38:14 ago, cause: power up
Last software reset time unknown, reason: HardFault zeroDiv, available RAM 51444, slot 2
Software reset code 0x0060 HFSR 0x40000000 CFSR 0x02000000 ICSR 0x00000803 BFAR 0xe000ed38 SP 0x20002cc0 Task TMC Freestk 366 ok
Stack: 00000000 20002d2f 00000000 00000000 00000000 00026359 00026368 41000000 0018a715 00024de3 20019948 20019948 00000001 00025d53 00025d3d 2001a874 001ceac9 00027c73 01601008 a0180030 08004d84 41c31e52 05c80021 3a341809 002ad181 2001a7c0 001ceac9
Moves scheduled 3003, hiccups 0 (0.00/0.00ms), segs 3, step errors 0 (types 0x0), maxLate 0 maxPrep 12, ebfmin 0.00 max 0.00
Phase step loop runtime (us): min=6, max=250, frequency (Hz): min=2767, max=17857
Sync err accum 68, peak jitter -4/4, peak Rx delay 180, resyncs 0/0, next timer interrupt due in 11 ticks, enabled, next step interrupt due in 4251168817 ticks, disabled
VIN voltage: min 24.4, current 24.4, max 24.4
V12 voltage: min 12.2, current 12.2, max 12.2
MCU temperature: min 23.4C, curDriver 0: pos -7356, 10060.2 steps/mm, standstill, SG min 0, mspos 824, reads 35839, writes 2 timeouts 0
Last sensors broadcast 0x00000000 found 0 72 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 555, send timeouts 0, received 309, lost 0, ignored 0, errs 0, boc 0, free buffers 38, min 38, error reg 0
dup 0, oos 0/0/0/0, rxMotionDelay 290, adv 36182/37178
Closed loop driver 0 mode: open loop, pre-error threshold: 7.50, error threshold: 50.00, encoder type linearComposite, position 1742
Shaft: Encoder reverse polarity: yes, full rotations 3, last angle 7017, minCorrection=-15.4, maxCorrection=10.9, agc 16, mag 4759, no error
Lin: Encoder reverse polarity: no, raw count 1742
Accelerometer: none
I2C bus errors 0, naks 0, contentions 0, other errors 0
5/12/2025, 11:03:15 AM: M122: === Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.6.0-rc.3 (2025-04-30 14:42:33) running on Duet 3 Mini5plus Ethernet (standalone mode)
Board ID: G5729-TU8LU-F65J0-409NU-3F03Z-7U6T6
Used output buffers: 1 of 40 (38 max)
=== RTOS ===
Static ram: 94764
Dynamic ram: 117524 of which 0 recycled
Never used RAM 28988, free system stack 136 words
Tasks: NETWORK(1,ready,23.3%,143) ETHERNET(5,nWait 7,0.0%,569) HEAT(3,nWait 6,0.0%,357) Move(4,nWait 6,0.0%,241) TMC(4,nWait 6,0.8%,65) CanReceiv(6,nWait 1,0.0%,755) CanSender(5,nWait 7,0.0%,324) CanClock(7,delaying,0.0%,337) MAIN(1,running,75.1%,659) IDLE(0,ready,0.0%,29) USBD(3,blocked,0.0%,147) AIN(4,delaying,0.8%,261), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 02:38:19 ago, cause: power up
Last software reset at 2025-05-09 12:14, reason: User, Gcodes spinning, available RAM 30268, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x04
MCU temperature: min 20.6, current 35.4, max 40.4
Supply voltage: min 22.8, current 23.9, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/37, heap memory allocated/used/recyclable 2048/1516/816, gc cycles 770
Events: 0 queued, 0 completed
Date/time: 2025-05-12 11:03:14
Slowest loop: 1038.30ms; fastest: 0.16ms
=== Storage ===
Free file entries: 19
SD card 0 detected, requested/actual speed: 25.0/24.0MBytes/sec
SD card longest read time 5.7ms, write time 163.5ms, max retries 0
=== Move ===
Segments created 8, maxWait 7451243ms, bed comp in use: none, height map offset 0.000, hiccups added 0/0 (0.00/0.00ms), max steps late 1, ebfmin 0.00, ebfmax 0.00
Pos req/act/dcf: 0.00/0/0.00 12721.00/12721/0.00 248.00/247/0.98 570.00/570/-0.00 26666.00/26666/0.00
No step interrupt scheduled
Driver 0: standstill, SG min 0, r/w errs 0/0, ifcnt 18, reads/writes 41195/18, timeouts 0, DMA errs 0, CC errs 0
Driver 1: standstill, SG min 0, r/w errs 0/0, ifcnt 18, reads/writes 41195/18, timeouts 0, DMA errs 0, CC errs 0
Driver 2: standstill, SG min 0, r/w errs 0/0, ifcnt 18, reads/writes 41195/18, timeouts 0, DMA errs 0, CC errs 0
Driver 3: standstill, SG min 0, r/w errs 0/0, ifcnt 10, reads/writes 41202/10, timeouts 0, DMA errs 0, CC errs 0
Driver 4: standstill, SG min 0, r/w errs 0/0, ifcnt 10, reads/writes 41203/10, timeouts 0, DMA errs 0, CC errs 0
Driver 5: not present
Driver 6: not present
=== DDARing 0 ===
Scheduled moves 96, completed 96, LaErrors 0, Underruns [0, 0, 0]
Segments left 0, axes/extruders owned 0x00000003, drives owned 0x00000003
Code queue is empty
=== DDARing 1 ===
Scheduled moves 0, completed 0, LaErrors 0, Underruns [0, 0, 0]
Segments left 0, axes/extruders owned 0x00000000, drives owned 0x00000000
Code queue is empty
=== Heat ===
Bed heaters -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
=== CAN ===
Messages queued 58847, received 136738, lost 0, ignored 0, errs 4447, boc 0
Longest wait 265ms for reply type 6041, peak Tx sync delay 23632, free buffers 26 (min 25), ts 45023/45018/0
Tx timeouts 0,0,4,0,0,0 last cancelled message type 30 dest 127
=== Network ===
Slowest loop: 192.81ms; fastest: 0.03ms
Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8
= Ethernet =
Interface state: active
Error counts: 0 0 0 0 0 0
Socket states: 6 2 2 2 2 0 0 0 0
5/12/2025, 11:03:31 AM: m122 b50 p1007 a{0x40002800} R16: Address 0x40002800: 00000002 00000000 00000000 00002008 00002008 00000000 00000000 0000b000 00b00000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
5/12/2025, 11:03:49 AM: m122 b50 p1007 a{0x4000280c} v{0x00002000}
5/12/2025, 11:07:10 AM: M118 P0 S{"Changed Probe state"} L2: Changed Probe state
5/12/2025, 11:07:18 AM: M122 B50.0: Diagnostics for board 50:
Duet EXP1HCL rev 1.0a or earlier firmware version 3.6.0-rc.3 (2025-04-29 14:20:58)
Bootloader ID: SAME5x bootloader version 2.4 (2021-12-10)
All averaging filters OK
Never used RAM 51300, free system stack 154 words
Tasks: EncCal(1,nWait 6,0.0%,469) Move(3,nWait 7,0.0%,119) CLSend(3,nWait 6,0.0%,149) TMC(2,nWait 6,64.5%,313) HEAT(2,nWait 6,0.0%,107) CanAsync(5,nWait 4,0.0%,66) CanRecv(3,nWait 1,0.0%,31) CanClock(5,nWait 1,0.0%,63) MAIN(1,running,34.6%,249) IDLE(0,ready,0.0%,29) AIN(2,nWait 2,0.9%,255), total 100.0%
Owned mutexes:
Last reset 02:42:23 ago, cause: power up
Last software reset time unknown, reason: HardFault zeroDiv, available RAM 51444, slot 2
Software reset code 0x0060 HFSR 0x40000000 CFSR 0x02000000 ICSR 0x00000803 BFAR 0xe000ed38 SP 0x20002cc0 Task TMC Freestk 366 ok
Stack: 00000000 20002d2f 00000000 00000000 00000000 00026359 00026368 41000000 0018a715 00024de3 20019948 20019948 00000001 00025d53 00025d3d 2001a874 001ceac9 00027c73 01601008 a0180030 08004d84 41c31e52 05c80021 3a341809 002ad181 2001a7c0 001ceac9
Moves scheduled 3003, hiccups 0 (0.00/0.00ms), segs 3, step errors 0 (types 0x0), maxLate 0 maxPrep 0, ebfmin 0.00 max 0.00
Phase step loop runtime (us): min=6, max=78, frequency (Hz): min=5395, max=17441
Sync err accum 78, peak jitter -4/5, peak Rx delay 183, resyncs 0/0, next timer interrupt due in 9 ticks, enabled, next step interrupt due in 4064199594 ticks, disabled
VIN voltage: min 24.4, current 24.4, max 24.4
V12 voltage: min 12.2, current 12.2, max 12.2
MCU temperature: min 23.4C, currenDriver 0: pos -7356, 10060.2 steps/mm, standstill, SG min n/a, mspos 824, reads 35605, writes 0 timeouts 0
Last sensors broadcast 0x00000000 found 0 114 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 2040, send timeouts 0, received 1191, lost 0, ignored 0, errs 0, boc 0, free buffers 38, min 38, error reg 0
dup 0, oos 0/0/0/0, rxMotionDelay 0
Closed loop driver 0 mode: open loop, pre-error threshold: 7.50, error threshold: 50.00, encoder type linearComposite, position 1741
Shaft: Encoder reverse polarity: yes, full rotations 3, last angle 7020, minCorrection=-15.4, maxCorrection=10.9, agc 16, mag 4750, no error
Lin: Encoder reverse polarity: no, raw count 1741
Accelerometer: none
I2C bus errors 0, naks 0, contentions 0, other errors 0
5/12/2025, 11:07:34 AM: m122 b50 p1007 a{0x40002800} R16: Address 0x40002800: 00000002 00000000 00000000 00000008 00000008 00002000 00000000 0000b000 00b00000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
5/12/2025, 11:09:13 AM: m122 b50 p1007 a{0x40002810} v{0x00002000}
5/12/2025, 11:09:57 AM: M122 B50.0: Diagnostics for board 50:
Duet EXP1HCL rev 1.0a or earlier firmware version 3.6.0-rc.3 (2025-04-29 14:20:58)
Bootloader ID: SAME5x bootloader version 2.4 (2021-12-10)
All averaging filters OK
Never used RAM 51300, free system stack 154 words
Tasks: EncCal(1,nWait 6,0.0%,469) Move(3,nWait 7,0.0%,119) CLSend(3,nWait 6,0.0%,149) TMC(2,nWait 6,1.7%,313) HEAT(2,nWait 6,0.0%,107) CanAsync(5,nWait 4,0.0%,66) CanRecv(3,nWait 1,0.0%,31) CanClock(5,nWait 1,0.0%,63) MAIN(1,running,98.2%,249) IDLE(0,ready,0.0%,29) AIN(2,nWait 2,0.0%,255), total 100.0%
Owned mutexes:
Last reset 02:45:02 ago, cause: power up
Last software reset time unknown, reason: HardFault zeroDiv, available RAM 51444, slot 2
Software reset code 0x0060 HFSR 0x40000000 CFSR 0x02000000 ICSR 0x00000803 BFAR 0xe000ed38 SP 0x20002cc0 Task TMC Freestk 366 ok
Stack: 00000000 20002d2f 00000000 00000000 00000000 00026359 00026368 41000000 0018a715 00024de3 20019948 20019948 00000001 00025d53 00025d3d 2001a874 001ceac9 00027c73 01601008 a0180030 08004d84 41c31e52 05c80021 3a341809 002ad181 2001a7c0 001ceac9
Moves scheduled 3003, hiccups 0 (0.00/0.00ms), segs 3, step errors 0 (types 0x0), maxLate 0 maxPrep 0, ebfmin 0.00 max 0.00
Phase step loop runtime (us): min=6, max=146, frequency (Hz): min=4838, max=17441
Sync err accum 70, peak jitter -5/4, peak Rx delay 183, resyncs 0/0, next timer interrupt due in 13 ticks, enabled, next step interrupt due in 3945272543 ticks, disabled
VIN voltage: min 24.4, current 24.4, max 24.4
V12 voltage: min 12.2, current 12.2, max 12.2
MCU temperature: min 23.4C, currDriver 0: pos -7356, 10060.2 steps/mm, standstill, SG min n/a, mspos 824, reads 15703, writes 0 timeouts 0
Last sensors broadcast 0x00000000 found 0 184 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 1352, send timeouts 0, received 762, lost 0, ignored 0, errs 0, boc 0, free buffers 38, min 38, error reg 0
dup 0, oos 0/0/0/0, rxMotionDelay 0
Closed loop driver 0 mode: open loop, pre-error threshold: 7.50, error threshold: 50.00, encoder type linearComposite, position 1741
Shaft: Encoder reverse polarity: yes, full rotations 3, last angle 7019, minCorrection=-15.4, maxCorrection=10.9, agc 16, mag 4750, no error
Lin: Encoder reverse polarity: no, raw count 1741
Accelerometer: none
I2C bus errors 0, naks 0, contentions 0, other errors 0
5/12/2025, 11:10:02 AM: M122: === Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.6.0-rc.3 (2025-04-30 14:42:33) running on Duet 3 Mini5plus Ethernet (standalone mode)
Board ID: G5729-TU8LU-F65J0-409NU-3F03Z-7U6T6
Used output buffers: 1 of 40 (38 max)
=== RTOS ===
Static ram: 94764
Dynamic ram: 117524 of which 0 recycled
Never used RAM 28988, free system stack 136 words
Tasks: NETWORK(1,ready,23.7%,143) ETHERNET(5,nWait 7,0.1%,569) HEAT(3,nWait 6,0.0%,357) Move(4,nWait 6,0.0%,241) TMC(4,nWait 6,0.8%,65) CanReceiv(6,nWait 1,0.0%,755) CanSender(5,nWait 7,0.0%,324) CanClock(7,delaying,0.0%,337) MAIN(1,running,74.6%,659) IDLE(0,ready,0.0%,29) USBD(3,blocked,0.0%,147) AIN(4,delaying,0.8%,261), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 02:45:06 ago, cause: power up
Last software reset at 2025-05-09 12:14, reason: User, Gcodes spinning, available RAM 30268, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x04
MCU temperature: min 34.3, current 34.3, max 35.4
Supply voltage: min 23.9, current 24.0, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/37, heap memory allocated/used/recyclable 2048/1540/840, gc cycles 770
Events: 0 queued, 0 completed
Date/time: 2025-05-12 11:10:01
Slowest loop: 70.55ms; fastest: 0.16ms
=== Storage ===
Free file entries: 19
SD card 0 detected, requested/actual speed: 25.0/24.0MBytes/sec
SD card longest read time 3.3ms, write time 3.8ms, max retries 0
=== Move ===
Segments created 8, maxWait 0ms, bed comp in use: none, height map offset 0.000, hiccups added 0/0 (0.00/0.00ms), max steps late 0, ebfmin 0.00, ebfmax 0.00
Pos req/act/dcf: 0.00/0/0.00 12721.00/12721/0.00 248.00/247/0.98 570.00/570/-0.00 26666.00/26666/0.00
No step interrupt scheduled
Driver 0: standstill, SG min 16, r/w errs 0/0, ifcnt 18, reads/writes 21421/0, timeouts 0, DMA errs 0, CC errs 0
Driver 1: standstill, SG min 14, r/w errs 0/0, ifcnt 18, reads/writes 21421/0, timeouts 0, DMA errs 0, CC errs 0
Driver 2: standstill, SG min 14, r/w errs 0/0, ifcnt 18, reads/writes 21420/0, timeouts 0, DMA errs 0, CC errs 0
Driver 3: standstill, SG min 0, r/w errs 0/0, ifcnt 10, reads/writes 21421/0, timeouts 0, DMA errs 0, CC errs 0
Driver 4: standstill, SG min 0, r/w errs 0/0, ifcnt 10, reads/writes 21421/0, timeouts 0, DMA errs 0, CC errs 0
Driver 5: not present
Driver 6: not present
=== DDARing 0 ===
Scheduled moves 96, completed 96, LaErrors 0, Underruns [0, 0, 0]
Segments left 0, axes/extruders owned 0x00000003, drives owned 0x00000003
Code queue is empty
=== DDARing 1 ===
Scheduled moves 0, completed 0, LaErrors 0, Underruns [0, 0, 0]
Segments left 0, axes/extruders owned 0x00000000, drives owned 0x00000000
Code queue is empty
=== Heat ===
Bed heaters -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
=== CAN ===
Messages queued 1949, received 3386, lost 0, ignored 0, errs 0, boc 0
Longest wait 8ms for reply type 6024, peak Tx sync delay 228, free buffers 26 (min 25), ts 1929/1929/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 5.18ms; fastest: 0.04ms
Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8
= Ethernet =
Interface state: active
Error counts: 0 0 0 0 0 0
Socket states: 2 6 2 2 2 0 0 0 0
5/12/2025, 11:15:19 AM: M118 P0 S{"Probe Now Functional"} L2: Probe Now Functional

dc42

@ironhydroxide thanks.

Unfortunately I haven't succeeded in reproducing your issue, and I can't see anything wrong with the software. My best guess is that intermittent contact between the blade and the tube is generating several interrupts in succession, and this is temporarily locking up the interrupt system. I can try changing a few things to see if this can be avoided.

My first attempt is the new 1HCL firmware at https://www.dropbox.com/scl/fo/dumsdufoej44q97ek9joo/AIBRnU-wtKfMrbWPzZwH_XY?rlkey=idmyinvvcuiwmycbb1l2obz38&dl=0. Please try it.

ironhydroxide

@dc42 said in [3.6.0-rc.3] sticky probe with 1HCL board:

My best guess is that intermittent contact between the blade and the tube is generating several interrupts in succession,

I would say this is more likely the problem.
I'll test with the rc3+1 and let you know what happens, but at this point I think I will probably go back to the mainboard connected probe and see if I can get it to be happier there with trying the filtered vs unfiltered settings.

The system I'm trying to replace with this has a weird capacitive pump setup and measures the difference in voltage after a delay, timed to the pump cycling. But that system is 8bit, was hoping something modern would be able to handle a simpler setup.

dc42

@ironhydroxide it's likely that we could solve this using a R-C network to filter the input from the probe; but we should be able to solve this in software too. There is a debounce facility available in the MCU that I will try enabling if necessary.

We're hoping to release 3.6.0 stable later this week. It would be good to get this issue fixed first.