Duet 3 Mini BLTouch Not RETRACTING

airscapes

Hi, sorry for more questions I should be able to find answer for.
Duet 3 min current 3.5.x firmware just installed last week.

M950 S0 C"io3.out"                              ; create servo pin 0 for BLTouch (IO_1/2/3 for Mini 5+)
M558 P9 C"io3.in" H3 F75 T6000 A3 R0 S0.03 B0.  ; Z probe, not end stop.
G31 X0 Y-21 Z1.037

Wired like this

When powered on probe deploys and retract 2 time and stays retracted. Red LED is on no Blue LED. If I home and send G30 it will deploy and go dark and stay deployed. I am at wits end... Not sure if this is a probe issue of more likely a config/wiring issue. I have it wired to 5v as it said it did not matter?
Thanks in advance.

robotsneversleep

@airscapes This is what I have for my BLTouch on Duet 3 Mini 5+

M950 S0 C"io1.out"
M558 P9 C"^io1.in" H2 F240 T6000
G31 P500 X0 Y25 Z2.43

Is it possible you need to enable the pullup on io3.in?
EDIT: I assume you have the appropriate deployprobe.g and retractprobe.g macros:

;
; deployprobe.g
; called to deploy a physical Z probe
;

M280 P0 S10 ; deploy BLTouch

;
; retractprobe.g
; called to retract a physical Z probe
;

M280 P0 S90 ; retract BLTouch

airscapes

@robotsneversleep No idea, it does not say to do so in any instructrions. I01-3 are all PWM ports.. I am really wishing I had used duet 2..
Since posting I ran M280 P0 S120 with the lights out in the room. The sensor does it' self test 10 times. The blue light is on. after this is done if I do a M401 and it deploys and goes dark, no lights a all. M402 does not retract it. Another attempt at m280 and self test runs again.
If I the pull the probe down it stays down and dark, if I push it up again it is red.. Think I read something about adjusting he core..seems like there is not enough magnetic attractions. Did not really help. on my workng BLTouch on DUet2 when probe is pulled down it snaps right back up.
Yes I have those values in both scripts, they came from the an identical machine with a working probe but Duet 2 board.
OH I did not have the ^ in the M558 line but adding it changed nothing.

airscapes

UPDATE: I have swapped both Probes between the working M2 with Duet 2 and the non working M2 with Duet 3 mini. Both probes work the same on the Duet 2 and neither work correctly on the Duet 3 mini.
Simplest test is M401 deploys, M402 does Nothing at all .
It is like the servo is not powered to retract, what did I miss on the configurations????
Ground is ground so I don't think it matters both black and brown are attached to the io port ground.

Phaedrux

@airscapes said in Duet 3 Mini BLTouch Not RETRACTING:

swapped both Probes between the working M2 with Duet 2 and the non working M2 with Duet 3 mini. Both probes work the same on the Duet 2 and neither work correctly on the Duet 3 mini.

Does that include the wiring?

your config looks ok and the wiring looks ok.

Can you send M122 and M98 P"config.g" and share the results here?

airscapes

@Phaedrux HI Phaedrux, no I did not swap the cable since the Duet2 and Duet 3 have different connection points and connectors. Just pulled the probes to make sure the new one was not defective. The cables are single cables running from the probe to the board, Duet 2 I think is 2 meters Duet 3 is 1 meter long
They are both V1.3 which I had not posted originally.
I did check the crimp connections with a continuity tester and all were good.

So this morning with a clear head , after running the 2 command requested I rechecked a few things.

M280 P0 S120 works
M280 P0 S10 works
M280 P0 S90 works
M401 works
M402 does not
G28
G1 F1000 X100 Y125 Z5
G30
Probe deploys
Bed rises
Probe triggers but does not retract
bed drop and rises
Probe triggers but does not retract
Ends with red led off blue LED on
G30 can be run again with same results
On the duet 2
G30 triggers and retracts, deploys, triggers and retracts, ending red and blue light on.

No idea what G30 does, but if it relies on M402 could be a firmware bug?
Probe works, wiring works M280s work but G30 does not work as expected.
I guess next step is to revert to 3.4? Does that wipe my config and all files? Have only upgraded and not sure of those steps if that is the next place to go.

