> 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-3-robot-functions.md).

# Lesson 3 - Robot Functions

How the components from Lesson 2 connect into a working robot: the wiring diagram, the CAN loop, sensors, and why the software team depends on CAN. The lesson ends with you drawing your own wiring diagram, graded on the components you include and whether each connection uses the right wire.

## Key terms

| Term           | What it means                                                                                                                         |
| -------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
| Wiring diagram | A drawing of every electrical component and the wire type between each pair. Compare the basic and modern FRC diagrams in the slides. |
| Belly pan      | The flat plate in the bottom of the robot that most electronics mount to.                                                             |
| CAN loop       | The chain of CAN wire through every CAN device. If it breaks, the code loses contact with everything past the break.                  |
| Phoenix Tuner  | CTR Electronics' tool for finding, configuring and testing CAN devices.                                                               |

## 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/16b1H-DBFfcmU7qJBKfOH31s2-7g7x0GucyfJtPcP1tc/edit?slide=id.g5b35a59fb_0_5#slide=id.g5b35a59fb_0_5>" %}


---

# 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-3-robot-functions.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.
