15fbe0df3e
200ms seems to iteract badly with some digital systems, causing unreliable blinking. I will turn the cycle interval into a configuration variable in 8.0. 200ms = original value, unreliable blinking 500ms = acceptable blinking with walksnail 1000ms = was also tested and worked ok For software blink emulation, Blinking changes a character appearance at a given frequency, the OSD code on digital systems updates the OSD at a different arbitrary frequency. Depending on the relationship between the two you may not see the text, or it may not blink. Similar to how lights can blink if you have mismatched frequencies when recording video (50Hz mains, 60fps video). I also suspect that the way some of the digital systems handle blinking characters may rely on the clear screen command, which also happens at a given frequency in INAV. |
||
|---|---|---|
| .github | ||
| .vscode | ||
| board | ||
| cmake | ||
| dev | ||
| docs | ||
| lib/main | ||
| src | ||
| .dir-locals.el | ||
| .dockerignore | ||
| .gitattributes | ||
| .gitignore | ||
| .travis.sh | ||
| .travis.yml | ||
| .vimrc | ||
| AUTHORS | ||
| build.sh | ||
| build_docs.sh | ||
| CMakeLists.txt | ||
| Dockerfile | ||
| fake_travis_build.sh | ||
| JLinkSettings.ini | ||
| LICENSE | ||
| readme.md | ||
| Vagrantfile | ||
INAV - navigation capable flight controller
PSA
INAV no longer accepts targets based on STM32 F411 MCU.
INAV 7 is the last INAV official release available for F411 based flight controllers. The next milestone, INAV 8 will not be available for F411 boards.
INAV Community
Features
- Runs on the most popular F4, F7 and H7 flight controllers
- On Screen Display (OSD) - both character and pixel style
- DJI OSD integration: all elements, system messages and warnings
- Outstanding performance out of the box
- Position Hold, Altitude Hold, Return To Home and Waypoint Missions
- Excellent support for fixed wing UAVs: airplanes, flying wings
- Fully configurable mixer that allows to run any hardware you want: multirotor, fixed wing, rovers, boats and other experimental devices
- Multiple sensor support: GPS, Pitot tube, sonar, lidar, temperature, ESC with BlHeli_32 telemetry
- SmartAudio and IRC Tramp VTX support
- Blackbox flight recorder logging
- Telemetry: SmartPort, FPort, MAVlink, LTM, CRSF
- Multi-color RGB LED Strip support
- Advanced gyro filtering
- Logic Conditions, Global Functions and Global Variables: you can program INAV with a GUI
- And many more!
For a list of features, changes and some discussion please review consult the releases page and the documentation.
Tools
INAV Configurator
Official tool for INAV can be downloaded here. It can be run on Windows, MacOS and Linux machines and standalone application.
INAV Blackbox Explorer
Tool for Blackbox logs analysis is available here
INAV Blackbox Tools
Command line tools (blackbox_decode, blackbox_render) for Blackbox log conversion and analysis here.
Telemetry screen for EdgeTX and OpenTX
Users of EdgeTX and OpenTX radios (Taranis, Horus, Jumper, Radiomaster, Nirvana) can use INAV OpenTX Telemetry Widget screen. Software and installation instruction are available here: https://github.com/iNavFlight/OpenTX-Telemetry-Widget
INAV magnetometer alignment helper
INAV Magnetometer Alignment helper allows to align INAV magnetometer despite position and orientation. This simplifies the process of INAV setup on multirotors with tilted GPS modules.
OSD layout Copy, Move, or Replace helper tool
Easy INAV OSD switcher tool allows you to easily switch your OSD layouts around in INAV. Choose the from and to OSD layouts, and the method of transfering the layouts.
Installation
See: https://github.com/iNavFlight/inav/blob/master/docs/Installation.md
Documentation, support and learning resources
- INAV 5 on a flying wing full tutorial
- INAV on a multirotor drone tutorial
- Fixed Wing Guide
- Autolaunch Guide
- Modes Guide
- Wing Tuning Masterclass
- Official documentation
- Official Wiki
- Video series by Paweł Spychalski
- Target documentation
Contributing
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.
- Buying your hardware from this link
A good place to start is the Discord channel, Telegram channel or Facebook group. Drop in, say hi.
Github issue tracker is a good place to search for existing issues or report a new bug/feature request:
https://github.com/iNavFlight/inav/issues
https://github.com/iNavFlight/inav-configurator/issues
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!
Developers
Please refer to the development section in the docs/development folder.