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

    Firmware 3.4b7 - firmware retraction bug

    Scheduled Pinned Locked Moved
    Beta Firmware
    7
    57
    3.5k
    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.
    • danzaywerundefined
      danzaywer @dc42
      last edited by

      @dc42
      I can confirm this strange behavior. I have an afterburner direct and from 3.4b6 I started to have problems with clogging in the parts where there were many retraction commands during the prints and the sound of the retraction was accentuated compared to 3.3. Same with 3.4b7. The parameters were M207 S0.5 F2100 Z0.0, I changed to M207 S0.2 F500 and for now it seems that the clogging is gone.
      No pressure advance.

      1 Reply Last reply Reply Quote 0
      • bbergerundefined
        bberger
        last edited by bberger

        I can also confirm that something is off with PA in the 3.4 beta release(s?). I just upgraded from 3.3 to the 3.4b7 and with PA on the printer doesn't feed enough filament anymore.

        Basically similar behaviour you'd get when either turning up PA too much (I use 0.15 on a very short bowden tube on a flying extrude) or use too low retraction speeds.

        When I turn off PA the issue is gone.

        Argoundefined 1 Reply Last reply Reply Quote 0
        • Argoundefined
          Argo @bberger
          last edited by

          @bberger

          I had similar issues with input shaping + pressure advance in 3.4b6:
          https://forum.duet3d.com/topic/26062/3-4-0beta6-new-input-shaper-disturb-pressure-advance/8?_=1641083316188

          Maybe there are issues with higher PA values in general.

          natthapol.vundefined 1 Reply Last reply Reply Quote 0
          • natthapol.vundefined
            natthapol.v @Argo
            last edited by

            @argo I have not had my PA activated for this issue to happen. I believe this issue neither related to Pressure Advance nor Input Shaping.

            dc42undefined 1 Reply Last reply Reply Quote 0
            • dc42undefined
              dc42 administrators @natthapol.v
              last edited by dc42

              Can any of you provide a short print (preferably only one layer) and associated config.g file that reliably demonstrates this issue? Preferably in the form of the sound being different between RRF 3.3 and 3.4beta7 when the printer settings are identical. I don't mind whether PA is needed or not.

              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

              natthapol.vundefined 1 Reply Last reply Reply Quote 0
              • natthapol.vundefined
                natthapol.v @dc42
                last edited by

                @dc42 Hi, I will setup some print files and all the associated settings and send it to you in couple of hours.

                dc42undefined 1 Reply Last reply Reply Quote 0
                • dc42undefined
                  dc42 administrators @natthapol.v
                  last edited by

                  @natthapol-vanasrivilai @danzaywer has either of you been able to produce a GCode file and associated config.g file that reliably demonstrate this problem?

                  @Argo if your issue only occurs when high PA and IS are together then I think it is a different issue. We already know that when input shaping is enabled, PA is affected and may need to be tuned again.

                  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

                  danzaywerundefined natthapol.vundefined Argoundefined 3 Replies Last reply Reply Quote 0
                  • danzaywerundefined
                    danzaywer @dc42
                    last edited by

                    @dc42 My current configuration would not work on 3.3, I have to bypass the toolchange macros. Anyway, can I downgrade from 3.4b7 to 3.3 simply by uploading the 3.3 files?

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

                      @danzaywer said in Firmware 3.4b7 - firmware retraction bug:

                      @dc42 Anyway, can I downgrade from 3.4b7 to 3.3 simply by uploading the 3.3 files?

                      If you are running the Duet in standalone mode, then yes.

                      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

                      danzaywerundefined natthapol.vundefined 2 Replies Last reply Reply Quote 0
                      • natthapol.vundefined
                        natthapol.v @dc42
                        last edited by

                        @dc42 Hi sorry that it took too long on my part.
                        I've attached the zip containing the files from SD card.

                        config, gcode, filament and macros that are used in startup/ending sequences.

                        The forum doesn't allow me to upload zip file, so please rename the file extension to ".zip" afterwards
                        repo.txt

                        The attached gcode file is just a bunch of 5x0.2mm hollowed cylinders. The machine and gcode is setup to do firmware retraction.

                        1 Reply Last reply Reply Quote 0
                        • Argoundefined
                          Argo @dc42
                          last edited by

                          @dc42

                          Coming from 3.3 the same PA values (with input shaper enabled) result in more or less bulging corners with 3.4b7. Increasing PA (from 0.065 to almost 0.1) then to get almost as sharp corners as with 3.3 results in starving infill lines which do not connect properly to the perimeter.
                          I‘ve added pics in my other thread.

                          1 Reply Last reply Reply Quote 0
                          • danzaywerundefined
                            danzaywer @dc42
                            last edited by

                            @dc42 I still can't downgrade but I found out what could have caused the problem: the M563 command in config.g (but also from the console) resets the retraction of the tool, so M207 must follow M563.

                            1 Reply Last reply Reply Quote 0
                            • natthapol.vundefined
                              natthapol.v @dc42
                              last edited by

                              @dc42 I have found something interesting. Since the firmware retraction behave unexpectedly, I've switch to slicer retraction and ran some test prints. The retract/unretract or let say any commands that involve extruder movement. Sometime the extruder move at a very high speed as well (Command that involve pure extruder move e.g. G1 E5).

                              This show that the issue is not purely related to retractions.

                              I think it will be easier to debug the issue by simply setup a gcode with a bunch of G1 E** commands and observe the extruder speed.

                              Hope it help for further investigation.

                              dc42undefined 1 Reply Last reply Reply Quote 0
                              • dc42undefined
                                dc42 administrators @natthapol.v
                                last edited by

                                @natthapol-vanasrivilai I've run your test file several times using both RRF 3.3 and 3.4b7, but I was unable to detect any differences in the sound. I disconnected the X and Y motors so that I could hear only the extruder motor.

                                However, when I enabled debug output I did see a different between RRF versions. This difference might occasionally cause the first 2, 4 or 8 microsteps of an extruder movement to be performed rapidly instead of at the correct speed. It is possible that this might explain the difference in sound you heard.

                                I have corrected this and put a new RRF firmware build at https://www.dropbox.com/sh/up0gytwkxcn4if2/AACO6rIrTu5kPSgMxOmjmxdZa?dl=0. Please try 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

                                Diamondbackundefined natthapol.vundefined 3 Replies Last reply Reply Quote 0
                                • Diamondbackundefined
                                  Diamondback @dc42
                                  last edited by

                                  @dc42 When this behavior happens to me, it lasts for the entire commanded movement of the extruder, so I don't think that anything about a few microsteps would create that sound. I'm confused why it only happens to rarely, just yesterday night it happened again during my normal filament unload macro.

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

                                    @diamondback can you provide a test file that reproduces this behaviour?

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

                                      @dc42 I'm afraid I can't, it happens seemingly randomly when unloading filaments via the DWC feature. The gcode that is running when it happens is posted in my first post in this thread.
                                      For what it's worth, it's a TC design with 4 tools, it seems to happen on all of them from time to time (ie. I've seen it happen on every tool at least once, it's not restricted to a specific tool)

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

                                        @diamondback the G91 and G90 commands in that macro will have no effect. You should replace G91 in that macro by M83 and remove the G90 line. That will probably fix the issue for 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

                                        Diamondbackundefined 1 Reply Last reply Reply Quote 0
                                        • natthapol.vundefined
                                          natthapol.v @dc42
                                          last edited by

                                          @dc42 I'll test with the attached firmware and let you know how it is

                                          1 Reply Last reply Reply Quote 0
                                          • natthapol.vundefined
                                            natthapol.v @dc42
                                            last edited by

                                            @dc42 Unfortunately, the issue is still persist with the 3.4b7+3 firmware.

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