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

    New beta firmware 1.20beta11

    Scheduled Pinned Locked Moved
    Firmware installation
    10
    29
    3.9k
    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.
    • dc42undefined
      dc42 administrators
      last edited by

      @k3lag:

      I noticed on beta10 (although I thought I was crazy) and now on beta11 that the layer count is wrong. It is off by 2. For a print 50 layers high, it will finish on layer 52. Right now I am printing the first layer of a print and duet web control says it is on layer 3.

      I'm pretty sure it wasn't like this before the last beta or two.

      Larry

      Thanks for the report, I'll check it out.

      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

      1 Reply Last reply Reply Quote 0
      • k3lagundefined
        k3lag
        last edited by

        @dc42:

        @k3lag:

        I noticed on beta10 (although I thought I was crazy) and now on beta11 that the layer count is wrong. It is off by 2. For a print 50 layers high, it will finish on layer 52. Right now I am printing the first layer of a print and duet web control says it is on layer 3.

        I'm pretty sure it wasn't like this before the last beta or two.

        Larry

        Thanks for the report, I'll check it out.

        I figured out why it's doing it. I had a fair bit of baby stepping dialed in and it must be taking that into account when it determines what layer it's on. I reconfigured my probe height and turned off the baby stepping and it's back to normal.

        I had made other changes to the printer the same time I upgraded the firmware and was too lazy to go in and update the probe height in config.g.

        Larry

        1 Reply Last reply Reply Quote 0
        • dc42undefined
          dc42 administrators
          last edited by

          Thanks for the update. It sounds like I should subtract the babystepping in the layer height computation.

          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

          1 Reply Last reply Reply Quote 0
          • deckingmanundefined
            deckingman
            last edited by

            @dc42:

            Thanks for the update. It sounds like I should subtract the babystepping in the layer height computation.

            I could be wrong (I usually am) but I have a sneaky feeling that DWC updates the number of layers completed every time it sees a Z move. So it counts a babystep as a layer completed. At least that is the behaviour that I thought I had observed but it was a long time, and probably a few versions of DWC ago.

            Ian
            https://somei3deas.wordpress.com/
            https://www.youtube.com/@deckingman

            1 Reply Last reply Reply Quote 0
            • mchiriciucundefined
              mchiriciuc
              last edited by

              I noticed that babystepping is also added to auto bed compensation values. It drowe me nuts, I thought that something is wrong with my frame :))

              1 Reply Last reply Reply Quote 0
              • mchiriciucundefined
                mchiriciuc
                last edited by

                Regarding bad layer count in interface, my current print has 191 layeys, and the interface shows me that the total number of layers is 969…. It may be that is also counting Z lifts during retracts as layers?

                1 Reply Last reply Reply Quote 0
                • dc42undefined
                  dc42 administrators
                  last edited by

                  It works out the number of layers from the object height and the layer height. Is the object height also shown incorrectly?

                  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

                  1 Reply Last reply Reply Quote 0
                  • mchiriciucundefined
                    mchiriciuc
                    last edited by

                    Yes. Current object 22mm height, reported as 310mm. Layer height is correct though, 0.34mm.
                    Got it!
                    My ending code does a G0 Z310 to lower the table (cube design printer). This is where the 310 value comes…
                    I have no idea how to work around this. Any suggestion (good as always)?

                    1 Reply Last reply Reply Quote 0
                    • dc42undefined
                      dc42 administrators
                      last edited by

                      At the end of the G0 Z310 line, add a comment beginning with ";E" or "; E".

                      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

                      1 Reply Last reply Reply Quote 0
                      • mchiriciucundefined
                        mchiriciuc
                        last edited by

                        That did the trick. Thank you!

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