All,
I am an experienced pro|e user with some experience in solidworks. I can model parts and surfaces just fine, but I've got a solidworks project coming up that is going to end up being a large assembly. I've been looking through some training materials and there seems to be a variety of ways to structure an assembly. My questions is: for large assemblies, what is the most robust approach to structuring the database?
For those of you that are familiar with pro|e, I have had great success in using the skeleton functionality. For those that aren't familiar, a skeleton based assy works like this:
create an assembly an insert the skeleton part (a special type of part)
v
the skeleton part has all the surfaces that make up the primary shape of the model
v
the last feautres in the skeleton model tree are "publish geometry" features that act as folders in which you can select what geometry/datums/etc. you want to "publish"
v
in the assembly you create regular parts
v
the first feature in those parts is a "copy geometry" that points to one of the "publish geometry" features in the skeleton
v
the part geometry is created around the copy geometry feature
I understand that this is a loaded question, but any advice would be greatly appreciated.
I am an experienced pro|e user with some experience in solidworks. I can model parts and surfaces just fine, but I've got a solidworks project coming up that is going to end up being a large assembly. I've been looking through some training materials and there seems to be a variety of ways to structure an assembly. My questions is: for large assemblies, what is the most robust approach to structuring the database?
For those of you that are familiar with pro|e, I have had great success in using the skeleton functionality. For those that aren't familiar, a skeleton based assy works like this:
create an assembly an insert the skeleton part (a special type of part)
v
the skeleton part has all the surfaces that make up the primary shape of the model
v
the last feautres in the skeleton model tree are "publish geometry" features that act as folders in which you can select what geometry/datums/etc. you want to "publish"
v
in the assembly you create regular parts
v
the first feature in those parts is a "copy geometry" that points to one of the "publish geometry" features in the skeleton
v
the part geometry is created around the copy geometry feature
I understand that this is a loaded question, but any advice would be greatly appreciated.