> 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-4-standards.md).

# Lesson 4 - Standards

The wiring standards that keep a robot from failing mid-match, and the reason for each. Routing means getting a wire from A to B safely; good routing also makes wires easy to trace when something needs fixing.

## Key terms

| Term                       | What it means                                                                                                              |
| -------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
| Routing                    | Safely running a wire or bundle of wires to where it connects.                                                             |
| Tracing                    | Following a wire to see where it comes from and goes.                                                                      |
| Main breaker standard      | Zip-tie battery wires 4 in from the breaker, cover the screws fully in electrical tape, and make sure crimps can't rotate. |
| PDH standard               | Strip and solder Anderson wires before inserting them, and pull-test every wire before every practice.                     |
| roboRIO and radio standard | Crimp and hot-glue every wire, screw the power adapter fully on, and hot-glue the radio's Ethernet and power.              |
| Pull test                  | A firm tug on each connection to catch anything that has worked loose.                                                     |

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


---

# 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-4-standards.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.
