Gantry leveling offset
-
Hi! I was wondering, if it is possible to have an idividual z offset for both z motors. After I level my gantry with g32 the right side is always higher than the left side and I get a bad first layer.
Board: Duet Maestro running RepRapFirmware for Duet 2 Maestro 2.05.1 (2020-02-09b1) -
G32 is supposed to result in a level bed.
Something is clearly not working as it should.
Post your config.g and bed.g files using the </> tag.
Frederick
-
Sure!
; Custom settings are not defined ; Configuration file for Duet Maestro (firmware version 2.03) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v2.1.8 on Wed Apr 22 2020 01:05:56 GMT+0200 (Mitteleuropäische Sommerzeit) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"My Printer" ; set printer name ; Network M552 P192.168.1.69 S1 ; enable network and set IP address M553 P255.255.255.0 ; set netmask M554 P192.168.1.254 ; set gateway M586 P0 S1 ; enable HTTP M586 P1 S1 ; enable FTP M586 P2 S0 ; disable Telnet M552 S1 P192.168.178.99 ; Drives M569 P0 S1 D3 v0 ; physical drive 0 goes backwards X M569 P1 S0 D3 v0 ; physical drive 1 goes backwards Y M569 P2 S0 D3 v0 ; physical drive 2 goes forwards Z M569 P3 S1 D3 v0 ; physical drive 2 goes forwards Z M569 P4 S1 D2 ; physical drive 3 goes forwards E M584 X0 Y1 Z2:3 E4 ; set drive mapping M350 X32 Y32 Z64 E32 I1 ; configure microstepping with interpolation M92 X160.00 Y160.00 Z1600.00 E695 ; set steps per mm M566 X420.00 Y420.00 Z24.00 E250.00 ; set maximum instantaneous speed changes (mm/min) M203 X6000.00 Y6000.00 Z720.00 E7200.00 ; set maximum speeds (mm/min) M201 X2000.00 Y2000.00 Z1000.00 E1250.00 ; set accelerations (mm/s^2) M906 X700 Y700 Z600 E850 I30 ; set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout M204 P1000 T2000 ; Set printing and travel accelerations M572 D0 S0.03 ; Pa M564 H0 ; movement without homing M669 K0 ; Axis Limits M208 X-5 Y-5 Z-5 S1 ; set axis minima M208 X234 Y226 Z260 S0 ; set axis maxima ; Endstops M574 X1 Y1 S1 ; set active high endstops M574 Z1 S2 ; set endstops controlled by probe ; Z-Probe M558 P9 H3 F120 T3000 A3 B1 ; set Z probe type to bltouch and the dive height + speeds G31 P500 X49 Y23 Z1.87 ; set Z probe trigger value, offset and trigger height M557 X49:233 Y23:220 S15 ; define mesh grid ; Heaters M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit M305 P0 T98801 B4185 R2200 ; set thermistor + ADC parameters for heater 0 M143 H0 S120 ; set temperature limit for heater 0 to 120C M305 P1 T100000 B4725 C7.060000e-8 R2200 ; set thermistor + ADC parameters for heater 1 M143 H1 S300 ; set temperature limit for heater 1 to 280C ; Fans M307 H2 A-1 C-1 D-1 ; Disables H2 M106 P0 A22 H-1 S0 F150 X185 ; Part cooling fan M106 P2 A2 H1 T45 ; Hotend fan ; 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 M208 X-23 Y-14 S1 ; Custom settings are not defined ; Miscellaneous M501 ; load saved parameters from non-volatile memory M911 S23 R23.7 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss G29 S1 M671 X-15.0:230.0 Y110.0:110.0
; bed.g ; called to perform automatic bed compensation via G32 ; ; generated by RepRapFirmware Configuration Tool v2 on Tue Jan 29 2019 19:02:30 GMT+0100 (Mitteleuropäische Normalzeit) G28 G30 P0 X60 Y100 Z-99999 ; probe near an adjusting screw G30 P1 x180 Y100 Z-99999 S2; probe near an adjusting screw
-
Hi,
Don't see anything wrong in those two files.
Please post your homeALL.g file.
Thanks.
Frederick
-
This post is deleted! -
@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
-
post the output of 3 consecutive G32
also after a G32, you need to home z again.
-
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
-
@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 -
@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.000For 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
-
@fcwilt Could my issues come from my rather old firmware version?
If so, is there a config converter from RRF2 to RRF3? -
@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
-
@fcwilt I'veloaded a v2 json for a v3 config. It won't populate any of the pin stuff.
-
@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