<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Tapped Thread Joint on MechCalc how-to Guide</title>
    <link>https://mechcalc.net/blog/en/tags/tapped-thread-joint/</link>
    <description>Recent content in Tapped Thread Joint on MechCalc how-to Guide</description>
    <image>
      <title>MechCalc how-to Guide</title>
      <url>https://mechcalc.net/blog/og-default.png</url>
      <link>https://mechcalc.net/blog/og-default.png</link>
    </image>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Mon, 20 Apr 2026 19:00:00 +0200</lastBuildDate>
    <atom:link href="https://mechcalc.net/blog/en/tags/tapped-thread-joint/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>VDI 2230 (009): Full Worked Example (ESV)</title>
      <link>https://mechcalc.net/blog/en/posts/vdi2230-09-worked-example-esv/</link>
      <pubDate>Mon, 20 Apr 2026 19:00:00 +0200</pubDate>
      <guid>https://mechcalc.net/blog/en/posts/vdi2230-09-worked-example-esv/</guid>
      <description>A full VDI 2230 tapped-thread joint (ESV/TTJ) worked example. Compared with the previous DSV example, it highlights the key ESV differences in the resilience calculation, the nut-region elastic modulus, and the engagement-depth check.</description>
    </item>
    <item>
      <title>VDI 2230 (002): Scope and Standard Positioning</title>
      <link>https://mechcalc.net/blog/en/posts/vdi2230-02-scope-and-positioning/</link>
      <pubDate>Mon, 20 Apr 2026 11:00:00 +0200</pubDate>
      <guid>https://mechcalc.net/blog/en/posts/vdi2230-02-scope-and-positioning/</guid>
      <description>The applicability conditions of VDI 2230 Blatt 1, the interface limiting dimension G, the family of standards it depends on, and the implicit premise about how force is transmitted. Making clear what the standard can and cannot compute, so you avoid applying it blindly in the wrong scenario.</description>
    </item>
  </channel>
</rss>
