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

    Duet2D PCB Variations

    Scheduled Pinned Locked Moved
    Duet Hardware and wiring
    3
    6
    241
    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.
    • MightyMaestroundefined
      MightyMaestro
      last edited by

      I have two large 3D printers with Duet2D controller and Duex5 driver boards. The machines have been verified numerous time to be identical, however, I receive "G28 Failed to Enable Endstops" on one, while the other works perfectly. Switching the boards creates more confusion, but suffice to say that switching both boards does not switch the problem. I have purchased and replaced both boards on the faulty machine.

      The (only) difference is: The good machine has Duet2D (1.04C) and Duex5 (0.9A) PCBs, while the faulty machine has Duet2D (1.05) and Duex5 (0.10) PCB's. So.... What is the difference between these versions of boards? And how do I get the newer boards to function?

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

        @mightymaestro said in Duet2D PCB Variations:

        G28 Failed to Enable Endstops

        Probably means you have a homing move in your homing files that uses an endstop that doesn't actually exist.

        If you post your config.g and homing files from the Duet in question we would have a better idea.

        Functionally there is no real difference between the PCB revisions.

        Z-Bot CoreXY Build | Thingiverse Profile

        1 Reply Last reply Reply Quote 0
        • MightyMaestroundefined
          MightyMaestro
          last edited by

          I'd like to agree with you, but the SD cards are identical (one cloned from the other) yet the first configuration (Duet2D (1.04C) and Duex5 (0.9A)) does not cause this problem, but the other configuration does.

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

            Post your config.g and homing files and the results of sending M122 and M98 P"config.g" in the gcode console in DWC.

            Z-Bot CoreXY Build | Thingiverse Profile

            1 Reply Last reply Reply Quote 0
            • MightyMaestroundefined
              MightyMaestro
              last edited by

              Hi Everyone.
              Solved the problem. It came down to firmware on the Duet2D board. The system that was working was running 2.05.1 firmware, while the new board causing the drama had 3.4.X.
              In summary, the new board firmware killed my printers.

              elmoretundefined 1 Reply Last reply Reply Quote 0
              • elmoretundefined
                elmoret @MightyMaestro
                last edited by elmoret

                RRF2 and RRF3 are quite different, config files need to be updated accordingly.

                https://docs.duet3d.com/User_manual/RepRapFirmware/Migration_RRF2_to_RRF3

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