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

    Firmware 1.20 released

    Scheduled Pinned Locked Moved
    Firmware installation
    20
    89
    14.2k
    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.
    • Captain_squndefined
      Captain_sq
      last edited by

      The "heartbeat" message

      [c]17:36:25.475 : N151 M10534
      17:36:25.476 : serial: M105
      17:36:28.535 : N152 M105
      33
      17:36:28.537 : serial: M105
      17:36:31.062 : Class GCodes spinning
      17:36:31.062 : Class Move spinning
      17:36:31.062 : Class Platform spinning
      17:36:31.062 : Class Network spinning
      17:36:31.062 : Class Network spinning
      17:36:31.064 : Class Heat spinning
      17:36:31.064 : Class PrintMonitor spinning
      17:36:31.601 : N153 M10532
      17:36:31.602 : serial: M105
      17:36:34.660 : N154 M105
      39
      17:36:34.661 : serial: M105
      17:36:37.720 : N155 M10538
      17:36:37.721 : serial: M105
      17:36:40.786 : N156 M105
      37
      17:36:40.787 : serial: M105
      [/c]

      Custom made Kossel Mini - Duet WiFi / Modded Tronxy X5S - Duet WiFi / Prusa i3 MKIII


      Embedded systems designer, RC Pilot, maker and Gadget-o-holic

      1 Reply Last reply Reply Quote 0
      • RGN01undefined
        RGN01
        last edited by

        I upgraded my Duet WiFi firmware from 1.19 to 1.20 yesterday. All seems to be working but I'm getting strange error messages when I start a print. They start at layer 0 but I was slow to capture them - each layer gives an error like this:

        [c]17:34:59Error: Bad command: // starting layer 19 at 2.47368mm
        17:34:47Error: Bad command: // starting layer 18 at 2.4mm
        17:34:35Error: Bad command: // starting layer 17 at 2.2mm
        17:34:24Error: Bad command: // starting layer 16 at 2.18947mm
        17:34:12Error: Bad command: // starting layer 15 at 2mm
        17:34:01Error: Bad command: // starting layer 14 at 1.90526mm
        17:33:49Error: Bad command: // starting layer 13 at 1.8mm
        17:33:37Error: Bad command: // starting layer 12 at 1.62105mm
        [/c]

        The print worked OK but layer height was 0.2mm so I'm a little surprised by some of the layer heights.

        What does this mean, please?

        Thanks.

        Richard

        (edited to correct the starting layer from 1 to 0)

        1 Reply Last reply Reply Quote 0
        • RGN01undefined
          RGN01
          last edited by

          OK, I figured out what it is. The slicer was adding a comment to the beginning of each layer. This was in the format "// starting layer [layer_num] at [layer_z]mm"

          The // was being interpreted as a comment but is no longer being interpreted so. I have changed the setting to "; starting layer [layer_num] at [layer_z]mm" and will try this as soon as I have finished the running print and can try another.

          I'll report back once I confirm that this is the issue and is sorted.

          1 Reply Last reply Reply Quote 0
          • RGN01undefined
            RGN01
            last edited by

            This is confirmed - it was a slicer setting, nothing at all to do with the Duet firmware but a bit strange that the prior version didn't report errors with that format. Anyway, all sorted, thanks.

            @RGN01:

            OK, I figured out what it is. The slicer was adding a comment to the beginning of each layer. This was in the format "// starting layer [layer_num] at [layer_z]mm"

            The // was being interpreted as a comment but is no longer being interpreted so. I have changed the setting to "; starting layer [layer_num] at [layer_z]mm" and will try this as soon as I have finished the running print and can try another.

            I'll report back once I confirm that this is the issue and is sorted.

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

              @RGN01:

              This is confirmed - it was a slicer setting, nothing at all to do with the Duet firmware but a bit strange that the prior version didn't report errors with that format. Anyway, all sorted, thanks.

              @RGN01:

              OK, I figured out what it is. The slicer was adding a comment to the beginning of each layer. This was in the format "// starting layer [layer_num] at [layer_z]mm"

              The // was being interpreted as a comment but is no longer being interpreted so. I have changed the setting to "; starting layer [layer_num] at [layer_z]mm" and will try this as soon as I have finished the running print and can try another.

              I'll report back once I confirm that this is the issue and is sorted.

              It's because RRF now recognises lower case command letters, and also parses lines of gcode more thoroughly.

              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
              • dc42undefined
                dc42 administrators
                last edited by

                @Captain_sq:

                I'm not sure wich number you're after so I copied the entire response:
                …
                17:34:17.154 : Last reset 00:07:46 ago, cause: power up
                17:34:17.154 : Last software reset time unknown, reason: Stuck in spin loop, spinning module Network, available RAM 8620 bytes (slot 2)
                17:34:17.154 : Software reset code 0x2041 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0440f80f, BFAR 0xe000ed38, SP 0x20087e6c
                17:34:17.155 : Stack: 000bfb1f 01c8a8c0 fffffff9 00ffffff 20087ebc 20070fe8 01c8a8c0 20087ebc 000a6221 000a6220 21000000 20087ea0 2007a938 00000000 2007376c 200737a8 20087ebc 0000012c 2007aea8 75207369 01c8a8c0 2007376c 000a5b1d 2001376c
                ...

                Thanks, that should help me to track the problem down.

                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
                • Captain_squndefined
                  Captain_sq
                  last edited by

                  @dc42
                  I've gone back to 1.19 while your busy finding the rodent messing around in the Network task in the 0.6 hardware. I kept the newest DWC and found that this also works with 1.19 FW. Nice with some new functionality. I'm not sure wether all the new controls works for real with 1.19 but the extended system edit possibilities are welcome.

                  Custom made Kossel Mini - Duet WiFi / Modded Tronxy X5S - Duet WiFi / Prusa i3 MKIII


                  Embedded systems designer, RC Pilot, maker and Gadget-o-holic

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

                    I have it on my list to investigate your report before the 1.20.1 release, however I need to get the prototype laser filament sensors completed and shipped first to avoid additional delay to production of filament sensors.

                    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
                    • Luca79undefined
                      Luca79
                      last edited by

                      Just tried to upgrade from 1.19 to 1.20. I've uploaded DuetWifiFirmware.bin, but I cannot connect anymore to the printer via wireless. Any idea?

                      1 Reply Last reply Reply Quote 0
                      • Luca79undefined
                        Luca79
                        last edited by

                        Adding some bits. I also tried connecting through USB but the serial device is not recognized by my linux machine (before upgrading used to work).
                        EDIT: i have tried the fallback procedure #2 described at https://duet3d.com/wiki/Updating_main_firmware but it still doesn't work.

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

                          The USB interface code did not change between 1.19 and 1.20, so I don't understand why you can't access the Duet over USB any more. Do you have any evidence that the firmware update succeeded in other ways, e.g. because an attached PanelDue is working?

                          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
                          • Luca79undefined
                            Luca79
                            last edited by

                            I don't own a PanelDue. I don't know how to debug this.

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

                              So as far as you know, the board isn't running at all. See https://duet3d.com/wiki/What_to_do_if_your_Duet_or_Duet_WiFi_won%27t_respond.

                              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
                              • abitidiundefined
                                abitidi
                                last edited by

                                I just want to report that the github link on this wiki page is broken. https://duet3d.com/wiki/Updating_main_firmware

                                1 Reply Last reply Reply Quote 0
                                • deckingmanundefined
                                  deckingman
                                  last edited by

                                  @abitidi:

                                  I just want to report that the github link on this wiki page is broken. https://duet3d.com/wiki/Updating_main_firmware

                                  Works for me. Maybe it got fixed between your post and mine?

                                  Ian
                                  https://somei3deas.wordpress.com/
                                  https://www.youtube.com/@deckingman

                                  1 Reply Last reply Reply Quote 0
                                  • abitidiundefined
                                    abitidi
                                    last edited by

                                    @deckingman:

                                    Works for me. Maybe it got fixed between your post and mine?

                                    Weird…I still get a 404 when I try the link.

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

                                      I just tried it again (using the link in deckingman's post above) and it works for me.

                                      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
                                      • Dougal1957undefined
                                        Dougal1957
                                        last edited by

                                        it also works for me with no issues (From the OP's original link)

                                        1 Reply Last reply Reply Quote 0
                                        • rar26undefined
                                          rar26
                                          last edited by

                                          do i have to redo my config file after the update?

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

                                            @rar26:

                                            do i have to redo my config file after the update?

                                            Read the upgrade notes to see whether you need to make any changes.

                                            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
                                            • First post
                                              Last post
                                            Unless otherwise noted, all forum content is licensed under CC-BY-SA