Drill and Tap; and calloutformat.txt (Part 1)

This entry is part 1 of 4 in the series Hole Callouts

Sooner or later, the topic of how to callout a threaded hole comes up in pretty much everyone’s career in the Mechanical Engineering field.  I’ve seen the nature of those discussions be straight forward, but I’ve also seen angst riddled arguements.  Though this isn’t a SolidWorks specific topic, it is important to its users. This is because SolidWorks specifies hole callouts differently in different scenarios.

The conventional rule (within ANSI Inch) is that a threaded hole should be called out as a leadered note showing its nominal drill size and depth on the first line, and the thread size, threads per inch, thread series designation, thread class and thread depth on the second line.  This is common practice, so most people are comfortable using it.

Example (without use of symbols):
2X .190 DIA .190 DEEP
8-32 UNC-2B .164 DEEP

Of course, this method has flaws, which I’ll get into later.

I’ve seen two extremes as well.  At one extreme, the threaded hole callout has the actual drill bit size listed in addition to specification for the tap and drill.  I gather it would look something like this:

2X .438 DIA .25 DEEP WITH 7/16 Q DRILL
.438 UNC-2B .375 DEEP

Of course the basic flaw with adding the drill size is that this is a specification of process, which is generally disallowed by ASME Y14.5M-1994.  It is equivalent to having the note “FORM THIS PART WITH LATHE MODEL XYB”  or even, “JUMP UP AND DOWN THREE TIMES AND SPIN IN A CIRCLE BEFORE USING THE MILL TO CUT THIS HOLE”.  Hyperbole aside, this practice is not appropriate.

On the other end, one might find a hole callout that simply states the thread size, such as “TAPPED HOLE”  This is a bad case of under-specification.  I haven’t seen this method often on formal drawings, but it is very common on preliminary sketches.  There just isn’t enough information.

What is just-enough-information for a threaded hole callout?  Well, this answer is easy.  Thread size, threads per inch, thread series designation (sometimes considered optional), thread class, thread depth, and sometimes drill depth or end condition.  The “nominal” drill diameter isn’t actually needed.  There’s several flaws with including the drill diameter.  First, the actual drill diameter is not based on the callout, but rather the thread itself.  It is over-specification.  Second, drill diameter is stated as a dimension, so it is not nominal.  Because of this, the standard drawing tolerance must be applied to that dimension.  Again, this is over-specification because the thread has its own tolerance for its final size.  Simply by stating the thread class, its tolerance is called out.  Third, because of these other points, specifying the drill diameter is actually a specification of process.  Given all that, I always callout a threaded hole as so:

2X 8-32 UNC-2B DEPTH .165

In the rare event that drill hole depth or end condition is necessary to call out, then simply state that specification in the callout, or show it dimensionally on the drawing view itself.  How this relates to SolidWorks and the calloutformat.txt file will be discussed in Part 2 of this article.




SolidWorks World 2008 Day 3 (Jan 23) General Session

Several presentations stand out in my mind from the Wednesday General Session.  This was the session that really got down to the business of talking about the SolidWorks community and the future of the SolidWorks software.

Richard Doyle introduced the SWUGN regional leaders to the General Session.  I’m guessing this is the first time many people even heard of this group. This is an important group that is responsible for increasing the number of SolidWorks User Groups nationwide; and worldwide too.

SWUGN Leadership

Another memorable presentation was Engineers in Crisis comedy skit used to introduce us to many of the new functions and improvements that will appear in SolidWorks 2009.  The skit consisted of a supposed talk show host addressing many frustrations that CAD users (unnamedly SolidWorks users) experienced when using their CAD software.  The frustration was collectively referred to as PAS (Performance Addiction Syndrome).

Engineering in Crisis

Who isn’t addicted to something that performs well?  They showed short videos of some engineers who were going mad because of issues they were having with an unnamed CAD program.  To help, three “doctors” presented the videos and then explained the solution offered in SolidWorks 2009.  This one particular engineer in one of the stories was vexed by “too many steps.”  This was prolly the funniest of the bunch.  I remember when they showed him getting out of his co-worker’s car.  His co-worker double beeped his remote to lock his car.  The engineer (Bill, I think) preceded to yell something like, “You only need to beep it once!  Doing it twice is too many steps!  Ughh!!!”  The interviews with his boss and co-workers were icing on the cake.

PAS

Anyway, the point was that SolidWorks 2009 would be adding functionality and simplifying some tasks.  Just to name a few:

  • Big news is that SolidWorks 2009 will accept negative dimensions when adding dimension values to objects within a sketch!
  • Handling of large assemblies has improved substantially.
  • Features created at the assembly level will be transferred to the part.
  • BOM tables can now be directly added to the Model Assembly.
  • Slot tool has finally been added.  (In fact, I recently participated in a questionnaire regarding how this feature will be dimensioned on the drawing.)
  • In sketch mode, dimensioning for sizes of objects will automatically pop up and ask to be populated when the object is created.
  • Routing now supports flat cables, and so on.

This skit was immediately followed by a demonstration of the speed differences we can expect from SolidWorks 2009.  They had a side by side comparison between SolidWorks 2008 and 2009.  It does appear that performance will indeed be massively improved.  This is of course based on the presentation.  I will reserve my final judgment for when I get a chance to use 2009 for myself.

SolidWorks World 2008 Day 2 (Jan 22) Block Party!

Go-Go Dancer at the Concert

After three whole days of almost nonstop geekdom business, it was time to let loose, all on SolidWorks Corporation’s tab.  This was the SolidWorks World 2008 Block Party!  For this event, a few blocks of the Gaslamp Quarter was shut down just for the attendees of the conference.  Most of the bars and restaurants served free tap beer all night.  There was plenty of pretty finger food that was OK.  The live band was a nice touch, but didn’t really do it for me; too many not-so-good covers of 70’s rock classics that I don’t much care about anyway.  Then there was the two lone Go-Go dancers that were kind enough to spend as much time taking pictures with all the guys as they did dancing.  They musta been good sports about the whole thing.  

Chris MacCormick and I meet up at this one place with a small out-door patio.  He then took me around to meet everyone, including fellow bloggers, reps, and SolidWorks Partners.  This was my first time at SWW8.  Here’s a snippet of a slide-show.  I’m sure some will recognize themselves! 🙂

The night did end a little early at 10pm.  I guess that is to be expected for an hosted event on public streets.  As far as I can tell, we all had a blast.

New Technologies

I received an email the other day that I found interesting technology. As some of you may know, voice activation/recognition has been around a few years, but is slowly gaining popularity. For SolidWorks users, the technology is available now.

http://www.xpressosoft.com/

I have not tried the software myself yet, but anything to help users make their job easier to create models is OK for me. (thanks Joshua)

Also, something to think about is future technology and where it is headed. Having worked in engineering for over 20 years and in I.T., I have seen some new technology coming our way in a few years. In 5-10 years, my opinion is there will be great strides in how we do computing in all professions. Because of these changes, our society will have to adapt to new ways how we will shop and communicate, among other differences [Be ready to buy stock in FedEx or UPS 😉 ]. Our grandkids may be doing all or some of their schooling online. The future is near.

http://tech.msn.com/news/articlepcw.aspx?cp-documentid=6183619>1=10938

SolidWorks Real Reward (Smart Button)

SolidWorks USB Web Key Smart ButtonSolidWorks has a new Real Reward program.  This new marketing scheme is being kicked off by mailing out these USB Web Key smart buttons.  All you need to do is plug this device into your USB port and press the button.  It kinda reminds me of the easy button from the commercials of one of those office supply stores.  Of course, those easy buttons pretty much solve whatever problem with which you happen to find your self.  This smart button does one thing.  It takes you to the SolidWorks Real Reward program website.  Oh, and it has an LED that glows at you all day (assuming you leave it attached to your computer).  No matter how many times I press it, it always takes me back to the Real Reward program website.

Yup, it did it again.

The Real Reward program allows you to give the SolidWorks Marketing Department all of your friends and family email addresses so that they may email them with an offer for a 30-day free trial of SolidWorks, along with online support and training.  Matt Lombard’s recent post about the Walmart dollar bin comes to mind for some reason.

Once I plugged it in, I pushed it.  It went to the Real Reward program website.  Oh, dang, I just pushed it by accident and it opened up my web browser and did it again.  The documentation that was included with the smart button suggested that the button was programmed with two websites, but unfortunately, both actions with the button goes to the Real Reward program website.  It would’ve been cool if the second setting went to the main SolidWorks website or something so that I have an excuse to keep it plugged in for more than 5 minutes.  Marketing, huh?  Oh well.

Anyway, I then started looking for ways to reprogram this dang thing to make it actually useful.  No such luck so far.  I’ll report if I find a method.  In the meantime, it will light up my desk with its tiny LED reminding me to sell my friends and family’s email addresses for free to SolidWorks so they can promote a $6000 program to them.  I’m sure my Aunt Cathy (a nurse by trade) will appreciate the offer and snap up a copy as soon as she tries it out.

