vh/forgefirm
1
0
Fork 0
mirror of https://github.com/openglow-org/forgefirm.git synced 2026-09-27 08:41:13 -07:00
Code Issues Packages Projects Releases Wiki Activity

SAFETY: hv_enable run-boundary behavior is established; drop it from the open items

Browse Source
This commit is contained in:
ScottW514
2026-08-15 14:11:32 -04:00
parent 7319c718fe
commit 3f81597c93
1 changed files with 2 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/SAFETY.md
+2 -7
View File
@@ -269,12 +269,7 @@ kernel readbacks (the runbook `BRINGUP.md` holds the drill records):
## 5. Not yet established
Present gaps in the hardware picture. None of them changes the safety
argument (every gap is on the readback/sense side or is a "which part" question),
but each is worth closing:
argument (every gap is on the readback/sense side or is a "which part"
question), but each is worth closing:
- **`hv_enable` toggles seen inside motion windows** are run boundaries:
`hv_enable` follows the watchdog exactly (active from the first pulse of a
run, inactive 0.45 s after its last), and homing and jogs are several
short runs. A feed late by more than ≈254 ms would look the same and has
not been observed.
- **`laser_pgood` (HV_OK, J1_14) semantics** are not fully characterized.