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

    A website estimates print time accurately from speed/acceleration/jerk

    Scheduled Pinned Locked Moved
    General Discussion
    13
    31
    5.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.
    • lignumaquaundefined
      lignumaqua
      last edited by

      @Shen:

      The problem is this line in your gcode:
      "G1 S1 X50 Y50 F5000: FRONT LEFT TO HEAT UP"
      You used a colon instead of a semi colon. It's a part of your starting gcode that's why none of your file works. I should have used some kind of gcode error handling, but I haven't got a change to work on it yet.

      Well, so I did. Doh! Thank you for spotting that. Page works as expected now. (As you knew it would. :- ) )

      1 Reply Last reply Reply Quote 0
      • Shenundefined
        Shen
        last edited by

        @lignumaqua:

        @Shen:

        The problem is this line in your gcode:
        "G1 S1 X50 Y50 F5000: FRONT LEFT TO HEAT UP"
        You used a colon instead of a semi colon. It's a part of your starting gcode that's why none of your file works. I should have used some kind of gcode error handling, but I haven't got a change to work on it yet.

        Well, so I did. Doh! Thank you for spotting that. Page works as expected now. (As you knew it would. :- ) )

        No problem, I just added some simple error handling code that would prevent problems like that.

        1 Reply Last reply Reply Quote 0
        • lignumaquaundefined
          lignumaqua
          last edited by

          Shen - ran another test today. Your app predicted a print time of 2 hours and 10 seconds. Actual time taken was 2 hours and 14 seconds. Pretty darn good! 🙂

          1 Reply Last reply Reply Quote 0
          • Shenundefined
            Shen
            last edited by

            @lignumaqua:

            Shen - ran another test today. Your app predicted a print time of 2 hours and 10 seconds. Actual time taken was 2 hours and 14 seconds. Pretty darn good! 🙂

            Good to know. The actual time always seems 5% slower than the predicted time. So I applied a 1.05 factor to the time estimation, the result became very accurate after that.

            1 Reply Last reply Reply Quote 0
            • Whitewolfundefined
              Whitewolf
              last edited by

              @Shen:

              @lignumaqua:

              Shen - ran another test today. Your app predicted a print time of 2 hours and 10 seconds. Actual time taken was 2 hours and 14 seconds. Pretty darn good! 🙂

              Good to know. The actual time always seems 5% slower than the predicted time. So I applied a 1.05 factor to the time estimation, the result became very accurate after that.

              Cant wait to see this integrated into the web interface. This with a realtime gcode visualizer will bring it up to par with Simplify3D

              Exploring the universe wherever the tech blows

              1 Reply Last reply Reply Quote 0
              • minimundefined
                minim
                last edited by

                Great work. Always wondered why the slicers didn't implement a feature like this. Having this in the interface would be awesome. I'd love to see a estimated column in the files section so I can have a quick look to see how long time it would use to print a certain item.

                1 Reply Last reply Reply Quote 0
                • Whitewolfundefined
                  Whitewolf
                  last edited by

                  @minim:

                  Great work. Always wondered why the slicers didn't implement a feature like this. Having this in the interface would be awesome. I'd love to see a estimated column in the files section so I can have a quick look to see how long time it would use to print a certain item.

                  that is a great idea +1

                  Exploring the universe wherever the tech blows

                  1 Reply Last reply Reply Quote 0
                  • AndreSundefined
                    AndreS
                    last edited by

                    yes, the idea is great, but…
                    everytime you go into the files folder the duet has to transfer the complete gcode to the web interface, so that it can calculate and display the estimated print time. If you have several large (>10MB) files, it can take some time. Are you sure, you will wait every time several 10s of seconds for the page to load?

                    I think a button for every file you can click and the print time will be calculated and displayed in the column will be better,

                    All things have pros and cons.

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

                      I have it in mind to have the firmware run gcode files in simulation mode when the printer is otherwise idle, so that it can build up a database of how long each file will take to print. But that won't happen until I have converted the firmware to use an RTOS, which in turn means that it won't be implemented for the Duet 0.6 or 0.8.5.

                      DWC already maintains a cache of data about gcode files on the SD card. So a facility whereby you can ask DWC for a print time estimate and it runs this program to generate one would work quite well, because the result could be added to the cached file information.

                      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
                      • okerchoundefined
                        okercho
                        last edited by

                        Just checking this (the page is awesome!) I'm not quite sure about what parameter goes where…

                        Maximum Speed: M203 ; Set maximum speeds (mm/min)
                        Print Acceleration: M201 ; Set accelerations (mm/s^2)
                        Travel Acceleration: M201 ; Set accelerations (mm/s^2)
                        Jerk: M566 maybe??

                        Can someone confirm? 😄

                        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
                        • Guyarosundefined
                          Guyaros
                          last edited by

                          @okercho:

                          Just checking this (the page is awesome!) I'm not quite sure about what parameter goes where…

                          Maximum Speed: M203 ; Set maximum speeds (mm/min)
                          Print Acceleration: M201 ; Set accelerations (mm/s^2)
                          Travel Acceleration: M201 ; Set accelerations (mm/s^2)
                          Jerk: M566 maybe??

                          Can someone confirm? 😄

                          Regards

                          Indeed.

                          I tested this calculator for several models I printed, with print time from 30[min] to 4[hours] depending on the model, and the results were very accurate, within +-1[min] which could be the time of hotend heating.

                          So, thanks for the great tool.
                          I hope it will be implemented in DWC.

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

                            In my case is not accurate, that's why I'm asking if the values I'm using are the right ones… the jerk (is M566 then?) seems not to be OK, it failed in a 6h print in more than 1h... :S

                            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
                            • Shenundefined
                              Shen
                              last edited by

                              @okercho:

                              In my case is not accurate, that's why I'm asking if the values I'm using are the right ones… the jerk (is M566 then?) seems not to be OK, it failed in a 6h print in more than 1h... :S

                              Regards

                              The unit used in config.g is different from the unit used in the tool.
                              For maximum speed(M203) and Jerk(M566) the unit is mm/min in the config.g file, but mm/s for the tool. You need to divide the values for M203 and M566 by 60. If you still have problems, you can upload your gcode so I can take a look.

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

                                Makes sense, I will check and let you know 🙂

                                Thanks!

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