bltouch on duet maestro

[jcwild]

ive followed the guide on this page: https://duet3d.dozuki.com/Wiki/Connecting_a_Z_probe#Section_Software_setup_Duet_2_Maestro_running_RepRapFirmware_Num_2
and when i turn the printer on either nothing happens or the probe just deploys and retracts over and over forever

[Phaedrux]

Please share your config.g and the results of M122 and M98 P"config.g"

Double check your wiring as well.

Does the Bltouch respond to any servo commands?

[jcwild]

@phaedrux
=== Diagnostics ===
RepRapFirmware for Duet 2 Maestro version 3.3 (2021-06-15 21:47:01) running on Duet Maestro 1.0
Board ID: 08DJM-957AU-PL3TJ-6JTDG-3SW6Q-T8AUT
Used output buffers: 1 of 24 (11 max)
=== RTOS ===
Static ram: 23556
Dynamic ram: 73396 of which 12 recycled
Never used RAM 18532, free system stack 220 words
Tasks: NETWORK(ready,22.4%,270) HEAT(delaying,0.0%,353) Move(notifyWait,0.1%,407) TMC(notifyWait,1.3%,117) MAIN(running,73.3%,471) IDLE(ready,2.9%,30), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:00:05 ago, cause: software
Last software reset at 2022-02-18 12:25, reason: User, GCodes spinning, available RAM 18456, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Step timer max interval 938
MCU temperature: min 27.0, current 27.6, max 27.7
Supply voltage: min 12.1, current 12.2, max 12.2, under voltage events: 0, 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
Driver 0: position 0, standstill, read errors 0, write errors 1, ifcnt 19, reads 937, writes 8, timeouts 0, DMA errors 0
Driver 1: position 0, standstill, read errors 0, write errors 1, ifcnt 19, reads 937, writes 8, timeouts 0, DMA errors 0
Driver 2: position 0, standstill, read errors 0, write errors 1, ifcnt 19, reads 937, writes 8, timeouts 0, DMA errors 0
Driver 3: position 0, standstill, read errors 0, write errors 1, ifcnt 19, reads 937, writes 8, timeouts 0, DMA errors 0
Driver 4: position 0, standstill, read errors 0, write errors 1, ifcnt 13, reads 939, writes 6, timeouts 0, DMA errors 0
Driver 5: position 0, assumed not present
Driver 6: position 0, assumed not present
Date/time: 2022-02-18 12:25:47
Slowest loop: 17.39ms; fastest: 0.17ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 15.0MBytes/sec
SD card longest read time 0.5ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1, chamberHeaters = -1 -1
=== GCodes ===
Segments left: 0
Movement lock held by 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 51.79ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8
Interface state active, link 100Mbps full duplex

M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Warning: Macro file config-override.g not found

wiring is as described in the documentation that i linked. probe does not deploy or retract in response to any commands no, seemingly on its own

[jcwild]

@phaedrux and here is the full config file: config.g

[Phaedrux]

Is this a genuine BLTouch or a clone or a Creality version?

Do you have another probe to test or another printer to test the probe on?

I've never heard of a BLtouch testing non-stop at power on before.

[jcwild]

@phaedrux it is a clone, and i do have another that has been working on my other machine, ill swap it out and test if its the probe itself

[jcwild]

@jcwild just swapped in the known working sensor and it just stays deployed and if i push my finger up against the probe it just deploys and retracts constantly. Duet web control reports 0/1000 under z-probe flashing on off in the same rythm that the probe would deploy/retract. Do I need to put some sort of modifier on the "zprobe.mod" pin?

[jcwild]

@Phaedrux

[Phaedrux]

What do you have in deployprobe.g and retractprobe.g?

Can you try M950 S0 C"^zprobe.mod" ?

Can you also show a photo of your wiring at the board showing the z probe connection?

[jcwild]

