Suppression And Assembly Constrains 1

[spadazenon]

We are currently moved to NX7.5 after many years in NX3.
We have some assemblies, where from expressions could someone suppress or not components.

This was working good in NX3 and is working well in NX7.5 still.

The problem here with assembly constraints (over 200), is that if you suppress a component the corresponding constraint will give an error, which will remain until you unsuppress the component.
Can somehow suppress those constraints automatically or do sth else?

Thank you all.

 

[eex23]

Yes, we have also this problem...

http://www.eng-tips.com/viewthread.cfm?qid=290124&page=1

in that thread I also asked about suppressed components and constraints...

 

[spadazenon]

Sorry for making a duplicate post.

Maybe the answer for the suppressed components is using Arrangements and the constraints for those components to be arrangement specific. But still we have a lot of assemblies not created with the arrangement option.

 

[JohnRBaker]

Starting with NX 7.5.2.x, we have changed the Constraint Icons as seen in the Assembly Navigatot to indicate the level of SEVERITY when a constraint fails to update or there is some issue which you may wish to get feedback concerning. In the past all that you would see was a single type of indication, a [COLOR=white red](X)[/color] indicating a failure with very little feedback as to exactly what happened. Now there will be 3 different status icons used.

There will still be an 'Error' status, shown as a [COLOR=white red](X)[/color] flag appended to the actual Constraint icon, but in addition there will also be a 'Warning' status, shown as a [COLOR=black yellow]/!\[/color], and finally an 'Info' status shown as a simple <i> flag. And if you enable the 'Info' column in the Assembly Navigator, these same symbols will be seen there as well and when you place your cursor over the symbols in this column a 'tool tip' will appear with information about what may have caused the flag to be appear. Also, since these flags are shown in a column of their own, they can be sorted by severity by simply clicking on the column header.

Note that for the next release of NX we will try to provide additional feedback as to what happened and eventually we would like to even offer 'hints' as to what your next course of action might be. Also with the new Constraint Navigator we will be able to provide even more tools to help highlight and investigate possible Constraint issues, including the ability to Group Constraints by Status which will make it very easy to isolate Constraints which have a status of 'Error', 'Warning', 'Info' and even constraints which are 'OK', that is those with NO issues whatsoever.

John R. Baker, P.E.
Product 'Evangelist'
Product Design Solutions
Siemens PLM Software Inc.
Industry Sector
Cypress, CA

http://www.siemens.com/plm

http://www.plmworld.org/museum/

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

 

[spadazenon]

We applied the update directly to NX7.5.2.5 from NX7.5.0. I see the changes in assembly constraint icon (is better than before).

But, because I like it to be clean, I've seen that the best way (in NX7.5) to avoid being confused with constraints that become red(or warning / info) is to right click on the constraint and choose arrangement specific. There you can apply in which you like to be present. But given the fact that we never used arrangements before and that we have a lot constraints this can take much time.

In NX3 the mates would simply suppress with the corresponding component.

 

[JohnRBaker]

Why the paranoia? You suppressed those components for a reason, correct? As long as those components are suppressed their Constraints are irrelevant anyway. So what's the problem if you ignore them and move on?

John R. Baker, P.E.
Product 'Evangelist'
Product Design Solutions
Siemens PLM Software Inc.
Industry Sector
Cypress, CA

http://www.siemens.com/plm

http://www.plmworld.org/museum/

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

 

[spadazenon]

Sorry for the late reply but....

Paranoia (Derived from the Greek words "Para"=Out and "Nous"=Mind)?

We have a big problem with the constraints and it is not a manner of just ignoring them. When the time of physical assembly comes, we need to be extra sure that all join together.

So we need to focus more that these constraints are not causing any problem to the parametrized assembly. That needs time and that decreases productivity.

So I thing that what I say are not out of mind.
Thanx.