z offset not holding between prints | VORONDesign | Page 1

deep lynx Jul 19, 2025, 3:34 PM

#

I have to find z offset with every print. Im using the cartographer, xxol toolhead with the rapido hotend, and nitehawk 36 board,.

#

📎 klippy_8.log

eager berry Jul 19, 2025, 3:55 PM

#

deep lynx

could you also please post your printer.cfg?

deep lynx Jul 19, 2025, 3:56 PM

#

yep, give me a minute

#

📎 message.txt

eager berry Jul 19, 2025, 4:01 PM

#

ah, i see you're using cartographer, i'll have to leave it to someone who has experience with that

deep lynx Jul 19, 2025, 4:01 PM

#

I just tried to delete cartographer and it said it couldnt find the file so i reinstalled it

#

Im going to try printing again

austere pine Jul 19, 2025, 9:15 PM

#

I'm no cartographer expert, but I'm suspicious of the fact that you're doing cartographer_touch after your mesh

#

That doesn't strike me as likely to be correct

outer gull Jul 20, 2025, 6:46 PM

#

Yea touch needs to come after bed mesh.

Print_Start should go in this order.

SET_DISPLAY_TEXT MSG="QGL"                             # Displays info
{% if printer.quad_gantry_level.applied == False %}    # Levels the buildplate via QGL
  quad_gantry_level                                    # Run QGL only if not applied
{% endif %}

# Bed Mesh
  {% if printer.bed_mesh.profile_name == "default" %}  # Mesh is already loaded, skip bed mesh calibration
      SET_DISPLAY_TEXT MSG="Bed mesh loaded"           # Displays info
  {% else %}
      SET_DISPLAY_TEXT MSG="Bed mesh"                  # Displays info
      BED_MESH_CALIBRATE                               # Starts bed mesh
  {% endif %}

CARTOGRAPHER_TOUCH                  # Calibrate z offset only with hot nozzle

low bloomBOT Jul 20, 2025, 6:57 PM

#

@outer gull When posting configs or logs, please surround with code fences (```) so that Discord formats them correctly. Example:
```ini
[mcu]
serial: /dev/serial/by-id/usb-klipper-12345-if00
```

[mcu]
serial: /dev/serial/by-id/usb-klipper-12345-if00

eager berry Jul 20, 2025, 6:59 PM

#

outer gull Yea touch needs to come after bed mesh. Print_Start should go in this order. ...

i'd argue that you should always do qgl and bed mesh, it's cheap insurance, even moreso with cartographer

if i'm doing a 5 hour print, do i really care if the startup routine takes 30 seconds?

outer gull Jul 20, 2025, 7:01 PM

#

eager berry i'd argue that you should *always* do qgl and bed mesh, it's cheap insurance, ev...

Its probably not a bad idea. So far I havent had any issues with it. Ive had perfect prints doing this with Carto ... and almost perfect prints with Eddy.

#

But I agree....the advice would be to do it everytime. LOL

deep lynx Jul 20, 2025, 9:54 PM

#

austere pine That doesn't strike me as likely to be correct

Is that shown in my printer.cfg?

austere pine Jul 20, 2025, 9:57 PM

#

deep lynx Is that shown in my printer.cfg?

yes, but you'll notice that people who do know cartographer also say I'm wrong, and it should be done last. so 🤷

deep lynx Jul 20, 2025, 9:58 PM

#

austere pine yes, but you'll notice that people who do know cartographer also say I'm wrong,...

im not using touch at all

austere pine Jul 20, 2025, 9:59 PM

#

deep lynx im not using touch at all

really?

#

because it says its in your print_Start

deep lynx Jul 20, 2025, 10:00 PM

#

From what ive read BED_MESH_PROFILE LOAD=default has to be in the start gcode.
i put it in and it seemed to work for awhile but now im back to having issues

austere pine Jul 20, 2025, 10:00 PM

#

[gcode_macro PRINT_START]
gcode = 
    
    {% set target_bed = params.BED|int %}
    {% set target_extruder = params.EXTRUDER|int %}
    {% set target_chamber = params.CHAMBER|default("45")|int %}
    {% set x_wait = printer.toolhead.axis_maximum.x|float / 2 %}
    {% set y_wait = printer.toolhead.axis_maximum.y|float / 2 %}
    
    SET_GCODE_OFFSET Z=0
    
    
    STATUS_HOMING
    G28
    G90
    
    
    BED_MESH_CLEAR
    
    
    {% if params.BED|int > 90 %}
    SET_DISPLAY_TEXT MSG="Bed: {target_bed}c"
    STATUS_HEATING
    M106 S255
    
    
    
    
    G1 X{x_wait} Y{y_wait} Z15 F9000
    M190 S{target_bed}
    SET_DISPLAY_TEXT MSG="Heatsoak: {target_chamber}c"
    
    
    
    {% else %}
    SET_DISPLAY_TEXT MSG="Bed: {target_bed}c"
    STATUS_HEATING
    G1 X{x_wait} Y{y_wait} Z15 F9000
    M190 S{target_bed}
    SET_DISPLAY_TEXT MSG="Soak for 5 min"
    G4 P300000
    {% endif %}
    
    
    SET_DISPLAY_TEXT MSG="Hotend: 150c"
    M109 S150
    
    
    
    SET_DISPLAY_TEXT MSG="Leveling"
    STATUS_LEVELING
    QUAD_GANTRY_LEVEL
    G28 Z
    
    
    SET_DISPLAY_TEXT MSG="Bed mesh"
    STATUS_MESHING
    BED_MESH_CALIBRATE
    
    CARTOGRAPHER_TOUCH
    
    
    SET_DISPLAY_TEXT MSG="Hotend: {target_extruder}c"
    STATUS_HEATING
    G1 X{x_wait} Y{y_wait} Z15 F9000
    M107
    M109 S{target_extruder}
    
    
    SET_DISPLAY_TEXT MSG="Printer goes brr"
    STATUS_PRINTING
    G0 X{x_wait - 50} Y4 F10000
    G0 Z0.4
    G91
    G1 X100 E20 F1000
    G90

austere pine Jul 20, 2025, 10:00 PM

#

deep lynx From what ive read BED_MESH_PROFILE LOAD=default has to be in the start gcode. ...

....your print start RUNS a mesh at the start of each print

#

so, no, you definitely shouldn't be loading a mesh

deep lynx Jul 20, 2025, 10:01 PM

#

so take that out?

austere pine Jul 20, 2025, 10:02 PM

#

the log file you posted doesn't have a mesh load in it (and does have a carto touch in it)

deep lynx Jul 20, 2025, 10:02 PM

#

This is my maching gcode

austere pine Jul 20, 2025, 10:02 PM

#

so I'm a little unsure wtf we're actually talking about

#

oh definitely get rid of that

#

all that's doing is completely erasing whatever new mesh you've generated, in favor of some older saved mesh

#

that's a terrible idea

deep lynx Jul 20, 2025, 10:03 PM

#

as far as macros go, i use the better start macro

deep lynx Jul 20, 2025, 10:04 PM

#

austere pine the log file you posted doesn't have a mesh load in it (and does have a carto to...

Do i need to change something in that file?

austere pine Jul 20, 2025, 10:05 PM

#

I mean, it says you're using carto touch, and you say you aren't, so it would probably be a good idea to figure out the discrepency there

#

but that doesn't necessarily mean you need to change anything

#

just...that you need to figure out why the facts aren't matching up

#

(might be a clue there as to why you're having problems)

deep lynx Jul 20, 2025, 10:10 PM

#

So PROBE_SWITCH apparantly switches back and forth between touch and scan, i nput it in and i will see what happens

#

just seems odd to me because it never initiated a touch process before

austere pine Jul 20, 2025, 10:12 PM

#

cartographer_touch does a single tap in the middle of the bed to calibrate the z offset, I think. it's totally unrelated to probe_switch

deep lynx Jul 20, 2025, 10:15 PM

#

im confused i guess lol. What am I looking for? It does do a single touch in the middle of the bed after qgl

austere pine Jul 20, 2025, 10:15 PM

#

deep lynx im confused i guess lol. What am I looking for? It does do a single touch in the...

just facts. you literally told me it wasn't doing any touches!

#

so if its actually doing one (after the mesh, not just qgl, surely) then ....we're good...

deep lynx Jul 20, 2025, 10:16 PM

#

i did, i didnt realize that was the touch, you are correct

austere pine Jul 20, 2025, 10:17 PM

#

okay, so now that you understand what a touch is, lets go all the way back to the beginning of this

#

you say you have to "find z offset" every print

#

so I assume you mean you're using the mainsail or klipperscreen controls to adjust that at the beginning of each print?

#

is the adjustment you have to make consistent? or does it vary from print to print?

deep lynx Jul 20, 2025, 10:18 PM

#

mainsail

#

It varies

#

It never seems to hold any of my adjustments and never follows the bed mesh

austere pine Jul 20, 2025, 10:19 PM

#

it's not actually supposed to hold your adjustments

#

unless you do something to apply them to somewhere more permanent

#

and even that, I suspect gets stomped on by the carto touch thing

deep lynx Jul 20, 2025, 10:20 PM

#

but it should be moving the z up and down to account for differences, correct?

austere pine Jul 20, 2025, 10:20 PM

#

...maybe...

#

I mean, yes, it should be

#

but I have to tell you. 90% of the time, when people say it's not following the mesh, they're just plain wrong

deep lynx Jul 20, 2025, 10:21 PM

#

Looking at z on the ui, its moving a very small amount

austere pine Jul 20, 2025, 10:21 PM

#

they just don't understand how little movement 0.1 or 0.2 mm (over a bunch of horizontal travel) really is

austere pine Jul 20, 2025, 10:22 PM

#

deep lynx Looking at z on the ui, its moving a very small amount

is your mesh that bad, that the very small z movements aren't what you would expect?

deep lynx Jul 20, 2025, 10:23 PM

#

no, i just figured id see a little more movement on the belts is all

austere pine Jul 20, 2025, 10:23 PM

#

No. It's such small, gradual movements, it's really really hard to see

deep lynx Jul 20, 2025, 10:23 PM

#

Im probably wrong too, on how small the movement is

austere pine Jul 20, 2025, 10:23 PM

#

Gotta get in there with like flags & crap to really have much chance of seeing it

#

You can HEAR it, sometimes 😛

deep lynx Jul 20, 2025, 10:24 PM

#

I stsrted another print and its doing good now

austere pine Jul 20, 2025, 10:24 PM

#

Let's assume for now, that if you're seeing small movements in z on the display, it is in fact following the mesh

#

And focus on why the overall z offset is a problem

#

So how much do you normally need to adjust?

deep lynx Jul 20, 2025, 10:26 PM

#

It seems to be printing good atm, which is weird, because I was having issues before I added that bed mesh line

austere pine Jul 20, 2025, 10:27 PM

#

It's doing well now...with no manual z adjustments?

deep lynx Jul 20, 2025, 10:27 PM

#

Maybe

#

yep

austere pine Jul 20, 2025, 10:27 PM

#

Heh

deep lynx Jul 20, 2025, 10:27 PM

#

Maybe probe switch allowed it to use the touch?

#

its doing good\

#

i was in the middle of typing something else and fat fingered it

#

FYI, im no expert on anything lol

deep lynx Jul 20, 2025, 10:32 PM

#

austere pine Heh

Best first layer ive seen in ages

deep lynx Jul 21, 2025, 2:52 AM

#

shockingly having problems again

outer gull Jul 21, 2025, 3:40 AM

#

As far as I know with Carto you can only use the scan or touch profiles. You cant switch on the fly. You have to recalibrate when you change from one to the other. But Im just an enthusiast...LOL. I have and use carto.,

deep lynx Jul 22, 2025, 2:23 AM

#

This issue has been solved

outer gull Jul 22, 2025, 6:24 AM

#

what was it?

eager berry Jul 22, 2025, 7:35 AM

#

deep lynx This issue has been solved

please detail how, so that if anyone else with the same/similar issue can learn

deep lynx Jul 23, 2025, 11:29 PM

#

my carto was mounted to high up

#

when they say between 2.6 to 3mm they mean it

#

I had to print some spacers to move the carto closer to the bed

deep lynx Jul 23, 2025, 11:31 PM

#

outer gull what was it?

Stupid mistake on my part

outer gull Jul 24, 2025, 1:10 AM

#

Yea that will do it. Its pretty specific.

deep lynx Jul 24, 2025, 2:25 AM

#

outer gull Yea that will do it. Its pretty specific.

its printing great now, it doesnt fail on the qgl anymore either

outer gull Jul 24, 2025, 2:42 AM

#

Nice. Mines been printing great also. Im very happy with the carto probe.

deep lynx Jul 25, 2025, 1:26 AM

#

outer gull Nice. Mines been printing great also. Im very happy with the carto probe.

Me too, all though I was on the verge of switching to the beacon because of the problems, but that would not have solved them, so im glad i didnt

outer gull Jul 25, 2025, 4:01 AM

#

Beacon is pretty much the same probe as carto. Just more expensive.

#z offset not holding between prints