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-09 17:35:23 +08:00
parent 2a98ae7556
commit 161af68fe3
1271 changed files with 58251 additions and 98639 deletions
Download Patch File Download Diff File Expand all files Collapse all files
App/wwwroot/HiAPI-docsite/workflows/basic-simulation.html
+16 -16
View File
@@ -99,7 +99,7 @@
Equipment --> Job --> Option --> Run --> View
</code></pre>
<h2 id="starting-from-client-deliverables">Starting from Client Deliverables</h2>
<p>A real project usually starts from a bundle a customer hands over: NC programs, part/blank CAD, a tool sheet, sometimes a machine model and a few words about how the part is clamped and zeroed. Before building anything, reconcile that bundle against the <a href="../manual/setup/project-data-checklist.html">Project Data Checklist</a>, then map each item to the steps below:</p>
<p>A real project usually starts from a bundle a customer hands over: NC programs, part/blank CAD, a tool sheet, sometimes a machine model and a few words about how the part is clamped and zeroed. Before building anything, reconcile that bundle against the <a class="xref" href="project-data-checklist.html">Project Data Checklist</a>, then map each item to the steps below:</p>
<table>
<thead>
<tr>
@@ -112,12 +112,12 @@
<tr>
<td>NC programs (<code>.nc</code>, <code>.anc</code>, …)</td>
<td>NC files + controller brand</td>
<td><a href="../manual/setup/controller-iso.html">General NC Code Support</a></td>
<td><a class="xref" href="../technique/nc-dialects/controller-iso.html">General NC Code Support</a></td>
</tr>
<tr>
<td>Tool sheet (diameters, corner radius, flute count, stick-out)</td>
<td>Tool House</td>
<td><a href="../manual/setup/cutter.html">Cutter</a>, <a href="../manual/setup/apt.html">APT</a></td>
<td><a class="xref" href="../technique/milling-physics/cutter-geometry.html">Cutter Geometry</a></td>
</tr>
<tr>
<td>Part CAD + blank/stock CAD</td>
@@ -137,7 +137,7 @@
<tr>
<td>Material name</td>
<td>Workpiece material + cutting parameters</td>
<td><a href="../manual/setup/project-data-checklist.html">Project Data Checklist</a></td>
<td><a class="xref" href="project-data-checklist.html">Project Data Checklist</a></td>
</tr>
</tbody>
</table>
@@ -154,7 +154,7 @@
<h3 id="machine-tool">Machine Tool</h3>
<p>The machine tool (<code>.mt</code> file) provides the kinematic model and STL bodies. Once selected it rarely changes between simulations.</p>
<h3 id="controller">Controller</h3>
<p>Select the controller brand and type (e.g., Fanuc, Heidenhain, Siemens). This determines how NC code is interpreted. See <a href="../manual/setup/controller-heidenhain.html">Heidenhain Support</a> and <a href="../manual/setup/controller-iso.html">General NC Code Support</a> for details.</p>
<p>Select the controller brand and type (e.g., Fanuc, Heidenhain, Siemens). This determines how NC code is interpreted. See <a class="xref" href="../technique/nc-dialects/controller-heidenhain.html">Heidenhain Support</a> and <a class="xref" href="../technique/nc-dialects/controller-iso.html">General NC Code Support</a> for details.</p>
<h3 id="gui-operation">GUI Operation</h3>
<p>Open or create a project in the HiNC application and configure machine tool and controller through the corresponding panels before setting up the job.</p>
<hr>
@@ -162,7 +162,7 @@
<p>With equipment fixed, configure the job-specific components that change between simulations.</p>
<div class="TIP">
<h5>Tip</h5>
<p>For the full list of data to collect before building a project (and a customer-facing checklist), see <a href="../manual/setup/project-data-checklist.html">Project Data Checklist</a>.</p>
<p>For the full list of data to collect before building a project (and a customer-facing checklist), see <a class="xref" href="project-data-checklist.html">Project Data Checklist</a>.</p>
</div>
<h3 id="job-components">Job Components</h3>
<table>
@@ -220,7 +220,7 @@ var fixture = Fixture;
</div>
<div class="NOTE">
<h5>Note</h5>
<p>Going <em>finer</em> is what costs the <strong>8x</strong> — and at the fine resolutions real NC machining needs, geometry removal is usually the bottleneck. Going <em>coarser</em> only saves time while geometry removal is the bottleneck. Once the mesh is coarse enough that geometry removal is already cheap (1–2 mm is already very coarse for NC), the fixed per-step costs dominate and raising <code>MachiningResolution_mm</code> further barely changes total time (this is why 1.0 mm and 2.0 mm can run at nearly the same speed). To speed up in that regime, reduce the step count via <a href="#33-machining-motion-resolution">Machining Motion Resolution</a>. See <a href="../manual/analysis/cpu-usage.html">CPU Usage During Simulation</a>.</p>
<p>Going <em>finer</em> is what costs the <strong>8x</strong> — and at the fine resolutions real NC machining needs, geometry removal is usually the bottleneck. Going <em>coarser</em> only saves time while geometry removal is the bottleneck. Once the mesh is coarse enough that geometry removal is already cheap (1–2 mm is already very coarse for NC), the fixed per-step costs dominate and raising <code>MachiningResolution_mm</code> further barely changes total time (this is why 1.0 mm and 2.0 mm can run at nearly the same speed). To speed up in that regime, reduce the step count via <a href="#33-machining-motion-resolution">Machining Motion Resolution</a>. See <a class="xref" href="../technique/simulation-performance/cpu-usage.html">CPU Usage During Simulation</a>.</p>
</div>
<h3 id="32-display-cache">3.2 Display Cache</h3>
<pre><code class="lang-csharp">DispCache_Mb = 260;
@@ -261,7 +261,7 @@ var fixture = Fixture;
</table>
<div class="IMPORTANT">
<h5>Important</h5>
<p><strong>Total simulation time is governed by whichever is slower: geometry removal or the per-step fixed costs.</strong> Geometry-removal cost is set by <a href="#31-workpiece-entity-resolution">mesh resolution</a>; the per-step fixed costs (physics, thermal/wear, per-step bookkeeping) are set by the <strong>number of steps</strong> — the motion-resolution mode plus the spindle revolutions along the toolpath, independent of mesh resolution and of workpiece size. At the fine resolutions real NC machining needs, <strong>geometry removal is usually the bottleneck</strong> (finer = much slower). Only once the mesh is coarse enough that geometry removal is already cheap do the fixed per-step costs dominate — then raising <code>MachiningResolution_mm</code> further will <strong>not</strong> speed things up (this is why 1.0 mm and 2.0 mm can run at nearly the same speed); reduce the step count instead — e.g. <code>ScaledFeedPerCycle(2)</code> takes one step per 2 revolutions, halving the steps, at the cost of sparser force-curve sampling. See <a href="../manual/analysis/cpu-usage.html">CPU Usage During Simulation</a>.</p>
<p><strong>Total simulation time is governed by whichever is slower: geometry removal or the per-step fixed costs.</strong> Geometry-removal cost is set by <a href="#31-workpiece-entity-resolution">mesh resolution</a>; the per-step fixed costs (physics, thermal/wear, per-step bookkeeping) are set by the <strong>number of steps</strong> — the motion-resolution mode plus the spindle revolutions along the toolpath, independent of mesh resolution and of workpiece size. At the fine resolutions real NC machining needs, <strong>geometry removal is usually the bottleneck</strong> (finer = much slower). Only once the mesh is coarse enough that geometry removal is already cheap do the fixed per-step costs dominate — then raising <code>MachiningResolution_mm</code> further will <strong>not</strong> speed things up (this is why 1.0 mm and 2.0 mm can run at nearly the same speed); reduce the step count instead — e.g. <code>ScaledFeedPerCycle(2)</code> takes one step per 2 revolutions, halving the steps, at the cost of sparser force-curve sampling. See <a class="xref" href="../technique/simulation-performance/cpu-usage.html">CPU Usage During Simulation</a>.</p>
</div>
<div class="WARNING">
<h5>Warning</h5>
@@ -304,7 +304,7 @@ PlayNc($&quot;G01 X{x} Y20 F100&quot;, &quot;Generated Command&quot;);
</code></pre>
<div class="NOTE">
<h5>Note</h5>
<p>Unlike the file players above, CL playback drives a <a class="xref" href="../api/HiMachining.Milling.ClMillingDevice.html">ClMillingDevice</a> chain — the cutter location is applied straight to the tool — <strong>not</strong> the machine-tool chain from <a href="#1-set-machine-tool-and-controller">§1</a>. Use it to verify the programmed path itself, independent of machine and post-processor. See <a href="../manual/runtime/cutter-location-playback.html">Cutter-Location (CL) Playback</a> for the supported record set, tool creation from <code>TLDATA</code>, and the chain requirement.</p>
<p>Unlike the file players above, CL playback drives a <a class="xref" href="../api/HiMachining.Milling.ClMillingDevice.html">ClMillingDevice</a> chain — the cutter location is applied straight to the tool — <strong>not</strong> the machine-tool chain from <a href="#1-set-machine-tool-and-controller">§1</a>. Use it to verify the programmed path itself, independent of machine and post-processor. See <a class="xref" href="../technique/scripting/cutter-location-playback.html">Cutter-Location (CL) Playback</a> for the supported record set, tool creation from <code>TLDATA</code>, and the chain requirement.</p>
</div>
<h3 id="45-player-control">4.5 Player Control</h3>
<table>
@@ -405,13 +405,13 @@ AppendMessagesToFile(&quot;Output/messages.txt&quot;);
</table>
<h2 id="see-also">See Also</h2>
<ul>
<li><a href="../manual/setup/controller-heidenhain.html">Heidenhain Support</a> — controller configuration</li>
<li><a href="../manual/setup/controller-iso.html">General NC Code Support</a> — ISO NC support</li>
<li><a href="../manual/runtime/cutter-location-playback.html">Cutter-Location (CL) Playback</a> — replay a CAM cutter-location file with <code>PlayClFile</code></li>
<li><a href="../manual/runtime/step.html">Step</a> — what a step is, accessing and outputting step data</li>
<li><a href="../manual/runtime/step-fields.html">Step Field Reference</a> — step field reference</li>
<li><a class="xref" href="../manual/runtime/script-command.html">Glossary: Script Commands</a> — script command basics</li>
<li><a class="xref" href="../manual/runtime/session-shell.html">Glossary: SessionShell Quick-Reference</a> — SessionShell quick-reference</li>
<li><a class="xref" href="../technique/nc-dialects/controller-heidenhain.html">Heidenhain Support</a> — controller configuration</li>
<li><a class="xref" href="../technique/nc-dialects/controller-iso.html">General NC Code Support</a> — ISO NC support</li>
<li><a class="xref" href="../technique/scripting/cutter-location-playback.html">Cutter-Location (CL) Playback</a> — replay a CAM cutter-location file with <code>PlayClFile</code></li>
<li><a class="xref" href="../technique/scripting/step.html">Step</a> — what a step is, accessing and outputting step data</li>
<li><a class="xref" href="../technique/scripting/step-fields.html">Step Field Reference</a> — step field reference</li>
<li><a class="xref" href="../technique/scripting/script-command.html">Script Commands</a> — script command basics</li>
<li><a class="xref" href="../technique/scripting/session-shell.html">SessionShell</a> — SessionShell quick-reference</li>
</ul>
</article>