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

    Layer count in DWC progress display

    Scheduled Pinned Locked Moved Solved
    Duet Web Control
    6
    15
    974
    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.
    • DaveAundefined
      DaveA @dc42
      last edited by

      @dc42 I'm updating my last reply to report that every .gcode file that I upload shows up with a 10mm object height. I've tried using Prusa Slicer and S3D with the same results. Actually all files uploaded in the last 5 days are 10mm.
      Just updated to RC8 and DWC 2.1.3 with no change.

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

        Please make available to us a sample file that incorrectly causes RRF to report 10mm object 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
        • DaveAundefined
          DaveA
          last edited by

          Here it is.

          Coupler v3 large.gcode

          1 Reply Last reply Reply Quote 0
          • Danalundefined
            Danal
            last edited by Danal

            Yeah, there is no tag in an S3D generated gcode-file directly for "Object Height" (or most slicers, for that matter).

            I took another look at the code, and RRF appears to be scanning for G0 or G1 commands, highest Z value it can find, or really the last value in the file it can find, skipping those in G91 relative mode, etc. It derives object height from that last one it finds.

            The last few statements in your file are:

            ; layer end
            M106 P2 S0	; case lights off
            M104 S0 	; turn off temperature
            M140 S0	; turn off heatbed
            G1 X0 Y200 F1800	;
            G1 Z10
            M84   	 ; disable motors
            M107	 ; turn off fan
            ; Build Summary
            ;   Build time: 1 hour 24 minutes
            ;   Filament length: 1363.3 mm (1.36 m)
            ;   Plastic volume: 3279.09 mm^3 (3.28 cc)
            ;   Plastic weight: 4.10 g (0.01 lb)
            ;   Material cost: 0.10
            

            A few thousand lines up from that (line 116782 in the gcode file) is the actual slicer generated G1 with the largest Z:

            G1 Z31.544 F1002
            

            RRF is finding G1 Z10 that just before the end of the file (line 6 above, line 117118 in the actual file). I believe this is coming from end gcode in S3D. S3D GUI actually calls this the "scripts" tab in a 'process', and it is the "Ending Script" sub-tab. So check all your processes if you are using multiples.

            Either take the 'G1 Z10' out, or make it relative (G91 first) or similar.

            Delta / Kossel printer fanatic

            DaveAundefined 1 Reply Last reply Reply Quote 0
            • DaveAundefined
              DaveA @Danal
              last edited by

              @Danal Bingo!!
              Thanks for that. I never thought that the software would walk through the entire file looking for Z move commands. I expected that it would be something fancier than that but I guess it works unless you to want to
              move the head out of the way at the end.

              Thanks again.

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

                You can make RRF ignore that G1 Z10 line when scanning for object height by adding a comment beginning ";E" or "; E" (without the quotation marks) at the end of that line:

                G1 Z10 ; E

                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

                demonlibraundefined 1 Reply Last reply Reply Quote 0
                • DeadNewbieundefined
                  DeadNewbie
                  last edited by

                  I have a similar issue, but only in S3D,

                  0b2c114b-0f38-4926-9a21-6d9b30a15b22-image.png

                  I can see it is detecting the layer height correctly, and I have scanned the file for any G1 Z comands after the end of the parts G-code, but cant find any.

                  I am at a loss, can someone take a look at my file and tell me what I am doing wrong?

                  DWC 2.0.7
                  Firmware 2.05.1

                  Link to the file on my NAS

                  Thanks in Advance

                  Michael

                  Phaedruxundefined 1 Reply Last reply Reply Quote 0
                  • Phaedruxundefined
                    Phaedrux Moderator @DeadNewbie
                    last edited by

                    @DeadNewbie Its in your end code

                    ; layer end
                    M104 S0 ; turn off extruder
                    M140 S0 ; turn off bed
                    M107
                    G0 Y190 Z190 X10
                    M84 ; disable motors
                    

                    G0 Y190 Z190 X10

                    Z-Bot CoreXY Build | Thingiverse Profile

                    1 Reply Last reply Reply Quote 0
                    • DeadNewbieundefined
                      DeadNewbie
                      last edited by

                      I will have a look, but I thought RRF ignored G0 Z?

                      Thanks for looking.

                      And yes you are correct, just tried it, I will amend the end scipt.

                      Thank you

                      1 Reply Last reply Reply Quote 0
                      • demonlibraundefined
                        demonlibra @dc42
                        last edited by

                        @dc42 It seems firmware parsing gcode and find last command "G1 Z..." to determine the height of the part.
                        Maybe it is better searching last command "G1 Z..." before last command "G1 ..... E...." to determine real printing height.

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

                          @demonlibra you can get RRF to ignore that line by putting a command starting with ;E or ; E at the end of it.

                          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