BLtouch not deploying
-
Hey everyone,
So I installed a BLtouch on my printer with a Duet3 mini5+.
I basically copied all the Zprobe settings from my other, similarly equipped, printer, where it works exactly as it should.
The BLtouch seems to respond to M280 commands, and can also home the Z axis, however, it will not deploy automatically. I wrote the M280 commands in the homeZ and HomeAll files to be able to home the printer.
But I get in trouble when trying to run mesh compensation, as the BLtouch will again not deploy automatically.
It is not a new BLtouch, but it worked fine last time I used it on the old printer.Any idea what the problem could be here? Or maybe there's a workaround for the mesh compensation?
Thanks in advance!
-
@Queevix can you post your config.g, homeall.g, homez.g, deployprobe.g and retractprobe.g
You shouldn't be using M280 in your homing files
https://docs.duet3d.com/en/User_manual/Connecting_hardware/Z_probe_connecting#wiring-the-bltouchOwns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is
-
config
General preferences
M575 P1 S1 B57600 ; enable support for PanelDue
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"BigBitch" ; set printer name; Network
M552 S1 ; enable network
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 S0 ; physical drive 0.1 goes forwards
M569 P0.2 S1 ; physical drive 0.2 goes forwards
M569 P0.3 S1 ; physical drive 0.3 goes forwards
M584 X0.0 Y0.1 Z0.2 E0.3 ; 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 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 X470 Y465 Z450 S0 ; set axis maxima; Endstops
M574 X1 S1 P"io5.in" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin io5.in
M574 Y1 S1 P"io6.in" ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin io6.in
M574 Z1 S2 ; configure Z-probe endstop for low end on Z; Z-Probe
M950 S0 C"io2.out" ; Duet 3 Mini 5+
M558 P9 C"io2.in" H10 F120 T6000 A3 ; set Z probe type to modulated and the dive height + speeds
G31 P1000 X-39 Y2 Z1.5 S21 H2 T0.02 ; Nozzle offset - Powder Coated Sheet with temperature compensation (0.02mm/°C)
M574 Z1 S2 ; set Z probe trigger value, offset and trigger height
M557 X40:400 Y2:440 P20:20 ; define mesh grid
M376 H5 ; Fade height 5mm; 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 B0 R0.213 C666.6 D8.13 S1.00 V24.1 ;
M140 H0 ; map heated bed to heater 0
M143 H0 S80 ; set temperature limit for heater 0 to 80C
M308 S1 P"temp1" Y"pt1000" B4725 C7.060000e-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 R1.350 K0.244:0.000 D5.89 E1.35 S1.00 B0 ; 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"out3" Q500 ; create fan 0 on pin out3 and set its frequency
M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"out4" Q500 ; create fan 1 on pin out4 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 0CM563 P1 D0 H1 F0 ; define tool 0
G10 P1 X0 Y0 Z0 ; set tool 0 axis offsets
G10 P1 R0 S0 ; set initial tool 0 active and standby temperatures to 0CM563 P2 D0 H1 F0 ; define tool 0
G10 P2 X0 Y0 Z0 ; set tool 0 axis offsets
G10 P2 R0 S0 ; set initial tool 0 active and standby temperatures to 0CM563 P3 D0 H1 F0 ; define tool 0
G10 P3 X0 Y0 Z0 ; set tool 0 axis offsets
G10 P3 R0 S0 ; set initial tool 0 active and standby temperatures to 0CM563 P4 D0 H1 F0 ; define tool 0
G10 P4 X0 Y0 Z0 ; set tool 0 axis offsets
G10 P4 R0 S0 ; set initial tool 0 active and standby temperatures to 0CM563 P5 D0 H1 F0 ; define tool 0
G10 P5 X0 Y0 Z0 ; set tool 0 axis offsets
G10 P5 R0 S0 ; set initial tool 0 active and standby temperatures to 0CM563 P6 D0 H1 F0 ; define tool 0
G10 P6 X0 Y0 Z0 ; set tool 0 axis offsets
G10 P6 R0 S0 ; set initial tool 0 active and standby temperatures to 0CM563 P7 D0 H1 F0 ; define tool 0
G10 P7 X0 Y0 Z0 ; set tool 0 axis offsets
G10 P7 R0 S0 ; set initial tool 0 active and standby temperatures to 0C
; Custom settings are not defined -
homeall
G91 ; relative positioning
G1 H2 Z10 F6000 ; lift Z relative to current position
G1 H1 X-470 Y-465 F3000 ; 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-470 Y-465 F360 ; move slowly to X and Y axis endstops once more (second pass); HOME Z
G1 H2 Z10 F2600 ; Raise the Z axis 2mm to ensure it is above the Z probe trigger height.
G90 ; Set absolute positioning mode.
G1 X225 Y225 F6000 ; Go to the center of the bed for probe point.M558 F1000 R0.2 A1 ; Set the Z-probe to fast for the first pass.
M280 P0 S10
G30 ; Perform Z probing.
M280 P0 S90
G1 H0 Z10 F1000 ; Lift the Z axis to the 5mm position.M558 F200 R0.2 A1 H10 S-1 ; Set the Z-probe to slow for the second pass, take 5 probes and yield the average.
M280 P0 S10
G30 ; Perform Z probing.
M280 P0 S90
G1 H0 Z10 F400 ; Lift the Z axis to the 5mm position.
M402
M558 F200 A1 ; Set the Z-probe to normal speed. -
homez
; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Sat Jan 22 2022 15:24:14 GMT+0100 (Central European Standard Time)
G1 H2 Z10 F2600 ; Raise the Z axis 2mm to ensure it is above the Z probe trigger height.
G90 ; Set absolute positioning mode.
G1 X225 Y225 F6000 ; Go to the center of the bed for probe point.M558 F1000 R0.2 A1 ; Set the Z-probe to fast for the first pass.
M280 P0 S10
G30 ; Perform Z probing.
M280 P0 S90
G1 H0 Z10 F1000 ; Lift the Z axis to the 5mm position.M558 F200 R0.2 A1 H10 S-1 ; Set the Z-probe to slow for the second pass, take 5 probes and yield the average.
M280 P0 S10
G30 ; Perform Z probing.
M280 P0 S90
G1 H0 Z10 F400 ; Lift the Z axis to the 5mm position.
M402
M558 F200 A1 ; Set the Z-probe to normal speed. -
deploy probe
M280 P0 S10
Retract probe
M280 P0 S90
-
@jay_s_uk
Thanks for the reply,I realise I shouldn't use them, as I didn't need them on the other printer, but its how I got it to work here
-
@Queevix does your BLTouch deploy and retract using
M401andM402? -
@jay_s_uk
No, it doesn't. The commands appear green in the console, but no response whatsoever from the printer...
Didn't know about these commands by the way.
-
@Queevix if they don't work (and your deploy and retract are correct, which they look to be) then check your wiring
Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is
-
Can you send M122 and M98 P"config.g" in the gcode console in DWC and copy and paste the results here?
-
@Phaedrux
M122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.4.1 (2022-06-01 21:06:56) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: URV2B-M396U-D65J0-40KMY-1H03Z-72JMX
Used output buffers: 9 of 40 (24 max)
=== RTOS ===
Static ram: 103684
Dynamic ram: 111512 of which 0 recycled
Never used RAM 26516, free system stack 194 words
Tasks: NETWORK(ready,14.9%,255) HEAT(notifyWait,0.0%,358) Move(notifyWait,0.0%,363) CanReceiv(notifyWait,0.0%,942) CanSender(notifyWait,0.0%,372) CanClock(delaying,0.0%,339) TMC(notifyWait,0.7%,114) MAIN(running,83.6%,426) IDLE(ready,0.0%,29) AIN(delaying,0.8%,273), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:56:07 ago, cause: power up
Last software reset at 2022-11-08 14:54, reason: User, GCodes spinning, available RAM 26516, 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
Aux0 errors 0,0,0
MCU revision 3, ADC conversions started 3367648, completed 3367647, timed out 0, errs 0
Step timer max interval 1079
MCU temperature: min 18.8, current 31.4, max 31.9
Supply voltage: min 24.0, current 24.1, max 24.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
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 0, read errors 0, write errors 0, ifcnt 9, reads 46133, writes 9, timeouts 0, DMA errors 0, CC errors 0
Driver 1: standstill, SG min 0, read errors 0, write errors 0, ifcnt 9, reads 46133, writes 9, timeouts 0, DMA errors 0, CC errors 0
Driver 2: standstill, SG min 0, read errors 0, write errors 0, ifcnt 9, reads 46133, writes 9, timeouts 0, DMA errors 0, CC errors 0
Driver 3: standstill, SG min 0, read errors 0, write errors 0, ifcnt 9, reads 46132, writes 9, timeouts 0, DMA errors 0, CC errors 0
Driver 4: standstill, SG min 0, read errors 0, write errors 0, ifcnt 9, reads 46133, writes 9, timeouts 0, DMA errors 0, CC errors 0
Driver 5: not present
Driver 6: not present
Date/time: 2022-11-08 20:44:36
Cache data hit count 4294967295
Slowest loop: 6.08ms; fastest: 0.13ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 1.5ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 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 30304, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 18 (min 18), ts 16837/0/0
Tx timeouts 0,0,16836,0,0,13466 last cancelled message type 30 dest 127
=== Network ===
Slowest loop: 16.91ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8- WiFi -
Network state is active
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.26
WiFi MAC address d8:bf:c0:15:0b:d5
WiFi Vcc 3.38, reset reason Power up
WiFi flash size 2097152, free heap 25536
WiFi IP address 192.168.1.34
WiFi signal strength -65dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 4 0 0 0 0 0 0 0
- WiFi -
-
@Phaedrux
M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Warning: Temperature coefficients ignored due to invalid sensor number 2 -
@jay_s_uk
I've double- and triple checked the wiring, and am pretty confident the wires are intact and well connected to the board -
@Queevix said in BLtouch not deploying:
The BLtouch seems to respond to M280 commands, and can also home the Z axis, however, it will not deploy automatically.
Where are your deployprobe.g and retractprobe.g files located? They should be in the sys folder.
Can you upload those files here?
Since the M280 commands work but M401 and M402 don't that means something is wrong with those files.
-
@Phaedrux
Yes, something was wrong alright. They were only in my macros.
A profoundly stupid oversight of mine. it works as it should now. Thanks for pointing this out, I could have been looking for a really long time...
I'll get back in my lair now, a little more embarrassed then before.Thanks everyone!
Grtz,
Alexander -
undefined Phaedrux marked this topic as a question
-
undefined Phaedrux has marked this topic as solved
