> For the complete documentation index, see [llms.txt](https://nxp.gitbook.io/hovergames/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nxp.gitbook.io/hovergames/rddrone-fmuk66/connectors/servorail.md).

# Servorail

The FMU has six PWM outputs for controlling motors or servos. Please refer to the [assembly guide](/hovergames/userguide/assembly/connecting-all-fmu-wires.md#servorail) for the order in which the ESCs should be connected. Make sure to plug in the connectors in the right way. The ground wire (black or brown) should go on top (closest to the board), the signal wire (white or yellow/orange) on the bottom.

The servorail also has a BEC input for powering the 5V rail, which is split from the internal 5V of the FMU and thus not powered when there is no BEC connected. This is done intentionally to isolate this as a source of electrical noise coming into the FMU. Some ESCs or servos require power from the servorail, but the default ESCs included in the HoverGames kit don't need this. They are powered directly from the battery, so it is not required to connect a BEC.

![](/files/-L9GMCwk-dmnPalvV7j7)

## Servo pinout

| Pin | Signal       | Voltage |
| --- | ------------ | ------- |
| 1   | SIGNAL (PWM) | +5.0V   |
| 2   | BEC INPUT    | +5.0V   |
| 3   | GND          | GND     |

## BEC pinout

| Pin | Signal    | Voltage |
| --- | --------- | ------- |
| 1   | NC        | NC      |
| 2   | BEC INPUT | +5.0V   |
| 3   | GND       | GND     |

## RDDRONE-FMUK66 Rev. C schematic

![](/files/-LVs-sVDAT0G1wq2SDeo)

## RDDRONE-FMUK66 Rev. B schematic

{% hint style="danger" %}
Rev. B (and older boards) are **not supported** anymore. This information is left for reference.
{% endhint %}

![](/files/-LOrulBWwQJVu01dzTrT)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://nxp.gitbook.io/hovergames/rddrone-fmuk66/connectors/servorail.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.