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/run/inspecting-a-step.html
T
2026-09-11 03:46:11 +08:00

233 lines
14 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>Inspecting a Step | HiAPI-C# 2025 </title>
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<meta name="title" content="Inspecting a Step | 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="">
<h1 id="inspecting-a-step">Inspecting a Step</h1>
<p>Once a strip chart has told you <em>where</em>, the Step Info column tells you <em>what</em>. Every panel in it is
a view of the one selected step — except the panel at the top, which deliberately is not, and the
reason for that exception is worth knowing before you read the column.</p>
<h2 id="where-it-is">Where it is</h2>
<p>The Execution page at <code>/execution</code>, rightmost column, switched on and off from the quick-toggles on
the menu bar. Most of it stays empty until a step is selected, and selecting one is a click on a
strip chart or on the tool path in the 3D canvas.</p>
<h2 id="sentence-syntax-and-why-it-sits-outside">Sentence Syntax, and why it sits outside</h2>
<p>The top panel is the odd one out, and it is placed outside the step group on purpose: <strong>a line of NC
need not produce a machining step at all</strong>. A tool change, a coordinate selection or a comment is a
sentence with no motion under it, so a panel that reads sentences cannot be a member of a group
keyed on steps.</p>
<p>It shows the sentence's own text and the reading the interpreter made of it, with a badge naming the
file, the line and the sentence, and a button that copies the parsed form.</p>
<p>Its two empty messages say different things, and the difference matters:</p>
<ul>
<li><strong>No sentence selected</strong> — nothing is picked yet.</li>
<li><strong>This line has no executed SyntaxPiece</strong> — a line <em>is</em> picked, and it did not run in this session.
That is an answer, not a gap: the line was skipped, or it belongs to a pass the run never reached,
or the session has been reset since.</li>
</ul>
<p>The sentence it follows comes from two directions: selecting a step brings its sentence here, and so
does clicking a line in a Program file panel. That is the bridge between reading the program and
reading the run.</p>
<h2 id="the-rest-of-the-column">The rest of the column</h2>
<p>Below the group bar every panel is a view of the same selected step.</p>
<table>
<thead>
<tr>
<th>Panel</th>
<th>What it shows</th>
</tr>
</thead>
<tbody>
<tr>
<td><strong>Step Properties</strong></td>
<td>The step's values, for the fields you have chosen</td>
</tr>
<tr>
<td><strong>CWE</strong></td>
<td>The cutter–workpiece engagement — what the cutter was actually touching</td>
</tr>
<tr>
<td><strong>Sim Cutting Force Cycle</strong></td>
<td>Simulated cutting force through one spindle revolution</td>
</tr>
<tr>
<td><strong>Sim Spindle Moment Cycle</strong></td>
<td>Simulated spindle moment through the same revolution</td>
</tr>
<tr>
<td><strong>Sensor Cutting Force Cycle</strong></td>
<td>The same force as measured by a dynamometer, against time</td>
</tr>
<tr>
<td><strong>Sensor Spindle Moment Cycle</strong></td>
<td>The same moment as measured, against time</td>
</tr>
</tbody>
</table>
<p>The group bar above them carries the step number as a badge, or <strong>No step selected</strong>. That badge is
the only place the step index is shown — Step Properties leaves that row out rather than repeat it,
which is why the list you configure and the list you see differ by one row.</p>
<p><strong>Step Properties shows short names.</strong> Hovering a name gives the full one, and the unit follows the
value. A field with nothing in it reads <code>-</code>.</p>
<p><strong>CWE is a footprint, not a solid.</strong> It is a small 3D view of its own, drawing the contact contours
the step left behind rather than the volume it swept, because contours are what a step stores. It has
its own view controls and a contour-grid toggle, and it reads <strong>No cut in this step</strong> for a step that
removed nothing — a rapid, or a move in air.</p>
<h2 id="two-scales-and-the-join-between-them">Two scales, and the join between them</h2>
<p>The strip charts beside this column and the cycle charts inside it are the same measurements at two
scales: the strip charts span the whole mission, the cycle charts span <strong>one revolution of one
step</strong>. Changing the selection on a strip chart re-reads every cycle chart, so scrubbing the mission
scrubs the detail with it.</p>
<p>The two simulated charts plot against <strong>spindle angle in degrees</strong>; the two sensor charts plot
against <strong>time in seconds</strong>, because measured data arrives on a clock rather than on a phase. Both
sensor charts need measurement data attached to the project; with none, they read <strong>No data for
step</strong> while the simulated pair beside them is full.</p>
<p>Each cycle chart's header carries a <strong>value boundary</strong> — <em>Auto</em>, or a fixed ± bound that pins the
scale so two steps can be compared without the axis moving under you — and a reload. The two spindle
moment charts carry one more: a <strong>Line / Dartboard</strong> switch, where Dartboard replots the same cycle
as a locus in the plane instead of three channels against the cycle parameter.</p>
<p><strong>Clicking a point in a cycle chart marks that point for its whole group.</strong> The two simulated charts
share one mark in spindle angle; the two sensor charts share another in seconds. The mark survives a
switch between Line and Dartboard and a change of selected step. It also reaches the CWE panel: the
cutter in that view rotates to the angle you clicked, so &ldquo;the force peaked here&rdquo; and &ldquo;this is what
the cutter was touching there&rdquo; become one picture rather than two.</p>
<p>The column with the demo mission paused and a step selected: Sentence Syntax at the top, the step
badge on the bar below it, then Step Properties, CWE and the two simulated cycle charts. The two sensor charts are folded away at the bottom — this project carries no measured data,
so nothing is lost by leaving them shut.</p>
<p><img src="inspecting-a-step-img/step-info.en.png" alt="The Execution page's Step Info column filled: a Sentence Syntax panel showing the arc block N0120 G02 I0.0 J11. above its parsed form, a group bar badged step #500, a Step Properties list reading FileNo 1, LineNo 13, FilePath NC/circle.ptp and a Time of four seconds, a CWE panel whose small 3D view draws the cutter's flute contours against an orange contact patch on the workpiece, and two cycle charts carrying X, Y and Z traces of cutting force and spindle moment across a full 0 to 360 degree spindle revolution"></p>
<h2 id="choosing-what-step-properties-shows">Choosing what Step Properties shows</h2>
<p>Step Properties does not show everything a step carries — it shows what you asked for, out of a much
longer list. The small button on that panel's header opens the chooser, beside the list it
configures.</p>
<p>Candidates are on the left, grouped into categories; a category header ticks or unticks the whole
group, and <strong>Add Selected</strong> moves what you ticked across. Anything already displayed is greyed with a
tick beside it, so the left side never offers you a duplicate. The displayed list is on the right, in
the order it will appear: drag a row, or use its up and down buttons, and remove one row at a time or
<strong>Clear</strong> the lot. <strong>Reset</strong> empties the list entirely.</p>
<p><strong>There is no Save button, and that is not an omission.</strong> Every add, removal and reorder is written
as you make it, and the header reports the write — so the way to undo an experiment is to put the
rows back, not to close the dialog.</p>
<p>The chooser open over the column, at <code>/execution</code>. The counts in its header are this account's
displayed list against everything the run can offer; the green ticks down the candidate side are the
rows already on the right.</p>
<p><img src="inspecting-a-step-img/step-present.en.png" alt="The Step Present Preference dialog open over the Execution page: a header counting displayed against available keys with Reset and close, a Candidate Keys panel on the left with collapsible categories and an Add Selected button, and a Displayed Keys panel on the right listing the chosen properties with up, down and remove buttons and a Clear action"></p>
<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="watching-the-run.html">Watching the Run</a> — the mission-wide charts whose selection fills this column</li>
<li><a href="running-a-simulation.html">Starting and Stepping</a> — stepping the run to land on the step you want to read</li>
<li><a href="the-program-branch.html">The Program Branch</a> — the file panels whose line clicks steer the Sentence Syntax panel</li>
<li><a class="xref" href="../../anatomy/execution/selected-step-info-panel.html">Selected-Step Info Panel</a> — the component behind Step Properties, and where its values come from</li>
<li><a class="xref" href="../../anatomy/execution/cycle-line-charts.html">Cycle-Line Charts</a> — the components behind the four cycle charts, and the shared cursor mark</li>
<li><a class="xref" href="../../anatomy/execution/step-present-dialog.html">Step Present Dialog</a> — the component behind the chooser: its categories, its labels and how it persists</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>