Skip to content

param_server: allow to change parameter internally#317

Closed
dayjaby wants to merge 1 commit intomavlink:mainfrom
dayjaby:parameter_server_local_change
Closed

param_server: allow to change parameter internally#317
dayjaby wants to merge 1 commit intomavlink:mainfrom
dayjaby:parameter_server_local_change

Conversation

@dayjaby
Copy link
Copy Markdown
Contributor

@dayjaby dayjaby commented Jun 11, 2023

Allow a param_server to change a parameter that it is providing.

@dayjaby dayjaby force-pushed the parameter_server_local_change branch from 279889c to 8a62fff Compare June 11, 2023 21:46
Copy link
Copy Markdown
Collaborator

@JonasVautherin JonasVautherin left a comment

Choose a reason for hiding this comment

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

Can't we (couldn't we?) do that by calling ProvideParam again with the same name but a different value?

@julianoes
Copy link
Copy Markdown
Collaborator

I think this makes sense. The tricky thing is that you're supposed to "provide" all params on init, before any mavlink traffic happens, and the number of params can't change later.

@JonasVautherin
Copy link
Copy Markdown
Collaborator

The tricky thing is that you're supposed to "provide" all params on init, before any mavlink traffic happens

Oh so that can't work with the language bindings, right?

@dayjaby
Copy link
Copy Markdown
Contributor Author

dayjaby commented Jun 12, 2023

Language bindings should be fine. So a python mavsdk app for example can represent an entire mavlink component, using the param_server plugin to provide all the parameters. If something happens within the component, the same plugin should be able to be used to "change" one of these parameters.

@julianoes
Copy link
Copy Markdown
Collaborator

Implemented in #388 instead.

@julianoes julianoes closed this Dec 22, 2025
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.

3 participants