Incorrect layer times [DWC]

Nxt-1

@dc42 The same issue is comming up as I am printing right now. I will let you know whether the final layer count is correct. Although KISSlicer doesn't seem to output the number of layers
If there is anything else you need in terms of diagnostics, now would be the time to say it.

Nxt-1

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

wilriker

@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 your config.g? The values of this command are used in that case to correctly calculate print progress.

Nxt-1

@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 your config.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.

dc42

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?

wilriker

@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 Nnnn is used to calculate that back into a length. Sorry, my fault. Did not remember correctly.

Nxt-1

@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.

Barracuda72

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

dc42

@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.

dc42

@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.

Barracuda72

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..