mastermodel strategy
mastermodel strategy
(OP)
It's nice having one database (the master-model) control features in parts that rely on other parts. In ProE-land, I make a part, usually just curves and surfaces, and reference just that part for everything else (to avoid circular reference, etc...). In ProE-land, one way is make "publish geometry" features in the master-model that references all the relavant things in the mastermodel that a certain part needs.
Here's how I'm trying to do this in Soldworks:
It's all based in modifying the part to get the mastermodel features in assembly, but referencing the mastermodel.
To get a surface body over, I do a surface offset of 0. Then I solidfy, thicken, or cut with it in the part.
For the rest, like planes, sketches, and curves, I just directly use the mastermodel feature while I'm editing the part.
How are ya'll referencing a master part?
Here's how I'm trying to do this in Soldworks:
It's all based in modifying the part to get the mastermodel features in assembly, but referencing the mastermodel.
To get a surface body over, I do a surface offset of 0. Then I solidfy, thicken, or cut with it in the part.
For the rest, like planes, sketches, and curves, I just directly use the mastermodel feature while I'm editing the part.
How are ya'll referencing a master part?






RE: mastermodel strategy
I do not use the Top Down approach because we use the same part in lots of assembies and with multiple users at different levels it just works out better to do Bottom Up design.
Best Regards,
Heckler
Sr. Mechanical Engineer
SW2005 SP 4.0 & Pro/E 2001
Dell Precision 370
P4 3.6 GHz, 1GB RAM
XP Pro SP2.0
NIVIDA Quadro FX 1400
o
_`\(,_
(_)/ (_)
Just because I'm paranoid doesn't mean that they aren't out to get me.
- Woody Allen
RE: mastermodel strategy
htt
htt
http
Helpful SW websites every user should be aware of FAQ559-520
How to get answers to your SW questions FAQ559-1091
RE: mastermodel strategy
Best Regards,
Heckler
Sr. Mechanical Engineer
SW2005 SP 4.0 & Pro/E 2001
Dell Precision 370
P4 3.6 GHz, 1GB RAM
XP Pro SP2.0
NIVIDA Quadro FX 1400
o
_`\(,_
(_)/ (_)
Just because I'm paranoid doesn't mean that they aren't out to get me.
- Woody Allen
RE: mastermodel strategy
I just finished an ID project that had common "A" surface definitions shared across many parts. I tried sharing those definitions using library features, but that unravelled and I had to disconnect all the references.
If you want a master part at the top level of an assembly, you can use envelope components to carry the master geometry. Not ompletely analogous to skeleton parts in Pro/E, but it can work in many cases.
http://www.EsoxRepublic.com-SolidWorks API VB programming help
RE: mastermodel strategy
How are you getting surfaces and surface bodies from the skeleton to the sub-parts? Since I'm doing fairly organic surfacing, I'd rather define all the surfaces and part-lines in the skeleton, and then import them into the sub-parts. That way all the contruction features for the final surfaces are done just once and I insure the the surfaces going to multiple parts are corresponding.
This is where I've been using "offset surface" features to get surface bodies from the skeleton part to the sub-parts. But I'll look around for the "envelope components" function you talked about.
RE: mastermodel strategy
FAQ559-1067
Regards,
Scott Baugh, CSWP
www.scottjbaugh.com
FAQ731-376