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

    Z-offset calibration

    Scheduled Pinned Locked Moved
    General Discussion
    3
    11
    1.7k
    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.
    • Max Arnoldundefined
      Max Arnold
      last edited by

      Hello DC42,

      we met at the TCT Show and it was a pleasure talking to you.
      We talked about a automatic z-offset calibration method, when one has 2 or more Hotends.
      Would it be possible to integrate a automatic z-offset calibration, when using a direct contact probe into the firmware?
      So I have 4 Hotends and I would like to have command where the same position is probed by all four Hotends and such the z-offset is determined.

      Thank you in advance for your reply.

      Kind Regards

      Max

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

        I think we could make G30 S-2 probe the bed and adjust the Z offset of the current tool by the difference between the configured trigger height and the recorded height when the probe triggers. Would that meet your requirement?

        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 1
        • Max Arnoldundefined
          Max Arnold
          last edited by

          Hello DC42,

          yes that would meet my requirements. Is it then possible to to store that z-offset value in G10 in the config.g file ?
          Thanks again for your fast response.

          1 Reply Last reply Reply Quote 0
          • Max Arnoldundefined
            Max Arnold
            last edited by

            I am not sure how or where the Z-offset is stored, but it is only stored temporarily. This means after a restart, the values are lost, so my guess is that the offset is stored in the flash memory. Would it be possible to store the value permanently in the G10 command in the config file?

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

              In firmware 1.20 any tool offsets that were found by probing are written to config-override.g when you run M500.

              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 1
              • Max Arnoldundefined
                Max Arnold
                last edited by

                Thank you. This solved my problem

                1 Reply Last reply Reply Quote 0
                • stephencundefined
                  stephenc
                  last edited by

                  Hi max I'm curious how your printer setup with 4 different heads. can you share your build?

                  Thanks
                  Stephen

                  Stephen
                  https://github.com/stephenci/ZideX

                  1 Reply Last reply Reply Quote 0
                  • stephencundefined
                    stephenc
                    last edited by

                    Id like to see wiki covering this feature.

                    So if those z offsets is then saved in G10 does that mean probing all 4 hotends can only by done once and your routine for every print would be to probe only yiur primary hotend?

                    Thanks
                    Stephen

                    Stephen
                    https://github.com/stephenci/ZideX

                    1 Reply Last reply Reply Quote 0
                    • Max Arnoldundefined
                      Max Arnold
                      last edited by

                      Hello StephenC,

                      I am very sorry for the late reply. Concering your last post, yes exactly that is true. I will share my build soon. Currently ironing out some issues.

                      Meanwhile DC42 I found a flaw with the z-offset of two nozzles or more. When swichting between the hotends the z-offset does not take affect until the next move which means that the when the printhead moves the z-offset is gradually adjusted. Is it possible to have to have some kind of command that would trigger the z-offset adjustment earlier,so that i can implement it in the tpost script?

                      Thanks.

                      Max

                      1 Reply Last reply Reply Quote 0
                      • Max Arnoldundefined
                        Max Arnold
                        last edited by

                        Well I found a work around. One can lower the bed using relative positioning (G91) and the when the printhead moves the z-height is adjusted again with the z-offset.

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

                          @max-arnold said in Z-offset calibration:

                          Well I found a work around. One can lower the bed using relative positioning (G91) and the when the printhead moves the z-height is adjusted again with the z-offset.

                          That is exactly what I would suggest. Even a no-motion command such as G1 Z0 (after G91) should suffice.

                          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 1
                          • First post
                            Last post
                          Unless otherwise noted, all forum content is licensed under CC-BY-SA