How to dimension feature patterns on drawings

This entry is part 3 of 8 in the series Dimensions and Tolerances

A couple of days ago, I briefly covered the mythical specification “non-accumulative tolerance” (or “non-cumulative”) as it is often applied to direct dimensions on feature patterns.  See the example in Figure 1 where the dimensional callout attempts to simply dimension a pattern without considering tolerance stack-up.  However, this attempt fails since any two non-adjecent holes cannot avoid accumulation of tolerance due to the dimensioning scheme.  The problem gets worse if three or more positions within the patten are compared to each other.

Non-accumulative tolerance dimension on a pattern
Figure 1

ASME repetitive feature dimensioning scheme

ASME Y14.5-2009 actually provides a linear method to detail feature patterns, called repetitive features and dimensions.  See Figure 2. Unfortunately, the standard does not provide any tolerance rules for its prescribed scheme. Presumably, this leads us to interpret a repetitive feature dimension as though it is shorthand for chain dimensioning.  Chain dimensioning accumulates tolerance as the pattern departs from the dimensioned start position.  Sometimes this is OK, but often this is unacceptable since the accumulation of tolerance can quickly lead to features that do not align to mating features on other components.

Figure 2
Figure 2

Disorganized direct dimensions

Another dimensioning scheme that I’ve seen involves a complete disregard for the fact that a pattern exists.  See Figure 3.  Directly dimensioning each of the positions within the pattern to each other may be acceptable in some scenarios, but likely isn’t a very clear choice for larger feature patterns.  The problem with this scheme is that it can be very difficult to determine the true accumulation of the tolerance stack-up.  It may also be difficult to determine design intent.

Figure 3
Figure 3

Baseline dimension scheme

To avoid the issues associated with other direct dimensioning schemes, one may choose to use baseline dimensioning, which may also be called rectangular coordinate dimensioning in some scenarios.  The advantage of a baseline dimension scheme is that it limits the accumulation of tolerances to the stake-up from just two dimensions.  This is because the total stack-up between any two positions within the feature pattern are related through a common baseline.  The problem with baseline dimensioning is obvious in Figure 4; its take up a lot of space on the drawing.

Figure 4
Figure 4

Ordinate dimensioning

A common alternative to baseline dimensioning is ordinate dimensioning, also known as rectangular coordinate dimensioning without dimension lines.  This scheme also relies on a baseline, referred to as zero (0), from which all of the features are dimensioned.  The advantage of ordinate dimensioning is that it takes up far less space on a drawing, as shown in Figure 5.  Tolerance stack-up is limited to just two dimensions between any two positions within the pattern.

Figure 5
Figure 5

Using GD&T for best results

The best way to avoid accumulation of tolerances is to use a methodology that does not rely on any form of direct dimensions.  ASME Y14.5 actually suggests that GD&T should be used instead of direct dimensions to locate features.  I have discovered the hard way that many individuals in the engineering field have an irrational fear of GD&T.  Even still, GD&T provides a far superior method for the location of positions within a feature pattern. The example in Figure 6 shows a less cluttered drawing.  With the addition of MMC to the feature control frame, this method could provide even better results since it would make use of bonus tolerance.  The position of each feature within the pattern has an optimal tolerance zone that more closely matches design intent.  One more added benefit is that all features controlled by a single feature control frame are automatically considered as a pattern.

Using GD&T to locate features
Figure 6

Since the tolerance zone is optimized, using GD&T may help reduce costs by allowing the manufacturing process to vary in a way that is more in line with design intent.  In turn, this can reduce the number of unnecessary part rejections.

Conclusion

When detailing feature patterns, one may wish to avoid the use of direct dimensioning methods or shortcuts like the mythical “non-accumulative tolerance”.  The best choice to detail a feature pattern is GD&T.  However, if GD&T is not desired, the next best method is prolly an ordinate dimension scheme.  It should be noted that for each of the dimensioning and tolerancing schemes shown within this article, there are a variety of ways to implement them.  This article is meant to present general examples.  Actual tolerancing requirements are guided by design intent and other considerations per individual cases.

DraftSight ends Beta; general release announced!

The big news from Dassault Systemes today is that they just announced the general release of DraftSight for Windows.  DraftSight is a no-cost 2D CAD application for CAD professionals, students and educators which allows them to create, edit and view .dwg files.  The very long beta release of the Windows version has ended with an impressive 400,000 450,000 downloads (as of 5:00PM ET on February 22, 2011) from the DraftSight website.  In a conversation I had with Aaron Kelly, Senior Director of DraftSight at Dassault Systemes, he stated that this number is “a lot more than we expected.”  He added that the total number of full DraftSight activations is over 95,000.

Language support

Also according to Kelly, since the beta 3 release, the DraftSight user interface has simultaneously supported 14 languages at once (English, German, French, Japanese, Simplified Chinese, Traditional Chinese, Spanish, Portuguese, Italian, Turkish, Korean, Polish, Russian, Czech).  As of today’s general release, DraftSight will now also support these languages in the Help file, meaning that DraftSight is now fully localized (all 14 versions will be released at once for each update).

DraftSight is community driven

Free support, training and enhancement requests may be conducted through the DraftSight online community, based on Dassault Systemes’ SwYm online collaboration and social innovation platform.  SwYm communities have profiles, blogs, micro-blogging, “iQuestions”, wikis, media sharing spaces (data, audio, video, and even 3D), status updates, and more all within one online user interface.

Other updates in the general release

API support for DraftSight is now available, for a fee.  This enables users to write add-on programs for DraftSight in C++ and other supported programming languages.  The addition of Command Variables Enhancement allows users to set and change system variables directly from the command line.  Aaron Kelly adds, “we fixed a bunch of bugs that people reported”.  He also stressed the value the user base in improving DraftSight.

