In the words of SolidWorks, “Sensors monitor selected properties of parts and assemblies and alert you when values deviate from the limits you specify.”  They come in handy when creating optimization studies.  (Check out this week’s blog.)

To create a sensor, right click the “Sensors” folder in the feature manager tree.  Then, select “Add Sensor”

Next, select your sensor type.

Simulation Data: Monitors simulation results like stress and displacement

Mass Properties: Monitors things like mass, volume and surface area

Dimension: Monitors any dimension you select

Interference Detection: This option is only available for assemblies.  It will warn you if any parts (of your choosing) interfere with one another.

Proximity: This option is also only available for assemblies.  It is similar to interference detection.  It will warn you if your parts cross a line.

Motion Data: This option is only available with the motion add in turned on.  It will monitor existing result information from a motion study.

Within these options there is much to explore.  Happy hunting!

The American Heritage dictionary defines a utility as:

(yū-tĭl’ĭ-tē)
n., pl., -ties.

1. The quality or condition of being useful; usefulness:
2. A useful article or device.
3. A public utility.
1. A commodity or service, such as electricity, water, or public transportation, that is provided by a public utility.

In SolidWorks, the utilities add-in available with seats of SolidWorks Professional or Premium can be very useful indeed!

SolidWorks defines Utilities as “a set of tools that lets you examine in detail the geometry of a solid model, and make comparisons to other models”.

With everything from automated tools to simplify your models to geometry comparison between separate files; these tools can give you valuable insight into your designs and give you the information you need to be successful.

Take some time to get familiar with SolidWorks Utilities by checking out this link:  http://help.solidworks.com/2012/English/SolidWorks/swutilities/SolidWorks_Utilities.htm

Do you ever find yourself using the same feature over and over again?  Or maybe your new designs share many similar features.  Hopefully you already know you can copy features from one part to another (Ctrl+Drag between tiled document windows), but a better solution for a feature that you want to re-use over and over again is to add it to your Design Library. Here’s a couple quick tips:

Pick the feature(s) you want to re-use from your Feature Manager Tree (you can pick multiple features with your Ctrl key).  Then from the Design Library Tab, pick the Add to Library command  .

In the Property manager you can give your library feature a file name and description which will appear in a tool tip if you were to hover over the file in your library.  Hit the green check.

Click for Hi Res Image

You can further customized the Library feature part to make it more customizable by opening it up from the library folder.  You may want to consider simplifying the original model to remove features you are not re-using.

And you can use the Folders at the top of the Feature Tree in your library part to control how the features behave when inserted into a new part.

The Reference folder shows the references that you’ll be prompted for when bringing in the features.  You can Rename them hereto be more descriptive.  And the Dimension folder allows you to rename the dimensions that will be copied into your new design and you can also move them into the Location Dimensions folder if you want them to be editable on inserting the feature, or in the Internal Dimensions folder if you do not want users to be able to access them.

Always remember to test!  You can drag and drop you library feature part into a new part to test it out and make sure you get the behavior you expect…

Click for Hi Res Image

For more information on this topic, our subscription service customers can check out my recorded webinar on our Events Page.  Here’s a link:  http://symsolutions.com/events-and-webinars.html

Let’s discuss the difference between the linear solver and the dynamic solver with a case study. Take the example of an engineer slamming his head on his desk after getting poor simulation results from his linear solver.

In scenario #1, the engineer lightly places his head on his desk then proceeds to slowly press down with his body weight. The force value, F, represents the maximum amount of force he can transmit through his neck.

In scenario #2, the engineers head starts a distance of 2 feet from his desk. The engineer proceeds to accelerate his head towards his desk with the aforementioned force value, F. After he comes into contact with the desk, his neck continues to transmit the force until his head comes to a complete rest against the surface.

Now, in both scenarios, the engineer’s neck transmits the same amount of force, F. However, the second scenario will produce higher levels of cranial stress at specific instances in time. The higher stress is related to momentum. The engineer recognizes this and proceeds with scenario #2 until the desired level of masochistic indulgence is achieved.

If we were to simulate these events, design scenario #1 could be adequately achieved with either the static solver or the dynamic solver and the results would be the same. However, if we were to run scenario #2 with a static solver, we would get the same result as we would with scenario #1. Obviously, the static solver has limitations.

The linear solver only sees the last moment in time; when things are at rest. Thus, we have two data points, the beginning and the end.

On the other hand, the dynamic solver is aware of the time in-between the beginning and the end. As a result, we are left with a much more complete picture.

For a moment, let’s sidestep the slamming head on desk approach, as this practice is no longer necessary. Let’s use the example of a cantilever beam with a weight of one hundred pounds suspended from the end.

For the linear study, let’s consider the case of loading the end very slowly. The results of this simulation are shown below.
The maximum displacement is 58 mm.

For the dynamic study, let’s consider that the weight will take .05 seconds to reach its maximum value of 100 pounds and will then level out. The maximum displacement results of this simulation are shown below.
The maximum displacement is 93 mm. This is an enormous jump from 58mm. Obviously, we’d want to study the dynamic simulation results over the static.

Does SolidWorks sometime feel like it’s working at a turtle’s pace? The problem might stem from being connected to a network!

Working on a network is great, and in today’s age it’s basically required. Unplugging from the network could solve a lot of issues, but usually isn’t feasible. The problem is that so much stuff is looking to the network it can sometimes slow down SolidWorks. There can be a ton of reasons for this, some can be fixed! Here’ are a few tips to make your performance a better while working with SolidWorks.

• Don’t work over the network!!! One of the biggest slowdowns you can cause in SolidWorks is by trying to work with files that are located on the network. If the files aren’t on your local computer, every time you open them, temp version of them are made in the directory they’re opened in. Every change you make has to get written to those. Every time you save the main files get written to. All of that going over the network is going to slow down SolidWorks. Copy files locally to avoid those issues.
• Backup/Auto-Recover: You should not have these locations be on the network. If these locations aren’t local, SW will again be constantly working and writing over the network and slow down. The backup option to put the backups in the same place as the original file can double the issue if you’re working on files over the network as well.
• SolidWorks Search: The SW Search is useful, but if you don’t use it, turn it off. If you do use it, make sure to set the indexing to “only when the computer is idle.”
• News Feed: Turn off the option in the general area of the options to “Show latest news feeds…” It may be minor, but it’s one more thing to slow down SW.
• Stop Streaming: Turn off things like streaming audio, unneeded web pages, and any other non-essential programs. The less trying to fight for resources the better.
• Stop the CPU War: Everything you’re running on a computer is constantly fighting for you CPU. When you’re on the network, even more things are fighting for it. If possible, dedicate a CPU core to SolidWorks. Windows defaults everything to the first core, once that’s full, it’ll start using other cores. Most of SW can only use one core, so the more it’s trying to fight with the slower it will run. If you can dedicate a core, it will reduce the chances of a slow down.