> 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/devices.md).

# Devices

**Robot › Devices** lists every device on the robot. Tap one to open its card.

## Find a device

Search by CAN ID (on every bus), the name in the code, the type or the subsystem. `12` finds ID 12 on every bus; `rio 12` narrows it to the rio bus. The same CAN ID can appear on different buses and on different device types, so a device is always named by bus, type and ID together.

## The device card

The card shows everything recorded about one device, with [how sure](https://docs.raidrobotics.org/raidsystems/reference/certainty.md) each value is:

* **On the robot:** its values (PDH channel, breaker, port, IP address, wire order) in certainty form,
* **From the library:** its drawing, manual and specs, from the [device library](https://docs.raidrobotics.org/raidsystems/library/library.md),
* **History:** every note, who recorded it and when.

## Add a note

On the card, open the field you checked and add a note. Choose what you know:

* **I checked this on the robot:** you looked at it yourself,
* **I only know it's one of two (two identical devices):** for example two identical motors whose channels you can't tell apart.

A note that disagrees with a value that's already confirmed waits for a mentor to **Approve** or reject it, so a weaker source never overwrites a confirmed one.

## Add a device the code doesn't build

**Add device** records something on the robot that isn't in the code, like a sensor wired straight to the roboRIO. Pick what it is from the library. It becomes an open item until it's in the code.

## Spreadsheets

* **Export spreadsheet (CSV)** writes the device list with each value in certainty form.
* **Import values…** (mentors) reads the same columns back: a `Device` column plus columns such as `PDH channel`, `Breaker` and `IP address`. Imported values count as one unchecked source until someone checks them.


---

# 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/devices.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.
