On Jan 24, 4:30 pm, graminator <graha...@[EMAIL PROTECTED]
> wrote:
> When you have an assembly and you need to keep a relation****p between
> parts (say for example you have a molded enclosure with screw bosses)
> how do you keep your parts parametric? Do you:
>
> 1. Use Copy Geometry from a master part in your assembly;
> 2. Use External Copy Geom and publish from a part that is not in your
> assembly;
> 3. Use copy and paste from a master part in your assembly;
> 4. Use >Edit >Component Operations >Merge and merge an entire master
> part into your child part.
>
> Why do you prefer your particular method?
fwiw...
For basic geometry that is to be shared globally across many
components, we'll use skeletons contained in a top level assembly.
Geometry such as point, plane, axis, and maybe some general surface
stuff, like envelopes surfaces. These are shared using ExtCopyGeom.
At the component level, we create a "master" one piece model, place
this in it's own assembly. This master model will use ExtCopyGeom on
the toplevel skeleton. Then stuff individual sub-components needed
for this component model into the same component assembly. These sub-
components use ExtCopyGeom from the master model (only geom needed to
create) . Some other sub-assemblies may be needed, etc. etc. The
point being, there are no isolated components. When you open the top
level assembly, ~all components are opened and all updates are
propagated through entirely. Drawings use Simplified Reps a lot due
to so many of the same components stuffed into the assemblies.
We use a lot of weldments in our operation. Weldments require a
unique method for modeling and after several years we have, what I
believe, nailed down successful methods. The above has worked pretty
flawless for us. Duplication can get a little problematic though.
Have to really think ahead before hand on what components may be re-
used.
imo, ~don't use Merge... this can be a real pain in the future. We
avoid them like the plague.
we use some inheritance--works good with castings.
use CopyGeom sparingly--only in short assemblies where sub-components
can be "hard-wired" and will not be used without the parent assembly.
-mark
|
