Skip to content

Empty textures folder problem with URDF to PROTO conversion #174

@ozangungor12

Description

@ozangungor12

Hello,
I created a xacro file which combines UR5e + Robotiq 2f85 gripper and automatically generated the URDF from that.
I can display and move the robot and the gripper on RVIZ so the URDF file is okay.
When I'm trying to convert the model to a PROTO file to be able to use in Webots, I get the output ur5e_with_2f85.proto but the auto-generated textures folder is empty.
In my URDF file I am using ur5e and 2f85 descriptions from other ros packages in my workspace so my initial guess is that it could be a problem with relative paths. But the terminal output correctly displays the absoluth paths of the dae files that are being imported.

There are entries in the URDF such as:

<geometry>
   <mesh filename="package://ur_description/meshes/ur5e/visual/shoulder.dae"/>
 </geometry>

I do the conversion with:
python3 -m urdf2webots.importer --input=ur5e_with_2f85.urdf

And the output is:

Robot name: ur5e_with_2f85
Parsing Mesh: home/og/catkin_ws/src/universal_robot/ur_description/meshes/ur5e/visual/base.dae
Parsing Mesh: /home/og/syn/adapt/adapt_ros/src/universal_robot/ur_description/meshes/ur5e/visual/shoulder.dae
Parsing Mesh: /home/og/syn/adapt/adapt_ros/src/universal_robot/ur_description/meshes/ur5e/visual/upperarm.dae
Parsing Mesh: /home/og/syn/adapt/adapt_ros/src/universal_robot/ur_description/meshes/ur5e/visual/forearm.dae
Parsing Mesh: /home/og/syn/adapt/adapt_ros/src/universal_robot/ur_description/meshes/ur5e/visual/wrist1.dae
Parsing Mesh: /home/og/syn/adapt/adapt_ros/src/universal_robot/ur_description/meshes/ur5e/visual/wrist2.dae
Parsing Mesh: /home/og/syn/adapt/adapt_ros/src/universal_robot/ur_description/meshes/ur5e/visual/wrist3.dae
Parsing Mesh: /home/og/syn/adapt/adapt_ros/src/robotiq/robotiq_2f_85_gripper_visualization/meshes/visual/robotiq_arg2f_85_outer_knuckle.dae
Parsing Mesh: /home/og/syn/adapt/adapt_ros/src/robotiq/robotiq_2f_85_gripper_visualization/meshes/collision/robotiq_arg2f_85_outer_knuckle.dae
Parsing Mesh: /home/og/syn/adapt/adapt_ros/src/robotiq/robotiq_2f_85_gripper_visualization/meshes/visual/robotiq_arg2f_85_outer_finger.dae
Parsing Mesh: /home/og/syn/adapt/adapt_ros/src/robotiq/robotiq_2f_85_gripper_visualization/meshes/collision/robotiq_arg2f_85_outer_finger.dae
Parsing Mesh: /home/og/syn/adapt/adapt_ros/src/robotiq/robotiq_2f_85_gripper_visualization/meshes/visual/robotiq_arg2f_85_inner_finger.dae
Parsing Mesh: /home/og/syn/adapt/adapt_ros/src/robotiq/robotiq_2f_85_gripper_visualization/meshes/collision/robotiq_arg2f_85_inner_finger.dae
Parsing Mesh: /home/og/syn/adapt/adapt_ros/src/robotiq/robotiq_2f_85_gripper_visualization/meshes/visual/robotiq_arg2f_85_inner_knuckle.dae
Parsing Mesh: /home/og/syn/adapt/adapt_ros/src/robotiq/robotiq_2f_85_gripper_visualization/meshes/collision/robotiq_arg2f_85_inner_knuckle.dae
Parsing Mesh: /home/og/syn/adapt/adapt_ros/src/robotiq/robotiq_2f_85_gripper_visualization/meshes/visual/robotiq_arg2f_85_outer_knuckle.dae
Parsing Mesh: /home/og/syn/adapt/adapt_ros/src/robotiq/robotiq_2f_85_gripper_visualization/meshes/collision/robotiq_arg2f_85_outer_knuckle.dae
Parsing Mesh: /home/og/syn/adapt/adapt_ros/src/robotiq/robotiq_2f_85_gripper_visualization/meshes/visual/robotiq_arg2f_85_outer_finger.dae
Parsing Mesh: /home/og/syn/adapt/adapt_ros/src/robotiq/robotiq_2f_85_gripper_visualization/meshes/collision/robotiq_arg2f_85_outer_finger.dae
Parsing Mesh: /home/og/syn/adapt/adapt_ros/src/robotiq/robotiq_2f_85_gripper_visualization/meshes/visual/robotiq_arg2f_85_inner_finger.dae
Parsing Mesh: /home/og/syn/adapt/adapt_ros/src/robotiq/robotiq_2f_85_gripper_visualization/meshes/collision/robotiq_arg2f_85_inner_finger.dae
Parsing Mesh: /home/og/syn/adapt/adapt_ros/src/robotiq/robotiq_2f_85_gripper_visualization/meshes/visual/robotiq_arg2f_85_inner_knuckle.dae
Parsing Mesh: /home/og/syn/adapt/adapt_ros/src/robotiq/robotiq_2f_85_gripper_visualization/meshes/collision/robotiq_arg2f_85_inner_knuckle.dae
Root link: world
There are 19 links, 18 joints and 0 sensors

Thank you in advance for any kind of help!

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions