Continue to Site

Eng-Tips is the largest engineering community on the Internet

Intelligent Work Forums for Engineering Professionals

  • Congratulations IDS on being selected by the Eng-Tips community for having the most helpful posts in the forums last week. Way to Go!

Configuration for "simplified"

Status
Not open for further replies.

Uka

Mechanical
Dec 15, 2003
46
Well... I created a part and added fillet after all other features are created. So all fillets are bottom of the feature manager tree.
And then I added a configuration, 'simplified', that doesn't have fillet and suppressed all fillet.
For some reason, when I suppress fillets for "simplified" config., features that are above fillets in the feature manager tree give me errors.
I just don't understand why this is happening because fillets are added at the end...
Does anybody have an idea?
 
Replies continue below

Recommended for you

Have you tried Diagnosing this yourself?

Unsuppress all the features and rollback each feature till you find the feature that is causing the failure.

One thing you might have is a problem from the beginning. Do a Ctrl-Q with everything unsuppressed. If it fails at the top it cause all the other features to follow.

A rebuild been each feature is not enough when building a part. You need to do a Crtl-Q every once in a while in the process of building a model. A Ctrl-Q goes to the top and rebuilds each sketch and feature it is associated too. You might have a problem at the top of your Tree and don't even know it. Then again you might not. If that's the case then you need to find the fillet or the features causing the issue and see if you can find a way around the problem.

Regards,

Scott Baugh, CSWP [borg2]
CSWP.jpg

faq731-376
 
I would like to add something to Scott's comments. Sounds like you are fairly new to SW and you might miss something here. Note Scott is telling you how to FIND the error, but don't try to FIX the errors in the same order. Feature errors are parent-child dependent, so you work on FIXING the errors highest in the feature tree first. So as Scott says, rollback one at a time until you do not get anymore errors (you found the root cause). Then look at the last error you found - which will be the highest or first error chronologically in the tree. Most often once you debug and fix this, the rest pretty much sort themselves out (at least most of them) because that was the parent causing the the children to fail. If they don't, and you still have residual errors, you work DOWN the tree when fixing. Also as you roll back one at a time as Scott mentioned, doing a quick "What's Wrong" sometimes can be very helpful. (I only said "sometimes"! See below ***).

BTW: For Mate errors you work from the bottom up, because they are not parent-child and it is the LAST one added that causes the problems.

*** It's like the old joke... small plane - lost in fog near Seattle - gap in fog - pilot sees guy at open office window - - shouts "Where am I?" - answer "In an airplane." - pilot makes a 270 left - breaks out of the fog right on the approach path and excutes a perfect landing - passenger asks how - pilot says - "I asked for specific help - he gave a perfectly accurate but totally worthless answer so I knew it was the Microsoft office building 5 miles due north of the runway!"

John Richards Sr. Mech. Engr.
Rockwell Collins Flight Dynamics

There are only 10 types of people in the world - those who understand binary and those who don't.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor