> 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/overview-and-code-sync.md).

# Overview and code sync

**Robot › Overview** shows the robot at a glance: its CAN buses, how many CAN devices and button bindings it has, how many open items are left, and whether the robot code is linked.

## Sync the robot code

Programmers, mentors and admins click **Sync code**. RAIDSystems reads the latest commit on the robot's branch on GitHub and finds:

* every CAN device and its ID, including IDs in nested constants classes, devices made in subsystems, and IDs passed through a module's constructor,
* every controller, including button boxes,
* every binding made on a controller's buttons. The comment right above a binding becomes its draft description.

Anything the parser can't read is listed under **What the parser couldn't read**. Nothing there was guessed: fix it in the robot code (or tell a programmer), then sync again.

A sync replaces the devices, controllers and bindings that came from the code. Notes people recorded, controller notes and button descriptions are kept. A binding whose code changed goes back to unreviewed on [Controls](https://docs.raidrobotics.org/raidsystems/robot/controls.md).

A device that leaves the code is removed, unless someone recorded notes about it. Then it stays, marked **Not in the code anymore**, with an open item until a mentor removes it.

## Link the code

If the Overview says **Not linked yet**, a mentor or admin opens **Manage › Robots**, then the robot's ⋯ › **Edit**, and enters its GitHub repo (for example `Team4469/RAID-4469_2026`) and branch if it isn't the default. See [Robots](https://docs.raidrobotics.org/raidsystems/manage/robots.md).

## Terminators

Each CAN bus ends at a 120 Ω terminator. The Overview shows **No terminator recorded** for a bus until someone records which device or connector it sits on.


---

# 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/overview-and-code-sync.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.
