Mating methods within in-context assemblies

This relates to top-down, fully parametric models where all parts are dependent on those around them - I have a question/suggestion, but it might help to put it in context first.

I have increasingly been moving away from the common method of having one fixed part, and mating all other parts to that part or each other. By definition, parts created in context of an assembly have their positioin and geometry pre-determined... adding mates afterwards can be problematic (as they need to match exactly the geometry, which can change down the line). This mating method is clearly a necessity for bottom-up assemblies, but seems a bit daft for top down assemblies.

My approach recently has been to mate ALL parts (including the first one) by their reference geometry to the ref geometry of the assembly. Just 3 mates per part, top to top, right to right, front to front. With this method, no matter what changes you make in the future, the parts will ALWAYS be defined, and the mates will NEVER bug.

I'm sure this is a common way of doing things, allthough strangely i havn't been able to find a thread confirming this.

My question is this:

Could I, by the same reasoning, simply 'fix' every part. Although the parts are supposedly fixed in space, they aren't in so far as their positioning is determined by sketches defined by neighbouring parts. ie, they will move according when changes are made to the model.

By doing one of these 2 methods, you are effectively removing the whole 'mate' issue entirely, and thereby massively reducing the error count. It also means that all parts are orientated in the same way. There are a few issues i can think of, but not many. I would be interested to hear people's opinions of this way of doing things. I feel like either i'm missing a very obvious disadvantage, or this is an extremely common approach but isn't documented anywhere!

Thanks in advance

SolidworksAssemblies
Answers 3
DD
DD 2011-02-11 Best Answer

With your method, there is no reason not to fix components instead of mating them to the origin. (BTW, if you drop a component on the assembly's origin in the graphic view, it will be placed at the origin and fixed. Or, if you select a component to insert and hit the OK check without selecting a position in the graphics view, you get the same result.)

You can fix everything at the assembly origin. It may work well for what you design. I'm not in favor of it. You lose the advantages of having the origin and default planes of the components in a convenient location. If you need to use a component again in a new position, you have to use mates.

I tend to blend your method for some components with mating to robust features like reference planes, axes, layout sketches, etc. Faces, edges and vertices can be robust, if they're in a part of the model that is unlikely to change. I also use skeleton components full of layout sketches, planes, etc. for mating and in-context relations. This is very robust. If you combine the use of skeleton components with subassemblies, you can have robust, in-context models that can still take advantage of assembly motion. Sometimes, it does make more sense to just fix a part at the origin.

Using mates without a methodical strategy based on robust features is a recipe for disaster. Oh, the messes I made in my youth.

SF
SF 2011-02-11

Hi Tom,

  The methodology you lay out effectively eliminates mates from the rebuild process.  The advantage, as you point out, is that this elminates the errors associated with mates.  There are two main disadvantages, one obvious and one not-so-obvious:

The obvious one is that motion doesn't work.  If you want to move things around realistically, you'll need to create a new mate system.  This is easily done using a Motion Study, though many users choose to make a different SLDASM for this purpose.  But it is more work.  Now, if you make welded frames or buildings or other things that don't move (or if you don't care about motion) then this isn't a big deal for you.

The disadvantage that might not be so obvious is that in addition to controlling the shape/size of your part by rebuilding (the only way to do so), you'd also be controlling the position of your components this way.  That means that anytime a part needed to simply move (without changing), SolidWorks would build it from scratch in its new location -- roughly equiquivalent to bringing your laptop home by throwing the one in the office away and building a new one at home.  (Can't say I haven't been tempted to do that myself :-) )

Some issues with that are:

  • It's pretty inefficent. It won't matter if you have simple parts and/or a fast computer, but with complex parts, or many parts, this gets really slow.
  • If you use revision control, all of this rebuilding will require parts to be up-revved even when their shape didn't actually change at all.  Whereas with a mate the entire part just moves, but doesn't change shape so it doesn't rebuild. 
  • As you've probably already figured out, the origin of your parts is now floating (relative to the part body -- I understand that the origin will be fixed or mated in the assy).  You can't reference the origin or default three refplanes, and large changes in location can make your parts appear to move around on your drawings. 

One thing you might think you'll avoid, but won't, is any errors caused by missing geometry.  Whether you mate to a face or make a geometry reference to it, if the face goes away, SW is going to complain.  Part references aren't any less susceptible to this than mates.

I don't mean any of the above to dissuade you from using the method you're considering.  Like any of the other methods (top-down, bottom-up, layout sketch, etc.), it has pros and cons, and you're the best judge of what works for your specific situation.  Just be aware of the ramifications. :-)

Thanks,

Mark

P.S.  I'm curious what kinds of mate errors you're experiencing.  Geometry going away?  Overconstrained issues?  Parts flipping?

SF
SF 2011-02-14

Thanks for your input.... its true, in our case there is no motion, and compared to some applications our use of solidworks is relatively simple (furniture/product design, numerous configurations but low number of parts).

The main issue we have, which you pointed out, is that the ref planes become useless... many of our parts are symetrical, but if the ref planes are miles away you need to hang new planes off stable geometry. And yes, there have been drawings views shooting off page as you mention.

However.. these issues are manageble and infrequent... and compared to the benefits of avoiding conflicting mates (particularly when there are individuals with varying levels of SW ability working on the same models), it seems to work for us.

As for which kind of mates we have issues with... well, none if the model is properly constructed, but when trying to implement a 'system' for building stable models, which works for everyone most of the time, this approach is considerable less messy and problems are much easier to sort out. And requires much less training for people to get up to speed. Particularly when working in a design environment where you don't necessarily know what something will look like until its finished... we all have good intentions of rebuilding a model from scratch once the design has been finalised, but in reality this rarely happens.

I agree with previous posts in that the SW help menu needs to give more examples of different methods for different uses. Working them all out for yourself is a long process, and the quality of the software is only as good as peoples ablility to use it.