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

    3xY Axis Endstops only low or high works, not both

    Scheduled Pinned Locked Moved
    Duet Hardware and wiring
    3
    6
    189
    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.
    • MiniFireDragonundefined
      MiniFireDragon
      last edited by

      I am in the stage of setting up a 9'x12' CNC machine. I have a 5 pepperl+fuchs sensors on the machine. I am trying to setup my y-axis to have 2 high endstops (used for squaring the gantry) and 1 low endstop to determine the length of the bed (that way I can move the end stop and not have to reprogram the gcode).

      When I have all the y endstops active, it will only tell me when the low endstop is triggered. If I rem out the Y1 endstop (as shown in the code below) and send M119, it will tell me the high endstops are triggered (as it should).

      TLDR; Everything works independently, but if I add in the Y1 endstop, the system does not send a message when the Y2 are triggered.

      Board: Duet 3 MB6HC (MB6HC)
      Firmware: RepRapFirmware for Duet 3 MB6HC 3.4.6 (2023-07-21) (Web UI is same)

      GCode:

      ; Endstops
      M574 X1 S1 P"!io4.in"                         ; configure switch-type (e.g. microswitch) endstop for low end on X via pin io1.in
      M574 Y2 S1 P"!io5.in+!io1.in"                 ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin io3.in
      ;M574 Y1 S1 P"!io2.in"                 		  ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin io3.in
      M574 Z2 S1 P"!io3.in"                         ; configure switch-type (e.g. microswitch) endstop for low end on Z via pin io5.in
      
      fcwiltundefined droftartsundefined 2 Replies Last reply Reply Quote 0
      • fcwiltundefined
        fcwilt @MiniFireDragon
        last edited by

        @MiniFireDragon

        As far as I know RRF 3.4.6 does not support endstops at both ends of an axis.

        I don't know if 3.5.x will.

        It would be nice.

        Frederick

        Printers: a small Utilmaker style, a small CoreXY and a E3D MS/TC setup. Various hotends. Using Duet 3 hardware running 3.4.6

        MiniFireDragonundefined 1 Reply Last reply Reply Quote 0
        • MiniFireDragonundefined
          MiniFireDragon @fcwilt
          last edited by

          @fcwilt Thanks for the information.

          fcwiltundefined 1 Reply Last reply Reply Quote 0
          • fcwiltundefined
            fcwilt @MiniFireDragon
            last edited by

            @MiniFireDragon

            You can always make an entry in the firmware wishlist category.

            Frederick

            Printers: a small Utilmaker style, a small CoreXY and a E3D MS/TC setup. Various hotends. Using Duet 3 hardware running 3.4.6

            1 Reply Last reply Reply Quote 0
            • droftartsundefined
              droftarts administrators @MiniFireDragon
              last edited by

              @MiniFireDragon RRF only supports one endstop per motor. Endstops are only active during homing moves; the rest of the time they can be repurposed as triggers. You could set up the low endstop as a trigger, and any move the hits that trigger stops the axis and sets the Y axis to 0 with G92. See https://docs.duet3d.com/en/User_manual/Tuning/Triggers

              Ian

              Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

              MiniFireDragonundefined 1 Reply Last reply Reply Quote 0
              • MiniFireDragonundefined
                MiniFireDragon @droftarts
                last edited by

                @droftarts Thanks, this maybe useful.

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