Cross platform configuration tool for the Betaflight firmware
 
 
 
 
 
 
Go to file
cTn 0c3374d8a1 add port handler support for non-timeout callbs 2014-02-26 07:23:50 +01:00
css adjusting element sizes due to window size change 2014-02-03 09:10:13 +01:00
images custom made frame (fixes chrome33+ no shadow) 2014-01-18 19:21:30 +01:00
js add port handler support for non-timeout callbs 2014-02-26 07:23:50 +01:00
tabs adding flash on connect UI, backend missing 2014-02-26 07:09:53 +01:00
LICENSE Initial commit 2013-04-08 17:29:52 +02:00
README.md adding note for linux users 2014-02-15 17:35:41 +01:00
background.js linux bugfixes for window handlers 2014-02-22 09:52:28 +01:00
changelog.html setting up for next dev cycle 2014-02-23 18:21:22 +01:00
main.html adding label element around auto-connect 2014-02-22 23:58:41 +01:00
main.js removing obsolete message 2014-02-26 06:49:38 +01:00
manifest.json setting up for next dev cycle 2014-02-23 18:21:22 +01:00

README.md

baseflight configurator

Configurator is based on chrome.serial API (currently found only in google chrome and chromium web browsers).

I am using Flotr2 as a plotting library (with a few UI tweaks).

Installation

    • Click add to Chrome
    • You are done

Alternative way

    • Clone the repo to any local directory or download it as zip
    • Start chromium or google chrome and go to tools -> extension
    • Check the "Developer mode" checkbox
    • Click on load unpacked extension and point it to the baseflight configurator directory (for example D:/baseflight-configurator)
    • Note: Don't go "inside" configurators directory (just point to the folder)
    • You are done

How to use

You can find the baseflight configurator icon in your application tab "Apps"

Linux users

  1. Dont forget to add your user into dialout group "sudo usermod -aG dialout YOUR_USERNAME" for serial access
  2. If you have 3D model animation problems, Enable "Override software rendering list" in chrome flags chrome://flags/#ignore-gpu-blacklist

Developers

We accept clean and reasonable patches, always target the "development" branch for the pull requests