Gantry leveling offset

Rushmere3D

This post is deleted!

maroonds

@fcwilt I usually have the g32 command in my start gcode. Here's the homeall.g file:

; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v2.1.8 on Wed Apr 22 2020 01:05:56 GMT+0200 (Mitteleuropäische Sommerzeit)
G91                     ; relative positioning
G1 H2 Z5 F6000          ; lift Z relative to current position
G1 H1 X-245 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-245 Y-240 F360  ; move slowly to X and Y axis endstops once more (second pass)
G90                     ; absolute positioning
G1 X0 Y0 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

Veti

post the output of 3 consecutive G32

also after a G32, you need to home z again.

fcwilt

@maroonds

The only thing I would change is the XY position when using G30.

I always use the same exact XY position whenever I do a G30 and I always use the center of the bed.

And as mentioned you need to do a G30 after doing one or more G32s.

Since it may take more than one G32 to get things level I do it this way:

; *** bed.g ***

; --- set positions of ball studs for auto-leveling (S is max allowed adjustment)

M671 X-180:0:180 Y-65:130:-65 S3

; --- run first pass ---

M98 P"bed_3.g"

; --- if deviation is too large run additional passes ---

while move.calibration.initial.deviation >= 0.02
  ; check if pass limit reached

  if iterations = 5
    abort "Bed Leveling Aborted - Pass Limit Reached"

  ; run next pass

  M98 P"bed_3.g"

; *** bed_3.g - called by bed.g ***

; --- probe near ball studs ---

G30 P0 X-145 Y-65 Z-99999    ; probe near ball stud #1
G30 P1 X0    Y100 Z-99999    ; probe near ball stud #2
G30 P2 X145  Y-65 Z-99999 S3 ; probe near ball stud #3

; --- set Z=0 datum ---

M98 P"center_probe.g"        ; position to center of bed for probing
G30                          ; do single probe which sets Z to trigger height of Z probe

maroonds

@Veti
7.3.2021, 13:20:13 g32
Leadscrew adjustments made: -0.035 0.005, points used 2, deviation before 0.016 after 0.000
7.3.2021, 13:19:38 g32
Leadscrew adjustments made: -0.028 0.006, points used 2, deviation before 0.012 after 0.000
7.3.2021, 13:19:05 g32
Leadscrew adjustments made: -0.041 0.043, points used 2, deviation before 0.021 after 0.000

fcwilt

@maroonds said in Gantry leveling offset:

@Veti
7.3.2021, 13:20:13 g32
Leadscrew adjustments made: -0.035 0.005, points used 2, deviation before 0.016 after 0.000
7.3.2021, 13:19:38 g32
Leadscrew adjustments made: -0.028 0.006, points used 2, deviation before 0.012 after 0.000
7.3.2021, 13:19:05 g32
Leadscrew adjustments made: -0.041 0.043, points used 2, deviation before 0.021 after 0.000

For reasons lost in the mists of time as you can see if my bed_3.g file I include a single G30 after the leveling pass.

I know you need to do a G30 but I don't know if you need to do it after each pass or after all passes.

Frederick

maroonds

@fcwilt Could my issues come from my rather old firmware version?
If so, is there a config converter from RRF2 to RRF3?

fcwilt

@maroonds said in Gantry leveling offset:

@fcwilt Could my issues come from my rather old firmware version?
If so, is there a config converter from RRF2 to RRF3?

It's possible but it has been quite a while since I used v2 so I don't have any specific recollection.

I don't know of a convertor. I converted by editing my existing files. It wasn't as much work as I thought it would be.

I've never used the RRF configuration tool so I don't know if you can load a v2 .json file into the v3 tool.

Frederick

Stephen6309

@fcwilt I'veloaded a v2 json for a v3 config. It won't populate any of the pin stuff.

fcwilt

@Stephen6309 said in Gantry leveling offset:

@fcwilt I'veloaded a v2 json for a v3 config. It won't populate any of the pin stuff.

Not too surprising since v2 didn't use pin assignments.

Thanks for the feedback.

Frederick