problem with the Mesh?second print start in the air

lui2004

@exerqtor said in problem with the Mesh?second print start in the air:

G29 S1

i have insert follow:

Starting script:
G28 ; home all axes
G29 S1 ; Load Mesh
G1 X0 Y20 Z0.2 F3000 ; get ready to prime
G92 E0 ; reset extrusion distance
G1 X100 E20 F600 ; prime nozzle

Ending Script:
M104 S0 ; turn off extruder
M140 S0 ; turn off bed
G1 X0 Y200 F1000 ; prepare for part removal
M84 ; disable motors

Phaedrux

Are you releveling your 2 lead screws again before starting the next print?

Your slicer end gcode turns off the motors, which could cause the two z axis motors to get out of sync.

So you may want to add G32 to your start gcode to run bed.g before the print.

lui2004

no i dont have made this to level for every print

thats my printer

ehat i can make for Ending Script
? leave it blank or delete the M84 ?

like this:

Starting script:
G28 ; home all axes
G29 S1 ; Load Mesh
G32 ; releveling lead Screaws
G1 X0 Y20 Z0.2 F3000 ; get ready to prime
G92 E0 ; reset extrusion distance
G1 X100 E20 F600 ; prime nozzle

Exerqtor

@phaedrux said in problem with the Mesh?second print start in the air:

Are you releveling your 2 lead screws again before starting the next print?

Your slicer end gcode turns off the motors, which could cause the two z axis motors to get out of sync.

So you may want to add G32 to your start gcode to run bed.g before the print.

Isn't G32 meant only if one have multible individually driven z-motors? If he drive he's two z-motors in paralell G32 won't do much?

lui2004

I have 1 z motor in E0 and 1 motor in z motor

Veti

@lui2004 said in problem with the Mesh?second print start in the air:

I have 1 z motor in E0 and 1 motor in z motor

youy mean E1?
M584 X0 Y1 Z2:4 E3 ; two Z motors connected to driver outputs Z and E1

Phaedrux

@exerqtor said in problem with the Mesh?second print start in the air:

@phaedrux said in problem with the Mesh?second print start in the air:

Are you releveling your 2 lead screws again before starting the next print?

Your slicer end gcode turns off the motors, which could cause the two z axis motors to get out of sync.

So you may want to add G32 to your start gcode to run bed.g before the print.

Isn't G32 meant only if one have multible individually driven z-motors? If he drive he's two z-motors in paralell G32 won't do much?

G32 just runs the bed.g macro, which he has setup to do independent lead screw leveling.

@lui2004 I think I would use this for your start gcode:

 Starting script:
G32 ; releveling lead Screaws
G29 S1 ; Load Mesh
G1 X0 Y20 Z0.2 F3000 ; get ready to prime
G92 E0 ; reset extrusion distance
G1 X100 E20 F600 ; prime nozzle

I removed the G28 since your bed.g already does G28, and then load the mesh again after the lead screws are leveled.

It's up to you if you want to leave M84 in your end gcode or not. If you only print 1 thing you may want to motors to turn off to be quieter and save power. But if you are usually printing many things in a row, maybe it makes more sense to leave it off.

I also just noticed that your bed.g calls G29 to run the mesh compensation mapping routine. You should decide if you want to run G29 every time, or if you want to load a saved heightmap instead. If you want to load the heightmap, remove the G29 from bed.g. If you want to run it every time, remove G29 S1 from your start gcode.

lui2004

Ok thanks a lot.

I will test now

Exerqtor

@phaedrux said in problem with the Mesh?second print start in the air:

@exerqtor said in problem with the Mesh?second print start in the air:

@phaedrux said in problem with the Mesh?second print start in the air:

Are you releveling your 2 lead screws again before starting the next print?

Your slicer end gcode turns off the motors, which could cause the two z axis motors to get out of sync.

So you may want to add G32 to your start gcode to run bed.g before the print.

