problema assembly constraints

[stefano.garbin]

Dearest,

I and my colleagues are fighting at times with a problem that we cannot understand and even play.
in fact it happens that opening some assemblies (in which all the pieces inside are completely bound) you see all the parts "navigate in the air", as if the constraints were failed.
However, looking at the assembler you can't see any warnings regarding the constraints!
then maybe after closing and reopening the asses everything is ok.
The only case we found a motion solution was that of a set with a component that created problems. If everything was suppressed, it would come back ok, eliminating and re-adjusting that component, the problem was settled.
do you have any problems?
ps: I forgot, we use nx7.5.4.4 + tc8.3.0.3

 

[ceschi1959]

Hi.
tried to load the assemblies with the 'use partial loading' option disabled?
the partial loading in fact makes sure that nx loads the components with only the geometry defined in the reference set. the constraints are on other geometry, hence the failure of constraints.

p.s. good work

 

[stefano.garbin]

Thank you for the helpful advice!
When the problem comes back, I'll try to do as you say!

 

[avalon3d]

stefano, you should centralize the load options, or give a std to all by also controlling the save options.

Hi.

 

[stefano.garbin]

all user management is already centralized (with "nx75custom" of rob cohon) with load options and save options preset.
the thing that intrigues me is that this behavior occurs with axioms facts, saved and reopened also by the same user and no one else.
nb: obviously no strange message in nx logs.

 

[avalon3d]

mh... nose must see how the constraints were given. the assembly constraint has simplified life a lot, but a user used to use mating condition remembers fun episodes. . :biggrin:

Are all solids of the assembly parametric and modeled with criterion?

bhe, I guess you've already figured out the user level of all users...

Try to see what happens even by launching a cleanup part if it re-captures.

Hi.

 

[spantik]

hi avalon, sorry if I deviate a moment, I take advantage of the point and if it serves I move: from nx5 to nx6 I can not understand the new logic of mating condition: how does it work? If there is already a post, can you direct me? Thank you and excuse the intromission.

 

[The_Matrix]

Hi.
tried to load the assemblies with the 'use partial loading' option disabled?
the partial loading in fact makes sure that nx loads the components with only the geometry defined in the reference set. the constraints are on other geometry, hence the failure of constraints.

p.s. good work

in nx8.5 the logic of the "partial loading" has changed, if I don't remember bad now the ac and wl also work to pl activated.
(I am 100% sure for wl... on ac I rely on memory)

 

[Utente NX]

in nx8.5 the logic of the "partial loading" has changed, if I don't remember bad now the ac and wl also work to pl activated.
(I am 100% sure for wl... on ac I rely on memory)

nx8 and nx8.5 behave the same way, nothing has changed.
the 'partial loading' you can activate it already from nx8, but I recommend you to activate also 'load smart lightweight data' in the customer default.

 

[The_Matrix]

nx8 and nx8.5 behave the same way, nothing has changed.
the 'partial loading' you can activate it already from nx8, but I recommend you to activate also 'load smart lightweight data' in the customer default.

the "smart lightweight" should be activated by default for everyone (after the refile, it means, otherwise it doesn't serve anything)... it must really be a good reason not to.
Oh, my God. you don't know how many companies don't use lightweight... :frown:
I throw it there: 90%.