Hi there,
I have a top level assembly in which I inserted the same sub-assembly twice. I have different configurations in the sub-assembly. I would like to use the configuration #1 for the first sub-assembly and the configuration #2 for the second sub-assembly. My problem is that whenever I assigned a configuration to one of them, it automatically changes the other subassembly.
Any idea how to fix this ?
Thank you
I don't understand what you are saying. I don't need to suppress any parts.... I want 2 different configurations of the same sub-assembly within the same top level assembly. The configurations are already created and correct. My problem is that I can't assign 2 different config because whenever i assign one to the subassemly, it automatically changes the other one....
Having a Sub-Assembly with (2) Two configurations and not suppressing any part in the feature tree makes them the same, or inserting parts into the Sub-Assembly that has (2) Two configurations and the features are not suppressed between the two configurations they would end up being the same part, therefore no difference. So there needs to be a difference either on the Sub-Assembly level or the Part Level..
I'm not sure exactly how you have your subassy setup as I do what you trying to do all the time. Make sure you have different configurations of your subassy and they each properly reference the different configurations of the part in question. Then, in the top-level assy make sure to select which configuration of the subassy you want used in each position.
BTW, you can also make each instance of the subs independently flexible/rigid.
Here is an example of what I am saying:
I just RMB on the subassy in the top level and selected the Component Porperties (the far right icon in the dialog box I get) and then choose which configuration to use for that instance.
Why do you make the sub assy flexible ?
In my case I needed to. I was just pointing out that the two instances of a subassy have complete independence from each other, including the option to make one flexible.
So, have you been able to get what you wanted?
Dennis,
it appeared that you understood the problem but I don't. Maybe it's my english skills or something else, but I find no reason for SW to behave like this and from what I understood, it sounded like a bug to me. Could you please explain to me what was the problem and why making the ASM flexible solved it?
Regards,
GF
The problem was how to get the top level assembly to properly reference a subassy with different configurations of a part. I only showed the one subassy as flexible to show that their settings are independent of each other, not to show that flexible was the solution in this case.
Ok... Aparently I got the problem right, so it was either a bug or some miss config by Thierry.
In the assembly feature tree, click on the subassy, then click on the config in the dropdown.
Do this on each subassy.
Thierry,
As you can see from the image below I have no issues inserting the same assembly twice into an assembly & having each set to a different configuration.
Are you sure that your sub-assembly actually changes if you open the sub-assembly & switch configurations?
I will try to send a video of my problem. What you did is exactly what I would like to do
Are you sure? The base parts are different. One is shown as lightweight and the other not. You will be "missing" features.
Ryan,
The image is of my test assembly I created to check Thierry's issue. The "Lightweight" is a configuration name, not a SolidWorks model state. The second configuration has had some material removed to reduce weight...hence...Lightweight
Sorry for confusion.
Perhaps you have made a derived configuration...
Scott, even a derived configuration is treated independently so that doesn't matter with regard to the OP's problem.
I would open the problematic subassembly and test if it really has two different and independent configurations as requited.
It sounds like you need to open the sub assembly and make a few corrections - in the configurations tab go from one configuration to the other and see what's changing, apparently you need to suppress a part or parts in one configuration and a different one in the other etc..