Isn't G32 meant only if one have multible individually driven z-motors? If he drive he's two z-motors in paralell G32 won't do much?

G32 just runs the bed.g macro, which he has setup to do independent lead screw leveling.

Aaah sorry i didn't see that he was running the Z-motors individually!

Wouldn't it be smart to have home Z and X and remove the old bed transform before running the bed.g macro to btw? Like this:

;Start script start
G28 XY                         ; Home X and Y axis
M561                           ; Clear any bed transform that might be in place  
G32                            ; Re-level lead screws
G29 S1                         ; Load and turn on bed height map (mesh)
G1 X0 Y20 Z0.2 F3000           ; Get ready to prime
G92 E0                         ; Reset extrusion distance
G1 X100 E20 F600               ; Prime nozzle
;Start script end

lui2004

@exerqtor said in problem with the Mesh?second print start in the air:

Wouldn't it be smart to have home Z and X and remove the old bed transform before running the bed.g macro to btw? Like this:

what do you mean with

Wouldn't it be smart to have home Z and X and remove the old bed transform before running the bed.g macro to btw?

Phaedrux

@exerqtor he already clears the mesh compensation in bed.g

Exerqtor

@phaedrux said in problem with the Mesh?second print start in the air:

@exerqtor he already clears the mesh compensation in bed.g

Also correct, don't mind me I'll sit this one out

lui2004

I think it works now

Tommorow i will test nore prints

Thanks to all for Help

dc42

I have added some additional notes on using mesh bed compensation at https://duet3d.dozuki.com/Wiki/Using_mesh_bed_compensation. Main takeaways are:

Immediately before running G29 S0 (or just G29) to probe the bed, you should establish a Z=0 datum using the Z probe. If you home Z using the Z probe the right way, using a G30 command in homez.g/homeall.g, then you will have done that already. Otherwise, before running G29 S0 you should do a single G30 probe at bed centre, or alternatively run delta auto calibration or leadscrew bed levelling.
Before running G29 S1 to load the previously-saved height map, you should also establish a Z=0 datum in exactly the same way.

A height map display that is entirely above or entirely below Z=0 is a signal that you did not establish a Z=0 datum using the Z probe.

I am considering changing the firmware to emit warning messages (and perhaps refuse to run G29) if these conditions are not met, because I suspect this is the main explanation for inconsistencies in the overall Z offset of the height map and changes in the Z=0 position before/after a print.

Exerqtor

@dc42 said in problem with the Mesh?second print start in the air:

I have added some additional notes on using mesh bed compensation at https://duet3d.dozuki.com/Wiki/Using_mesh_bed_compensation. Main takeaways are:

Immediately before running G29 S0 (or just G29) to probe the bed, you should establish a Z=0 datum using the Z probe. If you home Z using the Z probe the right way, using a G30 command in homez.g/homeall.g, then you will have done that already. Otherwise, before running G29 S0 you should do a single G30 probe at bed centre, or alternatively run delta auto calibration or leadscrew bed levelling.

Before running G29 S1 to load the previously-saved height map, you should also establish a Z=0 datum in exactly the same way.

A height map display that is entirely above or entirely below Z=0 is a signal that you did not establish a Z=0 datum using the Z probe.

I am considering changing the firmware to emit warning messages (and perhaps refuse to run G29) if these conditions are not met, because I suspect this is the main explanation for inconsistencies in the overall Z offset of the height map and changes in the Z=0 position before/after a print.

That sounds like a good idea, or at least make it totally clear in the dozuki that Z homing MUST be done before G29 S0 is issued.

And on that topic, should M561 be issued before Z-homing / G30 in the slicer start script. And then issue G29 or G29 S1 at the very end?

dc42

@exerqtor said in problem with the Mesh?second print start in the air:

And on that topic, should M561 be issued before Z-homing / G30 in the slicer start script. And then issue G29 or G29 S1 at the very end?

That's a wise precaution, although it shouldn't be essential.