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

    Duet 2 v1.04c to v1.06 swap issues

    Scheduled Pinned Locked Moved Unsolved
    Duet Hardware and wiring
    3
    9
    344
    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.
    • la_rdundefined
      la_rd
      last edited by

      The SD card slot on my Duet 2 wifi (revision 1.04c) seemingly failed after a few years, so I purchased a new duet 2 ethernet (revision 1.06). Swapped out the board, and kept the connections identical from before. Now when I try to home any of the axes, I get the message:

      Warning: Driver 1 warning: phase A may be disconnected, phase B may be disconnected
      

      The 3-D printer is a Voron 2.4, and I have a connected duex for the Z-axis. How can I fix this? Were the motor phases changed between board revisions?

      Thanks for the help.

      1 Reply Last reply Reply Quote 0
      • la_rdundefined
        la_rd
        last edited by

        config.g

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

          Double check the crimps and connection. Try moving another motor to that driver and remapping and see if it still follows.

          Z-Bot CoreXY Build | Thingiverse Profile

          la_rdundefined 1 Reply Last reply Reply Quote 0
          • la_rdundefined
            la_rd @Phaedrux
            last edited by

            @Phaedrux I have double checked the crimps and connection. After remapping to driver 4. The warning, as before showed up. This time I also saw both the A and B motor drivers warnings.

            Warning: Driver 0 warning: phase A may be disconnected, phase B may be disconnected
            Warning: Driver 4 warning: phase A may be disconnected, phase B may be disconnected
            
            Phaedruxundefined 1 Reply Last reply Reply Quote 0
            • Phaedruxundefined
              Phaedrux Moderator @la_rd
              last edited by

              @la_rd said in Duet 2 v1.04c to v1.06 swap issues:

              After remapping to driver 4.

              How did you change the wiring and mapping exactly? Before it was driver 1 and now it's 0 and 4?

              If it was a problem with the driver itself the error would stick with the driver, but it seems to be following the motor?

              Z-Bot CoreXY Build | Thingiverse Profile

              la_rdundefined 1 Reply Last reply Reply Quote 0
              • la_rdundefined
                la_rd @Phaedrux
                last edited by

                @Phaedrux Hello, it is more like this issue:
                All drivers, including the Z-drivers on the Duex have been outputting this errors. It was fine before on my other duet2. M906 and M913 show that the proper current is allegedly outputting.
                Screenshot 2023-10-01 at 10.31.06 PM.png

                When I try to home XY the AB motors error Screenshot 2023-10-01 at 10.32.43 PM.png

                And when I try to home the Z axis the Z-axis motors error.
                Screenshot 2023-10-01 at 10.34.04 PM.png

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

                  @la_rd which firmware version?

                  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

                  la_rdundefined 1 Reply Last reply Reply Quote 0
                  • Phaedruxundefined Phaedrux marked this topic as a question
                  • la_rdundefined
                    la_rd @dc42
                    last edited by

                    @dc42 the latest release: 3.4.6
                    I tried erasing with the jumper and fresh re-installing the firmware via SAMBa last night, to still receive the same errors.

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

                      Can you also try disconnecting the Duex? Do you also get the same errors? Can you send the output of M122? With and without the Duex?

                      Z-Bot CoreXY Build | Thingiverse Profile

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