Part Family Questions
Part Family Questions
(OP)
I am working in NX7.5.5 and have many assemblies that have family members with embedded family members 2 or 3 deep. There are issues with many of these assemblies which I am struggling to figure out how best to do the following.
- Identify what is actually causing the issues when trying to load the main assembly.
Usual errors are memory access error,file will not load the family member file with out prompting any type of error,last one is it will not load, and says it can't find the file, even though the file is in the released directory
- What is best practices for when creating part family masters and the components?
- Is it possible to do a part clean up on the master FAM part and update the members, and will the clean up be pushed to these members in this process?
- If when trying to do an update of the part family members and all members fail to update based on a feature issue, is it best to delete the members and recreate them, or to do an update once the issue is corrected?
- When trying to submit an assembly that has these multilevel family members in them, what is the best way to clone or save as and capture all the family members that don't get recreated with the new naming convention due to being read only?
I know it is a lot of questions, but this area of NX is where I spend 70% of my time in trying to assist the engineers in why their assemblies don't load properly or at all.
Thanks,
Kevin





RE: Part Family Questions
So my best practice is:
Best: make families only of parts in which dimension(s) varies.
Acceptable: parts in which features are suppressed/unsuppressed
Acceptable: simple assemblies in which an attribute changes (for color, for example)
Perhaps you could try to clean up your familes this way:
open the lowest level family with no partial loading and load interpart data turned on. Maybe also "allow replaecment." (I'm on NX7.5)
run edit>feature>playback step by step. Fix EVERY error that shows up.
Then run Part cleanup.
Then update the family members.
Repeat at the next assembly level up.
By a celebration pack of good beer if this works
Send to me (Ha!)
RE: Part Family Questions
Keep them simple and avoid assembly families.
"Wildfires are dangerous, hard to control, and economically catastrophic."
Ben Loosli
RE: Part Family Questions
Also, Has anyone use the reuse library for any type of common components that would allow for different options, similar to the part families? I am trying to figure out what is the best way to get the benefits of the part families but not having to deal with the read only members.
Thanks
RE: Part Family Questions
Also, there's a way to setup a Part File in the Reuse Library so that it behaves the same as would a Part Family part EXCEPT the files created are NOT 'Read Only'. If you have any of the Reuse Libraries installed, look at the the class of objects in the folder labeled 'Profiles' There you will find things like pipes and rolled structural shapes which behave like Family Table parts except that the part files created are NOT 'Read Only'.
John R. Baker, P.E.
Product 'Evangelist'
Product Engineering Software
Siemens PLM Software Inc.
Industry Sector
Cypress, CA
Siemens PLM:
UG/NX Museum:
To an Engineer, the glass is twice as big as it needs to be.
RE: Part Family Questions
RE: Part Family Questions
John R. Baker, P.E.
Product 'Evangelist'
Product Engineering Software
Siemens PLM Software Inc.
Industry Sector
Cypress, CA
Siemens PLM:
UG/NX Museum:
To an Engineer, the glass is twice as big as it needs to be.
RE: Part Family Questions
Models - omission of holes or features, which make up the different options that we have for these series of parts we create.
Assemblies - utilize the part family function to create assemblies that pull in different parts or family members that make up the assembly. Each assembly represents a different option that we product for that component.
The issues seem to be arising when we are dealing with these assemblies that contain a Sub-assembly that that has different subs inside of it, and all subs contain at least one PF member inside it. The example that I have loaded of the assembly navigator, shows the various sub-assemblies that contain many part family members at multiple levels of the build-up.