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

Duet reporting inaccurate percentage.

Scheduled Pinned Locked Moved Unsolved
Duet Web Control
5
28
1.9k
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
    dc42 administrators
    last edited by 15 Apr 2020, 12:15

    Are you referring to the % complete reported by DWC, or by PanelDue?

    Those % complete figures are not based on object height, which is why your end GCode does not affect them. AFAIR the % complete figure is based on filament consumption vs. filament required (if the filament length required is available in the GCode file), otherwise on the percentage of the GCode file that has been processed.

    Your sample GCode file has these figures:

    ; filament used [mm] = 6904.1
    ; filament used [cm3] = 16.6
    
    ; total filament used [g] = 0.0
    ; total filament cost = 0.0
    

    The 6904.1mm figure is being picked up by RRF. Next time you print this file (or another file that shows the same issue), please monitor the Filament Usage value of the DWC status page towards the end of the print, to see whether it is converging towards the filament usage recorded in the GCode file, or towards a lower value.

    I note that your GCode file contains some negative extrusion amounts:

    G1 F8640.000
    G1 X18.241 Y12.662 E-0.33092
    G1 X19.422 Y11.978 E-0.31506
    G1 X20.660 Y11.628 E-0.29710
    G1 X21.913 Y11.463 E-0.29192
    G1 E-0.06500 F2100.00000
    

    I presume this means you have "wipe while retracting" or similar enabled in the slicer.

    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
    • undefined
      dc42 administrators
      last edited by 15 Apr 2020, 12:41

      I've just run that file in simulation mode. It finished just after reporting 88% complete with >1m of filament remaining. This suggests to me that either RRF is accumulating filament usage incorrectly, or that PrusaSlicer is reporting incorrect filament usage for the particular options you are using.

      I think that RRF may be being confused by wipe during retraction. Please can you try running that print in simulation mode and check that you get the same results as me (or run another file if you prefer, and note the % complete figure it reaches just before the end). Then slice that file again, turning off wipe-while-retract. Simulate that file and see if the behaviour is different.

      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 15 Apr 2020, 18:31 Reply Quote 1
      • undefined
        Turbo @dc42
        last edited by Turbo 15 Apr 2020, 18:31

        @dc42 running that .gcode I linked earlier shows a correct readout in simulation mode; reaching 100% as expected. I am referring to the DWC %

        EDIT: i ran the file that finished at 55% from earlier in simulation mode, and it showed proper percentage up to 100%

        Cant stop tuning wont stop tuning.
        Dbot, Custom i3, Voron 0&2

        undefined 1 Reply Last reply 16 Apr 2020, 09:40 Reply Quote 0
        • undefined
          dc42 administrators @Turbo
          last edited by dc42 16 Apr 2020, 09:40

          @Turbo said in Duet reporting inaccurate percentage.:

          @dc42 running that .gcode I linked earlier shows a correct readout in simulation mode; reaching 100% as expected. I am referring to the DWC %

          EDIT: i ran the file that finished at 55% from earlier in simulation mode, and it showed proper percentage up to 100%

          Strange, when I ran your file in simulation mode (using RRF 3.01-RC7) it definitely jumped from about 88% to 100%.

          I am fairly sure that wipe-while-retract is confusing the filament used accumulator, but I don't know if that is the only issue here. Can you re-slice one of your prints with wipe-while-retract disabled and see if the problem goes away?

          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
          • undefined
            dc42 administrators
            last edited by 16 Apr 2020, 19:11

            This is now fixed in the 3.01 source code and in the firmware binaries at https://www.dropbox.com/sh/3azy1njy3ayjsbp/AACquxr2m00eV568RZg5QG5wa?dl=0.

            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 16 Apr 2020, 19:48 Reply Quote 0
            • undefined
              Turbo @dc42
              last edited by 16 Apr 2020, 19:48

              @dc42 disabling wipe while retract solved it! Although am i able to use 3.01 with a duet 2 wifi board?

              Board: Duet WiFi 1.02 or later
              Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 2.05.1 (2020-02-09b1)
              Duet WiFi Server Version: 1.23 
              

              Cant stop tuning wont stop tuning.
              Dbot, Custom i3, Voron 0&2

              1 Reply Last reply Reply Quote 0
              • undefined
                dc42 administrators
                last edited by 16 Apr 2020, 19:55

                @Turbo said in Duet reporting inaccurate percentage.:

                Although am i able to use 3.01 with a duet 2 wifi board?

                Yes you can, however you will need to make substantial changes to your config.g file if you do upgrade. See https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview#Section_Summary_of_what_you_need_to_do_to_convert_your_configuration_and_other_files for the details.

                The fix will probably make it to RRF 2 eventually, but not until it has been in RRF3 long enough for me to be certain that it has no unexpected side effects.

                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 2 Replies Last reply 16 Apr 2020, 19:56 Reply Quote 0
                • undefined
                  Turbo @dc42
                  last edited by 16 Apr 2020, 19:56

                  @dc42 Got it, thanks. I always assumed the RRF 3 would only work for Duet 3 boards and later. IDK Why

                  Cant stop tuning wont stop tuning.
                  Dbot, Custom i3, Voron 0&2

                  1 Reply Last reply Reply Quote 0
                  • undefined
                    Turbo @dc42
                    last edited by Turbo 17 Apr 2020, 04:58

                    @dc42 After updating to RRF3.0 RC7, the issue is still present it seems. i have a current print about 50% done, however, the DWC only shows 6%, and i can watch it go up and down in percentage, which i dont think is supposed to happen. The object is consistent all the wey to the top, so there shouldnt be any large discrepancies that would affect %. This is with wipe while retract is on, because it does affect my print quality noticeably.

                    Cant stop tuning wont stop tuning.
                    Dbot, Custom i3, Voron 0&2

                    1 Reply Last reply Reply Quote 0
                    • undefined
                      dc42 administrators
                      last edited by 17 Apr 2020, 06:13

                      Yes the bug is present in the 3.01-RC7 release, but fixed in the post RC7 build that I linked to earlier.

                      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
                      • undefined
                        SpoonUnit
                        last edited by 15 Apr 2021, 10:16

                        I'm not sure if this issue is connected with my recent move to RRF3.3b2. Since I did, I've had a number of prints telling me they are over 100% complete. Querying the forum I found this thread, and the detail that completion calculation is based on GCODE-embedded filament usage.

                        In the GCODE file I see:

                        ; filament used [mm] = 13125.43
                        

                        In DWC, I see this at the end of the print during my cool down phase:

                        a818e4c0-3053-4c41-b862-f55085dd08f1-image.png
                        and
                        8f87567a-a58f-45e8-985a-ab3c796f57f9-image.png

                        The layer count is off, but the filament consumption seems to suggest the reported job completion level should be 99%, not 144.7%.

                        To add to the mix, I'm also testing ArcWelder, so the GCODE has G2/G3 commands scattered throughout.

                        undefined chrishammundefined 2 Replies Last reply 15 Apr 2021, 10:40 Reply Quote 0
                        • undefined
                          dc42 administrators @SpoonUnit
                          last edited by 15 Apr 2021, 10:40

                          One for @chrishamm.

                          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
                          • chrishammundefined
                            chrishamm administrators @SpoonUnit
                            last edited by 15 Apr 2021, 10:47

                            @spoonunit Please share the full G-code file and I'll have a look.

                            Duet software engineer

                            undefined 1 Reply Last reply 15 Apr 2021, 11:07 Reply Quote 0
                            • undefined
                              SpoonUnit @chrishamm
                              last edited by 15 Apr 2021, 11:07

                              @chrishamm here you go

                              seq26.gcode

                              undefined undefined 2 Replies Last reply 15 Apr 2021, 12:56 Reply Quote 1
                              • undefined
                                SpoonUnit @SpoonUnit
                                last edited by 15 Apr 2021, 12:56

                                It's even more exciting in simulation mode - getting to about 354% before then completing and setting itself to 100%.

                                1 Reply Last reply Reply Quote 0
                                • undefined
                                  dc42 administrators @SpoonUnit
                                  last edited by 28 Apr 2021, 11:03

                                  @spoonunit, please share your config.g fie.

                                  What sort of mixing extruder do you have? In your M567 command(s), is the total mix ratio 1.0?

                                  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 30 Apr 2021, 11:48 Reply Quote 0
                                  • undefined
                                    SpoonUnit @dc42
                                    last edited by 30 Apr 2021, 11:48

                                    @dc42 I'm not using mixing at all. There are no M567 commands.

                                    config.g

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