Derived parts in an assembly

[Kman]

I would like to save a new part starting with an existing part which is
derived from a base part and retain all the feature history from the base
part. Putting it another way, I would like the new part to inherit the
feature history of the base part. I can certainly break the references and
save with a new name. However, the new part is like a dumb solid (i.e. no
feature history).

The only way I know how to achieve the end result is to take the base part
and saveAs new file. Then start chopping and adding features as necessary
until it looks like what I want. Very time consuming, especially when I
have a derived part that is close to what I would like to start with.

Kman

[CS]

As I try to follow your problem I think you have a derived part that is
close to what you want but most of it's feature tree is dumb, and in your
new part you want the origional feature tree from the origional part and
include the feature tree of the derived part also? That can't be done. If
your derived part is essencially a mirror of your base part I would do a
SaveAs of the base part and mirror the body and then do your mods. This
gives you all the features to be easily modified to what you want.

Regards,
Corey

Post by Kman
I would like to save a new part starting with an existing part which is
derived from a base part and retain all the feature history from the base
part. Putting it another way, I would like the new part to inherit the
feature history of the base part. I can certainly break the references and
save with a new name. However, the new part is like a dumb solid (i.e. no
feature history).
The only way I know how to achieve the end result is to take the base part
and saveAs new file. Then start chopping and adding features as necessary
until it looks like what I want. Very time consuming, especially when I
have a derived part that is close to what I would like to start with.
Kman

[Kman]

You interpretation is right on. I ended up renaming the base part multiple
times for similar parts and proceeded to remove and add features as needed.
Has anyone else come across the need for this capability on a regular basis.
The features are already there buried away in another part, why not take
advantage.

Kman

Post by CS
As I try to follow your problem I think you have a derived part that is
close to what you want but most of it's feature tree is dumb, and in your
new part you want the origional feature tree from the origional part and
include the feature tree of the derived part also? That can't be done.

If

Post by CS
your derived part is essencially a mirror of your base part I would do a
SaveAs of the base part and mirror the body and then do your mods. This
gives you all the features to be easily modified to what you want.
Regards,
Corey

Post by Kman
I would like to save a new part starting with an existing part which is
derived from a base part and retain all the feature history from the base
part. Putting it another way, I would like the new part to inherit the
feature history of the base part. I can certainly break the references

and

Post by Kman
save with a new name. However, the new part is like a dumb solid (i.e. no
feature history).
The only way I know how to achieve the end result is to take the base part
and saveAs new file. Then start chopping and adding features as necessary
until it looks like what I want. Very time consuming, especially when I
have a derived part that is close to what I would like to start with.
Kman

[\\/\\/im]

Can't you use configurations to make extra parts?
In the extra configurations you can swith on or off the extra features, so
all your parts have the same base and can also have the same extrenal
references.

Wim

Post by Kman
You interpretation is right on. I ended up renaming the base part multiple
times for similar parts and proceeded to remove and add features as needed.
Has anyone else come across the need for this capability on a regular basis.
The features are already there buried away in another part, why not take
advantage.
Kman

[CS]

In that case you could take your base part and save it as one of your
templates then you create a new part every time, but it will have the same
feature tree.

Corey

Post by \\/\\/im
Can't you use configurations to make extra parts?
In the extra configurations you can swith on or off the extra features, so
all your parts have the same base and can also have the same extrenal
references.
Wim

Post by Kman
You interpretation is right on. I ended up renaming the base part

multiple

Post by Kman
times for similar parts and proceeded to remove and add features as

needed.

Post by Kman
Has anyone else come across the need for this capability on a regular

basis.

Post by Kman
The features are already there buried away in another part, why not take
advantage.
Kman

[Kman]

Configurations may work in some situations. Generally with the exception of
commercialized hardware type stuff, I prefer that each fabricated part (i.e.
custom machine components) have a unique filename. This becomes more the
case if using incontext relations with other parts and assemblies. What if
it is decided in advance or later the base part should be different for some
of the existing and future parts.

Kman

