Derived Configuration Problems
Derived Configuration Problems
(OP)
In my assembly I have a configuration "Default" from which I created 2 derived configurations, "Config 1" and "Config 2." I am having various problems with features and functions since creating these.
1. I make an extrude-cut through my model in one of the derived configurations. But it shows up in the other derived config and in the parent configuration.
2. I suppress that same extrude-cut in the configuration in which I created it, but it is unsuppressed in the other 2.
3. Then, making sure the extrude-cut shows in all configs first, I suppress it in the parent configuration. It is unsuppressed in the 2 children.
4. In the "Default" (parent) configuration, I select the 2 major parts of the assembly (either from the feature manager design tree or directly in the model) and change the transparency of them both. In each of the children configurations, one part updates accordingly but the other is not affected.
At one point, I could have sworn that the cut-extrude was shown as suppressed in the feature manager tree of one of the configs, but showed up in the model. However, I do not have the direct circumstances around that and can't seem to repeat it.
I don't understand these issues. I read all I could find on derived configurations and tweaked all the settings I could find but nothing seems to work. I was under the impression that having a "parent-child" relationship using configurations meant that any changes to the original config would carry over to the derived configurations, whereas if those changes were modified, or if new changes, additions, or subtractions were made to the derived configurations, these would not appear in the original. Am I not selecting things in the right sequence? Maybe I need to have specific settings selected amongst the properties of the parts/views/configs, ect. in order for it to work properly? Please help!
1. I make an extrude-cut through my model in one of the derived configurations. But it shows up in the other derived config and in the parent configuration.
2. I suppress that same extrude-cut in the configuration in which I created it, but it is unsuppressed in the other 2.
3. Then, making sure the extrude-cut shows in all configs first, I suppress it in the parent configuration. It is unsuppressed in the 2 children.
4. In the "Default" (parent) configuration, I select the 2 major parts of the assembly (either from the feature manager design tree or directly in the model) and change the transparency of them both. In each of the children configurations, one part updates accordingly but the other is not affected.
At one point, I could have sworn that the cut-extrude was shown as suppressed in the feature manager tree of one of the configs, but showed up in the model. However, I do not have the direct circumstances around that and can't seem to repeat it.
I don't understand these issues. I read all I could find on derived configurations and tweaked all the settings I could find but nothing seems to work. I was under the impression that having a "parent-child" relationship using configurations meant that any changes to the original config would carry over to the derived configurations, whereas if those changes were modified, or if new changes, additions, or subtractions were made to the derived configurations, these would not appear in the original. Am I not selecting things in the right sequence? Maybe I need to have specific settings selected amongst the properties of the parts/views/configs, ect. in order for it to work properly? Please help!






RE: Derived Configuration Problems
RE: Derived Configuration Problems
Regards,
Scott Baugh, CSWP
http://www.3dvisiontech.com
http://www.scottjbaugh.com
If you are in the SW Forum Check out the FAQ section
To make the Best of Eng-Tips Forums FAQ731-376
RE: Derived Configuration Problems
I'm also still having the same problem with changing the transparency at the parent level. Still, only one part that I select (of the two) changes in the 2 child configs.
Originally, I had added all new configurations. However, this is a large assembly and it is still in mid-design. A lot of things will probably change and I'd prefer to make changes that affect all configurations from the parent config. With add new configs, I had to go through them all one at a time to make the same exact changes and it was too time consuming. If SW offers derived configs I'd like to take advantage of it.
RE: Derived Configuration Problems
This one sounds as simple as changing it from 'as per parent config' to 'this config'.
Design tables are a good way to control this.
The best way for me personally has been to do away with derived configs and just put that little bit extra work in.
Parts and assemblies are more robust and less mistakes are made when changing features etc.
regards,
Jim
NZ
RE: Derived Configuration Problems
Have you checked the dimension dialog boxes in your sketches within those configurations to see if changes are set for "this configuration" or "all configurations" ?
Similiar settings appear in the feature dialog boxes for extrusions, cuts and revolves.
It's very easy to miss this, as I did in a recent job involving a pipe support device which had multiple configurations and the same problems with features as you are having.
Best Regards
Adrian Dunevein
AAA Drafting Services
www.aaadrafting.com