Release 6.0.0 #1710
Merged
Release 6.0.0 #1710
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This PR allows default baud rates to be set, per function, on the ports page. For example, SmartPort should run at 57600 baud. But, when the option is selected currently, the baud rate stays at 115200. This PR corrects that.
- Add missing airspeed alarms - Slight reorganisation of alarms - Only show alarms when they should be available - Hide CRSF section when not using CRSF protocol - Hide Baro temp and/or ESC telemetry elements when no barometer and/or ESC telemetry is available.
Sorts Rx providers alphabetically.
Created new branch based on MrD_Use-cardinal-indicator-for-ESP32-Radar. Due to problems updating from master.
…en-selecting-port-device Allow default baud rates on ports page
OSD: Add missing alarms, and set visibility based on availability
Default updates
Dynamic gyro LPF configuration
…-markers,-plus-pan-enhancements Pan Enhancements and cardinal markers for ESP32 Radar
Bump min version to 6.0.0
…-OSD-page-more-intuitive
Update defaults for new AHRS parameter names
…AHRS-parameter-names Update defaults_dialog.js
- Added const to make bitfield stuff more readable - changed `checkAltElevationSanity()` as it was treating P3 as a Boolean. Some times this function was called with explicitly not using absolute altitude. This is still possible. The function can accept a Boolean _or_ the P3 bitfield. - Fixed issue where alt and user action checkboxes could not be unset. - Added **.mission** filter to the load mission from file dialog box.
One other change to stop using P3 as a Boolean.
Fixed the cat's contribution.
…com/iNavFlight/inav-configurator into MrD_Fix-alt-type-in-mission-planner
Move storage of P£ til after the check
Revise setBit function
…planner Mission Control: Bug fixes related to P3 field
1. When save and reboot was applied on the mixer page, the has flaps option was not saved. 2. When defaults were selected, the auto-mixer application did not take mixer config in to account.
…pearing-when-save-and-reboot-applied Fixed mixer config issues
Fix led direction saving issue reported in #1731
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.