BLTouch not Triggering
-
Hi all,
I've looked into every article. Compared my configs and after 3 days I'm at a loss and need help. I have a genuine bltouch configured based on the betrue3d post but it won't trigger. I'll start by saying that this was working fine with my old Creality board, so I don't believe it's the BLT.
I have the following wiring connected:
White = Z_probe_in
Black = Ground
Red = Pin 1 on expansion
Blue = Pin 2 on expansion
Yellow = Pin 31 on expansionAll the commands work for the touch, pin down, up, self-test, etc. but it won't trigger no matter what I've done. Here are my configs:
config.g
; Configuration file for Duet WiFi (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.2.3 on Tue Mar 16 2021 10:43:48 GMT-0400 (Eastern Daylight Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"PrintBoss" ; set printer name ; Network M551 P"*****" ; set password M552 P0.0.0.0 S1 ; enable network and acquire dynamic address via DHCP M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ; Drives M569 P0 S0 ; physical drive 0 goes backwards M569 P1 S0 ; physical drive 1 goes backwards M569 P2 S1 ; physical drive 2 goes forwards M569 P3 S1 ; physical drive 3 goes forwards M584 X0 Y1 Z2 E3 ; set drive mapping M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X80.00 Y80.00 Z400.00 E409.00 ; set steps per mm M566 X900.00 Y900.00 Z60.00 E120.00 ; set maximum instantaneous speed changes (mm/min) M203 X6000.00 Y6000.00 Z180.00 E1200.00 ; set maximum speeds (mm/min) M201 X500.00 Y500.00 Z20.00 E250.00 ; set accelerations (mm/s^2) M906 X800 Y800 Z800 E1200 I30 ; set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ; Axis Limits M208 X0 Y0 Z0 S1 ; set axis minima M208 X300 Y300 Z400 S0 ; set axis maxima ; Endstops M574 X1 S1 P"xstop" ; configure active-high endstop for low end on X via pin xstop M574 Y1 S1 P"ystop" ; configure active-high endstop for low end on Y via pin ystop M574 Z1 S2 ; configure Z-probe endstop for low end on Z ; Z-Probe M950 S0 C"exp.heater7" ; create servo pin 0 for BLTouch M558 P9 C"^zprobe.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds G31 P500 X-44 Y0 Z1.5 ; set Z probe trigger value, offset and trigger height M557 X15:215 Y15:195 S20 ; define mesh grid ; Heaters M308 S0 P"bedtemp" Y"thermistor" T100000 B3950 ; configure sensor 0 as thermistor on pin bedtemp M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0 M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit M140 H0 ; map heated bed to heater 0 M143 H0 S120 ; set temperature limit for heater 0 to 120C M308 S1 P"e0temp" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 1 as thermistor on pin e0temp M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1 M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit M143 H1 S300 ; set temperature limit for heater 1 to 300C ; Fans M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on ; Tools M563 P0 D0 H1 F0 ; define tool 0 G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C ; Custom settings M918 P2 E2 ; Support for directly-connected LCD ; Miscellaneous M501 ; load saved parameters from non-volatile memory M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss bed.g
; bed.g ; called to perform automatic bed compensation via G32 ; ; generated by RepRapFirmware Configuration Tool v3.2.3 on Tue Mar 16 2021 10:43:48 GMT-0400 (Eastern Daylight Time) M561 ; clear any bed transform G29 ; probe the bed and enable compensation homeall.g
; homeall.g ; called to home all axes ; ; generated by RepRapFirmware Configuration Tool v3.2.3 on Tue Mar 16 2021 10:43:48 GMT-0400 (Eastern Daylight Time) G91 ; relative positioning G1 H2 Z5 F6000 ; lift Z relative to current position G1 H1 X-305 Y-305 F1800 ; move quickly to X and Y axis endstops and stop there (first pass) G1 H2 X5 Y5 F6000 ; go back a few mm G1 H1 X-305 Y-305 F360 ; move slowly to X and Y axis endstops once more (second pass) G90 ; absolute positioning G1 X150 Y150 F6000 ; go to first bed probe point and home Z G30 ; home Z by probing the bed ; Uncomment the following lines to lift Z after probing ;G91 ; relative positioning ;G1 Z5 F100 ; lift Z relative to current position ;G90 ; absolute positioning homez.g
; homez.g ; called to home the Z axis ; ; generated by RepRapFirmware Configuration Tool v3.2.3 on Tue Mar 16 2021 10:43:48 GMT-0400 (Eastern Daylight Time) G91 ; relative positioning G1 H2 Z5 F6000 ; lift Z relative to current position G90 ; absolute positioning G1 X150 Y150 F6000 ; go to first probe point G30 ; home Z by probing the bed ; Uncomment the following lines to lift Z after probing ;G91 ; relative positioning ;G1 Z5 F100 ; lift Z relative to current position ;G90 ; absolute positioning deployprobe.g
; deployprobe.g ; called to deploy a physical Z probe ; ; generated by RepRapFirmware Configuration Tool v3.2.3 on Tue Mar 16 2021 10:43:48 GMT-0400 (Eastern Daylight Time) M280 P0 S10 ; deploy BLTouch retractprobe.g
; retractprobe.g ; called to retract a physical Z probe ; ; generated by RepRapFirmware Configuration Tool v3.2.3 on Tue Mar 16 2021 10:43:48 GMT-0400 (Eastern Daylight Time) M280 P0 S90 ; retract BLTouch Thank you in advance,
Bob -
check the extension cable. it is known to cause problems because of bad contact.
-
@brewchester said in BLTouch not Triggering:
All the commands work for the touch, pin down, up, self-test, etc. but it won't trigger no matter what I've done. Here are my configs:
and what do you mean by that? you will not see a bltouch trigger in the web interface, because the trigger is just a fraction of a second.
did you test it with a g30 and triggering the pin by hand? -
@Veti Sorry, yes... I meant that I tried a G30 and get it to trigger by hand. As far as the cabling, I checked the wiring and crimps. Did a continuity check using Ohms on each of the pins and everything seems to check out.
-
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.