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
HiNC-2025-win-desktop-Deploy/App/wwwroot/HiAPI-docsite/workflows/basic-simulation.html
T
2026-09-09 17:35:23 +08:00

442 lines
24 KiB
HTML
Raw 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>Workflow: Basic Machining Simulation | HiAPI-C# 2025 </title>
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<meta name="title" content="Workflow: Basic Machining Simulation | 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="Workflow-BasicSimulation">
<h1 id="workflow-basic-machining-simulation">Workflow: Basic Machining Simulation</h1>
<p>This workflow walks through setting up and running a machining simulation from scratch, including project configuration, option tuning, NC execution, and result inspection.</p>
<p>For the <em>method</em> of assembling one — build order, how to shape the mission, and the replay-and-read-the-messages acceptance test that says the project is finished — see <a href="project-construction.html">Project Construction</a>.</p>
<pre><code class="lang-mermaid">flowchart TD
Equipment[&quot;Set machine tool &amp;&lt;br&gt;controller brand/type&quot;]
Job[&quot;Set workpiece, fixture,&lt;br&gt;tool house, NC files,&lt;br&gt;controller offsets&quot;]
Option[&quot;Tune simulation options&lt;br&gt;(resolution, physics, etc.)&quot;]
Run[&quot;Run simulation&quot;]
View[&quot;View results&quot;]
Equipment --&gt; Job --&gt; Option --&gt; Run --&gt; 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 class="xref" href="project-data-checklist.html">Project Data Checklist</a>, then map each item to the steps below:</p>
<table>
<thead>
<tr>
<th>Client deliverable</th>
<th>Maps to</th>
<th>Setup page</th>
</tr>
</thead>
<tbody>
<tr>
<td>NC programs (<code>.nc</code>, <code>.anc</code>, …)</td>
<td>NC files + controller brand</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 class="xref" href="../technique/milling-physics/cutter-geometry.html">Cutter Geometry</a></td>
</tr>
<tr>
<td>Part CAD + blank/stock CAD</td>
<td>Workpiece <code>IdealGeom</code> + <code>InitGeom</code></td>
<td><a href="../manual/setup/anchor.html">Anchor</a></td>
</tr>
<tr>
<td>Machine model + axis layout (3-axis, 3+1, 5-axis)</td>
<td>Machine tool kinematic chain</td>
<td><a href="../manual/setup/machine-tool.html">Machine Tool</a></td>
</tr>
<tr>
<td>&ldquo;Where is program zero?&rdquo; notes, work-offset list</td>
<td>Program zero + work-offset table</td>
<td><a href="../manual/setup/program-zero-alignment.html">Program Zero Alignment</a></td>
</tr>
<tr>
<td>Material name</td>
<td>Workpiece material + cutting parameters</td>
<td><a class="xref" href="project-data-checklist.html">Project Data Checklist</a></td>
</tr>
</tbody>
</table>
<div class="NOTE">
<h5>Note</h5>
<p>CAD geometry commonly arrives as <strong>STEP</strong> (<code>.step</code> / <code>.stp</code>). The workpiece and machine bodies are consumed as <strong>STL</strong> (or parametric primitives), so convert STEP to STL before import. The tool sheet's diameter and corner radius are authoritative; flute length, tooth count, helix, and stick-out are often missing and may have to be estimated from the spec string and confirmed with the client.</p>
</div>
<div class="TIP">
<h5>Tip</h5>
<p>When deliverables are incomplete (no blank CAD, unknown work offsets, unverified machine model), you can still stand up a <strong>rough</strong> project: use the NC tool diameters, the named material, a placeholder stock box that encloses the tool path, and an identity work offset — then run a coarse pass (see <a href="#31-workpiece-entity-resolution">§3.1</a>) to catch gross overcut/collision while you wait for the missing data. Record every assumed value so it can be confirmed later.</p>
</div>
<h2 id="1-set-machine-tool-and-controller">1. Set Machine Tool and Controller</h2>
<p>The machine tool and controller are fixed equipment that define the physical simulation environment.</p>
<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 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>
<h2 id="2-set-job-components">2. Set Job Components</h2>
<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 class="xref" href="project-data-checklist.html">Project Data Checklist</a>.</p>
</div>
<h3 id="job-components">Job Components</h3>
<table>
<thead>
<tr>
<th>Component</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td><strong>Workpiece</strong></td>
<td>Geometry (STL or parametric), material, and coordinate frame</td>
</tr>
<tr>
<td><strong>Fixture</strong> (optional)</td>
<td>Fixture geometry that participates in collision detection</td>
</tr>
<tr>
<td><strong>Tool House</strong></td>
<td>One or more cutting tools with geometry and flute definitions</td>
</tr>
<tr>
<td><strong>NC Files</strong></td>
<td>The NC programs to simulate</td>
</tr>
<tr>
<td><strong>Controller Offsets</strong></td>
<td>Tool offset tables, work offset tables, and other controller-specific presets</td>
</tr>
</tbody>
</table>
<div class="TIP">
<h5>Tip</h5>
<p>All file paths used in script commands are relative to the project directory unless an absolute path is given.</p>
</div>
<h3 id="script-access">Script Access</h3>
<p>The workpiece and fixture objects are available through <a class="xref" href="../api/Hi.MachiningProcs.SessionShell.html#Hi_MachiningProcs_SessionShell_Workpiece">Workpiece</a><small>(API)</small> and <a class="xref" href="../api/Hi.MachiningProcs.SessionShell.html#Hi_MachiningProcs_SessionShell_Fixture">Fixture</a><small>(API)</small>.</p>
<pre><code class="lang-csharp">var workpiece = Workpiece;
var fixture = Fixture;
</code></pre>
<h3 id="gui-operation-1">GUI Operation</h3>
<p>Configure each component through the corresponding panels (Workpiece, Fixture, Tool House windows).</p>
<hr>
<h2 id="3-tune-simulation-options">3. Tune Simulation Options</h2>
<p>Simulation options control the trade-off between accuracy and speed.</p>
<h3 id="31-workpiece-entity-resolution">3.1 Workpiece Entity Resolution</h3>
<p><a class="xref" href="../api/Hi.MachiningProcs.SessionShell.html#Hi_MachiningProcs_SessionShell_MachiningResolution_mm">MachiningResolution_mm</a><small>(API)</small> sets the smallest cube width of the workpiece mesh.</p>
<pre><code class="lang-csharp">MachiningResolution_mm = 0.125;
</code></pre>
<p>Valid values are <strong>powers of 2</strong> (e.g., 4, 2, 1, 0.5, 0.25, 0.125). If you supply a non-power-of-2 value the system rounds to the nearest power of 2.</p>
<div class="WARNING">
<h5>Warning</h5>
<p>Each halving of mesh width can increase computation time and RAM by up to <strong>8x</strong>. Start with a coarser resolution and refine only when needed.</p>
</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 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;
</code></pre>
<p>The display resolution depends on the cache size. Recommended value should not exceed 1000 Mb.</p>
<h3 id="33-machining-motion-resolution">3.3 Machining Motion Resolution</h3>
<p>Machining motion resolution determines the interval of each simulation step. Options:</p>
<table>
<thead>
<tr>
<th>Mode</th>
<th>Command</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td>Feed Per Cycle</td>
<td><code>MachiningMotionResolution = FeedPerCycle;</code></td>
<td>One step per spindle revolution (<strong>default</strong>)</td>
</tr>
<tr>
<td>Scaled Feed Per Cycle</td>
<td><code>MachiningMotionResolution = ScaledFeedPerCycle(2);</code></td>
<td>One step per (revolution × scale): scale &gt; 1 → fewer steps (faster); scale &lt; 1 → more steps (finer)</td>
</tr>
<tr>
<td>Feed Per Tooth</td>
<td><code>MachiningMotionResolution = FeedPerTooth;</code></td>
<td>One step per tooth pass (revolution ÷ flute count)</td>
</tr>
<tr>
<td>Fixed Pace</td>
<td><code>MachiningMotionResolution = FixedPace(1, 15);</code></td>
<td>Fixed linear (mm) and rotary (deg) resolution; cuts by sweeping between steps</td>
</tr>
</tbody>
</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 class="xref" href="../technique/simulation-performance/cpu-usage.html">CPU Usage During Simulation</a>.</p>
</div>
<div class="WARNING">
<h5>Warning</h5>
<p><strong>Do not use scaled model dimensions as a substitute for adjusting mesh width.</strong> Scaling model dimensions causes internal algorithm thresholds (minimum cuttable amount, floating-point-to-fraction range) to become invalid, producing irregular geometry artifacts. Adjust resolution settings instead.</p>
</div>
<h3 id="34-xml-configuration">3.4 XML Configuration</h3>
<p>Resolution can also be set in the <code>.hincproj</code> file or changed mid-simulation via NC code comments:</p>
<pre><code>T01 M06 (;@MachiningResolution_mm=0.03125;)
</code></pre>
<hr>
<h2 id="4-run-simulation">4. Run Simulation</h2>
<p>There are four ways to drive the simulation, plus player controls.</p>
<h3 id="41-playncfile--execute-from-a-file">4.1 PlayNcFile — Execute from a File</h3>
<p><a class="xref" href="../api/Hi.MachiningProcs.SessionShell.html#Hi_MachiningProcs_SessionShell_PlayNcFile_">PlayNcFile</a><small>(API)</small> reads and executes an NC file.</p>
<pre><code class="lang-csharp">PlayNcFile(&quot;NC/file1.nc&quot;);
</code></pre>
<h3 id="42-plaync--execute-from-a-string">4.2 PlayNc — Execute from a String</h3>
<p><a class="xref" href="../api/Hi.MachiningProcs.SessionShell.html#Hi_MachiningProcs_SessionShell_PlayNc_">PlayNc</a><small>(API)</small> executes NC code directly from a string, useful for programmatic or dynamically generated commands.</p>
<pre><code class="lang-csharp">double x = 10.0;
PlayNc($&quot;G01 X{x} Y20 F100&quot;, &quot;Generated Command&quot;);
</code></pre>
<h3 id="43-playcsvfile--drive-from-csv-data">4.3 PlayCsvFile — Drive from CSV Data</h3>
<p><a class="xref" href="../api/Hi.MachiningProcs.SessionShell.html#Hi_MachiningProcs_SessionShell_PlayCsvFile_">PlayCsvFile</a><small>(API)</small> drives the simulation from a CSV file containing axis positions, spindle speed, and feed rate.</p>
<pre><code class="lang-csharp">PlayCsvFile(&quot;Data/file1.csv&quot;);
</code></pre>
<p>Required CSV columns (default headers): <code>MC.X</code>, <code>MC.Y</code>, <code>MC.Z</code>, <code>ToolId</code>, <code>SpindleSpeed_rpm</code>, <code>Feedrate_mmdmin</code>. Optional: <code>MC.A</code>, <code>MC.B</code>, <code>MC.C</code>, <code>ActualTime</code>, <code>StepDuration</code>.</p>
<p>Headers and timestamp values may be wrapped in double quotes; the parser strips them. <code>ActualTime</code> accepts either <code>HH:mm:ss.fff</code> or an absolute <code>yyyy-MM-dd HH:mm:ss.ffffff</code> form (the absolute form is required when chaining with <a class="xref" href="../api/Hi.MachiningProcs.SessionShell.html#Hi_MachiningProcs_SessionShell_MapSeriesByCsvFile_">MapSeriesByCsvFile</a><small>(API)</small>, which matches by <code>TimeTag</code>):</p>
<pre><code class="lang-csv">&quot;ActualTime&quot;,&quot;Feedrate_mmdmin&quot;,&quot;MC.X&quot;,&quot;MC.Y&quot;,&quot;MC.Z&quot;,&quot;SpindleSpeed_rpm&quot;,&quot;ToolId&quot;
&quot;2026-03-16 15:57:45.559000&quot;,10000.0,-351.745,-244.799,-215.799,1270,1
&quot;2026-03-16 15:57:45.705000&quot;,10000.0,-351.745,-244.799,-215.799,1270,1
</code></pre>
<p>When a real-world controller log includes extra columns (e.g., <code>t_receive</code>, <code>cnc_delay_s</code>, <code>status</code>) or uses alternative column names (<code>X</code>/<code>Y</code>/<code>Z</code>, <code>feedrate</code>, <code>spindle_speed</code>), preprocess the file to drop or rename columns before passing it to <a class="xref" href="../api/Hi.MachiningProcs.SessionShell.html#Hi_MachiningProcs_SessionShell_PlayCsvFile_">PlayCsvFile</a><small>(API)</small>.</p>
<div class="TIP">
<h5>Tip</h5>
<p>CSV files exported by <a class="xref" href="../api/Hi.MachiningProcs.SessionShell.html#Hi_MachiningProcs_SessionShell_WriteStepFiles_">WriteStepFiles</a><small>(API)</small> can be directly read back with <a class="xref" href="../api/Hi.MachiningProcs.SessionShell.html#Hi_MachiningProcs_SessionShell_PlayCsvFile_">PlayCsvFile</a><small>(API)</small>.</p>
</div>
<h3 id="44-playclfile--drive-from-a-cutter-location-file">4.4 PlayClFile — Drive from a Cutter-Location File</h3>
<p><a class="xref" href="../api/Hi.MachiningProcs.SessionShell.html#Hi_MachiningProcs_SessionShell_PlayClFile_">PlayClFile</a><small>(API)</small> replays an NX cutter-location file (CLSF / APT-source, <code>.cls</code>) directly as tool motion — the machine-independent CAM toolpath, <strong>before</strong> it is post-processed for a specific machine.</p>
<pre><code class="lang-csharp">PlayClFile(&quot;CL/part-op10.cls&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 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>
<thead>
<tr>
<th>Command</th>
<th>Purpose</th>
</tr>
</thead>
<tbody>
<tr>
<td><a class="xref" href="../api/Hi.MachiningProcs.SessionShell.html#Hi_MachiningProcs_SessionShell_Pace">Pace()</a><small>(API)</small></td>
<td>Insert a pausable checkpoint</td>
</tr>
<tr>
<td><a class="xref" href="../api/Hi.MachiningProcs.SessionShell.html#Hi_MachiningProcs_SessionShell_Pause">Pause()</a><small>(API)</small></td>
<td>Pause execution</td>
</tr>
<tr>
<td><a class="xref" href="../api/Hi.MachiningProcs.SessionShell.html#Hi_MachiningProcs_SessionShell_Reset">Reset()</a><small>(API)</small></td>
<td>Reset player state</td>
</tr>
</tbody>
</table>
<pre><code class="lang-csharp">PlayNcFile(&quot;NC/file1.nc&quot;);
if (someCondition)
Pause();
</code></pre>
<hr>
<h2 id="5-view-results">5. View Results</h2>
<h3 id="51-meshed-geometry">5.1 Meshed Geometry</h3>
<p>After simulation the workpiece geometry is a <strong>Meshed Geometry</strong> (cubic mesh). You can save and reload it to avoid re-computing the initial shape:</p>
<pre><code class="lang-csharp">WriteMeshedGeom(&quot;Cache/file1.wct&quot;);
ExportMeshedGeomToStl(&quot;Output/file1.stl&quot;);
</code></pre>
<p>To reload a saved geometry for a subsequent run:</p>
<pre><code class="lang-csharp">ReadMeshedGeom(&quot;Cache/init.wct&quot;);
PlayNcFile(&quot;NC/file1.nc&quot;);
</code></pre>
<h3 id="52-step-data-inspection">5.2 Step Data Inspection</h3>
<p>Each simulation step carries rich data (force, torque, power, thermal, wear). Access individual steps:</p>
<pre><code class="lang-csharp">var step = GetMillingStep(100);
Message($&quot;ToolId={step.ToolId}, Force={step.MaxAbsForce_N} N&quot;);
</code></pre>
<p>Total step count:</p>
<pre><code class="lang-csharp">var total = StepCount;
Message($&quot;Total steps: {total}&quot;);
</code></pre>
<h3 id="53-export-data">5.3 Export Data</h3>
<p>Export step-level CSV:</p>
<pre><code class="lang-csharp">WriteStepFiles(&quot;Output/[NcName].step.csv&quot;);
</code></pre>
<p>Export waveform (shot) CSV:</p>
<pre><code class="lang-csharp">WriteShotFiles(&quot;Output/[NcName].shot.csv&quot;, 1);
</code></pre>
<h3 id="54-messages">5.4 Messages</h3>
<p>Use messages to log and track simulation progress:</p>
<pre><code class="lang-csharp">Message(&quot;Simulation complete&quot;);
AppendMessagesToFile(&quot;Output/messages.txt&quot;);
</code></pre>
<hr>
<h2 id="troubleshooting">Troubleshooting</h2>
<table>
<thead>
<tr>
<th>Symptom</th>
<th>Likely Cause</th>
<th>Fix</th>
</tr>
</thead>
<tbody>
<tr>
<td>Very slow simulation, large pink trail behind the tool</td>
<td>Geometry removal is the bottleneck (mesh too fine)</td>
<td>Increase <code>MachiningResolution_mm</code> (coarser mesh)</td>
</tr>
<tr>
<td>Very slow simulation, but a coarser mesh doesn't help</td>
<td>Limited by step count (per-step physics)</td>
<td>Reduce steps via <code>MachiningMotionResolution</code> (e.g. <code>ScaledFeedPerCycle(2)</code>)</td>
</tr>
<tr>
<td>Irregular bumps on geometry</td>
<td>Scaled model dimensions instead of resolution</td>
<td>Use resolution settings only; see warning above</td>
</tr>
<tr>
<td>Display lag</td>
<td><code>DispCache_Mb</code> too large</td>
<td>Reduce display cache (&lt; 1000 Mb recommended)</td>
</tr>
<tr>
<td>Empty step data</td>
<td>Simulation not run or tool not engaging workpiece</td>
<td>Verify tool path intersects the workpiece</td>
</tr>
</tbody>
</table>
<h2 id="see-also">See Also</h2>
<ul>
<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>
<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>