Archive for January, 2008

Choice of Pressure Boundary Condition in FloWorks

Wednesday, January 30th, 2008

At SolidWorks World 2008, Seth and I had the privilege of getting into a discussion with Bill Dziedzic, FloWorks Technical Specialist at SolidWorks Corp. and Arvind Krishnan, Product manager of FloWorks, about the correct usage of the pressure boundary condition in COSMOS FloWorks. It is to be kept in mind that FloWorks gives a user three choices when assigning a pressure boundary condition – static pressure, total pressure or environmental pressure.

The formal definitions of Static and Total Pressure are as follows:

Static pressure is the pressure indicated by a measuring device moving with the flow or by a device that introduces no velocity change to the flow. The usual method for measuring static pressure in a flow along a wall is to drill a small hole normal to the surface of the wall and connect the opening to a manometer or pressure gage. In the region of the flow away from the wall, static pressure can be measured by introducing a probe, which in effect creates a wall.

Total pressure is the pressure measured by bringing the flow to rest isentropically (without loss). A device for measuring total pressure is the Pitot tube, an open-ended tube facing directly into the flow, where the kinetic energy of the fluid is converted into potential energy.

Bernoulli’s equation states that Total Pressure = Static Pressure + Dynamic Pressure.

CHOOSING THE RIGHT BOUNDARY CONDITION

The decision to select Static or Total Pressure should be based off real testing procedures (whether the pressure at the outlet is measured by a manometer, or a pitot tube arrangement). In the event that one is unsure, it is always a good idea to pick the Environmental Pressure condition. This ensures that any potential reversals in fluid flow (like vortices across a pressure opening) are accounted for.

NOTE 1: If, during the calculation, a vortex crosses an opening with the Environment pressure condition specified, the pressure will be considered as the total pressure at the part of opening through which the flow enters the model, and as the static pressure at the part of the opening through which the flow leaves the model.

NOTE 2: It is important to remember that FloWorks uses Absolute Pressure values. Hence, 2psig should be specified as 16.69 psi in absolute terms (2 + 14.69psi atmospheric).

Vikram Vedantham

Vikram Vedantham
CAE Technical Specialist
3DVision Technologies

The Best SolidWorks World Technical Training Session Ever

Friday, January 25th, 2008

What do you get when you take the best two SolidWorks World presenters and put them in the same room? Simply the best SolidWorks World Technical Training session ever!

Ed Eaton of the Dimonte Group is an industrial designer who has been doing his “Curvy Stuff” presentations at SolidWorks World for years. Even though I have hardly ever designed curvy stuff in SolidWorks I have never missed one of his presentations. Ed’s understanding of how SolidWorks “thinks” always fascinates me.

Phil Sluder of TriAxial Design is a mechanical engineer who has given a presentation at SolidWorks World every year. I have to admit I have missed a few of them but the ones I have attended I have left with pages of notes -the guy knows how get the most out of the SolidWorks software.

The last day of SolidWorks World was capped off by Ed and Phil teaming up putting together the presentation titled: “Sluder and Eaton Take on your SolidWorks Problems”. I liked the concept, they each took several real world modeling questions and answered how they would solve them. Since they both have drastically different backgrounds I was expecting some rather heated debates and two unique ways to solve the problems.

The debates never happened and their solutions were rather similar -however the educational and entertainment value was just what I hoped for!

They started out with a part they found in a blog posting by Elise Moss. She found a part that has many [patterned] holes in it. The part did not look like it was very complex but it had terrible rebuild times. They challenged each other to improve rebuild performance. First both noticed that turning off the option: “verification on rebuild” significantly improved performance. (over 90%!) They weren’t done, knowing that complex features later in the feature manager run faster than if they are earlier in the feature manager they found significant improvement just by reordering the features in the part. Moral of the story, spend time with the “feature statistics” tool in SolidWorks, tweak your features and their order to learn how SolidWorks builds models. It CAN make a difference. (Just don’t spend more time tweaking a model to improve performance than you would ever save!)

Other quick hits:

  • Since it is true complex features work better at the end of the feature tree, if you have several complex features sometimes you can see performance improvements if you break the part into multiple sub parts.
  • Back a few versions ago SolidWorks no longer automatically displayed the “update folders” in assemblies. They were so handy when inspecting your in-context relationships in the parts of your assemblies. I don’t know why they did this, but did you know they are still there? Just right mouse click on the assembly feature, the option to display them is there!
  • Want SolidWorks to handle your slip and press fit dowel holes and call them out by your standards on drawings? Try creating your own custom standard in the hole wizard!

