search

ros / solidworks_urdf_exporter

SolidWorks to URDF Exporter
http://wiki.ros.org/sw_urdf_exporter
MIT License
392 stars 104 forks source link

Meshes are created in the global coordinate system, when Origin-CS is located in subassembly #116

Open twhuhn opened 3 years ago

twhuhn commented 3 years ago

Might be related to #87 and #103

I created a model of a mostly serial robot structured the following way:

main.sldasm
|- link1.sldasm
|  |- part11.sldprt
|  L part12.sldprt
|- link2.sldasm
|  |- part21.sldprt
|  L part22.sldprt
...

The origins and joint axes are located in the linkx.sldasm files.

In earlier™ versions of the tool and Solidworks, this made no problem. To the contrary, it allowed for the model to be structured in a logical way, and the coordinate systems only had to be defined in a canonical manner when finishing the subassemblies. We always created this reference coordinate system in the origin of the subassembly. The export then produced the STL files with the origin in the same origin as the subassembly, and everything worked out fine.

With the current version however, this does not work anymore. All STLs are now created with the origin set in the origin of the main assembly. If all files are loaded into blender, the robot is built together as it is in main.sldasm, opposite to all lying on top of each other with their origin in (0|0|0) (how it should be).

brawner commented 3 years ago

What version of SolidWorks are you using?

hustchenli commented 2 years ago

Hello, got any solution? I have the same problem about coordinate systems. The origins of all STLs are set to the main assembly , no matter which coordinate system is chosen. Here is the version: https://github.com/ros/solidworks_urdf_exporter/releases/tag/1.6.1

bkinman commented 2 years ago

I'm having this issue as well. Is anybody actually maintaining this package anymore?

brawner commented 1 year ago

This has been a known issue with SolidWorks in the past and is not related to a bug with the exporter. Generally, SolidWorks versions from 2018 are most affected.