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-16 00:00:49 +08:00
parent 1a75503105
commit bfa3106a69
60 changed files with 696 additions and 268 deletions
Download Patch File Download Diff File Expand all files Collapse all files
App/wwwroot/HiAPI-docsite/manual/basics/finding-your-way.html
+5 -5
View File
@@ -96,7 +96,7 @@ described.</p>
job, in the order a job uses it:</p>
<ul>
<li><strong>Tool House</strong> — the tools, one editor per tool</li>
<li><strong>General Setup</strong> — the equipment: the machine tool, the spindle capability, the background and
<li><strong>General Setup</strong> — the equipment: the machine tool, the spindle capability, the ambient and
coolant conditions, the fixture, the workpiece and the controller</li>
<li><strong>Execution</strong> — the run: the mission that is executed, the program as it was played, and what the
run reports</li>
@@ -124,9 +124,9 @@ address is <code>/preference/log</code>.</li>
path of the selection — <em>General Setup / Workpiece / Anchor / Geom To Fixture</em> — which is also how
these pages name a place in prose; the header shows as much of it as the dock is wide, so a deep
path arrives truncated.</p>
<p>General Setup's tree has one root, <strong>General Setup</strong>, holding <strong>Machine Tool</strong>, <strong>Spindle
Capability</strong>, <strong>Background</strong>, <strong>Coolant</strong>, <strong>Fixture</strong>, <strong>Workpiece</strong> and <strong>Controller</strong>, in that
order. With a project open, a <strong>CSV Controller</strong> and a <strong>CL Controller</strong> node follow, each behind
<p>General Setup's tree has four roots — <strong>Mechanism</strong> (holding <strong>Machine Tool</strong>, <strong>Fixture</strong> and
<strong>Workpiece</strong>), <strong>Spindle Capability</strong>, <strong>Environment</strong> (holding <strong>Ambient Temperature</strong> and
<strong>Coolant</strong>) and <strong>Controller</strong> — in that order. With a project open, a <strong>CSV Controller</strong> and a <strong>CL Controller</strong> node follow, each behind
its own Preference checkbox — as siblings of Controller at the same level, not as children of it.
With no project open neither node is built, whatever the preferences say. Execution's tree has one
root, <strong>Execution</strong>, holding <strong>Mission</strong> above <strong>Program</strong>.</p>
@@ -253,7 +253,7 @@ page's node instead:</p>
</tr>
<tr>
<td><code>/equipment/background-coolant</code></td>
<td>General Setup, the Background item</td>
<td>General Setup, the Environment root (Ambient Temperature / Coolant)</td>
</tr>
<tr>
<td><code>/mission</code></td>
App/wwwroot/HiAPI-docsite/manual/basics/projects.html
+1 -1
View File
@@ -88,7 +88,7 @@
<h1 id="projects">Projects</h1>
<p>A project is the whole of what a simulation runs against: the machine tool, the spindle capability,
the background and coolant conditions, the fixture, the workpiece, the tool house, the controller and
the ambient and coolant conditions, the fixture, the workpiece, the tool house, the controller and
the NC programs a mission plays. It is a project file together with the folder that file sits in, and
the <strong>Project</strong> dropdown on the menu bar is where one is created, opened, saved and closed. The
equipment and mission screens are editors on whichever project is open, so a change of project