1
0
Fork 0
mirror of https://github.com/betaflight/betaflight-configurator.git synced 2025-07-17 05:15:21 +03:00

updating readme

This commit is contained in:
cTn 2014-03-25 15:58:05 +01:00
parent a7fab85d42
commit cff066d5db

View file

@ -1,27 +1,26 @@
baseflight configurator
==================================
Configurator is based on chrome.serial API (currently found only in google chrome and chromium web browsers).
Baseflight Configurator
=======================
Configurator based on chrome.serial API running on Google Chrome/Chromium core
I am using Flotr2 as a plotting library (with a few UI tweaks).
Keep in mind that this configurator is the most up-to-date configurator implementation for Baseflight flight software,
in many cases it requires latest firmware on the flight controller, if you are experiencing any problems,
please make sure you are running the latest version of firmware.
Installation
------------
1. - Visit https://chrome.google.com/webstore/detail/baseflight-multiwii-confi/mppkgnedeapfejgfimkdoninnofofigk
2. - Click add to Chrome
3. - You are done
1. - Visit [Chrome web store](https://chrome.google.com/webstore/detail/baseflight-multiwii-confi/mppkgnedeapfejgfimkdoninnofofigk)
2. - Click <strong>+ Free</strong>
Alternative way
---------------
1. - Clone the repo to any local directory or download it as zip
2. - Start chromium or google chrome and go to tools -> extension
3. - Check the "Developer mode" checkbox
4. - Click on load unpacked extension and point it to the baseflight configurator directory (for example D:/baseflight-configurator)
5. - Note: Don't go "inside" configurators directory (just point to the folder)
6. - You are done
How to use
-----------
You can find the baseflight configurator icon in your application tab "Apps"
You can find the Baseflight - Configurator icon in your application tab "Apps"
Linux users
-----------
@ -30,4 +29,4 @@ Linux users
Developers
----------
We accept clean and reasonable patches, always target the "development" branch for the pull requests
We accept clean and reasonable patches, always target the <strong>"development"</strong> branch for the pull requests