> 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/raidlogs/programmers/signals-and-mechanisms.md).

# Signals and mechanisms

Set these up once a season, and again when the robot changes.

## Mechanisms and robot revisions

**Event setup › Mechanisms** groups devices into mechanisms, so findings say "Elevator: TalonFX 14 (rio bus)" and the Power view can split current by mechanism. Name devices as they appear in the converted hoot logs: `TalonFX-12`, or `canivore:TalonFX-12` when two buses use the same ID.

The robot changes through a season, so mechanisms belong to a **robot revision**. Each match is checked against the revision in effect when it was played, so re-checking an old match after a rebuild still groups it as it was. **New revision** copies the mechanisms of the one before.

Revisions come from RAIDSystems: **Sync from RAIDSystems** adds the revisions RAIDLogs doesn't have yet, with each one's motors grouped by subsystem. It needs the RAIDSystems key in [Manage › API keys](https://docs.raidrobotics.org/raidlogs/admin/manage.md).

## Signals

**Event setup › Signals** chooses which entry in the robot's `.wpilog` plays each role (robot state, loop time, pose, speeds, CAN, CPU), so the Performance view and checks read the right one. **Auto-detect** looks for common names. A role that can't be found is left empty rather than guessed. Choices appear after a match's logs have been uploaded and checked.


---

# 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/raidlogs/programmers/signals-and-mechanisms.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.
