-
Notifications
You must be signed in to change notification settings - Fork 18.2k
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
Plane/Copter/Rover/Tracker: 4.6.0-beta4 release #29289
Plane/Copter/Rover/Tracker: 4.6.0-beta4 release #29289
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
6b4e2ff
to
55195fd
Compare
addressed HenryW's requests, thanks!
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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks Randy!
55195fd
to
bb8d902
Compare
I've rebased and updated this PR after these backport were created and merged thanks to the kind help of @bugobliterator, @tpwrules and @peterbarker.
If I could just get one more approval, perhaps from @peterbarker then I'll merge and we can do the beta release |
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
bb8d902
to
69b4900
Compare
I've force pushed this one last time in order to include the CADDX driver fix #29309 I plan to merge after this PR passes CI |
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!