NX 1969 broken wavelinks still trigger update to all parts in assembly

[Goldor]

Hello everyone!

I've been using wavelinks in NX for many years now, and have found them to be incredibly useful.

However, I'm currently working on a complex assembly with around 30 different components (some of which are mirrored bodies). I have tried to limit the quantity of wavelinks I used, because I know how much of a mess an assembly can become with careless wavelinking. Unfortunately, I still needed to use quite a few in order to work fast, and for my updates between parts to happen quickly.

I was at a point where almost all of my parts would update whenever I made a small change to one of them, which doesn't make sense, because I made sure that the wavelinks would only flow downwards in the assembly (no loopbacks). Nevertheless, I broke all wavelinks using the Interpart Link Browser in order to stop this behaviour, but to my dismay... it continued!

I have searched the web and have come up empty, so now I'm turning to this wonderful community which has unknowingly helped me for the past several years.

Is there a possibility for some sort of phantom wavelinks to still exist between the parts? I've never seen this kind of behaviour before.

Thank you so much for your help.

 

[DrPriest]

When you make the "small change" you do it with "Edit parameters" or "Edit with rollback"? Then latter can cause further model update thus marking it out of date and forcing an update.
You can also try to delay link updates make the change then toggle the delay links update off and see if it still causes an overall update.
Ultimately you can try to freeze the links so they do not update unless unfrozen.

 

[Goldor]

Thanks for your reply DrPriest!

I believe that I do most of my changes using "Edit with rollback". I was unaware that there was a difference in the amount of model update involved.

I have already found the toggle for delaying the links update, which helped a little, but I always had to reactivate the links in the end, and this still updated most of the models in my assembly (without actually changing anything, thankfully, but I still had to save their "modified" state).

Regardless, I have found the root cause of my issue. At the top level assembly, I had created associative mass measurements per category of components (by manually selecting the different solid bodies). I had tried to suppress them last week, but the updating issue was still present, so thought nothing more of it. More recently, I realized that even though it was relatively useful to have these on hand, they were out of date anyway (missing new components) and needed to be maintained, so I thought it was safer to delete them. Surprise surprise, the issue is now gone... I had no idea that an associative solid bodies mass measurement at the top level could have an impact on all of the components when updating only one of them.

Problem solved then, and explained for all future google searches to see.

Cheers!