HiNC-Deploy/HiNC-2025-win-desktop-Deploy
Archived
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

deploy.

Browse Source
This commit is contained in:
iamboss
2026-09-15 01:12:50 +08:00
parent 2db889ad89
commit 1a75503105
99 changed files with 4168 additions and 726 deletions
Download Patch File Download Diff File Expand all files Collapse all files
App/wwwroot/HiAPI-docsite/technique/measurement/smart-tool-holder.html
+14 -5
View File
@@ -104,10 +104,10 @@
<li>The impact of coordinate system misalignment is relatively smaller compared to the moment arm setting</li>
</ul>
</li>
<li><p><strong>Installation Angle Adjustment</strong></p>
<li><p><strong>Setup Angle Adjustment</strong></p>
<ul>
<li>If perfect alignment is not possible, measure the offset angle</li>
<li>Enter the measured angle in the &ldquo;Installation Angle&rdquo; field</li>
<li>Enter the measured angle in the cutter's <strong>Setup Angle</strong> field (Tool House → Cutter → Flute Contours)</li>
<li>The maximum possible deviation is 45 degrees</li>
</ul>
</li>
@@ -115,15 +115,24 @@
<h2 id="factors-affecting-accuracy">Factors Affecting Accuracy</h2>
<h3 id="coordinate-transformation-effects">Coordinate Transformation Effects</h3>
<ul>
<li>An installation angle deviation can cause up to a √2 factor difference in values</li>
<li>A setup angle offset rotates the measured (Mx, My) pair. The resultant |M| does not change, but a single channel can read anything from 0 to |M| — the same 45° offset takes Mx to √2 times its aligned value one way and to zero the other way</li>
<li>This difference is inherently a result of coordinate transformation, not a measurement accuracy issue</li>
<li>Even with the same smart tool holder, different installation angles will produce different measurement data</li>
<li>Even with the same smart tool holder, different setup angles will produce different measurement data</li>
</ul>
<p><img src="smart-tool-holder-img/setup-angle-rotation.svg" alt="Three top-view sketches of a two-flute cutter section: on the left the cutting edge lies on the sensor X axis and the moment vector M sits at 45°; in the middle the edge is turned 45° one way, M turns with it onto the X axis and Mx becomes the whole of |M|; on the right the edge is turned 45° the other way, M lands on the Y axis and Mx becomes zero">
<em>① — the cutting edge (blue) lies on the sensor X axis, θ = 0; in this example the transverse
moment M the cut produces sits at 45°, so Mx = My = |M|/√2. ② — the same cutter mounted with its
edge 45° clockwise of the X axis. Nothing about the cut has changed, so M is carried round with
the edge and lands on the X axis: Mx′ = |M|, √2 times the value in ①, and My′ = 0. ③ — the same
45° the other way puts M on the Y axis, and Mx′ = 0. In general Mx′ = |M| · cos(angle between M
and the sensor X axis): the resultant never changes, and one channel on its own can read anything
between 0 and |M| — a coordinate effect, not a measurement error. Entering θ as the cutter's
Setup Angle lets the simulation report in the sensor's own frame.</em></p>
<h3 id="best-practices">Best Practices</h3>
<ol>
<li>Prioritize accurate moment arm height configuration</li>
<li>Align the cutting edge with the sensor X-axis as closely as possible</li>
<li>If perfect alignment is not achievable, always measure and set the correct installation angle</li>
<li>If perfect alignment is not achievable, always measure and set the correct setup angle</li>
</ol>
<p>Only with these parameters correctly configured will the simulated micro-waveforms match the actual sensor measurements.</p>
<h2 id="see-also">See Also</h2>