> For the complete documentation index, see [llms.txt](https://yagsl.yassrobotics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://yagsl.yassrobotics.com/how-to-guides/verify-module-locations.md).
# Verify your module locations
Your front may not be what you think it is on a robot.
After you have initially configured the robot with YAGSL, test it on blocks to make sure the modules are facing the correct directions while in the air. You may need to [swap the module configurations](/how-to-guides/the-8-steps.md#how-to-swap-module-configurations) around to ensure they're doing what the robot program thinks they're doing.
## Drive straight
The first test is to command the robot to drive straight. The modules should look like this both in real life and in Elastic or [AdvantageScope](/how-to-guides/set-up-advantagescope.md).
If it doesn't look like this in real life, change the offending modules' `location` (and, if needed, CAN IDs) to match this layout.
## Rotate the robot
Your robot should rotate CCW+. For this verification step, as long as the robot appears to be doing either of the following while attempting to rotate, you should be fine.
{% hint style="warning" %}
The depiction on the left requires you to run through [The 8 steps](/how-to-guides/the-8-steps.md), since your translational axis changes based on your robot's heading.
{% endhint %}
---
# 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://yagsl.yassrobotics.com/how-to-guides/verify-module-locations.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.
