Continue to Site

Eng-Tips is the largest engineering community on the Internet

Intelligent Work Forums for Engineering Professionals

  • Congratulations KootK on being selected by the Eng-Tips community for having the most helpful posts in the forums last week. Way to Go!

Search results for query: *

  1. G_Apache

    Hole Pattern as Datum with different hole depths

    Our set up is nearly identical to ASME Y14.5-2018 Figure 7-18. I want to convey that the 4-hole hole pattern is to be considered the datum. However, the hole callouts are split into 2, with 2X holes having a different depth than the other 2X. I am getting pushback that the way I annotated the...
  2. G_Apache

    Can Basic Dimensions Be Overdefined?

    Hi all, Assuming we had 3 proper datums set up with a proper profile tolerance/feature control frame, would the following dimensioning scheme with basic dimensions be kosher? As in not over defined? If this would be okay, how is rounding dealt with? What would happen if I decided to add...
  3. G_Apache

    Interpreting ASME Y14.3 Paragraph on Orthographic View Labels

    My colleagues and I are disputing the meaning of the last sentence of the first paragraph in ASME Y14.3-2012 Section 6: "The terms "top," "front," "bottom," "right side," "left side," and "rear" shall themselves not be used for naming views. I'm interpreting this to mean the principal...
  4. G_Apache

    List of acceptable THRU callouts

    Hi Burunduk, This is an example of where we would use THRU TO CENTER. Basically it would be like THRU TO NEXT in Solidworks but I haven't seen prints with that callout whereas I have seen a couple with THRU TO CENTER. I got mixed up a bit though - the middle flange thing should be on the left...
  5. G_Apache

    List of acceptable THRU callouts

    Hi all, At my place of work we're having a discussion over whether "THRU TO CENTER" is a valid/common callout. I have seen "THRU", "THRU ALL", and "THRU TO BORE" but I am wondering if there is a generally agreed upon list of variations of THRU that would be generally understandable across...
  6. G_Apache

    How to quantify features

    I'm looking to see what the proper way to quantify multiple features is. In a situation like this where there are 2 surfaces for one datum and 3 surfaces for another, how do you express that the 2 surfaces are, say, 16mm away from the 3 surfaces? Should the quantity be dropped, be 2X, or be 3X?

Part and Inventory Search