Macros are small pieces of software that can do work for you.
They can create parts that you have to recreate often, or apply changes to many drawings at once. You can even make them work with Excel. Basically anything is possible.
Here I’ll go into my adventures with SolidWorks macros to share what I’ve learned.
SolidWorks equations are underappreciated.
By using equations, you can make your model more adaptive to changes. You can make it smarter.
Furthermore, you can use equations to evaluate values or mathematical functions, suppress features or use them in custom properties. Even nested IF statements are a possibility.
Parametric 3D CAD makes the life of the engineer so much better.
It doesn’t necessarily make it easier, nor does the first iteration of a design go much faster. But revisions will happen. And when they do, parametric designs will certainly be updated significantly quicker than 2D AutoCAD designs or drawings by hand.
But sometimes you just want to do something that was a piece of cake when drawn by hand. Adding a few milliliters of oil to the bill of materials (BOM) of a gearbox assembly is such a matter.
It can be done however. I’ll show you how to do it manually and by using the API.
Continue reading “Customizing the bill of materials quantity”
Did you ever have to do some extremely boring task over and over again in SolidWorks?
Jobs like creating 2D drawings of hundreds of sheet metal parts. Or assignments like exporting all fifty configurations of a part separately.
Oh by the way, could you also write down the mass of each configuration?
Continue reading “How to get started with SolidWorks macros”
Macros can be great for replacing repetitive manual labor (usually in the form of mindless clicking) with robotized micro-tasks. If you can think of a task that you have to do often enough and if it can be standardized, you can probably automate it.
You can even add buttons to your SolidWorks toolbar. But sometimes they just stop working. I get a help request for this every week or so. Luckily the solution is very simple.
This is some weird behavoir of SolidWorks that I have come to understand and accept over time. It might not even be SolidWorks’s fault, but that’s where I have encountered it and where it has bugged me so many times.
You may notice this non-saving behavior when you are working on a macro in Visual Basic for Applications, or VBA for short. You will click on save and you assume the macro has been stored for all eternity. Then you close the editor and you get the following pop-up:
