How to create a mesh for Bltouch

IvanG

; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool on Sun Apr 08 2018 20:13:54 GMT+0200 (Hora de verano romance)
G91 ; relative positioning
G1 Z5 F6000 S2 ; lift Z relative to current position
G1 S1 X-295 Y265 F1800 ; move quickly to X or Y endstop and stop there (first pass)
G1 S1 X-295 ; home X axis
G1 S1 Y255 ; home Y axis
G1 X5 Y-5 F6000 ; go back a few mm
G1 S1 X-295 F360 ; move slowly to X axis endstop once more (second pass)
G1 S1 Y255 ; then move slowly to Y axis endstop
G90 ; absolute positioning
G1 X150 Y-130 F6000 ; go to first bed probe point and home Z
G30 ; home Z by probing the bed
;G1 Z5 F100 S2 ; uncomment this line to lift the nozzle after homing;G90

; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool on Sun Apr 08 2018 20:13:54 GMT+0200 (Hora de verano romance)
G91 ; relative positioning
G1 Z5 F6000 S2 ; lift Z relative to current position
G90 ; absolute positioning
G1 X150 Y130 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 S2 ; lift Z relative to current position
;G90 ; absolute positioning

; bed.g
; called to perform automatic bed compensation via G32
;
; generated by RepRapFirmware Configuration Tool on Sun Apr 08 2018 20:13:54 GMT+0200 (Hora de verano romance)
M561 ; clear any bed transform
; Probe the bed at 5 points
G30 P0 X15 Y15 H0 Z-99999
G30 P1 X15 Y245 H0 Z-99999
G30 P2 X285 Y245 H0 Z-99999
G30 P3 X285 Y15 H0 Z-99999
G30 P4 X150 Y150 H0 Z-99999 S

; retractprobe.g

M280 P7 S90 I1

; deployprobe.g

M280 P7 S10 I1

dc42

@ivang said in How to create a mesh for Bltouch:

when I do home all does not work for me, the axes x and y if they work correctly but the z axis does not make me home, if I take home the individual axes if it works correctly

Homing: your homeall.g files has this:

G1 X150 Y-130 F6000 ; go to first bed probe point and home Z

but your homez.g file has this:

G1 X150 Y130 F6000 ; go to first probe point

Do you see the difference?

Mesh: if you send M557 without parameters, does it report the values you specified in the M557 command in config.g?

IvanG

Perfect now if you make me home all without problems, thank you very much.

Now how can I create a mesh for example of 40 points for my bltouch?

Phaedrux

To do mesh grid compensation you will need to specify the grid area in config.g with M557 and then tell it to load your saved heightmap on powerup with M375.

For example:

M557 X15:285 Y15:245 S30                           	; Define mesh grid
M375							; Load heightmap.csv

To create a heightmap, run G29. Ideally after you've tried to level your bed mechanically as good as possible.

IvanG

@phaedrux said in How to create a mesh for Bltouch:

To do mesh grid compensation you will need to specify the grid area in config.g with M557 and then tell it to load your saved heightmap on powerup with M375.

For example:
M557 X15:285 Y15:245 S30                           	; Define mesh grid
M375							; Load heightmap.csv
To create a heightmap, run G29. Ideally after you've tried to level your bed mechanically as good as possible.

Thank you for your answer, I just did what it says but when I send the G29 command the printer moves about 15mm and then stops and does nothing, the duetwifi plate stays in busy state and I can only hit the stop button emergency, why does this happen to me?

dc42

Send M557 without parameters and review the response, to check that the mesh parameters you set in config.g have been accepted.
After you run G29 and it stops, check the GCode Console page of Duet Web Control for error messages.

IvanG

@dc42 said in How to create a mesh for Bltouch:

Send M557 without parameters and review the response, to check that the mesh parameters you set in config.g have been accepted.

After you run G29 and it stops, check the GCode Console page of Duet Web Control for error messages.

When I send the M557 command, the following message appears:

M557
Grid: X15.0:205.0, Y15.0:245.0, radius -1.0, X spacing 30.0, Y spacing 30.0, 56 points

After sending G29 there is no error message or anything, the printer moves a little and stops, the status of the printer is always busy and nothing else I can give emergency stop or turn off the duertwifi and turn it on current.

dc42

Please change your microstepping from x256 to x16 with interpolation enabled in the M350 command in config.g and try again.

IvanG

Hello I have changed it to x16 interpolated and now if it works correctly, although the noise from the engines is annoying, is there any way to work it to x256 interpolated?

Phaedrux

@dc42 said in How to create a mesh for Bltouch:

M350

Does your M350 command have I1?

IvanG

@phaedrux said in How to create a mesh for Bltouch:

@dc42 said in How to create a mesh for Bltouch:

M350

Does your M350 command have I1?

But I do not understand why with the configuration of X16 interpolated steps if it works correctly but when I change it to interpolated X256 the G29 command does not work

dc42

Depending on your steps/mm and how fast you are trying to move the print head, the rate at which step pulses need to be generated and the Z probe checked can exceed the capabilities of the processor. When this happens the movement should just slow down, however in the past few days it has become evident that under some conditions it causes the movement system to lock up. This is on my list to investigate and fix.

IvanG

So for the moment the only solution is to run X16 the steps of the engine? I buy a duetwifi for the X256 and for the little noise that engines make but if I have to run to X16 it makes the same noise as my mks gen

T3P3Tony

@ivang from a noise perspective running x16 interpolated to 256 and running x256 is functionally the same. The only difference is that the driver is generating the intermediate steps. I could not tell a noise difference between the two during testing.

I think maybe you do not have I1 in you M350 command ?

Also note that interpolation only works on x16 (not for example x32 and x64)

IvanG

@t3p3tony said in How to create a mesh for Bltouch:

@ivang from a noise perspective running x16 interpolated to 256 and running x256 is functionally the same. The only difference is that the driver is generating the intermediate steps. I could not tell a noise difference between the two during testing.

I think maybe you do not have I1 in you M350 command ?

Also note that interpolation only works on x16 (not for example x32 and x64)

He is right I just put the end I1 and the noise is almost nonexistent, thank you very much.

T3P3Tony

@ivang glad you got it sorted!