说明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:
@@ -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:
|
||||
|
||||
Reference in New Issue
Block a user