0
$\begingroup$

Rosanswers logo

Hi,

I am on Ubuntu 16.04 LTS and ROS Kinetic right now and trying to import a model that I designed in SolidWorks (a simple tree made with sticks, its in a .sldprt file) into my Gazebo simulation. I know that URDF files only support .stl and collada (.dae) files and that I should use .stl files for the collision tag and .dae for the visual tag. I can properly export my model using the SolidWorks2URDF plugin (http://wiki.ros.org/sw_urdf_exporter) and I get a package with an URDF file which includes an .stl file for both visual and collision tags, because the exporter doesn't export any collada (.dae) files.

I tried to use the SimLab Soft Collada Exporter for SolidWorks to export my model into to a collada file but when I tried to use it in the simulation, the only thing that appears is a white cube (???) and I don't know why because if I open the file in FreeCad, I can see my tree with no problems, except the fact that it is colourless and I don't know why... first my model had a wood appearence but then I changed it to a brown color, just to check that the appearance had nothing to do with this, but I still see the white cube as my visual object while my collision object (orange) stays correct:

image description

I have also tried to convert my model file from .sldprt to .stp file (format 214 so that it also has colors but not appearances) and follow the steps in here http://gazebosim.org/tutorials?tut=guided_i2 to convert my file into a collada one but everything remains the same.

Can somebody help me on how to do this? Thanks in advance!

Best regards, José Brito


Originally posted by znbrito on ROS Answers with karma: 95 on 2018-04-10

Post score: 0

$\endgroup$

1 Answer 1

0
$\begingroup$

Rosanswers logo

Hi,

solved the problem. When a white cube appears on Gazebo that means that the path to the visual mesh in not well specified. I guess I wasn't expecting this error because I was using the package finder, but when I used the full path the tree appear and everything seemed to be fine. After that I changed to the package finder once again and I got no errors so it seems that the first time I inserted the path I must have misspelled something...

Anyway, just in case you guys want to know, when you are working with SolidWorks to build your own models:

(I also discovered that it is not possible to export appearances to a STEP (.stp file), which was something that I also tried when trying to work my problem around).

Combining this 2 SolidWorks plugins allowed me to fully export a SolidWorks model, which is something that I think that is not well documented on the Internet so I hope this helps you all as it helped me.

Cheers! José Brito


Originally posted by znbrito with karma: 95 on 2018-04-10

This answer was ACCEPTED on the original site

Post score: 2

$\endgroup$

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.