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

Simulated Print Time in G-Code Files

Scheduled Pinned Locked Moved
Firmware wishlist
7
14
2.1k
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.
  • undefined
    R3play
    last edited by 11 Jan 2019, 15:08

    Hi there,

    I don't know if this has been suggested before (Atleast I couldn't find anything).
    But I would really like it if the simulated print time would be added in the G-Code files.

    Example:
    0_1547219212363_Screenshot_57.jpg

    That way you only would have to do the simulation once (if you don't delete the file) and just see it at a glance.

    What do you guys think?

    undefined 1 Reply Last reply 11 Jan 2019, 15:13 Reply Quote 0
    • undefined
      wilriker @R3play
      last edited by wilriker 1 Nov 2019, 15:13 11 Jan 2019, 15:13

      @r3play This has been requested before and is implemented in DWC2 (currently beta/RC status).

      P.S.: This also lists the slicer's calculated print time (if recognized).

      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
      • undefined
        R3play
        last edited by R3play 1 Nov 2019, 15:14 11 Jan 2019, 15:14

        Awesome!
        Then sorry for my double request 😄

        undefined 1 Reply Last reply 11 Jan 2019, 15:15 Reply Quote 0
        • undefined
          wilriker @R3play
          last edited by 11 Jan 2019, 15:15

          @r3play And here's a quick screenshot how that looks:

          0_1547219730354_DWC2_filelist.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 1
          • undefined
            dc42 administrators
            last edited by 11 Jan 2019, 18:03

            The simulated time is shown by recent versions of PanelDue firmware too.

            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

            undefined 1 Reply Last reply 11 Jan 2019, 18:09 Reply Quote 0
            • undefined
              garyd9 @dc42
              last edited by 11 Jan 2019, 18:09

              @dc42

              In the case of a gcode file that has NOT been simulated, could the firmware append the actual print time instead (once the file is done printing, of course.) There are many files I've printed (but not simulated.)

              "I'm not saying that you are wrong - I'm just trying to fit it into my real world simulated experience."

              1 Reply Last reply Reply Quote 1
              • undefined
                stevenwm
                last edited by 12 Jan 2019, 05:35

                Any chance of supporting the M73 command that Slic3r PE can insert into the GCode file? At 1 minute intervals in the GCode it inserts something like "M73 P25 R35" P being the percentage done, and R being the minutes remaining.

                If it is enabled, the very first command in the GCode is a M73 with the full remaining time of the file.

                undefined 1 Reply Last reply 12 Jan 2019, 23:37 Reply Quote 0
                • undefined
                  Phaedrux Moderator @stevenwm
                  last edited by 12 Jan 2019, 23:37

                  @stevenwm Aren't those values only valid when you're using a Prusa printer and their firmware, since Slicer uses the marlin motion planner for it's time estimate and it knows the acceleration and jerk values?

                  Z-Bot CoreXY Build | Thingiverse Profile

                  undefined 1 Reply Last reply 20 Jan 2019, 23:00 Reply Quote 0
                  • undefined
                    stevenwm @Phaedrux
                    last edited by 20 Jan 2019, 23:00

                    @phaedrux I don't think so... I use Slic3r PE with my Rockstock Max.. The time estimates inserted by M73 are the same ones as shown in Slic3r itself. The time estimate as given by Slic3r is always spot on for me within 5 seconds and always has been.

                    undefined 1 Reply Last reply 20 Jan 2019, 23:18 Reply Quote 0
                    • undefined
                      Phaedrux Moderator @stevenwm
                      last edited by 20 Jan 2019, 23:18

                      @stevenwm Interesting. Are you using Marlin, or RepRap Gcode flavour in Slic3r?

                      For me the Slic3r estimate is about 30 minutes faster than actual print time.

                      Z-Bot CoreXY Build | Thingiverse Profile

                      1 Reply Last reply Reply Quote 0
                      • undefined
                        Wyvern
                        last edited by 20 Jan 2019, 23:38

                        I'm not certain, but since the recent update my slicing/printing times are way out of whack, For instance I'm printing something that had a 50hr estimate, it's now hour 54 and I have another 30% to go!

                        How long does it take for the machine to "simulate" a print?

                        undefined 1 Reply Last reply 21 Jan 2019, 10:57 Reply Quote 0
                        • undefined
                          wilriker @Wyvern
                          last edited by 21 Jan 2019, 10:57

                          @wyvern said in Simulated Print Time in G-Code Files:

                          How long does it take for the machine to "simulate" a print?

                          That heavily depends on the complexity of the part. Usually up to a few minutes.

                          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

                          undefined 1 Reply Last reply 21 Jan 2019, 16:37 Reply Quote 0
                          • undefined
                            Wyvern @wilriker
                            last edited by 21 Jan 2019, 16:37

                            @wilriker 0_1548088528347_Bowser print time.png

                            Almost done, Cura said 2 days 4 hours, 890gr filiment, I had to swap the roll with 50gr left, probably at 1200gr!

                            It was almost spot on before the update, not sure what changed- doesn't really matter though, it ends when it ends.

                            undefined 1 Reply Last reply 21 Jan 2019, 20:21 Reply Quote 0
                            • undefined
                              wilriker @Wyvern
                              last edited by 21 Jan 2019, 20:21

                              @wyvern According to your screenshot it did get the required length of filament about right. You need to check the density setting for the filament selected in Cura if this matches your used filament. Otherwise weight calculations are off - like in this case.

                              Regarding time estimates. Get the Printer Settings plugin and check/adjust the accel and max speed settings. Doing so brought the estimates very close for me.

                              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