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

    Archive of release candidates

    Scheduled Pinned Locked Moved Solved
    Firmware installation
    3
    4
    168
    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.
    • cbusilloundefined
      cbusillo
      last edited by

      Hi all. Is there an archive of release candidates anywhere? It looks like they have been removed from GitHub. I am specifically looking for 3.2-RC2. That seems to be the last version of the firmware that worked for me without layer shifting. I am trying to load that firmware again to compare to 3.2 and newer to see if the shifting goes away. I have two boards and both have this issue. Before I updated the second one from 3.2-RC2 to the latest, it worked perfectly. Thanks all! Hopefully I can figure out what I am doing wrong and get this fixed.

      chrishammundefined dc42undefined 2 Replies Last reply Reply Quote 0
      • chrishammundefined
        chrishamm administrators @cbusillo
        last edited by

        @cbusillo Only here: https://github.com/Duet3D/RepRapFirmware/releases

        Duet software engineer

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

          @cbusillo we remove unsupported releases (i.e. betas and release candidates) when the corresponding stable release has been out for a while. However, the tags for them are still present in Github so it is possible to build them from the source code.

          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

          cbusilloundefined 1 Reply Last reply Reply Quote 0
          • cbusilloundefined
            cbusillo @dc42
            last edited by

            Thank you both! It turned out to be the change in the M593, input shaping. The discord helped me figure that one out. I didn't realize the old algorithm was not in the new firmware. I have an accelerometer coming so I can really tune it now. thank you both for the great hardware/software.

            1 Reply Last reply Reply Quote 0
            • cbusilloundefined cbusillo marked this topic as a question
            • cbusilloundefined cbusillo has marked this topic as solved
            • First post
              Last post
            Unless otherwise noted, all forum content is licensed under CC-BY-SA