Continue to Site

Eng-Tips is the largest engineering community on the Internet

Intelligent Work Forums for Engineering Professionals

  • Congratulations MintJulep on being selected by the Eng-Tips community for having the most helpful posts in the forums last week. Way to Go!

importing IGES in SW, how to manage layers

Status
Not open for further replies.

jllprod

New member
Feb 8, 2005
2
Hello all,
I use UG, and one of my colleagues, using Missler TopSolid, is testing SW thiese days. She has some difficulties with layers.
I try to help her finding some answers.
In UG and TS (and also Catia e.g.), designed features are manages by layers, also called levels in TS (e.g. layer 1 to 256 in UG). It allows to make visible or not the items you need at one moment, and to create new elements in the particular layer you need.
IGES file format also uses this way of managing items.
I must admit I am quite confused when we try to import IGES :
How are managed the layers ? when we import IGES files, it seems that the notion of layer is lost. Is there such a way of sorting features in SW ? without any sort by layers, an imported, unparametered IGEs is quite... confused.
Thanks in advance for any help !
Best regards,
Jean-Luc
 
Replies continue below

Recommended for you

SW doens't use laters in Parts and assemblies, only in drawings. I don't know how you work in layers of a solid model? Once you get used to SW interface you won't either. The best thing for you to do is work within SW and understand SW before trying to figure out complicated things like how to manage layers in SW when SW parts and assemblies don't support layers.

Regards,

Scott Baugh, CSWP [pc2]
3DVision Technologies

faq731-376
faq559-716 - SW Fora Users
 
Ok, I understand, but the problem is that people using SW in my job will have to use data from customers, with different origins (Catia, Ug...), which are structured with layers, and export data to programmers who use UG (same problem).
We *can't* change the way the customers manage their data...
Regards,
Jean-Luc
 
I have customers that do this all the time and I have never heard them complain about layers in Catia, etc... So as far as I knew there are were no layers.

With that in mind, the way SW brings in data translated files is as an Imported body. So you don't have to worry about layers anymore. It will come in as a singlebody with no feature geometry. Just a dumb solid.

Regards,

Scott Baugh, CSWP [pc2]
3DVision Technologies

faq731-376
faq559-716 - SW Fora Users
 
Methinks I understand thee.

Here's what I'd recommend. Have only the layers (features) you want to use in SolidWorks shown at the time of exporting from UG (or whatever program). These are the only ones that will show up when imported.

When importing an IGES file, we have no capacity to hide or show layers, so one should "show" exactly what one will expect to use in the imported SolidWorks file from the IGES file. So if you don't want a lot of construction surfaces on the imported model, hide those layers before exporting. Same with curves.


Jeff Mowry
Reality is no respecter of good intentions.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor