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-13 19:45:24 +08:00
parent 397a7a8cc4
commit 2db889ad89
58 changed files with 3526 additions and 213 deletions
Download Patch File Download Diff File Expand all files Collapse all files
App/wwwroot/HiAPI-docsite/api/Hi.NcParsers.Keywords.IMachineCoordinateStateDef.html
+4 -2
View File
@@ -6,7 +6,7 @@
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<meta name="title" content="Interface IMachineCoordinateStateDef | HiAPI-C# 2025 ">
<meta name="description" content="Modal machine-coordinate state — absolute six-axis machine position after the block has executed. Written on every block by motion-related LogicSyntaxs (, , , , , ); seeded on the init block by ; carried across non-motion blocks — and per-key completed on partially-written blocks (an XYZ-only motion block receives the carried modal rotary values) — by . Only configured axes appear as keys (X/Y/Z/A/B/C). Non-existent axes (e.g., A/B/C on a 3-axis machine) are omitted rather than written as NaN sentinels. After the PostLogic carry the section is a MODAL record: key presence means &quot;state known&quot;, never &quot;this block commanded the axis&quot;. Consumers needing &quot;commanded&quot; must read the block&#39;s Parsing words or compare values against the previous block (see LinearMotionUtil.HasRotaryMotion). The only presence-as-commanded carve-out is CompoundMotion.Items[*] item-level sections, which the carry never touches.">
<meta name="description" content="Modal machine-coordinate state — absolute six-axis machine position after the block has executed. Written on every block by motion-related LogicSyntaxs (, , , , , ); seeded on the init block by ; carried across non-motion blocks — and per-key completed on partially-written blocks (an XYZ-only motion block receives the carried modal rotary values) — by . Only configured axes appear as keys (X/Y/Z/A/B/C). Non-existent axes (e.g., A/B/C on a 3-axis machine) are omitted rather than written as NaN sentinels. After the PostLogic carry the section is a MODAL record: key presence means &quot;state known&quot;, never &quot;this block commanded the axis&quot;. Consumers needing &quot;commanded&quot; must read the block&#39;s Parsing words, the one-shot record (the rotary words this block itself spoke, written by ), or compare values against the previous block (see LinearMotionUtil.HasRotaryMotion). The only presence-as-commanded carve-out is CompoundMotion.Items[*] item-level sections, which the carry never touches.">
<link rel="icon" href="../img/HiAPI.favicon.ico">
<link rel="stylesheet" href="../public/docfx.min.css">
<link rel="stylesheet" href="../public/main.css">
@@ -117,7 +117,9 @@ as NaN sentinels.
<p>
After the PostLogic carry the section is a MODAL record: key presence
means "state known", never "this block commanded the axis". Consumers
needing "commanded" must read the block's Parsing words or compare
needing "commanded" must read the block's Parsing words, the one-shot
<a class="xref" href="Hi.NcParsers.Keywords.RotaryWords.html">RotaryWords</a> record (the rotary words this block itself
spoke, written by <a class="xref" href="Hi.NcParsers.LogicSyntaxs.McAbcSyntax.html">McAbcSyntax</a>), or compare
values against the previous block (see
<code>LinearMotionUtil.HasRotaryMotion</code>). The only presence-as-commanded
carve-out is <code>CompoundMotion.Items[*]</code> item-level sections, which