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

    [3.5b1+] Inaccurate print dimensions

    Scheduled Pinned Locked Moved
    Beta Firmware
    6
    43
    2.3k
    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.
    • Diamondbackundefined
      Diamondback @dc42
      last edited by Diamondback

      @dc42 Two more images. The first shows the difference between a "well" printed (3.4.5) MFM housing variation and a faulty (3.5b1+) one, note the stark difference in the height of the posts, this is not a result of the viewing angle. Also note the bulging extrusion again. (one is rotated 180°, so don't be confused by the different sides being visible)
      IMG_20230113_182118.jpg

      This one is the faulty one alone, note how clearly the hole in the front is not round at all, again this not an illusion from the photo.
      IMG_20230113_182153.jpg

      (Sorry for the weird colors in the photos, looks like my phone is doing some over the top HDR stuff or something...)

      1 Reply Last reply Reply Quote 1
      • Philippe71undefined
        Philippe71 @dc42
        last edited by

        @dc42
        There are 2 Z motors

        MaxGyverundefined 1 Reply Last reply Reply Quote 1
        • MaxGyverundefined
          MaxGyver @Philippe71
          last edited by

          @dc42

          I can confirm the problem. With 3.5b1+ layers seem periodically “squished” in Z direction, almost like Z-Wobble.

          My setup:

          Duet36HC with 4 Z-Leadscrews.
          Bed tramming is performed before every print, and mesh compensation is active.
          I also redid the mesh probing after updating, just to be sure.

          1 Reply Last reply Reply Quote 1
          • Diamondbackundefined
            Diamondback
            last edited by

            @dc42 anything else we can do to help you diagnose/replicate the issue? Looks like so far, everyone here has more than one Z stepper and is using active bed tramming?

            oliofundefined 1 Reply Last reply Reply Quote 0
            • oliofundefined
              oliof @Diamondback
              last edited by

              @Diamondback maybe try printing without bed compensation to see if that triggers the same issue. Use a raft if required to ensure bed is not causing issues.

              <>RatRig V-Minion Fly Super5Pro RRF<> V-Core 3.1 IDEX k*****r <> RatRig V-Minion SKR 2 Marlin<>

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

                @oliof said in [3.5b1+] Inaccurate print dimensions:

                @Diamondback maybe try printing without bed compensation to see if that triggers the same issue. Use a raft if required to ensure bed is not causing issues.

                An excellent idea! Right now I don't know what is causing this issue. Knowing whether bed compensation is implicated would help me to narrow it down.

                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 1
                • Diamondbackundefined
                  Diamondback
                  last edited by

                  Ok cool, I can disable both mesh compensation and active leveling. (the leveling part before each print is not really needed anymore anyway since I upgraded my spindles to finder pitch)

                  oliofundefined 1 Reply Last reply Reply Quote 0
                  • oliofundefined
                    oliof @Diamondback
                    last edited by

                    @Diamondback if you disable two things, please make three runs: One without both, and one where either or is disabled

                    @dc42 the reason I thought of that is that elsewhere I recently helped debug an issue that looked like bad segmentation, but it was low Z jerk and acceleration combined with bed compensation that looked like the bulging corner issue.

                    <>RatRig V-Minion Fly Super5Pro RRF<> V-Core 3.1 IDEX k*****r <> RatRig V-Minion SKR 2 Marlin<>

                    1 Reply Last reply Reply Quote 0
                    • IndeX4Dundefined
                      IndeX4D
                      last edited by IndeX4D

                      My print dimensions are correct, but when start a new print the z axis is exactly 0.2mm to deep.
                      +
                      After pause, It seemed like the z offset has completely gone. Should I make a new thread about this?

                      -4 z-axis
                      -Axis compensation active

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

                        @IndeX4D said in [3.5b1+] Inaccurate print dimensions:

                        My print dimensions are correct, but after every print, but every new print hast the Z axis 0.2 to deep.
                        +
                        After pause, It seemed like the z offset has completely gone. Should I make a new thread about this?

                        Yes please! Include your config file, and whether you are using babystepping or any other use of M290.

                        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
                        • Diamondbackundefined
                          Diamondback
                          last edited by

                          @dc42
                          Ok so, here are the results from 3.5b1+:

                          • Active leveling before the print + mesh bed compensation active -> Broken
                          • Only mesh bed compensation -> Broken
                          • Only active leveling -> No issue

                          So it appears that mesh bed compensation is indeed related in some way.

                          dc42undefined 2 Replies Last reply Reply Quote 1
                          • dc42undefined
                            dc42 administrators @Diamondback
                            last edited by

                            @Diamondback thanks, that's very useful.

                            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 @Diamondback
                              last edited by

                              @Diamondback

                              • Do you have any layer change script in those models, or anything else happening during the print (after initial heating etc.) other than G1 commands?
                              • Do you have daemon.g running?

                              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

                              Diamondbackundefined 1 Reply Last reply Reply Quote 1
                              • Diamondbackundefined
                                Diamondback @dc42
                                last edited by

                                @dc42 Not exactly sure what you mean with the first point, I can share the gcode though.
                                AccuracyDebug.gcode

                                As for daemon, yes, at that point it was a regular daemon.g with NO loop in it that has this content:

                                if state.status == "idle" && global.deactivateToolAfterFilamentChange == true
                                	echo "Unloading tool after filament change"
                                	T-1
                                
                                set global.deactivateToolAfterFilamentChange = false
                                
                                if state.status == "processing" && state.gpOut[1].pwm > 0 && job.layer == 3
                                	M98 P"/macros/Misc/Lights/Off" 
                                
                                dc42undefined 1 Reply Last reply Reply Quote 0
                                • dc42undefined
                                  dc42 administrators @Diamondback
                                  last edited by dc42

                                  @Diamondback I tried to reproduce this on my tool changer, which uses a 6HC, but the print using the current RRF 3.5 build was the same height as the one using RRF 3.4.5 and doesn't show the layer artefacts. I had mesh bed compensation enabled.

                                  Have you time to run some more tests? If so:

                                  • Please try the latest RRF build for the 6HC at https://www.dropbox.com/sh/5vxz29a7400gwcy/AAAPexxpGsP0LMo0jEFOOCqVa?dl=0
                                  • If it shows the same issue, try stopping the daemon task (rename daemon.g to something else)
                                  • If it still shows the same issue, try disabling bed compensation and instead enable segmentation using M669 S100 T10 (preferably, replace the 10 by the mesh spacing you use). This will tell me whether it is the bed compensation that provokes the issue, or the segmentation that occurs when bed compensation is enabled.

                                  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

                                  Diamondbackundefined 1 Reply Last reply Reply Quote 1
                                  • Diamondbackundefined
                                    Diamondback @dc42
                                    last edited by

                                    @dc42 Currently printing some actual parts, will do these tests afterwards. 👍

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

                                      @Diamondback do you have bed compensation taper enabled?

                                      EDIT - yes I see that you have, from your config.g. Does disabling taper make the problem go 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

                                      Diamondbackundefined 1 Reply Last reply Reply Quote 1
                                      • Diamondbackundefined
                                        Diamondback @dc42
                                        last edited by

                                        @dc42 Yes I do, will test that as well.

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

                                          @Diamondback did you have a chance to run any tests?

                                          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

                                          Diamondbackundefined 2 Replies Last reply Reply Quote 1
                                          • Diamondbackundefined
                                            Diamondback @dc42
                                            last edited by Diamondback

                                            @dc42 Literally printing tests all day already, I have issues replicating the issue on any of the 3.5 builds and trying to find out what changed. Since you mentioned daemon.g as a possible cause I'm reverting some changes there (most notably going back to the 10s dameon stuff rather than having an infinite loop in there)

                                            I'll keep you posted.

                                            IMG_20230206_121341.jpg

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