i haven't had use of this before, but not seeing how to do it or even if it is possible.
can we not control the configuration of a component in an assembly with an assembly equation?
Other than cheating with VBA, equations can only suppress/unsuppress or return numerical values. They can't change configs.
So, you can have multiple instances of the same comp in your model with different configs and let your equations suppress/unsuppress, or you can control the config by design table. However, design table is only evaluated when you update the table. It doesn't evaluate with every rebuild.
Controlling the component(s) configuration by equation is possible for SolidWorks files!
At least 15 years ago, it was used in my previous company (elevator & lefting system) for customized production.
you wouldn't happen to know the syntax to make it work, would you? - i can find no reference to it in the help...
1. Controlling the component(s) configuration by equation is possible for SolidWorks files;
2. Using programs to handle the equation(s).
Yes you can add any equation you want to control the configuration of a component, using an excel based design table. Considering we don't know exactly what you are trying to achieve we can't exactly give you the equation to make it work.
But in B3 you could have something like =IF(A3="Default","test_part_A","test_part_B")
It would be nice if you give us a working screenshot for a real sample (if you have some)
You should be able to use a design table to change the configuration. That would be where I would try to add some logic to it.
create the design table in the main assembly and there you can control the different configurations of the parts in the assembly
yeah - I am VERY familiar with design tables . trying to avoid having to rely on users remembering to open it up to drive the changes.
which means the SW equation option is off the table - still have a few others to explore and present as options.
Jeremiah Feist wrote: yeah - I am VERY familiar with design tables . trying to avoid having to rely on users remembering to open it up to drive the changes.
Jeremiah Feist wrote:
In the past I've used macros later on down the road to update design tables. It was basically guaranteed that the user would use the BOM sorting and exporting macros we had, so I put the code to update all design tables in one of those. I forget which one...
Retrieving data ...