This AIO F4 FC is a lighter version of their other 2S F4 FC, but this also includes the receiver built-in as well. This is perfect for lightweight drones like the Beta65 Pro 2 or Beta75 Pro 2 etc. It integrated a Betaflight F411 processor FC, Betaflight OSD, SPI Frsky receiver and 1-2S 5A ESC. This allows your 2S drone to save much weight for a faster fly experience.

Specifications

Flight Controller

• CPU: STM32F411CEU6 (100MHZ )
• Six-Axis: MPU-6000 triaxial accelerometer / triaxial gyroscope (SPI connection)
• Size: 26mm x 26mm, fully compatible with the all whoop drone mounting pattern, recommend the Beta65X frame and Beta75 Pro frame.
• Firmware version: betaflight_matekf411rx_4.0.0 (Development Version)
• OSD: Built-in BetaFlight OSD (STM32 controls OSD chip over SPI in DMA mode)
• Built-in SPI Frsky D16 protocol native receiver, compatible with almost ALL Frsky FCC radios(e.g. Taranis X9D/X9D Plus/X7) or Frsky compatible transmitter module. Not compatible with Frsky LBT protocol.
• Power Cable: 55mm, with 2pcs JST-PH 2.0 connector, AKA PowerWhoop connector
• Weight: 4.5g

ESC

• Built-in ESC with 5A continuous and peak 6A current
• Power supply: 1-2S
• Support BLHeliSuite programmable
• Factory firmware: S_H_50_REV16_7.HEX
• Signal Support: D-shot150, D-shot300, D-shot600, Oneshot125, Multishot, PWM

Status LED

There are 3 LEDs on the bottom of the board to indicate the status, including Receiver LED ( Green), FC Status LED ( Red ) and FC Power LED ( Blue ).

SPI Frsky Receiver

Currently, the built-in Frsky receiver is compatible with Taranis, Taranis Plus, X9E, Horus X12S, XJT Modules. Pay attention, this is an SPI connection receiver. In Betaflight Configuration, it should be set as FRSKY_D receiver (aka Frsky D8 mode) or FRSKY_X receiver (aka Frsky D16 mode) in SPI RX mode.

The Frsky D16 unstable connection issue is totally resolved since Betaflight 3.4.1. Nowadays, the default configuration from the factory is a Frsky D16 mode (FRSKY_X).

Note: If you are using EU-LBT firmware radio controller, you might find that you can't bind successfully to this SPI Frsky receiver. Here are the solutions we provide for you. Thanks to Sebastian Abramowski for giving us the important feedback about binding to EU-LBT firmware radio controller.

Binding Procedure

The binding procedure is reversed as usual. No need to click the bind button when powering on.

Power on the board, either by connecting the battery or USB power. Then the green receiver LED start to flash.
The second step, click the bind button for 3s. Then the green receiver LED will be solid on. This means that the receiver is in bind mode and you could start to bind your radio transmitter.
For detail procedure of binding, please check the SPI Frsky Receiver Binding Manual.

Note: This FC board could support the SPI Futaba protocol with this firmware.

Some pilots would complain that it is definitely not a long-range FC. It loses signal with my transmitter far too often and for what appears to be no reason. This issue is often caused by the location of the antenna. You should keep the antenna away from the FC board to get a stronger signal. For example, run the signal upwards. Thanks for Harley Feinberg's advice.

Includes

• 1 * F4 2S brushless flight controller
• 4 * M1.2x4mm screws
• 4 * M1.4x5mm screws
• 4 * Anti-vibration rubber dampers

FAQ

1. Can this FC use on the Beta75X with 1103 motors?

Yes, we have tested this FC board with 1103 motors on Beta75X. It performs very well and almost no wash-out issue then. So if you already have a Beta75X, you could just take this AIO FC to replace the stock FC&ESC stack.

Note: because of the built-in ESC and Frsky receiver, you will lose some remote range and little bit power on Beta75X with this AIO FC.

2. About the alarm buzzer and LED port?

No alarm buzzer is supported on this FC board. Programmable LED is supported.