Service options

DraftSight offers a variety of support options, including no-cost community support (mentioned above), as well as fee-based Premium Services that may include telephone and email support, network licensing and access to DraftSight APIs.  There is now the Education Premium Service for educators which includes curriculum materials, network licensing and telephone and email support.

SWUGN reaches 200

Old SWUGN headerRichard Doyle announced today that the number of SolidWorks User Groups  in the SolidWorks User Group Network (SWUGN) has reached 200 worldwide.  His announcement may be found on the SolidWorks Community Blog in the SolidWorks Forums.  In a forward looking statement, Doyle predicts, “There are at least 2 more groups coming on line in the next few days.”

Mythical Specifications: Non-accumulative tolerance

This entry is part 4 of 4 in the series Mythical Specifications

Mythical specifications come in many forms.  One realm they seem to haunt is that of repetitive features, also known as patterns.  Many attempts to shorthand pattern callouts are continuously made.  Bad habits die hard as old mistakes are passed down from one generation of engineers to the next.  One particularly bad habit is the use of linear dimensions with the term “NON-ACCUMULATIVE TOLERANCES”, or something similar.  There is no such thing.  Trying to use this shorthand leads to tolerance issues.

Pattern non-accumulative tolerance callout

In the example above, the dimensional callout attempts to simply dimension a pattern without considering tolerance stack-up.  However, this attempt fails since any two non-adjecent holes cannot avoid accumulation of tolerance due to the dimensioning scheme.  Tolerance stack-ups on linear dimensions have accumulation.  There’s no way to avoid it without dumping linear dimensions.

I had originally planned on a short article about this topic.  However, once I started delving into it, I found out that there is a lot of ground to cover.   So, this topic will be addressed in detail within a future article (Feb 23, 2011) where examples of different pattern dimensioning schemes will be explored.

Also see How to dimension feature patterns on drawings.

SolidWorks World 2012 is on Valentine’s Day (luvification letter included)

HeartYes, it is true. SolidWorks World 2012 will be from February 13-15, 2012. It’s on Valentine’s Day! Maybe SolidWorks Corp is trying to schedule the event around other major conferences in southern California? Maybe someone didn’t think about the fact that many of us not only have to get approval from our boss at work, but now we have to get special approval from our boss at home?

Well, SolidWorks Corp has decided to help out. They created a new justification, or luvification, letter to help potential SolidWorks World 2012 attendees get approval from their spouses to be away on Valentine’s Day.

From their new weblink:

DS SolidWorks Corporation understands that SolidWorks World 2012 will fall on Valentines Day in 2012. Unfortunately, scheduling around other major events in southern California, such as the MD&M show, requires us to push our conference into mid-February next year. We are sympathetic to the many spouses that may be away from their loved-ones on Valentines Day. This justification, or luvification, letter was written to aid in getting spousal approval for attending SolidWorks World 2012.

SolidWorks World Luvification Letter

Dear madam or sir,

I am writing to you [spouse’s name here], who I love, to request permission to attend the SolidWorks World 2012. It is highly important that I attend this significant event because I believe the conference’s opportunities for technical training and networking with SolidWorks users worldwide can help me accelerate my career. In turn, that will help me bring home more bacon (and other such required groceries).

Don’t worry about me enjoying myself. I’ll be too busy with more than 150 technical training sessions and three long General Sessions. Then there’s the Special Event where I will congregate with other individuals who are missing their spouses. Yes, dear, I will miss you something fierce. The pain and agony of being away from you on Valentines Day will not be bareable. Therefore, the very next weekend, I’m taking you on a very special trip to [insert appropriate location and activities here] without the kids.

Thank you in advance for your consideration, and please let me know if you need additional information on specific conference opportunities and activities. I look forward to your positive response to my request.

With great love,

[insert your pitiful name here]

I originally posted this “luvification letter” in the SolidWorks Forum. And in case someone missed it, this is a joke. 🙂

 

Hidden SolidWorks Commands – compiled by Scott Baugh

SolidWorks Help file is notoriously unhelpful at times.  It has evolved over the years to improve its usefulness.  However, there are still many under-documented functions within the Help file or commands that are completely undocumented.  One day in January 2011, Scott Baugh asked a sincere and innocent question in the SolidWorks area on Eng-Tips.

Does anyone no (sic) where I can find a document with hidden SW commands. There are some key strokes and commands in SW that are not always listed in the help, or if they are they are overlooked very easy (sic).

From there, a long thread of comments grew.  Someone mentioned that users can print out a list of keystroke assignments.  This isn’t what Baugh was looking for. 

Then, the list of “hidden SolidWorks commands” began as people submitted commands they felt were obscure or impossible to find in the SolidWorks Help file.  It wasn’t long before Baugh offered to compile the list into a document.  At first, the idea was to build the list in a discrete document.  However, Deepak Gupta suggested GoogleDocs. 

From there, Baugh built the list of “hidden SolidWorks commands”.  There were three types of items added to the list:  commands that are truly undocumented, commands that are under-documented (full functionality isn’t described), and commands that were too hard to find within the documentation.

Baugh then brought the topic over to the SolidWorks Forums, where the discussion further exploded.  SolidWorks staff chimed in to address several points, but also to learn.  Jim Wilkinson provided several detailed responses to help bring clarity to the conversation.  Through his efforts, he also discovered several areas where improvement to the SolidWorks Help file is needed. 

The Hidden SolidWorks Commands list is now a treasure of numerous golden nuggets.  It’s not long, yet it can take awhile to fully explore.  Check it out.  If you have any further suggestions, feel free to leave a comment here, or in either the SolidWorks Forum thread or the Eng-Tips thread.

Hidden SolidWorks Commands