Key differences between standalone/subordinate options when creating UDF's

[OM_10919029]

I'm here seeking some clarification on the main differences between using standalone vs subordinate when creating a user-defined feature (UDF). I am currently using Creo 7.0.2.0, and I think I've started to grasp the concept of it by performing some tests. From what I've gathered, standalone and subordinate are the same in the fact that both options allow you to modify the UDF by adding/removing/changing the variable dimensions and family table dimensions as well as changing the reference prompts using the UDF Menu Manager.

Correct me if I'm wrong, but I believe that the key difference between the two is the ability to edit the actual feature the UDF is referencing. So, when creating a subordinate UDF, since it is directly related to the parent part, if you go back and change the features of the parent part, then the changes will be included in the UDF as well. For example, if you have a UDF of a revolved hole feature, you can go back to the base model and change the dimension of a radius or the angle of a chamfer. However, if you create a standalone UDF, and want to go back to the base model to edit the features, it will not update the UDF that is created from it. Is this correct?

Also, if you are not able to edit the original features of a standalone UDF, what would be the point in "including the reference part" after selecting the standalone option? I noticed that when you select this option, it creates a gp.prt file in addition to the standard .gph file. Is this just used in case you want to make changes to the feature, but do not want to mess up the original part? Therefore, you would have to make the changes to the feature in the copied part and then create a new UDF since the standalone UDF does not update.

I'm also curious about the limitations of what features you can change when using the subordinate option while also having a family table if anyone happens to know.

Thanks in advance!

[tbraxton · Accepted solution]

You have assessed the main difference already. The subordinate option is making the placed UDF in a target part dependent on the UDF original model. I have no insight into the family table behavior when used in conjunction with a subordinate UDF.

PTC summary of the differences:

• Subordinate UDF: 
  • A subordinate UDF gets its values directly from the original model at run time, so the original model 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.
  • if you add reference after created subordinate UDF, the new added reference also be added when you using UDF.
    • When creating the UDF the original model will automatically be saved to its location or to the working directory if it hasn't been saved already
    • When using the UDF the original model will need to be in the working directory or else the message "Can not find group" will be displayed
• Standalone UDF: 
  • A standalone UDF copies all the original model information into the UDF file.
  • If you make any changes to the reference model, they are not reflected in the UDF.
    • When creating the UDF Creo will ask Do you want to include reference part? and by Yes will store the original model in the working directory
    • When using the UDF the original model doesn't necessarily need to be in the working directory but if it isn't the option View source model won't be available

[OM_10919029]

Thanks for the reply!

Do you happen to know the reasoning for having the gp.prt file in addition to original part and the .gph file when opting for the standalone UDF? Is it so you can make the changes in the copied file instead of the original in the case you want to make a new UDF?

[tbraxton]

I am pretty sure that those are used to manage the UDF library, should you use one. There are database management functions specific to UDFs files.

From PTC docs:

Before you create a UDF, you may want to create a UDF library directory. By default, the UDF is created in the current directory.

If you create a UDF library directory, make sure all users have Read access permission. When you create a UDF library, copy the UDF files, name.gph and name_gp.prt (for standalone udfs), to this UDF library directory.