Oh, I didn’t mention the best part.  See, you don’t really sell the email addresses for free.  I was exaggerating.  Here’s the deal, if the people you refer actually buy SolidWorks, you start collecting prizes!   Seriously, check it out.  There’s some pretty cool stuff.  Maybe we can all send in each other’s email addresses so everyone gets credit for everyone else’s purchases so we can all get the free computer!  Oops, did I already find the MLM loop hole in this Marketing scheme?

Update (12/18/2009)

This program was cancelled by SolidWorks Corp as of December 2009.  I am not able to fulfill any further submission requests for the trial version of SolidWorks.  It is my understanding that SolidWorks still has other programs available.  Please contact a local VAR for details.  To find a local VAR or for information about current offers, please see the SolidWorks.com website.

[30-trial, 30-day trial, 30 day trial, thirty-day trial, 30-trial program, 30 day trial program, 30-day trial program]

SolidWorks World 2008 Day 2 (Jan 22) Breakout sessions and such

Finally, after two days of being strangers passing in the night, Chris MacCormick and I finally had a chance to meet up on this day.  But more of that later.

After the General Session was over, my first breakout session of the day was the Hands-On Session Creating SolidWorks Add-ins.  Although I dabble in creating and editing SolidWorks API to help shortcut common functions, I still am just a hack at VBA programming.  I had hoped this session would’ve been useful to continuing my exposure to VB.NET and making add-ins for SolidWorks.  I was very dissatisfied with this session.  This was particularly disappointing because this was my only Hands-On session for the entire SWW8, even though I had logged-on to the SWW8 website at the right time to allow me to get any Hands-On sessions I wanted (way back in 2007).  The session didn’t start off well.  There was a typo on my schedule card that pointed me to the wrong room.  Once I found the correct room and sat down, it took too long to get the session started.  Once the presenter started, he asked a question to check every-one’s experience level.  He asked the question so quickly, I do not believe anyone understood what he said until he uttered the words something like, “Good, everyone will know what I’m talking about.  Let’s get to this.”  Once he did start with the lesson, he flew through so fast, most everyone just gave up trying to follow along.  It took forever to get his attention to tell him no one know where he was in the lesson.  He just wasn’t paying attention to the attendees.  Worse yet, very few of the computers were even configured correctly to allow us to successfully follow along, even if we tried.  By the time some of us finally were able to bring this to his attention, half the session was over.  Many of us had not passed the first few steps.  He then discovered our computers had a wrong setting.  As we moved on again, we again found we couldn’t follow along.  He found out that yet another setting on the computer was wrong.  Basically, the presenter did not make sure the classroom computers where set up properly for his lesson.

At that point Chris MacCormick gave me a call to check when and where we were going to meet up for lunch.  I was so frustrated at the poor quality of the session, I answered the phone without apology. Chris and I planned to meet up in a few minutes.  I then just walked out with 15 minutes to spare. By that time, I was about the fifth person at a Hands-On computer to walk, and I wasn’t the last.  Also, almost all back of the room observers had left by that point.  What did I learn?  Know when to hold them; know when to fold them; know when to walk away; know when to run.

I finally met up with Chris just before the cafeteria opened.  It was about time.  He turns about to be a cool guy with a lot of dynamic energy.  Lunch provided by SWW8 was pretty good.  (I had given up on the SWW8 breakfasts by this time.)  We were later joined by Richard Doyle and another acquaintance of mine.  Chris had missed the SWUGN Annual Summit Meeting on the day before, so Mr. Doyle filled him in on some of the details.

After lunch, my first breakout session of the afternoon was Chris’ own Using the Power of 3D to Teach GD&T.  This session was geared towards being an interactive event between educators.  There were a lot of others who attended that may not have understood this paradigm.  Chris went into detail about the DimXpert and how to use this an other functionality to demonstrate GD&T, including possible limitations or dangers with relying too much on the software to define specifications.  I’ll let Chris go into more detail about this and his other session if he chooses. His session did spark a lot of dialogue between educators.  After the session, I witnessed more people flood up to the front of the room to talk to him than any other presenter at any other session I attended throughout SWW8.

Chris MacCormick

My final breakout session for the day was Exploring the SolidWorks API from a Battleship.  This session was more of a demonstration of how to use SolidWorks and its API creatively for unusual tasks.  The game of Battleship was completely modelled and emulated within SolidWorks.  It was very cleaver and extremely comprehensive.  The presenter did go into his methodology for writing API.  In part, these are some of the points:

  • Identify goals and level of user interaction.
  • Build API ready SolidWorks data (in the model and any files that will be used in the program).
  • Outline the code and define variables; including organization of classes and modules.
  • Explore SolidWorks API for automation.
  • Use clear naming convention for variables.

Because of the nature of the demonstration, this session proved to be a bit self-serving to the presenter.  However, this is also why this particular session was prolly the most entertaining of the day.