-
Notifications
You must be signed in to change notification settings - Fork 13.3k
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
PX4 ROS2 Parameter Bridge #23156
Labels
Comments
I think we need a new module ParameterManager which implements the parameter microservice via uORB. This would then be the common interface in PX4 for mavlink, uavcan, and dds. The parameter system really should be unified across all of these different protocols and subsystems. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe problem solved by the proposed feature
With the introduction of the px4-ros2-interface-lib and the long term goal of tight integration between PX4 firmware and ROS2 linux, we need a way to unify the parameter systems of PX4 and ROS2.
Describe your preferred solution
uORB version of the mavlink parameter microservice?
Describe possible alternatives
🤷
Additional context
One example is ROS2 mode which overrides Precision Land, you would want to reuse the existing PLD_ parameters. Users at the GCS shouldn't need to know or care where modes live.
The text was updated successfully, but these errors were encountered: