BLtouch probe pin does not deploy

imonsei

I cannot get the "M280 P0 S10" and "M280 P0 S160" commands working. (nor M401)

I'm amost done assembling my Ratrig V-core 3, and I'm stumbling over this last hurdle, before I can begin stumbling over printer calibration
The board is a Duet 3 MB6HC.
I use the ethernet connection standalone webinterface to interface with the board.

The probe does go through the self test on power on.

Below is the wiring of my BLtouch (original)

The probe is connected to my io2 port on the board.
This is the BLTouch relevant part of my config.g

;; BLTouch
M950 S0 C"io2.out"                     ; Create a servo pin on io2
M558 P9 C"io2.in" H5 F240 T10800 A5    ; set Z probe type to unmodulated and the dive height + speeds
;M558 P9 C"io6.in" F150 H4 R0.2 T12000 A5 B0
G31 P25 X-28.00 Y-13.00 Z0.90          ; set Z probe trigger value, offset and trigger height, more Z means closer to the bed

I do have a deployprobe.g and a retractprobe.g with the relevant M280 commands. (but those shouldn't be relevant for me sending a M280 command manually)

Other than that I have not changed any config.

Steps I have tried:
Two different sets of wires, and both times ensured the connections were good with a multimeter.
Connecting a different BLTouch, which didn't get the command either.
Connecting the wires to io6, and changing the config.g from io2 to io6.
Disconnecting the motor for the filament.

Is there something you can suggest for me to try?

PCR

@imonsei can you run M98 P"config.g" and post the poutput

imonsei

@pcr said in BLtouch probe pin does not deploy:

M98 P"config.g"

sure thing

M98 P"config.g"
Error: Height map file 0:/sys/heightmap.csv not found
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Warning: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 470C
Warning: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 302C

PCR

@imonsei running latest 3.3 stable?

imonsei

@pcr yes sir. its the one it shipped with. "Duet Web Control 3.3.0" is what it says in Settings->General

PCR

@imonsei please send M122

imonsei

@pcr said in BLtouch probe pin does not deploy:

M122

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.3 (2021-06-15 21:45:47) running on Duet 3 MB6HC v1.01 or later (standalone mode)
Board ID: 08DJM-956BA-NA3TJ-6J9DJ-3SD6R-1996T
Used output buffers: 1 of 40 (11 max)
=== RTOS ===
Static ram: 150904
Dynamic ram: 91940 of which 112 recycled
Never used RAM 111236, free system stack 208 words
Tasks: NETWORK(ready,30.1%,212) ETHERNET(notifyWait,0.1%,117) HEAT(notifyWait,0.0%,331) Move(notifyWait,0.0%,302) CanReceiv(notifyWait,0.0%,944) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,343) TMC(notifyWait,7.4%,93) MAIN(running,61.6%,924) IDLE(ready,0.8%,29), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:00:13 ago, cause: power up
Last software reset at 2021-11-19 12:36, reason: User, GCodes spinning, available RAM 111236, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Step timer max interval 126
MCU temperature: min 17.1, current 24.8, max 24.8
Supply voltage: min 24.0, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.1, current 12.1, max 12.2, under voltage events: 0
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Driver 0: position 0, standstill, reads 6291, writes 15 timeouts 0, SG min/max 0/0
Driver 1: position 0, standstill, reads 6291, writes 15 timeouts 0, SG min/max 0/0
Driver 2: position 0, standstill, reads 6291, writes 15 timeouts 0, SG min/max 0/0
Driver 3: position 0, standstill, reads 6292, writes 15 timeouts 0, SG min/max 0/0
Driver 4: position 0, standstill, reads 6292, writes 15 timeouts 0, SG min/max 0/0
Driver 5: position 0, standstill, reads 6292, writes 15 timeouts 0, SG min/max 0/0
Date/time: 2021-11-19 13:44:44
Slowest loop: 9.18ms; fastest: 0.05ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 3.2ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, 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 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
Heater 1 is on, I-accum = 0.0
=== 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
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.
=== CAN ===
Messages queued 117, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 49 (min 49), ts 66/0/0
Tx timeouts 0,0,65,0,0,50 last cancelled message type 30 dest 127

=== Network ===
Slowest loop: 16.31ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions
HTTP sessions: 1 of 8
- Ethernet -
State: active
Error counts: 0 0 0 0 0
Socket states: 5 2 2 2 2 0 0 0

rjenkinsgb

Can you add a photo of the BLTouch itself with the cable attached to it?

There are at least three different sets of wire colours supplied with genuine BLTouch probes / kits.

I have one on mine connected to a 6HC and it works fine, it's just working out which wiring version you need.

The probe end connections are in a fixed sequence, it's just the supplied cables that vary from unit to unit.

imonsei

I'm noticing that it doesn't say anything about a z-probe or an endstop in any of the info commands.
Should I be worrying about this, or is that normal?

Phaedrux

@imonsei said in BLtouch probe pin does not deploy:

The probe is connected to my io2 port on the board.

For Duet 3 MB6HC, use IO_4, IO_5 or IO_7.

https://duet3d.dozuki.com/Wiki/Connecting_a_Z_probe#Section_Duet_Num_3

io2 is not a PWM capable port.

imonsei

@phaedrux IT'S ALIIIIIIIIIIIIVE!!!!! Thank you so much.
I'll write a note to the ratrig people.
Their documentation and config files specify that we should use the io2 port.

I am so excited now. Weeeeeeee ^____^

droftarts

@imonsei it’s io1, io2 or io3 when using a Duet 3 Mini 5+, which might be more usual in a RatRig.

Ian

imonsei

@droftarts they have a section in their assembly instructions specifically for the 6HC that said to use io2.
I figure they just copied over the mini instructions without actually testing it beforehand.

BLtouch probe pin does not deploy

Robert J.