> For the complete documentation index, see [llms.txt](https://docs.raidrobotics.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.raidrobotics.org/raidsystems/robot/bus-check.md).

# Bus check

The bus check confirms which devices actually answer on each CAN bus.

1. Connect a laptop to the robot (USB or Ethernet).
2. Open Phoenix Tuner X for CTRE and Redux devices, and REV Hardware Client for REV ones.
3. On **Robot › Bus check**, tick each device you see.
4. If **Something answered that isn't listed**, add it with its bus and CAN ID.
5. Save.

A device the bus check finds counts as confirmed. A device that didn't answer, or something that answered but isn't in the record, becomes an [open item](https://docs.raidrobotics.org/raidsystems/robot/open-items.md). Until the first bus check, every CAN ID comes only from the code.


---

# 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.raidrobotics.org/raidsystems/robot/bus-check.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.
