Export from Rhino import to Solidworks

I’ve searched in the forum, and it seems STEP is popular for exporting from Rhino to Solidworks.

Is this advised method?

I tried with IGES default(The file I sent is very simple and small consisting of several closed polysurfaces) but it didn’t seem to open well in the solidworks
(I don’t have it so not sure what the problem is). They mention the data is not watertight(I think what they meant…).

Should I put things in different layers? Any good settings to check out?

That’s what I have had the best results with, yes.
Better than parasolid .x_t or other formats.

Personally I have better results with Iges. I find solidworks knits iges files together very nicely. If I’m having problems closing polysurfaces sometimes I import into solid works where they knit closed and import back into rhino. My formats of choice in order: Igs, stp, xt, sat, 3dm.

I should mention that when exporting igs I only do this with objects that are not contacting each other. If it is a group of objects that some are contacting each other I either export them individually or I just use stp.

Thanks!
Does layers get exported as well? Any need to send one part at a time?

Thanks for the tip, maybe that may be the cause of the problem.
Any way to automate saving parts separately?..

I recommend avoiding IGES. If your model has 2,000 separate surface-pieces, do you really want to pick and join them manually? Hell, no! Just think how messy your file would be if you selected every object and then hit EXPLODE. That’s an IGES.

STEP will maintain each and every polysurface as a single entity, just like it was created. If it was joined in Rhino, it stays joined as a STEP.

@schultzeworks
I see, so I guess IGES utilizes surfaces and not interpreting any closed polysurface as solids. I’ll skip learning IGES stuff. saves time =)

When exporting with STEP, should each parts be done separately?
If there’s two parts with surfaces touching each other will that complicate the importing in solidworks side?

Also, is there way to export from rhino so that each closed polysurface becomes separate “parts” in solidworks?
(I don’t have solidworks myself, so don’t know exactly how it works, but kinda guessing from what I learned so far…)

I found that exporting to Rhino V4 can be one solution, but same question of making into separate “parts”.

No need. I do the entire file at once. Each separate polysurface OR solid will stay as a separate piece and not “get joined.” I recommend you do a quick test and see what happens.

  • Select a bunch of geometry.
  • Export them as a STEP file.
  • Now, bring it all back in with the IMPORT command.
  • You can’t tell the original from the import; it’s all beautiful NURBS and you can even work on it. Sweet.

Thanks for the quick reply. Will check it out.

Interesting. My iges files automatically join in solidworks. It even patches any naked edges. It works really really well. I suggest you try it. Also iges files keep the file color, step files the body has the color but not the component so any modifications to the object will not have the same color. Maybe that might be desired for some people but not me.

I do all my designs this way with Solidworks as I find iges imports much cleaner then step into Solidworks.

The exception is with components that are touching. Solidworks 2012 doesn’t keep the name of components from rhino when brought in as an assembly. It doesn’t seem to matter what format I try (stp, igs, sat, xt…)

I think that STEP is the right format to do that.
But if you often need to export from Rhino to SolidWorks, you should try to directly convert your 3dm files in sldprt.
You can do it with this converter. It is not free, but it makes the process easier, and you should have better result than using a neutral format.

1 Like

Thanks!
I don’t have solid works myself but I’ll see if the other side would be interested.

You don’t need to have Solidworks to use this converter.
But yes, it can be installed on the side of your partner if they have more interest in investing in such a tool. The result will be the same.

thanks!