Parts not visible.

[VW181]

Hello,

A colleague has a problem with an assembly.

Two the same part are not visible. They are loaded in the assembly structure, but are grayed out and not checked.
First he gets the massage: "This component cannot be made visible. It is in an excluded reference set"
As mentioned on this forum I checked the only sub-assembly and that has the "Reference Set" set to "model", so I changed that to "Entire Part".

Now we don't get the warning "This component cannot be made visible. It is in an excluded reference set", but the parts are still not visible.

Now we get the next massage when opening the assembly:

######################################################################################
The following substituted component in Teamcenter has been found:

VNMVS-0228/01.001 replaced with VNMVS-0047/01.001

The following substituted component in Teamcenter has been found:

VNMVS-0228/01.001 replaced with VNMVS-0047/01.001

Child VNMVS-0056/01.001 of Parent VNMVS-0166/01.001: Child position Not Updated (Mating Conditions Present)
Child VNMVS-0056/01.001 of Parent VNMVS-0166/01.001: Child position Not Updated (Mating Conditions Present)
Child VNMVS-0047/01.001 of Parent VNMVS-0166/01.001: Child position Not Updated (Mating Conditions Present)
Child VNMVS-0132/01.001 of Parent VNMVS-0166/01.001: Child position Not Updated (Mating Conditions Present)
Child VNMVS-0132/01.001 of Parent VNMVS-0166/01.001: Child position Not Updated (Mating Conditions Present)
######################################################################################

Strange thing is that I could once check the part VNMVS-0028 and than it changed to the part VNMVS-0047. The part was checked then and not grayed out, but still invisible.
After reloading this assembly again this behavior was gone.

I also tried updating the component VNMVS-0228. The result is in the attached image.
The component VNMVS-0228 is a copy of the VNMVS-0047.

I have no idea what is going one here.
What can I try to get those part visible again?


Thanks in advance,
Tjeerd


Using NX 8.0 and Teamcenter 8 on Windows 7 (64)

 

[JohnRBaker]

Check to see if it might be either Hidden or on an invisible Layer.

John R. Baker, P.E.
Product 'Evangelist'
Product Engineering Software
Siemens PLM Software Inc.
Digital Factory
Cypress, CA
Siemens PLM:
UG/NX Museum:

To an Engineer, the glass is twice as big as it needs to be.

 

[VW181]

Thank you for your answer John.
But sadly, both options don't solve the problem.

Using NX 8.0 and Teamcenter 8 on Windows 7 (64)

 

[NutAce]

Did you change the ref set for the subassembly (in context of your main assy) or did you change the ref set for your component in cntext of the subassembly?.
Keep in mind that a ref set only works one level up...

Ronald van den Broek
Senior Application Engineer
Winterthur Gas & Diesel Ltd
NX8.5.3 / TC9.1.2
HPZ420 Intel(R) Xeon(R) CPU E5-1620 0 @ 3.60GHz, 32 Gb Win7 64B
Nvidea Quadro4000 2048MB DDR5

HP Zbook15
Intel(R) Core(TM) i7-4800MQ
CPU @ 2.70 GHz Win7 64b
Nvidia K1100M 2048 MB DDR5

 

[Arkance/PhoeNX]

Also check that layers visible in view haven't been played with.
I had a customer who got data recently and couldn't see anything as you can and was getting the excluded reference sets error as well.
Turned out that the supplier had created a custom view, with all layers turned off, so no matter what layers you turned on in the Layer dialog, you couldn't see anything.
Change the view or use Layers Visible in View and you can then see the objects.


Anthony Galante
Senior Support Engineer


NX3 to NX10 with almost every MR (21versions)

 

[VW181]

@ nutace:
I set the reference set of the sub-assy in the top level.
The 2 invisible parts are also in the toplevel.
For faster testing i've removed the only (big) sub-assy, so now it's a simple assy with a few parts in it, but still, the 2 parts stay invisible.

@PhoeNX:
You are talking about a drawing i think?
This problem is in the modeling environment.


