Free Shipping on orders over $50
781-859-3020 (9:00am - 4:00pm EST)

More Views

BetaFPV F4 OSD Brushed Flight Controller - Frsky Version

SKU: 313249

Availability: In Stock

$42.99
As low as$0.00/mo with Affirm Learn More

Description

Description

 Update of the F4 Brushed Flight Controller (Frsky Rx + OSD)

  • Since the firmware is the latest  Betaflight 3.4.1, SPI Frsky D16 connection works well in this F4 flight controller. 
  • The position of the BOOT pad on the latest F4 Brushed Flight Controller is changed to near the BIND button. 

Note: If you are using EU-LBT firmware radio controller, you might find that you can't bind successfully to F4 Brushless FC. 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.

Here is a review video made by Mr ShutterBug. (The FC that Mr Shutterbug reviews is the original version, the position of the BOOT pad is different from the latest version)

A smooth and thrilled flying in the forest and detailed explanation of F4 brushed fc.

BETAFPV F4 brushed FC board bring a new era in FPV whoop technology. STM32F411 100MHz high performance MCU, 30A lower resistance MOSFETs, SPI Frsky Rx, Build-in Betaflight OSD and polar reversed protection. All of these is backed by the same reliability and warranty of all BETAFPV FC boards.

High-performance ST Microelectronics ARM Cortex-M4 core F411 100MHz CPU (safely overclocked to 120MHz). Okay, i am the second highest performance whoop board in the world.

30A continuous drain current MOSFET. Lower to 8.5mΩ inner resistance value (4.5V). It has a noticeable power improvement in low battery voltage status or with 8x20/8.5x20 motors.

TX1 is available for VTX control. You could change VTX settings such as channel and output power in your Betaflight OSD or using your Taranis LUA Script. Here is the diagram when using the TBS Unify PRO Nano 5.8G VTX. 

Polarity reversed connection protection. Battery polar reversed connected. Bomb. This issue will never happens.

Key Features

  • The world's first compatible BetaFlight OSD, FrSky Rx, BetaFlight firmware, born for acro flight controller for the Micro Whoop or Blade Inductrix quadcopter.
  • Fully programmable through Betaflight, using the onboard USB port, tune all the parameters, PID's, and rates to your perfect settings
  • Designed to work with current Tiny Whoop or Blade Inductrix setups
  • Built in SPI Frsky D16 protocol native receiver, compatible with almost ALL Frsky radios(e.g. Taranis X9D/X9D Plus/X7) or Frsky compatible transmitter module
  • The flight controller board comes pre-flashed with Betaflight firmware, and pre-soldered 55mm power cable pigtail with JST-PH 2.0 connector, AKA PowerWhoop connector.

