Skip to content

Conversation

@julianoes
Copy link
Contributor

Backport of #12627.

This adds the logic we have in place for other camera requets already.
We try to request it both using the old specific command as well as
using the newer general MAV_CMD_REQUEST_MESSAGE command.
We have to try both commands, the deprecated specific one and the
new generic one. We do this by calling the function twice.

Also, we need to wait just a little bit in the "Basic" case because
otherwise we seem to conflict with another MAV_CMD_REQUEST_MESSAGE and
trigger a duplicate command request in which case the command is never
sent out.

This will need proper fixing in the underlying MAV_CMD_REQUEST_MESSAGE
logic but for now this improves discovery of a camera, at least in my
case.
We need to call factChanged initially, otherwise the ranges and
exclusions are not taken into account when first displaying the camera
settings UI. (They are taken into account on subsequent updates.)
@julianoes julianoes merged commit 5b8008e into Stable_V4.4 May 4, 2025
5 of 7 checks passed
@julianoes julianoes deleted the pr-backport-camera-fixes branch May 4, 2025 23:59
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.

2 participants