nozzle dives almost 4 mm too deep into the bed

axiom

@axiom
I discovered that you can create a config.overridge file using the M500 command. I did that but there is not much in it:

; config-override.g file generated in response to M500 at 2023-04-15 08:54
; This is a system-generated file - do not edit
; Heater model parameters
M307 H1 R1.797 K0.742:0.000 D7.57 E1.35 S1.00 B0 V23.8
M307 H2 R0.283 K0.463:0.000 D7.17 E1.35 S1.00 B0
; Workplace coordinates
G10 L2 P1 X0.00 Y0.00 Z0.00
G10 L2 P2 X0.00 Y0.00 Z0.00
G10 L2 P3 X0.00 Y0.00 Z0.00
G10 L2 P4 X0.00 Y0.00 Z0.00
G10 L2 P5 X0.00 Y0.00 Z0.00
G10 L2 P6 X0.00 Y0.00 Z0.00
G10 L2 P7 X0.00 Y0.00 Z0.00
G10 L2 P8 X0.00 Y0.00 Z0.00
G10 L2 P9 X0.00 Y0.00 Z0.00

Phaedrux

If you manually move the nozzle to touch the bed, then send G92 Z0, then jog to Z100, if you measure the distance is it actually 100mm?

If you home X and Y and then send G30 to probe the bed, does Z0 equate to the nozzle touching the bed?

axiom

@Phaedrux I installed a new probe..that didn't change anything.
if I move the bed with G1 Z40 after executing the G92 Z0 command, the distance is correct. But when I run the G1 Z40 command after homing, the distance is about 5mm too small.

Phaedrux

@axiom said in nozzle dives almost 4 mm too deep into the bed:

But when I run the G1 Z40 command after homing, the distance is about 5mm too small.

That would be because your trigger height is -5mm. You're telling it that the nozzle is 5mm below the surface of the bed when the probe triggers.

Can you try this? Set your probe type to M558 P0 for manual probe mode. Change to G31 X0 Y0 Z0 since there are no offsets. Then go through your normal homing and leveling routine. This will prompt you to jog the nozzle down to touch the bed whenever the probe would normally be called.

axiom

@Phaedrux said inDon't get me wrong: I change the M588 and the G31 command in config.g?
Does this mean I should manually check 190 points when leveling bed?

axiom

@Phaedrux I rather have the impression that the value is not being transferred, I can never find the M500 command anywhere....I already sent the code...where should it be with the M500?

Phaedrux

Yes you need to change the M558 and G31 in config.g

Since the manual probing is very slow, I would also recommend changing the mesh grid size to be much smaller. Maybe a 2x2 grid for now. 190 points would take a very very long time.

@axiom said in nozzle dives almost 4 mm too deep into the bed:

@Phaedrux I rather have the impression that the value is not being transferred, I can never find the M500 command anywhere....I already sent the code...where should it be with the M500?

I'm not sure what you mean. You don't need to use M500 at all for this. M500 is only used to save things that are calculated by the firmware, like heater PID tuning values, etc.

jay_s_uk

@axiom if you want the probe offset saved with M500, use M500 P31

axiom

@Phaedrux I think I was able to partially solve the riddle: I thought the M561 command would also delete the trigger values in config.g. You have to manually set the trigger value G31 of Z to 0 before the trigger test. The second thing I did is physically decrease the distance of the sensor. The disadvantage of a capacitive sensor is that the heat from the bed will greatly reduce the life of the sensor. So I'll be looking for a new sensor system in the long term...I've started reading about the piezo technology, but I suspect that the one on my Volcano hotend is too big...but in any case, the printer is running reasonably well now... ..just to understand: Are the values after the mesh bed compensation automatically taken into account during the job and are the unevenness compensated?

Phaedrux

@axiom said in nozzle dives almost 4 mm too deep into the bed:

just to understand: Are the values after the mesh bed compensation automatically taken into account during the job and are the unevenness compensated?

Yes, that's the point of the mesh.

axiom

@Phaedrux thanks for your patience ! Maybe you could set that with z=0 in the config.g for complete beginners like me in the documentation?