How do I enable MESH leveling for the print?
-
Previously using Marlin, I would manually probe the bed and keep that in EEPROM. I would simply run a command in my print starting script (G29 S1 IIRC) to use it. Tried the same script now using a Maestro, and it doesn't work.
How is MESH used on this platform? I have a BLTouch sensor on my carriage.
-
-
So I need to probe the bed for every print?
-
No, once a bed mesh has been built, it is loaded automatically (if so enabled in config.g) on startup and is used as a default for every print.
The Duet can take just over 400 mesh bed data points and in my case it takes about 3 hours to run a full (automated) scan. It would be a real bummer if I had to do that before every print
You can also build multiple mesh beds (say for different bed temperatures) and load a different bed if you want. In my case I decided to probe the bed at my most commonly used temperature and live with the slight differences at other temperatures. -
@Rat_Patrol
Once you have probed the bed with the commandG29 S0the result of the mesh probe is saved to /sys/heightmap.csv
Without probing the bed again, you can load the saved result from an earlier mesh probe using the command
G29 S1 ; this loads the contents of /sys/heightmap.csv -
@Rat_Patrol said in How do I enable MESH leveling for the print?:
Tried the same script now using a Maestro, and it doesn't work.
If you used G29 S1 and it didn't work, what exactly didn't work about it?
Typically you'd put G29 S1 in the slicer start gcode. Or even at the end of homeall.g (called by G28) if you wanted it to be active at all times to protect the nozzle from contacting the bed surface if you happen to have a less than perfectly flat bed.
-
My slicer start code:
M572 D0 S0.045
G28
G29 S1When the print starts, the Z rods visibly aren't running MESH, and the uneven first layer confirms it. I have run MESH probing, can view the map, but MESH is strangely absent during a print.
-
M122 shows you whether mesh levelling has been activated or not
-
10:24:26 AMM122 === Diagnostics === RepRapFirmware for Duet 2 Maestro version 2.05 running on Duet Maestro 1.0 Board ID: 08DAM-9F9GA-J24TD-6J9F0-3SW6R-K51QV Used output buffers: 1 of 24 (14 max) === RTOS === Static ram: 19804 Dynamic ram: 91164 of which 0 recycled Exception stack ram used: 336 Never used ram: 19768 Tasks: NETWORK(ready,716) HEAT(blocked,1272) MAIN(running,3896) IDLE(ready,160) Owned mutexes: === Platform === Last reset 17:18:54 ago, cause: power up Last software reset at 2020-01-20 16:37, reason: User, spinning module GCodes, available RAM 19780 bytes (slot 2) Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0400f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d Error status: 0 Free file entries: 10 SD card 0 detected, interface speed: 15.0MBytes/sec SD card longest block write time: 53.1ms, max retries 0 MCU temperature: min 21.1, current 34.8, max 41.8 Supply voltage: min 0.0, current 24.2, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes Driver 0: standstill, read errors 0, write errors 0, ifcount 16, reads 2962, timeouts 0 Driver 1: standstill, read errors 0, write errors 0, ifcount 16, reads 2949, timeouts 13 Driver 2: standstill, read errors 0, write errors 0, ifcount 16, reads 2962, timeouts 0 Driver 3: standstill, read errors 0, write errors 0, ifcount 14, reads 2948, timeouts 16 Driver 4: standstill, read errors 0, write errors 0, ifcount 6, reads 2972, timeouts 0 Driver 5: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 2977 Driver 6: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 2977 Date/time: 2020-01-21 10:24:21 Slowest loop: 147.95ms; fastest: 0.05ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Move === Hiccups: 0, FreeDm: 160, MinFreeDm: 130, MaxWait: 56660031ms Bed compensation in use: mesh, comp offset 0.073 === DDARing === Scheduled moves: 12, completed moves: 12, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 === Heat === Bed heaters = 0, chamberHeaters = -1 -1 Heater 0 is on, I-accum = 0.0 === GCodes === Segments left: 0 Stack records: 2 allocated, 0 in use Movement lock held by null http is idle in state(s) 0 telnet is idle in state(s) 0 file is idle in state(s) 0 serial is idle in state(s) 0 aux is idle in state(s) 0 daemon is idle in state(s) 0 queue is idle in state(s) 0 lcd is idle in state(s) 0 autopause is idle in state(s) 0 Code queue is empty. === Network === Slowest loop: 135.62ms; fastest: 0.02ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0) HTTP sessions: 1 of 8 Interface state 5, link 100Mbps full duplex -
@Rat_Patrol said in How do I enable MESH leveling for the print?:
=== Move ===
Hiccups: 0, FreeDm: 160, MinFreeDm: 130, MaxWait: 56660031ms
Bed compensation in use: mesh, comp offset 0.073It shows as being active.
Do you have a picture of your bed mesh?
How many probe points do you have?
Do you probe it hot or cold? -
Pic of probing results:
Ran MESH at PETG temps.
-
My bed is very uneven at this point: I'm running a temporary Y carriage setup until I get some hardware in to manually level it out.
Or until I cut up some soda cans
-
Well, I re-sliced and uploaded, and MESH appears to be working now.
Not doing a great job though, its like my nozzle-to-probe offset is wrong.
I got the numbers for the offset from Fusion where I modeled all the parts, does my config look good?
; Configuration file for Duet Maestro (firmware version 2.03) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v2.1.5 on Thu Jan 09 2020 17:14:50 GMT-0600 (Central Standard Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"Robo R1++" ; set printer name M918 P1 E4 F2000000 ; configure direct-connect display ; Network M551 P"xxxxx" ; set password M552 P0.0.0.0 S1 ; enable network and acquire dynamic address via DHCP M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ; Drives M569 P0 S1 ; physical drive 0 goes forwards M569 P1 S1 ; physical drive 1 goes forwards M569 P2 S1 ; physical drive 2 goes forwards M569 P3 S1 ; physical drive 3 goes forwards M584 X0 Y1 Z2 E3 ; set drive mapping M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X80.00 Y80.00 Z400.00 E813.65 ; set steps per mm M566 X100.00 Y100.00 Z100 E100 ; set maximum instantaneous speed changes (mm/min) M203 X9000.00 Y9000.00 Z720.00 E2100.00 ; set maximum speeds (mm/min) M201 X1100.00 Y1100.00 Z1100.00 E3000.00 ; set accelerations (mm/s^2) M906 X1500 Y1500 Z1000 E1500 I50 ; set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ; Axis Limits M208 X0 Y0 Z0 S1 ; set axis minima M208 X210 Y210 Z250 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 H5 F300 T6000 ; set Z probe type to bltouch and the dive height + speeds G31 P500 X-32.201 Y-26.389 Z3.00 ; set Z probe trigger value, offset and trigger height M557 X0:210 Y0:210 S40 ; define mesh grid ; Heaters M305 P0 T100000 B4138 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 S280 ; set temperature limit for heater 1 to 280C ; Fans M106 P0 S0 I0 F500 H-1 ; set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off M106 P1 T45 S1 H1 ; set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on ; Tools M563 P0 S"Extruder" 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 ; Custom settings are not defined -
In my experience I manually level the bed using to 4 screws on my ender3.
I try and make it as level as possible using paper gauge between nozzle and bed.
Not teaching sucking eggs, I release the x/y steppers so I can move the gantry. Z is jogged down to grip paper, but stepper is engaged.The I run the mesh after heating the nozzle to 160 and bed to 60
I also have 2 mirrors I use. I rename each heightmap to mirror 1 or 2 and call each mirror from cura’s start code. -
I too had my offset from CAD, but turns out, it's not correct, since tolerances make things imperfect. Put a paper on the Heatbed, and slowly and manually run the nozzle into it, leaving a tiny mark, and also mark where your bed Probe is. Now measure everything and use that.
I had the same issue of thinking that mesh bed leveling was doing a bad job, until I remeasured my offset and realized I was off my 10mm.
-
@Rat_Patrol said in How do I enable MESH leveling for the print?:
M558 P9 H5 F300 T6000 ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X-32.201 Y-26.389 Z3.00You can increase the accuracy and repeatability of the BLTouch by tweaking those settings a bit.
M558 P5 H5 F100 T6000 R0.5 A5
G31 P25Then use this link to calibrate the trigger height and measure the X Y offset for the rest of G31.
-
@Phaedrux said in How do I enable MESH leveling for the print?:
M558 P5 H5 F100 T6000 R0.5 A5
G31 P25Don’t you mean M558 P9 H5 F100 T6000 R0.5 A5 ?
Ian
Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth
-
@droftarts absolutely I did!
-
Its not that the initial layer height is just wrong everywhere, some parts of the print have major squish and others are just fine.
-
I did run through the BLTouch probe calibration procedure (ended up at 2.95mm IIRC). I designed my extruder carriage, so I just took the probe offset from the nozzle from Fusion, so it should be darned accurate.
