-
Notifications
You must be signed in to change notification settings - Fork 804
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
Support for Gazebo 11 #699
Comments
@McKayCyborg I run gazebo11 with ROS Noetic without any issues, and it is the standard environment where the PX4 SITL tests run in CI Therefore it is suppoeted |
Thanks @Jaeyoung-Lim, Given that I am running into the same issue as posted in: #419, what ended up being the solution? |
@McKayCyborg Could you explain what your issue is? The issue you are referring to is gazebo11 with Ubuntu 18.04 and the errors are usually different |
@Jaeyoung-Lim to begin with, I'm not using the most up-to-date version of PX4 and I am using the mavlink interface plugins and the various sensor plugins in a custom ROS package so if you feel like answering this question is too much of a stretch, I understand if you just want to just close out the issue. Although, I opened the thread because I feel like this issue is has everything to do with the mavlink plugin itself. Some details: What I've done: The error:
My Question: |
@McKayCyborg It was added by this PR: #497 The error you are showing simply means gazebo was unable to find one of the resources, so it is hard to tell what is wrong. If you are using custom code I would recommend you to try running PX4 master with Gazebo11 first to check if everything else is configured properly on your system |
Thankyou @Jaeyoung-Lim, I'll do that and make sure my system is configured properly. |
@Jaeyoung-Lim after cloning the master branch, it appears that the Gazebo rover sim loads without errors (except for being unable to load a bunch of visuals), although it doesn't connect to QGroundControl so I can't verify if the vehicle will actually run a mission. The Gazebo environment loads but the daemon just shows this output:
My QGC version is v4.1.1 |
@McKayCyborg I am not sure what you are saying is accurate
The log you are showing is trying to load the iris model. Probably something else is wrong? |
@Jaeyoung-Lim Sorry for the confusion - I ran it again with the iris model to see if it was something rover-specific and have sent that output to you instead of the rover output |
@McKayCyborg And you don't have connection to QGC on both? Now I am confused - qgc connection should not be related to gazebo versions How are you running the sim? Can you try
|
@McKayCyborg Any updates? |
@Jaeyoung-Lim after a deeper dive yesterday it looked like the gazebo_mavlink_interface plugin was failing inside the Load method during this call:
In the updated plugins, there is a conditional define that reworks this to:
Clearly, my system was not able to locate the boost::any_cast<>() resource. My simulation appears to be working alright now, although the vehicle position seems to drift alot. Thankyou for your guidance |
Hi there,
Currently, I am seeing issues similar to: #419 whereby the mavlink interface plugin fails to load if run it using Gazebo 11.
Are there any plans to update the simulation tools to run on Gazebo 11 in the near future? My issue is that I would like to use the libgazebo_mavlink_interface with ros_control and need to use Noetic (because I am using Ubuntu 20.04), but ROS Noetic only supports Gazebo 11 as far as I can tell.
Any help would be awesome!
Thanks
The text was updated successfully, but these errors were encountered: