You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the Bug
A common use in the ROS world of the urdf file associated with the robot_state_publisher node and the tf_system is to set up all the static_transforms known in advance directly in the urdf file. For instance, it's common to have the base_footprint -> base_link static joint, where base_footprint is a "virtual" link with no Solid attached to it. When spawining, the resulting robot does have neither Physics or BoudingObject properties set, resulting in a robot not in kinematic behavior.
In addition, the base link is converted as a Solid where a Transform would be more appropriate. More generally, an empty link should result in a Transform in webots, a link with only a <visual> tag should result in a Transform + a Shape, and only a link with a <collision> tag should result in a Solid.
Steps to Reproduce
Consider the following urdf file :
Expected behavior
With the urdf provided, the robot should be in kinematic mode. In addition, the base link is converted as a Solid where a Transform would be more appropriate. More generally, an empty link should result in a Transform in webots, a link with only a <visual> tag should result in a Transform + a Shape, and only a link with a <collision> tag should result in a Solid.
Affected Packages
List of affected packages:
webots_ros2_driver
System
Webots Version: R2023a for macOS
ROS Version: Humble
Operating System: Ubuntu jammy in docker, host macOS Monterey 12.2.1, using local_simulation_server.py
The text was updated successfully, but these errors were encountered:
Describe the Bug
A common use in the ROS world of the urdf file associated with the
robot_state_publisher node
and thetf_system
is to set up all thestatic_transforms
known in advance directly in the urdf file. For instance, it's common to have thebase_footprint -> base_link
static joint, wherebase_footprint
is a "virtual" link with no Solid attached to it. When spawining, the resulting robot does have neither Physics or BoudingObject properties set, resulting in a robot not in kinematic behavior.In addition, the base link is converted as a Solid where a Transform would be more appropriate. More generally, an empty link should result in a Transform in webots, a link with only a
<visual>
tag should result in aTransform
+ aShape
, and only a link with a<collision>
tag should result in aSolid
.Steps to Reproduce
Consider the following urdf file :
Expected behavior
With the urdf provided, the robot should be in kinematic mode. In addition, the base link is converted as a Solid where a Transform would be more appropriate. More generally, an empty link should result in a Transform in webots, a link with only a
<visual>
tag should result in aTransform
+ aShape
, and only a link with a<collision>
tag should result in aSolid
.Affected Packages
List of affected packages:
System
The text was updated successfully, but these errors were encountered: