> 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/electrical/training/basic-training/lesson-2-components.md).

# Lesson 2 - Components

What each part of the FRC control system does and how power and data move between them. The battery feeds the PDH through the main breaker, the PDH powers everything else, and the roboRIO runs the robot over CAN.

## Key terms

| Term            | What it means                                                                                                                                                               |
| --------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Main breaker    | The robot's on/off switch and 120 A protection between the battery and the PDH.                                                                                             |
| Fuse vs breaker | A fuse is used once and replaced when it blows; a breaker trips and can be reset. Fuses protect small wires, breakers medium ones.                                          |
| PDH             | Power Distribution Hub. Takes battery power and sends it to every motor controller and module, each on its own protected slot.                                              |
| VRM and MPM     | Modules that turn PDH power into steady low-voltage outputs. The Mini Power Module (six fused outputs) replaced the VRM because the VRM had too few useful slots.           |
| roboRIO         | The robot's brain. Starts the CAN loop, takes power from the PDH, talks to the radio over Ethernet and reads sensors on its PWM and DIO ports. Unused ports are taped over. |
| Radio and RPM   | The radio makes the Wi-Fi link to the driver station. The Radio Power Module powers it over Ethernet, which is far more secure than the barrel plug.                        |
| Pigeon 2.0      | Measures the robot's heading and motion. Mounted near the center of the robot.                                                                                              |
| CANivore        | A second, faster CAN bus connected to the roboRIO by USB-C. Most devices go on it.                                                                                          |
| CANcoder        | A magnetic encoder on CAN that measures rotation, used on wheels and swerve modules.                                                                                        |

## Slides

{% hint style="info" %}
The slides are from FRC Team 1678 Citrus Circuits' electrical training. Parts named in them are what 1678 used when the deck was made; our robot may differ, so check the current wiring reference sheet.
{% endhint %}

{% embed url="<https://docs.google.com/presentation/d/11jlUqFix8rAi2rwakzWJBpIwQmFZjBT4JTa6-1QFJvs/edit?usp=share_link>" %}


---

# 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/electrical/training/basic-training/lesson-2-components.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.
