Skip to main content
A
Anonymous
January 25, 2018
Question

Drive Thread Size (tapped hole) via Family Table?

  • January 25, 2018
  • 6 replies
  • 5521 views

Is it yet possible to Drive Thread Size (tapped hole or cosmetic thread) via Family Table?

 

If not, how are you all handling this?

6 replies

R
RoyCrerar1-Visitor
1-Visitor
January 26, 2018

Hi, Use engineered holes they have all the sizes you need with drill points, counter bores and countersunk. You also get for free the hole notes that can be customised in format to keep notation common in your design group.

 

Holes is under the model tab, engineering. Pull down to reveal holes.

KenFarley
KenFarley21-Topaz II
21-Topaz II
January 26, 2018

From what I've seen, this is something people have been wanting for a while, but it's not possible. The excuse seems to be that the family table would somehow "conflict" with the hole tables (?). The only method I saw that I would be willing to do is to create the hole(s) at with all the sizes and suppress all but one size. In the family table put all the features with the different sizes, and turn them on or off for each instance.

A lame solution, I know, but it's what they've given us.

A
Anonymous
January 26, 2018

"The only method I saw that I would be willing to do is to create the hole(s) at with all the sizes and suppress all but one size. In the family table put all the features with the different sizes, and turn them on or off for each instance."

 

Ken, this is exactly how we have handled it.  It's fine for a small table, but some of our tables have grown, with other users adding to the table... and really has made a mess.

 

I guess another option would be just have a regular hole and a separate cosmetic sketch, drive them with dimensions.  Would be a pain, but the table would be much cleaner?

T
TomU23-Emerald IV
23-Emerald IV
January 26, 2018

I guess another option would be just have a regular hole and a separate cosmetic sketch, drive them with dimensions.  Would be a pain, but the table would be much cleaner?

The approach I've taken in the past is similar to this.  I built a group of features with all the intelligence for the different fastener sizes embedded into the feature's relations.  Changing a single value on the first feature would automatically change all other aspects of the hole features.  Likewise, entering this one value in the family table would cause the fastener to automatically change sizes based on the table.  Once these are built they can quickly be placed as UDFs.

Terms & ConditionsAccessibility statement