BLTouch not Triggering
-
Can you provide the results of sending M122 and M98 P"config.g" in the console?
Your config looks correct and your wiring sounds correct, but let's make sure you're on RRF3 to match your config.
Failing to trigger usually means there is a bad connection on the white wire. Either in the wiring itself or perhaps internal to the BLTouch.
-
What version BLTouch do you have? It is typically printed on the PCB visible from the outside of the BLTouch.
-
@Mac3D-FPV said in BLTouch not Triggering:
What version BLTouch do you have? It is typically printed on the PCB visible from the outside of the BLTouch.
Version 3.1 - I believe I got it from Matterhackers.
-
Here's the M122 @Phaedrux :
=== Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2.2 running on Duet Ethernet 1.02 or later Board ID: 0JD0M-9P6M2-NWNS4-7J1F8-3SN6N-KU23K Used output buffers: 1 of 24 (18 max) === RTOS === Static ram: 23460 Dynamic ram: 72736 of which 40 recycled Never used RAM 15844, free system stack 193 words Tasks: NETWORK(ready,160) HEAT(blocked,308) MAIN(running,453) IDLE(ready,20) Owned mutexes: HTTP(MAIN) === Platform === Last reset 03:32:54 ago, cause: software Last software reset at 2021-03-16 12:04, reason: User, GCodes spinning, available RAM 15844, slot 1 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 Aux0 errors 0,0,0 MCU temperature: min 16.3, current 18.6, max 19.0 Supply voltage: min 12.1, current 12.1, max 12.2, under voltage events: 0, over voltage events: 0, power good: yes Driver 0: position 0, standstill, SG min/max not available Driver 1: position 0, standstill, SG min/max not available Driver 2: position 0, standstill, SG min/max not available Driver 3: position 0, standstill, SG min/max not available Driver 4: position 0, standstill, SG min/max not available Driver 5: position 0 Driver 6: position 0 Driver 7: position 0 Driver 8: position 0 Driver 9: position 0 Driver 10: position 0 Driver 11: position 0 Date/time: 2021-03-16 15:37:48 Cache data hit count 4294967295 Slowest loop: 14.55ms; fastest: 0.22ms 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: 20.0MBytes/sec SD card longest read time 3.9ms, 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 -1 -1, chamberHeaters = -1 -1 -1 -1 === GCodes === Segments left: 0 Movement lock held by null HTTP is ready with "M122 and M98 P"config.g"" 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: 10.93ms; fastest: 0.02ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions HTTP sessions: 2 of 8 Interface state active, link 100Mbps full duplex HTTP is enabled on port 80 FTP is disabled TELNET is disabled Error: Heater 7 not found Warning: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 365C 3/16/2021, 3:37:49 PM M122 and M98 P"config.g" === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2.2 running on Duet Ethernet 1.02 or later Board ID: 0JD0M-9P6M2-NWNS4-7J1F8-3SN6N-KU23K Used output buffers: 1 of 24 (18 max) === RTOS === Static ram: 23460 Dynamic ram: 72736 of which 40 recycled Never used RAM 15844, free system stack 193 words Tasks: NETWORK(ready,160) HEAT(blocked,308) MAIN(running,453) IDLE(ready,20) Owned mutexes: HTTP(MAIN) === Platform === Last reset 03:32:54 ago, cause: software Last software reset at 2021-03-16 12:04, reason: User, GCodes spinning, available RAM 15844, slot 1 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 Aux0 errors 0,0,0 MCU temperature: min 16.3, current 18.6, max 19.0 Supply voltage: min 12.1, current 12.1, max 12.2, under voltage events: 0, over voltage events: 0, power good: yes Driver 0: position 0, standstill, SG min/max not available Driver 1: position 0, standstill, SG min/max not available Driver 2: position 0, standstill, SG min/max not available Driver 3: position 0, standstill, SG min/max not available Driver 4: position 0, standstill, SG min/max not available Driver 5: position 0 Driver 6: position 0 Driver 7: position 0 Driver 8: position 0 Driver 9: position 0 Driver 10: position 0 Driver 11: position 0 Date/time: 2021-03-16 15:37:48 Cache data hit count 4294967295 Slowest loop: 14.55ms; fastest: 0.22ms 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: 20.0MBytes/sec SD card longest read time 3.9ms, 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 -1 -1, chamberHeaters = -1 -1 -1 -1 === GCodes === Segments left: 0 Movement lock held by null HTTP is ready with "M122 and M98 P"config.g"" 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: 10.93ms; fastest: 0.02ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions HTTP sessions: 2 of 8 Interface state active, link 100Mbps full duplex HTTP is enabled on port 80 FTP is disabled TELNET is disabled Error: Heater 7 not found Warning: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 365C -
@brewchester said in BLTouch not Triggering:
Error: Heater 7 not found
Is the deploy and retract commands working? M401 and M402?
-
@Phaedrux said in BLTouch not Triggering:
@brewchester said in BLTouch not Triggering:
Error: Heater 7 not found
Is the deploy and retract commands working? M401 and M402?
Yes they are.
-
Can you post a photo of the wiring at the board? Just the other day someone had connected the white wire to the PanelDue port rather than the Z probe port... never hurts to have a second pair of eyes.
-
@Phaedrux said in BLTouch not Triggering:
Can you post a photo of the wiring at the board? Just the other day someone had connected the white wire to the PanelDue port rather than the Z probe port... never hurts to have a second pair of eyes.
-
@brewchester Just checking to best sure. BLTouch version 3.1, at least for me, worked out of the box (after adjusting the mounting height). Earlier versions required cutting a trace on the PCB to operate on 3.3V logic; this was not required for the v3.1.
Here are my BLTouch settings (I am on firmware version 3.1.1), if it helps:
; Z-Probe
M950 S0 C"exp.heater3" ; create servo pin 0 for BLTouch
M558 P9 C"^zprobe.in" H5 F90 T10800 A10 S0.005 ; set Z probe type to bltouch and the dive height + speeds probe up to 5 times until 2 consecutive readings are within 0.005, if none average of 5
G31 P500 X67.5 Y-11.5 Z2.946 ; set Z probe trigger value, offset and trigger height
M557 X70:280 Y15:255 S30 ; define mesh gridThe mounting specs (for the pin height relative to the tip of the nozzle) for the BLTouch, if I recall correctly, changed with the v3.1, compared to earlier 2.X versions. You might want to double check the antclabs manuals (available at www.antclabs.com) to verify your retracted pin height is within that specified for the v3.1 ). I have mine at 3.3mm above the nozzle tip - in the middle of the acceptable range.
-
@Mac3D-FPV said in BLTouch not Triggering:
@brewchester Just checking to best sure. BLTouch version 3.1, at least for me, worked out of the box (after adjusting the mounting height). Earlier versions required cutting a trace on the PCB to operate on 3.3V logic; this was not required for the v3.1.
Here are my BLTouch settings (I am on firmware version 3.1.1), if it helps:
; Z-Probe
M950 S0 C"exp.heater3" ; create servo pin 0 for BLTouch
M558 P9 C"^zprobe.in" H5 F90 T10800 A10 S0.005 ; set Z probe type to bltouch and the dive height + speeds probe up to 5 times until 2 consecutive readings are within 0.005, if none average of 5
G31 P500 X67.5 Y-11.5 Z2.946 ; set Z probe trigger value, offset and trigger height
M557 X70:280 Y15:255 S30 ; define mesh gridThe mounting specs (for the pin height relative to the tip of the nozzle) for the BLTouch, if I recall correctly, changed with the v3.1, compared to earlier 2.X versions. You might want to double check the antclabs manuals (available at www.antclabs.com) to verify your retracted pin height is within that specified for the v3.1 ). I have mine at 3.3mm above the nozzle tip - in the middle of the acceptable range.
Thanks... I haven't let it drive to the bed yet and only have been using my hand to try and trigger the touch. The height shouldn't matter at this point correct?
-
You are correct, the height would not matter at that point.
-
@brewchester said in BLTouch not Triggering:
@Phaedrux said in BLTouch not Triggering:
@brewchester said in BLTouch not Triggering:
Error: Heater 7 not found
Is the deploy and retract commands working? M401 and M402?
Yes they are.
Error: Heater 7 not foundThis error message is a bit confusing then.Could you change from that heater 7 pin to heater 3/pin 8 on the expansion header? Then change the reference to exp.heater7 to exp.heater3 and send M98 P"config.g" again to see if it's still complaining about heater 7.
-
if deploy and retract are working then the servo part of the bltouch is working.
the trigger signal is the problem. -
@Phaedrux said in BLTouch not Triggering:
@brewchester said in BLTouch not Triggering:
@Phaedrux said in BLTouch not Triggering:
@brewchester said in BLTouch not Triggering:
Error: Heater 7 not found
Is the deploy and retract commands working? M401 and M402?
Yes they are.
Error: Heater 7 not foundThis error message is a bit confusing then.Could you change from that heater 7 pin to heater 3/pin 8 on the expansion header? Then change the reference to exp.heater7 to exp.heater3 and send M98 P"config.g" again to see if it's still complaining about heater 7.
I've done this a few times and it has the same affect. I've tried 3, 5, and 7 and it still won't trigger.
-
if you have revision 1.04 of the duet you can try chaning the trigger logic
using
M280 P0 S140
and
M280 P0 S150 -
@Veti said in BLTouch not Triggering:
M280 P0 S150
Where would I put those commands? I ran them and they don't do anything. Well, it comes up green, but that's it.
-
The commands are for the BLTouch so you just send them once.
There is this page from antclabs that you could try.
-
@Veti said in BLTouch not Triggering:
if deploy and retract are working then the servo part of the bltouch is working.
the trigger signal is the problem.Yes, just wondering why it's complaining about heater 7. I don't think it's references in config.g other than in his M950 for the bltouch.
-
@Phaedrux said in BLTouch not Triggering:
@Veti said in BLTouch not Triggering:
if deploy and retract are working then the servo part of the bltouch is working.
the trigger signal is the problem.Yes, just wondering why it's complaining about heater 7. I don't think it's references in config.g other than in his M950 for the bltouch.
Is it because I added the line:
M307 H7 A-1 C-1 D-1 -
Ah ok. I guess that would have been added after you shared the config.g above.
