BL touch file help
-
can anyone look over my files im having issue getting my BL Touch to work, all else works just not z probe. any help is appreciated.
; Configuration file for Duet WiFi (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.3.0 on Wed Aug 18 2021 14:59:32 GMT-0700 (Pacific Daylight Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"My Printer" ; 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 S1 ; physical drive 0 goes forwards 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 Z4000.00 E67.91 ; set steps per mm M566 X4500.00 Y4500.00 Z60.00 E600.00 ; set maximum instantaneous speed changes (mm/min) M203 X30000.00 Y30000.00 Z600.00 E3000.00 ; set maximum speeds (mm/min) M201 X800.00 Y800.00 Z20.00 E2500.00 ; set accelerations (mm/s^2) M906 X1300 Y1300 Z1300 E1000 I30 ; set motor currents (mA) and motor idle factor in per cent M84 S10 ; 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 Y2 S1 P"!ystop" ; configure active-high endstop for high 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" H10 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds G31 P500 X0 Y0 Z5 ; 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 S150 ; set temperature limit for heater 0 to 150C M308 S1 P"e0temp" Y"thermistor" T100000 B4000 ; 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 are not defined ; Miscellaneous M501 ; load saved parameters from non-volatile memory undefined ```here is my deploy probe aswell
; deployprobe.g
; called to deploy a physical Z probe
;
; generated by RepRapFirmware Configuration Tool v3.3.0 on Wed Aug 18 2021 14:59:32 GMT-0700 (Pacific Daylight Time)
M280 P0 S10 ; deploy BLTouchundefined
-
home all and my home z and retract in that order
; homeall.g ; called to home all axes ; ; generated by RepRapFirmware Configuration Tool v3.3.0 on Wed Aug 18 2021 14:59:32 GMT-0700 (Pacific Daylight Time) G91 ; relative positioning G1 H2 Z10 F6000 ; lift Z relative to current position G1 H1 X-305 Y305 F1800 ; move quickly to X and Y axis endstops and stop there (first pass) G1 H2 X5 Y-5 F6000 ; go back a few mm G1 H1 X-305 Y305 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 Z10 F100 ; lift Z relative to current position ;G90 ; absolute positioning
undefined
; called to home the Z axis ; ; generated by RepRapFirmware Configuration Tool v3.3.0 on Wed Aug 18 2021 14:59:32 GMT-0700 (Pacific Daylight Time) G91 ; relative positioning G1 H2 Z10 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 Z10 F100 ; lift Z relative to current position ;G90 ; absolute positioning
undefined
; called to retract a physical Z probe ; ; generated by RepRapFirmware Configuration Tool v3.3.0 on Wed Aug 18 2021 14:59:32 GMT-0700 (Pacific Daylight Time) M280 P0 S90 ; retract BLTouch undefined
-
@kevinlallshouse @kevinlallshouse Try removing the ! from this line.
M558 P9 C"^!zprobe.in" H10 F120 T6000
Try these commands also
If the probe needs to be deployed before use (e.g. BLTouch), test the deploy and retract functions, by sending M401 to deploy the probe and M402 to retract it.
When the printer is powered does it do the init sequence? out / in, out /in?
HTH
Paul. -
What exactly doesn't work? Or what does work?
What happens when it's powered on? Does the pin drop and retract?
Does the BLtouch light up?
Does M401/M402 work?
Does sending G30 cause the pin to drop?
Does touching the pin stop the Z axis? -
so i got it to all work and ran my bed calabrations but when i run a print z axis homes then raises and drops back down in to my bed on the second drop. i have a 30mm x off set for bl touch and it works on the first home do you think i need to put in another offset for the second drop? any ideas were to start?
-
Post your current config file, homing files, and bed.g file.
-
thank you I got that issue figured out and I'm on to another issue unfortunately but thank you for your response.
-
@kevinlallshouse said in BL touch file help:
thank you I got that issue figured out and I'm on to another issue unfortunately but thank you for your response.
What was the problem and how did you solve it?
-
ended up it was in my cura gcode there was some marlin in there and once deleted its been running fine now thank you again.