Error message "There is an object which depends on itself"

[Bogdan1985]

Hi Team,

I thought the last time I know the most I need in NX. I cannot open a large assembly because an error
message show up with the words "There is an object which depends on itself".

How can I figure out which part it is when I not can open the assembly? Is there maybe a trick
via an analyses?
Maybe I go nuts one time!!

 

[NutAce]

Did you check the logfile?
What I usually do in such cases is, open the assembly "structure only" and then the components / sub-assemblies one by one until the error pops up. When this happens with a sub-assembly I repeat the same procedure again.

Ronald van den Broek
Senior Application Engineer
Winterthur Gas & Diesel Ltd
NX9 / TC10.1.2

Building new PLM environment from Scratch using NX11 / TC11

 

[Toost]

As Ronald says, Use Structure Only loading,
( also using Full load , not partial load, has helped me on some cases.)
then load "the lower half" of the navigator. if it crashes,restart and load the lower 1/4 of the assy navigator, if not , try the lower 3/4 of the assy navigator.
"half the half-etc"

When loaded, have a thorough look at Wave links if there are such. My experience is that these might produce this error.
- load the entire assy fully, then Update all linked objects.

Regards,
Tomas

 

[Bogdan1985]

Ronald and Toast,

it works with structure.

As Saved
Structure only
use partial loading
uncheck "allow replacement"
uncheck "Generate Missing Part family members
uncheck restore fully loaded state
check restore reference set
previous visible components

Took a while to figure out what's happen.

But the assembly came back with error messages. I made a screenshot of
the error message with the numbers of the parts and cut them
in the assembly folder and in the tree.

Great Thanks

 

[NutAce]

Don't see any screenshots

Ronald van den Broek
Senior Application Engineer
Winterthur Gas & Diesel Ltd
NX9 / TC10.1.2

Building new PLM environment from Scratch using NX11 / TC11

 

[niedzviedz]

Don't You have some wave links between parts:
in part 1 links from part 2, then after some changes in part 1 links goes to part 2?

For example: 1 big part call it Core and You wanna add some insert in it, so You create another part and create wave link from core, cut it to required shape, then in core You have to cut this section for insert, so You created another wave link from insert, the cut it out. In this situation, if You didn't check "fix at current timestamp" when linking, You have Recursion effect.

If You have some smaller assemblies in this big assembly, try to open each one separately, and discover which one have open errors.
You can also try to choose option from menu -> tools -> update -> interpart update -> delay geometry, expressions and PMI update.

With best regards
Michael