Strange things is, that the behavior of the assy is every time different when i open it.
- one time i can replace the part by itself and it become visible. Next time I get the massage I can't replace a part with the same part.
- One time I can check (tick off??) the part in the assy-navigater and in the assy-navigator it seems like the part is visible, but it isn't. Next time when i check (tick off??) the part it stays grayed out like it's hidden.
- And two times I got the Reference set warning again, but most time ii don't get it.

So it seems more like a NX bug.
A new placed same part stays visible in the test-assy, so hopefully placing new parts in the original assy will work also good.
My colleague is gonna test it later today.


Using NX 8.0 and Teamcenter 8 on Windows 7 (64)

 

[Arkance/PhoeNX]

no i am referring to the modelling environment

Anthony Galante
Senior Support Engineer


NX3 to NX10 with almost every MR (21versions)

 

[VW181]

Then i have no idea what you mean, how to create other views, or how to change to other views.

Using NX 8.0 and Teamcenter 8 on Windows 7 (64)

 

[JohnRBaker]

Go to...

View -> Layout -> Replace View...

...and select something like 'Top' or 'Front' and then hit OK.

John R. Baker, P.E.
Product 'Evangelist'
Product Engineering Software
Siemens PLM Software Inc.
Digital Factory
Cypress, CA
Siemens PLM:
UG/NX Museum:

To an Engineer, the glass is twice as big as it needs to be.

 

[VW181]

Isn't that the same effect as rotating the parts with the space mouse?
(Also new to me that you can create more views of the part in one screen)

But changing the view has no effect on the visibility of the parts.


Using NX 8.0 and Teamcenter 8 on Windows 7 (64)

 

[JohnRBaker]

You're thinking of 'Orient View' found on the view pop-up menu. 'Replace View' is doing exactly what it says, REPLACING the current view with one of the hard-coded default views.

John R. Baker, P.E.
Product 'Evangelist'
Product Engineering Software
Siemens PLM Software Inc.
Digital Factory
Cypress, CA
Siemens PLM:
UG/NX Museum:

To an Engineer, the glass is twice as big as it needs to be.

 

[VW181]

OK, learnt something new again.
But when do you use it?

Using NX 8.0 and Teamcenter 8 on Windows 7 (64)

 

[ewh]

Rotating with the spaceball is not as exact as the canned view orientations.
You could also save a specific view orientation that you would use frequently which is different than the canned views.
Also, while it is usually considered poor practice, layer visible in view can be used in model views.

"Know the rules well, so you can break them effectively."
-Dalai Lama XIV

 

[cowski]

"But when do you use it?" (replace view)

I use it most often when creating exploded views of an assembly in the drawing file. When creating an exploded view, you create the "explosion" and apply it to an existing view; the explosion can then be toggled on or off for the given view. I like to create a new modeling view exclusively for the exploded view and use "replace view" to switch between the exploded and assembled views.

www.nxjournaling.com

 

[VW181]

Ok,
Thanks for all the answers.

Using NX 8.0 and Teamcenter 8 on Windows 7 (64)

 

[VW181]

When opening the assembly, we keep getting the massage "Child position Not Updated".
What does it mean and what can we do about it?

Using NX 8.0 and Teamcenter 8 on Windows 7 (64)

 

[VW181]

I still get the massege: Child position Not Updated (Mating Conditions Present)

Anybody an idea how to fix this?

I get a whole list of this problem


NX detected 159 Modified Transforms. Summary:
___________________________________________
Child RG00039000_01/01.005 of Parent VNTBL-0404/01.001: Child position Not Updated (Mating Conditions Present)
Child VNB48456/01.001 of Parent VNTBL-0404/01.001: Child position Not Updated (Mating Conditions Present)
Child VN27852406/01.001 of Parent VNTBL-0404/01.001: Child position Not Updated (Mating Conditions Present)
Child VN27852406/01.001 of Parent VNTBL-0404/01.001: Child position Not Updated (Mating Conditions Present)
.
.


Using NX 8.0 and Teamcenter 8 on Windows 7 (64)