Archived
deploy webservice static-file routing for docsite folder URLs, per-instance step-cache db, and constant-height panel title bars.
This commit is contained in:
@@ -118,6 +118,43 @@ Cutting tools, EDM (electrical discharge machining) dies.</li>
|
||||
<blockquote>
|
||||
<p>For information on measuring rake angle and relief angle, refer to <a href="../analysis/radial-angle-measurement.html">Radial Angle Measurement</a>.</p>
|
||||
</blockquote>
|
||||
<h3 id="upper-beam-clamping-end--shank-geometry">Upper Beam (Clamping End / Shank) Geometry</h3>
|
||||
<p>The <em>upper beam</em> is the cutter's shank / body above the flute — the non-cutting,
|
||||
clamping zone. It can be modeled with several geometry types; the two common
|
||||
choices are:</p>
|
||||
<ul>
|
||||
<li><p><strong>Cylindroid</strong> — an explicit ZR table. You author every <code>(Z, r)</code> pair, so the
|
||||
shank radius (and any stepped / necked profile) is whatever you type in. This
|
||||
faithfully reproduces a <em>known</em> shank, but every value is data you must supply.</p>
|
||||
</li>
|
||||
<li><p><strong>Extended Cylinder</strong> — a cylinder whose <strong>start (bottom) profile is driven by
|
||||
the flute</strong> and whose only parameter is the total length. Its radius follows
|
||||
the cutter (flute-top) radius automatically, so it needs <strong>no shank
|
||||
measurements</strong> — only a length long enough to reach the holder.</p>
|
||||
<p>⚠ <strong><code>FullLength</code> is the beam's FULL length measured from <code>Z=0</code> (the cutter
|
||||
tip), so it includes the flute span</strong> — it is <em>not</em> the remaining segment from
|
||||
the flute top to the exposed end. It must therefore be <strong>larger than the flute
|
||||
height</strong>: e.g. flute height 20 mm and 10 mm of shank above it → <code>FullLength = 30</code>, not 10. A value at or below the flute height inverts the beam solid;
|
||||
thermal physics then cannot build its shank shell layers and reports a
|
||||
<code>Cutter-UpperBeam--BelowFluteHeight</code> configuration error at tool change (the
|
||||
web editor rejects such a value outright).</p>
|
||||
</li>
|
||||
</ul>
|
||||
<p><strong>Convention — prefer the Extended Cylinder when the shank is not given.</strong> Most
|
||||
tool sheets (especially at quoting stage) list only the cutting diameter, corner
|
||||
radius, and stick-out; they do not give a shank diameter or a stepped/necked
|
||||
profile. In that case use the <strong>Extended Cylinder</strong>: it extends the flute by a
|
||||
length without inventing a radius the data does not support. A hand-authored
|
||||
Cylindroid here would bake a <em>guessed</em> shank radius into the model — and an
|
||||
over-fat guess produces false clearance / collision results, while an over-thin
|
||||
one understates the body. Reserve the <strong>Cylindroid</strong> (explicit ZR) for tools
|
||||
whose shank or neck profile is actually known or measured — e.g. stepped,
|
||||
necked, or back-tapered shanks where a flute-radius extension would be wrong.</p>
|
||||
<blockquote>
|
||||
<p>Tip: because the Extended Cylinder's radius tracks the flute, set its length
|
||||
comfortably past the exposed cutter height so the beam reaches into the holder
|
||||
with no gap; the overlap is harmless for clearance checks.</p>
|
||||
</blockquote>
|
||||
<h3 id="relief-angle-setting">Relief Angle Setting</h3>
|
||||
<p>The relief angle setting in HiNC refers to the primary relief angle. It is used to calculate flank wear width (Flank Wear, VB).</p>
|
||||
<h3 id="cutter-body-weight">Cutter Body Weight</h3>
|
||||
|
||||
Reference in New Issue
Block a user