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

    Inconsistent delays during homing and other movements

    Scheduled Pinned Locked Moved
    General Discussion
    5
    38
    4.3k
    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.
    • synfinaticundefined
      synfinatic @dc42
      last edited by

      @dc42 Connections are solid. Using ferrules on the Duet/Deux5 side and spade connectors on the power supply end. Wire is 13AWG silicone wire. Here's the wiring:
      alt text

      1 Reply Last reply Reply Quote 1
      • elmoretundefined
        elmoret
        last edited by

        Not convinced that this is the cause of your issues, but note that your grounding configuration is in express violation of the recommendations in the documentation.

        synfinaticundefined 1 Reply Last reply Reply Quote 0
        • synfinaticundefined
          synfinatic @elmoret
          last edited by synfinatic

          @elmoret You're right. I miss-read the docs. What is the proper way? With the ferrules, I can't daisy-chain the grounds can I? Am I supposed to splice the wires together (solder & heat shrink?). Smaller wires and run two wires into the same ferrule?

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

            Some of the ferrules we normally supply have wider, almost rectangular inlets, designed to accept two cables. Did you not receive any of those? I'll post a photo when I am in the office.

            Edit: here is the photo.

            alt text

            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

            synfinaticundefined 1 Reply Last reply Reply Quote 0
            • synfinaticundefined
              synfinatic @dc42
              last edited by

              @dc42 So I do have those, but they're too small for a single 13AWG wire I've been using for power, let alone two of them, so I used my own. The next smallest size wire I know I have is 20. Might have some 18 lurking around. What size wire is acceptable/is it designed for?

              1 Reply Last reply Reply Quote 1
              • synfinaticundefined
                synfinatic
                last edited by

                So I rewired the ground for the Duet/Duex5 to be per the instructions. The 20AWG wire was IMHO a bit too thin so I spliced the ground together. Basically, the two boards are connected via a single 13AWG wire and then I soldered in another 13AWG wire to connect to the power supply at a single point. I measured the resistance between the 3 connectors to verify a good connection and added some strain relief.

                TL;DR: It follows the same pattern. Was able to home a couple of times and run the mesh bed scan via the PanelDue without problems, but I couldn't even get to homing the Y axis the first time without tripping the 20sec delay using DWC.

                Any other suggestions/ideas?

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

                  OK, I'm running out of ideas. Please ask Tim to exchange your Duet.

                  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
                  • synfinaticundefined
                    synfinatic
                    last edited by

                    Thanks David. I'll reach out to Tim.

                    1 Reply Last reply Reply Quote 0
                    • synfinaticundefined
                      synfinatic
                      last edited by

                      Just a quick followup. Was able to RMA both boards and finally found the time to install them and test again. Made sure to use the latest stable releases for both firmware and DWC. All my problems seem to have been resolved. 🙂

                      Thanks to everyone for their help!

                      1 Reply Last reply Reply Quote 2
                      • Jeremy Watkinsundefined
                        Jeremy Watkins
                        last edited by

                        I just started setting up a Cartesian and I am experiencing a very similar issue. When I home all, the board immediately homes the x and y axis. However, the z axis doesn't home until around 60 seconds later. This doesn't happen if I home the z, x, and y independently.

                        Here is my homeall.g

                        ; homeall.g
                        ; called to home all axes
                        ;
                        ; generated by RepRapFirmware Configuration Tool on Wed Sep 26 2018 00:09:26 GMT-0400 (Eastern Daylight Time)
                        G91 ; relative positioning
                        G1 Z5 F6000 S2 ; lift Z relative to current position
                        G1 S1 X207 Y-215 F1800 ; move quickly to X and Y axis endstops and stop there (first pass)
                        G1 X-5 Y5 F6000 ; go back a few mm
                        G1 S1 X-07 Y-215 F360 ; move slowly to X and Y axis endstops once more (second pass)
                        G1 S1 Z-150 F1800 ; move Z down stopping at the endstop
                        G90 ; absolute positioning
                        G92 Z.2 ; set Z to axis minimum (you may want to adjust this)

                        ; Uncomment the following lines to lift Z after probing
                        G91 ; relative positioning
                        G1 S2 Z5 F100 ; lift Z relative to current position
                        G90 ; absolute positioning

                        Jeremy Watkinsundefined 1 Reply Last reply Reply Quote 0
                        • Jeremy Watkinsundefined
                          Jeremy Watkins @Jeremy Watkins
                          last edited by

                          @jeremy-watkins I just caught my mistake. Clearly, I didn't have enough sleep to see it last night, but my 5th line of code has X-07 instead of X207. Changing it resolved all my issues.

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