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

[Bug]: Nested drone SDFs in Gazebo simulation #21767

Open
hmer101 opened this issue Jun 27, 2023 · 0 comments
Open

[Bug]: Nested drone SDFs in Gazebo simulation #21767

hmer101 opened this issue Jun 27, 2023 · 0 comments

Comments

@hmer101
Copy link

hmer101 commented Jun 27, 2023

Describe the bug

Cannot connect to drone models when they are nested in higher-level SDF models in a Gazebo simulation. This is caused by the drone names in GZBridge.cpp not expecting to have a higher-level model name prepended. This specifically causes problems with the GZMixingInterfaceESC and GZMixingInterfaceServo classes and in the GZBridge::poseInfoCallback name check.

A full description of the error and the debugging process can be found on the forums here.

To Reproduce

  1. Set up an x500 (or other) drone in a nested SDF model in the simulation>gz>worlds folder.
  2. Following these instructions, use the PX4_GZ_MODEL_NAME argument to connect to an existing x500 drone model in Gazebo (sitl simulation).
  3. Attempt to takeoff in sitl using 'commander takeoff'.
  4. See issue - arming fails.

Expected behavior

Drone takes off regardless of how many SDF models it is nested within.

Screenshot / Media

See here for screenshots.

Flight Log

https://logs.px4.io/plot_app?log=54a64667-8ec9-4d74-b56f-45f5c3811894

Software Version

Version v1.14.0beta2, main branch commit: a6d2c2cf5e21ecdad8d737c31de81fab128898c5.

Flight controller

Gazebo sitl simulation

Vehicle type

Multicopter

How are the different components wired up (including port information)

No response

Additional context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant