| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Please carefully read all of this document for the best possible experience and safety.
Contact other pilots, share experiences, suggestions and ask for help on:
| INAV Discord Server | |
| INAV Official on Facebook |
INAV 9.1 is primarily a maintenance release focused on reliability improvements, safety fixes, and GPS accuracy. Since 9.0.1: 46 fixes and 76 new features/enhancements, including 19 new hardware targets. It contains no incompatible settings changes — your 9.0.x diff all will load cleanly.
For full PR-by-PR detail, see the wiki release notes.
Note
The INAV 9.1 Configurator includes a settings migration tool in the CLI tab that can assist with upgrading from older versions.
If you have the FLYINGRCF4WINGMINI, you will need to re-do the accelerometer alignment, as the gyro rotation has been corrected.
Two GPS defaults have changed. These only affect you if you never explicitly set them in your configuration (i.e., they are not in your diff all):
Warning
If you have increased nav_mc_pos_z_p or nav_mc_vel_z_p above their default values since INAV 7.1, it is advisable to lower those gains or re-tune them to avoid possible throttle oscillations in navigation modes that control altitude (WP, Cruise, RTH, and forward-flight Poshold).
The improved position estimator relies more on accelerometer weighting, so ensure your multicopter or VTOL is free from propeller and motor vibrations. See Multirotor filter setup for tips.
INAV now provides an optimized GPS update rate based on your hardware type (M8, M9, M10) and the number of active constellations. PR #11262
Pilots flying without a compass can now point the front of their multicopter or VTOL toward a known North heading before takeoff. PR #11529
Several changes improve multicopter position hold accuracy when GPS signal is poor or fluctuating. #11270, #11322, #11387
Post-disarm stats, Multifunction mode expansion, toilet-bowl compass deviation warning, and Surface mode/Geozone message improvements. #11506, #11308, #10854
New Sensors: ICM-45686 IMU, MS5525DSO airspeed sensor, SSD1315 OLED display, LSM6DSV16X/LSM6DSK320X accgyro
New Flash Storage: XT25F128F, MX35LF2G
19 New Targets: AIKONF4V2, AXISFLYINGH743PRO, BLADE_F4, BLUEBERRYH743, BLUEBERRYF405, Brahma H7, DAKEFPVH743_SLIM, FlyDragon Pro, FLYWOOF405HD, FLYWOOF405PRO, FRSKYF405, HAKRCH743, NEXUS (Original), PAURCF405V2, SDMODELH7V2, SimplyFly H7, SOLOGOODF722, TBS_LUCID_H7_OEM, TBS_LUCID_H7_V3
Full list: wiki release notes (see "Since 9.1.0-RC1" section)
Full Changelog: 9.0.1...9.1.0
Wiki Release Notes: https://github.com/iNavFlight/inav/wiki/9.1.0-Release-Notes
Please carefully read all of this document for the best possible experience and safety.
Contact other pilots, share experiences, suggestions and ask for help on:
| INAV Discord Server | |
| INAV Official on Facebook |
This is a Release Candidate. RC builds are for testing purposes. If you find issues, please report them on GitHub Issues.
INAV 9.1 is primarily a maintenance release focused on reliability improvements, safety fixes, and GPS accuracy. It contains no incompatible settings changes — your 9.0.x diff all will load cleanly.
Note
The INAV 9.1 Configurator includes a settings migration tool in the CLI tab that can assist with upgrading from older versions (7.0+).
Two GPS defaults have changed. These only affect you if you never explicitly set them in your configuration (i.e., they are not in your diff all):
Warning
If you have increased nav_mc_pos_z_p or nav_mc_vel_z_p above their default values since INAV 7.1, it is advisable to lower those gains or re-tune them to avoid possible throttle oscillations in navigation modes that control altitude (WP, Cruise, RTH, and forward-flight Poshold).
The improved position estimator relies more on accelerometer weighting, so ensure your multicopter or VTOL is free from propeller and motor vibrations. See Multirotor filter setup for tips.
INAV now provides an optimized GPS update rate based on your hardware type (M8, M9, M10) and the number of active constellations. More constellations at lower update rates generally gives better position accuracy. Configure in the Configurator GPS Tab. PR #11262
Pilots flying without a compass can now point the front of their multicopter or VTOL toward a known North heading before takeoff, allowing navigation modes to activate without first flying a short distance to acquire a GPS course. PR #11529
Several changes improve multicopter position hold accuracy when GPS signal is poor or fluctuating, with small benefits for fixed-wing navigation as well. #11270, #11322, #11387
AIKONF4V2, BLADE_F4, BLUEBERRYH743, BLUEBERRYF405, Brahma H7, FlyDragon Pro, FLYWOOF405HD, FLYWOOF405PRO, FRSKYF405, HAKRCH743, NEXUS (Original), PAURCF405V2, SDMODELH7V2, SimplyFly H7, TBS_LUCID_H7_OEM, TBS_LUCID_H7_V3
Full Changelog: 9.0.1...9.1.0-RC1
Wiki Release Notes: https://github.com/iNavFlight/inav/wiki/9.1.0-Release-Notes
Please carefully read all of this document for the best possible experience and safety.
Contact other pilots, share experiences, suggestions and ask for help on:
| INAV Discord Server | |
| INAV Official on Facebook |
This is a patch release with bug fixes and new target support. No settings have been renamed or removed, so your 9.0.0 configuration will work without changes.
Tip
Concerning step 6.
It can be a safer option to load your Diff All settings in two parts if you are using multiple Profiles. e.g. Control, Mixer or Battery.
This can be done by copying and loading the Diff All text setting from the top, down to the bottom of the # master settings category. Then load that into the CLI and press enter. Once it has written, press the Save Settings button.
Wait until it reboots and go back to the CLI tab again, then copy and load the rest of the Diff All text file. Starting from the # Control_profile 1 settings category, down to the bottom. Press enter. Once written, it will save by itself.
Rather than steps 4 and 5 above. You can try this diff update tool. This is a work in progress. Currently it will try to update version 7 or later diffs to version 8 or later. Just paste your full diff all (not dump) in to the tool. Select the INAV version you're upgrading to. Then press the button. It will create a new diff for you and give you warnings about anything you should check.
Please follow the instructions on this page.
Full Changelog (since 9.0.0): 9.0.0...9.0.1
Full Changelog (since 8.0.1): 8.0.1...9.0.1
Wiki Release Notes: https://github.com/iNavFlight/inav/wiki/9.0.0-Release-Notes
Stable Release
This is the stable 9.0.0 release. For a complete list of changes since 8.0.1, please see the 9.0.0 Release Notes Wiki.
Tip
Concerning step 6.
It can be a safer option to load your Diff All settings in two parts if you are using multiple Profiles. e.g. Control, Mixer or Battery.
This can be done by copying and loading the Diff All text setting from the top, down to the bottom of the # master settings category. Then load that into the CLI and press enter. Once it has written, press the Save Settings button.
Wait until it reboots and go back to the CLI tab again, then copy and load the rest of the Diff All text file. Starting from the # Control_profile 1 settings category, down to the bottom. Press enter. Once written, it will save by itself.
Rather than steps 4 and 5 above. You can try this diff update tool. This is a work in progress. Currently it will try to update version 7 or later diffs to version 8 or later. Just paste your full diff all (not dump) in to the tool. Select the INAV version you're upgrading to. Then press the button. It will create a new diff for you and give you warnings about anything you should check.
Please follow the instructions on this page.
Full Changelog: 8.0.1...9.0.0
Wiki Release Notes: https://github.com/iNavFlight/inav/wiki/9.0.0-Release-Notes
Release Candidate 4 for Testing
This is a pre-release for testing purposes. Please report issues on GitHub.
Please carefully read all of this document for the best possible experience and safety.
Contact other pilots, share experiences, suggestions and ask for help on:
| INAV Discord Server | |
| INAV Official on Facebook |
Note
Make sure to remove props and check your motor and servo outputs before powering your upgraded flight controller with a battery for the first time. The changes to enable flexible motor and servo allocation may change what outputs your configuration uses by default.
Tip
Concerning step 6.
It can be a safer option to load your Diff All settings in two parts if you are using multiple Profiles. e.g. Control, Mixer or Battery.
This can be done by copying and loading the Diff All text setting from the top, down to the bottom of the # master settings category. Then load that into the CLI and press enter. Once it has written, press the Save Settings button.
Wait until it reboots and go back to the CLI tab again, then copy and load the rest of the Diff All text file. Starting from the # Control_profile 1 settings category, down to the bottom. Press enter. Once written, it will save by itself.
Rather than steps 4 and 5 above. You can try this diff update tool. This is a work in progress. Currently it will try to update version 7 or later diffs to version 8 or later. Just paste your full diff all (not dump) in to the tool. Select the INAV version you're upgrading to. Then press the button. It will create a new diff for you and give you warnings about anything you should check.
Please follow the instructions on this page.
Please test and report issues with:
Fixeding aircraft can now use a Pitot sensor or virtual airspeed to dynamically adjust the PIDFF gains inflight. This adds the advantage of a tighter stabilization response across the whole flight speed envelope.
Full details of setup and tuning can be found here. Under the topics APA and TPA and Pitch angle. Do not tune your PIFF too tight!
Via the Programming Framework. It allows the user to have more flexibility when flying in higher wind conditions. To ensure the airplane makes headway.
In addition, you can program it to dynamically adjust the minimum ground speed according to the Wind direction and Wind speed.
More information can be found in this link.
Allows the pilot to see the throttle as a vertical digital gauge.
Functional information can be found here in the PR link
Changes have been made to improve its operation on a broader range of airframes. One of two methods can be selected to better suited different climb rate conditions.
See here for more information. And the required PID tune settings for either control method.
Changes to the position estimator are mainly intended to improve issues with Z velocity accuracy but also includes code clean-ups and fixes.
There has also been setting changes added with the code alterations. Depending on the sensor data quality. It may be beneficial in some cases to revert your settings back to the old ones, or somewhere in between the two.
| Name CLI | Old | New |
|---|---|---|
| w_z_baro_v | 0.1 | 0.35 |
| inav_w_z_gps_p | 0.2 | 0.35 |
| inav_w_z_gps_v | 0.1 | 0.35 |
More information directly related to the changes can be found here.
QMC5883P magnetometer driver
| Name | Function |
|---|---|
| OSD_VERTICAL_SPEED_INDICATOR | New name for OSD vario |
| OSD_ADSB_WARNING | CMS stick menu |
| OSD_ADSB_INFO | CMS stick menu |
| OSD_THROTTLE_GAUGE | OSD |
| OSD_NAV_MIN_GROUND_SPEED | OSD |
The Minimum Ground Speed and Throttle Gauge additions to the OSD require new font symbols. The analogue fonts are up-to-date. However, there may be time needed for this to propagate to the digital systems. For HDZero and Walksnail A...
This release candidate is for testing the new features and changes that will be part of the INAV 9.0.0 release soon
Please carefully read all of this document for the best possible experience and safety.
Contact other pilots, share experiences, suggestions and ask for help on:
| INAV Discord Server | |
| INAV Official on Facebook |
Note
Make sure to remove props and check your motor and servo outputs before powering your upgraded flight controller with a battery for the first time. The changes to enable flexible motor and servo allocation may change what outputs your configuration uses by default.
Tip
Concerning step 6.
It can be a safer option to load your Diff All settings in two parts if you are using multiple Profiles. e.g. Control, Mixer or Battery.
This can be done by copying and loading the Diff All text setting from the top, down to the bottom of the # master settings category. Then load that into the CLI and press enter. Once it has written, press the Save Settings button.
Wait until it reboots and go back to the CLI tab again, then copy and load the rest of the Diff All text file. Starting from the # Control_profile 1 settings category, down to the bottom. Press enter. Once written, it will save by itself.
Rather than steps 4 and 5 above. You can try this diff update tool. This is a work in progress. Currently it will try to update version 7 or later diffs to version 8 or later. Just paste your full diff (not dump) in to the tool. Select the INAV version you're upgrading to. Then press the button. It will create a new diff for you and give you warnings about anything you should check.
Please follow the instructions on this page.
Full Changelog: 9.0.0-RC2...9.0.0-RC3
This release candidate introduces new features and improvements for testing before the official INAV 9.0.0 release. Users are advised to remove props and verify motor/servo outputs before first battery power-up, as flexible motor and servo allocation may alter default output configurations.
The Programming Framework now enables dynamic adjustment of minimum ground speed based on wind conditions, allowing aircraft to maintain headway in challenging flight environments.
A new vertical digital throttle gauge display option provides pilots with real-time throttle visualization on-screen.
Two selectable altitude control methods accommodate different airframe types and climb rate requirements:
Enhanced Z velocity accuracy through algorithm refinements and new default weighting parameters for barometric and GPS measurements.
New QMC5883P magnetometer driver support expands hardware compatibility.
New Settings include blackbox arm control extension, temperature correction factors, ADSB warning styles, and VTOL transition PID multipliers.
New Flight Controller Targets: 32 additional targets now supported, including variants from Blueberry, DakeFPV, TBS, and others.
New elements: OSD_VERTICAL_SPEED_INDICATOR, OSD_ADSB_WARNING, OSD_ADSB_INFO, OSD_THROTTLE_GAUGE, and OSD_NAV_MIN_GROUND_SPEED.
From INAV 8.0, users must perform full chip erase during flashing and reload configuration via CLI diff commands. Phased loading of multi-profile settings is recommended for safety.
The term "PID Profile" has been renamed to "Control Profile" throughout INAV 9.0 to better reflect that these profiles control more than just PID settings.
| Old Name (8.0.x) | New Name (9.0.0) | Notes |
|---|---|---|
| controlrate_profile | use_control_profile | Selects which control profile to use |
| mixer_pid_profile_linking | mixer_control_profile_linking | Links mixer profile to control profile |
| osd_pan_servo_pwm2centideg | osd_pan_servo_range_decadegrees | Pan servo range renamed for clarity |
| Setting Name | Reason | Replacement |
|---|---|---|
| reboot_character | Legacy MSP reboot method removed | Use standard MSP reboot command |
This release candidate is for testing the new features and changes that will be part of the INAV 9.0.0 release soon
Please carefully read all of this document for the best possible experience and safety.
Contact other pilots, share experiences, suggestions and ask for help on:
| INAV Discord Server | |
| INAV Official on Facebook |
Note
Make sure to remove props and check your motor and servo outputs before powering your upgraded flight controller with a battery for the first time. The changes to enable flexible motor and servo allocation may change what outputs your configuration uses by default.
Tip
Concerning step 8.
It can be a safer option to load your Diff All settings in two parts if you are using multiple Profiles. e.g. Control, Mixer or Battery.
This can be done by copying and loading the Diff All text setting from the top, down to the bottom of the # master settings category. Then load that into the CLI and press enter. Once it has written, press the Save Settings button.
Wait until it reboots and go back to the CLI tab again, then copy and load the rest of the Diff All text file. Starting from the # Control_profile 1 settings category, down to the bottom. Press enter. Once written, it will save by itself.
Please follow the instructions on this page.
Via the Programming Framework. It allows the user to have more flexibility when flying in higher wind conditions. To ensure the airplane makes headway.
In addition, you can program it to dynamically adjust the minimum ground speed according to the Wind direction and Wind speed.
More information can be found in this link.
Allows the pilot to see the throttle as a vertical digital gauge.
Functional information can be found here in the PR link
Changes have been made to improve its operation on a broader range of airframes. One of two methods can be selected to better suited different climb rate conditions.
See here for more information. And the required PID tune settings for either control method.
Changes to the position estimator are mainly intended to improve issues with Z velocity accuracy but also includes code clean-ups and fixes.
There has also been setting changes added with the code alterations. Depending on the sensor data quality. It may be beneficial in some cases to revert your settings back to the old ones, or somewhere in between the two.
| Name CLI | Old | New |
|---|---|---|
| w_z_baro_v | 0.1 | 0.35 |
| inav_w_z_gps_p | 0.2 | 0.35 |
| inav_w_z_gps_v | 0.1 | 0.35 |
More information directly related to the changes can be found here.
QMC5883P magnetometer driver
| Name | Function |
|---|---|
| OSD_VERTICAL_SPEED_INDICATOR | New name for OSD vario |
| OSD_ADSB_WARNING | CMS stick menu |
| OSD_ADSB_INFO | CMS stick menu |
| OSD_THROTTLE_GAUGE | OSD |
| OSD_NAV_MIN_GROUND_SPEED | OSD |
| Function | Name | Values |
|---|---|---|
| Battery | SMARTPORT | vbat_meter_type , current_meter_type |
| Programming Framework | Gimbal Sensitivity | Scales Operand A from [-16 : 15] |
| Programming Framework | Override Minimum Ground Speed | When active, sets the minimum ground speed to the value specified in Operand A [m/s]. Minimum allowed value is set in nav_min_ground_speed. Maximum value is 150 |
| Programming Framework | Minimum Ground Speed [m/s] | The current minimum ground speed allowed in navigation flight modes |
| Programming Framework | Horizontal Wind Speed [cm/s] | Estimated wind speed. If the wind estimator is unavailable or the wind estimation is invalid, -1 is returned |
| Programming Framework | Wind Direction [deg] | Estimated wind direction. If the wind estimator is unavailable or the wind estimation is invalid, -1 is returned |
| Programming Framework | Relative Wind Offset [deg] | The relative offset between the heading of the aircraft and the heading of the wind. 0 indicates flying directly into a headwing. Negative numbers are a left offset. For example, if -20° is shown, turning right will correct towards 0. If the wind estimator is unavailable or the wind estimation is invalid, 0 is returned |
| Name | Description |
|---|---|
| blackbox_arm_control | Can extend blackbox logging up to 60 seconds after disarming |
| acc_temp_correction | Accelerometer temperature correction factor to compensate for acceleromter drift |
| baro_temp_correction | Baro temperature correction factor to compensate for Baro altitude drift |
| osd_adsb_warning_style | ADSB warning element style - COMPACT or EXTENDED |
| nav_fw_alt_use_position | Use position for fixed wing altitude control rather than velocity |
| osd_pan_servo_range_decadegrees | Replaces the name of the old osd_pan_servo_pwm2centideg |
| mavlink_autopilot_type | Sets the Mavlink telemetry type - GENERIC or ARDUPILOT |
| transition_pid_mmix_multiplier_pitch | Intended to solve pitch coupling in transtion mode on tilting rotor VTOL |
| transition_pid_mmix_multiplier_roll | intended to solve roll/yaw coupling oscillation in transtion mode on tilting rotor VTOL |
| transition_pid_mmix_multiplier_yaw | Intended to solve yaw/roll coupling oscillation in transtio... |
Please carefully read all of this document for the best possible experience and safety.
Contact other pilots, share experiences, suggestions and ask for help on:
| INAV Discord Server | |
| INAV Official on Facebook |
INAV 8 no longer includes F411 targets as part of the official release.
GPS: UBLOX7 and UBLOX have been merged into a single UBLOX option, and units with older firmware are now deprecated. Only M8 and newer will be supported in the future.
Make sure to remove props and check your motor and servo outputs before powering your upgraded flight controller with a battery for the first time. The changes to enable flexible motor and servo allocation may change what outputs your configuration uses by default.
This is a minor release and If nothing serious is found, this will be released as 8.0.1 final.
This tool can help migrate your INAV 7.x diff over to INAV 8.0.0. It will take care of the major changes that have been highlighted in these release notes.
Please follow the instructions on this page.
DJI has released new firmware for O4, DJI Goggles 2, 3, N3 and integra that will add INAV font support on those goggles and fix the armed detection in O4.
With configurator 8.0.1 you should be able to select DJI_NATIVE as the video system, but if you don't want to upgrade, the AVATAR option should also give you the correct INAV font and canvas size, but don't forget to select INAV as the OSD type in your updated goggles.
The O4 arming workaround will be remove in INAV 9.
The Geozone feature allows pilots to define one or multiple areas on the map in Mission Control, to prevent accidental flying outside of allowed zones (Flight-Zones, FZ) or to avoid certain areas they are not allowed or not willing to fly in (No-Flight-Zone, NFZ). This type of feature might be known to many pilots as a "Geofence" and despite providing the same core functionality, INAV Geozones are significantly more versatile and provide more safety and features. Read the Documentation for more info
IMPORTANT: Geozones will not be available for STM32F722 based Flight Controllers due to insufficient flash storage.
This new feature allows INAV to return to its launch location, in case of a failed GPS due to hardware failure or interference. INAV will use the remaining sensors and the already calculated wind speed and direction, to blindly return towards the home location. For this feature, no extra sensors are strictly necessary, aside from the standard Accelerometer, Gyroscope and Barometer, but its highly recommended to have a compass and for best precision, to also have an Airspeed sensor. The feature will not be able to precisely return to the pilot, but it allows the Aircraft to either get out of an area with interferences, or to give the pilot time and a chance to regain control for a manual return, when the aircraft is closer. Details here
A new MSP Message that allows RC links that communicate with the Flight controller via MSP, to provide Link Information to INAV like LQ, RSSI, Power Level, SNR and more. The first RC Link to support this is the mLRS Project with more possibly coming in the future. Details here
MSP-VTX has been updated by @geoffsim to increase compatibility with HDZero vtxs.
The previously simple Mavlink Telemetry was extended to be compatible with flow control capable links (Thanks @MUSTARDTIGERFPV). This now allows RC Control via Mavlink and Telemetry at the same time over a Single UART. It is tested successfully with ELRS Mavlink-RC and mLRS Mavlink. Additionally it allows the Use of Mission Planner, QGroundControl and potentially other GCS Applications to be used for Flight Monitoring with INAV.
Note: To receive RSSI and LQ for ELRS Mavlink-RC you need to set mavlink_radio_type=ELRS in the CLI. Details here
INAV now also supports the Caddx / Walksnail GM Series Gimbals. These can now be controlled via a dedicated uart UART or via MSP and don't need up to 3 PWM Outputs anymore. This enables the direct Gimbal Control via Head Tracking from Walksnail goggles, without additional wiring. Details Here
It is now possible to connect an ADSB receiver to your flight controller and get OSD Warnings if any ADSB enabled Aircraft, is close by. INAV Configurator can show these Aircraft on the map for additional safety of UAV flights. ADSB is supported for generally available receivers like uAvionix pingRX (not tested) and Aerobit TT-SC1 (tested) and should also work with the upcoming PicoADSB Details here
The Fixed Wing PIDFF Controller was reworked. The PIDs are now attenuated based in the amount of Setpoint (Stick deflection in Acro Mode) for a more "Manual" flight feel during aggressive inputs while keeping the locked in feel of a PID-Assisted flight. This allows the Pilot to have a PID tune with very high P and I values for a locked in flight feel, while keeping a good manual feeling of the plane's flight characteristics, especially when flying slow. Additionally the Attenuation fixes the Bounce-Back caused by the Integral of the PID controller, after sharp roll or pitch inputs. Details Here
AssistNow is a Service that provides GPS Satellite information data for offline-applications, to dramatically increase the time to fix for GPS Devices. By Providing your own AssistNow Token, INAV Configurator can automatically download the latest data set and transfer it to any connected INAV UAV. With this, a GPS fix after cold start should merely take seconds instead of minutes. This is especially helpful for people who go fly with a big fleet of aircraft. Details here
The sensor IDs for the Modes and GNSS data have changed in SmartPort telemetry. The default settings in INAV are to now use the new sensor IDs. The INAV OpenTX-Telemetry-Widget has been updated to use these new IDs. So you will not see any issues when using the latest version of this widget. However, if you use another widget or app that uses the SmartPort telemetry. It is r...
Please carefully read all of this document for the best possible experience and safety.
Contact other pilots, share experiences, suggestions and ask for help on:
| INAV Discord Server | |
| INAV Official on Facebook |
INAV 8 no longer includes F411 targets as part of the official release.
GPS: UBLOX7 and UBLOX have been merged into a single UBLOX option, and units with older firmware are now deprecated. Only M8 and newer will be supported in the future.
Make sure to remove props and check your motor and servo outputs before powering your upgraded flight controller with a battery for the first time. The changes to enable flexible motor and servo allocation may change what outputs your configuration uses by default.
This is a minor release and If nothing serious is found, this will be released as 8.0.1 final.
This tool can help migrate your INAV 7.x diff over to INAV 8.0.0. It will take care of the major changes that have been highlighted in these release notes.
Please follow the instructions on this page.
DJI has released new firmware for O4, DJI Goggles 2, 3, N3 and integra that will add INAV font support on those goggles and fix the armed detection in O4.
With configurator 8.0.1 you should be able to select DJI_NATIVE as the video system, but if you don't want to upgrade, the AVATAR option should also give you the correct INAV font and canvas size, but don't forget to select INAV as the OSD type in your updated goggles.
The O4 arming workaround will be remove in INAV 9.
The Geozone feature allows pilots to define one or multiple areas on the map in Mission Control, to prevent accidental flying outside of allowed zones (Flight-Zones, FZ) or to avoid certain areas they are not allowed or not willing to fly in (No-Flight-Zone, NFZ). This type of feature might be known to many pilots as a "Geofence" and despite providing the same core functionality, INAV Geozones are significantly more versatile and provide more safety and features. Read the Documentation for more info
IMPORTANT: Geozones will not be available for STM32F722 based Flight Controllers due to insufficient flash storage.
This new feature allows INAV to return to its launch location, in case of a failed GPS due to hardware failure or interference. INAV will use the remaining sensors and the already calculated wind speed and direction, to blindly return towards the home location. For this feature, no extra sensors are strictly necessary, aside from the standard Accelerometer, Gyroscope and Barometer, but its highly recommended to have a compass and for best precision, to also have an Airspeed sensor. The feature will not be able to precisely return to the pilot, but it allows the Aircraft to either get out of an area with interferences, or to give the pilot time and a chance to regain control for a manual return, when the aircraft is closer. Details here
A new MSP Message that allows RC links that communicate with the Flight controller via MSP, to provide Link Information to INAV like LQ, RSSI, Power Level, SNR and more. The first RC Link to support this is the mLRS Project with more possibly coming in the future. Details here
MSP-VTX has been updated by @geoffsim to increase compatibility with HDZero vtxs.
The previously simple Mavlink Telemetry was extended to be compatible with flow control capable links (Thanks @MUSTARDTIGERFPV). This now allows RC Control via Mavlink and Telemetry at the same time over a Single UART. It is tested successfully with ELRS Mavlink-RC and mLRS Mavlink. Additionally it allows the Use of Mission Planner, QGroundControl and potentially other GCS Applications to be used for Flight Monitoring with INAV.
Note: To receive RSSI and LQ for ELRS Mavlink-RC you need to set mavlink_radio_type=ELRS in the CLI. Details here
INAV now also supports the Caddx / Walksnail GM Series Gimbals. These can now be controlled via a dedicated uart UART or via MSP and don't need up to 3 PWM Outputs anymore. This enables the direct Gimbal Control via Head Tracking from Walksnail goggles, without additional wiring. Details Here
It is now possible to connect an ADSB receiver to your flight controller and get OSD Warnings if any ADSB enabled Aircraft, is close by. INAV Configurator can show these Aircraft on the map for additional safety of UAV flights. ADSB is supported for generally available receivers like uAvionix pingRX (not tested) and Aerobit TT-SC1 (tested) and should also work with the upcoming PicoADSB Details here
The Fixed Wing PIDFF Controller was reworked. The PIDs are now attenuated based in the amount of Setpoint (Stick deflection in Acro Mode) for a more "Manual" flight feel during aggressive inputs while keeping the locked in feel of a PID-Assisted flight. This allows the Pilot to have a PID tune with very high P and I values for a locked in flight feel, while keeping a good manual feeling of the plane's flight characteristics, especially when flying slow. Additionally the Attenuation fixes the Bounce-Back caused by the Integral of the PID controller, after sharp roll or pitch inputs. Details Here
AssistNow is a Service that provides GPS Satellite information data for offline-applications, to dramatically increase the time to fix for GPS Devices. By Providing your own AssistNow Token, INAV Configurator can automatically download the latest data set and transfer it to any connected INAV UAV. With this, a GPS fix after cold start should merely take seconds instead of minutes. This is especially helpful for people who go fly with a big fleet of aircraft. Details here
The sensor IDs for the Modes and GNSS data have changed in SmartPort telemetry. The default settings in INAV are to now use the new sensor IDs. The INAV OpenTX-Telemetry-Widget has been updated to use these new IDs. So you will not see any issues when using the latest version of this widget. However, if you use another widget or app that uses the SmartPort telemetry. It is recommended to inform the creator of the app/widget, as the old sensor IDs will be removed in INAV 10.0.0. Details here
You can change INAV to use the old sensor IDs ...
Please carefully read all of this document for the best possible experience and safety.
Contact other pilots, share experiences, suggestions and ask for help on:
| INAV Discord Server | |
| INAV Official on Facebook |
INAV 8 no longer includes F411 targets as part of the official release.
GPS: UBLOX7 and UBLOX have been merged into a single UBLOX option, and units with older firmware are now deprecated. Only M8 and newer will be supported in the future.
Make sure to remove props and check your motor and servo outputs before powering your upgraded flight controller with a battery for the first time. The changes to enable flexible motor and servo allocation may change what outputs your configuration uses by default.
This is a minor release and If nothing serious is found, this will be released as 8.0.1 final.
This tool can help migrate your INAV 7.x diff over to INAV 8.0.0. It will take care of the major changes that have been highlighted in these release notes.
Please follow the instructions on this page.
DJI will soon soon release new firmware for O4, DJI Goggles 2, 3, N3 and integra that will add INAV font and fix the arm detection.
With configurator 8.0.1 you should be able to select DJI_NATIVE as the video system, but if you don't want to upgrade, the AVATAR option should also work.
For O4 firmware V1.00.0100 and earlier, the follwing still applies:
DJI released a new air unit, and while rumors suggested it would include full INAV font support, that is unfortunately not true with the released firmware. There is also a bug on DJI firmware that prevents it from detecting when the flight controller is armed and leaves the air unit stuck in low power mode.
There are two possible workaround for the arming issues:
With the added workarounds, setup in INAV should be the same as O3.
The Geozone feature allows pilots to define one or multiple areas on the map in Mission Control, to prevent accidental flying outside of allowed zones (Flight-Zones, FZ) or to avoid certain areas they are not allowed or not willing to fly in (No-Flight-Zone, NFZ). This type of feature might be known to many pilots as a "Geofence" and despite providing the same core functionality, INAV Geozones are significantly more versatile and provide more safety and features. Read the Documentation for more info
IMPORTANT: Geozones will not be available for STM32F722 based Flight Controllers due to insufficient flash storage.
This new feature allows INAV to return to its launch location, in case of a failed GPS due to hardware failure or interference. INAV will use the remaining sensors and the already calculated wind speed and direction, to blindly return towards the home location. For this feature, no extra sensors are strictly necessary, aside from the standard Accelerometer, Gyroscope and Barometer, but its highly recommended to have a compass and for best precision, to also have an Airspeed sensor. The feature will not be able to precisely return to the pilot, but it allows the Aircraft to either get out of an area with interferences, or to give the pilot time and a chance to regain control for a manual return, when the aircraft is closer. Details here
A new MSP Message that allows RC links that communicate with the Flight controller via MSP, to provide Link Information to INAV like LQ, RSSI, Power Level, SNR and more. The first RC Link to support this is the mLRS Project with more possibly coming in the future. Details here
MSP-VTX has been updated by @geoffsim to increase compatibility with HDZero vtxs.
The previously simple Mavlink Telemetry was extended to be compatible with flow control capable links (Thanks @MUSTARDTIGERFPV). This now allows RC Control via Mavlink and Telemetry at the same time over a Single UART. It is tested successfully with ELRS Mavlink-RC and mLRS Mavlink. Additionally it allows the Use of Mission Planner, QGroundControl and potentially other GCS Applications to be used for Flight Monitoring with INAV.
Note: To receive RSSI and LQ for ELRS Mavlink-RC you need to set mavlink_radio_type=ELRS in the CLI. Details here
INAV now also supports the Caddx / Walksnail GM Series Gimbals. These can now be controlled via a dedicated uart UART or via MSP and don't need up to 3 PWM Outputs anymore. This enables the direct Gimbal Control via Head Tracking from Walksnail goggles, without additional wiring. Details Here
It is now possible to connect an ADSB receiver to your flight controller and get OSD Warnings if any ADSB enabled Aircraft, is close by. INAV Configurator can show these Aircraft on the map for additional safety of UAV flights. ADSB is supported for generally available receivers like uAvionix pingRX (not tested) and Aerobit TT-SC1 (tested) and should also work with the upcoming PicoADSB Details here
The Fixed Wing PIDFF Controller was reworked. The PIDs are now attenuated based in the amount of Setpoint (Stick deflection in Acro Mode) for a more "Manual" flight feel during aggressive inputs while keeping the locked in feel of a PID-Assisted flight. This allows the Pilot to have a PID tune with very high P and I values for a locked in flight feel, while keeping a good manual feeling of the plane's flight characteristics, especially when flying slow. Additionally the Attenuation fixes the Bounce-Back caused by the Integral of the PID controller, after sharp roll or pitch inputs. Details Here
AssistNow is a Service that provides GPS Satellite information data for offline-applications, to dramatically increase the time to fix for GPS Devices. By Providing your own AssistNow Token, INAV Configurator can automatically download the latest data set and transfer it to any connected INAV UAV. With this, a GPS fix after cold start should merely take seconds instead of minutes. This is especially helpful for people who go fly with a big fleet of aircraft. Details here
The sensor IDs for the Modes and GNSS data have changed in SmartPort telemetry. The default settings in INAV are to now use the new sensor IDs. The INAV OpenTX-Telemetry-Widget has been ...
| Back | FazBrowse Home | New Git URL |