bad autolevel
-
Post your homeall/homez, bed.g and your slicer start gcode.
-
Hi, here is my gcode in cura and configuration.
-
; Ender 3 Custom Start G-code G92 E0 ; Reset Extruder G28 ; Home all axes G29 S1 G1 Z2.0 F3000 ; Move Z Axis up little to prevent scratching of Heat Bed G1 X0.1 Y20 Z0.5 F5000.0 ; Move to start position G1 X0.1 Y200.0 Z0.5 F1500.0 E15 ; Draw the first line G1 X0.4 Y200.0 Z0.5 F5000.0 ; Move to side a little G1 X0.4 Y20 Z0.5 F1500.0 E30 ; Draw the second line G92 E0 ; Reset Extruder G1 Z2.0 F3000 ; Move Z Axis up little to prevent scratching of Heat Bed G1 X5 Y20 Z0.5 F5000.0 ; Move over to prevent blob squish
; bed.g ; called to perform automatic bed compensation via G32 ; ; generated by RepRapFirmware Configuration Tool v3.1.10+4-LPC on Tue Jan 19 2021 17:25:01 GMT+0800 (中国标准时间) M561 ; clear any bed transform G29 ; probe the bed and enable compensation
; ################# Home Z Preparation ################ G91 ; Relative mode G1 H2 Z5 F5000 ; Lower the bed G90 ; Back to absolute positioning G1 X130 Y130 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 F60 ; Set a slower probing speed G30 ; Probe a single point
-
@pelikán-jiří said in bad autolevel:
one side of the bed is too high and the other too low, because the motor balances the bed incorrectly
What does your heightmap look like?
You're not really doing any auto leveling, just compensation. Have you manually leveled your bed first?
-
@phaedrux
This is what my bed looks like. -
@pelikán-jiří I hoped that the printer would adjust the movements from the Z engine according to the map so that it would always be the same distance from the bed.
-
Yes it should. Are the Z motors moving at all during a layer?
If you send M122 during a print, post the results here. -
@phaedrux
Yes, they move, from the first when they make a line set in gcode, then at the first the nozzle is too high and at the second (way back) the nozzle is already correct. And I'm attaching diagnostics.=== Diagnostics ===
RepRapFirmware for STM32F4 based Boards version 3.3beta1_5 running on STM32F4
Used output buffers: 3 of 40 (21 max)
=== RTOS ===
Static ram: 30760
Dynamic ram: 68932 of which 76 recycled
Never used RAM 11408, free system stack 107 words
Tasks: NETWORK(notifyWait,200) HEAT(delaying,323) MAIN(running,424) IDLE(ready,20)
Owned mutexes: WiFi(NETWORK) HTTP(MAIN)
=== Platform ===
Last reset 00:44:38 ago, cause: [software]
Last software reset at 2021-06-09 22:03, reason: User, GCodes spinning, available RAM 11408, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00438000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU temperature: min 47.2, current 47.5, max 47.5
Supply voltage: min 24.0, current 24.0, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: position 8680, 2209 ok, reads 9480, writes 0, SG min/max 0/48
Driver 1: position 8680, 2209 standstill, reads 9480, writes 0, SG min/max 0/60
Driver 2: position 43, 2209 standstill, reads 9479, writes 0, SG min/max 0/16
Driver 3: position 0, 2209 ok, reads 9479, writes 0, SG min/max 0/16
Driver 4: position 0
Driver 5: position 0
Driver 6: position 0
Driver 7: position 0
Driver 8: position 0
Driver 9: position 0
Driver 10: position 0
Date/time: 2021-06-09 22:47:53
Slowest loop: 48.72ms; fastest: 0.08ms
=== Storage ===
Free file entries: 9
SD card 0 detected
SD card longest read time 1.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 0ms, bed compensation in use: mesh, comp offset 0.000
=== DDARing ===
Scheduled moves 318, completed moves 314, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state 3
=== Heat ===
Bed heaters = 0, chamberHeaters = -1
Heater 0 is on, I-accum = 0.0
Heater 1 is on, I-accum = 0.6
=== GCodes ===
Segments left: 1
Movement lock held by null
HTTP is ready with "M122 " in state(s) 0
File is doing "G1 X126.9 Y108.1 E0.50023" in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty. -
@pelikán-jiří said in bad autolevel:
bed compensation in use: mesh,
So it is enabled.
Where is the 0,0 origin of your printer?
Does -x move left, +x move right?
Does -y move front, +y move back?Based on your G31 your probe offset shows the BLtouch is 44mm to the right of the nozzle directly in line on Y?
Have you measured the Z offset? It's unusual that it's exactly 2mm.
-
@phaedrux
I already see one mistake, I entered 44 offset, but it should be -44. I already understand why the defined mesh grid didn't make sense. And I'm still trying to catch Z offset. So far I have it set to 1.90 and somehow it works a bit. Thank you very much, I will try to correct the mistake. Hopefully the printer will do what I wants.