Quantcast
Channel: NX Design Forum topics
Viewing all articles
Browse latest Browse all 5175

Bizzare behavior with assembly constraints and component patterns

$
0
0

Hello, I'm adding components to an assembly and then I just patterned a component.  What I completely do not understand and never even saw in NX 10 (even with all the trouble that was) is, that when I finished creating the component pattern, the assembly constraints for some parts (that appears to have nothing to do with the patterned component) are all of a sudden showing as having a conflict.  After scrolling up and down the Constraint Navigator, I now see that there are probably 30 components or more showing assembly constraint conflicts.  Of course, there's probably just one offending constraint, but could take a very long time to find that one.

The component pattern that I made is a Linear layout and is just going off in one direction with a certain count and pitch distance.  How would that affect already existing components?  Just before this, I created a similar component pattern and there weren't any problems.  I moved a little over to another part and tried the exact same thing, but with completely different results.  

I put in a different post today  how the preview for component patterns is flaking out and I mentioned earlier that assembly constraints were shown as failing until I hit OK and then they cleared up.  Could all this be related?  NX 10 had it's share of problems, but sure seemed more stable than 12.  Thanks

 

Update:  Since the pattern kept flaking out, I deleted it.  I then deleted constraints for the component I was trying to pattern and also did the same for another component.  When I deleted constraints, several components now showed as having conflicting constraints - when NONE of them showed as having conflicting constraints before I deleted the constraints for the two components.  I don't understand....

 

Final update for the day:  I deleted 2 constaints and the at least 417 (not exxagerating) that showed as conficting were now resolved.  All this was tied back to one component that had 2 bad constraints.   This one offending component had been added earlier on and other components had been added later.  This didn't show up until I removed 2 other component and then red conflicting constaint indicators were thrown up all over the Constraint Navigator.   How is this a good thing???


Viewing all articles
Browse latest Browse all 5175

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>