Revision history [back]

I see two potential problems. First, did you generate your stl files from solidworks? Solidworks seems to prepend their binary STL files with '<solid' ,="" which="" messes="" up="" assimp.="" if="" you="" manually="" edit="" the="" files="" and="" change="" that="" to="" any="" other="" five="" letter="" word,="" such="" as="" robot,="" then="" assimp="" will="" load="" the="" mesh="" file.="" <="" p="">

For the second error, OMPL is not able to configure the search space. I've seen this happen when your robot consists entirely of continuous joints with no joint limits. We can't currently plan for such robots - if you change at least one joint in your URDF to a regular Revolute joint and set joint limits and re-run the wizard I think things will work.

I see two potential problems. First, did you generate your stl files from solidworks? Solidworks seems to prepend their binary STL files with '<solid' ,="" which="" messes="" up="" assimp.="" if="" you="" manually="" edit="" the="" files="" and="" change="" that="" to="" any="" other="" five="" letter="" word,="" such="" as="" robot,="" then="" assimp="" will="" load="" the="" mesh="" file.="" <="" p=""> 'solid' , which messes up assimp. If you manually edit the files and change that to any other five letter word, such as robot, then Assimp will load the mesh file.

For the second error, OMPL is not able to configure the search space. I've seen this happen when your robot consists entirely of continuous joints with no joint limits. We can't currently plan for such robots - if you change at least one joint in your URDF to a regular Revolute joint and set joint limits and re-run the wizard I think things will work.