Machinery Library Components Causing Assy to be "Modified"?

[Kyle89]

I have recently started using the NX Machinery Library (in NX6) and it works great, however any assembly that I insert machinery library components into always shows as being "modified" even after it has been saved. I narrowed it down to the machinery library components by suppressing components out of the assembly one at a time. It doesn't seem to matter what the component is as long as it is a component that came with NX's library (I have a couple of custom part family components that don't cause any issue) or how it is placed in the assembly (mated or completely unrestrained).

Any thoughts on this would be greatly appreciated.

Thanks,
Kyle

 

[JohnRBaker]

I would run refile on the Machinery Libraries and bring those parts up to the level of whatever version of NX that you're currently using.

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.

 

[Kyle89]

Thanks for the reply John,

What exactly do you mean by "refile"?

 

[Toost]

Refile is a function / program which can be executed such that you update all your Unigraphics / NX parts to the last possible version of NX.
Say that you have some thousands of parts which have been created over the years in different Unigraphics / NX versions. Then If you run the Refile function, all parts will be upgraded to NX6 format ( as you are running NX6)

Running Refile is a bit complex, there are things to consider before starting. I am pretty sure that there should be best practices maybe on this site.
also the NX documentation has quite some info.


Do you use Teamcenter ? ( Then there are more things to consider, and possibly a few other possible issues for the original question.)

Regards,
Tomas

 

[Kyle89]

Refile worked... kind of....
It looks like I have to refile each individual part file after it is created from the machinery library master which is a little annoying.

FYI not using Teamcenter

 

[JohnRBaker]

If the 'family member' does not currently exist, when you create a new one using the master template, even if the template itself was not run through refile, the new family member will be created using the current release of NX. When you refile the Reuse Library, it's the FAMILY MEMEBERS that need to be updated. Make sure that you're including them as well since they are NOT automatically saved in the same location as are the master templates. In fact, if you're running in production with multiple versions of NX, not different MR/MP releases but actual full versions, like NX 8.5 and NX 9.0, it might be best to NOT update the templates if you've only got one set of reuse libraries installed.

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.

 

[Kyle89]

My master templates have all been run through refile.

When I create a NEW family member in an assembly and save it there are no issues with that assembly. However, if I add that same family member to a new assembly then the new assembly will show as being "modified" until I refile that family member.

Everything is running in the same version of NX and at every step along the way the correct version of NX is shown in the family member part history.

 

[JohnRBaker]

Well if you just added a component to an Assembly, of course it will be flagged as 'modified'.

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.

 

[Kyle89]

After saving and reopening it still shows "modified" (the original problem).

 

[JohnRBaker]

You are aware, aren't you, that if you use the master template to create a family member and that family member already exists, even if it was created using an older version of NX, that NX will use the existing file and NOT create a new one? That means that the Family Member could be flagged as 'out-of-date'.

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.

 

[Kyle89]

Yes I am aware of that. I really don't think it is a versioning issue (at least a straight forward one) as everything is being created in the same version of NX and all master files were refiled to the current version. All of the parts involved (master and family member) show the correct version of NX in their Part History.

Like I said, after a NEW family member is created, the only way to get any assembly (other than the one in which the component was initially added) to save properly is to refile the FAMILY MEMBER part file first. I doesn't make sense to me that the assembly in which the family member was initially created should act any differently than any other assemblies that use the same component.

 

[JohnRBaker]

I know there have been issues in the past with Assemblies shown as being modified when they were not so I would check with GTAC to see if you perhaps are in need of updating to a version of NX where these issues have been addressed.

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.