Plane/Copter/Rover/Tracker: 4.6.0-beta4 release #29289
Open
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
AP_ADSB: uAvionix Transponder Status V3 + Current version of ping200X sends the v1 status message periodically and the v3 status message in response to the transponder control message, so ardupilot needs to handle both gracefully; version 1 and version 3 are very different in structure and naively assuming one version over another will cause errors. AP_ADSB: Process additional xpdr status v3 fields AP_ADSB: Send GCS xpdr status at least every 10s AP_ADSB: Send ping200X estimated HPL + When AP sends the ping200X the GPS data GDL90 message, it needs to provide a valid HPL for the ping200X to report a valid NIC. AP_ADSB: Don't send unsolicited transponder status AP_ADSB: Better initialization of xpdr id/config AP_ADSB: Better initialization of frontend status AP_ADSB: Suggestions from review
allows for servo drivers to be written in lua
add UART6 and VBUS to BETAFPV F405 add alt config to BETAFPV-F405 to support RELAY2 instead of UART6_TX as per betaflight enable SBUS input on BETAFPV-F405 on UART5_RX enable IMU temperature calibration for BETAFPV-F405 correct current scale on BETAFPV-F405. BETAFPV-F405 SPL06 Baro correct baro SPI read rate on BETAFPV-F405 use SPL06 with background updates on BETAFPV-F405
Signed-off-by: Ryan Friedman <[email protected]>
this might have worked if parity1 and parity2 were static values - but theyr're not. I'm guessing the code evolved
while Copter is the only user at the moment, will be useful on Rover shortly
while Copter is the only user at the moment, will be useful on Rover shortly
while Copter is the only user at the moment, will be useful on Rover shortly
The command should also take negative values Redo scaling to comply with mavlink documentation.
don't cache connection result and return appropriate error if connection fails. don't wait 1s to send first serial passthrough message retry failed cmd_DeviceInitFlash as per betaflight ensure the bootinfo structure is large enough
only configure DMA on groups that are actually being used for soft serial
rmackay9
requested review from
lthall,
tpwrules,
tridge,
andyp1per,
bugobliterator and
Hwurzburg
Hwurzburg
previously requested changes
Feb 13, 2025
tpwrules
approved these changes
Feb 13, 2025
rmackay9
force-pushed
the
ardupilot-460-beta4
branch
from
6b4e2ff to
55195fd
Compare
rmackay9
dismissed
Hwurzburg’s stale review
addressed HenryW's requests, thanks!
Huibean
approved these changes
Feb 14, 2025
|
I've created a backport PR for the ibus naming fix (#29294) and removed the conflicting backport |
|
I've created a backport PR for the CaddX support and added it to the project, removing the old PR which was against master. |
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.
This is the 4.6.0-beta4 release for Copter, Rover, Tracker and Plane.
The full list of PRs can be seen in the "4.6.0-beta4" column of this project.
There was just one PR that I was unable to backport due to a merge conflict but if we're keen to get this into 4.6 maybe @bugobliterator could produce a backport PR?
Any and all feedback on the release note wording or anything else is greatly appreciated!