-
Notifications
You must be signed in to change notification settings - Fork 13.7k
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
gz: use server config file for loading world plugins #24441
Conversation
@hamishwillee let's chat sometime about adding docs for gz plugins |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
I added magnetometer callback to GZBridge. Tested functional. |
just for developing the plugin. will change to new plugin infrastructure once PX4/PX4-Autopilot#24441 merges.
atm it does nothing, but it builds and runs. - temporarily loaded by specifying in world sdf file. Tools/simulation/gz submodule update does that. Waiting for #24441 - Build works but is very ugly. TODOs: - separate completely from OpticalFlowSystem - Add dependency on MovingPlatformController in a way that it works when setting the world with env var, not only when setting it with build target gz_$MODELNAME_$WORLDNAME (just always?)
This pull request has been mentioned on Discussion Forum for PX4, Pixhawk, QGroundControl, MAVSDK, MAVLink. There might be relevant details there: |
This pull request has been mentioned on Discussion Forum for PX4, Pixhawk, QGroundControl, MAVSDK, MAVLink. There might be relevant details there: |
atm it does nothing, but it builds and runs. - temporarily loaded by specifying in world sdf file. Tools/simulation/gz submodule update does that. Waiting for #24441 - Build works but is very ugly. TODOs: - separate completely from OpticalFlowSystem - Add dependency on MovingPlatformController in a way that it works when setting the world with env var, not only when setting it with build target gz_$MODELNAME_$WORLDNAME (just always?)
just for developing the plugin. will change to new plugin infrastructure once PX4/PX4-Autopilot#24441 merges.
See gazebo docs
https://gazebosim.org/api/sim/8/server_config.html
TLDR; the plugins can be loaded via a config file. This ensures we have all the plugins needed for PX4 without hardcoding them into the world files.