Skip to main content

CrazyBee F4 FR Pro

CrazyBee F4 FR Pro front CrazyBee F4 FR Pro back

Description

CrazyBee F4 FR Pro flight controller is a Highly integrated board(Receiver/4in1 ESC/OSD/Current Sensor) for 1~2S Whoop brushless racing drone.

MCU, Sensors and Features

Hardware and Features

  • MCU: STM32F411CEU6 (100MHZ, 512K FLASH)
  • IMU: MPU6000 (SPI)
  • OSD: Betaflight OSD
  • Battery Voltage Sensor: yes
  • Power supply: 1-2S battery input (DC 3.5-8.7V)
  • Built-in 5V 1A Buck / Boost with LC filter
  • Integrated Current sensor:Max 28A,Current meter scale set to 1175
  • Built-in SPI FrSky receiver with telemetry(D8/D16 switchable)
  • Integrated inverter for sbus(when use external rx) in UART1 RX
  • Integrated 4x Blheli_s ESC: Max 5A per ESC(EMF8BB21F16G)
  • ESC Connector: 3-pin, PicoBlade 1.25mm pitch
  • Beeper output: 2-pin, soldering pad
  • 4 Rx Indicating LEDs: 2 x red and 2 x white
  • Board size: 28.5 * 28.5mm

Resource mapping

LabelPinTimerDMADefaultNote
MPU6000_INT_EXTIPA1
MPU6000_CS_PINPA4SPI1
MPU6000_SCK_PINPA5SPI1
MPU6000_MISO_PINPA6SPI1
MPU6000_MOSI_PINPA7SPI1
OSD_CS_PINPB12SPI2
OSD_SCK_PINPB13SPI2
OSD_MISO_PINPB14SPI2
OSD_MOSI_PINPB15SPI2
RX_CS_PINPA15SPI3
RX_SCK_PINPB3SPI3
RX_MISO_PINPB4SPI3
RX_MOSI_PINPB5SPI3
RX_GDO0_PINPC14
BIND_PLUG_PINPB2
RX_LED_PINPB9
PWM1PB8TIM2, CH3
PWM2PB9TIM4, CH1
PWM3PA3TIM4, CH2
PWM4PA2TIM4, CH3
VBAT_ADC_PINPB0ADC1
CURRENT_ADC_PINPB1ADC1
BEEPERPC15
UART1 TXPA9
UART1 RXPA10
UART2 TXPA2
UART2 RXPA3

Manufacturers and Distributors

Designers

Maintainers

FAQ & Known Issues

FRSKY Version:

  • To bind to your Taranis, you need to be running the non-eu OpenTX version, which allows you to use the required D8 setting to bind to the RX. The factory default BF receiver mode is FRSKY_X, so remember to configure this if needed.
  • FrSky X (8 / 16 channels) and FrSky D (8 channels) work both reliably, including in combination with crash flip / DShot beacon, as long as the TELEMETRY feature is disabled; Basic telemetry information like RSSI and battery voltage will be sent even when the TELEMETRY feature is disabled;
  • On FrSky D, the TELEMETRY feature causes occasional dropouts, depending on how many sensors (BARO, GPS, ...) are enabled, probably due to a timing overrun;
  • On FrSky X, the TELEMETRY feature causes hard lockups due to a bug in the telemetry generation code.

Other Resources