Join our MCAD Central community forums, the largest resource for MCAD (Mechanical Computer-Aided Design) professionals, including files, forums, jobs, articles, calendar, and more.
Is there an option like Configurations as in Solidworks. This would be useful if i want to have 2 models(/Quilts) with a few modifications - (adding Holes, M/c'ing Allowance etc., -- Casting & Machined Model).
I am not sure whether Family Table could be used. I have 1 component & it will have 2 variations. Some features will be present in 1 variation whereas some other features will be there in the 2nd one. If changes were to be made in only one model, then maybe Family Table could be used.
Another option is to use inheritance features. Built the basic, common
model as the 'generic'. Then create a new part and use insert -> shared data -> merge/inheritance. Then browse to your 'generic' and select it as the source model. That will bring in the full feature tree of the 'generic' under a single feature called an inheritance feature. You can set up ways that the geometry should vary, by changing dims and suppressing features, if you like. You can also then add other features after the inheritance.
If you dont have AAX , then you have to use merge . Regarding inheritance, when you want to copy some geometry from a part into another part, but you might want to skip som features from it, then use Inheritance. The inheritance becomes like a famlitable instance where you can say no to some features...but still have have thedependency if something updates.
If you got part A , and want to copy A geometry into part B, but you want to leave out some holes in part A when copying it, then use inheritance.
Pro/E help = Inheritance features allow one-way associative propagation of geometry and feature data from a reference part to a target part within an assembly. The created target part is fully functional even when the reference part is not in session. Use Inheritance features to create variations of existing models. An Inheritance feature begins with all of its geometry and data identical to the reference part from which it is derived. You can define the following varied items of an Inheritance feature:
<UL>
<LI =kadov-p-CTopic-Text-Bulleted> Dimension values, tolerances, and boundaries
<LI =kadov-p-CTopic-Text-Bulleted> Geometry tolerances (part of Annotations)
<LI =kadov-p-CTopic-Text-Bulleted> Parameters
<LI =kadov-p-CTopic-Text-Bulleted> References
<LI =kadov-p-CTopic-Text-Bulleted> Suppressed, resumed or erased state of features
<LI =kadov-p-CTopic-Text-Bulleted> Annotations</LI>[/list] Note: Varied item settings that are the same as the original model are identified with a
in the Varied Items dialog box. You can add new varied items, redefine them, or remove the existing ones.
//Tobias
A family table builds copies of the generic with variations, but does so all in one file.
An inheritance builds a stand alone, although dependent, copy of another file (the 'generic') and allows you to vary items within the copied features as well as add features after those.
Copy geometry is really a different animal, it allows you to copy specific pieces of geometry (curves, planes, surfaces, etc) from the targeted model. It really doesn't lend it self to copying entire models and doesn't allow variations of the copied data.
If your goal is to copy the geometry from one part to another, youcanuse "copy geometry" and use the option "solid surfaces" when youspecify your surfs (works perfect when the geo is updated) .If you do that , the modell size will not be as big with CG as with inheritance . It
Another not so trivial difference between family tables and inheritance is that family tables are... well... tables So you can generate new instances simply by editing the table. Family tables are good when you have an entire set of variable parts.
With an inheritance based model, opening any instance and doing a 'Save As' creates a new instance. Pretty easy, but depending on how custom the original inheritance feature was, might take time to generate what you want.
With an inheritance based model, opening any instance and doing a 'Save As' creates a new instance. Pretty easy, but depending on how custom the original inheritance feature was, might take time to generate what you want.
I think inheritance is better when you have to change quite a lot in your part, for example I made a lot of LEGO pieces and managed all variations of size and thickness of basic parts with family tables. That's easy because if you want a 4x6 piece you don't have to open the part, look for the patterning feature etc, you simply add a line to the table. But then I used family tables too for managing a 1x1 simple block and a 1x1 car light block, they are so different that the family table is full of suppressed or retained features. In this case the inheritance should've worked much better
The context I saw inheritance features promoted was to work better with PDM/link. With family tables, a change to 1 instance marked the generic as changed which then marked all instances as changed. With the inheritance approach, a change to an instance only tagged that instance as changed.
I'm not familiar with PDM/Link or any PDM system, some have said that's not the case or maybe it isn't the case any more.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
So you can generate new instances simply by editing the table. Family tables are good when you have an entire set of variable parts.