> 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-1-wires.md).

# Lesson 1 - Wires

The four kinds of wire on an FRC robot, what each is for, and how they're colored and connected. Electricity is electrons moving through the wire, so the color and gauge (thickness) of a wire tell you what it carries.

## Key terms

| Term         | What it means                                                                                                                                                                            |
| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| CAN wire     | 20 AWG yellow (CAN high) and green (CAN low). One continuous loop, the daisy chain, through every motor, encoder, the roboRIO, Pigeon, CANivore, CANdle and PDH. Ends in ferrule crimps. |
| PWM wire     | About 22 AWG red, black and white, easy to pull apart. Red is positive, black is negative, white is signal. Ends in PWM male or female crimps.                                           |
| Power wire   | 10, 12 or 14 AWG red and black, usually 12. Carries power from the PDH to DC components. Ends in Anderson connectors.                                                                    |
| Battery wire | 4 or 6 AWG. Uses the large Anderson connector, which needs its own crimper. Veteran members teach battery lead assembly in build season.                                                 |
| AWG          | American Wire Gauge. A smaller number is a thicker wire.                                                                                                                                 |

## 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/1oRd6U6edJ8Ou-LAJSqBGL8el6yXtAdT7YVNRLGeLi6A/edit?slide=id.g255fd3bcbab_0_73#slide=id.g255fd3bcbab_0_73>" %}


---

# 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-1-wires.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.
