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

The fan floors proven on a pinned image; a fan fault ends with its session

Browse Source 
The dated record of dev image 20260822135848: the campaign of every
non-operator, non-live test at 18 of 18 PASS with the measured floors and
the operating-point rule (cooling.fan-gate-trips and the hunt leg of
cloud.mode-switch as recorded), and the unplugged-exhaust-fan drill:
AIRFLOW at the grace plus three ticks with the exhaust dead, the other
fans held, the reason relayed on the Grbl port, the replugged fan ok
inside the next session's grace.

The drill showed the fault riding into idle, where the hold canceled
jogs and would have refused the cloud print that re-proves the fan.
forgectrl pin d51dbdb: the fault ends with its run session, and the next
session judges every fan afresh. cooling.fan-gate-trips checks the
verdict is OK with no hold once the tripped session is over (the unit
fake mirrors it); its covers, and the cooling tests' shared covers, gain
src/coolfmt.* (the tree manifest carries the new files at the bumped pin,
and the lint was right to ask). cloud.mode-switch samples the hunt's gate
rows twice a second: a hunt's run phase is a few seconds long.

Docs: COOLING 3a, BRINGUP item 19, CAMPAIGN-LOG.
This commit is contained in:
ScottW514
2026-08-22 10:46:41 -04:00
parent adcd1adb9a
commit c1591e4f69
7 changed files with 107 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/BRINGUP.md
+14 -6
View File
@@ -1358,12 +1358,20 @@ Open items only. Anything closed is in `CAMPAIGN-LOG.md`.
and unarmed whenever it is commanded at the run duty; a cloud hunt,
sent with the extraction fans off, is measured and not judged.
`cooling.fan-gate-trips` and the hunt leg of `cloud.mode-switch` in
the catalog. The shipped floors are 55 percent of the bench machine's
measured steady speeds (facts bank: exhaust 6400, intake 2290, air
assist 6000 rpm, purge current 300, grace 15 s); the bench run of the
gate tests on an image carrying them, and the unplugged-tach drill,
are still owed. The coolant critical tier and the watch-only board
temperatures follow.
the catalog, both PASS on the pinned dev image `20260822135848`
(campaign 18 of 18). The shipped floors are 55 percent of the bench
machine's measured steady speeds (facts bank: exhaust 6400, intake
2290, air assist 6000 rpm, purge current 300, grace 15 s). The
unplugged-exhaust-fan drill PASS on the same image: `AIRFLOW` at
grace plus three ticks with the exhaust dead, the other fans held,
the reason relayed on the Grbl port, and the replugged fan `ok` inside
the next session's grace (CAMPAIGN-LOG). From the drill: the fault
ends with its run session (decided; a standing hold at idle canceled
GRBL jogs and would have refused the cloud print that re-proves the
fan), since every session judges every fan afresh after the grace;
`cooling.fan-gate-trips` checks it, bench run owed on the next image.
The coolant critical tier and the watch-only board temperatures
follow.
Nothing here can put energy where it was not commanded: the hardware chain
is the emission boundary and no header field touches it, and forgectrl runs