This repository has been archived on 2026-10-11. You can view files and clone it. You cannot open issues or pull requests or push a commit.
Files
2026-09-11 03:46:11 +08:00

198 lines
11 KiB
HTML
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<title>Designing a Training Cut Set | HiAPI-C# 2025 </title>
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<meta name="title" content="Designing a Training Cut Set | HiAPI-C# 2025 ">
<link rel="icon" href="../../img/HiAPI.favicon.ico">
<link rel="stylesheet" href="../../public/docfx.min.css">
<link rel="stylesheet" href="../../public/main.css">
<meta name="docfx:navrel" content="../../toc.html">
<meta name="docfx:tocrel" content="toc.html">
<meta name="docfx:rel" content="../../">
<meta name="loc:inThisArticle" content="In this article">
<meta name="loc:searchResultsCount" content="{count} results for &quot;{query}&quot;">
<meta name="loc:searchNoResults" content="No results for &quot;{query}&quot;">
<meta name="loc:tocFilter" content="Filter by title">
<meta name="loc:nextArticle" content="Next">
<meta name="loc:prevArticle" content="Previous">
<meta name="loc:themeLight" content="Light">
<meta name="loc:themeDark" content="Dark">
<meta name="loc:themeAuto" content="Auto">
<meta name="loc:changeTheme" content="Change theme">
<meta name="loc:copy" content="Copy">
<meta name="loc:downloadPdf" content="Download PDF">
<script type="module" src="./../../public/docfx.min.js"></script>
<script>
const theme = localStorage.getItem('theme') || 'auto'
document.documentElement.setAttribute('data-bs-theme', theme === 'auto' ? (window.matchMedia('(prefers-color-scheme: dark)').matches ? 'dark' : 'light') : theme)
</script>
</head>
<body class="tex2jax_ignore" data-layout="" data-yaml-mime="">
<header class="bg-body border-bottom">
<nav id="autocollapse" class="navbar navbar-expand-md" role="navigation">
<div class="container-xxl flex-nowrap">
<a class="navbar-brand" href="../../index.html">
<img id="logo" class="svg" src="../../img/HiAPI.logo.png" alt="">
</a>
<button class="btn btn-lg d-md-none border-0" type="button" data-bs-toggle="collapse" data-bs-target="#navpanel" aria-controls="navpanel" aria-expanded="false" aria-label="Toggle navigation">
<i class="bi bi-three-dots"></i>
</button>
<div class="collapse navbar-collapse" id="navpanel">
<div id="navbar">
<form class="search" role="search" id="search">
<i class="bi bi-search"></i>
<input class="form-control" id="search-query" type="search" disabled placeholder="Search" autocomplete="off" aria-label="Search">
</form>
</div>
</div>
</div>
</nav>
</header>
<main class="container-xxl">
<div class="toc-offcanvas">
<div class="offcanvas-md offcanvas-start" tabindex="-1" id="tocOffcanvas" aria-labelledby="tocOffcanvasLabel">
<div class="offcanvas-header">
<h5 class="offcanvas-title" id="tocOffcanvasLabel">Table of Contents</h5>
<button type="button" class="btn-close" data-bs-dismiss="offcanvas" data-bs-target="#tocOffcanvas" aria-label="Close"></button>
</div>
<div class="offcanvas-body">
<nav class="toc" id="toc"></nav>
</div>
</div>
</div>
<div class="content">
<div class="actionbar">
<button class="btn btn-lg border-0 d-md-none" type="button" data-bs-toggle="offcanvas" data-bs-target="#tocOffcanvas" aria-controls="tocOffcanvas" aria-expanded="false" aria-label="Show table of contents">
<i class="bi bi-list"></i>
</button>
<nav id="breadcrumb"></nav>
</div>
<article data-uid="Technique-TrainingCutSetDesign">
<h1 id="designing-a-training-cut-set">Designing a Training Cut Set</h1>
<p>Training recovers the six milling coefficients by fitting simulated force against measured force
over a set of passes. Whether a given set of cutters and passes can determine those coefficients at
all is a property of the design rather than of the data quality: two specific degeneracies leave a
coefficient unrecoverable however clean the samples are. Each has its own fix, and neither fix
substitutes for the other.</p>
<h2 id="the-two-degeneracies">The Two Degeneracies</h2>
<table>
<thead>
<tr>
<th>What goes wrong</th>
<th>How it shows up in the result</th>
<th>What removes it</th>
</tr>
</thead>
<tbody>
<tr>
<td><strong>The bending-moment plane null.</strong> In rotation-averaged Mx/My one particular combination of the edge and normal shear coefficients is exactly unobservable</td>
<td>Shear coefficients come back orders of magnitude too large, and their signs flip between runs on the same data</td>
<td><strong>Helix diversity</strong> — at least two clearly different helix angles among the cutters trained together</td>
</tr>
<tr>
<td><strong>Slope–intercept collinearity</strong> between the shear and ploughing coefficients, which enter the fit as the slope and the intercept of the same line</td>
<td>The correlation still looks good. Shear comes back low by roughly a tenth, ploughing high by around a half</td>
<td><strong>A spread of feed per tooth</strong> across the passes — a range of chip loads, not a range of depths</td>
</tr>
</tbody>
</table>
<p>A set that fixes one and not the other still fails, and it fails in the manner of the one left
unfixed. Both are properties of the cut set as a whole, so both are decided before any metal is cut.</p>
<h2 id="why-the-helix-angle-is-the-lever">Why the Helix Angle Is the Lever</h2>
<p>The unobservable direction is a combination of the edge and normal shear coefficients weighted by
the cosine and sine of the helix angle. Changing the helix angle does not remove that direction —
it <strong>rotates</strong> it. Two helix angles far enough apart therefore give two different null directions
whose only common point is zero, so the pooled fit has no null at all, and the edge coefficient
becomes identifiable from the measurement alone: no torque channel, no prior value, no externally
supplied phase.</p>
<p>A single helix angle of zero is the worst case, and misleadingly so, because it aligns the null
exactly with the edge-coefficient axis. A cut set built that way returns an edge coefficient that
is null-space fill rather than a value the data demands, while the normal coefficient beside it
comes out as the most accurate number on the page.</p>
<div class="IMPORTANT">
<h5>Important</h5>
<p>At a single helix angle the individual edge and normal shear values are not meaningful on their
own, even when the correlation coefficient is high. A training run is judged by the force it
reproduces over time — see <a class="xref" href="../validation/cutting-force.html">Cutting Force and Torque</a> —
not by the magnitude of any one coefficient.</p>
</div>
<h2 id="flute-count-is-not-a-lever">Flute Count Is Not a Lever</h2>
<p>Adding more passes with the same symmetric multi-flute cutter buys nothing, at any feed. That
sample subspace is degenerate, and more of it stays degenerate. Evenly spaced flutes also cancel
the rotation-averaged transverse moment a run derives its own cutter phase from, so a set made only
of symmetric passes carries no phase reference of its own. Which way it then fails depends on the
channels measured: with the axial torque channel present the fit still converges and reports a high
correlation over shear coefficients orders of magnitude too large; without it the fit collapses
rather than degrading. Neither outcome is usable, and adding passes repairs neither. What buys
identifiability is spread — in helix angle, and in feed per tooth.</p>
<p>Supplying the phase from outside removes that half of the problem and nothing else.
<a class="xref" href="../../api/Hi.MillingForces.Training.MillingTraining.html#Hi_MillingForces_Training_MillingTraining_EnableCwePhasePairing">EnableCwePhasePairing</a> <small>(API)</small> reads
each step's phase from the engagement blocks instead of bootstrapping it from the samples, for
one-flute and symmetric two-flute cutters in light radial side cuts; outside those preconditions the
training falls back to the bootstrapped path with a warning, so a four-flute set is not rescued by
it. The null a single helix angle leaves is untouched either way.</p>
<p>The shipped smart-holder cut set has exactly this shape: its milling passes are one symmetric
four-flute end mill at two feeds, so the set is spread in feed per tooth alone and does not
determine its own edge and normal shear values — see
<a href="smart-holder-training.html">Smart Holder Training</a>.</p>
<p>Symmetric off-the-shelf cutters are nonetheless sufficient. Custom single-flute grinding is not
required for either fix; a pair of stock two-flute cutters ground at different helix angles carries
the same identifiability, and is what a shop can actually obtain.</p>
<h2 id="engagement-side-cuts-rather-than-slots">Engagement: Side Cuts Rather Than Slots</h2>
<p>The useful excitation comes from passes whose radial engagement is small enough that at most one
helix flute is in contact at a time — the engagement arc narrower than the angular pitch between
flutes. A full slot holds several flutes in the cut at once and averages away the very variation
the fit needs. Stepping a shallow side cut along the edge of the stock produces a set where no pass
is ever a slot.</p>
<p>Adding depth of cut is not a substitute. Depth moves the load without changing the chip load, so it
does nothing for the slope–intercept collinearity that the feed-per-tooth spread exists to break.</p>
<h2 id="see-also">See Also</h2>
<ul>
<li><a href="smart-holder-training.html">Smart Holder Training</a> — the shipped cut shapes these constraints apply to</li>
<li><a class="xref" href="../milling-physics/cutter-geometry.html">Cutter Geometry</a> — where the helix angle this design turns on is described and entered</li>
</ul>
</article>
<div class="contribution d-print-none">
</div>
<div class="next-article d-print-none border-top" id="nextArticle"></div>
</div>
<div class="affix">
<nav id="affix"></nav>
</div>
</main>
<div class="container-xxl search-results" id="search-results"></div>
<footer class="border-top text-secondary">
<div class="container-xxl">
<div class="flex-fill">
<span> Copyright © 2025 <a href='https://superhightech.com.tw'>Tech Coordinate</a>. All rights reserved. <a href='https://superhightech.com.tw'>超級高科技股份有限公司</a> © 2025 版權所有 </span>
</div>
</div>
</footer>
</body>
</html>