Layer,Filament Used and Remaining stats
-
Anyone explain what's going on here?
Layer 45 of 25?
-
Can you post the gcode file?
I suspect you have some Z moves at the start of the file doing a nozzle prime, or a Z move perhaps at the end of the file?
-
It is common with every print I do. I'm using Cura slicer so based on what you said it must be something in my start.g or end.g in cura.
Here is the code: -
One solution may be to move the g28 and g1 z15 move into a file called start.g
That would get run before every print. That way the z move wouldn't be in the start code that gets parsed by the DWC.
But it could also be the extra z move and retraction in your end code.
This is one of the reasons I've moved all my start and end gcode into seperate macro files.
Start.g which gets run before every print and stop.g which gets called by M0 which iputinthe slicer end code.
This also has the benefit of keeping the slicer code generic which is handy if you use multiple slicer all the time. If I want to change the start and end gcode I just edit the one macro on the duet.
-
Thanks for that. I will make the changes.
If I put the code into start.g and end,g in the duet system folder will they run automatically or do I still have to call them before every print? -
@phaedrux said in Layer,Filament Used and Remaining stats:
Start.g which gets run before every print and stop.g which gets called by M0 which i put in the slicer end code.
-
@chas2706 I think this might be caused by Z-Hop in Cura (although i have not noticed it so maybe not) as an experiment can you try slcing without Z hop and see if that fixes the issue?
-
Thanks both of you I will make the changes and see if the problem goes away.
-
I think in Cura, if your z hop height (eg 0.1mm) is not the same as the layer height (eg 0.2mm), it will count as an extra layer, so you'll have double the number of layers.
Ian
-
@droftarts ahh that may be why i did not notice it.