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/manual/setup/coolant.html
T
2026-09-16 00:00:49 +08:00

235 lines
12 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>Coolant | HiAPI-C# 2025 </title>
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<meta name="title" content="Coolant | 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="Equipment/Coolant">
<h1 id="coolant">Coolant</h1>
<p>Two thermal settings sit beside each other in the equipment tree: how the cutting zone is cooled,
and how warm the shop is around it. Both feed the milling-temperature model, so they move computed
temperatures and everything downstream of them — and setting them needs no heat-transfer numbers at
all, because the cooling types ship as ready-made files.</p>
<h2 id="where-it-is">Where it is</h2>
<p>The General Setup page, at <code>/general-setup</code>, reached from the menu bar's <strong>Page</strong> dropdown.
<strong>Ambient Temperature</strong> (<code>/general-setup?tree=equipment/background/environment-temperature</code>) and
<strong>Coolant</strong> (<code>/general-setup?tree=equipment/background/coolant</code>) are the two leaves of the Control
Tree's <strong>Environment</strong> root, between Spindle Capability and Controller (the ids keep the legacy
<code>background</code> spelling). Both are inert until a project is
open: the fields are disabled and the panel says so.</p>
<p>The <strong>Coolant</strong> leaf selected on a demo project. The panel under the tree opens with the file row —
the <strong>Select</strong> dropdown, the path field reading <em>No coolant file (saved inline)</em>, and <strong>Save As&hellip;</strong>
— then the read-only <strong>Name</strong> and <strong>Note</strong> of whatever file is loaded, and then the condition's own
values. Neither leaf puts anything in the middle column.</p>
<p><img src="coolant-img/coolant-leaf.en.png" alt="The Coolant leaf of the Control Tree selected on the General Setup page, its panel showing the Select dropdown and empty file path above read-only Name and Note fields, then a Coolant Temperature of 25 °C and a Flood Convection Coefficient of 1000 W/(m²·K) with the app's own guidance underneath it"></p>
<h2 id="pick-a-cooling-type">Pick a cooling type</h2>
<p>The three standard cooling types ship as ready-made <code>.CoolantHeatCondition</code> files, so picking one
<em>is</em> the cooling-type selection — exactly the way a workpiece material file is picked.</p>
<ol>
<li>Select the <strong>Coolant</strong> leaf.</li>
<li>Open the <strong>Select</strong> dropdown at the left of the file row and choose <strong>Browse Resource&hellip;</strong>. It
opens the file picker in the shipped library's own coolant folder, so the three files below are
what it lists. <strong>Browse&hellip;</strong> above it opens the same picker without that jump, which is how a
condition you saved yourself is reached.</li>
<li>Pick the file that matches the machine.</li>
</ol>
<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.</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 read-only <strong>Name</strong> and <strong>Note</strong> and every value below them, and reports the
name it loaded.</p>
<p><strong>A project nobody has touched here is not neutral.</strong> Every project carries a coolant condition from
the moment it exists, and it starts on the water-soluble numbers — 25 °C, a flood baseline of
1000 W/(m²·K), a mist ratio of 0.5 and 50 W/(m²·K) with the coolant off. The read-only <strong>Name</strong> is
blank, because no file has been picked, and that blank is the only sign that nobody chose these
values. A dry-cutting machine left alone therefore simulates as though it were flooded with
water-soluble coolant, and its computed temperatures come out low.</p>
<h2 id="the-four-values">The four values</h2>
<p>They are visible whether or not a file is loaded, and editing one tunes <em>this project's</em> copy rather
than the file it came from. Each carries the app's own working range as a hint:</p>
<table>
<thead>
<tr>
<th>Field</th>
<th>What it is</th>
<th>Range the panel suggests</th>
</tr>
</thead>
<tbody>
<tr>
<td><strong>Coolant Temperature</strong> (°C)</td>
<td>The temperature of the coolant as it arrives at the cut</td>
<td>—</td>
</tr>
<tr>
<td><strong>Flood Convection Coefficient</strong> (W/(m²·K))</td>
<td>Heat removal with the coolant on</td>
<td>Forced air 10–500; typical liquid coolant 1000–10000</td>
</tr>
<tr>
<td><strong>Mist / Flood Ratio</strong></td>
<td>Mist heat removal relative to flood</td>
<td>Typically 0.4–0.8</td>
</tr>
<tr>
<td><strong>Off (Air) Convection Coefficient</strong> (W/(m²·K))</td>
<td>Heat removal with the coolant off</td>
<td>Natural air 5–25; forced air inside an enclosure about 50</td>
</tr>
</tbody>
</table>
<p>Negative temperatures are accepted, for cryogenic coolant; the three convection coefficients cannot
go below zero.</p>
<p>Which of the three coefficients is in force at any moment is not decided here — the NC program's own
M07 / M08 / M09 decide it, step by step. That, and what the numbers do to the simulation, are
<a class="xref" href="../../technique/milling-physics/coolant-model.html">Coolant Model</a>.</p>
<h2 id="keeping-a-tuned-condition">Keeping a tuned condition</h2>
<p><strong>Save As&hellip;</strong> writes the current values out as a <code>.CoolantHeatCondition</code> file in the project folder
and starts tracking it, so the project saves a reference to the file instead of a copy of the
values. It offers a name taken from the loaded condition; a file picked from the shipped library
loses its <code>.default</code> marker on the way, because that marker means <em>shipped</em> and a file you saved is
yours.</p>
<p>The result is loadable into the next project through the same <strong>Select</strong> dropdown — which is the
point of saving one: a shop with its own measured coolant performance describes it once.</p>
<h2 id="ambient-temperature">Ambient temperature</h2>
<p>The <strong>Ambient Temperature</strong> leaf carries a single field of the same name, in °C: the shop-floor ambient
temperature — the temperature the workpiece, the cutter, the chips and the spindle start at, and the
one the spindle cools toward. The cutting zone itself convects to the <strong>Coolant</strong> leaf's coolant
temperature, not to this one. It defaults to 25 °C, it belongs to the project exactly as the coolant
condition does, and it is read by the same milling-temperature model and by the feed optimizer, so
it is not a display setting.</p>
<p>Set it to the shop's real ambient temperature. There is no file to load and nothing else to
configure: one number, applied to the whole project.</p>
<h2 id="see-also">See Also</h2>
<ul>
<li><a class="xref" href="../../technique/milling-physics/coolant-model.html">Coolant Model</a> — the coefficients, the M-code that selects one, the shipped presets and the file format</li>
<li><a class="xref" href="../../anatomy/general-setup/background-coolant.html">Environment: Ambient Temperature / Coolant Page</a> — the Control-Tree editor for these values, field by field</li>
<li><a href="index.html">Setup</a> — the rest of the pre-simulation configuration</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>