problem with the Mesh?second print start in the air

dc42

Are you able to reproduce this problem without doing an actual print? Or with a "print" comprising just a few lines of GCode taken from a real print?

lui2004

do i need to post gcode from a print ?

dc42

What I would like a the GCode for a simple sequence that replicates the problem - not a full GCode file that takes a long time to print, but a very simple one that takes only a few seconds.

lui2004

if you explane me how to do this i will post it

because now i finisched my first print after mesh and the second print is to heigh from the bed

T3P3Tony

@lui2004 Please share a small gcode file from your slicer that causes this issue.

PaulHew

I am having this problem too, again.
Full hardware check after upgrading my hotend to a DirectDrive etc.
Manual bed level, Setup correct Z height M564, G92 Z0, probe tests etc.
Ran mesh Level.
Printed a test object to test retraction came out fine.
Went to print a second object and would not stick to bed.

Piece of paper under nozzle dropped Z to where the Maestro thought was 0 and it was above again, paper not being gripped.
Redid the probe height again and was out by about -0.15 to get it to touch the paper.
This happened a number of times, I upgraded my Maestro to 2.03RC3 just incase.
Printed an object overnight to test how well everything is and print came out fine, after performing the procedure multiple times.

This morning I came back from gym and have tried to print something, everytime failing.
Piece of paper under the nozzle drop Z to where it thinks 0 is and again I can get a piece of paper under the nozzle and it is not touching.
M564 S0
Adjust down to paper and it is -0.20 out again.

Issued G92 Z0 which supposedly tells the board where 0 is.
Powered off and on printer, homed all.
Piece of paper, drop Z to where it thinks 0 is and again it is -0.15 out.
I am doing this as I am typing to make sure I give you all info to help.

This keeps happening and no one touches the printer apart from me.
It seems to have a mind of its own and this is not the first time I have reported this issue along with other people.

Is there anything I can do to help Duet isolate this problem please let me know.

Regards

Paul.

lui2004

now if i put in G31 Z-0.1 it print first layer with 0.12mm
if i put 0.2 the printer print 0.2.4mm,why ?

something is going wrong or no ?

Veti

@lui2004
you do not adjust the first layer for the first layer with G31. The slicer does that for you.
The G31 is the same for every layer height.

lui2004

I insert only The trigger height what i get with G30 -1 ?

My config in first Post is ok ?
I will use 2 indepenent z motors and mesh what is The best procedur ?

Exerqtor

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

I insert only The trigger height what i get with G30 -1 ?

I don't think you have quite understood how this all is supossed to work mate.

You shouldn't have to rely on a G30 at all other than when your doing Z-homing, all that should be taken care of in the G31 inside your config.g. When at Z0 and you have your G31 configured correct your nozzle should be actually touching the bed surface. And then the first layer setting you choose in your slicer wil raise the nozzle to the corresponding amount.

The mesh bed leveling is applied on the firmware side at all time to adjust for the uneaveness in your bed on top of that initial first layer height, given that you have G29 S1 after the homing sequence of your startup script (in your slicer).

Being your using a microswitch type Z-probe you have to be pretty accurate with the physical Z-ofsett from your nozzle not to buttom it out depending on your switch and bed setup ofc.

To get this to work you have to give us the Start script you have set in your slicer like the other guys here have been asking for. Given that the 0.320mm Z-offset you have in your config.g is correct the problem have to be somewhere in your startup code.

lui2004

Hi

Thanks for your answer !
My english is not The best sorry for some errors.

I think also i dont have understand hownto use it.

Can you Help me to get it work ?
And how to procedur? My config is in Post 1 what i have in usr.

In my slicer in start Scripts i have only G28 ; Home all axes nothing more

Phaedrux

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

I am having this problem too, again.
Full hardware check after upgrading my hotend to a DirectDrive etc.
Manual bed level, Setup correct Z height M564, G92 Z0, probe tests etc.
Ran mesh Level.
Printed a test object to test retraction came out fine.
Went to print a second object and would not stick to bed.

Piece of paper under nozzle dropped Z to where the Maestro thought was 0 and it was above again, paper not being gripped.
Redid the probe height again and was out by about -0.15 to get it to touch the paper.
This happened a number of times, I upgraded my Maestro to 2.03RC3 just incase.
Printed an object overnight to test how well everything is and print came out fine, after performing the procedure multiple times.

This morning I came back from gym and have tried to print something, everytime failing.
Piece of paper under the nozzle drop Z to where it thinks 0 is and again I can get a piece of paper under the nozzle and it is not touching.
M564 S0
Adjust down to paper and it is -0.20 out again.

Issued G92 Z0 which supposedly tells the board where 0 is.
Powered off and on printer, homed all.
Piece of paper, drop Z to where it thinks 0 is and again it is -0.15 out.
I am doing this as I am typing to make sure I give you all info to help.

This keeps happening and no one touches the printer apart from me.
It seems to have a mind of its own and this is not the first time I have reported this issue along with other people.

Is there anything I can do to help Duet isolate this problem please let me know.

Regards

Paul.

In order to keep peoples problems and configs etc straight it would be best to start a seperate thread with your own issues. It can get fairly confusing trying to help two seperate people in the same thread.

Phaedrux

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

Hi

Thanks for your answer !
My english is not The best sorry for some errors.

I think also i dont have understand hownto use it.

Can you Help me to get it work ?
And how to procedur? My config is in Post 1 what i have in usr.

In my slicer in start Scripts i have only G28 ; Home all axes nothing more

Can you post a picture of your heightmap image from the DWC?

Do you have any end gcode in your slicer?

G31 tells the firmware where the probe is in relation to the nozzle tip in X and Y and how far away the nozzle is from the bed when the probe triggers in Z.

G30 takes that information from G31 and probes the bed and when the probe triggers it sets the current height to be equal to the G31 Z value, which should allow it to know where Z0 is.

The first layer height in the slicer is set based on Z0 being at 0.

Can you give us some more details about your printer? How is the Z axis setup?

If you move the nozzle to Z0 and then move the Z axis up and down many times does it then return to Z0 accurately when you command it to?

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.