> 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/stromag-limits.md).
# Stromag Limits
1. Jog the machine to the location where you want to set the limit
2. Engage the E-Stop
3. Remove the limit cover
4. Adjust your limit with small limit screws which are self locking. Ultimate Reverse Initial Reverse Initial Forward Ultimate Forward |
{% hint style="info" %}
**Pro Tips: To ensure the limit strikes in just the right spot**
* Rotate the cam close to the switch then slowly continue to rotate
* When you hear it \*click\*, very slowly back OFF the limit until you hear it \*click\* again
* EXTREMELY carefully and slowly rotate back onto the switch until it \*clicks\*
{% endhint %}
5. Verify that the limit stops the motion where desired
6. Jog the machine off the limit (this is usually about 18”-36” inside of where the limit triggered)
7. Jog back onto the limit
8. If it doesn’t stop within the desired tolerance, try again until it stops where you want
9. Repeat steps 4-8 for each hard limit.
10. When all limits are set, it is best practice to go through and re-check all limits to verify that the relationship between all 4 is correct.
---
# 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/stromag-limits.md?ask=&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.
