Printer Model: Qidi X Max 3 Revo
MCU / Printerboard: MKS PI X4 klippy.log
Gentleman,
I have a strange problem with my KAMP installation that was not able to solve yet.
I would appreciate if someone has an idea and can point me in the right direction.
Klipper 12 and mainsail are freshly installed as well as KAMP following all instructions from Github.
In printer.cfg I included the KAMP folder [include KAMP/*.cfg] but there are empty .cfg files and there read only.
So I created new versions within the config dir and also included it in printer.cfg.
Well, thatâs not entirely accurate. Native adaptive bed meshing was just implemented, KAMP is Klipper Adaptive Meshing & Purging. While adaptive probing is the killer feature that attracts most people to KAMP, some people also want the adaptive purging and smart park macros (or they wouldnât exist.)
This is also not correct. Adaptive meshing is activated by passing ADAPTIVE=1 when you call BED_MESH_CALIBRATE, it defaults to off.
You can put BED_MESH_CALIBRATE ADAPTIVE=1 either in your slicerâs start gcode or in a Klipper PRINT_START macro. Of course after homing and I would recommend also after heating the bed.
Note that you need to be on pretty much the latest Klipper git version to use this feature.
Hello,
Iâve been using ChipCEâs âKlipper mesh on print area onlyâ for adaptive meshing for a long time and it works great.
Today I saw that Klipper now has its own adaptive meshing and wanted to test it, but unfortunately it doesnât work.
I added it to the printer.cfg
[exclude_object]
In moonraker.conf
[file_manager]
enable_object_processing: True
In my START_PRINT macro I added ADAPTIVE=1 after BED_MESH_CALIBRATE.
[gcode_macro START_PRINT]
gcode:
{% set t_extruder = params.T_EXTRUDER|default(0) %}
{% set t_bed = params.T_BED|default(0) %}
SET_GCODE_OFFSET Z=0.0 ; Reset the G-Code Z offset (adjust Z offset if needed)
M220 S100 ; Set speed factor override percentage
M221 S100 ; Set extrude factor override percentage
G90 ; use absolute coordinates
M83 ; extruder relative mode
M104 S180 ; set extruder temp to warm up a little
M140 S{t_bed} ; set bed temp
M190 S{t_bed} ; wait for bed temp
G28 ; homing
BED_MESH_CLEAR
BED_MESH_CALIBRATE ADAPTIVE=1
M104 S{t_extruder} ; set extruder temp
G1 X3 Y30 Z30 F2000 ; go to the waiting position
M109 S{t_extruder} ; wait for extruder temp
PRIME_LINE ; prime a line
After restarting Klipper there was no error message.
But unfortunately it moves the entire bed and not just the area of the printed object as desired.
Klipper version is currently v0.12.0-103-g6ce6fbbc and no newer version is provided.
Make sure your slicer is configured to label objects. The latest version of PrusaSlicer can be configured to inject the Klipperâs exclude object gcode commands, eliminating the requirement for Moonraker to process the files:
In Printer Settings â General set the G-Code flavor to Klipper:
Also make sure you have PrusaSlicer in âExpertâ mode to view these options. See the upper right corner in PrusaSlicer, I accidentally cut it off in the above screenshots.
Not sure what you are reporting. Adaptive meshing is now included directly in Klipper and apart from updating Klipper to the latest version there is nothing to install.
You seem to have a wrong or obsolete section in the moonraker.conf.
Something like this:
[update_manager Klipper-Adaptive-Meshing-Purging]
type: git_repo
channel: dev
path: ~/Klipper-Adaptive-Meshing-Purging
origin: https://github.com/kyleisah/Klipper-Adaptive-Meshing-Purging.git
managed_services: klipper
primary_branch: main
Either delete this, uninstall KAMP and use Klippers native adapting bed mesh as @Sineos already mentioned or correct the above section with valid parameters.