Post by \\/\\/im
Can't you use configurations to make extra parts?
In the extra configurations you can swith on or off the extra features, so
all your parts have the same base and can also have the same extrenal
references.
Wim

Post by Kman
You interpretation is right on. I ended up renaming the base part

multiple

Post by Kman
times for similar parts and proceeded to remove and add features as

needed.

Post by Kman
Has anyone else come across the need for this capability on a regular

basis.

Post by Kman
The features are already there buried away in another part, why not take
advantage.
Kman

[Tonius K]

What's your email-address? I might have something what you're looking
for but it's a word-document and needs to be emailed.

[Kman]

Could you send it to the newsgroup as a text file. There may be others that
are interested in this information.

Thanks,
Kman

Post by Tonius K
What's your email-address? I might have something what you're looking
for but it's a word-document and needs to be emailed.

[Tonius K]

I have ten pictures in the document so i'm not able to post it here. If
you want the document you can send your email address to mine which is
***@netti.fi and i'll send it to you.

-Tonius-

[Tonius K]

toni dot korhonen @ netti dot fi

[Jerry Steiger]

Post by Kman
You interpretation is right on. I ended up renaming the base part multiple
times for similar parts and proceeded to remove and add features as needed.
Has anyone else come across the need for this capability on a regular basis.
The features are already there buried away in another part, why not take
advantage.

Ken,

Not only am I way behind on reading the newsgroup, I'm confused about what
you are looking for. Why not just make more derived parts from the base
part? Why break the references to the base part?

Jerry Steiger
Tripod Data Systems
"take the garbage out, dear"

[Kman]

Jerry,

I started out with one base part and derived two parts called upper and
lower which are used in an ASM-1. The derived upper and lower parts were
created by cutting the base part in half. The intent is to create a family
of products ASM-1, ASM-2 etc... with as many shared components as possible.
The only parts that change from ASM to ASM are the upper and lower parts,
while the other components remain unchanged but their quantities vary.
Further into the design it became apparent the base part could not be used
as is for the entire family of products. But most of the original base part
features were still valid and some others useable if modified or removed.
Modifying the original base part isn't an option because it would change all
the reliant parts in ASM-1

Next create ASM-2 from ASM-1 using SolidWorks Explorer. Copied all the
parts over into ASM-2, assigning new part numbers to the upper and lower
components before clicking Apply button. During the process of creating the
new upper and lower components for ASM-2 it would be nice to have a way for
these parts to become underived (user choice) and inherit all the features
of the original base part as applied to upper and lower components. The new
upper and lower parts would have a complete feature history of their own.
In this situation, it saves the steps of opening the original base part,
renaming, modifying into an upper and lower part, then replacing upper and
lower components in ASM-2. This all started because I chose the path of
derived parts to initiate the first design.

Kman

Post by Kman

Post by Kman
You interpretation is right on. I ended up renaming the base part

multiple

Post by Kman
times for similar parts and proceeded to remove and add features as

needed.

Post by Kman
Has anyone else come across the need for this capability on a regular

basis.

Post by Kman
The features are already there buried away in another part, why not take
advantage.

Ken,
Not only am I way behind on reading the newsgroup, I'm confused about what
you are looking for. Why not just make more derived parts from the base
part? Why break the references to the base part?
Jerry Steiger
Tripod Data Systems
"take the garbage out, dear"

[CS]

Post by Kman
Modifying the original base part isn't an option because it would change all
the reliant parts in ASM-1

Not necessarily true. You can create a second configuration and carefully
modify the part to be sure you don't affect the origional config. Then you
can derive new parts off of the second config.

Regards,
Corey

[Kman]

See what ya mean
I think that is what "Wim" was suggesting also

Thanks,
Kman

Post by CS

Post by Kman
Modifying the original base part isn't an option because it would change

all

Post by Kman
the reliant parts in ASM-1

Not necessarily true. You can create a second configuration and carefully
modify the part to be sure you don't affect the origional config. Then you
can derive new parts off of the second config.
Regards,
Corey