Ender 3 RRF v1.1 setting up BLtouch

[re_tour]

@gixxerfast The servo pin is PB0 and the sensor is PC5.
The bltouch glows red indeed, and when I turn the printer on it pushes the sensor pin out and retracts it two times.

[Gixxerfast]

@re_tour

In your config.g, do you have something like this:

M950 S0 C"io2.out"                                       ;<-- Servo pin
M558 P9 C"io2.in" H5 F300:120 A3 T6000 ;<-- Sensor pin  
G31 P500 X37.1 Y9.25 Z4.370                      ; set Z probe trigger value, offset and trigger height

I don't know what the pins are called in RRF when you have a non duet board, are they just PB0 and PC5 or are they "translated" ?

[Gixxerfast]

@re_tour

OK, should be like this as far as I can see:

M950 S0 C"servo0"                                       ;<-- Servo pin
M558 P9 C"^probe" H5 F300:120 A3 T6000 ;<-- Sensor pin  
G31 P500 X37.1 Y9.25 Z4.370                      ; set Z probe trigger value, offset and trigger height
 

Then you should have a file in the sys folder called deployprobe.g:

M280 P0 S10 ; deploy BLTouch

And another file called retractprobe.g:

M280 P0 S90 ; retract BLTouch

I don't know if you've seen this but TeamGloomy got a lot of documentation for the STM and LPC based boards:
https://teamgloomy.github.io/skr_rrf_e3_general.html

[re_tour]

@gixxerfast
I have this in my config.g:

; Z-Probe
M950 S0 C"servo0"                              ; create servo pin 0 for BLTouch
M558 P9 C"^probe" H5 F120 T6000                ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X117.5 Y117.5 Z2.5                            ; set Z probe trigger value, offset and trigger height
M557 X15:215 Y15:195 S20                       ; define mesh grid

deployprobe.g looks like this:

; deployprobe.g
; called to deploy a physical Z probe
;
; generated by RepRapFirmware Configuration Tool v3.3.1-LPC-STM32+2 on Tue Dec 28 2021 01:07:55 GMT+0100
M280 P0 S10 ; deploy BLTouch

and retractprobe.g like this:

; retractprobe.g
; called to retract a physical Z probe
;
; generated by RepRapFirmware Configuration Tool v3.3.1-LPC-STM32+2 on Tue Dec 28 2021 01:07:55 GMT+0100
M280 P0 S90 ; retract BLTouch

[Gixxerfast]

@re_tour So if you do a manual G30 it deploys and probes?

Or if you just try this: M280 P0 S10 manually

?

[re_tour]

@gixxerfast well it ejected the probe and now its flashing red.

[Gixxerfast]

@re_tour When you did what?

[re_tour]

@gixxerfast sent M280 P0 S10 in the console to the printer

[Gixxerfast]

@re_tour OK, should not flash. Did it have room (in z) to fully deploy without hitting the bed?

[re_tour]

@gixxerfast Not really

[re_tour]

@gixxerfast okay so I raised the head and tried again, now the probe is extended and the red led is not on at all.
Sent out the M280 P0 S90 command, now the pin went back to its place and the red LED glows constantly.

[Gixxerfast]

@re_tour Good, then that works.

EDIT: Not needed as you did it above ^ Retract the probe with

M280 P0 S90

Then when the probe is above the bed, do a

G30

[re_tour]

@gixxerfast After doing a G30 the probe extended, the head started going down on the Z axis very slowly until the probe pin reached the bed, when that happened it retracted the probe and the whole rig went up a bit faster.

[Gixxerfast]

@re_tour Great. Then all works as it should and what you now want is to configure your homez.g and your homeall.g

Look here for examples of that:
https://teamgloomy.github.io/skr_rrf_e3_bltouch.html

Just make sure to modify the x and y coordinates so that you probe wherever you want. (middle of the bed)

I am now assuming you have working homex.g and homey.g in your /sys directory

[re_tour]

@gixxerfast Yeah, about that, I already did that.
Here's my homez.g:

; ################# Home Z Preparation ################

G91 															; Relative mode
G1 H2 Z5 F6000													; Lower the bed
G90																; Back to absolute positioning
G1 X117.5 Y117.5 F10000 		 								; Move to the center of the bed. Adjust to the co-ordinates required for the centre of your bed

