UG Updating

[jamesdufour]

Hi All

We are experiencing updating on most of the jobs we open fully. Why is this happening and how can we fix this issue?

Thanks

James Dufour

 

[KhimaniMohiki]

Tools>Update>Interpart Update>Delay Geometry, Expressions and PMI

Tools>Update>Delay Model Update

Khimani Mohiki
Design Engineer - Aston Martin
NX8.5

 

[looslib]

Files will always update if you are running a newer version of UG than the file was saved in.


"Wildfires are dangerous, hard to control, and economically catastrophic."

Ben Loosli

 

[jamesdufour]

This updating happens every time you load the same file even after saving it. This should not be happening.

 

[cowski]

Does the file make use of any wave linking or interpart expressions?
If so, these parts may be updating if the source file is open and marked as modified.

www.nxjournaling.com

 

[KhimaniMohiki]

Have you tried starting in Gateway rather than modelling?

Khimani Mohiki
Design Engineer - Aston Martin
NX8.5

 

[kapmnit123]

Hi James,
There might be couple of reasons:
(1) Wave linking as already pointed to by cowski
(2) one more reason can be If a part is saved while it's last feature is not the CURRENT FEATURE (i mean if you have used MAKE CURRENT FEATURE on any intermediate feature ) .... Just make the last feature the CURRENT FEATURE and save it back..this should solve the issue.
(3)This might not be truely your case but i have noticed (not in many cases though and at least not in normal modelling) that some how when you work (in a partially loaded state) on an assembly with a complex WAVE LINKING pattern and save it like this...the next time you open it you may find some broken links in some parts and no matter if you fully load it afterwards and save it..the next time you open it ...it will still show parts updating...so the only option avaliable will be to reach out to those broken links and mend them (use relation browser for a quick validation)

Best Regards
Kapil Sharma

 

[multicaduser]

There is another possibility, that all the parts are not being saved even though NX is reporting that they are. We have here specific examples (not assembly specific), where over a local netowork some files were saved and some were not. This was discovere accidentally when one user with the assembly open asked another user to open it and it updated incorrectly. This did not happen when working locally with the same assembly.

 

[jpetach]

Another possible trigger for updating during loading is positioning constraints. Similar to the suggestion from KhimaniMohiki, delaying these position updates may help. As Cowski suggests if there are interpart links in the assembly defer those as well. (these links may have occurred implicitly for various reasons (assembly cut, deform component, routing port selection, selection outside work part)

As multicaduser and looslib point out the parts may not have saved to the current NX version. This would also occur if the component parts are part family members. Open the part family template and update the members using the latest NX version. Use info, part, loaded parts to check the NX version of the parts.

The NX status line may provide insights in to what and why the updates are occurring. Are there out of date sheet metal flat patterns in any of the parts?

HTH, Joe