BLTouch Duet 2 Wifi didnt work
-
Hello, i connect my original BLTouch to my Duet 2 Wifi and changed it in the firmware. But it isnt work. The Pin of the BL didnt get out. But it lights red. But he dont takes his pin out. Do you see the Problem?
It is connected like here:
www.duet3d.dozuki.com/wiki/connecting_a_z_probe
In the Config.g i write:
M307 H3 A-1 C-1 D-1
M558 P9 H5 F100 T2000
G31 X19 Y0 Z0 P25In deployprobe.g i write:
M280 P3 S10 I1
In retractprobe.g i write:
M280 P3 S90 I1
Anything other i didnt change.
Thank you for help
-
What firmware version?
Can you please post your full config.g and your homing files?Also the results of sending M122 and M98 P"config.g"
-
@robiiinx
Do you have line likeM950 S0 C"exp.heater3" M558 P9 C"^zprobe.in" H5 F120 T6000
and try use
M280 P0 S10 M280 P0 S90
look on this docs https://docs.duet3d.com/en/User_manual/Connecting_hardware/Z_probe_connecting
-
Here is my whole config
; Configuration file for Duet WiFi (firmware version 3.3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Mon Apr 04 2022 20:14:28 GMT+0200 (Mitteleuropäische Sommerzeit); General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"My Printer" ; set printer name
M669 K1 ; select CoreXY mode; Network
M552 S1 ; enable network
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 S0 ; physical drive 2 goes backwards
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 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 X800.00 Y800.00 Z800.00 E500.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 X300 Y300 Z300 S0 ; set axis maxima; Endstops
M574 X1 S1 P"xstop" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin xstop
M574 Y1 S1 P"ystop" ; configure switch-type (e.g. microswitch) 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.heater3" ; 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 X0 Y0 Z2.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 B4138 ; 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 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"e0temp" Y"thermistor" T100000 B4138 ; 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 S280 ; set temperature limit for heater 1 to 280C; 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 0CM307 H3 A-1 C-1 D-1
M558 P9 H5 F100 T2000
G31 X19 Y0 Z0 P25; Custom settings are not definedHere is the homeall.g
; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Mon Apr 04 2022 20:14:28 GMT+0200 (Mitteleuropäische Sommerzeit)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 X-305 Y-305 F1800 ; move quickly to X or Y endstop and stop there (first pass)
G1 H1 X-305 ; home X axis
G1 H1 Y-305 ; home Y axis
G1 X5 Y5 F6000 ; go back a few mm
G1 H1 X-305 F360 ; move slowly to X axis endstop once more (second pass)
G1 H1 Y-305 ; then move slowly to Y axis endstop
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 positioning -
I think the issue is that you're using M307 (RRF 2) where you should be using M950 (RRF3)
My working config:
M950 S0 C"exp.heater3" ; create servo pin 0 for BLTouch M558 P9 C"^zprobe.in" H1 F120 T9000 ; set Z probe type to bltouch and the dive height + speeds G31 P500 X45 Y0 Z2.399 ; set Z probe trigger value, offset and trigger height
I also have a macro defined for finding the nozzle to probe offset:
G29 S2 ;Disable mesh compensation G1 X75 Y75 Z10 ; change this to a convenient position on your bed G30 ;Extend probe and touch G92 Z15 ;Allow extra room M291 S3 Z1 P"Move nozzle to touch bed" ; dialogue to jog nozzle to bed. G92 Z0 ;set new zero G1 Z10 ;move away G30 S-1 ;see output for offset
You'll need to feed the measurement it prints to console to the Z parameter of G31. Further reading here:
https://betrue3d.dk/bltouch-on-duet-wifi-configuratio-and-usage/#testandcalibrateHopefully that gets you going
-
@phaedrux said in BLTouch Duet 2 Wifi didnt work:
Also the results of sending M122 and M98 P"config.g"
Please provide this so we can see what firmware version you are using so we know which commands you need to use. Right now you have both commands for RRF2 and RRF3. Most of your config appears to be for RRF3 so I think you should remove these additions.
M307 H3 A-1 C-1 D-1 M558 P9 H5 F100 T2000 G31 X19 Y0 Z0 P25; Custom settings are not defined
But without knowing for certain what firmware you're using I don't know.