Release: ArduPilot-4.6.0-beta2 #28838
Merged
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
we should only add fence types to the no auto-enable mask if the enable actually changed that type of fence. This fixes the case where the user has both FENCE_AUTOENABLE=3 and RCn_OPTION=11. The disable triggered by the init of the aux function was preventing the fence from auto-enabling
for polygon fences we need to check if the vehicle has a position and is inside the polygon
this is only ever set/checked within a function
the _auto_enable_mask was try to make AUX function overrides disable the FENCE_AUTOENABLE functionality. This isn't the right bevaviour, both the aux function and the auto-enable should be edge triggered, with last function taking effect
the automatic min-alt fence should not auto-enable based on altitude if the fence has been manually disabled. This is needed to allow for a manual landing by disabling the fence before descending
the FENCE_AUTOENABLE option should be honoured even with a fence switch in the disable position
in TAKEOFF mode with either very poor yaw source or no yaw source we need to use ground vector and wait for sufficient ground speed
avoid creation of static pointers to objects held within SRV_Channels
avoid creation of static pointers to objects held within SRV_Channels
avoid creation of static pointers to objects held within SRV_Channels
avoid creation of static pointers to objects held within SRV_Channels
avoid creation of static pointers to objects held within SRV_Channels
avoid creation of static pointers to objects held within SRV_Channels
avoid creation of static pointers to objects held within SRV_Channels
avoid creation of static pointers to objects held within SRV_Channels
avoid creation of static pointers to objects held within SRV_Channels
for symmetry with the push function
for symmetry with the push function
for symmetry with the push function
for symmetry with the push function
Issue introduced in ArduPilot#27370 and partially fixed in ArduPilot#27762, though evidently not properly tested. Failing to track the maximum can result in dangerously low values being calculated for `ATC_ACCEL_[RPY]_MAX` and the vehicle becoming unflyable. Make the variable a reference so that the maximum value is preserved between function calls.
|
I've added release notes and updated the versions |
rmackay9
approved these changes
Dec 11, 2024
andyp1per
approved these changes
Dec 11, 2024
rmackay9
force-pushed
the
pr-ArduPilot-4.6.0-beta2
branch
from
4210086 to
5576b4d
Compare
|
Thanks @tpwrules, I've pushed the contents of those PRs |
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.
changes for beta2
PRs included are listed in the 4.6.0-beta2 of this project