Combining Bottom-Up and Top-Down Design in Solidworks

Hello everyone,

Is it possible to properly reconcile bottom-up and top-down design in SW.

If I take an example:

I have an A1 assembly in which I have defined several global variables used to drive my constructions in the parts that make up A1. So far, so good, it's top-down design.

When I insert A1 into another Assembly A0 and I go to edit my part P1, I have in the variable panel the famous exclamation mark telling me that the relationship is defined out of context and the message informing me of a syntax error when I leave the panel. It's really not clean despite the fact that it seems to work anyway.

It's doable, but avoid mixing the genres too much.

For me, the top-down assembly lends itself well to a first draft, a draft, a quick study that you then have to do again as a top-down model as soon as the solution is ok.

3 Likes

Totally agree with @alain. ERP.

In addition, Solidworks has difficulty managing as soon as there are external references. And if it happens to plant in the middle, you will very quickly cry out for help to find what has been lost or not.

But for a study no problem as long as you back up regularly.

Cdt

Unfortunately, this is the answer I feared. As a former CATIA user, I'm a little flabbergasted to see this (I know the price is not the same). But when I see things like this, I hallucinate:

The passage of a parameter between an assembly and its component (virtual at that) should be handled cleanly and we should not get this kind of message when opening the piece in a new window.

So if I understand correctly, the only viable way to share settings between files in solidworks is to link them to a .txt file?