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

    emergency stop

    Scheduled Pinned Locked Moved
    Duet Hardware and wiring
    4
    8
    416
    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.
    • Tinchusundefined
      Tinchus
      last edited by

      I have installed an emergency stop buttom and configured it with:
      M950 J0 C"^io8.in" ; Definition of emervengy stop pin
      M581 P0 R0 T0 ; Assigment of the emergency stop

      And it works perfect. When pressed I can see the emergency message on the console and prints stops.

      But I want to configure a little more the actions taken when pressing the emergency buttom. So I change the command to M581 P0 R0 T1 and create the fyle /sys/trigger1.g having this:

      M42 P5 S1 ; activates buzzer
      M112

      But it doesnt work. I dont see any message in the console now when pressing the buttom.
      Im suspecting the system cant find the file? because another one of my problems is that the macros I put on the MACROS folder, are just not found unless I specifically called them with /macros/macro_name.g

      Thanks in advance

      1 Reply Last reply Reply Quote 0
      • Zhang Jianyuundefined
        Zhang Jianyu
        last edited by

        Trigger 1 is already reserved for a print pause trigger, so you could try renaming your file to trigger2.g and reconfiguring the trigger to use T2.

        If you are calling other macro files with M98 command, I think it will only look in the /sys/ folder. To get around this, you could move all your macros to /sys/, or use the full path like so in your script: M98 P"0:/macros/mymacro.g"

        Tinchusundefined 1 Reply Last reply Reply Quote 1
        • Tinchusundefined
          Tinchus @Zhang Jianyu
          last edited by

          @Zhang-Jianyu
          Ahhhhh that solved the problem, partially.
          Now the trigger2.g file is being executed, but not totally. Tis is what I have inside
          M42 P5 S1
          M112

          The M112 is executed, but the M42 not. The same command run manually starts the buzzer

          1 Reply Last reply Reply Quote 0
          • Zhang Jianyuundefined
            Zhang Jianyu
            last edited by

            Is it possible the emergency stop command is resetting the buzzer output signal as well?

            To test this, you could try to insert a delay before the emergency stop to see if the buzzer works (for a short time) and then stops, something like:

            M42 P5 S1 ; activate buzzer
            G4 S5 ; wait 5 seconds
            M400 ; wait for buffered commands to execute (maybe does nothing?)
            M112 ; e-stop
            
            Tinchusundefined 1 Reply Last reply Reply Quote 1
            • Tinchusundefined
              Tinchus @Zhang Jianyu
              last edited by

              @Zhang-Jianyu Thanks for the tips.
              I have tried your idea. Using it exactly as your wrote, it "works", the problem I see is that this is not exactly and emergency stop. The buzzer works, but the printing doesnt stop till the buffer is empty, and in my example gcode, that took like 5 extra seconds. That makes a total of 10 second to stop the printing... no t exactly an emergency stop jajajaja
              Then I tried:
              removing the M400: still not perfect, the machines stops after 5 seconds (little more may be), but buzzer is not triggered
              removing the G4 delay: the same, it stop after seconds, and buzzer is not triggered.

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

                Why the buzzer? Presumably you're the one that pushed the estop button, what do you need the notification for?

                https://duet3d.dozuki.com/Wiki/Gcode#Section_M112_Emergency_Stop

                Since the board needs to be reset after, you could add the buzzer to the end of config.g to hear it when the machine boots back up?

                Z-Bot CoreXY Build | Thingiverse Profile

                Tinchusundefined 1 Reply Last reply Reply Quote 1
                • Tinchusundefined
                  Tinchus @Phaedrux
                  last edited by

                  @Phaedrux you are right, buzzr is just a "detail". I want the buzzer also for notification when print ends, stops, pause, etc.

                  IF I add the buzzer to the end of the config file, how do I make it stop automatically, is there any way to create a counter, like "beeo for 5 seconds"

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

                    @Tinchus you can add a delay for example

                    G4 S5
                    

                    That's a 5 second delay. And then send the code to turn it off.

                    Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

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