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

    Layer and filament estimation not working

    Scheduled Pinned Locked Moved
    General Discussion
    5
    19
    2.0k
    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.
    • antoncheezundefined
      antoncheez
      last edited by

      Hello,

      I am running a duet wifi in a Core XY on firmware version 1.20. I have the file progress time estimation field populated, but the layer and filament fields are N/A. I don't know how to fix this, I have seen examples of it working and I cannot find the discrepancy between my non working setup and others working setups. I am running prusia slicer 1.39.1a, i have seen this function work in this version of slicer. Any insight anyone could give would be much appreciated. Thank you.

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

        Please share a gcode file that demonstrates the problem.

        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
        • antoncheezundefined
          antoncheez
          last edited by

          http://bit.ly/2nPk5Mo here is a file that does as described

          1 Reply Last reply Reply Quote 0
          • antoncheezundefined
            antoncheez
            last edited by

            I have solved the problem. The .ngc file format needs to be a .gcode file format upon output. I just never thought this could be the issue. Thanks for your attention

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

              I'm glad you solved it. But I am curious: why did the file have a .ngc extension, when it appears to be a standard GCode file for 3D printers? I thought all the commonly used slicers generate files with a .g or .gcode extension.

              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
              • antoncheezundefined
                antoncheez
                last edited by

                the default profile in my sli3er config is .ngc because i started out with an absolutely ancient machinekit setup.

                1 Reply Last reply Reply Quote 0
                • Barracuda72undefined
                  Barracuda72
                  last edited by

                  Hi i Capture this Thread for a very similar problem.
                  Updated to the actual rc2 version…and change the starting code of S3D so i´m not sure when the prob exactly started.
                  I dont get a Layer time..for the DWC theres only one layer..a very long layer 😉
                  I changed some lines in my starting code:

                  G21 ;metric values
                  G90 ;absolute positioning
                  M82
                  M107 ;start with the fan off
                  G28 ;move to endstops
                  G29 S1
                  G92 E0 ;zero the extruded length
                  G1 X-44 Y-75 Z0.2 E0.5 F7000 ; Drop to bed
                  M117 Preparing...;Put message on LCD screen
                  G1 X0 Y-90 E10 F500 ; Extrude 10mm of filament in a 4cm line
                  G1 X44 Y-75 E12 F500 ; Extrude 12mm of filament in a 4cm line
                  G92 E0 ; zero the extruded length
                  G1 E-0.4 F500 ; Retract a little
                  G1 X87 Y-17 Z1 F6000 ; Quickly wipe away from the filament line
                  G1 Z5 ; Raise and begin printing.
                  M117 Printing...;Put printing message on LCD screen

                  guess before that layer time in DWC was ok..but how could that gcode prevent DWC to show correct layer time?

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

                    Try 1.21RC3 tomorrow when I release it, and if the problem is still there, make the gcode file available to me.

                    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
                    • Barracuda72undefined
                      Barracuda72
                      last edited by

                      made a Scrrenshot..print is already 1:45:00 in progress and still on first layer 😉 https://imgur.com/a/q3tmb of the DWC

                      and this happens with all prints so far

                      1 Reply Last reply Reply Quote 0
                      • Barracuda72undefined
                        Barracuda72
                        last edited by

                        ok..updated to RC3 but the problem is the same…only one big layer in the timer..

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

                          I can't do anything about this without a sample GCode file from you.

                          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
                          • Barracuda72undefined
                            Barracuda72
                            last edited by

                            will upload it later…have to test if its slicer specific

                            1 Reply Last reply Reply Quote 0
                            • Barracuda72undefined
                              Barracuda72
                              last edited by

                              ok..made a calibration cube..
                              1. with Cura 15.04
                              https://drive.google.com/file/d/15f5AtY0VROXYdu-Rqe2Fgv7t0LyyHXp-/view?usp=sharing

                              2. with Simplify3D
                              https://drive.google.com/file/d/17FLBhOeISPs6M6-l8X4HPyd2fQa3IvDW/view?usp=sharing

                              most settings are similar except in the S3D file the printer do that little wipe line before the print. Even tried to erase the 2nd G92E0

                              With the Cura file the layer informations are ok..he count each layer.

                              With the S3D file its only 1 long layer in the DWC…first layer 1. sec ( thats the prime/wipe line in my starting code)..2nd layer...endless

                              DWC after the S3D print: "Layer: 2 of 83, Filament Usage: 1598.2mm of 1601.2mm (3.0mm remaining)"

                              strange

                              hmm I should start doing LEGO bricks instead of Calibration Cube..so they are at least useful 😉

                              1 Reply Last reply Reply Quote 0
                              • Barracuda72undefined
                                Barracuda72
                                last edited by

                                Already had the spare time to look at the gCode files?

                                1 Reply Last reply Reply Quote 0
                                • tbahreundefined
                                  tbahre
                                  last edited by

                                  Having layer and estimation problems myself. I posted thinking it was a problem with Cura but I'm not so sure:
                                  https://www.duet3d.com/forum/thread.php?pid=40787#p40787
                                  Also: https://www.duet3d.com/forum/thread.php?pid=40843#p40843

                                  1 Reply Last reply Reply Quote 0
                                  • c310undefined
                                    c310
                                    last edited by

                                    i have similar issue.

                                    you can see that on the picture it shows 96 layers. however file had 6 layers or so.
                                    even looking at progress indicator of 50% and 2 layers printed it gives an idea that there is no 96 layers 🙂

                                    https://1drv.ms/u/s!AhtLyZEPcjv9gc48ed0BtcWa-GX5xQ link to gcode file

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

                                      Thanks, that's on my list to investigate before the 1.21 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
                                      • dc42undefined
                                        dc42 administrators
                                        last edited by

                                        @c310:

                                        i have similar issue.

                                        …

                                        you can see that on the picture it shows 96 layers. however file had 6 layers or so.
                                        even looking at progress indicator of 50% and 2 layers printed it gives an idea that there is no 96 layers 🙂

                                        The reason it thinks you have 96 layers is that your print is only 0.8mm high but you have 15mm of Z hop configured. The large amount of Z hop is confusing the code that works out the total number of layers.

                                        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
                                        • dc42undefined
                                          dc42 administrators
                                          last edited by

                                          @Barracuda72:

                                          ok..made a calibration cube..
                                          1. with Cura 15.04
                                          https://drive.google.com/file/d/15f5AtY0VROXYdu-Rqe2Fgv7t0LyyHXp-/view?usp=sharing

                                          2. with Simplify3D
                                          https://drive.google.com/file/d/17FLBhOeISPs6M6-l8X4HPyd2fQa3IvDW/view?usp=sharing

                                          most settings are similar except in the S3D file the printer do that little wipe line before the print. Even tried to erase the 2nd G92E0

                                          With the Cura file the layer informations are ok..he count each layer.

                                          With the S3D file its only 1 long layer in the DWC…first layer 1. sec ( thats the prime/wipe line in my starting code)..2nd layer...endless

                                          DWC after the S3D print: "Layer: 2 of 83, Filament Usage: 1598.2mm of 1601.2mm (3.0mm remaining)"

                                          strange

                                          hmm I should start doing LEGO bricks instead of Calibration Cube..so they are at least useful 😉

                                          The problem is this line:

                                          G1 X-44 Y-75 Z0.2 E0.5 F7000 ; Drop to bed

                                          The firmware treats it as a printing move because it contains both extrusion and XY movement. Z is very high at that point, which throws off the layer height computation. The workaround is to do the extrusion in a separate move.

                                          The reason that it worked in 1.20 is that in 1.21 the layer height code was changed to allow for slicers that use variable layer height.

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