Incorrect layer times [DWC]
-
The print finished and the final layer count on the blue progress bar was 115/114. I believe the correct layer count should be 164 however. I'll attach the gcode file so you can verify/experiment.
gcode -
@nxt-1 You say you are using KISSlicer and there is one part in the source code of RepRapFirmware regarding print monitor that explicitly mentions KISSlicer and issues with layer height IIRC. Do you have
M404(https://duet3d.dozuki.com/Wiki/Gcode?revisionid=HEAD#Section_M404_Filament_width_and_nozzle_diameter) in yourconfig.g? The values of this command are used in that case to correctly calculate print progress.Manuel
Duet 3 6HC (v0.6) with RPi 4B on a custom Cartesian
with probably always latest firmware/DWC (incl. betas or self-compiled)
My Tool Collection -
@wilriker said in Incorrect layer times [DWC]:
@nxt-1 You say you are using KISSlicer and there is one part in the source code of RepRapFirmware regarding print monitor that explicitly mentions KISSlicer and issues with layer height IIRC. Do you have
M404(https://duet3d.dozuki.com/Wiki/Gcode?revisionid=HEAD#Section_M404_Filament_width_and_nozzle_diameter) in yourconfig.g? The values of this command are used in that case to correctly calculate print progress.I've never head of issues with KISSlicer, I'd love to hear what @dc42 has to say about this. I currently do not have a M404 in my config.g, I'll add that for future prints.
-
M404 is not normally needed.
The graph shows that about 2 out of every 3 layers took about 35sec and 1 in 3 took zero time until near the end. Is the GCode file using variable layer height?
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@nxt-1 said in Incorrect layer times [DWC]:
I've never head of issues with KISSlicer, I'd love to hear what @dc42 has to say about this.
Just looked it up again and it was not about layer height but older KISSlicer versions do not add info about filament length but only volume and the value of
M404 Nnnnis used to calculate that back into a length. Sorry, my fault. Did not remember correctly. -
@dc42 said in Incorrect layer times [DWC]:
M404 is not normally needed.
The graph shows that about 2 out of every 3 layers took about 35sec and 1 in 3 took zero time until near the end. Is the GCode file using variable layer height?
Yes, adaptive layer height is used.
-
I still have problems with estimated Print time ans layer time...sometimes all work as intended and on other prints he not count the layertimes and all is messed up..all with the same profile from S3D..very annoying
-
@nxt-1 said in Incorrect layer times [DWC]:
@dc42 said in Incorrect layer times [DWC]:
M404 is not normally needed.
The graph shows that about 2 out of every 3 layers took about 35sec and 1 in 3 took zero time until near the end. Is the GCode file using variable layer height?
Yes, adaptive layer height is used.
I think that explains it. The layer count mechanism in the firmware assumes that all layers except the first are the same height.
-
@barracuda72 said in Incorrect layer times [DWC]:
I still have problems with estimated Print time ans layer time...sometimes all work as intended and on other prints he not count the layertimes and all is messed up..all with the same profile from S3D..very annoying
The layer time is usually the least accurate estimate. The estimate based on filament usage is usually the best.
-
yes..but theres no layertime at all..first layertime was 37sec...and now my print is at the 2nd layer till 1h 12m so its count only 2 layers.
And that problem i have from time to time..
