After really thinking about this post, getting some feedback and losing a slap fight with an angry camel trader, I’ve decided to totally revamp the former SolidWorks Success post and put them in all together.
It lacks the detail I originally determined I wanted to put into the points, but the angst about not having the list all together was more than I and some others could bear. Fear not, it’s all here, in one short post, ready to be devoured.
About this list
Many would say there’s A LOT more you need to know about SolidWorks in order to use it and be successful using it. They would be partly right… they would also be partly wrong.
When using SolidWorks, there’s a few key components you need to know in order to build the rest. If you don’t have them, knowing anything else can actually make you a weaker user. I’ve seen it, it’s not pretty, especially when they are trying to teach others the ‘right way to do things’.
I’ll touch on the first two again to get the scope of everything. Hopefully this will be a good checklist, go-by or paper wad to use in your quest for mastering SolidWorks. Here we go…
Create Your Model from the Basics
When you start to model a part dissect it. When you look at it or imagine it, remove the fancy stuff, the fillets, the chamfers, the holes, etc. Turn it into the basics, looking for symmetry and commonality between features.
Use Relations to Control Your Sketches
Control your sketches by adding relations first. So are added automatically. Before dimensioning, create relations. Use symmetrical relation where possible, when it matches your vision of how the model will change. Always fully-define sketches
Plan out your Assembly Construction
There’s a few things that should always be done when creating assemblies. Build assemblies on the origin using the existing planes to define any symmetry. Add parts as they would be assembled and simplify assemblies with configurations.
Understand how Top-Down Modeling Works
Building parts off other parts is easy. Doing it right isn’t so easy. Start with building off of a single part (or sketch) define all your other parts from it. This will give you a good understanding to how design changes affect your other parts.
Add Properties and Weight to Your Parts
Your model can have descriptions and mass. This helps with drawings and cost savings. If it’s an aluminum part, add the density in Tools, Options, DOcument Properties. Add the property for mass, descriptions and more in File, Properties.
Fix Problems the Smart Way
You’ll over-define sketches and create conflicts. Don’t delete anything. Start at the top of the FeatureMananger tree and see ‘What’s Wrong’. Suppress Mates and relations with errors first. Deleting geometry and parts can just create more work.
Create Clear and Amazing Drawings
Take a board drafting class. Really. You’ll understand space and permanence much better. Don’t create Isometric and Section views just because you can. Try to define each stages of manufacturing and/or assembly in different view.
When to Use Surfacing
Learn to use it, even for machine design. Use surface to define mid-planes. Trim Excess material with a zero offset surface. Use surfaces as an end condition for extrusions or cuts. Use them to set up complicated seams in sheet metal parts.
Where to Save Your Files
Not on your desktop. Even if you’re a one-man operation. Use a separate drive off your work computer. Use a Network Attached Storage (NAS) if at home. Use a folder structure and naming. Always Backup.
How to Re-use Models
You can use File, Pack and Go to copy entire assemblies and rename them. Re-use starts with building parts for re-use. Whenever creating anything, think about how it could be reused. This goes a long way to designing for change.
Ok, so whatcha think? Straight and to the point? Lacking? It’s basics to some maybe, but they’re also the most important areas for anybody that uses SolidWorks to gain a comprehensive understand of. Imagine having a potential employee that was aware of all of these? Yeah, hired.
I’m open to what you think should be added. More? Do anyof these not matter so much?