Duet3D Logo

    Duet3D

    • Register
    • Login
    • Search
    • Categories
    • Tags
    • Documentation
    • Order

    Firmware 2.0RC2 released

    Firmware installation
    19
    45
    4250
    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.
    • dc42
      dc42 administrators last edited by dc42

      Get it and the associated Duet Web Control update from https://github.com/dc42/RepRapFirmware/releases/tag/2.0RC2. Release notes are at https://github.com/dc42/RepRapFirmware/blob/dev/WHATS_NEW.md.

      If there is any demand, I will issue a 1.21.1RC2 release for the older Duets too. However, I have not received any feedback from anyone running 1.21.1RC1 on an older Duet 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
      • timcurtis67
        timcurtis67 last edited by

        Sweet! I'll try it out tonight.

        1 Reply Last reply Reply Quote 0
        • Dougal1957
          Dougal1957 last edited by

          Whats the Scanner interface David if I may ask?

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

            @dougal1957 said in Firmware 2.0RC2 released:

            Whats the Scanner interface David if I may ask?

            It's an interface for a 3D scanner that one of our OEMs uses with the Duet and a RPi. Chrishamm can tell you more.

            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

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

              @dc42 Thats sounds interesting If you see this Chris can you elaborate a little more?

              Doug

              1 Reply Last reply Reply Quote 1
              • TYPPA Albert Einstein
                TYPPA Albert Einstein last edited by TYPPA Albert Einstein

                Hi David
                HW Duet Wi-Fi
                FW 2.0R2
                DuetWiFiserver 1.21 and DuetWebControl 1.21.1RC4
                .....
                Gcode file 2.5 Mb upload is very slow ... error on upload ...
                No deleting file after upload ( failed ) .... DWC response : ....file is open ...
                Thanks Giorgio

                I have no special talent. I am only passionately curious.
                -Albert Einstein

                1 Reply Last reply Reply Quote 0
                • wilriker
                  wilriker last edited by wilriker

                  DHT sensor support?! That sounds cool, especially as I have at least one of them laying around. How would they get connected? And is there any use-case already? I could imagine measuring humidity in a filament dry-box. Any other ideas?

                  Manuel
                  Duet 3 6HC (v0.6) with RPi 4B on a custom Cartesian
                  with probably always latest firmware/DWC (incl. betas or self-compiled)
                  My Tool Collection

                  resam 1 Reply Last reply Reply Quote 0
                  • resam
                    resam @wilriker last edited by

                    @wilriker DHT support is available since a few releases ago!
                    You can use M305 to configure two new channels for temp and humidity:

                    Channels 400, 401... are DHTxx temperature and humidity channels. The DATA line of the DHTxx must be connected to CS6 (was E3 Endstop on the expansion header) on the Duet WiFi/Ethernet. Specify the sensor type (11 for DHT11, 21 for DHT21 or 22 for DHT22) via the T-parameter

                    whosrdaddy 1 Reply Last reply Reply Quote 0
                    • mperdue
                      mperdue last edited by

                      I tried installing this but now things don't work.

                      The software information shows:

                      Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet
                      Firmware Electronics: Duet WiFi 1/02 or later + Duex5
                      Firmware Version: 2.0(RTOS)RC2 (2018-05-10b1)
                      WiFi Server Version: 1.21
                      Web Interface Version: 1.21.1-RC4

                      I can activate the bed and the extruder heater but I can't move in any axis.

                      Anyone have any ideas what I may have done wrong?

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

                        @mperdue said in Firmware 2.0RC2 released:

                        I tried installing this but now things don't work.

                        The software information shows:

                        Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet
                        Firmware Electronics: Duet WiFi 1/02 or later + Duex5
                        Firmware Version: 2.0(RTOS)RC2 (2018-05-10b1)
                        WiFi Server Version: 1.21
                        Web Interface Version: 1.21.1-RC4

                        I can activate the bed and the extruder heater but I can't move in any axis.

                        Anyone have any ideas what I may have done wrong?

                        Were you already running firmware 1.21 ? If not then read the upgrade notes for version 1.21 and any other stable versions that you skipped.

                        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
                        • whosrdaddy
                          whosrdaddy @resam last edited by whosrdaddy

                          @mperdue: in newer firmwares, you can only moves axes when they are homed.
                          If you want to revert to the original behavior, add M564 H0 to your config.g, or else you will need to add S2 to your G1 commands to allow movement on a non homed axis...

                          1 Reply Last reply Reply Quote 1
                          • mperdue
                            mperdue last edited by mperdue

                            I had skimmed the release notes prior to updating but, obviously, I need to read them more closely. The movement comments certainly address the immediate issues I was having but I think I’ll read everything before I do it again. Thanks guys.

                            1 Reply Last reply Reply Quote 0
                            • carlosspr
                              carlosspr last edited by

                              Same for me. At some point the Web Interface lost connection and the print stopped. I was able to access the board via Telnet and generate an M122, but several atpempts needed before gettign the log because the Telnet would close connection before dumping all information.

                              === Diagnostics ===
                              RepRapFirmware for Duet 2 WiFi/Ethernet version 2.0(RTOS)RC2 running on Duet WiFi 1.02 or later
                              Board ID: 08DDM-9FAM2-LW4S4-6J1D8-3SJ6M-TMVZY
                              Used output buffers: 2 of 20 (8 max)
                              === RTOS ===
                              Static ram: 28564
                              Dynamic ram: 96048 of which 0 recycled
                              Exception stack ram used: 288
                              Never used ram: 6172
                              Task NETWORK ready, free stack 1408
                              Task HEAT blocked, free stack 1256
                              Task MAIN running, free stack 3804
                              === Platform ===
                              Last reset 00:01:23 ago, cause: software
                              Last software reset time unknown, reason: Hard fault, spinning module Platform, available RAM 5864 bytes (slot 3)
                              Software reset code 0x4030 HFSR 0x40000000, CFSR 0x00000400, ICSR 0x0041f803, BFAR 0xe000ed38, SP 0x20005004
                              Stack: 0040b539 00433b84 01000200 f8000000 406e386f 3edb6db7 b7b4d800 3e178897 3e1cd04f 41700000 3e23e0ac 3e3a4c97 3e63a87e 3e9258c9 3cd1cfc0 3f317180 3f800000 60000000 40382d26 60000010 004448bb 20005070 200050b8 00000001
                              Error status: 0
                              Free file entries: 10
                              SD card 0 detected, interface speed: 20.0MBytes/sec
                              SD card longest block write time: 0.0ms
                              MCU temperature: min 37.5, current 37.7, max 38.0
                              Supply voltage: min 23.9, current 24.0, max 24.2, under voltage events: 0, over voltage events: 0
                              Driver 0: standstill, SG min/max not available
                              Driver 1: standstill, SG min/max not available
                              Driver 2: standstill, SG min/max not available
                              Driver 3: standstill, SG min/max not available
                              Driver 4: standstill, SG min/max not available
                              Date/time: 1970-01-01 00:00:00
                              Slowest main loop (seconds): 0.010376; fastest: 0.000075
                              === Move ===
                              Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm 240, MaxWait: 0ms, Underruns: 0, 0
                              Scheduled moves: 0, completed moves: 0
                              Bed compensation in use: none
                              Bed probe heights: 0.000 0.000 0.000 0.000 0.000
                              === Heat ===
                              Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
                              Heater 1 is on, I-accum = 0.0
                              === GCodes ===
                              Segments left: 0
                              Stack records: 2 allocated, 0 in use
                              Movement lock held by null
                              http is idle in state(s) 0
                              telnet is idle in state(s) 0
                              file is idle in state(s) 0
                              serial is idle in state(s) 0
                              aux is idle in state(s) 0
                              daemon is idle in state(s) 0
                              queue is idle in state(s) 0
                              autopause is idle in state(s) 0
                              Code queue is empty.
                              === Network ===
                              Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(2) Telnet(0)
                              HTTP sessions: 0 of 8

                              • WiFi -
                                Network state is running
                                WiFi module is connected to access point
                                Failed messages: pending 0, notready 0, noresp 0
                                Failed to get WiFi status
                                Socket states: 2 0 0 0 0 0 0 0
                                === Expansion ===
                              dc42 2 Replies Last reply Reply Quote 0
                              • mperdue
                                mperdue last edited by

                                OK, I've reloaded and gotten things moving again so I'm working on my homely.g file now. In the previous releases I've run I would start the home sequence by moving both the X and Y towards the origin simultaneously, then I would fine home each of them separately. I don't seem to be able to move them both at the same time anymore but I can live with that. A bigger issue is that I would also fast home the Z and then fine home it. I'd do this my moving the X and X to the center of the bed and then moving the Z at a reasonable speed toward the bed. Then I'd back off and do the actual probe.

                                The code I used

                                M401 ; Deploy probe
                                G1 Z-999 F1000 S1 ; Course home Z Only
                                G1 Z5 F1000 ; Back off home location
                                M401 ; Deploy the probe
                                G30 Z-300 S0 ; Probe Z

                                The G1 using the S1 no longer seems to work as it did so this script no longer works. The G30 works well but it is very slow so if the machine was shut down with the bed at Z 250 it will take a very long time to probe the Z. Is there something I'm doing wrong here?

                                On the plus side I no longer have to tell it to deploy the probe since the BLTouch now has a unique definition and is handled properly.

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

                                  You should still be able to home X and Y concurrently initially, nothing has been changed in that respect.

                                  Your method of Z homing is unusual. Normally you would use either a G1 S1 Z move and a homing switch, or a G30 Z probe, not both. But either of the following methods should still work if you want to do fast then slow Z homing:

                                  1. Tell the firmware that the Z endstop (for the G1 S1 Z command) is the Z probe, by using M574 Z1 S2 in config.g.

                                  2. Use G30 to do the fast Z homing instead of a G1 S1 Z move, but use an extra M558 command to temporarily increase the probing speed (F parameter in M558).

                                  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

                                  mperdue 1 Reply Last reply Reply Quote 0
                                  • Cata
                                    Cata last edited by

                                    What is that? need a not-maestro explanation
                                    0_1526080068620_12864 disp.JPG

                                    JohnOCFII 1 Reply Last reply Reply Quote 0
                                    • okercho
                                      okercho last edited by

                                      Hi, I just installed the RC2 and from the interface I'm not able to shutdown the heater, it turned on automatically (at 0ºC for active and standby temp) and if I try to "control all, turn everything off" or to switch from active to standby (from the interface) it does nothing, but I can switch from active from standby in the paneldue though.

                                      In the console I see this "G10 P0 R-273.15 S-273.15", but nothing changes.

                                      I think nothing changed at heater config level between 1.21 and this RC, right? (at least, I didn't see it...)

                                      Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet
                                      Firmware Electronics: Duet WiFi 1.02 or later
                                      Firmware Version: 2.0(RTOS)RC2 (2018-05-10b1)
                                      WiFi Server Version: 1.21
                                      Web Interface Version: 1.21.1-RC4

                                      Anyone else sees the same?

                                      Regards

                                      Okercho
                                      Custom Prusa i3 Hephestos with Duet Wi-Fi
                                      E3d V6 with Bondtech BMG DirectDrive and PrecisionPiezo Sensor
                                      Rebuilding Hypercube Evolution

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

                                        @dc42

                                        I've changed my Z homing code to work as in your second option and it works well. However, I've decided to disable the functionality for now using M564 H0. I'll revisit this after I get a few print jobs completed and I can give it my full attention.

                                        1 Reply Last reply Reply Quote 0
                                        • JohnOCFII
                                          JohnOCFII @Cata last edited by

                                          @cata This is a 12864 display.

                                          https://www.amazon.com/Sintron-Graphic-Display-Controller-Printer/dp/B06WP8BSBB

                                          Cata 1 Reply Last reply Reply Quote 0
                                          • Cata
                                            Cata @JohnOCFII last edited by

                                            @johnocfii Yes, i know. But, can we have that on the duets?

                                            JohnOCFII 1 Reply Last reply Reply Quote 0
                                            • JohnOCFII
                                              JohnOCFII @Cata last edited by JohnOCFII

                                              @cata said in Firmware 2.0RC2 released:

                                              @johnocfii Yes, i know. But, can we have that on the duets?

                                              I looked into this a bit a year or so ago. My understanding is that it would require another board to supply the smarts that are in the PanelDue displays in between the Duet and the 12864. With that level of hassle and expense, it would be easier to just get the PanelDue if you wanted a display. At least -- that is what I remember. I decided not to pursue a display.

                                              Cata 1 Reply Last reply Reply Quote 0
                                              • Cata
                                                Cata @JohnOCFII last edited by Cata

                                                @johnocfii You are wrong, i see the full graphics display with a 2 usd wemos working in the duet. Total cost = 10 usd. I want to know how is working in the maestro.

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

                                                  On the Duet Maestro we included 2 more 10-pin ribbon cable sockets and and extra chip to gate and convert the SPI bus to 5V, so that we can support 12864 displays. We did that on the basis that someone buying a budget board would be more likely to want to use a budget display.

                                                  To do the same on the other Duets you would need an adapter that plugs into the daughter board connector and the CONN_SD connector, to provide the gating and level shifting.

                                                  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

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

                                                    @dc42 said in Firmware 2.0RC2 released:

                                                    On the Duet Maestro we included 2 more 10-pin ribbon cable sockets and and extra chip to gate and convert the SPI bus to 5V, so that we can support 12864 displays. We did that on the basis that someone buying a budget board would be more likely to want to use a budget display.

                                                    To do the same on the other Duets you would need an adapter that plugs into the daughter board connector and the CONN_SD connector, to provide the gating and level shifting.

                                                    Another type of budget display that works with all Duets is an old smartphone running DWC.

                                                    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

                                                    mickey30m Cata 2 Replies Last reply Reply Quote 2
                                                    • wilriker
                                                      wilriker last edited by

                                                      I upgraded to 2.0RC2 and currently my second print is running perfectly fine so far.

                                                      Only thing I realized was that after upgrading I did not reset the Duet (would that have been recommended anyway?) and when running a G29 (no Z probe, so manually adjusting via DWC buttons) movement commands where heavily delayed. So when clicking on a button to move Z up/down sometimes this was instantaneously and sometimes it would take up to several seconds for the printer to react. I have not reset the Duet afterwards and I have not yet tried this again (I will likely do it tonight or tomorrow as I have to move the printer again).

                                                      If you tell me that this is something that can be expected when upgrading firmware and not doing a reset then you can ignore this one. 😉

                                                      Manuel
                                                      Duet 3 6HC (v0.6) with RPi 4B on a custom Cartesian
                                                      with probably always latest firmware/DWC (incl. betas or self-compiled)
                                                      My Tool Collection

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