Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations cowski on being selected by the Eng-Tips community for having the most helpful posts in the forums last week. Way to Go!
nx5 new assembley constraints
- Thread starter uwam2ie
- Start date
- Thread starter
- #2
Here is an example for my problems with the new constraints.
The example is an simple table with 4 legs. Try to position the legs with the constraints without touching the assembley structure. I fix the plate/squamous then the legs. What does the the custumers default ... somewhere in ass. The only way to solve this with variable positioning? What about fixing the assembley part? Why can I move fixed part only confirming an
dialog...
The example is an simple table with 4 legs. Try to position the legs with the constraints without touching the assembley structure. I fix the plate/squamous then the legs. What does the the custumers default ... somewhere in ass. The only way to solve this with variable positioning? What about fixing the assembley part? Why can I move fixed part only confirming an
dialog...
JohnRBaker
Mechanical
Why did you choose the structure that you did? Why not the more obvious structure that I've choosen with 'assembly4-jrb.prt' (download below)?
Remember to keep it simple.
John R. Baker, P.E.
Product 'Evangelist'
NX Design
Siemens PLM Software Inc.
Cypress, CA
Remember to keep it simple.
John R. Baker, P.E.
Product 'Evangelist'
NX Design
Siemens PLM Software Inc.
Cypress, CA
- Thread starter
- #4
John, so far
this is a an example,
a simplied structure of our designs.
The idea of this structure is to have standard parts an part to produce new in seperate assemblys.
- what about the the moving opportunities of fixed parts.
( I expect it is not posible to move a fixed part - what is the story behind))
- why can I fix parts more than one time ?
thx in ad
this is a an example,
a simplied structure of our designs.
The idea of this structure is to have standard parts an part to produce new in seperate assemblys.
- what about the the moving opportunities of fixed parts.
( I expect it is not posible to move a fixed part - what is the story behind))
- why can I fix parts more than one time ?
thx in ad
JohnRBaker
Mechanical
- what about the the moving opportunities of fixed parts.
( I expect it is not posible to move a fixed part - what is the story behind))
I've run into the same thing and I suspect that it's a bug (I plan to open a PR). However, after you have toggled the override option for the lower-level component, the easy way out is to just select the newly inherited 'Fixed' constraint(s) and suppress it(them).
- why can I fix parts more than one time?
For the same reason that you can over-constrain anything. Besides, unlike underconstraining, over-constraining will have very little impact on the final behavior of the model.
John R. Baker, P.E.
Product 'Evangelist'
NX Design
Siemens PLM Software Inc.
Cypress, CA
( I expect it is not posible to move a fixed part - what is the story behind))
I've run into the same thing and I suspect that it's a bug (I plan to open a PR). However, after you have toggled the override option for the lower-level component, the easy way out is to just select the newly inherited 'Fixed' constraint(s) and suppress it(them).
- why can I fix parts more than one time?
For the same reason that you can over-constrain anything. Besides, unlike underconstraining, over-constraining will have very little impact on the final behavior of the model.
John R. Baker, P.E.
Product 'Evangelist'
NX Design
Siemens PLM Software Inc.
Cypress, CA
- Thread starter
- #6
John,
//taken from UG answer
what does this setting:????
Customer Default 'Assemblies -> Positioning -> Interface ->
Move Component Scope' is set to "Anywhere in Assembly", then selecting any
component in the assembly will allow it to be moved in its immediate parent
assembly, whether that is the work part or not.
thx in ad
//taken from UG answer
what does this setting:????
Customer Default 'Assemblies -> Positioning -> Interface ->
Move Component Scope' is set to "Anywhere in Assembly", then selecting any
component in the assembly will allow it to be moved in its immediate parent
assembly, whether that is the work part or not.
thx in ad
JohnRBaker
Mechanical
Yes, but that is an 'All or Nothing' setting affecting EVERY component in EVERY sub-assembly in the overall assembly. While there might be uses for this, I prefer to explicitly decide WHICH components of WHICH sub-assembly do I wish to be made 'movable' from my current level of the overall assembly since it's conceivable that I will NOT need that level of control over ALL components on ALL levels ALL of the time.
Besides, as it states in the Customer Default description of the option, setting the option to 'Anywhere in Assembly' means that ALL assembly constraints are solved at once and while computers are fast (and getting faster) solving perhaps several hunderd, if not thousands, of simultaneous constraint equations, even if many of them have not changed since the last update, could have an impact on performance, which of course is why that Customer Default is set to 'Work Part Only' by default since that will have the smalles impact on performance and until users are aware of what the implications are, the least surprises.
John R. Baker, P.E.
Product 'Evangelist'
NX Design
Siemens PLM Software Inc.
Cypress, CA
Besides, as it states in the Customer Default description of the option, setting the option to 'Anywhere in Assembly' means that ALL assembly constraints are solved at once and while computers are fast (and getting faster) solving perhaps several hunderd, if not thousands, of simultaneous constraint equations, even if many of them have not changed since the last update, could have an impact on performance, which of course is why that Customer Default is set to 'Work Part Only' by default since that will have the smalles impact on performance and until users are aware of what the implications are, the least surprises.
John R. Baker, P.E.
Product 'Evangelist'
NX Design
Siemens PLM Software Inc.
Cypress, CA
- Status
Similar threads
- Locked
- Question
