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

    Jerk & acceleration value change after Resume APF

    Scheduled Pinned Locked Moved Unsolved
    Beta Firmware
    5
    15
    575
    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.
    • R006undefined
      R006 @T3P3Tony
      last edited by

      @T3P3Tony
      no in config Acceleration is 3000mm/s2 and jerk is 300mm/s.

      T3P3Tonyundefined 1 Reply Last reply Reply Quote 0
      • T3P3Tonyundefined
        T3P3Tony administrators @R006
        last edited by

        @R006 ok so are the values that are restored related to anything in your settings or gcode file?

        www.duet3d.com

        JayTundefined 1 Reply Last reply Reply Quote 0
        • JayTundefined
          JayT @T3P3Tony
          last edited by

          @T3P3Tony :

          I use this version too and have observed same problems. The value of acceleration on resume is not something I am able to trace from gcode file or config. Its some random very high value like 20000 or 50000. even jerk changes.

          I have also observed, that despite setting max acceleration & speeds in config, its not limited on resume after power failure. Can you check this?

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

            @JayT @R006 in the forthcoming 3.5.0-rc.4 the M204 acceleration settings are restored when resuming after power fail.

            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

            JayTundefined R006undefined 2 Replies Last reply Reply Quote 1
            • JayTundefined
              JayT @dc42
              last edited by

              @dc42 :

              Noted.
              However, there are 2 more errors that appear on resume:
              a) tool0 was not driven because its heater temperature were not high enough. heater fault. Yet it resumes, but why this error?

              b) Loading the heightmap before setting duetZ0 - warning,

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

                @JayT regarding (a) it's your responsibility to use M116 or a similar command in your resurrect-prologue.g file to wait for temperatures to be reached. Are you doing that?

                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

                JayTundefined 1 Reply Last reply Reply Quote 0
                • JayTundefined
                  JayT @dc42
                  last edited by JayT

                  @dc42 :

                  My resurrect-prologue.g file is as below, it has M116 to wait.
                  ;rel
                  G91
                  G1 Z2
                  G28 X Y
                  ;wait
                  M116
                  ;rel
                  M83
                  M21 P1
                  G1 E5 F500
                  ;mesh
                  G29 S1
                  ;Buzz
                  M300 S600 P100
                  ;Buzz
                  M300 S700 P1200
                  ;Buzz
                  M300 S500 P300
                  ;Abs
                  G90

                  1 Reply Last reply Reply Quote 0
                  • R006undefined
                    R006 @dc42
                    last edited by R006

                    @dc42 hey,

                    After upgrading to the latest firmware version 3.5.0rc4, we observed improvement in print acceleration settings. However, the travel acceleration is taking random value: while print acceleration seems to be functioning correctly, travel acceleration values are fluctuating unexpectedly.

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

                      @R006 please check whether the M204 command in resurrect.g is setting the correct travel acceleration for resuming the print.

                      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

                      JayTundefined 1 Reply Last reply Reply Quote 0
                      • JayTundefined
                        JayT @dc42
                        last edited by JayT

                        @dc42 :

                        with RC4, sometimes it resumes fine with minimal offset. Whereas sometimes it shift by 5-8mm in Y direction for me on resume after power failure. Mostly it shifting by >5mm happens when print height is <5mm. So i disabled meshbed compensation & tried. It still has the same problem.

                        There are instances when even at height 3mm, it resumes fine.
                        skew in YZ is included. Does that have any effect?

                        What should I check for ?
                        Shift is always in Y axis & amount of shift is more w.r.t X axis.

                        1 Reply Last reply Reply Quote 0
                        • JayTundefined JayT referenced this topic
                        • Phaedruxundefined Phaedrux marked this topic as a question
                        • First post
                          Last post
                        Unless otherwise noted, all forum content is licensed under CC-BY-SA