2.5.0 Release Notes
Hello and welcome to INAV 2.5.0 Release!
Please carefully read all of this document for the best possible experience and safety.
Get in touch with other pilots, share experiences, suggestions and ask for help on:
 |
INAV Official on Telegram |
 |
INAV Official on Facebook |
Please continue to support developers, for free, by checking out from the following stores after having clicked on the following links:
 |
Support us on Banggood |
Your contribution from the past month has been very welcome! Thanks!
Tested and suggested hardware can be found here
- Download and install the new configurator
- Save to a file the current diff all from the CLI.
- Upgrade to INAV 2.5 using the Full Erase option in the configurator.
- Upload your OSD font of choice from the OSD tab.
- Go the CLI again and paste the contents on the file you previously create and write save , press ENTER and done!
- You should be ready, explore new 2.5 features and enjoy!
Please follow the instructions on this page.
| Command | Description |
|---|---|
| Setting | Description |
|---|---|
| Setting | Description |
|---|---|
- BME280 Barometer (@gereic)
Initial Rover and Boat support (@DzikuVx)
Description
Reversible ESCs support (@DzikuVx)
Description
New Matrix Filters for Multirotors (@DzikuVx)
Description
JUMP, HOLD and LAND Waypoint types support (@giacomo892, @Jacky2k, @stronnag)
New Waypoints types supported by INAV. Now INAV can perform much more complex missions!
- JUMP: Defines a 'jump' back to a prior waypoint number, allowing mission loops. The number of jumps may also be defined.
- POSHOLD_TIME: Defines the amount of time for which the aircraft will loiter at the waypoint position before proceeding to the next waypoint.
- LAND: Defines a location for landing. This allows INAV to perform one-way missions.
See the navigation messages wiki page for more information and an annotated example.
HUD POI Waypoints markers (@OlivierC-FR)
Shows the next waypoints in the hud. To enable this feature, enter the count of next waypoints in the CLI command:
set osd_hud_wp_disp = 0 to 3
Or on the CMS menu: OSD > HUD > Displayed items > Next waypoints: (from 0 to 3, 0 means disabled)
Then start a WP mission, the next WPs will appear as soon as the mission is loaded in FC memory AND that the aircraft has a valid GPS heading, so it must move if it's not fitted with a magnetometer.