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

    Stable firmware 2.01 (Duet 2) and 1.22 (Duet 06/085) released

    Scheduled Pinned Locked Moved
    Firmware installation
    19
    65
    9.8k
    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.
    • whosrdaddyundefined
      whosrdaddy @whosrdaddy
      last edited by

      Ok, I sliced a smaller file and now I can see the object height. I suppose the firmware does not attempt to read the height for larger files?

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

        @whosrdaddy I just uploaded the largest GCode file I could find on my hard drive (just a little under 11 MiB) and it got the height correctly from it. I also checked the file and it does not contain a comment with object height, so RRF must have scanned for the last rise in Z.

        Don't get me wrong, I don't wanna say you don't have a problem, just that I cannot reproduce it.

        Could you try to slice the same source file with another slicer?

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

          Well did as requested and it seems it has nothing to do with the slicer, used exactly the same STL files:

          alt text

          wilrikerundefined Dougal1957undefined 2 Replies Last reply Reply Quote 0
          • wilrikerundefined
            wilriker @whosrdaddy
            last edited by

            @whosrdaddy OK, your file is larger than mine, so maybe there is a lower limit to this issue.

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

              @whosrdaddy Can you post the stl for the 2 that fail so we can try it? I have several file much bigger than those that are correct

              0_1533215847677_bb70cff7-55c2-43a2-b2b5-6290303968bb-image.png

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

                Sure, you can download it from here:
                https://www.thingiverse.com/download:3377042

                wilrikerundefined Dougal1957undefined 2 Replies Last reply Reply Quote 0
                • wilrikerundefined
                  wilriker @whosrdaddy
                  last edited by

                  @whosrdaddy With this file I can reproduce your issue:
                  0_1533216277238_215bcc9e-e548-4929-ab23-4aab0234e39d.png

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

                    @whosrdaddy this is what I get for that file

                    0_1533216451119_dca35fb3-8080-4b6a-bfe9-5bf946efd9db-image.png

                    It's not easy to read cos this forum is re-sizing the image but my file is 3 times the size of yours but gives 8.2mm hight and 39.xxx mtrs of filament. the diff may be the amount of infill mind

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

                      so we established there is an issue, it's not the file size because you have a 31MB file.
                      Lets wait & see what @dc42 thinks about this...

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

                        I Too am on the latest FW and DWC

                        0_1533216886004_2b852a75-7583-4377-87f4-db21c57d7802-image.png

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

                          The firmware has has to seek backwards through the file from the end to find the last Z move. With large files this can get very slow because of the way the FAT file system works, especially if the SD card is formatted using a small cluster size. So to prevent DWC timing out, recent firmware versions apply a time limit to this operation.

                          To speed up access and minimise the chance of reaching the time limit, format the SD card using the largest cluster size you can, which is 64kb for 4Mb cards and smaller (FAT16 format), and 32kb for larger cards (FAT32 format). Send M39 to find the current cluster size.

                          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

                          wilrikerundefined appjawsundefined 2 Replies Last reply Reply Quote 0
                          • whosrdaddyundefined
                            whosrdaddy
                            last edited by

                            Thanks David, I understand now. It's not a big issue anyway, since I am currently printing non stop, I will try your advice later 🙂

                            1 Reply Last reply Reply Quote 0
                            • Qdeathstarundefined
                              Qdeathstar
                              last edited by

                              I consider this to be a bug:

                              Now that you can upload g-code while you print, if you upload a file with the same name as the file you are printing, the print will switch from the file you were printing to the new file.

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

                                @qdeathstar said in Stable firmware 2.01 (Duet 2) and 1.22 (Duet 06/085) released:

                                I consider this to be a bug:

                                Now that you can upload g-code while you print, if you upload a file with the same name as the file you are printing, the print will switch from the file you were printing to the new file.

                                I'll add this to the list of things to fix. The firmware already checks for trying to delete a file while it is being printed.

                                EDIT: I just found it was already on the list, but low priority.

                                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

                                BPisLifeundefined 1 Reply Last reply Reply Quote 0
                                • dragonnundefined
                                  dragonn
                                  last edited by

                                  Maybe add a warning/question? This helped my last time when I need to add a pause command into a running print.

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

                                    @dc42 said in Stable firmware 2.01 (Duet 2) and 1.22 (Duet 06/085) released:

                                    The firmware has has to seek backwards through the file from the end to find the last Z move. With large files this can get very slow because of the way the FAT file system works, especially if the SD card is formatted using a small cluster size. So to prevent DWC timing out, recent firmware versions apply a time limit to this operation.

                                    To speed up access and minimise the chance of reaching the time limit, format the SD card using the largest cluster size you can, which is 64kb for 4Mb cards and smaller (FAT16 format), and 32kb for larger cards (FAT32 format). Send M39 to find the current cluster size.

                                    I just ran M39 and got

                                    SD card in slot 0: capacity 3.98Gb, free space 3.78Gb, speed 20.00MBytes/sec, cluster size 64kb
                                    

                                    so my card is already formatted to the largest possible cluster size (it came this way I never touched it) and still I could reproduce @whosrdaddy's issue. Intersting why it works for @Dougal1957 with an even larger file though.

                                    Just an idea: @Dougal1957 do you still have the stock SD card or do you maybe use a faster one? Also @dc42 do you know more details on the speed of the stock SD card?

                                    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

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

                                      @wilriker Prob not I go thru cards quite a lot (take them out put them down and lose them lol) M39 gives

                                      SD card in slot 0: capacity 15.93Gb, free space 15.18Gb, speed 20.00MBytes/sec, cluster size 32kb

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

                                        @dc42 said in Stable firmware 2.01 (Duet 2) and 1.22 (Duet 06/085) released:

                                        The firmware has has to seek backwards through the file from the end to find the last Z move. With large files this can get very slow because of the way the FAT file system works, especially if the SD card is formatted using a small cluster size. So to prevent DWC timing out, recent firmware versions apply a time limit to this operation.

                                        When uploading a laser file, which could be in excess of 30MB there is a large delay. I keep getting "could not fine end of file error".
                                        For Laser files, the Object Height, Layer Height and Filament Usage are not required or recorded in the file, so the firmware will ever obtain the data.

                                        appjaws - Core XYUV Duet Ethernet Duex5
                                        firmware 3.5.0-rc.4 Web Interface 3.5.0-rc.4
                                        Ormerod 1-converted to laser engraver, Duet wifi
                                        OpenSCAD version 2024.03.18
                                        Simplify3D 5.1.2

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

                                          @appjaws, what is the exact message you are getting, and when?

                                          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
                                          • appjawsundefined
                                            appjaws
                                            last edited by appjaws

                                            DWC just sits after the file has been uploaded until it fills each box with N/A.
                                            The firmware is searching for this data when it doesn't need to for laser files.
                                            The "could not find end of file error" appears randomly during printing.
                                            I will see if I can nail the exact conditions later

                                            Edit. The "could not find end of file error" appears when the print starts

                                            appjaws - Core XYUV Duet Ethernet Duex5
                                            firmware 3.5.0-rc.4 Web Interface 3.5.0-rc.4
                                            Ormerod 1-converted to laser engraver, Duet wifi
                                            OpenSCAD version 2024.03.18
                                            Simplify3D 5.1.2

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