Cura slicer: Layer count when print sequence is "Once at a Time"



  • Dear community and administration!

    I'm using only Cura slicer and there is a bug, when selected "Special Modes" / "Print Sequence" = "Once at a Time".
    Two screenshots: DWC and Cura.
    You can see 5 details, in first will be printed bottom row from right to left (the same details with max height eq. 5 mm, 25 layers), then (last) upper frame (height is 3 mm, 15 layers).

    DWC reports me, that there is only 15 layers and 3mm height, as for last detail. So, while printing, I've got "Layer: 25 of 15" (because first detail has 25 layers) and last value of "Current Layer Time" will count up to the end of file (real last layer).

    I've tried to edit g-code file (edit first ";LAYER_COUNT:" and delete others, renumber all layers at ";LAYER:"), but no - looks like DWC determine number of layers in other way - change of Z value.

    I think, that DWC g-code parser should enumerate not only positive Z change, but all Z changes. What do you think?

    PS I've searched for the same problem here, but looks like nobody use "Once at a Time".



  • Hi everyone!
    No ideas about this? Maybe mr. @dc42 could give any comments?
    Mostly, I'm interested in how DWC determines layer quantity.


  • administrators

    @AfanasevSA said in Cura slicer: Layer count when print sequence is "Once at a Time":

    I've tried to edit g-code file (edit first ";LAYER_COUNT:" and delete others, renumber all layers at ";LAYER:"), but no - looks like DWC determine number of layers in other way - change of Z value.

    That's right the firmware looks at Z moves near the end of the file to determine the object height, and calculates the layer height form that. But in future I plan to make use of layer comments, when they are present.

    I think, that DWC g-code parser should enumerate not only positive Z change, but all Z changes. What do you think?

    That may cause problems when users put tool change scripts or tool offsets in the slicer, because then the slicer will generate negative Z movements. So I think the current plan to use the layer height comments is better.



  • @dc42 thanks for your answer.
    Are layer comments the same for every slicer?
    Could you answer two more questions, please:

    1. How DWC determines layer change?
    2. If I'll place any G-command (one or block of commands) with summary Z, DWC will take it, divide per layer height, then show me correct info? You wrote, that it looks for Z moves , so, it looks like "last Z" minus "pre-last Z" = "layer height" for DWC, then "last Z" / "layer height" = "layer quantity"?