deploy.

2026-09-16 00:00:49 +08:00
parent 1a75503105
commit bfa3106a69
60 changed files with 696 additions and 268 deletions
@@ -372,7 +372,13 @@ bounded field on the four leaves, at zero or above.</li>
 <p>The stroke limits are checked at each played step against the chain's current machine pose while the
 session's stroke-limit check is on; a position past a configured limit is reported as a
 stroke-limit validation error anchored to that step, and pauses the player when pause-on-failure is
-set. The check walks a <strong>fixed axis vocabulary</strong> — X, Y and Z from the machine point, A, B and C
+set. The comparison carries a small tolerance
+(<a class="xref" href="../../../../api/Hi.NcParsers.Dependencys.StrokeLimitUtil.html#Hi_NcParsers_Dependencys_StrokeLimitUtil_Tolerance">Tolerance</a>), so an axis parked exactly on its limit
+is not reported. The rotary limits also steer the tilt solves: when a <code>G53.1</code>, <code>G68.2</code>, <code>CYCLE800</code>,
+<code>PLANE SPATIAL</code> or <code>LN</code> posture has its nearest rotary solution outside the travel, the solve takes
+the admissible branch nearest the entry instead of commanding a posture the machine cannot take. A
+project that declared its travel only in the legacy machine-limits boxes gets those ends copied into
+this table on load, for the axes carrying no end here. The check walks a <strong>fixed axis vocabulary</strong> — X, Y and Z from the machine point, A, B and C
 from its orientation — so a limit stored against any other axis name is kept and shown here but never
 tested. Rapid-traverse timing has the same shape and the same six names: a G00 move is timed
 axis-by-axis at each axis' rate and takes the slowest, falling back to the same 20000 mm/min and