2 Parts into 1

[treddie]

Hi.
Here is a problem I don't know if there is a solution to, although I have looked and looked for one.
I have a screw .prt file. It has a non standard head that would take too long to recreate (a spline section), and a threaded shaft that I want to change to the shaft in ANOTHER .prt file. The problem with any of the MERGE procedures I have been able to test, is that the imported parts are no longer editable AND independent from their originals; only the original part in the .prt file is editable (the imports are more like uneditable quilts that reference external files which ARE editable). But that seems unnecessarily complicated; to have to have a portion of the merged part depend on external files as if the merged part were an assembly, is annoying, when ideally, I'm looking for a FULLY editable merged part independent from ANY external files, as if the .prt file was originally created that way. I know that trying to import a fully editable .prt file into another .prt file could lead to regen problems, but in this case, the screw head is simply butting up against the threaded screw shaft.
Any guidance would be appreciated, if just a reference to an earlier thread or book for information.
Thank you in advance.
treddie

 

[dakeb]

Save the part with the spline head to a new name, make a udf of the shaft feature of the other part, delete the shaft feature from the new part, add the udf of the shaft feature.

You may have to redefine the features of the shaft part before creating your udf to minimise the references when you add it to the spline head part.

If the shaft is more than a single feature, you might be better off grouping the features before creating the udf.

 

[treddie]

Hi dakeb.
Sorry I haven't responded...been very busy, no time to breath. I am going to try your suggestion tomorrow, after a good night's sleep.

treddie

 

[Heckler]

FYI - About User-Defined Features:

User-defined features can be subordinate or standalone. Consider the following definitions:
• Subordinate—A subordinate UDF gets its values directly from the original model at run time, so the latter must be present for the subordinate UDF to function. If you make any changes to the dimension values in the original model, they are automatically reflected in the UDF.
A model can have more than one subordinate UDF associated with it. Items in the family table of a subordinate UDF show the identifiers and symbols from the original model.
• Standalone—A standalone UDF copies all the original model information into the UDF file. Because of this, a standalone UDF requires more storage space than a subordinate UDF. If you make any changes to the reference model, they are not reflected in the UDF.
When you create a standalone UDF, you have the option of creating a reference part by copying the original part from which the UDF is derived. The reference part has the same name as the UDF, with the extension Ò_gpÓ. For example, if you name a UDF radial_holes, the reference part is named radial_holes_gp.prt. A reference part displays UDF references and elements through the original features.


Best Regards,

Heckler
Sr. Mechanical Engineer
SW2005 SP 5.0 & Pro/E 2001
Dell Precision 370
P4 3.6 GHz, 1GB RAM
XP Pro SP2.0
NVIDIA Quadro FX 1400
o
_`\(,_
(_)/ (_)

Never argue with an idiot. They'll bring you down to their level and beat you with experience every time.

 

[treddie]

That did it.
Thanks guys. If someone doesn't know where to look for procedures, it sure can be hard to find 'em.
Sure seems like PTC could make it easier by making it possible just to import an existing .prt file, and simply replace references then, or tell it to use a coord system. It can be done in Assembly, why not Part? Weird...Once again, PTC takes one step and turns it into 10 steps.
Again, thank you. And I must donate to Eng-Tips Forum. This is probably the best resource for ProE I have found in all my Inet travels. Well worth supporting.

treddie