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

    Software bundle 3.3RC3 now available

    Scheduled Pinned Locked Moved
    Beta Firmware
    15
    37
    3.0k
    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.
    • dc42undefined
      dc42 administrators
      last edited by dc42

      On behalf of the Duet3D team I am pleased to announce the release of firmware bundle 3.3RC3. This releases fixes bugs in 3.3RC2. Here are the links to the upgrade notes and change lists:

      RRF: https://github.com/Duet3D/RepRapFirmware/wiki/Changelog-RRF-3.x-Beta-&-RC#reprapfirmware-33rc3
      DWC: https://github.com/Duet3D/DuetWebControl/blob/v3.3-dev/WHATS_NEW.md
      DSF: https://github.com/Duet3D/DuetSoftwareFramework/blob/v3.3-dev/WHATS_NEW.md

      Users of Duet in standalone mode should use the files at https://github.com/Duet3D/RepRapFirmware/releases/tag/3.3RC3.

      Users of Duet in SBC mode should upgrade from the unstable feed of the Duet3D package server.

      If this release works well for you, or you encounter only minor issues that do not require a response, please post a short message in this thread. If you encounter more serious issues with this release, please start a new thread to describe the issue and include "[3.3RC3]" in the topic name.

      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

      tecnoundefined EducatingSavvasundefined 2 Replies Last reply Reply Quote 4
      • apakundefined
        apak
        last edited by

        updating from 3.3RC2

        just noted that firmware file uploaded to a new firmware folder

        As the new folder was just created, it had no IAP file....upload the IAP file that went also to the new firmware folder.

        Reloader again the fw file and this time upgraded fine...

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

          @apak I'm surprised the folder didn't already exists seeing that you were on RC2 already.

          Z-Bot CoreXY Build | Thingiverse Profile

          apakundefined 1 Reply Last reply Reply Quote 0
          • apakundefined
            apak @Phaedrux
            last edited by

            @phaedrux probably existed, but last update to rc2 was "normal", and I got me this time the mod.

            I like it better this way, so config is isolated from fw files

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

              @apak this is to be expected the second time you install a 3.3 series release. The first time, your old 3.2 firmware is using /sys to hold firmware and IAP files, so the firmware file goes into /sys and the upgrade works. When you next upgrade, RRF 3.3 looks in /firmware for those files. So if you upload just the binary and not the IAP file too, there will be no IAP file in /firmware yet.

              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
              • DaveAundefined
                DaveA
                last edited by

                I don't see any firmware for the Duet Maestro?

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

                  Oops, I missed that one! Now added.

                  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 1
                  • makemerushundefined
                    makemerush
                    last edited by

                    I was on 3.3RC1, then RC2, then RC2+3 and didn't have any issues.

                    After updating to 3.3RC3 the wifi module isn't connecting. On my paneldue the screen says "wifi module is idle" and the console says "WiFi reported error: Failed while trying to connect to my network SSID" and "WiFi reported error: network scan failed".

                    Did this update include any changes that could affect wifi?

                    My board is a Duet2WiFi.

                    Thanks!

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

                      @makemerush Were you already running wifi server 1.26 from the previous 3.3 releases?

                      Try placing the wifi server .bin file in the firmware folder from the RC3 release and sending M997 S1 to flash it again. That usually takes care of it.

                      Z-Bot CoreXY Build | Thingiverse Profile

                      makemerushundefined 1 Reply Last reply Reply Quote 1
                      • makemerushundefined
                        makemerush @Phaedrux
                        last edited by

                        @phaedrux Thanks for your help!

                        Seems that it was actually just a coincidence that the update and WiFi issue coincided:

                        Running M997 S1 didn't resolve the issue however I did some further investigation and noticed that ALL of my 2.4 GHz devices were disconnected from my router. After updating my router's channel settings manually and rebooting the router everything is working again, including the Duet2WiFi! 🙂

                        My apologies for the false alarm!

                        1 Reply Last reply Reply Quote 1
                        • tecnoundefined
                          tecno @dc42
                          last edited by

                          @dc42

                          Is there any particular order to update my Mini 5+ WiFi ?
                          These are files that i Downloaded

                          452e3c93-1a7c-4466-97d8-53ae83cd995a-image.png

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

                            @tecno said in Software bundle 3.3RC3 now available:

                            @dc42

                            Is there any particular order to update my Mini 5+ WiFi ?
                            These are files that i Downloaded

                            I suggest DWC first, then the IAP file, then the main and tool firmware files. You only need to update DuetWiTFiServer if you are not already running version 1.26.

                            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

                            tecnoundefined 1 Reply Last reply Reply Quote 0
                            • tecnoundefined
                              tecno @dc42
                              last edited by

                              @dc42

                              Thank you, now updated 😉

                              1 Reply Last reply Reply Quote 0
                              • EducatingSavvasundefined
                                EducatingSavvas @dc42
                                last edited by

                                @dc42 Playing around with the new RRF and CNC controls seems to be working. Just to confirm for CNC users - you will need to specify the tool first by having T# in the Gcode being processed, and then using M3 S# to turn on the spindle at the required RPM. Unless you include a tool number in your config.g file (which I don't) M3 S# wont turn on the spindle tool and you will need to include the spindle P# or select the tool by writing T# into the console. Many thanks.

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

                                  @educatingsavvas said in Software bundle 3.3RC3 now available:

                                  select the tool by writing T# into the console

                                  Not sure if it would apply to you, but for printer applications it would be typical to have T0 at the end of config.g to select the tool at startup. Alternatively you could add it to start.g so that it got executed when a job was started.

                                  Z-Bot CoreXY Build | Thingiverse Profile

                                  EducatingSavvasundefined 1 Reply Last reply Reply Quote 0
                                  • EducatingSavvasundefined
                                    EducatingSavvas @Phaedrux
                                    last edited by

                                    @phaedrux Thanks but I'm not sure yet. I'm planning to use 4 tools on my CNC machine. T0 - laser, T1 - Spindle Router (main tool), T2 - Pen Tool in Spindle, and T3 - Tangential Knife. I'm still getting my head around workflow, working out offsets and g-code generation for multiple tool jobs.

                                    CNCModellerundefined 1 Reply Last reply Reply Quote 1
                                    • war4peaceundefined
                                      war4peace
                                      last edited by war4peace

                                      Attempted to upgrade from 3.3 RC2 to 3.3 RC3, mainly to fix the file simulation issue.
                                      For the last 30 minutes, the upgrade process is stuck at 96%, with last message being "Sending update request to DCS..."

                                      Setting up vlc-plugin-video-splitter:armhf (3.0.12-0+deb10u1+rpt2) ...
                                      Setting up libvlc5:armhf (3.0.12-0+deb10u1+rpt2) ...
                                      Setting up libraspberrypi-doc (1:1.20210527-1) ...
                                      Setting up libraspberrypi-bin (1:1.20210527-1) ...
                                      Setting up vlc-plugin-visualization:armhf (3.0.12-0+deb10u1+rpt2) ...
                                      Setting up libraspberrypi-dev (1:1.20210527-1) ...
                                      Setting up vlc-plugin-qt:armhf (3.0.12-0+deb10u1+rpt2) ...
                                      Setting up libvlc-bin:armhf (3.0.12-0+deb10u1+rpt2) ...
                                      Setting up rpi-eeprom (12.4-1) ...
                                      Setting up vlc-plugin-base:armhf (3.0.12-0+deb10u1+rpt2) ...
                                      Setting up vlc-plugin-skins2:armhf (3.0.12-0+deb10u1+rpt2) ...
                                      Setting up vlc-bin (3.0.12-0+deb10u1+rpt2) ...
                                      Setting up vlc (3.0.12-0+deb10u1+rpt2) ...
                                      Setting up duettools (3.3-rc3) ...
                                      Setting up duetwebserver (3.3-rc3) ...
                                      Setting up duetsoftwareframework (3.3-rc3) ...
                                      To modify config files consider adding yourself to the dsf groupd: # usermod -a       -G dsf <username>
                                      Setting up duetwebcontrol (3.3-rc3) ...
                                      Setting up duetcontrolserver (3.3-rc3) ...
                                      Installing new version of config file /opt/dsf/conf/config.json ...
                                      Setting up reprapfirmware (3.3-rc3-1) ...
                                      Sending update request to DCS...
                                      Progress: [ 96%] [#############################################################...]
                                      
                                      

                                      It just sits there.
                                      Do I attempt a forced reboot? Any idea?

                                      The web interface is unavailable, tells me "Please wait while updates are being installed..." in a popup box.

                                      EDIT: I have forced a reboot after 20 more minutes, and now DCS is not starting anymore.

                                      chrishammundefined 1 Reply Last reply Reply Quote 0
                                      • CNCModellerundefined
                                        CNCModeller @EducatingSavvas
                                        last edited by

                                        @educatingsavvas said in Software bundle 3.3RC3 now available:

                                        @phaedrux Thanks but I'm not sure yet. I'm planning to use 4 tools on my CNC machine. T0 - laser, T1 - Spindle Router (main tool), T2 - Pen Tool in Spindle, and T3 - Tangential Knife. I'm still getting my head around workflow, working out offsets and g-code generation for multiple tool jobs.

                                        @EducatingSavvas If you're using fusion 360 for CAM you configure tool selection there and it can be different for each tool path in each setup. It's worth a look if you haven't already. I use it all the time.

                                        Polar Duet3 Mini + 1HCL
                                        https://youtube.com/playlist?list=PLWjZVEdMv1BY82izahK45qKh-hp3NFkix
                                        Wanhao D4S: Duet2
                                        https://forum.duet3d.com/post/296755
                                        K40 Laser, Duet2
                                        https://forum.duet3d.com/post/312082
                                        Wanhao D5S
                                        https://www.youtube.com/CNCModellerUK

                                        1 Reply Last reply Reply Quote 1
                                        • tom33undefined
                                          tom33
                                          last edited by

                                          Hi,
                                          since I upgrade to the 3.3 RC3 I have an issue with my motor. They don't move.
                                          I Use duet3 with expansion board for external stepper driver.

                                          1 Reply Last reply Reply Quote 0
                                          • war4peaceundefined
                                            war4peace
                                            last edited by

                                            Update tom my previous post.
                                            I had to connect the Duet 3 6HC to USB and to a laptop, and update the firmware using BOSSA.
                                            Everything now works correctly.

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