Specifications

  • CPU: STM32F411CEU6
  • Six-Axis: MPU6000
  • ESC: All FETs are rated at 30A maximum. Support 6x15mm/7x20mm/8x20mm/8.5x20mm etc motors.
  • Size: 26mm x 26mm,fully compatible with the Inductrix quad frame and mounting pattern
  • Firmware version: Betaflight MATEKF411RX 3.4.0
  • OSD: Built-in BetaFlight OSD (STM32 controls OSD chip over SPI in DMA mode)
  • Receiver: SPI Frsky D16 protocol (AKA FRSKY_X on Betaflight Configuration)
  • Power Cable: 55mm, with JST-PH 2.0 connector, AKA PowerWhoop connector
  • Weight: 3.7g 

      BetaFlight OSD

      Betaflight OSD (on screen display) is integrated in BETAFPV F4 brushed flight controllers that shows important flight data on your FPV feed, such as battery voltage, current draw and much more. You can even use it as a menu to change your quad’s PID, rates, filters and other settings. 

      How would do an OSD with the AIO cameras?

      There is a video in and out on the fc itself, labeled CAM and VTX as show below. There should be a video in and out on the AIO camera, like BETAFPV H02 etc. If not, you would have to modify the camera for sure but it would totally be worth it. There is some examples.

      BETAFPV H02 Camera, FX806TC, VM275, FX805, Eachine XT02 etc aio camera vtx are available to use the OSD function.

      BETAFPV Support Freshdesk for BetaFlight OSD Setup.

      Tips: There is no current sensor on the FC boards. So the amperage value on the OSD is invalid.

      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 ). 

      LED

      Status

      Description

      Receiver LED ( Green)

      Solid

      Connected or in bind mode

      Receiver LED ( Green)

      Flashing

      Not connected

      Power LED ( Blue )

      Solid

      Power on

      Status LED ( Red )

      Solid

      Motor Armed


      SPI Frsky Receiver

      Currently the built in Frsky receiver is compatible with Taranis, Taranis Plus, X9E, Horus X12S, XJT Modules. Pay attention, this is a SPI connection receiver. In Betaflight Configuration, it should be setted 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 factory is Frsky D16 mode (FRSKY_X).

      Binding Procedure

      The binding procedure is reversed as usual. No need to click the bind button when power 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 detailed procedure of binding, please check the SPI Frsky Receiver Binding Manual.

      Some pilots would complaint that it is definitely not a long range FC. It looses 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 singal upwards. Thanks for Harley Finberg's advice.

      Assemble Guide

      The mounting pattern of this board is compatible with all the Tiny Whoop airframes, like the original stock Blade Inductrix frame or the Beta75 75mm frame. For other frames like Eachine E010 or E011, a little bit modify is need.

        Package

        • 1 * F4 OSD brushed flight controller ( 55mm PH-JST 2.0 power cable soldered)
        • 4 * M1.2x4mm screws (Fit for stock Inductrix frame)
        • 4 * M1.4x5mm screws (Fit for Beta75 etc 75mm frame)
        • 4 * Anti-vibration ruber dampers

        User Manuals

        Go to BETAFPV Support Freshdesk for F3 Brushed Flight Controller

          Warranty, Returns & Support

          Warranty Information

          We truly thank you for your purchase, and when things go wrong, we are here to help in any way that we are capable of doing so.

          In regards to any warranty related matter, please reference the below information to help understand our warranty policies, as these warranty policies are absolute when it comes to any purchase made via HeliDirect.

          Warranty Time Frame

          Regarding product(s) purchased via HeliDirect, each manufacturer has their own specified warranty time frame, and HeliDirect holds the sole right to direct the customer to the manufacturer for stated warranty support in regards to manufacturer's that require direct level warranty support.

          Our stated (14) day return policy directly relates to brand new, unused products being returned for a refund or store credit, and does not relate to warranty related situations for faulty product(s). Faulty, damaged or problematic items are handled upon a case by case basis, and will be detailed below based upon the warranty options available.

          Our team at HeliDirect is highly motivated to assist in every possible way regarding warranty support, but please be 100% aware that warranty support for the product(s) you have purchased may be handled directly via the manufacturer, and not through HeliDirect.

          If your product(s) involve direct manufacturer support, we are still available to assist. We ask that the customer make the initial manufacturer contact for warranty support, but in the case where a manufacturer response is not receive within (5) business days, HeliDirect will step in upon your behalf, utilizing our channels to assist you with this manufacturer based support.

          In the above case, HeliDirect will do everything in our power to make sure the manufacturer assists you directly, but please note that all such warranty in regards to an issue like this will still be directed through the manufacturer.

          Warranty Related Issues

          Please note that HeliDirect is not a warranty repair center, nor do we offer warranty regarding many items we resell. Product(s) purchased via HeliDirect are subject to the original vendor’s repair / replacement warranty policies & timelines, and will be directed to the manufacturer at our discretion.

          HeliDirect will not assume responsibility and / or liability for any manufacturer defect, or damage due the use / misuse of the product(s) purchased. Further, HeliDirect cannot / will not be held liable for ancillary damage to product(s) based upon a manufacturer fault or defect. All such issues will be dealt with at the manufacturer based level.

          If your item is found to have a fault or defect after installation or use, your product may be subject to warranty repair via the original manufacturer, no matter what the purchase date may be. HeliDirect does not cover repair, replacement or warranty via used / installed products. All such issues will need to be dealt with at the manufacturer level.

          Damage Due to Ancillary Product Failure

          In regards to damage that directly results to a failed product installed in conjunction with another product, we are happy to assist in terms of warranty support for the product that has failed, but please be aware that we cannot be held liable for ancillary damage to other items or components that may have been damaged due to the original product failure.

          Warranty Returns

          If your product is approved by our customer service staff as a valid return that we will handle directly, please note the below information regarding all such approved warranty items sent to HeliDirect.

          - Any item(s) approved for return to HeliDirect will be subject to inspection and or testing to verify the noted information provided by the customer regarding the flaws, faults or damage.

          - Due to the various aspects of testing, repair and other return processes, please be aware that any such approved return will require (2) to (5) business days for proper processing. Our staff will certainly do all that we can to reduce this time to the bare minimum, but please be aware that the return process can take up to (5) business days to complete.

          - If the product(s) approved for return are deemed faulty by our returns specialists, we will proceed with a repair, exchange, credit or refund based upon the situation at hand. All such information will be communicated to the customer before any re-shipment is made.

          - If an item that encounters a warranty issue after usage, HeliDirect may opt to repair the product versus an exchange, as exchanges can only be made for valid warranty relating to products that have no use of flaws. Our staff will be sure item is in 100% working order based upon any repairs, but exchanges, credits or refund cannot be offered for items under warranty that have been used and are no longer able to be sold as new.

          - In the case of product(s) returned to us that test to be non faulty, the product(s) will be returned to the customer in the condition received. Our staff will reach out to the customer with necessary information regarding what may have been missed, and what steps to take in order to utilize the product(s) effectively.

          - For non faulty diagnoses of returned product(s), refunds, store credits or exchanges cannot be offered, as the product(s) received cannot be sold as new and unused.

          Product Tags

          Use spaces to separate tags. Use single quotes (') for phrases.