I made a macro that alters your bed grid to the area the printer is actually printing on.

Inspired by https://forum.duet3d.com/topic/15302/cura-script-to-automatically-probe-only-printed-area

Features:

• makes sure the requested grid fits your probeable area (not neccesarily the same as the printable area)
• makes sure the grid is at least 3x3 points
• the grid is centered on the print and expanded to fit a whole number of constant size squares
• has two defined probe spacings - fine for small prints, coarse for large prints, so that you don't take ages to probe the entire bed

Works with prusaslicer and perhaps others

How to use:

• put the script into your /sys folder
• open it and edit the constants for your machine (read the comments)
• in PrusaSlicer, go to Printer settings / Custom G-code and replace G29 in your Start G-code with

M98 P"localised_mesh_bed.g" A[first_layer_print_min_0] B[first_layer_print_max_0] C[first_layer_print_min_1] D[first_layer_print_max_1] ; only probe the part of the bed that you're printing on

• add a command to reset the grid back to normal to your End G-code

M557 X24:228 Y6:210 S51 ; reset bed grid

• Those numbers are for my machine, please replace with your own.

localised_mesh_bed.g

@dc42 I confirm that the new binary does fix the issue for me, thank you!

• some way to display strings that are too long for the entire display width. It could be linebreaks, scrolling text...
• string slicing (some way to display a job file name without the 0:/gcodes/)
• time remaining based on slicer. It's already exposed in the object model, but the expressipn to convert [number of seconds] to HH:MM:SS seems to be too long for the menu file system.

Hello,
I've been working on a set of menu files for my printer and now that I have some time I decided to share them.
My files began as a modification of the menu created by @mudcruzr, but some of the files got so different in the end that I decided not to do a pull request (in particular, I created my own icons and removed some options from the main screen that I felt weren't used often enough to warrant beng on the main screen)

The printer this was designed for is a cartesian "bedslinger" with a single extruder, a heated bed and an inductive bed probe (modified Prusa)

Anyway, here's the link, enjoy!
https://github.com/Sidic101/Duet-Maestro-12864-Menu-Files

@oliof
Sliced for Duet: ringing_tower_0.4n_0.2mm_PLA_MK3.9_9m.gcode
Sliced for Klipper: ringing_tower_0.4n_0.2mm_PLA_MK3.9_7m.gcode

Here's what I use: https://github.com/gregsaun/maker_cheatsheet/blob/master/3d_printing/techniques.md

The different banding in the top and bottom half of each tower segment is (I think) because the move direction flips midway.

That's all I got so far. @oliof

And now: Klipper MZV:

That's the harshest lighting I could manage. It's just perfect somehow.

MZV, no besh bed:

EI3, no mesh bed: it made shorter segments worse than baseline

All shapers except EI3. Reduced speed, so the bands are closer together. 38 Hz, 0.1 dampening factor.

Interestingly, the results do differ for small segments:

Photos! They're here!

MZV, frequency sweep from 36 to 56 Hz, jerk 300.

I did in the end notice some weird corner artifacts, I didn't pay much attention to this area before.

Another thing I forgot to mention. Disabling pressure advance also didn't help.

@oliof I know the Duet version has high jerk and mesh bed enabled. I have disabled those manually while printing. Haven't seen a improvement.

(I am trying to tune the printer to use Prusa MK3.9 profiles, since it shares most of the mechanics with it. My printer is a heavily modified MK2 with a homebrew version of the Bondtech MK3 extruder)

@oliof
Sliced for Duet: ringing_tower_0.4n_0.2mm_PLA_MK3.9_9m.gcode
Sliced for Klipper: ringing_tower_0.4n_0.2mm_PLA_MK3.9_7m.gcode

@oliof
RRF 3.5 RC3+ (last week, DC42's hotfix of the network issues from here https://forum.duet3d.com/post/332835)

I have tried MZV at both 40 and 50 Hz in RRF to basically no improvement over no shaping.

I haven't encountered layer shifting or blobbing in RRF, but some of the shapers caused sharp corners to print much worse. No such issue with Klipper.