Skip to content
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

Create and use MAV_ parameter namespace #29568

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

Conversation

peterbarker
Copy link
Contributor

I've only moved one parameter, but SYSID_MYGCS is also an obvious one to move.

Entry is required in each vehicle as we subclass the GCS object for each vehicle (eg. GCS_Plane)

Past this we should sprout MAVn_OPTIONS so we can move things from SERIALn_OPTIONS (eg. "private").

... and also have MAV1_SR_EXTRA etc etc.

I have tested each vehicle's parameter upgrade individually. The automatic testing script fails because the system ID changes!

@tridge
Copy link
Contributor

tridge commented Mar 19, 2025

it would be nice for the MAVn subgroups to be SUBGROUPPTR so they appear when allocated

@peterbarker
Copy link
Contributor Author

MAV1_PORT==21 meaning a network port that's doing mavlink...

@peterbarker peterbarker added the WikiNeeded needs wiki update label Mar 19, 2025
@amilcarlucas
Copy link
Contributor

Good idea!

@peterbarker peterbarker force-pushed the pr/gcs-params branch 3 times, most recently from 4d66ce4 to 6539666 Compare March 19, 2025 13:16
Move serveral parameters in

Rover: create and use MAV_ parameter namespace

Move serveral parameters in
Move serveral parameters in

Rover: create and use MAV_ parameter namespace

Move serveral parameters in
Move serveral parameters in

Rover: create and use MAV_ parameter namespace

Move serveral parameters in
.... which are sorted.

Also reformat this so a simple change doesn't affect more than it should!
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants