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

    Duet 3 Expansion 3HC sensorless homing via CAN

    Scheduled Pinned Locked Moved
    General Discussion
    7
    29
    1.1k
    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.
    • T3P3Tonyundefined
      T3P3Tony administrators @Cognirit
      last edited by T3P3Tony

      @Cognirit thanks for the kind words!

      www.duet3d.com

      1 Reply Last reply Reply Quote 0
      • tru_annundefined
        tru_ann @T3P3Tony
        last edited by

        @T3P3Tony @dc42 Glad to hear this!
        I'm relatively new to your platform, but it's nice how customizable it is and how responsive the developers are.

        1 Reply Last reply Reply Quote 0
        • tru_annundefined
          tru_ann
          last edited by

          @dc42 @T3P3Tony Hello! We installed firmware 3.6 beta3 and tested sensorless homing on the Duet3 3HC board. Individually all Z-axes perform homing without problems. However, when we tried to run homing with independent stopping (M574 Z2 S4) the system worked the same way as with S3 mode: when the first axis reached the end, all axes stopped. We tried running homing with the same settings, connecting the motors to the Duet3 6HC main board and it worked as it should: each motor stopped at the correct time. Is it possible that this is another unresolved problem with the Duet3HC Expansion board? I am attaching our configuration files. Thanks!
          homez.g
          config.g

          T3P3Tonyundefined dc42undefined 3 Replies Last reply Reply Quote 1
          • T3P3Tonyundefined
            T3P3Tony administrators @tru_ann
            last edited by

            @tru_ann thanks for testing and reporting this, we will investigate further

            www.duet3d.com

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

              @tru_ann I confirm this is a bug and I am looking into it.

              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
              • dc42undefined
                dc42 administrators @tru_ann
                last edited by

                @tru_ann this is now fixed in the source code. The fix will be in a new 3.6 beta, RC or internal build soon.

                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

                tru_annundefined 1 Reply Last reply Reply Quote 0
                • tru_annundefined
                  tru_ann @dc42
                  last edited by

                  @dc42 @T3P3Tony Thank you! It's nice that the problem was fixed so quickly!

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

                    @tru_ann there are now unofficial 3.6.0-beta.3+4 builds containing the fix available at https://www.dropbox.com/scl/fo/wyqfqmzj0v7otx6wzqfdl/AJXLaai4nWowqfLtA4gePUk?rlkey=jpyla60xf2tqql0h4nx4sn9yv&dl=0

                    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

                    tru_annundefined 1 Reply Last reply Reply Quote 0
                    • tru_annundefined
                      tru_ann @dc42
                      last edited by

                      @dc42 Thank you very much! We successfully implemented unofficial 3.6.0-beta.3+4 build.The functionality we are interested in, including independent homing in S4 mode when connected to Duet3HC, works fine with it. We have not found for any other bugs, because we didn't do a full test. If we find any, we will write to you.
                      We are very satisfied with the use of sensorless homing for the Z axes, as it allows us to completely get rid of the end stops. We have been using this functionality for a long time in our previous 3D printers and have now implemented it in the new one. We would like to share our experience with those who may also be interested in this option, so that it is easier for them to configure and try it out. We attach a video of how the system works as well as our config files.
                      Triple Z axis sensorless homing.mp4
                      config.g
                      homex.g, homey.g, homez.g

                      dc42undefined droftartsundefined 2 Replies Last reply Reply Quote 1
                      • dc42undefined
                        dc42 administrators @tru_ann
                        last edited by

                        @tru_ann I'm glad it's working for you. We've released 3.6.0-beta.4 now.

                        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
                        • droftartsundefined
                          droftarts administrators @tru_ann
                          last edited by

                          @tru_ann Are your Z axes belt or leadscrews? As noted here https://docs.duet3d.com/en/User_manual/Connecting_hardware/Sensors_stall_detection#limitations-of-stall-detection, stall homing is not as precise or repeatable as endstops or probes:

                          The stepper drivers only update the stall detection state every 1 or 4 full steps, depending on configuration. So the actual position of the stall is uncertain to either +/- half a full step or +/- 2 full steps. This means that when using stall detection to replace endstop switches, the position defined by the stall is much less accurate than with typical endstop switches.

                          Ian

                          Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

                          tru_annundefined 1 Reply Last reply Reply Quote 0
                          • tru_annundefined
                            tru_ann @droftarts
                            last edited by

                            @droftarts Leadscrews. If you're interested, we've attached a video in the post above.

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