@phaedrux
changing that line in the config didnt seem do anything, the probe is still deployed and bounces off a finger if applied. also the wiring is just 5 random colored wires in the connector because of how ive extented them but Ill go quintuple check it

deployprobe.g is :
; deployprobe.g
; called to deploy a physical Z probe
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Thu Feb 10 2022 16:59:05 GMT-0500 (Eastern Standard Time)
M280 P0 S10 ; deploy BLTouch

retractprobe.g is:
; retractprobe.g
; called to retract a physical Z probe
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Thu Feb 10 2022 16:59:06 GMT-0500 (Eastern Standard Time)
M280 P0 S90 ; retract BLTouch

[Phaedrux]

And with the known working sensor are you able to send M401 and M402 to work the pin?

Can you send the bltouch servo command to clear error state and retract the pin?

M280 P0 S160 I think it is.

[jcwild]

@phaedrux said in bltouch on duet maestro:

M280 P0 S160

none of the commands do anything at all. why did i even waste my money on this stupid board.

[Phaedrux]

Is the probe mounted upright when you're doing the testing or laying on it's side?

@jcwild said in bltouch on duet maestro:

none of the commands do anything at all.

It seems like the servo control wire isn't making contact or isn't connected to the right in. Can you check the wire connected to the zprobe.mod pin for continuity?

[Phaedrux]

One possibility is an inconsistent 5v connection causing the bltouch to constantly reboot.

Have you tried connecting the bltouch directly to the board without any extension wires?

[jcwild]

@phaedrux YES i think you were right about the 5v being inconsistent i made a shorter extension harness and plugged that in and it just deploys and retracts twice on startup! m280 p0 s10 and m280 p0 s90 still dont control it, so i went back and took off the "^" in front of zprobe.mod and no change.

[Phaedrux]

@jcwild said in bltouch on duet maestro:

m280 p0 s10 and m280 p0 s90 still dont control it

And you're sure you're plugged into the zprobe.mod pin?

How does the plug on the back of the bltouch look?

[jcwild]

@phaedrux
green and black are crimped together on the gnd pin

[JonDaniel]

@jcwild I'm not sure how much additional help I can be, but i am also running a genuine BL Touch on a Maestro board. I just went and checked my connections against yours, and your wiring is correct. Also, my bltouch wiring is ~ 24" long, with 1 JST connector in the middle, so i wouldn't think that the wiring itself was too terribly sensitive. I retract this, and after reading what @Phaedrux has been saying, i agree there must be ghosts in the wiring Do you have the means to re-crimp a new one?

Edit:
I've pasted the probe section of my config. Hopefully this will give you a starting point for troubleshooting.

 
 
; Z-Probe
M558 P9 C"^zprobe.in" H5 F1500 T8000            ; set Z probe type to bltouch and the dive height + speeds
M950 S0 C"zprobe.mod"                           ; create servo pin 0 for BLTouch
G31 P500 X0 Y-43 Z2.35                          ; set Z probe trigger value, offset and trigger height
M557 X0:117 Y-6:81 S23.4                        ; define mesh grid 
 

Quality of Life Improvement:
I would suggest setting up a macro for resetting the BLTouch in the event it ever enters an error state. (eg. if you crash the probe on deployment.) Especially when troubleshooting, it'll come in super useful!

M280 P0 S160 I1

[Gixxerfast]

@phaedrux @jcwild A question/observation. Do you know how these clones work in regard to logic levels? I see that the Z_PROBE_MOD pin is, as far as I can see, a 3.3V logic level pin and I haven't been able to find any information that the 3DTouch is working with 3.3V

Isn't a logic high often relative to the input voltage, (therefore sometimes Neopixels work with 3.3V if the input voltage is low enough)?

I see that the same output is buffered to 5V to the servo pin. Is that an option to see if it could work (more reliably.)

[jcwild]

@jondaniel yes i agree something is wrong with my original wiring. i just recrimped a new cable and thats what that picture is of. Thanks for the config.