-
Notifications
You must be signed in to change notification settings - Fork 138
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
[ros2] Different interpretation of xacro/urdf files between igniton-gazebo3 and igniton-gazebo4/5 #147
Comments
I suspect this may be related to changes from libSDFormat 9 (Citadel) to libSDFormat 10 (Dome), because that's where the URDF gets parsed into SDF. In fact, a quicker way of reproducing this can be achieved with the Citadel has the sensor pose: ign sdf --force-version 9.5.0 -p /tmp/urdf
Dome doesn't: ign sdf --force-version 10.3.0 -p /tmp/urdf
Looking through SDFormat's changelog, nothing stood out as being the culprit though. |
I believe this is connected to fixed-joint reduction with the libsdformat parser_urdf.cc file |
I think this was fixed by gazebosim/sdformat#525 |
Hopefully. It looks like it is related. Will test once merged or released in sdf11 |
Confirmed fixed in dome/sdf10, still need a merge in edifice/sdf11 |
The SDFormat fix has been forward-ported to Edifice. I'm closing this. ROS users will get the updated versions as the fix is released and ported to packages.ros.org. |
Environment
Description
Don't know if I should report here or there: https://github.com/ignitionrobotics/ign-gazebo
I have a ROS / Ignition robot simulation working well with
citadel
, I did few tests with the newly releasededifice
and run into an issue on how my xacro/files are interpreted by gazebo when spawning withros_ign_gazebo create
.More specifically on how a lidar sensor is positioned by gazebo.
When interpreting the following xacro/urdf file:
igniton-gazebo3 places properly the lidar sensor at the origin of the link "link", whereas igniton-gazebo4 and igniton-gazebo5 place it at the origin of the link "base_footprint"
And indeed, if I use the gazebo GUI feature "Save world as..." I get a different sdf file between igniton-gazebo3 and igniton-gazebo4/5. With igniton-gazebo3, the sensor has the attribute
<pose>0 0 3 0 -0 0</pose>
, whereas with igniton-gazebo4/5, the sensor has no pose attribute. Full sdf files below:igniton-gazebo3 :
and with igniton-gazebo5 :
The text was updated successfully, but these errors were encountered: