Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login

    Layer chart not updating in 3.2

    Scheduled Pinned Locked Moved Unsolved
    Duet Web Control
    5
    14
    769
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Phaedruxundefined
      Phaedrux Moderator
      last edited by

      Can you confirm that you have DWC 3.2 installed?
      Can you provide the output of M115 to confirm the firmware version?
      Can you also provide a sample gcode file?

      Z-Bot CoreXY Build | Thingiverse Profile

      1 Reply Last reply Reply Quote 0
      • Jobie52undefined
        Jobie52
        last edited by

        Herewith screenshots and code.

        DWC.JPG M115.JPG camera adapter.gcode

        1 Reply Last reply Reply Quote 0
        • Phaedruxundefined
          Phaedrux Moderator
          last edited by

          I don't see any obvious reason in the gcode example why it wouldn't show the layers. Sometimes having some Z moves in the start and end gcode can throw it off, but you don't have anything odd.

          Z-Bot CoreXY Build | Thingiverse Profile

          1 Reply Last reply Reply Quote 0
          • Jobie52undefined
            Jobie52
            last edited by

            Thanks for looking at my problem.
            I just noticed that the job information box has the layer height at "0.00mm". Where does DWC get this info from?Layer.JPG

            The last 13 hour print I did the chart did not update at all.

            1 Reply Last reply Reply Quote 0
            • Vetiundefined
              Veti @Jobie52
              last edited by

              @Jobie52 said in Layer chart not updating in 3.2:

              Slic3r 1.3.0

              maybe its time to update to prusaslicer 2.3 ?

              Jobie52undefined 1 Reply Last reply Reply Quote 0
              • matt3oundefined
                matt3o
                last edited by

                does reprapfirmware rely on the slicer to output some code/comment on layer change?

                Vetiundefined 1 Reply Last reply Reply Quote 0
                • Vetiundefined
                  Veti @matt3o
                  last edited by

                  @matt3o said in Layer chart not updating in 3.2:

                  does reprapfirmware rely on the slicer to output some code/comment on layer change?

                  yes as far as i understand it.
                  how else would it identify the slicer that sliced the g code?

                  matt3oundefined 1 Reply Last reply Reply Quote 0
                  • matt3oundefined
                    matt3o @Veti
                    last edited by

                    @Veti said in Layer chart not updating in 3.2:

                    @matt3o said in Layer chart not updating in 3.2:

                    yes as far as i understand it.
                    how else would it identify the slicer that sliced the g code?

                    yeah I get that it reads the comment for cosmetic reasons (slicer name, estimated total print time), but I didn't realize that it relies on some comments for functional reasons (even those the I guess the graph is still cosmetic).

                    I don't remember if Slic3r supports variables, if so @Jobie52 you may try to add

                    ;LAYER:X
                    

                    at each layer change, where X is the current layer

                    1 Reply Last reply Reply Quote 0
                    • tooundefined
                      too
                      last edited by too

                      We see the same issue on Duet2 with latest firmware installed, Layer time is not updating.
                      The gcode we tested definitely worked previously.

                      @Veti said in Layer chart not updating in 3.2:

                      how else would it identify the slicer that sliced the g code?

                      I think if you have lines like ; layer 42 in your gcode the duet uses this as indicator for layer change.

                      Cartesian Duet3+Raspberry pi 4 with 5x 1XD using servo drives printing mortars and concrete

                      1 Reply Last reply Reply Quote 0
                      • Jobie52undefined
                        Jobie52
                        last edited by

                        Ok, now I am flummoxed, restarted Repetier host and sliced a new part using slic3r, now the layer chart is working! The job information box now has the correct information.

                        @matt3o - the coded generated already has a comment " ;layer_height = 0.3" this comment was also present in the "non working" code.

                        Thanks for all the comments.!Job.JPG

                        matt3oundefined 1 Reply Last reply Reply Quote 0
                        • matt3oundefined
                          matt3o @Jobie52
                          last edited by

                          @Jobie52 said in Layer chart not updating in 3.2:

                          the coded generated already has a comment " ;layer_height = 0.3"

                          you need the layer number for each layer (not just the layer height)... but anyway it works now, so everything's fine 🙂

                          1 Reply Last reply Reply Quote 0
                          • Jobie52undefined
                            Jobie52 @Veti
                            last edited by

                            @Veti said in Layer chart not updating in 3.2:

                            @Jobie52 said in Layer chart not updating in 3.2:

                            Slic3r 1.3.0

                            maybe its time to update to prusaslicer 2.3 ?

                            Thanks, will do

                            1 Reply Last reply Reply Quote 0
                            • Jobie52undefined
                              Jobie52
                              last edited by

                              Guess I spoke too soon. Problem still persist. I have updated to PrusaSlicer 2.3 as suggested by @Veti. No difference I cannot understand why it worked in firmware version 2 and not in 3.

                              Oh well, have to live with it.

                              1 Reply Last reply Reply Quote 0
                              • First post
                                Last post
                              Unless otherwise noted, all forum content is licensed under CC-BY-SA