Skip to content

Conversation

@julianoes
Copy link
Collaborator

@julianoes julianoes commented Oct 30, 2025

This updates mavlink including a patch containing ArduPilot/pymavlink#1143.

Then, we add PARAM_ERROR for better param error handling as added in mavlink/mavlink#2344.

Depends on mavlink/MAVSDK-Proto#384.

FYI @hamishwillee

JonasVautherin
JonasVautherin previously approved these changes Oct 31, 2025
@julianoes
Copy link
Collaborator Author

Pending: mavlink/mavlink#2373
Once that's in I can remove the patch and this will pass Windows again.

Currently the PARAM_EXT param_value field is broken due to a recent
pymavlink change. Until that's fixed, we have to carry another patch.
This adds support for the new PARAM_ERROR message which makes the param
protocol more robust in case things go wrong. Instead of waiting for a
timeout, we actually get an error.
@sonarqubecloud
Copy link

sonarqubecloud bot commented Nov 4, 2025

@julianoes julianoes merged commit 5379eed into main Nov 4, 2025
56 checks passed
@julianoes julianoes deleted the pr-param-error branch November 4, 2025 09:16
@hamishwillee
Copy link
Collaborator

@julianoes Thanks very much!

FYI I am tidying up the param xml in mavlink/mavlink#2365 - in particular to make it clear when index/id are returned in the PARAM_VALUE and PARAM_ERROR (I'll get you to look when fully agree this with Peter).

Anyhow, the point is that there will be another error for "no parameters at all" returned by the request for all parameters.
Note that I haven't got to the point of thinking about actually sending that though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants