Skip to content

bugfix; ArduPilot SRx_ parameters note #532

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.

Sign up for GitHub

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

Open
drtrigon wants to merge 2 commits into
base: master
Choose a base branch
from
Open

bugfix; ArduPilot SRx_ parameters note #532

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7b499f9
bugfix; ArduPilot `SRx_` parameters note
drtrigon Apr 12, 2026
4ebeeaa
follow-up; move note from general section to ArduPilot
drtrigon Apr 13, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions docs/software/mavlink.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -82,6 +82,9 @@ The minimum versions to use this feature are:
1. Configure all `SRx_` parameters to be `1`, except for `SRx_ADSB`, `SRx_PARAMS`, `SRx_RAW_CTRL` that should stay `0` (otherwise yaapu will see a few sensors only and GCS might not be able to connect)
1. Save parameters and reboot the flight controller

!!! note "NOTE: ArduPilot parameters"
The `x` in the ArduPilot `SRx_` parameters does **not** need to be the same `x` as the in the `SERIALx` parameters. Often they are the same but that must not always be true. In case of doubt you have to figure this out by trial and error or just set all of them to the same value.

=== "PX4"
For the below steps, when a UART connection is mentioned, it will be written as `SER_TELx`. Replace `x` with the UART number you are using.

Expand Down
Loading