# FMUK66 Hardware Reference

- [Schematics and design files](https://nxp.gitbook.io/hovergames/rddrone-fmuk66/schematics.md): Schematics and design files for the RDDRONE-FMUK66 Rev. D as well as previous revisions of the board.
- [Connectors and pinout](https://nxp.gitbook.io/hovergames/rddrone-fmuk66/connectors.md): This section gives an overview of the location and pinout of the different ports on RDDRONE-FMUK66.
- [FMU power input](https://nxp.gitbook.io/hovergames/rddrone-fmuk66/connectors/fmu-power-input.md): Details and pinout of the power input connector on the FMU.
- [FMU power module](https://nxp.gitbook.io/hovergames/rddrone-fmuk66/connectors/fmu-power-input/fmu-power-module.md): The power module provides power to the FMU and has voltage and current sensors.
- [Servorail](https://nxp.gitbook.io/hovergames/rddrone-fmuk66/connectors/servorail.md): The FMU has a servorail with six PWM outputs and a BEC input to power the 5V rail.
- [RC input](https://nxp.gitbook.io/hovergames/rddrone-fmuk66/connectors/rc-input.md): Connectors for providing RC input from a RC receiver module.
- [GPS](https://nxp.gitbook.io/hovergames/rddrone-fmuk66/connectors/gps.md): Pinout of the GPS connector on FMU side and on the side of the GPS module.
- [Micro USB](https://nxp.gitbook.io/hovergames/rddrone-fmuk66/connectors/micro-usb.md)
- [Serial 1 / Telemetry 1](https://nxp.gitbook.io/hovergames/rddrone-fmuk66/connectors/telemetry-1.md): Serial port meant for use with telemetry radios, or to communicate with a companion computer.
- [Serial 2 / Telemetry 2 / IRDA](https://nxp.gitbook.io/hovergames/rddrone-fmuk66/connectors/telemetry-2.md): Pinout and schematic for the Telemetry 2 port, which can also be configured as IRDA or extra I2C bus.
- [External I2C bus / NFC](https://nxp.gitbook.io/hovergames/rddrone-fmuk66/connectors/i2c-nfc.md)
- [External SPI bus](https://nxp.gitbook.io/hovergames/rddrone-fmuk66/connectors/external-spi.md)
- [Debug interface (DCD-LZ)](https://nxp.gitbook.io/hovergames/rddrone-fmuk66/connectors/debug-interface-dcd-lz.md): Debug interface pinout, schematics and technical details.
- [DCD-LZ breakout board](https://nxp.gitbook.io/hovergames/rddrone-fmuk66/connectors/debug-interface-dcd-lz/dcd-lz-breakout-board.md): Breakout board that exposes the different interfaces from the DCD-LZ connector.
- [Analog-digital converters](https://nxp.gitbook.io/hovergames/rddrone-fmuk66/connectors/analog-digital-converters.md)
- [CAN transceivers](https://nxp.gitbook.io/hovergames/rddrone-fmuk66/connectors/can-transceivers.md)
- [Automotive ethernet](https://nxp.gitbook.io/hovergames/rddrone-fmuk66/connectors/ethernet.md)
- [Ultrasound sensor](https://nxp.gitbook.io/hovergames/rddrone-fmuk66/connectors/ultrasound-sensor.md)
- [Arming switch](https://nxp.gitbook.io/hovergames/rddrone-fmuk66/connectors/arming-switch.md): The arming switch is a safety feature that prevents the drone from take-off while not activated.
- [Buzzer](https://nxp.gitbook.io/hovergames/rddrone-fmuk66/connectors/buzzer.md): Buzzer for audio feedback.
- [Electrical fuses](https://nxp.gitbook.io/hovergames/rddrone-fmuk66/electrical-fuses.md): The RDDRONE-FMUK66 includes three electrical fuses. They will blow when too much current goes through them, to protect the MCU and other components on the PCB.
- [Hardware errata](https://nxp.gitbook.io/hovergames/rddrone-fmuk66/hardware-errata.md): During the development of the RDDRONE-FMUK66 (NXPhlite) several hardware issues were discovered and fixed in newer revisions. Boards send to HoverGames participants should NOT have these issues.


---

# Agent Instructions: 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/rddrone-fmuk66.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.