This is a multi-part message in MIME format.
------=_NextPart_000_0006_01C85EA5.BA5422B0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
"graminator" <grahamew@[EMAIL PROTECTED]
> wrote in message =
news:54dab32c-ef3b-40f1-aee3-59325cdef513@[EMAIL PROTECTED]
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?
I did something similar in a way that's not on your list. I use a =
skeleton model to communicate information between components in an =
assembly.
I had a relatively small component rack with a lot of cables and cable =
terminations, often more than one per cable: over 50 cables, over 120 =
terminations and routing between them. After someone else started the =
cable routing business and created half a dozen circular references, I =
decided there had to be a way to avoid this, to get component references =
into the cables without creating circular references and robust enough =
to update when component position changed.
That way was to create pub geoms on the component terminations, copy the =
pub geoms, with copy geometry, into the skeleton part, mate all the =
cables to the default location (comp csys to assem csys) so no circular =
refs were possible, and, ignoring how the components were assembled, =
built the cables with geometry refs copied from the skeleton model, =
through which the cable terminations stayed parametrically linked to the =
components. It was pretty robust, though somewhat labor intensive.
In addition to the component terminations, copied from pub geoms on the =
components, I also copied a lot of reference geometry from the rack to =
use for creating points for routing cables. So, in the end, this =
skeleton part had hundreds of features (surfaces, datum =
points/planes/axes and patterns) that could all be used for components =
references, especially thru point curve references. They could be =
directly created in the skeleton or be copied from component geometry or =
pub geoms (which are nice because you can include a range of geometry in =
one pub geom feature, e.g. surfaces, points, axes, planes.) And when you =
copy geom from a pub geom in a skeleton part, you get this geometry as a =
group.
In addition to the methods you mentioned, another I've heard of for =
molds, specifically, is Inheritance Features. Haven't used them, though =
they are reputed to avoid drawbacks of other methods.
David Janes
------=_NextPart_000_0006_01C85EA5.BA5422B0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.3243" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"graminator" <<A=20
href=3D"mailto:grahamew@[EMAIL PROTECTED]
">grahamew@[EMAIL PROTECTED]
>> wrote in =
message=20
<A=20
=
href=3D"news:54dab32c-ef3b-40f1-aee3-59325cdef513@[EMAIL PROTECTED]
">news:54dab32c-ef3b-40f1-aee3-59325cdef513@[EMAIL PROTECTED]
>...</DIV>When=20
you have an assembly and you need to keep a relation****p =
between<BR>parts (say=20
for example you have a molded enclosure with screw bosses)<BR>how do =
you keep=20
your parts parametric? Do you:<BR><BR>1. Use Copy Geometry from a =
master part=20
in your assembly;<BR>2. Use External Copy Geom and publish from a part =
that is=20
not in your<BR>assembly;<BR>3. Use copy and paste from a master part =
in your=20
assembly;<BR>4. Use >Edit >Component Operations >Merge =
and=20
merge an entire master<BR>part into your child part.<BR><BR>Why do you =
prefer=20
your particular method?</BLOCKQUOTE>
<DIV>I did something similar in a way that's not on your list. I use a =
skeleton=20
model to communicate information between components in an =
assembly.</DIV>
<DIV> </DIV>
<DIV>I had a relatively small component rack with a lot of cables and =
cable=20
terminations, often more than one per cable: over 50 cables, over 120=20
terminations and routing between them. After someone else started the =
cable=20
routing business and created half a dozen circular references, I decided =
there=20
had to be a way to avoid this, to get component references into the =
cables=20
without creating circular references and robust enough to update when =
component=20
position changed.</DIV>
<DIV> </DIV>
<DIV>That way was to create pub geoms on the component terminations, =
copy the=20
pub geoms, with copy geometry, into the skeleton part, mate all the =
cables to=20
the default location (comp csys to assem csys) so no circular refs were=20
possible, and, ignoring how the components were assembled, built the =
cables with=20
geometry refs copied from the skeleton model, through which the cable=20
terminations stayed parametrically linked to the components. It was =
pretty=20
robust, though somewhat labor intensive.</DIV>
<DIV> </DIV>
<DIV>In addition to the component terminations, copied from pub geoms on =
the=20
components, I also copied a lot of reference geometry from the rack to =
use for=20
creating points for routing cables. So, in the end, this skeleton part =
had=20
hundreds of features (surfaces, datum points/planes/axes and patterns) =
that=20
could all be used for components references, especially thru point curve =
references. They could be directly created in the skeleton or be copied =
from=20
component geometry or pub geoms (which are nice because you can include =
a range=20
of geometry in one pub geom feature, e.g. surfaces, points, axes, =
planes.) And=20
when you copy geom from a pub geom in a skeleton part, you get this =
geometry as=20
a group.</DIV>
<DIV> </DIV>
<DIV>In addition to the methods you mentioned, another I've heard of for =
molds,=20
specifically, is Inheritance Features. Haven't used them, though they =
are=20
reputed to avoid drawbacks of other methods.</DIV>
<DIV> </DIV>
<DIV>David Janes</DIV></BODY></HTML>
------=_NextPart_000_0006_01C85EA5.BA5422B0--
|
