Hi sneather, I'm not especially familiar with how Solidworks does its export so I'm not sure if I'll be able to help, but one thing you might ask about is what option they are using for the STEP export type.

There are basically 2 sub-varieties of STEP files, called AP203 and AP214 - the original AP203 format I think can only contain geoemtry and the AP214 variant added support for more stuff like colors and layers I think. So if it's possible that at their export time if they can set the option for using AP214 that may possibly help.

- Michael

Thanks, Michael.

Yeah, we already tried the 203 and 214 options. The 203 didn't even import (no warning dialogue, just nothing) at all in MOI nor Rhino. 214 does import, but in that case, it's back to the original issue that you helped me with yesterday, in having no individual names or layers for all those hundreds of parts. But that's the main issue. I don't know all the other countless variables in Solidworks, which might contribute to the STEP issues.

I'm hoping that a Solidworks and MOI user might happen across this thread.

try Onshape as bridge between all this 3D nurbs program !

I'm not sure an entirely new and different "cloud-based" application is really my ultimate goal, for what is essentially a request for information about optimizing the export of STEP files.

Just with it you have nothing special to do with the SolidWorks format !
And then export in Step format to Moi! What do want more simple ?
That's all! No need to learn ONshape: just 2 clicks! It's just a gobetween! :)

<< Onshape can read native CAD (SolidWorks, Pro/ENGINEER, CATIA, NX, DWG, etc) and neutral CAD formats (IGES, SAT, STEP, ACIS, JT, Parasolid, DXF etc). Furthermore, Onshape’s unique multi-CAD capabilities store the original native CAD data as well as the Onshape translation. It all gets versioned, shared, and is available for download.

Hi Sneather,

I was puzzled by this post since I come from a CAD Engineering background and haven't heard of such an issue with translations, especially these days . I had a quick look at this and had no issue importing a STEP file assembly from Solidworks 2011 with all part names and styles(colours) used in Solidworks, see attached.

The only thing I can think of is if your client is using SW correctly, what I mean is you can model all parts of an assembly in a single model window/session, the industry standard for SW is to model each piece as an individual part file (*.SLDPRT) then you create an assembly file (*.SLDASM) and bring in the individual part files to create the assembly.

The only way I can check is I'd need the original SW file to see what's going on, if you like you can PM me and we can organise it.





Please note the object names are different it's just that they begin with the same 3 words, I think Michael was looking into expanding long object names on mouse over, isn't that right Michael ;)

*Model from GrabCad*

Cheers
~Danny~

I gave it a whirl since I use SW2015 Pro and MoI. I had no issues exporting from SW in STEP 203 format and having the part names travel along. I see the same kind of results Danny shows. As for SW STEP Export options, there are not a lot of them. The difference between 204 and 204 is that 204 loads styles, 203 does not.

If you want to post one of the step files they have sent you I can check it out.

DannyT,

Thank you for the help!
I'll consult with the CAD designer to see whether they are working as you outlined.

Don,

Thank you for your offer, and for your prior post as well!
I'll have to ask the client whether they will be okay with me posting any of their work. But I'll let you know.

Cheers!

If you prefer, you can always email it to me and I will keep it confidential. I work with confidential client files all day every day so know the importance of that.

dcheke@sasktel.net