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:
@@ -88,6 +88,32 @@
|
||||
<h1 id="coolant">Coolant</h1>
|
||||
|
||||
<p>Models the cutting-zone cooling for the milling temperature FEM. Lives on <a class="xref" href="../../api/Hi.Physics.CoolantHeatCondition.html">CoolantHeatCondition</a><small>(API)</small>; consumed by <a class="xref" href="../../api/Hi.Physics.MillingTemperatureUtil.html">MillingTemperatureUtil</a><small>(API)</small> every simulation step.</p>
|
||||
<h2 id="pick-a-cooling-type">Pick a cooling type</h2>
|
||||
<p>You do not need to know any heat-transfer numbers to set up cooling. In the Player control tree, open <strong>Equipment Setup → Coolant</strong>, click <strong>Select → Browse Resource…</strong>, and pick the ready-made <code>.CoolantHeatCondition</code> file for the cooling your machine uses — exactly the way a workpiece material file is picked:</p>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
<th>Shipped file</th>
|
||||
<th>Pick it when</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td><strong>StandardForcedAir</strong></td>
|
||||
<td>The machine only blows air at the cutter — no liquid coolant.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><strong>StandardWaterSolubleCoolant</strong></td>
|
||||
<td>Water-based emulsion coolant, the common flood coolant. (A fresh project already carries these values.)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><strong>StandardOilBasedCoolant</strong></td>
|
||||
<td>Neat-oil cutting fluid: better lubrication, noticeably less heat removal than water-based.</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<p>Loading a file fills the <strong>Name / Note</strong> and every property field shown below them. For a customized setup, tune the fields directly and keep the result as your own named file with <strong>Save As…</strong> — it can be loaded back later, or from another project.</p>
|
||||
<p>That is the whole end-user setup. Everything below explains what the values mean.</p>
|
||||
<h2 id="nc-program-drives-the-mode">NC program drives the mode</h2>
|
||||
<p>The parser reads M07/M08/M09 into <a class="xref" href="../../api/Hi.Numerical.CoolantMode.html">CoolantMode</a><small>(API)</small> and carries it on every <a class="xref" href="../../api/Hi.MachiningSteps.MachineMotionStep.html">MachineMotionStep</a><small>(API)</small>. The FEM picks the effective convection coefficient at run time from that mode.</p>
|
||||
<table>
|
||||
@@ -102,7 +128,7 @@
|
||||
<tr>
|
||||
<td><code>M08</code></td>
|
||||
<td><code>Flood</code></td>
|
||||
<td><code>CoolantConvectionCoefficient_Wdm2K</code> (baseline you set)</td>
|
||||
<td><code>CoolantConvectionCoefficient_Wdm2K</code> (baseline of the chosen type)</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>M07</code></td>
|
||||
@@ -117,7 +143,46 @@
|
||||
</tbody>
|
||||
</table>
|
||||
<p>Before the first M07/M08/M09 the mode is <code>UnDefined</code>; the FEM treats it as <code>Off</code>.</p>
|
||||
<p>For <strong>StandardForcedAir</strong> (dry cutting) the machine has no liquid circuit, so even <code>M08</code> only means “air blast on” — its flood baseline is an air-blast coefficient, not a liquid one.</p>
|
||||
<h2 id="what-each-shipped-file-sets">What each shipped file sets</h2>
|
||||
<p>Each shipped cooling type is also a static preset on <a class="xref" href="../../api/Hi.Physics.CoolantHeatCondition.html">CoolantHeatCondition</a><small>(API)</small> (<code>StandardForcedAir</code>, <code>StandardWaterSolubleCoolant</code>, <code>StandardOilBasedCoolant</code>) — the same pattern as <code>WorkpieceMaterial.Al6061T6</code>; the resource files are generated from them:</p>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
<th>Preset / file</th>
|
||||
<th>Flood baseline W/(m²·K)</th>
|
||||
<th>Mist ratio</th>
|
||||
<th>Off W/(m²·K)</th>
|
||||
<th>Temperature °C</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td><code>StandardForcedAir</code></td>
|
||||
<td>100</td>
|
||||
<td>0.5</td>
|
||||
<td>50</td>
|
||||
<td>25</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>StandardWaterSolubleCoolant</code></td>
|
||||
<td>1 000</td>
|
||||
<td>0.5</td>
|
||||
<td>50</td>
|
||||
<td>25</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>StandardOilBasedCoolant</code></td>
|
||||
<td>300</td>
|
||||
<td>0.5</td>
|
||||
<td>50</td>
|
||||
<td>25</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<p>The baselines are engineering defaults from the literature ranges below; when you have dynamometer / thermocouple data for your own system, tune the fields and save your own file instead. API side: <code>ApplyPreset</code> copies a preset in place; <code>MatchStandardPreset</code> maps values back to a preset name.</p>
|
||||
<h2 id="properties">Properties</h2>
|
||||
<p>These are the fields shown under Name / Note in the Coolant panel:</p>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
@@ -135,7 +200,7 @@
|
||||
<tr>
|
||||
<td><code>CoolantConvectionCoefficient_Wdm2K</code></td>
|
||||
<td>1 000</td>
|
||||
<td>Flood baseline. Water-based emulsion ≈ 1 000–3 000, oil ≈ 100–500.</td>
|
||||
<td>Flood baseline. Water-based emulsion ≈ 1 000–3 000, oil ≈ 100–500, forced air ≈ 10–500.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>MistFloodConvectionRatio</code></td>
|
||||
@@ -147,6 +212,11 @@
|
||||
<td>50</td>
|
||||
<td>Forced air inside a running enclosure. Natural air ≈ 5–25.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>Name</code> / <code>Note</code></td>
|
||||
<td>—</td>
|
||||
<td>From the loaded file / preset; <strong>Save As…</strong> renames the condition after the file. Legacy projects without a name still work.</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h2 id="why-the-mist-ratio-defaults-to-05">Why the mist ratio defaults to 0.5</h2>
|
||||
@@ -155,15 +225,23 @@
|
||||
<h5>Note</h5>
|
||||
<p>Further reading: UNIST <em>MQL Handbook</em> (source of the “about half” rule), ANEBON mist-vs-flood AISI 1045 tests, Mukesh et al. <em>IEJ</em> May 2023 review on sustainable machining. Use these only to dig deeper — the <code>0.5</code> default is already calibrated from them.</p>
|
||||
</div>
|
||||
<h2 id="coolant-files-workpiecematerial-pattern">Coolant files (WorkpieceMaterial pattern)</h2>
|
||||
<p><code>MachiningEquipment.CoolantHeatConditionFile</code> tracks an optional <code>.CoolantHeatCondition</code> side-file, exactly like <code>Workpiece.WorkpieceMaterialFile</code> tracks a material file:</p>
|
||||
<ul>
|
||||
<li><strong>No file (default):</strong> the condition serializes inline in the <code>.hincproj</code>, byte-compatible with pre-pattern readers.</li>
|
||||
<li><strong>File tracked:</strong> the project save externalizes the condition as <code><CoolantHeatCondition><XmlSource>relPath</XmlSource></CoolantHeatCondition></code> and (re)writes the side-file. Loading a file installs it in place of the current condition and records the reference (<code>XFactory.GenByFile<CoolantHeatCondition></code>); a file loaded from the resource folder is copied into the project on the next save (self-contained project root).</li>
|
||||
</ul>
|
||||
<h2 id="xml">XML</h2>
|
||||
<pre><code class="lang-xml"><CoolantHeatCondition>
|
||||
<Name>StandardOilBasedCoolant</Name>
|
||||
<Note>Oil-based cutting fluid (neat oil).</Note>
|
||||
<CoolantTemperature_C>25</CoolantTemperature_C>
|
||||
<CoolantConvectionCoefficient_Wdm2K>1000</CoolantConvectionCoefficient_Wdm2K>
|
||||
<CoolantConvectionCoefficient_Wdm2K>300</CoolantConvectionCoefficient_Wdm2K>
|
||||
<MistFloodConvectionRatio>0.5</MistFloodConvectionRatio>
|
||||
<OffConvectionCoefficient_Wdm2K>50</OffConvectionCoefficient_Wdm2K>
|
||||
</CoolantHeatCondition>
|
||||
</code></pre>
|
||||
<p>Omit the last two elements to accept the defaults.</p>
|
||||
<p><code>Name</code>/<code>Note</code> are optional (pre-preset files omit them); omit the last two elements to accept the defaults. The same element saved standalone is the <code>.CoolantHeatCondition</code> file format; inside a <code>.hincproj</code> it may instead appear as the <code><XmlSource></code> reference shown above.</p>
|
||||
|
||||
</article>
|
||||
|
||||
|
||||
Reference in New Issue
Block a user