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-09 17:35:23 +08:00
parent 2a98ae7556
commit 161af68fe3
1271 changed files with 58251 additions and 98639 deletions
Download Patch File Download Diff File Expand all files Collapse all files
App/wwwroot/HiAPI-docsite/api/Hi.NcParsers.Syntaxs.FanucSyntaxUtil.html
+56 -1
View File
@@ -220,6 +220,51 @@ Class FanucSyntaxUtil
<a id="Hi_NcParsers_Syntaxs_FanucSyntaxUtil_G05Syntax_" data-uid="Hi.NcParsers.Syntaxs.FanucSyntaxUtil.G05Syntax*"></a>
<h3 id="Hi_NcParsers_Syntaxs_FanucSyntaxUtil_G05Syntax" data-uid="Hi.NcParsers.Syntaxs.FanucSyntaxUtil.G05Syntax">
G05Syntax
</h3>
<div class="markdown level1 summary"><p>G05 P{n}: Fanuc HPCC family selector. P is a function-selection
code, not a quantity: P10000 enters high-precision contour control
(RISC-board look-ahead — never alters programmed coordinates), P0
cancels, P10001–P10999 call high-speed cycle machining (executes
cycle data pre-registered in the variable area — real axis motion),
and small P values select the high-speed remote buffer modes
(binary DNC transfer). Consumed by
<a class="xref" href="Hi.NcParsers.LogicSyntaxs.FanucPathSmoothingSyntax.html">FanucPathSmoothingSyntax</a> into the
block-local <code>FanucHpcc</code> section (see
<a class="xref" href="Hi.NcParsers.Keywords.IFanucHpccDef.html">IFanucHpccDef</a>). Both the <code>G05</code> and
<code>G5</code> spellings are captured (the
<a class="xref" href="Hi.NcParsers.LogicSyntaxs.DwellSyntax.html">DwellSyntax</a> G4/G04 discipline); the
trailing-character guard keeps <code>G05.1</code> for
<a class="xref" href="Hi.NcParsers.Syntaxs.FanucSyntaxUtil.html#Hi_NcParsers_Syntaxs_FanucSyntaxUtil_G05p1Syntax">G05p1Syntax</a>.</p>
</div>
<div class="markdown level1 conceptual"></div>
<div class="codewrapper">
<pre><code class="lang-csharp hljs">public static ParameterizedFlagSyntax G05Syntax { get; }</code></pre>
</div>
<h4 class="section">Property Value</h4>
<dl class="parameters">
<dt><a class="xref" href="Hi.NcParsers.ParsingSyntaxs.ParameterizedFlagSyntax.html">ParameterizedFlagSyntax</a></dt>
<dd></dd>
</dl>
<a id="Hi_NcParsers_Syntaxs_FanucSyntaxUtil_G05p1Syntax_" data-uid="Hi.NcParsers.Syntaxs.FanucSyntaxUtil.G05p1Syntax*"></a>
<h3 id="Hi_NcParsers_Syntaxs_FanucSyntaxUtil_G05p1Syntax" data-uid="Hi.NcParsers.Syntaxs.FanucSyntaxUtil.G05p1Syntax">
@@ -303,7 +348,17 @@ would truncate scope before H and lose the offset id.</p>
</h3>
<div class="markdown level1 summary"><p>G54.1 P… additional work offset family syntax.</p>
<div class="markdown level1 summary"><p>G54.1 P… additional work coordinate system selection, in both
spellings Fanuc's manual gives the chapter (&ldquo;G54.1 or G54&rdquo;):
<code>G54.1 P4</code> / <code>G54.1P4</code> and <code>G54 P4</code> / <code>G54P4</code>
all land as <code>Parsing.G54.1 = {P: 4}</code>. The <code>G54</code> spelling is
a <a class="xref" href="Hi.NcParsers.ParsingSyntaxs.ParameterizedFlagSyntax.html#Hi_NcParsers_ParsingSyntaxs_ParameterizedFlagSyntax_ParamGatedAliases">parameter-gated
alias</a>: without a P word it is left alone and stays the ordinary
G54 flag for <a class="xref" href="Hi.NcParsers.ParsingSyntaxs.NumberedFlagSyntax.html">NumberedFlagSyntax</a>. Any P word on a G54
block is taken as the offset index, as the controller does (the
manual forbids other P uses on that block). Shared by the Syntec and
Mazak presets; consumed by
<a class="xref" href="Hi.NcParsers.LogicSyntaxs.IsoCoordinateOffsetSyntax.html">IsoCoordinateOffsetSyntax</a>.</p>
</div>
<div class="markdown level1 conceptual"></div>