Video of Duet 2 G30 working correctly
https://youtu.be/6kOmml-o4M0
Video Duet 3 G30 Not working correctly
https://youtu.be/uaodohkrZVQ

5/16/2024, 7:44:22 AM M122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.5.1 (2024-04-19 14:41:25) running on Duet 3 Mini5plus Ethernet (standalone mode)
Board ID: JLUSU-MT8LU-F65J0-409NU-M503Z-ZMRV2
Used output buffers: 1 of 40 (18 max)
=== RTOS ===
Static ram: 103232
Dynamic ram: 115964 of which 12 recycled
Never used RAM 19352, free system stack 208 words
Tasks: NETWORK(1,ready,23.4%,171) ETHERNET(5,nWait 7,0.1%,577) HEAT(3,nWait 1,0.0%,351) Move(4,nWait 6,0.0%,355) CanReceiv(6,nWait 1,0.0%,940) CanSender(5,nWait 7,0.0%,336) CanClock(7,delaying,0.0%,339) TMC(4,nWait 6,0.7%,111) MAIN(1,running,74.1%,665) IDLE(0,ready,0.8%,30) AIN(4,delaying,0.8%,264), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:00:18 ago, cause: power up
Last software reset at 2024-05-15 18:02, reason: User, Gcodes spinning, available RAM 19352, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
MCU revision 3, ADC conversions started 18895, completed 18895, timed out 0, errs 0
MCU temperature: min 22.6, current 25.9, max 25.9
Supply voltage: min 24.1, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/12/12, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 0, read errors 0, write errors 0, ifcnt 10, reads 953, writes 10, timeouts 0, DMA errors 0, CC errors 0
Driver 1: standstill, SG min 0, read errors 0, write errors 0, ifcnt 10, reads 953, writes 10, timeouts 0, DMA errors 0, CC errors 0
Driver 2: standstill, SG min 0, read errors 0, write errors 0, ifcnt 10, reads 952, writes 10, timeouts 0, DMA errors 0, CC errors 0
Driver 3: standstill, SG min 0, read errors 0, write errors 0, ifcnt 10, reads 952, writes 10, timeouts 0, DMA errors 0, CC errors 0
Driver 4: standstill, SG min 0, read errors 0, write errors 0, ifcnt 10, reads 953, writes 10, timeouts 0, DMA errors 0, CC errors 0
Driver 5: not present
Driver 6: not present
Date/time: 2024-05-16 07:44:21
Cache data hit count 32633200
Slowest loop: 8.29ms; fastest: 0.15ms
=== Storage ===
Free file entries: 20
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 3.4ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00
no step interrupt scheduled
Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0
=== DDARing 0 ===
Scheduled moves 0, completed 0, 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, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Movement locks held by null, null
HTTP is ready with "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
File2 is idle in state(s) 0
Queue2 is idle in state(s) 0
Q0 segments left 0, axes/extruders owned 0x0000803
Code queue 0 is empty
Q1 segments left 0, axes/extruders owned 0x0000000
Code queue 1 is empty
=== CAN ===
Messages queued 166, received 0, lost 0, errs 87749, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 26 (min 26), ts 94/0/0
Tx timeouts 0,0,93,0,0,71 last cancelled message type 30 dest 127
=== Network ===
Slowest loop: 4.39ms; 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: 5 2 2 2 2 2 0 0

5/16/2024, 7:49:06 AM M98 P"config.g"
HTTP is enabled on port 80
FTP is enabled on port 21
TELNET is disabled
Warning: Heater 1 predicted maximum temperature at full power is 497°C

droftarts

@airscapes said in Duet 3 Mini BLTouch Not RETRACTING:

M402 does not

What's in your 'retractprobe.g'?

Ian

airscapes

@droftarts
deployprobe.g M280 P0 S10 works
retractprobe.g M280 P0 S90 works
OMFG
This is a classic Doug.. retractprob.g is not retractprobe.g..
Wow, I apologize
But thank you Ian.. I am guessing after I fix that i will be good to go

droftarts

@airscapes RRF can be a cruel mistress! Hopefully that fixes the issue.

Ian

airscapes

@droftarts Yup.. works as expected. Had I know 402 read those config files I would have figured it out last night.. thanks and sorry for the wasted time.