说明virtual HAL仿真提升

结论:补充 virtual HAL 成果对 Web 数控仿真的提升说明,并用 docs smoke 固化关键提升点;baseline 保持 28/28/131/0,Python remap、tool DB、external user-M hard block 未解锁。
This commit is contained in:
2026-06-18 17:35:03 +08:00
parent 56da43b7b1
commit 04db87dddd
3 changed files with 44 additions and 0 deletions

View File

@@ -51,6 +51,34 @@ motion feedback. It does not unlock rows whose defining behavior is Python
remap runtime, tool database process protocol, external user-M process state,
or upstream-invalid demo code.
## Web Simulation Improvements From Virtual HAL
Using the completed virtual HAL evidence improves the Web CNC simulation in
these concrete ways:
- Browser and Node simulation no longer need host `halcmd`, `halrun`, or a
native motion-controller process for HAL-level diagnostics.
- UI workflows can inspect and update HAL pins, signals, and params through a
shared source-derived registry instead of private page state.
- Simulation pages can run deterministic `halcmd`-style command fixtures such
as `setp`, `sets`, `newsig`, `net`, `show`, `getp`, `gets`, `loadrt`,
`loadusr`, `addf`, `start`, and `stop`.
- Motion feedback can advance through servo-period stepping so dashboards can
display axis/joint target and feedback state without host realtime services.
- Browser diagnostics artifacts can carry source compliance, sim-config source
coverage, command fixture, promotion candidate, macro/load fixture, and
manifest-backed motion matrix evidence in one release surface.
- Release URL workflows can show the promotion candidate summary, including
8 diagnostics-ready candidates across 3 families and 17 source files.
- OPFS/session workflows can persist and reload virtual HAL-backed diagnostics
evidence for repeatable browser validation.
These improvements make the Web simulation more complete and inspectable for
HAL/UI/machine-state cases. They are still evidence and simulation-surface
improvements only: they do not implement Linux kernel hard realtime, native HAL
module ABI loading, Python remap runtime, tool DB process protocol, external
user-M process execution, or new JavaScript-owned CNC semantics.
## Promotion Rules After Virtual HAL
A sim-config case can move forward only when all of these are true:

View File

@@ -390,6 +390,18 @@ realtime scheduling, external device drivers, native HAL module ABI behavior,
HALUI process behavior, and Tcl/Python process integration remain explicit
boundaries.
In practical Web simulation terms, the completed virtual HAL evidence improves
the system by making HAL/UI/machine-state diagnostics inspectable without host
LinuxCNC processes. Browser and Node workflows can share one source-derived HAL
pin/signal/param registry, execute deterministic `halcmd`-style command
fixtures, advance motion feedback through servo-period stepping, persist
virtual HAL diagnostics through OPFS/session artifacts, and expose release URL
workflow evidence for 8 diagnostics-ready promotion candidates across 3
families and 17 LinuxCNC source files. These are simulation and evidence
surface improvements only; Python remap runtime, tool DB process protocol,
external user-M execution, native HAL module ABI behavior, and JavaScript-owned
CNC semantics remain outside this scope.
## Project release readiness export
`createProjectReleaseGateManifest()` returns the required release gate IDs,

View File

@@ -66,6 +66,10 @@ for (const phrase of [
"axis/vismach/puma/puma_seam_weld.ngc",
"axis/rose_engine/rcone_demo.ngc",
"axis/external_offsets/queuebuster.ngc",
"Web Simulation Improvements From Virtual HAL",
"Browser and Node simulation no longer need host `halcmd`, `halrun`, or a",
"servo-period stepping",
"8 diagnostics-ready candidates across 3 families and 17 source files",
"L4-PYTHON-REMAP",
"L4-TOOL-DB",
"L4-USER-M-PROCESS",