Skip to content

ArduPilot-4.6.0-beta5 release #29654

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 101 commits into from
Apr 1, 2025
Merged

Conversation

rmackay9
Copy link
Contributor

@rmackay9 rmackay9 commented Mar 31, 2025

This is the ArduPilot-4.6.0-beta5 release which includes Copter, Rover, Plane and Tracker

The list of PRs included can be found in the 4.6.0-beta5 column of this project

There were also a few PRs that could not be merged without conflicts so I hope that the original devs of each PR can create backport PRs. This is primarily @tridge and @peterbarker. The list can be seen in the "merge conflict" column of this project but they are also copied below:

All feedback welcome including re the release notes

dakejahl and others added 30 commits March 31, 2025 20:08
we should stop looking for SOL as soon as we know we have PVT, instead
of waiting for all others to be cleared

may help with
https://discuss.ardupilot.org/t/fc-tries-to-config-gps-constantly-when-trying-to-arm-in-loiter-mode/129930
if we get an unexpected VALSET NACK we could dereference NULL. This
could happen if we reboot while configuring an invalid key
messages coming in with a size of 24120 bytes.  It takes so long to try to read those bytes in (at the device's message rate) that we time out the GCS and try detecting again
if using GPS and our horizontal velocity innovation is high then mark
the filter as unhealthy, which causes an arming failure

this helps with ArduPilot#29384
tridge and others added 12 commits April 1, 2025 14:50
if the GCS commands a guided re-position with an AGL frame and
quadplane is in Q_GUIDED_MODE=1 then this prevents us adding the home
altitude to the target terrain altitude
check for range of terrain heights while repositioning
similarly to the way we do batteries, do not scale the amount of telemetry sent according to the number of backends we have.
... and reduce the default rate

this is currently unconditionally streamed at 50Hz, chewing up all available bandwidth on some telemetry radios.
only compiled in on Rover at the moment.

need to add an additional Rover-specific check for frame type, so move this code into Rover for now.
only compiled in on Rover at the moment.

need to add an additional Rover-specific check for frame type, so move this code into Rover for now.
@rmackay9 rmackay9 force-pushed the ap-460-beta5 branch 2 times, most recently from 78a5370 to 3e96323 Compare April 1, 2025 06:06
@tridge tridge merged commit b136aa2 into ArduPilot:ArduPilot-4.6 Apr 1, 2025
109 of 111 checks passed
@rmackay9 rmackay9 deleted the ap-460-beta5 branch April 1, 2025 20:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.