Clean-code version of baseflight flight-controller - flight controllers are used to fly multi-rotor craft and fixed wing craft.
This fork differs from baseflight in that it attempts to use modern software development practices which result in:
- Greater reliability through code robustness and automated testing.
- Easier maintenance through code cleanliness.
- Easier to develop new features.
- Easier to re-use code through code de-coupling and modularisation.
The MultiWii software, from which baseflight originated, violates many good software development best-practices. Hopefully this fork will go some way to address them. If you see any bad code in this fork please immediately raise an issue so it can be fixed, or better yet submit a pull request.
Cleanflight also has additional features not found in baseflight.
- Multi-color RGB LED strip support (each LED can be a different color using variable length WS2811 addressable RGB strips - use for orientation indicators, low battery warning, flight mode status, etc.).
- Oneshot ESC support.
- Blackbox flight recorder logging (to onboard flash or external SD card).
- Support for additional targets that use the STM32F3 processors (baseflight only supports STM32F1).
- Support for the Seriously Pro Racing F3 board (STM32F303, I2C sensors, large flash, excellent I/O.).
- Support for the TauLabs Sparky board (STM32F303, I2C sensors, based board with acc/gyro/compass and baro, ~$35).
- Support for the OpenPilot CC3D board (STM32F103, board, SPI acc/gyro, ~$20).
- Support for the CJMCU nano quadcopter board.
- Support for developer breakout boards: (Port103R, EUSTM32F103RC, Olimexino, STM32F3Discovery).
- Support for more than 8 RC channels - (e.g. 16 Channels via FrSky X4RSB SBus).
- Support for N-Position switches via flexible channel ranges - not just 3 like baseflight or 3/6 in MultiWii.
- Lux's new PID (uses float values internally, resistant to looptime variation).
- Simultaneous Bluetooth configuration and OSD.
- Better PWM and PPM input and failsafe detection than baseflight.
- Better FrSky Telemetry than baseflight.
- LTM Telemetry.
- Smartport Telemetry.
- RSSI via ADC - Uses ADC to read PWM RSSI signals, tested with FrSky D4R-II and X8R.
- OLED Displays - Display information on: Battery voltage, profile, rate profile, version, sensors, RC, etc.
- In-flight manual PID tuning and rate adjustment.
- Rate profiles and in-flight selection of them.
- Graupner PPM failsafe.
- Graupner HoTT telemetry.
- Multiple simultaneous telemetry providers.
- Configurable serial ports for Serial RX, Telemetry, MSP, GPS - Use most devices on any port, softserial too.
- And many more minor bug fixes.
For a list of features, changes and some discussion please review the thread on MultiWii forums and consult the documentation.
If what you need is not covered, check the Baseflight documentation. If you still can't find what you need then visit the #cleanflight channel on the Freenode IRC network (info below).
IRC Support and Developers Channel
There's a dedicated Cleanflight IRC channel on the Freenode IRC network:
If you are using Windows and don't have an IRC client installed, take a look at HydraIRC.
Etiquette: Don't ask to ask and please wait around long enough for a reply - sometimes people are out flying, asleep or at work and can't answer immediately.
There is a dedicated Cleanflight YouTube channel which has progress update videos, flight demonstrations, instructions and other related videos.
Please subscribe and '+1' the videos if you find them useful.
To configure Cleanflight you should use the Cleanflight-configurator GUI tool (Windows/OSX/Linux) that can be found here:
The source for it is here:
Contributions are welcome and encouraged. You can contribute in many ways:
- Documentation updates and corrections.
- How-To guides - Received help? Help others!
- Bug fixes.
- New features.
- Telling us your ideas and suggestions.
The best place to start is the IRC channel on freenode (see above), drop in, say hi. Next place is the github issue tracker:
Before creating new issues please check to see if there is an existing one, search first otherwise you waste peoples time when they could be coding instead!
Please refer to the development section in the docs/development folder.
TravisCI is used to run automatic builds: https://travis-ci.org/cleanflight/cleanflight