1.7.3 Release notes - iNavFlight/inav GitHub Wiki

Please read the release notes carefully and upgrade INAV Configurator available at Chrome Store. You can also use Configurator built as a native MacOS or Windows application.

INAV is and will remain open-source and free, but you are more than welcome to support the development.

This release was supported by our awesome sponsors CarbonBird.com, Airbot and ADPM Drones.

Known bugs

OSD blinking doesn't work [#2088]
No I2C available on Matek F405-OSD [#2047]

EOL announcement

This release is the last release featuring F1-based boards (NAZE, CC3D, AirHero32). They don't have enough memory and CPU power to make use of new code. Support is not removed from source tree, DIY-ers are welcome to build their own setups.

Bugs that are related to limited memory and/or CPU power on those boards won't be fixed. Functionality issues will only be fixed if they would be reproducible on more powerful F3/F4/F7 targets.

CLI parameter renaming / new parameters

New parameters have been introduced. Some CLI parameters were renamed to support new features or to better reflect their meaning:

Old name	New name(s)
`i2c_overclock`	`i2c_speed`
-	`cpu_underclock`
-	`smartport_fuel_percent`

I2C bus speed selection

Some sensors (especially cloned barometer/compass sensors) are reported to work unreliably on default 400kHz speed. New i2c_speed setting allows to reduce I2C clock rate to 200kHz and 100kHz to allow these picky sensors to function properly. Overclocking to 800kHz is also possible but not recommended.

If on your board compass/baro sensor is not recognized or hangs (usually indicated by rapidly increasing I2C error count) please try setting i2c_speed to 200KHZ before reporting a bug.

Underclocking for F1/F3 targets

F1/F3 boards are working on 72MHz clock which may interfere with 433MHz long range RC control systems. A new CLI option (cpu_underclock) for F1 and F3-based targets allows user to select between 72MHz (default) and 48MHz CPU clock. Should theoretically reduce interference to 433MHz LRS systems.

Other clock speeds are not possible because native USB will only function with 72/48MHz system clock speed.

Use caution - lower CPU speed means that you'll probably have to slow down looptime as well to keep CPU usage within sane limits.

New boards

New features

Support for MTK GPS automatic configuration
New experimental DIY sonar-to-I2C converter support (https://github.com/iNavFlight/INAV-Rangefinder-I2C-interface)
MatekF405 boards now support common I2C baro/compass sensors. Note that MatekF405 OSD board doesn't have I2C outputs so only MatekF405 AIO board can benefit from the change
Add airspeed indication to OSD
Add analog pitot sensor support for all F3/F4 targets
Support for VL53L0X laser rangefinder (short range)
Add RunCam Split control via RC radio
MSPv2 protocol
AIRMODE now available as a feature to have it always enabled (recommended for airplanes)
QMC5883 compass support (pin-to-pin compatible to HMC5883L sensor, used in some Chinese GPS modules)
Multiple Smartport telemetry improvements
Add support for UK mode units in the OSD (Show the speed in mp/h while using metric for other values)
Speed up blackbox downloading. Now downloading full 8Mb dataflash takes mere minutes.

Bugs fixed

Fix ledstrip on Omnibus target
Fix HEX6X mixer
Fix OSD crosshair blinking
Fix OSD ghost AHI
Fix feature bits being reset when exiting CMS
Fix bug with UK units in OSD
Fix horizon drift bug on some boards with OSD
Fix altitude control not working under 5m altitude on airplanes
Fix swapped values for frsky_unit in CLI. Dumps from previous versions should be modified to change IMPERIAL to METRIC and viceversa before restoring them on INAV >= 1.7.3.
Fix auto re-arm after landing issue when using switch-arming and landing with zero throttle in RTH & auto-disarm
Fix BlueJayF4 gyro not detected

Kudos

@martinbudden, @stronnag, @fiam, @DzikuVx, @oleost, @Schalonsus, @adtinnis, @sambas, @teckel12