Skip to content

Emergency STOP #4

Description

@m3d

Similarly to XP (eXtreme Programming), where I write unit test before the code, in mobile robotics we first implement STOP button before our robot moves for the first time. You will need it anyway, and sooner you have it the better.

Your life, or maybe life of your robot, may depend on it one day, so we invest a little bit more than for normal buttons. We use industrial STOP buttons which you have to turn in order to release them.

And some motivation story? Probably the best one so far is "autonomous" tractor John Deere R300X participating in Robotem Rovne 2015. Our control algorithm was not finished yet so homologation and the first two(?) rounds it was controlled with Emergency STOP only.

I have seen some robots suddenly going crazy (Quadrons robot, for example, decided to jump to the river on Robotour 2016). In such a case you realize how important it is that the STOP button is easily accessible (for bigger robots you may need more than one Emergency STOP). Wiring is also important - once STOP is pressed there should not be any "smart" module, which could overwrite it - we just cut the power to the motors. But we keep our control computer alive! Finally it is a good idea to have a way how to inform the computer that STOP button was pressed - there are typically multiple pins available on industrial STOP buttons.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions