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

    G1 option to apply max deceleration to stop

    Scheduled Pinned Locked Moved
    Firmware wishlist
    2
    5
    389
    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.
    • theKMundefined
      theKM
      last edited by theKM

      New option on G1 gcode ("H5"?) that applies the current max deceleration value from M201 to bring the axis to a stop rather than the hard termination.

      This would allow bigger/heavier machines to jog at speed toward the endstop, pass an extra switch/sensor that will indicate slowing down for the approaching endstop.

      If the move is not terminated by the switch, it currently decelerates as usual... so the info for the deceleration is already somewhere in the move's calculation, just need to truncate/skip between the switch trigger and the part where it would otherwise be slowing down and just let that play out.

      o_lampeundefined 1 Reply Last reply Reply Quote 2
      • o_lampeundefined
        o_lampe @theKM
        last edited by

        @thekm This behaviour is (was?) already implemented for dc42's mini IR Z-probe, but since there is only one connector dedicated to approximative sensors, it won't be useful for all axis.

        theKMundefined 1 Reply Last reply Reply Quote 0
        • theKMundefined
          theKM @o_lampe
          last edited by

          @o_lampe ...then I guess the implementation is what was done, but allow it to connect to switch inputs?

          o_lampeundefined 1 Reply Last reply Reply Quote 0
          • o_lampeundefined
            o_lampe @theKM
            last edited by

            @thekm said in G1 option to apply max deceleration to stop:

            @o_lampe ...then I guess the implementation is what was done, but allow it to connect to switch inputs?

            Analog input doesn't work for every I/O pin. There has to be an A/D converter behind it.

            theKMundefined 1 Reply Last reply Reply Quote 0
            • theKMundefined
              theKM @o_lampe
              last edited by

              @o_lampe ...sure, I just meant that the firmware has logic it can borrow from, but that it needs to optionally consider other interrupts.

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