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

    Firmware 1.21 release candidate 2 now available

    Scheduled Pinned Locked Moved
    Firmware installation
    22
    81
    11.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.
    • kazolarundefined
      kazolar
      last edited by

      I kept getting disconnect messages because duet was busy, then it finally loaded the 67mb file, and I got:
      Error: Cannot read file.
      Error: Failed to read footer from G-Code file "0:/gcodes/Part1V2.gcode"

      1 Reply Last reply Reply Quote 0
      • kazolarundefined
        kazolar
        last edited by

        After it finally read it – I started printing it -- and it fell of the network entirely, but the screen said it was printing -- then i disconnected the network cable and plugged it back in, and it came back, and DWC is back and responsive.

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

          I uploaded your files to one of my printers, and they uploaded OK and are displayed in the file list. However, no object height or filament usage is displayed. The reason according to Notepad++ is that both files contain vast quantities of null characters shortly before the end, within the footer comments region. If these are as S3D generated them, then I suspect a bug in S3D.

          The error message you received suggests to me that you should replace the SD card.

          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
          • kazolarundefined
            kazolar
            last edited by

            I have seen this before with S3D especially with large files. I will try to re-save them – this is a new high speed card. I think the null characters are confusing duet...I'll try to re-save them and upload them.

            1 Reply Last reply Reply Quote 0
            • kazolarundefined
              kazolar
              last edited by

              I edited the file and got rid of the nulls, and it got loaded right away. I'll report this bug to S3D. Thanks for checking.

              1 Reply Last reply Reply Quote 0
              • k3lagundefined
                k3lag
                last edited by

                I updated, changed my probe type to 9, removed my M401s and M402s from bed.g, homez.g and homeall.g. Everything is working as expected on my IDEX cartesian.

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

                  @k3lag:

                  I updated, changed my probe type to 9, removed my M401s and M402s from bed.g, homez.g and homeall.g. Everything is working as expected on my IDEX cartesian.

                  Thanks for the feedback. Be aware the the multi touch Z probing is not compatible with bltouch in this release.

                  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
                  • kazolarundefined
                    kazolar
                    last edited by

                    I have a BL touch and have had the probe type set to 5 and was using multi-touch and it works fine, what is the benefit of using type 9?

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

                      Some bltouch users had the problem of the bltouch extending too soon again after probing.

                      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
                      • k3lagundefined
                        k3lag
                        last edited by

                        @dc42:

                        @k3lag:

                        I updated, changed my probe type to 9, removed my M401s and M402s from bed.g, homez.g and homeall.g. Everything is working as expected on my IDEX cartesian.

                        Thanks for the feedback. Be aware the the multi touch Z probing is not compatible with bltouch in this release.

                        I don't use multi touch at this point, but I may check it out at some point in the future. I seem to get pretty good results with my setup without it. Maybe I got lucky and got a pretty consistent bltouch.

                        Larry

                        1 Reply Last reply Reply Quote 0
                        • nytundefined
                          nyt
                          last edited by

                          @dc42:

                          A few issues with this release have come to light:

                          • The new bltouch probe support doesn't work properly if you enable the multi-tap function, because it fails to deploy the probe before the second tap
                          • The multi-tap function only implements the recovery delay before the first tap at each probe point, instead of before each tap
                          • Support for the Duet3D rotating magnet filament sensor is not working

                          Is it possible to get multitap for Z homing?

                          1 Reply Last reply Reply Quote 0
                          • Gosuundefined
                            Gosu
                            last edited by

                            Firmware Name: RepRapFirmware for Duet WiFi and Duet Ethernet
                            Firmware Electronics: Duet WiFi 1.02 or later
                            Firmware Version: 1.21RC2 (2018-02-15 build 2)
                            WiFi Server Version: 1.21RC2
                            Web Interface Version: 1.20

                            When i upload a file that is named fooprint(2).gcode and want to print the file it will say file does not exist
                            Error: M32: GCode file "0:/gcodes/26mmgauntbaseV2.gcode" not found
                            10:04:14 PMM32 0:/gcodes/26mmgauntbaseV2(2).gcode
                            any chance you might have a look into that?

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

                              This issue has been raised several times already. It is part of the NIST GCode standard that parenthesis surround comments, therefore they are stripped out. The workaround is to surround the filename in double quotes. The latest beta of PanelDueFirmware already does this, so will the next version of 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

                              1 Reply Last reply Reply Quote 0
                              • Captain_squndefined
                                Captain_sq
                                last edited by

                                @dc42:

                                This issue has been raised several times already. It is part of the NIST GCode standard that parenthesis surround comments, therefore they are stripped out. The workaround is to surround the filename in double quotes. The latest beta of PanelDueFirmware already does this, so will the next version of DWC.

                                …or use square brackets instead.

                                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
                                • nickpgreundefined
                                  nickpgre
                                  last edited by

                                  Came here to report.

                                  CoreXY with bltouch and multitouch probing enabled with Probe 5 (P5), prints and everything works fine. Also the web interface feels more responsive.

                                  1 Reply Last reply Reply Quote 0
                                  • BMMalundefined
                                    BMMal
                                    last edited by

                                    I just installed this RC so I have not yet reached the end of a print with this firmware but it seems that the slowdown issue here: https://www.duet3d.com/forum/thread.php?id=4045#p36659 still persists. I recently noticed that sometimes my machine would enter this state at the beginning of a print as well as consistently at the end (on RC1). It got stuck in this slow state with RC2 at the beginning of the first print I just started.

                                    I expect that it will enter this slow state at the end of the print as well but if not I will be sure to report back.

                                    Duet Ethernet - Most likely the most recent Edge firmware
                                    Duet X5
                                    7" Panel Due V2
                                    Cartesian, 4 Nozzles with Flex3Drives, Heated Chamber, Simple Switch Filament Sensing

                                    1 Reply Last reply Reply Quote 0
                                    • BMMalundefined
                                      BMMal
                                      last edited by

                                      On RC1, I got 3 of my simple switch filament sensors working, using the following configurations:

                                      T0 M591 D0 P2 C3
                                      T1 unused for now
                                      T2 M591 D2 P2 C5
                                      T3 M591 D3 P2 C5

                                      I am now getting errors that C5 is not acceptable. Is this correct?

                                      With X, Y, and Z endstops connected what are the C numbers that I can use for 4 filament sensors?

                                      If I went to sensor less homing, what would the C numbers be?

                                      Can some C numbers be used with only certain types of sensors (P)?

                                      Does it matter if an expansion board is present?

                                      It looks like the pad printing on the boards and C numbers correspond as follows, correct?
                                      X C0
                                      Y C1
                                      Z C2
                                      E0 C3
                                      E1 C4
                                      E2 C5
                                      E3 C6
                                      E4 C7
                                      E5 C8
                                      E6 C9

                                      Sorry to ask so many questions but I'm having a hard time figuring this out from the wiki: https://duet3d.dozuki.com/Wiki/Gcode#Section_M591_Configure_filament_sensing

                                      Duet Ethernet - Most likely the most recent Edge firmware
                                      Duet X5
                                      7" Panel Due V2
                                      Cartesian, 4 Nozzles with Flex3Drives, Heated Chamber, Simple Switch Filament Sensing

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

                                        Thanks for spotting this, it will be fixed in RC3.

                                        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
                                        • BMMalundefined
                                          BMMal
                                          last edited by

                                          After installing RC1 (at least that is when I noticed), my machine stopped reporting layer times and therefore estimates based on layer time. This issue persists in RC2. My gcodes are generated using KISSlicer. This may have started because I began using Z hop in Kisslicer (an no FW z hop) since it can filter hops out for really short travel moves.

                                          Duet Ethernet - Most likely the most recent Edge firmware
                                          Duet X5
                                          7" Panel Due V2
                                          Cartesian, 4 Nozzles with Flex3Drives, Heated Chamber, Simple Switch Filament Sensing

                                          1 Reply Last reply Reply Quote 0
                                          • kazolarundefined
                                            kazolar
                                            last edited by

                                            I was going to submit a new bug report, but my machine is doing this SLOW CRAWL right now – it's a slow state of 12 hours into 15 hour print. Which is really frustrating. The DWC disconnects -- I don't know if there is away to save the print as I know where it is,

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