Archived
258 lines
13 KiB
HTML
258 lines
13 KiB
HTML
<!DOCTYPE html>
|
|
<html>
|
|
<head>
|
|
<meta charset="utf-8">
|
|
<title>Starting and Stepping | HiAPI-C# 2025 </title>
|
|
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
|
<meta name="title" content="Starting and Stepping | 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 "{query}"">
|
|
<meta name="loc:searchNoResults" content="No results for "{query}"">
|
|
<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="">
|
|
<h1 id="starting-and-stepping">Starting and Stepping</h1>
|
|
|
|
<p>Six buttons and four keys drive a run. What each of them does is short to say; <strong>which of them you
|
|
can press at a given moment is the part worth learning</strong>, because the availability of a button is
|
|
what tells you where the run actually is.</p>
|
|
<h2 id="where-it-is">Where it is</h2>
|
|
<p>The Execution page at <code>/execution</code>. The transport sits along the top of the editor panel in the left
|
|
dock, and it is mounted for the <strong>Execution</strong> root and every node beneath it — so it stays reachable
|
|
while you are editing a Mission command one level in. There is exactly one of it on the page, and it
|
|
is the thing that binds <kbd>F5</kbd> to <kbd>F8</kbd>.</p>
|
|
<h2 id="the-six-controls">The six controls</h2>
|
|
<table>
|
|
<thead>
|
|
<tr>
|
|
<th>Control</th>
|
|
<th>Key</th>
|
|
<th>What it does</th>
|
|
</tr>
|
|
</thead>
|
|
<tbody>
|
|
<tr>
|
|
<td><strong>Start</strong> / <strong>Resume</strong></td>
|
|
<td><kbd>F5</kbd></td>
|
|
<td>Starts the run, or resumes a paused one</td>
|
|
</tr>
|
|
<tr>
|
|
<td><strong>Pause</strong></td>
|
|
<td><kbd>F6</kbd></td>
|
|
<td>Holds the run where it is</td>
|
|
</tr>
|
|
<tr>
|
|
<td><strong>Run one NC line</strong></td>
|
|
<td><kbd>F7</kbd></td>
|
|
<td>Advances by one line of the program</td>
|
|
</tr>
|
|
<tr>
|
|
<td><strong>Run one machining step</strong></td>
|
|
<td><kbd>F8</kbd></td>
|
|
<td>Advances by one machining step</td>
|
|
</tr>
|
|
<tr>
|
|
<td><strong>Stop</strong></td>
|
|
<td>—</td>
|
|
<td>Ends the run</td>
|
|
</tr>
|
|
<tr>
|
|
<td><strong>Reset</strong></td>
|
|
<td>—</td>
|
|
<td>Unwinds the session back to the start</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
<p>Start and Resume are the same button, not two: it reads <strong>Start</strong> from the beginning and <strong>Resume</strong>
|
|
once the run is paused. The two single-advance buttons share one icon and are told apart by a small
|
|
letter in the corner — <strong>L</strong> for a line, <strong>S</strong> for a step. Stop and Reset carry no key.</p>
|
|
<p>Reset unwinds in the background: the button shows a spinner while it works and the rest of the
|
|
application stays usable.</p>
|
|
<h2 id="one-line-is-not-one-step">One line is not one step</h2>
|
|
<p>The two single-advance buttons exist because the two units do not line up. One line of program can
|
|
produce many machining steps — a long move at a fine machining resolution is dozens of them — while
|
|
another line produces none at all, because a tool change or a coordinate selection is a sentence with
|
|
no motion under it. So advancing by one line and advancing by one step land in different places.</p>
|
|
<p>Use <strong>Run one NC line</strong> when you are following the program: it stops where the next line begins,
|
|
which is where the program text you are reading changes. Use <strong>Run one machining step</strong> when you are
|
|
following the cut: it stops at the next thing the machine did, which is the unit the Step Info column
|
|
and the strip charts are keyed on. Stepping by step through a single long move is how you watch one
|
|
cut develop; stepping by line skips straight past it.</p>
|
|
<h2 id="what-you-can-press-and-when">What you can press, and when</h2>
|
|
<p>The whole bar is dead until two things are true: <strong>a project is open</strong>, and <strong>the page's 3D canvas
|
|
has connected to the service</strong>. The second one is easy to miss — the connection is what binds the
|
|
run engine to this page, so a canvas that has dropped its connection leaves every transport button
|
|
greyed even though the project is plainly loaded. The connection badge on the menu bar is where you
|
|
check that.</p>
|
|
<p>With both in place, availability follows the run state:</p>
|
|
<table>
|
|
<thead>
|
|
<tr>
|
|
<th>Control</th>
|
|
<th>Available while the run is</th>
|
|
</tr>
|
|
</thead>
|
|
<tbody>
|
|
<tr>
|
|
<td><strong>Start</strong> / <strong>Resume</strong></td>
|
|
<td>ready, or paused</td>
|
|
</tr>
|
|
<tr>
|
|
<td><strong>Pause</strong></td>
|
|
<td>running</td>
|
|
</tr>
|
|
<tr>
|
|
<td><strong>Run one NC line</strong> / <strong>Run one machining step</strong></td>
|
|
<td>ready, or paused</td>
|
|
</tr>
|
|
<tr>
|
|
<td><strong>Stop</strong></td>
|
|
<td>running, paused, or finished</td>
|
|
</tr>
|
|
<tr>
|
|
<td><strong>Reset</strong></td>
|
|
<td>any time a project is open</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
<p><strong>Nothing steps a moving run.</strong> Both single-advance buttons are unavailable while the run is going,
|
|
so the way to step through something you are already watching is to pause first and then step. That
|
|
is the single most useful thing in the table: the buttons are not refusing you, they are telling you
|
|
the run has not stopped yet.</p>
|
|
<p>The bar at rest, with the demo project open and nothing run yet, at <code>/execution</code>. Start, the two
|
|
single-advance buttons and Reset are live; Pause and Stop are greyed, because there is no run to hold
|
|
or to end — and the two single-advance buttons carry the <strong>L</strong> and the <strong>S</strong> that tell them apart. The
|
|
badge on the <strong>Execution</strong> tree item reads <em>ready</em>, and the block on the canvas is uncut.</p>
|
|
<p><img src="running-a-simulation-img/transport-ready.en.png" alt="The Execution page with the Control Tree on the left showing the Mission and Program branches, a green ready badge on the Execution item, the transport row above the editor panel with the pause and stop buttons greyed, and the 3D canvas showing an uncut rectangular aluminium block on its fixture"></p>
|
|
<h2 id="reading-the-run-state">Reading the run state</h2>
|
|
<p>The state rides the <strong>Execution</strong> item in the Control Tree as a coloured badge — <em>ready</em>, <em>running</em>,
|
|
<em>paused</em>, <em>finished</em> — so it is readable from wherever you are in the tree rather than only from the
|
|
transport. The footer along the bottom of the window carries the session's own messages beside it.</p>
|
|
<p>The same page with the mission paused part way through. The badge now reads <em>paused</em> in orange, Pause
|
|
has gone grey, and Stop has joined the live ones — so the bar alone tells you a run is open and held.
|
|
On the canvas the tool path the run has laid down so far is now drawn over the block, and the tabs
|
|
under it are counting what the run has reported: this mission trips the collision check, which is
|
|
what the red line in the footer and the number on <strong>Step Diagnostics</strong> are saying.</p>
|
|
<p><img src="running-a-simulation-img/transport-paused.en.png" alt="The Execution page with the Control Tree on the left, its Execution item carrying an orange paused badge, the transport row above the editor panel with the pause button greyed and the rest live, the 3D canvas showing the block with the covered tool path drawn over it, and a footer line reporting a collision"></p>
|
|
<h2 id="the-keys-and-where-they-stop">The keys, and where they stop</h2>
|
|
<p><kbd>F5</kbd> to <kbd>F8</kbd> are bound only while the Execution page is the one on screen. On every
|
|
other page <kbd>F5</kbd> is the browser's own reload, and the same is true here in two cases: when
|
|
the button a key drives is unavailable at that moment, and when the focus is inside a text field.</p>
|
|
<div class="WARNING">
|
|
<h5>Warning</h5>
|
|
<p>That exception bites hardest on <kbd>F5</kbd> during a run. Start is unavailable while the run is
|
|
going, so the key falls through to the browser, the page reloads, and the session goes with it.
|
|
Pause with <kbd>F6</kbd> first.</p>
|
|
</div>
|
|
<h2 id="see-also">See Also</h2>
|
|
<ul>
|
|
<li><a href="index.html">Running a Simulation</a> — the rest of running a job</li>
|
|
<li><a href="building-a-mission.html">Building a Mission</a> — the command list this transport plays</li>
|
|
<li><a href="watching-the-run.html">Watching the Run</a> — the canvas and the charts that fill while this plays</li>
|
|
<li><a href="inspecting-a-step.html">Inspecting a Step</a> — the column that reads whichever step you stopped on</li>
|
|
<li><a href="when-something-goes-wrong.html">When Something Goes Wrong</a> — what to read when the run does not do what you expected</li>
|
|
<li><a href="../basics/the-app-window.html">The Application Window</a> — the menu bar's connection badge, and the footer this page's state is reported in</li>
|
|
<li><a href="a-mission-that-resumes.html">A Mission That Resumes</a> — how to lay the mission out so a stopped run restarts from where it got to</li>
|
|
<li><a class="xref" href="../../anatomy/execution/execution-tool-bar.html">Execution Tool Bar</a> — the component behind these buttons: the enable rules, the status feed and the key bindings</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>
|