We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Add another related link
Fix destroyed 8.0 release notes
updated pr-agent best practices with auto analysis
Added graphical illustration of surface mode
Fix link
Add comprehensive optic flow and rangefinder documentation - Create new wiki guide: Optic-Flow-and-Rangefinder.md - Complete setup and configuration instructions - Hardware compatibility tables - Surface mode explanation and usage - GPS-free position hold with optic flow - Troubleshooting guide and examples - Update _Sidebar.md: Add "Rangefinder & Optic Flow" section - Update Modes.md: Expand SURFACE section with detailed explanation - Update Navigation-modes.md: Clarify rangefinder behavior and platform limitations - Update Calibration-Tab.md: Add optic flow calibration section Closes gap in user documentation - previously only had scattered mentions. Now provides complete reference for terrain following and indoor navigation.
Updated Getting started with iNav (markdown)
Updated 9.0.0 Release Notes (markdown)
Update some info for 9.0
Clean-ups
Update for 9.0 full release
Update info according to fixes made for the 9.0 full release
Updated Boards, Targets and PWM allocations (markdown)
Updated Target and Sensor support (markdown)
Updated _Sidebar (markdown)
More info on GNSS update rate
Add prominent download links to wiki Home page This change makes it easier for users to find and download INAV Configurator and firmware by adding a dedicated Downloads section near the top of the wiki Home page. The new Downloads section appears right after the hardware design guidelines link and before the "Using the wiki" section, making it immediately visible to users landing on the wiki. Benefits: - Reduces user friction - fewer clicks to find downloads - Improves user experience for new users - Links use /releases/latest URLs that automatically show the latest version - Clear instructions to select platform from Assets section 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <[email protected]>
Docs: Fix 'Available Objects' section to show namespaced API Replaced confusing destructuring syntax with clear organized list: - Shows actual namespaced syntax (inav.flight.*, inav.events.*, etc.) - Organized by category (Flight Data, Control & Override, etc.) - Updated Tips section to use namespaced syntax - Fixed RC channel range (1-18, not 0-17)
Docs: Update to use fully namespaced syntax Removed mention of const destructuring (no longer used). Updated all API references to use namespaced syntax: - inav.flight.*, inav.rc[n].*, inav.gvar[n] - inav.override.*, inav.pid[n].* - inav.events.edge(), inav.events.sticky(), etc. - inav.helpers.xor(), inav.helpers.mapInput(), etc. Documentation now shows only current syntax, not historical approaches.
Docs: Update JavaScript Programming wiki to use namespaced syntax Update all JavaScript code examples to use fully namespaced inav.* syntax instead of destructuring. This matches the transpiler changes that removed backward compatibility for destructuring syntax. Changes: - Remove const { flight, override, ... } = inav; destructuring - Replace flight.* with inav.flight.* - Replace override.* with inav.override.* - Replace gvar[ with inav.gvar[ - Replace rc[ with inav.rc[ - Replace waypoint.* with inav.waypoint.* - Replace pid[ with inav.pid[ - Replace edge() with inav.events.edge() - Replace sticky() with inav.events.sticky() - Replace delay() with inav.events.delay() - Replace timer() with inav.events.timer() - Replace whenChanged() with inav.events.whenChanged() All code examples now demonstrate the proper namespaced API access that users should use when writing JavaScript programs for INAV.
Updated Calibration Tab (markdown)
Add more details
Double check scaling limits in older 2016 branch to be sure.
Add info relating to setting relationships and reword float value.