Betaflight wont download blackbox file

Should be definately a warning in the release notes, killed my plans quickly tweaking some settings. The exe has some files is broken.

As suggested by McGiverGim uninstall the current version before installing this one. I uninstalled previous Betaflight configuration and it still took forever at this part.

Asking why is not helpful without understanding the background. I am not a fan of installer in general, I prefer the zip package. I do not install BF on a daily basis and only install when I need. I happened to run into this specific version to start with and realized the problem, thus, I wanted to report so others can be aware of what is going on. Saving people time from running into the problem is much appreciated.

Because when searching for Betaflight Configurator Installer, Google takes you directly to So not keen to try it if at all possible. But I've been sitting with the I've uninstalled the previous version and deleted all the contents that remained It didn't solve the issue. Still busy updating Brand new windows install. BF configurator has never been installed on this computer. Created by. Category: Crafting , Modding or Configuration. Languages: English. Guide Index. Before Flight.

In Flight. After Flight. Extract The BlackBox. Fly it! In the Select Model screen, put a model name, select your file, and launch the extraction process. Oct 27, Improve Betaflight logo. Oct 19, Remove unneeded file. Sep 1, Sep 3, Nov 2, Rebrand the readme to Betaflight. Dec 23, Expo curve tests. May 12, Added unified '. Oct 1, Remove Chrome support. Oct 14, Add Workspace Dropdown. Oct 12, Add SonarCloud analysis file.

Nov 5, Updated documentation from template repository. Mar 8, Generate win64 version for Windows by default. Mar 22, Oct 29, Added the changelog entry for 3. Apr 27, Now you must decide which device to store your flight logs on. You can either transmit the log data over a serial port to an external logging device like the OpenLog serial data logger to be recorded to a microSDHC card, or if you have a compatible flight controller you can store the logs on the onboard dataflash storage instead.

The OpenLog is a small logging device which attaches to your flight controller using a serial port and logs your flights to a MicroSD card. Although this original OpenLog firmware will work with the Blackbox, in order to reduce the number of dropped frames it should be reflashed with the higher performance OpenLog Blackbox firmware.

The special Blackbox variant of the OpenLog firmware also ensures that the OpenLog is using Cleanflight compatible settings, and defaults to baud. You can find the Blackbox version of the OpenLog firmware here , along with instructions for installing it onto your OpenLog. Your choice of microSDHC card is very important to the performance of the system.

The OpenLog relies on being able to make many small writes to the card with minimal delay, which not every card is good at. A faster SD-card speed rating is not a guarantee of better performance. You should format any card you use with the SD Association's special formatting tool , as it will give the OpenLog the best chance of writing at high speed. First, tell the Blackbox to log using a serial port rather than to an onboard dataflash chip.

You need to let Cleanflight know which of your serial ports you connect your OpenLog to i. SoftSerial ports can be used for the Blackbox. However, because they are limited to baud, your logging rate will need to be severely reduced to compensate.

Therefore the use of SoftSerial is not recommended. When using a hardware serial port, Blackbox should be set to at least baud on that port.

The serial port used for Blackbox cannot be shared with any other function e. This will mean that you can't use the Configurator or any other function that requires MSP, such as an OSD or a Bluetooth wireless configuration app, while the board is armed. Don't connect the serial port's RX pin to the OpenLog, as this will cause the OpenLog to interfere with any shared functions on the serial port while disarmed. If Blackbox is connected to the pins on top of the Naze32, the Configurator will stop working once the board is armed.

This configuration is usually a good choice if you don't already have an OSD installed which is using those pins while armed, and aren't using the FrSky telemetry pins. Cleanflight automatically shifts logical channel mapping for you when UART2 is enabled in Ports tab so you'll have to shift receiver pins that are connected to Naze32 pins 3 to 6 by two. The OpenLog tolerates a power supply of between 3.

Boards other than the Naze32 may have more accessible hardware serial devices, in which case refer to their documentation to decide how to wire up the logger. The key criteria are:. Power up the OpenLog with a microSD card inside, wait 10 seconds or so, then power it down and plug the microSD card into your computer. TXT" file on the card, open it up in a text editor. You should see the baud rate that the OpenLog has been configured for usually or from the factory.