> For the complete documentation index, see [llms.txt](https://wiki.purduesigbots.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.purduesigbots.com/vex-electronics/vex-sensors/3-pin-adi-sensors/limit-switch.md).

# Limit Switch

The Limit Switch is a sensor that returns a value when it is pressed.

![](https://phabricator.purduesigbots.com/file/data/e6uhtyrngcdmk4rf26js/PHID-FILE-vb2juqo4kc7k2gsoeeea/limit_switch-300x300.jpg)

The limit switch is also a digital sensor (returning 1 or 0) and acts very similarly to the [bump switch](/vex-electronics/vex-sensors/3-pin-adi-sensors/bumper.md). When the little metal lever is up, as in the photo above, it returns a value of 1, when the little metal lever is depressed, it gives a value of 0.

Like the bumper switch, the limit switch is also easy to use and quite reliable, but fragile (otherwise known as “flimsy”). You don’t want to put this sensor in a place where it can get entangled with other robots or on a robot appendage that will hit things hard. If you did, you’d probably have to replace this sensor at the end of every match.

This sensor requires only a tiny amount of force to trigger it, as compared to the bump switch.

## Teams Contributed to this Article:

* [BLRS](https://purduesigbots.com/) (Purdue SIGBots)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://wiki.purduesigbots.com/vex-electronics/vex-sensors/3-pin-adi-sensors/limit-switch.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.