assembly "configuration changes"

[dgiy]

sw2003 sp3.1

I have a part that has a shaft on it.
In the part file I created two different configurations for different shaft lengths.
I edited the shaft definition and specified which length to apply to which configuration. Works fine.

Now I inserted the part into an assembly and I want to have this same selection possible for the shaft in the assembly.
But I can't seem to get it to work.
I can create an additional configuration, but when I go to the part and try to associate different shaft lengths with different configurations SW won't let me deselect the default configuration.

I get an error dialog that says
"Cannot deselect the active configuration for this operation."

Any suggestions on how to get this shaft length to change in the assembly with configurations. It worked when I would manually changed the part file but it would be easier to just have the assembly open.

Thanks,
DG

 

[TateJ]

I usually set up assembly configurations in a design table.
It's easier for me to organize/contol the part config's if I can see them in a "spreadsheet.
The column header should be something like: $CONFIGURATION@PART<INSTANCE>
If this don't work, I'll correct myself tommorrow...

Read my profile & make me an offer... now!
tatejATusfilter.com[/u]​

 

[TheTick]

From the assembly, right-click the shaft component in the feature manager tree and select &quot;Component Properties&quot;. Here, you can control which configuration of a component is visible. If your assembly has multiple configurations, you will be able to select which component configuration goes to which assembly configuration.

Good and evil: wrap them up and disguise it as people.

 

[dgiy]

OK Tick it worked great.

Now...

If I include this assembly as a sub-assembly into a larger assembly how can I maintain control of the two different configurations? It looks like I can't select subassembly properties like I could for the part.

Thanks again,
DG

 

[Standing]

DG,
I am sure you can. You will have to create a configuration for the sub-assembly.
Let us know what happens.

Bradley

 

[dgiy]

Oh yea,

I forgot to mention, If I am in the larger assembly and I select the component properties, I can see my configurations in the component property manager &quot;referenced configuration&quot; box but it is grayed out with no way I can see to &quot;un-grey&quot; it.

Thanks,
DG

 

[JNR]

Well, this is something we do a lot of. We have some parts/subassemblies with permananetly different configurations and some where we use configurations to show the various positions of moveable mechanisms. Here's the rub - and it is logical when you think about it. Let's say you have:

Part1, configs A & B
Subassy 2 configs C & D
Assy 3 configs E & F

3E contains 2C which contains 1A
3F contains 2D which contains 1B

That about what you have in principle?

OK, now if you have Subassy 2 open you can change the config of Part1 - just like TheTick showed you.

BUT if you have Assy 3 open you can't change the config of Part 1 - you can only go one level at a time.

So you have to open Subassembly 2 and do it there first. Then select the appropriate one of it's configs at the higher level.

I just re-read that and its as clear as mud.... just put it this way. You can only select the configuration of a part/&quot;sub&quot;assy in any assembly if it is on that assembly's single level BOM.

When you think about it, it is logical because you would be trying to edit sub 2 without it opening it.

3/4 of all the Spam produced goes to Hawaii - shame that's not true of SPAM also.......

 

[automationbabe]

JNR made sense. Depending on the size of the assembly, I'd watch how many configurations are created though. We noticed that the more configs, as nice as they are, tend to bog down the performance.

Could also check that &quot;Named Configuration&quot; is selected instead of &quot;In-Use&quot; in the Component Properties dialog box. That switch seems to get me at times.

 

[dgiy]

Thanks JNR that helped.

DG