> 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/archive/s500-drone-frame/connecting-all-fmu-wires.md).

# Connecting all FMU wires

{% hint style="warning" %}
This page is **archived**. You are probably looking for the up-to-date [assembly guide](/hovergames/userguide/assembly.md).
{% endhint %}

## Connector pinout

We are almost ready. We only need to connect the wires to the right connectors on the FMU. A diagram showing all port locations is available below. [More indepth information](/hovergames/rddrone-fmuk66/connectors.md) is also available in the technical reference section.

![Port locations on the RDDRONE-FMUK66.](/files/-LOSBDPL_Vn5OwbLiPwO)

The power module plugs into the XT60 connector at the back of the drone. Its other end should go through the hole in the bottom plate. The battery can be connected to this end later. The smaller cable coming from the power module should go between the two plates and come out near the front of the FMU. This 6-pin connector plugs into the POWER IN connector.

The 6-pin GPS cable should go to the GPS connector just below the POWER IN connector. Below this is a 6-pin UART connector, to which the telemetry radio cable should be connected.

On the left side of the FMU we have the 4-pin FRSKY/RC IN connector, which is meant for the receiver of the radio controller. Below it is a 3-pin connector for the safety switch. In the middle of the board is a 2-pin connector for the buzzer.

![All cables plugged into the RDDRONE-FMUK66.](/files/-LX3tpRQ2r9jClm-llcK)

## Servorail

The servorail pinout is shown in the diagram below. The BEC should be connected to the leftmost pins. The ESCs should be connected to the first four sets of pins on the right side.

![Pinout of the servo rail.](/files/-LX3u-d98cIxjmgzlk3b)

The order in which the ESCs should be connected to the servo rail is given by the diagram below. The motor/ESC at the front-right should be the first, the one at the back-left should be second. The motor/ESC at the front-left should be third, and the one at the back-right should be fourth.

![Numbering of the motors.](/files/-LX3u2kyoarsjavV9Wln)

The black (ground) wires should be on top, the white (signal) wires on the bottom. The BEC doesn't have a white wire, but it has a red wire, which goes in the middle. It will provide 5V power to all middle pins. However, the ESCs included in the HoverGames kit already receive power directly from the PDB and therefore don't have a wire that connects to the middle pins of the servo rail.

![Power module plugged into the XT60 connector and the BEC and ESCs connected to the servo rail.](/files/-LX3uCbCTKi-eriP0SKo)

The drone should now look similar to the picture below.

![](/files/-LX3uQbrcNkj6q7yYgu7)

## Final result

Finally, you can use some zip ties to make sure the propellers won't cut through any loose wires. You could already install the propellers, but you might have to remove them again later. The clockwise rotating motors (with a mark on top) have propellers with black nuts, the counter clockwise rotating motors have propellers with silver nuts.

{% hint style="danger" %}
When you are setting up the software you should take the propellers off for your own safety. It is a good idea to only have the propellers installed when you are ready to fly. Also have a look at our section about [flying safely](/hovergames/userguide/flying.md).
{% endhint %}

![](/files/-LX3uSZFwLEDIhUbZyfo)


---

# 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:

```
GET https://nxp.gitbook.io/hovergames/archive/s500-drone-frame/connecting-all-fmu-wires.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.