Duet3D Logo

    Duet3D

    • Register
    • Login
    • Search
    • Categories
    • Tags
    • Documentation
    • Order

    Jerk policy

    Tuning and tweaking
    4
    6
    194
    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.
    • Tinchus
      Tinchus last edited by

      Hello, command M566 has the option for policy 0 or 1. It is not being clear to me the difference. When should I use policy 0 or policy 1?
      Thanks in advance

      alankilian 1 Reply Last reply Reply Quote 0
      • alankilian
        alankilian @Tinchus last edited by alankilian

        @tinchus

        The default jerk policy is 0, which replicates the behaviour of earlier versions of RRF.
        (jerk is only applied between two printing moves, or between two travel moves, and only if they both involve XY movement or neither does). 
        
        Changing the jerk policy to 1 allows jerk to be applied between any pair of moves.
        

        So if you want the jerk policy to be implemented between a printing move followed by a travel move, or a travel move followed by a printing move, you set the policy to one.

        SeemeCNC Rostock Max V3 converted to V3.2 with a Duet2 Ethernet Firmware 3.2 and SE300

        Tinchus 1 Reply Last reply Reply Quote 0
        • CCS86
          CCS86 last edited by

          The only time I noticed a functional difference is when using "coasting" (a Cura feature). With jerk policy set to 0, there is a small stutter at the start of the coasting move. Jerk policy 1 avoids this.

          1 Reply Last reply Reply Quote 0
          • Tinchus
            Tinchus @alankilian last edited by

            @alankilian this the thing taht is not clear to me. So, what happens when a travel move finishes and a printing move follows this travel move, what jerk is applied to the start of that printing move if jerk policy is 0?

            alankilian 1 Reply Last reply Reply Quote 0
            • alankilian
              alankilian @Tinchus last edited by

              @tinchus As I understand it, no jerk control will be applied in your example.

              SeemeCNC Rostock Max V3 converted to V3.2 with a Duet2 Ethernet Firmware 3.2 and SE300

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

                Policy 1 will allow for a faster transition between travel and print moves because a minimum jerk speed is applied.

                Policy 0 would basically be a dead stop between the moves.

                It's most noticeable with a fast travel speed and lower print speed.

                Z-Bot CoreXY Build | Thingiverse Profile

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