I now have a lot of families of homemade rooms with lots of configurations that work well. A library^^ I now have assembly templates with ready-to-use configurations to standardize and facilitate the work.
My problem is that every time I integrate a part from my library" into a set with several configurations, the configuration of the part is basically in " this configuration only " mode (see image) which is a source of error and waste of time if you don't pay attention to it right away.
Can we set the configs of a part so that when it is inserted into a set its configuration is in " All configurations " mode?
Unless I'm mistaken, I think it's not possible to block the configuration. Indeed I think it's a bug, because also I encounter this problem. I would also be in favour of a solution on this subject. @+. AR.
Regarding the configurations of the destination assembly: are they design variants (different "physical products" to use 3DX vocabulary), or representation variants (different subassembly positions)?
If I ask the question, it is because in the case of representation variants, it is recommended to work with derived configurations. And with derived configurations, the problem of setting the component's config to "This configuration" or "All configurations" no longer arises, because derived configurations inherit the "additions" and "modifications" made to the parent configuration.
In my case, but I think generally of machine design, it's for subset positions. But for me, the design or position variants require the same "function" in the parent assembly, right?
To put it simply, I have for example an encoder that has its axial connection, or on the side. We can take the idea of screws that have a certain size too. The configurations of these parts (part family or difference in design and properties at the same time) have 99% of the time no reason to change in size (for screws) at the moment when a cylinder in the machine is in the retracted or extended position (to speak only of simple configuration) But when I have placed the bearings, screws, nuts, encoders, bearings (all managed by families, so configs) we have to put everything back in "all the configs" while a certain logic would require that we choose the particular cases by config of the whole and not the other way around when creating configurations Often, apart from a few constraints, nothing changes.
Hoping to have been clear^^
For having done the test, same with a derived config. Everything goes to "this config" when the derived config is created.
Hello I hadn't paid attention to it until then but indeed that's the behavior on the 2022 (I don't remember for the 2021). Probably a bright idea from one of SW's developers. I didn't see any settings or fixes for this behavior in the different SPs. Probably the same behavior in 2023 and 2024.
It's also the behavior in 2020 and 2018 so it seems to me upstream I don't remember too much! And this is not one of the modifiable options of a configuration in an assembly:
A workaround is to create virtual subassemblies for subassemblies that remain together. As each sub-assembly has only one configuration, you no longer have the problem to manage for the general assembly (except for a few parts and sub-assemblies that move).
For the remaining parts/sub-assemblies, you select them (you can select more than one) and click on ' configure component ' and you get this nice table: Note the box I circled in red which allows you to quickly see all the configs that change
Hello Indeed, it is a possibility but it remains a troubleshooting solution. I'd love an option that puts it in a hard place. Because it's "funny". A part to which a confi is added does not see all its dimensions, or functions, change to "this configuration". The philosophy should be the same... it seems to me.
I didn't understand the initial request... We agree, on the image above:
Selecting the configuration of the assembly component.
Selecting the configurations in the assembly in which the component configuration should be applied.
In answer to my question about assembly configurations
Are they design variants (different "physical products" to use 3DX terminology), or representation variants (different positions of subsets)?
You answer:
[…] it's for subset positions.
We are therefore in the case of configurations for " representation ". I'm also in machine building, and regularly my colleagues ask me " Should I make a config? a derived config? or a display state? »
Let's take a simple case:
A machine, without options (design variant), which we want to represent in the different states of its operating kinematics.
This machine only needs a first-level configuration (i.e. the " Default " configuration). All other configurations to be created to represent subsets in other positions will be configurations derived from the top-level " Default " configuration.
Thus, when you insert a bearing or screw with several first-level configurations (because they are size variants), you insert them into the assembly with an active " Default " first-level configuration, and you don't need to worry about selection 2, because the configuration selected for the component will be automatically applied to all the configurations derived from the assembly. A little video for example...
We can work like this indeed but it is true that the configuration could have been done from the other way around. By default, when inserting a component, we apply to all the configurations, then the user selects what he wants specifically for each configuration.
in my case, I have a set with 3 positions so 3 first level configs to make them appear on a single view of MEP. So no derivative or display state. By the way, I never use derived configs. Useful?? Otherwise I insert my screw in the "default" config, at the time indeed, no worries. I tinker with my configs, and op, I change a length of screws, and well no, my screw is in "this config". That's why for a long time I've been doing one or more configs at the very end of the project. Because the work is exponential and so is the risk of errors in nomenclature. As soon as there is a configuration, you have to be 200% vigilant. Unfortunately, during the assembly there are often small modifications, and once the configs are done,... Careful! An infallible method, put the different constraints in a folder per config. Delete config. Rebuild everything, and recreate the configs for the MEP.
Hello I took a look a little more in-depth at the derived configs. I don't have any interesting use at my level for them (Creation of simple parts with no derivatives or very little) and after testing, my families of parts suffer from the same config problem.
Thank you for the time spent finding a solution. At least, to put it simply. As soon as I have several configs, none of my parts or sets stay in "all configs" mode. No matter how much I turn the problem around, a config remains frozen on the world "this config".
Clicking on "all configs" only works once in fact!
