Duet3D Logo

    Duet3D

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

    Solved question about use M581

    Duet Hardware and wiring
    2
    5
    88
    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.
    • Kevin
      Kevin last edited by Kevin

      I have a question if it is possible.

      I came across a link on how to use M581.
      am currently using a duet 2 with rrf2 with an emergency stop on trigger9.g

      it is possible to add more buttons to trigger.g folders i read

      but is it right what i think ?

      exemple :

      button 1 extrude 100mm = trigger1.g G1 E100 F300
      button 2 retract 100mm = trigger2.g G1 E-100 F300
      button 3 G32 = trigger3.g Bed.g
      emergency stop = trigger4.g M24

      and what I read normal push buttons can be used,
      pressing once is then going through trigger.g command

      I hope it's easy to understand with google transstate 🙂

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

        @kevin

        If you want a true emergency stop you need to specify trigger 0 in the M581 command.

        Triggers 0 and 1 are acted upon immediately.

        Triggers 2 and up don't execute until the current move is finished.

        If you want trigger 3 to execute bed.g just put G32 into the trigger3.g file.

        Frederick

        Printers: A FT-5 with the 713 upgrade bits. A custom MarkForged style. A small Utilmaker style and a CoreXY from kits. Various hotends. Using Duets (2 and 3) running 3.4.1

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

          @fcwilt

          the emergency stop runs on M24 pause during printing.

          ; Input/Output
          M581 E2 S1 T1 C1 ; Pause - trigger1.g
          M581 E3 S1 T2 C0 ; extrude 100mm - trigger2.g
          M581 E4 S1 T3 C0 ; retract 100mm- trigger3.g
          M581 E5 S1 T4 C0 ; G32- trigger4.g

          ; trigger1.g
          M24
          ; trigger2.g
          G1 E100 F300
          ; trigger3.g
          G1 E-100 F300
          ; trigger4.g
          G32

          so it is explained a bit more clearly what I was planning

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

            @kevin said in question about use M581:

            @fcwilt

            the emergency stop runs on M24 pause during printing.

            ; Input/Output
            M581 E2 S1 T1 C1 ; Pause - trigger1.g
            M581 E3 S1 T2 C0 ; extrude 100mm - trigger2.g
            M581 E4 S1 T3 C0 ; retract 100mm- trigger3.g
            M581 E5 S1 T4 C0 ; G32- trigger4.g

            ; trigger1.g
            M24
            ; trigger2.g
            G1 E100 F300
            ; trigger3.g
            G1 E-100 F300
            ; trigger4.g
            G32

            so it is explained a bit more clearly what I was planning

            When using trigger 0 (emergency stop - as if M122 was received) or trigger 1 (pause - as if M25 was received) there is no actual file used - it is handled directly by the firmware.

            Only triggers 2 and higher run a file.

            Frederick

            Printers: A FT-5 with the 713 upgrade bits. A custom MarkForged style. A small Utilmaker style and a CoreXY from kits. Various hotends. Using Duets (2 and 3) running 3.4.1

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

              @fcwilt
              thanks for the quick response ,I know enough for now

              1 Reply Last reply Reply Quote 0
              • Topic has been marked as a question  dc42 dc42 
              • Topic has been marked as solved  dc42 dc42 
              • First post
                Last post
              Unless otherwise noted, all forum content is licensed under CC-BY-SA