problem with the Mesh?second print start in the air
-
@lui2004
no but it is a good idea to do so.
it is just a command and does not take up time. -
Ok i will give it a try
Or i insert the gcode in my bed.g to load automatic
-
Or put it in your Slicer 'Start GCode', easiest way I find.
-
I have G29 S1 at the end of my config.g that way it's loaded every time on startup.
-
so the first print after mesh works perfectly but when i start the second the nozzle is to high
i have try to send beofor i start the second print G29 S1 but always the nozzle to high
Firmwarename: RepRapFirmware for Duet 2 WiFi/Ethernet
Firmware Elektronik: Duet WiFi 1.02 or later
Firmware Version: 2.02(RTOS) (2018-12-24b1)
WiFi Server Version: 1.22
Web Interface Version: 1.22.6i hope you can help to solve it
-
you do home before each print?
-
yes in my slicer is this starting code
G28 ; home all axes
-
@lui2004 what is at the end of your files that the slicer is putting in there?
-
I have only G28 i my starting code nothing else
-
do check with m122 that mesh bed leveling is still active.
-
@veti said in problem with the Mesh?second print start in the air:
m122
seems active
Bed compensation in use: mesh
Bed probe heights: -0.052 -0.028 0.000 0.000 0.000 -
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?
-
do i need to post gcode from a print ?
-
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.
-
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
-
@lui2004 Please share a small gcode file from your slicer that causes this issue.
-
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.
-
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 ?
-
@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. -
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 ?