Hello all When I issue the command BED_MESH_OUTPUT I get (as expected) the list of probed z values then the list of interpolated poins. Is it then correct to have a specular view of interpolated points vs. probed? This could be explaining my issues with poor bed mapping. // Bed Mesh state has bee…

(kicking myself) Found the solution: I was probing the bed at working temperature. BUT forgot that test print was performed also with HEATED CHAMBER. Turning on the chamber during probing fixed it all. Sorry to have bothered you all…

[grafik] [image] How-To Ask for Help Knowledge Base How-To Ask for Help General All contributors here help out in their spare time and because they want to give something back to the Klipper project. Be respectful and patient. If someone knows the answer to y…

Ok, was thinking it was a quick thing (hoping I was wondering about something usual). Surprisingly enough, the values shown into the log are quite different from console output. At this point I pass the hand to more skilled people to tell me what is going on. Brgds klippy_log.zip (15.5 KB)

The SAVE_CONFIG log entry shows the points as they are stored internally. The first probed point is at (min_x, min_y). The BED_MESH_OUTPUT command was implemented to be compatible with Marlin / Prusa Firmware at the time, therefore the y-axis is inverted. The first point printed is at (min_x, max…

Argh. Was hoping to hear I made some weird configuration mistake, since I am wrestling with Klipper bed meshing but got nowhere near to a workable solution. Tried -mapping and using without saving (yes, using BED_MESH_PROFILE LOAD=whonows) -saving with and without name (default or whonows). -us…

The only place in the config that I I see BED_MESH_CALIBRATE is in G29: ** [gcode_macro G29] gcode = BED_MESH_CLEAR T0 G28 T0 SET_VELOCITY_LIMIT ACCEL=3000 G1 X2 Y62 F16000 G1 Z0.1 F3000 G4 P500 G1 Z60 F3000 BED_MESH_CALIBRATE PROFILE="default" M400 BED_MESH_OUTPUT BED_MESH_PROFILE LO…

[image] garethky: I don’t know what PLATTER_CALIBRATION is and I cant find a source for it. Its some extra that’s not part of core klipper. Can we have a link please? Starting Klippy... Args: ['/opt/klipper/NPU/klippy/klippy.py', '/var/lib/Repetier-Server/database/klipper/NPU.cfg', '-l', '/tm…

Hello Sineos It is a klipper installation running on Repetier server. All the installation process is handled from the user interface - surely I didn’t alter/touch 118 files! I began installing version 11, then 12, then latest/greatest (Python3) on Github - always using Repetier Server graphical …

[image] tettabeta: …but result is always the same: squashed on front left corner, in the air mid front side. My guess for that… This is, I think, common for probes that are located somewhere along the Y axis in relation to the nozzle. The X rail will always have some twist in it. Usually the…

Ok, making a bracket to host probe on same X of nozzles. Will update as I install bracket and try new mapping!

Mounted a new bracket to bring probe aligned on X (therefore ruling out any issue of Y beam warping). Sadly, problems are unchanged: same problems are into same locations. Probe precision is still high (marginally improved, but we are splitting hair here, at micron scale), repeatibility is OK . I…

Bed mesh upside down?

General Discussion

Sineos April 10, 2025, 9:41am 2

Topic		Replies	Views
Experimental mesh leveling changes Developers	29	10529	July 2, 2023
Impossible Bed mesh leveling - Cr10sPro V2 General Discussion	89	23130	January 2, 2024
Bed_mesh is set based on x and y probe offsets, BEDMESH_CALIBRATE does not follow offsets and puts probe off the bed General Discussion	4	2105	June 30, 2021
Bed level not representative of real life General Discussion	21	430	February 11, 2025
Bed Mesh generated but not enough compensation for existing topography General Discussion	23	5189	February 29, 2024

Bed mesh upside down?

Related topics