> For the complete documentation index, see [llms.txt](https://teravolt.gitbook.io/teravolt/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://teravolt.gitbook.io/teravolt/peripherals/aerobuddy/hardware-overview.md).

# Hardware Overview

#### The Connections

The AeroBuddy acts as a traffic cop between the two receivers and the flight controller.

<figure><img src="/files/z83DQV2lvgSZRkow4034" alt=""><figcaption></figcaption></figure>

| **Port Label**   | **Function**          | **Connection**                                                                    |
| ---------------- | --------------------- | --------------------------------------------------------------------------------- |
| PWM IN           | The "Handover" Signal | Connects to a spare channel (e.g., CH5/AUX1) on the Master (Instructor) receiver. |
| SBus IN (Top)    | Master Signal         | Connects to the SBUS output of the Master (Instructor) receiver.                  |
| SBus IN (Middle) | Student Signal        | Connects to the SBUS output of the Slave (Student) receiver.                      |
| SBus OUT         | Output to Drone       | Connects to the standard SBUS IN or UART RX pad on your Flight Controller.        |

#### LED Status Indicators

The LEDs provide immediate visual confirmation of who has control.

* 🔴 Red (SBUS1): INSTRUCTOR CONTROL. (PWM Signal is Low). The Master receiver is flying the drone.
* 🔵 Blue (SBUS2): STUDENT CONTROL. (PWM Signal is High). The Student receiver is flying the drone.
* 🟡 Yellow: Power is ON.