The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
[ WARN] [1425218598.009362723]: Assimp reports no scene in file:///home/jros/Downloads/staubli-hydro-devel/staubli_rx160_support/meshes/rx160/collision/base_link.stl [ WARN] [1425218598.011305919]: Assimp reports no scene in file:///home/jros/Downloads/staubli-hydro-devel/staubli_rx160_support/meshes/rx160/visual/base_link.stl [ WARN] [1425218598.012032617]: Assimp reports no scene in file:///home/jros/Downloads/staubli-hydro-devel/staubli_rx160_support/meshes/rx160/collision/link_1.stl [ WARN] [1425218598.051607272]: Assimp reports no scene in file:///home/jros/Downloads/staubli-hydro-devel/staubli_rx160_support/meshes/rx160/collision/link_2.stl [ WARN] [1425218598.064820333]: Assimp reports no scene in file:///home/jros/Downloads/staubli-hydro-devel/staubli_rx160_support/meshes/rx160/collision/link_3.stl [ WARN] [1425218598.070363355]: Assimp reports no scene in file:///home/jros/Downloads/staubli-hydro-devel/staubli_rx160_support/meshes/rx160/collision/link_4.stl [ WARN] [1425218598.087058005]: Assimp reports no scene in file:///home/jros/Downloads/staubli-hydro-devel/staubli_rx160_support/meshes/rx160/collision/link_5.stl [ WARN] [1425218598.096185427]: Assimp reports no scene in file:///home/jros/Downloads/staubli-hydro-devel/staubli_rx160_support/meshes/rx160/collision/link_6.stl
The quoted warning should give you enough information: the assimp library (used for loading mesh resources in many parts of ROS), cannot deal with the stl files that you (through the MoveIt Setup Assistant) are requesting it to load.
This is a known issue with assimp and has been asked before. See planning_component_visualizer bug and ros-pkg/ticket/4740 (on the old ROS trac). In short: replace string solid at the start of your stl with something else.
PS: It would seem that these are actually not the meshes that are distributed in the staubli_rx160_support package from ROS-Industrial, as those do not suffer from the issue described. I'm also pretty sure that the meshes shown in your first screenshot are in fact not from an RX160. I would advise you to create your own package, which reflects the actual model you have. This would also avoid potential name-clashes with the 'real' RX160 support pkg.
| | 2 | No.2 Revision |
[ WARN] [1425218598.009362723]: Assimp reports no scene in file:///home/jros/Downloads/staubli-hydro-devel/staubli_rx160_support/meshes/rx160/collision/base_link.stl [ WARN] [1425218598.011305919]: Assimp reports no scene in file:///home/jros/Downloads/staubli-hydro-devel/staubli_rx160_support/meshes/rx160/visual/base_link.stl [ WARN] [1425218598.012032617]: Assimp reports no scene in file:///home/jros/Downloads/staubli-hydro-devel/staubli_rx160_support/meshes/rx160/collision/link_1.stl [ WARN] [1425218598.051607272]: Assimp reports no scene in file:///home/jros/Downloads/staubli-hydro-devel/staubli_rx160_support/meshes/rx160/collision/link_2.stl [ WARN] [1425218598.064820333]: Assimp reports no scene in file:///home/jros/Downloads/staubli-hydro-devel/staubli_rx160_support/meshes/rx160/collision/link_3.stl [ WARN] [1425218598.070363355]: Assimp reports no scene in file:///home/jros/Downloads/staubli-hydro-devel/staubli_rx160_support/meshes/rx160/collision/link_4.stl [ WARN] [1425218598.087058005]: Assimp reports no scene in file:///home/jros/Downloads/staubli-hydro-devel/staubli_rx160_support/meshes/rx160/collision/link_5.stl [ WARN] [1425218598.096185427]: Assimp reports no scene in file:///home/jros/Downloads/staubli-hydro-devel/staubli_rx160_support/meshes/rx160/collision/link_6.stl
The quoted warning should give you enough information: the assimp library (used for loading mesh resources in many parts of ROS), cannot deal with the stl files that you (through the MoveIt Setup Assistant) are requesting it to load.
This is could be a known issue with assimp and has been asked before. . See planning_component_visualizer bug and ros-pkg/ticket/4740 (on the old ROS trac). In short: replace string solid at the start of your stl with something else.
Why this didn't happen on 'Computer 1', I cannot say.
PS: It would seem that these are actually not the meshes that are distributed in the staubli_rx160_support package from ROS-Industrial, as those do not suffer from the issue described. I'm also pretty sure that the meshes shown in your first screenshot are in fact not from an RX160. I would advise you to create your own package, which reflects the actual model you have. This would also avoid potential name-clashes with the 'real' RX160 support pkg.
| | 3 | No.3 Revision |
[ WARN] [1425218598.009362723]: Assimp reports no scene in file:///home/jros/Downloads/staubli-hydro-devel/staubli_rx160_support/meshes/rx160/collision/base_link.stl[ WARN] [1425218598.011305919]: Assimp reports no scene in file:///home/jros/Downloads/staubli-hydro-devel/staubli_rx160_support/meshes/rx160/visual/base_link.stl [ WARN] [1425218598.012032617]: Assimp reports no scene in file:///home/jros/Downloads/staubli-hydro-devel/staubli_rx160_support/meshes/rx160/collision/link_1.stl [ WARN] [1425218598.051607272]: Assimp reports no scene in file:///home/jros/Downloads/staubli-hydro-devel/staubli_rx160_support/meshes/rx160/collision/link_2.stl [ WARN] [1425218598.064820333]: Assimp reports no scene in file:///home/jros/Downloads/staubli-hydro-devel/staubli_rx160_support/meshes/rx160/collision/link_3.stl [ WARN] [1425218598.070363355]: Assimp reports no scene in file:///home/jros/Downloads/staubli-hydro-devel/staubli_rx160_support/meshes/rx160/collision/link_4.stl [ WARN] [1425218598.087058005]: Assimp reports no scene in file:///home/jros/Downloads/staubli-hydro-devel/staubli_rx160_support/meshes/rx160/collision/link_5.stl [ WARN] [1425218598.096185427]: Assimp reports no scene in file:///home/jros/Downloads/staubli-hydro-devel/staubli_rx160_support/meshes/rx160/collision/link_6.stl...
The quoted warning should give you enough information: the assimp library (used for loading mesh resources in many parts of ROS), cannot deal with the stl files that you (through the MoveIt Setup Assistant) are requesting it to load.
This could be a known issue with assimp. See planning_component_visualizer bug and ros-pkg/ticket/4740 (on the old ROS trac). In short: replace string solid at the start of your stl with something else.
Why this didn't happen on 'Computer 1', I cannot say.
PS: It would seem that these are actually not the meshes that are distributed in the staubli_rx160_support package from ROS-Industrial, as those do not suffer from the issue described. I'm also pretty sure that the meshes shown in your first screenshot are in fact not from an RX160. I would advise you to create your own package, which reflects the actual model you have. This would also avoid potential name-clashes with the 'real' RX160 support pkg.
| | 4 | No.4 Revision |
[ WARN] [1425218598.009362723]: Assimp reports no scene in file:///home/jros/Downloads/staubli-hydro-devel/staubli_rx160_support/meshes/rx160/collision/base_link.stl ...
The quoted warning should give you enough information: the assimp library (used for loading mesh resources in many parts of ROS), cannot deal with the stl files that you (through the MoveIt Setup Assistant) are requesting it to load.
This could be a known issue with assimp. See planning_component_visualizer bug and ros-pkg/ticket/4740 (on the old ROS trac). In short: replace string solid at the start of your stl with something else.
Why this didn't happen on 'Computer 1', I cannot say.
PS: It would seem that these are actually not the meshes that are distributed in the staubli_rx160_support package from ROS-Industrial, as those do not suffer from the issue described. I'm also pretty sure that the meshes shown in your first screenshot are in fact not from an RX160. I would advise you to create your own package, which reflects the actual model you have. This would also avoid potential name-clashes with the 'real' RX160 support pkg.
Edit: ok, then this could be an OpenGL / video card driver issue. Make sure you have the correct -- and up-to-date -- drivers for your video card installed.
At the point where the Setup Assistant is loading the urdf, it starts to make proper use of your OpenGL subsystem. If anything is not ok there, it might lead to crashes such as your seeing. This is especially true if you are running Ubuntu/ROS in a VM.
In any case, make sure you have the correct (and up-to-date) drivers installed (check output of glxinfo, look at OpenGL vendor/renderer/version strings).
| | 5 | No.5 Revision |
[ WARN] [1425218598.009362723]: Assimp reports no scene in file:///home/jros/Downloads/staubli-hydro-devel/staubli_rx160_support/meshes/rx160/collision/base_link.stl ...
The quoted warning should give you enough information: the assimp library (used for loading mesh resources in many parts of ROS), cannot deal with the stl files that you (through the MoveIt Setup Assistant) are requesting it to load.
This could be a known issue with assimp. See planning_component_visualizer bug and ros-pkg/ticket/4740 (on the old ROS trac). In short: replace string solid at the start of your stl with something else.
Why this didn't happen on 'Computer 1', I cannot say.
PS: It would seem that these are actually not the meshes that are distributed in the staubli_rx160_support package from ROS-Industrial, as those do not suffer from the issue described. I'm also pretty sure that the meshes shown in your first screenshot are in fact not from an RX160. I would advise you to create your own package, which reflects the actual model you have. This would also avoid potential name-clashes with the 'real' RX160 support pkg.
Edit: Edit:
and this is what I get in the shell using staubli_rx160_support package:
How did you download those files? Could you check the first few bytes of base_link.stl for instance?
Edit2: ok, then this could be an OpenGL / video card driver issue. Make sure you have the correct -- and up-to-date -- drivers for your video card installed.
At the point where the Setup Assistant is loading the urdf, it starts to make proper use of your OpenGL subsystem. If anything is not ok there, it might lead to crashes such as your seeing. This is especially true if you are running Ubuntu/ROS in a VM.
In any case, make sure you have the correct (and up-to-date) drivers installed (check output of glxinfo, look at OpenGL vendor/renderer/version strings).
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
