> For the complete documentation index, see [llms.txt](https://docs.creativeconners.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.creativeconners.com/docs/machinery/pushstick/setting-the-limits.md).

# Setting the Limits

The Pushstick v2 has up to four physical limits depending on the machine wiring: FWD ULT, FWD, REV, REV ULT. See the limit table below for details.

| Limits  | Apprentice & Classic | Pro |
| ------- | -------------------- | --- |
| FWD     | X                    | X   |
| REV     | X                    | X   |
| FWD ULT |                      | X   |
| REV ULT |                      | X   |
|         |                      |     |

The limits are actuated by the block attached to the end of the drum’s acme rod. All four of these limits are adjustable.

To adjust the limits, loosen the socket head cap screw attaching the limit to its track with a 5/32” allen key. Move the limit to your desired position and re-tighten the socket head cap screw to set the limit into place on the track.

Sometimes pictures are better than words - take a look at the slideshow below for guidance.

{% embed url="<https://docs.google.com/presentation/d/e/2PACX-1vS_07uUuwV5jJa5gs9SH0OljEVirnPjbxRHXvOOI5sT_MwVC-UIzNkCa_zvz2can_pVSdcBI89bLGRW/pub?delayms=3000&loop=false&start=false>" %}


---

# 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://docs.creativeconners.com/docs/machinery/pushstick/setting-the-limits.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.