Mesh leveling
-
Hello,
I'm trying to figure out mesh leveling and "think" I've got it setup correctly, but it doesn't really appear to be working. I have a Duet Wifi with recent firmware update and also using an IR sensor. All previously working with the old 5 point leveling setup. The instructions on the Wiki were a bit confusing to me so this is what I've done…I created a macro with this:
M557 X20:120 Y10:220 S40
G29Because it takes a while to do, after having run the macro once, I have sent G29 S1 which, I believe, will used the last height map which is saved? in memory. I've sent G29 S1 and am running a print. It's a large flat part and I see no discernible movement in the z-axis as it prints. What am I doing wrong?
Thanks!
-
It's hard to see Z movement unless you have a gear wheel on the Z drive that you can see rotating, because the amount of movement is small. The M122 diagnostic report includes the type of bed compensation in use.
-
Thanks, David. Here's what M122 results in AFTER running the grid macro:
M122
=== Diagnostics ===
Used output buffers: 1 of 32 (11 max)
=== Platform ===
Memory usage:
Program static ram used: 20276
Dynamic ram used: 73876
Recycled dynamic ram: 56
Current stack ram used: 3304
Maximum stack ram used: 4288
Never used ram: 32576
Last reset 00:02:21 ago, cause: power up
Last software reset code 0x0003, HFSR 0x00000000, CFSR 0x00000000, ICSR 0x00400000, BFAR 0xe000ed38, SP 0xffffffff
Stack: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffff
Spinning module during software reset: GCodes, available RAM 28868 bytes (slot 3)
Error status: 0
Max PWM loop count 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 3.2ms
MCU temperature: min 35.7, current 39.8, max 42.7
Supply voltage: min 12.1, current 12.1, max 12.3, under voltage events: 0, over voltage events: 0
Driver 0: stalled standstill
Driver 1: stalled standstill
Driver 2: standstill
Driver 3: standstill
Driver 4: standstill
Current date and time: 2017-04-01 07:18:28
Slowest main loop (seconds): 0.120956; fastest: 0.000153
=== Move ===
MaxReps: 2, StepErrors: 0, MaxWait: 1556ms, Underruns: 0, 0
Bed compensation in use: mesh
Bed probe heights: 0.027 0.067 0.085 0.017 0.015 0.035 -0.028 -0.013 0.005 -0.038 -0.015 -0.025 -0.033 -0.060 -0.040 -0.130 -0.040 -0.030 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000
Probe change coordinates:
=== Heat ===
Bed heater = 0, chamber heater = -1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Stack records: 2 allocated, 0 in use
Movement lock held by null
http is ready with "M122"
telnet is idle
file is idle
serial is idle
aux is idle
daemon is idle
=== Network ===
WiFiServer is running
SPI underruns 0, overruns 0
=== Webserver ===
HTTP sessions: 1 of 8I tried M122 when I first powered the Duet Wifi on and it reported no bed compensation was in use. If I want to use grid leveling but don't want to wait for the whole process to complete, I would just send G29 S1, correct? The height map is saved on the SD card?
-
That's correct.