There was so much more. There was a filming crew there recording the entire session and the PowerPoint presentation was promised to be available as well. Keep your eye out for it, you won’t be sorry!

Jeff Sweeney

Jeff Sweeney
Engineering Data Specialist
3DVision Technologies

More control in SP4

Friday, January 25th, 2008

DriveWorks 6, service pack 4 has a great new control for your dialog boxes. It allows your users to enter in linear dimensional values in any units they choose and DriveWorks will do the conversion for you. Users can even enter in mathematical formulas. It acts like the dimensional input box that you use in SolidWorks!

This is certainly one of those “I cannot believe it took them this long to add it!” -but it is nice that they did.

Jeff Sweeney

Jeff Sweeney
Engineering Data Specialist
3DVision Technologies

SolidWorks TIPS & TRICKS

Friday, January 25th, 2008

Have you ever wanted to REORDER multiple Features in the tree, but realized that you cannot do this in SolidWorks ? Here is a simple “workaround”…

Add the features that you want to REORDER into a FOLDER (ctrl select or shift select the features in the tree, RTclick and choose ADD TO NEW FOLDER), then you can Drag & Drop to reorder the FOLDER in the tree. Then just DELETE the folder ! E-A-S-Y !

(In some cases you may get a warning message about “cannot reorder a feature that is used in another feature”, just accept it. It will end up grouping all previous features into the folder, but after you delete the folder the result will still be what you wanted…)

Randy Simmons

Randy Simmons
Application Engineer, CSWP
3DVision Technologies

SolidWorks TIPS & TRICKS

Friday, January 25th, 2008

Tired of making a reference line or a reference point in your sketches just so you can DIMENSION to a MIDPOINT ? Try this…!

When you are using the SmartDimension tool in SolidWorks you can RT-CLICK a line (or other entities) and choose “SELECT MIDPOINT” from the RT-CLK menu to dimension to the MIDPOINT ! Piece of cake.

Randy Simmons

Randy Simmons
Application Engineer, CSWP
3DVision Technologies

What machine should I buy for running COSMOS?

Monday, January 14th, 2008

As a COSMOS technical support engineer, customers often ask for suggestions as to what they should get as an analysis machine. This is a difficult question to answer. Without knowing the type and complexity of problems that the customer is running, it is tough to provide a recommendation that will best fit the customer’s needs. In this entry, I will outline the key factors that make or break an analysis machine.

RAM

RAM is the most important factor in the ability to solve large and complex problems. SolidWorks and COSMOS are RAM resident programs so the more RAM that you have available, the more capable your workstation will be.

Good: 2 GB

Better: 4 GB

Best: 8 GB

Two gigs of RAM are adequate for relatively simple to moderately complex linear analysis. Additional RAM should be available for more complex problems (non-linear analysis, FloWorks, etc). If the user has to make a choice based on a budget restriction, it is recommended to add more RAM than to focus on the number of processors or processor speed. However, it should be kept in mind that the x32 bit version of Windows allows only up to 4GB of RAM (realistically only 3GB after enabling the 3GB switch during the boot sequence) for any given process.

Processor

Second in importance to RAM is the processor. Processor speed as well as the number of processors can improve solution time. Also, x64 bit processors give you access to more RAM which will permit the user to solve more complex problems.

Good: Single processor > 2GHz

Better: Dual Core

Best: Quad or Dual Quad Core

Please see the following link for recommended and preferred processors:

http://66.223.111.93/WebHelp/FAQID__x135.htm

COSMOS FloWorks has the capability to utilize multiple processors for solving batch runs. Multiple processors will not make a single FloWorks analysis run faster compared w/ a single processor machine. The FloWorks solver does not have the multi-threaded capability to utilize multiple processors for a single analysis. However, having multiple processors for a single analysis will permit the solution to be running on one processor and other tasks to be done simultaneously. Please see the following link for more information on this topic:

http://66.223.111.93/WebHelp/FAQID__x031.htm

Please see the following link for an analysis of the effect of multiple processors on COSMOSWorks solution times:

http://66.223.111.93/WebHelp/FAQID__x385.htm

Note: When considering a multiple processor machine, do not fall for the false pretense that two slower processors will perform better than one faster processor. The multi-processor benefit is based on the assumption of equivalent processor speed.

Video Card

A weak video card can ruin an otherwise excellent machine. This is especially true with some of the new graphics-intensive features in SolidWorks such as RealView. Please refer to the following link to see approved video cards:

http://www.solidworks.com/pages/services/VideoCardTesting.html

Hard drive

From the COSMOS knowledge base article “COSMOS – Operating System Requirements and Recommended Hardware”, a minimum of 160 GB of hard disk space is required but 250 GB or more is recommended. Please see the following link to view this knowledge base article:

http://66.223.111.93/WebHelp/FAQID__x135.htm

Operating System

We recommend Windows XP as an operating system. The XP 64 bit version again will give the user access to more RAM which will help in the solution of more complex problems. Windows Vista is supported for the 32 bit versions of SolidWorks and COSMOS only.

Good: XP

Better: XP 64 bit

Best: XP 64 bit

These are the major factors that influence the performance of an analysis machine. Now it is up to you to determine what level of machine best fits your processes and budget. I encourage you to read the following article to help you determine the best option for you:

http://manufacturing.cadalyst.com/manufacturing/article/articleDetail.jsp?id=99700

Seth Bischoff

Seth Bischoff
CAE Support Engineer
3DVision Technologies

New design automation web sites

Monday, January 14th, 2008

There is now a web site completely devoted to supporting the growing DriveWorksXpress community. If you get a chance go check it out. It has forums, tutorials and videos, FAQs and examples -everything you need to keep your design automation heart happy!

Speaking of design automation, have you seen SolidWorks’ new design automation micro-site?

DriveWorksXpress has been available as a free download for several years now. Isn’t it amazing how much more interest there is in design automation now that DriveWorksXpress is included in the core SolidWorks product?

Jeff Sweeney

Jeff Sweeney
Engineering Data Specialist
3DVision Technologies

On the fly email notifications

Thursday, January 3rd, 2008

A common PDMWorks Enterprise enhancement request is to give the users the ability to pick and choose who gets notified when a document goes through a workflow transition.

While personally that request seems like it would make a loophole users could use to get around the system i.e. not notifying your manager or quality control if a document is approved. -I’ll grant there may be cases where it would be useful.

So I thought I’d give you a little application that could be used to get you started in creating your own. There are fancier ways this could be done but this provides a very flexible solution and the price is right eh?

The program would be kicked off as an “action” as a document goes through a transition. [As an example see screen shot.]

Transaction

Note the full file name is sent as a command line argument using the “File Path” tag. This is how the file name gets sent to the program. Additionally, ensure the compiled .exe program is in a location where everyone has access to it.

Once started by the PDMWorks Enterprise transition, this routine simply creates a pre-populated Outlook message -populated with anything you choose. Typically the body of the message wouldn’t need to contain much -mostly just containing a link to the file that triggered the routine and some minimal instructions. The user would then, in this Outlook message, choose who to send the email to. He could also modify the body of the email if he chose. Then when the email looks as he likes he simply clicks “send”.

Here is the .NET code. Feel free to modify it to fit your needs, just keep the first comment line in! :)

Imports Microsoft.Office.Interop
Imports Microsoft.VisualBasic
Module modMain
Public Sub Main()
'by Jeff Sweeney, may he live long and prosper
Dim strFileName As String = Interaction.Command()
Dim objOutlook As Outlook.Application
Dim objNameSpace As Outlook.NameSpace
Dim objMailFolder As Outlook.MAPIFolder
Dim objMailItem As Outlook.MailItem
objOutlook = CreateObject("Outlook.application")
objNameSpace = objOutlook.GetNamespace("MAPI")
objMailFolder = objNameSpace.GetDefaultFolder(4)
objMailItem = objMailFolder.Items.Add
objMailItem.Subject = "A file needs your approval"
objMailItem.HTMLBody = strFileName & " has gone through a transition and requires you to do something"
objMailItem.Display()'gives the user a chance to modify
objMailItem = Nothing
objMailFolder = Nothing
objNameSpace = Nothing
objOutlook = Nothing
End Sub
End Module

Tip: Don’t forget you will need to add Outlook as a reference in your .NET project. Otherwise simply compile as a “Console Application” and you are set!

This is just the tip of the iceberg. You could change the routine to accept more than one parameter. An additional parameter could be the transition name, so you could get different emails depending on the transition that called it. You could have the routine examine the extension of the file and do different things depending on the file’s extension.

I’d love to learn how you end up using it!

Jeff Sweeney

Jeff Sweeney
Engineering Data Specialist
3DVision Technologies

WordPress SEO fine-tune by Meta SEO Pack from Poradnik Webmastera