Skip to content

Comments

docs:ManualControlSetpoint uORB topic#26529

Open
hamishwillee wants to merge 4 commits intomainfrom
docs_manual_control_setpoint
Open

docs:ManualControlSetpoint uORB topic#26529
hamishwillee wants to merge 4 commits intomainfrom
docs_manual_control_setpoint

Conversation

@hamishwillee
Copy link
Contributor

Updates ManualControlSetpoint topic to the current docs standard. I did some creative writing. Needs review. See comments inline.

Comment on lines +3 to +5
# This message provides a representation of a manual control input, such as an RC controller or MAVLink controller (Joystick).
# It also defines the manual_control_setpoint topic, which represents the selected input.
# The message includes fields for the roll, pitch, yaw, throttle and flaps, along with auxiliary channels and button states.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this accurate and sufficient? Essentially we want to define the uses, publishers and consumers.

As stated I think this represents each of the inputs, and also it represent a selected input. However it might be a synthesized input. Can you confirm?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What do you mean by synthesized? Since input can be coming from Mavlink MANUAL_CONTROL messages you have no idea how that was produced. Usually joystick, but could be generated by anything.

Comment on lines 25 to 26
# on a common RC mode 1/2/3/4 remote/joystick the stick deflection: -1 is down/left, 1 is up/right
# Note: QGC sends throttle/z in range [0,1000] - [0,1]. The MAVLink input conversion [0,1] to [-1,1] is at the moment kept backwards compatible.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This wouldn't be rendered. Can this move up into the long description?

@hamishwillee hamishwillee requested a review from katzfey February 19, 2026 07:09
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