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

    Software version 3.5.0-rc.3 released

    Scheduled Pinned Locked Moved
    Beta Firmware
    3
    4
    613
    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.
    • chrishammundefined
      chrishamm administrators
      last edited by

      On behalf of the Duet3D team I am pleased to announce the availability of the third release candiate for v3.5.0. Please consider testing this build as it is very likely the last candidate before the final release of stable version 3.5.

      Highlights of this particular versions include:

      • Improvements in the Ethernet backend of RepRapFirmware
      • Increase of free RAM on the Duet 2 series
      • Added DSF support for Debian Bookworm (latest RPi OS version)
      • Various bug fixes

      Please read the upgrade notes to avoid potential issues on upgrade:

      • RepRapFirmware
      • DuetWebControl
      • DuetSoftwareFramework

      Users in standalone mode can obtain the latest version from here. Users running in SBC mode can update using the apt update/apt upgrade appraoach as usual.

      If you encounter any more issues, please open a new thread starting with [3.5.0-rc.3] in the title.

      PS: A new experimental Bookworm-based DuetPi image will follow very soon. This version will provide automatic online upgrades for DSF/RRF via M997 S2 as well.

      Duet software engineer

      jens55undefined paralepsisundefined 2 Replies Last reply Reply Quote 4
      • chrishammundefined chrishamm pinned this topic
      • droftartsundefined droftarts referenced this topic
      • jens55undefined
        jens55 @chrishamm
        last edited by jens55

        @chrishamm, the release notes for RRF say:

        [Duet 2] [Duet Maestro] The number of HTTP responders has been reduced from 4 to 3. This should not matter unless you have HTTP connections to the Duet open on several PCs or in several browser tabs, or you upload files from two or more PCs or browser tabs concurrently.

        I regularly use/monitor/operate my Duet2 based printers from two different computers. The tabs are always open. On occasion I might have an additional instance/tab open. I only interact with the Duet2 from one computer at a time. Each browser tab can have a web video stream running in it to monitor print progress.

        Can you tell me if the change of HTTP responders has any effect on my current way of using the web connection? Do I need to change anything in my procedures? If I went to three different computers, would things still work? What would I see or what would happen if I ran into a problem with this?

        chrishammundefined 1 Reply Last reply Reply Quote 0
        • chrishammundefined
          chrishamm administrators @jens55
          last edited by

          @jens55 You may get connection aborts if all responders are busy and the sockets can't queue any more incoming connections. If you do, please report back.

          Duet software engineer

          1 Reply Last reply Reply Quote 0
          • paralepsisundefined
            paralepsis @chrishamm
            last edited by paralepsis

            @chrishamm FWIW, working fine on my RailCore with PA and IS. Printed 10-15 hours so far. Heightmap when skipping points still looks funny :).

            Edit: I'm running standalone mode.

            Railcore II 300XL w/ Duet 3 & RRF 3.5rc4, Makerbot R2X w/ Duet 2 WiFi & RRF 3.4

            1 Reply Last reply Reply Quote 2
            • chrishammundefined chrishamm unpinned this topic
            • First post
              Last post
            Unless otherwise noted, all forum content is licensed under CC-BY-SA