; ################# Home Z Preparation ################

M558 F250 				 										; Set the probing speed
G30					 											; Probe a single point
M558 F30 				 										; Set a slower probing speed
G30					 											; Probe a single point

and my homeall.g:

; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v3.3.1-LPC-STM32+2 on Tue Dec 28 2021 01:07:55 GMT+0100 (közép-európai téli idő)
G91                     ; relative positioning
G1 H2 Z5 F6000          ; lift Z relative to current position
G1 H1 X-240 Y-240 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-240 Y-240 F360  ; move slowly to X and Y axis endstops once more (second pass)
G1 H1 Z-265 F360        ; move Z down stopping at the endstop
G90																; Back to absolute positioning
G1 X117.5 Y117.5 F10000 		 								; Move to the center of the bed. Adjust to the co-ordinates required for the centre of your 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

Problem is I don't know what I did wrong. It could be the order or something.

[Gixxerfast]

@re_tour
Your homeall.g is missing stuff but this is how I do it and it's not perfect and my Ender so modified now I don't really know what it is any longer but it should work fairly OK:

homeall.g:

; homeall.g
; called to home all axes
;
M98 P"/sys/homex.g"
M98 P"/sys/homey.g"
M98 P"/sys/homez.g"

homex.g:

; homex.g
; called to home the X axis
;
G91

if !move.axes[1].homed
	; raise Z a bit
	G1 H2 Z5 

G1 H2 Z5 F6000    ; lift Z relative to current position
G1 H1 X-240 F3000 ; move quickly to X axis endstop and stop there (first pass)
G1 H2 X5 F6000    ; go back a few mm
G1 H1 X-240 F240  ; move slowly to X axis endstop once more (second pass)
G90               ; absolute positioning

homey.g:

; homey.g
; called to home the Y axis
;
G91

if !move.axes[0].homed
	; raise Z a bit
	G1 H2 Z5 
	
G1 H1 Y-240 F3000 ; move quickly to Y axis endstop and stop there (first pass)
G1 H2 Y5 F6000    ; go back a few mm
G1 H1 Y-240 F240  ; move slowly to Y axis endstop once more (second pass)
G90               ; absolute positioning

and finally homez.g

; homez.g
; called to home the Z axis

; do nothing if XY is not homed yet
if !move.axes[0].homed || !move.axes[1].homed
    echo "XY are not homed yet. Aborting"
    abort
;end if

G91
G1 H2 Z5 F6000

G90
G1 X130 Y160 F6000

G30 K0 Z-99999						    ; Probe the Z pin at the back

G1 Z10 F9000

Also you cab define two speed probeing with this in your config.g:

M558 P9 C"io2.in" H5 F300:120 A3 T6000 ; See the F300:120 first speed 300 second 120

When all this is done do a, in order, to test:

g28 x
g28 y
g28 z
g28

[re_tour]

@gixxerfast Okay, after doing everything, during the testing all axises find their homes and the Z homing does 3 probing and then stays in place, in the middle. bltouch red led is on constantly.

[Gixxerfast]

@re_tour Good, then all works as expected.

What you want to do now is calibrate your Z offset.

I usually do the paper friction thing and just home z and then lower it slowly by G1 Z-0.2 (DON'T FORGET THE G91 before that) (or less) until it's right. Then I adjust the offset in the G31 in config.g

[re_tour]

@gixxerfast said in Ender 3 RRF v1.1 setting up BLtouch:

by G1 Z-0.2 (DON'T FORGET THE G91 before that)

So like

G1 Z-0.2
*axis moves*
G91
G1 Z-0.2
*axis moves*
G91
G1 Z-0.2

this?

[Gixxerfast]

@re_tour G91 set's RRF in realtive coordinates mode so you only need to do that once AFAIK. G90 sets it back to absolute coordinates mode.

So it's like:

G91
G1 z-5
G1 z-.2
G1 Z-.1
... until you're happy
then look at the Z offset in DWC (or some gcode command I don't remember right now) and remember it
G90 

Take it down until the nozzle touches the paper and you can feel the friction some when moving the paper. You may need to correct this when printing later but then you can baby step it up and down until it looks fine.

I think you do almost the same in Marlin and Klipper. Maybe there's some automated method you can use in RRF but I don't know about it.