From 3f81597c93fa90eaea5bc77e8f2dd0a7031b084b Mon Sep 17 00:00:00 2001 From: ScottW514 Date: Sat, 15 Aug 2026 14:11:32 -0400 Subject: [PATCH] SAFETY: hv_enable run-boundary behavior is established; drop it from the open items --- docs/SAFETY.md | 9 ++------- 1 file changed, 2 insertions(+), 7 deletions(-) diff --git a/docs/SAFETY.md b/docs/SAFETY.md index 1872f28..513afb7 100644 --- a/docs/SAFETY.md +++ b/docs/SAFETY.md @@ -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.