BLTouch Won't deploy
-
Hi I am trying to get my BLTouch working. I have followed the online guides to ensure it has been correctly wired up. When I boot up my printer the BLTouch will deploy and retract and the red light will stay on. However when I try to deploy the probe manually to test it nothing happens (No errors on the interface the BLTouch doesn't move). When I try to home the Z it will move the Z axis but the probe won't deploy the probe. If anyone is able to help me fix this that would be greatly appreciated.
Please see my config file below:
; Configuration file for Duet 3 (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.3.0 on Sun Aug 15 2021 14:13:39 GMT+0100 (British Summer Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"My Printer" ; set printer name ; Network 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.0 S1 ; physical drive 0.0 goes forwards M569 P0.1 S1 ; physical drive 0.1 goes forwards M569 P0.2 S1 ; physical drive 0.2 goes forwards M569 P0.4 S1 ; physical drive 0.4 goes forwards M584 X0.0 Y0.1 Z0.2:0.3 E0.4 ; set drive mapping M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X160.00 Y160.00 Z5120.00 E420.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 E800 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 X500 Y500 Z750 S0 ; set axis maxima ; Endstops M574 X1 S1 P"io0.in" ; configure active-high endstop for low end on X via pin io0.in M574 Y1 S1 P"io1.in" ; configure active-high endstop for low end on Y via pin io1.in M574 Z1 S2 ; configure Z-probe endstop for low end on Z ; Z-Probe M950 S0 C"io4.out" ; create servo pin 0 for BLTouch M558 P9 C"^io4.in" H4 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds G31 P500 X37.5 Y10 Z2.5 ; set Z probe trigger value, offset and trigger height M557 X15:485 Y15:485 S20 ; define mesh grid ; Heaters ;M308 S0 P"temp0" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin temp0 ;M950 H0 C"out0" T0 ; create bed heater output on out0 and map it to sensor 0 ;M307 H0 B1 S1.00 ; enable 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"temp1" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 1 as thermistor on pin temp1 M950 H1 C"out1" T1 ; create nozzle heater output on out1 and map it to sensor 1 M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit M143 H1 S280 ; set temperature limit for heater 1 to 280C ; Fans M950 F0 C"out4" Q500 ; create fan 0 on pin out4 and set its frequency M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off M950 F1 C"out5" Q500 ; create fan 1 on pin out5 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 are not defined ; Miscellaneous M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss -
@eegroeg said in BLTouch Won't deploy:
M557 X15:485 Y15:485 S20
probably this is not the reason, but your M557 limit is too high, 441 points is the maximum allowed, and you define to probe 576 points.
To find the reason, publishing the homing files and deploy/retract files would be helpful.
The ^io4.in pullup is probably not needed, Duet 3 has it builtin for some inputs by default. https://duet3d.dozuki.com/Wiki/Connecting_endstop_switches#Section_Duet_3_endstop_inputs
-
@joergs5 Thanks for pointing that out I have amend that on my config file.
Please see the homing and deploy/retract files below:
Home all:
; homeall.g ; called to home all axes ; ; generated by RepRapFirmware Configuration Tool v3.3.0 on Sun Aug 15 2021 14:13:39 GMT+0100 (British Summer Time) G91 ; relative positioning ;G1 H2 Z5 F6000 ; lift Z relative to current position G1 H1 X-505 Y-505 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-505 Y-505 F360 ; move slowly to X and Y axis endstops once more (second pass) G90 ; absolute positioning G1 X15 Y15 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 positioningHome X:
; homex.g ; called to home the X axis ; ; generated by RepRapFirmware Configuration Tool v3.3.0 on Sun Aug 15 2021 14:13:39 GMT+0100 (British Summer Time) G91 ; relative positioning ;G1 H2 Z5 F6000 ; lift Z relative to current position G1 H1 X-505 F1800 ; move quickly to X axis endstop and stop there (first pass) G1 H2 X5 F6000 ; go back a few mm G1 H1 X-505 F360 ; move slowly to X axis endstop once more (second pass) ;G1 H2 Z-5 F6000 ; lower Z again G90 ; absolute positioningHome Y:
; homey.g ; called to home the Y axis ; ; generated by RepRapFirmware Configuration Tool v3.3.0 on Sun Aug 15 2021 14:13:39 GMT+0100 (British Summer Time) G91 ; relative positioning ;G1 H2 Z5 F6000 ; lift Z relative to current position G1 H1 Y-505 F1800 ; move quickly to Y axis endstop and stop there (first pass) G1 H2 Y5 F6000 ; go back a few mm G1 H1 Y-505 F360 ; move slowly to Y axis endstop once more (second pass) ;G1 H2 Z-5 F6000 ; lower Z again G90 ; absolute positioningHome Z:
; homez.g ; called to home the Z axis ; ; generated by RepRapFirmware Configuration Tool v3.3.0 on Sun Aug 15 2021 14:13:39 GMT+0100 (British Summer Time) G91 ; relative positioning ;G1 H2 Z5 F6000 ; lift Z relative to current position G90 ; absolute positioning G1 X15 Y15 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 positioningDeploy:
; deployprobe.g ; called to deploy a physical Z probe ; ; generated by RepRapFirmware Configuration Tool v3.3.0 on Sun Aug 15 2021 14:13:39 GMT+0100 (British Summer Time) M280 P0 S10 ; deploy BLTouchRetract:
; retractprobe.g ; called to retract a physical Z probe ; ; generated by RepRapFirmware Configuration Tool v3.3.0 on Sun Aug 15 2021 14:13:39 GMT+0100 (British Summer Time) M280 P0 S90 ; retract BLTouch -
What Board are you using? Are you sure your BLT is connected to IO4?
Try commenting out this line.M574 Z1 S2just put a ' ; ' at the beggining of that line, then try again, after the board has rebooted.
Does M401 or M402 do anything? M401 should extend the pin and M402 retract it.
HTH
Paul. -
@paulhew said in BLTouch Won't deploy:
M402
Sadly no change. The command doesn't give any errors and the BLTouch doesn't do anything.
-
@eegroeg My board is a Duet 3 MB 6HC. The BLTouch is connected to iO4.
-
@eegroeg there was similar problem here: https://www.reddit.com/r/ender3/comments/dr6lcd/bl_touch_not_deploying_probe_when_homing_help/
The solution was that the wiring was exchanged.
See the sentence starting with "Just got it working, ...."(Sometimes the cable coulours of the BLTouch are wrong... https://www.antclabs.com/bltouch-v3 at bottom shows rewiring)
-
@joergs5 Thanks for that, I have checked the wiring again and it all seems to match up. I have ordered a new longer Antclabs cable kit. I will give that a go and let you know if it makes a difference. If there's anything else you think I can try in the meantime please let me know.
-
@eegroeg I expect a wiring problem, because the BLtouch is able to deploy and retract at the beginning self test. You could of course try a different io port to exclude the possibility of a defective board, but this reason is unprobable imho.
Later when it works, the recommended https://forum.duet3d.com/topic/16993/strange-behavior-with-bl-touch/10 shielding is a good idea, I think. But unfortunately the product is not available here.
-
@joergs5 No change on IO7 so think you're right. Thanks for the advice on the shielding. I will update the thread with how the new cable works!
-
My 2cents is to go with IR probe that works 24/7.
I have had my battles with BLT original as well as clones = NO MOORE !!!!!
-
@joergs5 I got a replacement and M280 P3 S10 I1 causes it to deploy! M401 & M402 still don't do anything though is there any reason why this might be the case?
-
@eegroeg said in BLTouch Won't deploy:
@joergs5 I got a replacement and M280 P3 S10 I1 causes it to deploy! M401 & M402 still don't do anything though is there any reason why this might be the case?
If M280 P3 S10 I1 works that would mean your firmware version is still RRF2 but your config files are for RRF3.
Please send M122 and M98 P"config.g" and post the results.
To update the firmware to RRF3 If you still have access to DWC. Upload these 3 zip files, one at a time in the system tab. Don't extract them. Reboot after each. Use M115 to verify the firmware has been applied.
https://github.com/Duet3D/RepRapFirmware/releases/download/2.05.1/Duet2Firmware-2.05.1.zip
https://github.com/Duet3D/RepRapFirmware/releases/download/3.0/Duet2and3Firmware-3.0.zip
https://github.com/Duet3D/RepRapFirmware/releases/download/3.3/Duet2and3Firmware-3.3.zip
That will get your firmware and DWC up to date.Then I think you'll find that your config file will work a lot better.
-
@phaedrux said in BLTouch Won't deploy:
M98 P"config.g"
M122 === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.2.2 running on Duet 3 MB6HC v1.01 or later (standalone mode) Board ID: 08DJM-9P63L-DJMSS-6J9FD-3S86R-TBD39 Used output buffers: 1 of 40 (11 max) === RTOS === Static ram: 149788 Dynamic ram: 92412 of which 272 recycled Never used RAM 116360, free system stack 200 words Tasks: NETWORK(ready,183) ETHERNET(blocked,110) HEAT(blocked,300) CanReceiv(blocked,927) CanSender(blocked,371) CanClock(blocked,352) TMC(blocked,51) MAIN(running,1105) IDLE(ready,19) Owned mutexes: === Platform === Last reset 00:02:41 ago, cause: power up Last software reset at 2021-08-19 21:24, reason: User, GCodes spinning, available RAM 116360, 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 Aux0 errors 0,0,0 Aux1 errors 0,0,0 MCU temperature: min 21.2, current 32.9, max 33.0 Supply voltage: min 23.9, current 23.9, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 12.0, current 12.1, max 12.2, under voltage events: 0 Driver 0: position 0, standstill, reads 63447, writes 14 timeouts 0, SG min/max 0/0 Driver 1: position 0, standstill, reads 63447, writes 14 timeouts 0, SG min/max 0/0 Driver 2: position 0, standstill, reads 63448, writes 14 timeouts 0, SG min/max 0/0 Driver 3: position 0, standstill, reads 63448, writes 14 timeouts 0, SG min/max 0/0 Driver 4: position 0, standstill, reads 63448, writes 14 timeouts 0, SG min/max 0/0 Driver 5: position 0, standstill, reads 63451, writes 11 timeouts 0, SG min/max 0/0 Date/time: 2021-08-19 21:38:11 Slowest loop: 7.24ms; fastest: 0.05ms === Storage === Free file entries: 10 SD card 0 detected, interface speed: 25.0MBytes/sec SD card longest read time 2.1ms, 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 = -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -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 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. === Network === Slowest loop: 13.08ms; 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 === CAN === Messages queued 646, send timeouts 1453, received 0, lost 0, longest wait 0ms for reply type 0, free buffers 48M98 P"config.g" HTTP is enabled on port 80 FTP is disabled TELNET is disabled Error: Invalid use of P parameter Error: Missing Z probe pin name(s) Error: Invalid Z probe index -
@eegroeg said in BLTouch Won't deploy:
Error: Invalid use of P parameter Error: Missing Z probe pin name(s) Error: Invalid Z probe index
Interesting.
Very strange that M280 P3 S10 I1 does anything at all.
Can you please post your current config.g and deployprobe.g and retractprobe.g files?
Can you also verify that those files are in the system folder and not the macros folder or elsewhere?
Can you also verify which io port you are using? For Duet 3 MB6HC, use IO_4, IO_5 or IO_7.
@eegroeg said in BLTouch Won't deploy:
Duet 3 MB6HC version 3.2.2
I'd still update the firmware to 3.3 as well.
https://github.com/Duet3D/RepRapFirmware/releases/download/3.3/Duet2and3Firmware-3.3.zip
-
@phaedrux Ah well now it is back to no response again... I can confirm nothing is in macros I am using IO_7
My Printer Send code... Status Idle Mode: FFF Tool Position X 0.0 Y 0.0 Z 0.00 Extruder Drives Drive 0 0.0 Speeds Requested Speed 0 mm/s Top Speed 0 mm/s Sensors Vin 23.9 V V12 12.1 V MCU Temperature 33.6 °C Tools Extra Control Heaters Tool Heater Current Active Standby Tool 0 T0 - Load Filament Heater 1 off 21.8 °C 0 0 Temperature Chart System Directory 0:/sys/config.g ; Configuration file for Duet 3 (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.3.0 on Sun Aug 15 2021 14:13:39 GMT+0100 (British Summer Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"My Printer" ; set printer name ; Network 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.0 S1 ; physical drive 0.0 goes forwards M569 P0.1 S1 ; physical drive 0.1 goes forwards M569 P0.2 S1 ; physical drive 0.2 goes forwards M569 P0.4 S1 ; physical drive 0.4 goes forwards M584 X0.0 Y0.1 Z0.2:0.3 E0.4 ; set drive mapping M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X160.00 Y160.00 Z5120.00 E420.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 E800 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 X500 Y500 Z750 S0 ; set axis maxima ; Endstops M574 X1 S1 P"io0.in" ; configure active-high endstop for low end on X via pin io0.in M574 Y1 S1 P"io1.in" ; configure active-high endstop for low end on Y via pin io1.in M574 Z1 S2 P"io7.in" ; configure Z-probe endstop for low end on Z ; Z-Probe M950 S0 C"io7.out" ; create servo pin 0 for BLTouch M558 P9 H4 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds G31 P500 X37.5 Y10 Z2.5 ; set Z probe trigger value, offset and trigger height M557 X15:215 Y15:215 S20 ; define mesh grid ; Heaters ;M308 S0 P"temp0" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin temp0 ;M950 H0 C"out0" T0 ; create bed heater output on out0 and map it to sensor 0 ;M307 H0 B1 S1.00 ; enable 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"temp1" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 1 as thermistor on pin temp1 M950 H1 C"out1" T1 ; create nozzle heater output on out1 and map it to sensor 1 M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit M143 H1 S280 ; set temperature limit for heater 1 to 280C ; Fans M950 F0 C"out4" Q500 ; create fan 0 on pin out4 and set its frequency M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off M950 F1 C"out5" Q500 ; create fan 1 on pin out5 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 are not defined ; Miscellaneous M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss; deployprobe.g ; called to deploy a physical Z probe ; ; generated by RepRapFirmware Configuration Tool v3.3.0 on Sun Aug 15 2021 14:13:39 GMT+0100 (British Summer Time) M280 P0 S10 ; deploy BLTouch; retractprobe.g ; called to retract a physical Z probe ; ; generated by RepRapFirmware Configuration Tool v3.3.0 on Sun Aug 15 2021 14:13:39 GMT+0100 (British Summer Time) M280 P0 S90 ; retract BLTouch -
@Phaedrux I also am struggling to update it, when I upload the ZIP then run the M115 command after reboot I get...
M115 FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.2.2 ELECTRONICS: Duet 3 MB6HC v1.01 or later FIRMWARE_DATE: 2021-02-11George
-
@eegroeg I can confirm BLTouch is now Probing with M280 P0 S10/M280 P0 S90
-
@eegroeg said in BLTouch Won't deploy:
M558 P9 H4 F120 T6000
Your command isn't correct. You're missing the pin name. You need:
M558 P9 C"^io7.in" H4 F120 T6000Change that and send M98 P"config.g" again.
-
@eegroeg said in BLTouch Won't deploy:
@Phaedrux I also am struggling to update it, when I upload the ZIP then run the M115 command after reboot I get...
M115 FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.2.2 ELECTRONICS: Duet 3 MB6HC v1.01 or later FIRMWARE_DATE: 2021-02-11Where are you uploading it to? Should be the system tab.
