extra z-offset every new print G29?

Phaedrux

Do you have a stop.g present in the sys folder?

When do you run G32 for bed.g?

When do you run G29 S1 to load the heightmap. It should be loaded after homing Z.

Can you add M561 to the start of your homez.g?

IndeX4D

@Phaedrux
Do you have a stop.g present in the sys folder? - no, should I?

When do you run G32 for bed.g? - also when homed manually.not every print. I´m not sure if before or after G29. What would be correct?

When do you run G29 S1 to load the heightmap. It should be loaded after homing Z. ----- after homing Z ( I tried before only one time but of course I got an error)

droftarts

@IndeX4D as I said earlier

As for why it resets higher up at the end of each print, I'd guess there's a G92 Z... in your end Gcode somewhere that is messing it up. Post a (short) Gcode file that exhibits this behaviour and we'll have a look.

Or post whatever is the last 10 or 20 lines of your Gcode (actual Gcode, not the comments).

Ian

IndeX4D

This post is deleted!

IndeX4D

@droftarts
I did already above..

G1 X610.176 Y449.295 E0.10056
G1 X611.585 Y450.704 E0.19684
G1 X610.566 Y450.704 E0.10066
G1 X609.158 Y449.295 E0.19677
G1 X608.14 Y449.295 E0.10056
G1 X609.548 Y450.704 E0.19677
G1 X608.53 Y450.704 E0.10056
G1 X607.121 Y449.295 E0.19684
G1 X606.103 Y449.295 E0.10056
G1 X607.512 Y450.704 E0.19684
G1 X606.493 Y450.704 E0.10066
G1 X605.085 Y449.295 E0.19677
G1 X604.067 Y449.295 E0.10056
G1 X605.475 Y450.704 E0.19677
G1 X604.457 Y450.704 E0.10056
G1 X603.048 Y449.295 E0.19684
G1 X602.03 Y449.295 E0.10056
G1 X603.439 Y450.704 E0.19684
G1 X602.421 Y450.704 E0.10056
G1 X601.012 Y449.295 E0.19684
G1 X600.745 Y449.295 E0.02637
G1 X600.745 Y450.046 E0.07419
G1 X601.402 Y450.704 E0.09185
G1 X600.745 Y450.704 E0.0649
;TIME_ELAPSED:5734.465541
G1 F6000 E-0.2
M140 S0
M204 P4000
M204 T4000
M566 X1200 Y1200
M82 ;absolute extrusion mode
M107
G91 G1 Z20 F400 G90
M83 ;relative extrusion mode
M104 S0
;End of Gcode

droftarts

@IndeX4D said in extra z-offset every new print G29?:

@droftarts
I did already above..

Sorry, yes you did, missed that. I’d say it’s this last Z move:

G91 G1 Z20 F400 G90

It’s at 6.66mm/s over a longer distance than usual Z moves. Try halving the speed to F200 and see if it still does it.

Ian

IndeX4D

@droftarts ok
no problem
I´ll try it.
thanks

o_lampe

@IndeX4D said in extra z-offset every new print G29?:

G91 G1 Z20 F400 G90

@droftarts Just wild guessing, but maybe there is a bug when switching to G91 and back to G90?
Maybe FW applies (or forgets?) the meshbed correction?

I have a similar line in my stop.g, but I usually do a paper test after each homing sequence.

jay_s_uk

@o_lampe i think the issue is bunching multiple gcode instructions on one line.
see this thread https://forum.duet3d.com/topic/32279/multiple-commands-on-single-line-bug-rf3-5b3

o_lampe

@jay_s_uk That would be easy to find out for @IndeX4D

IndeX4D

@o_lampe
oh I´m not sure.
So I should delete this at my end?

gloomyandy

@IndeX4D Try changing it to...

G91
G1 Z20 F400
G90

IndeX4D

@gloomyandy

ah ok
to easy to be true
ok thanks