The question left open by 5.3.132 turned out to be neither of the causes
being weighed. One diagnostic line printed the whole comparison:
'Gyroscope' watched='Avionics' level=4 minVoltage=50
measured=10000 rated=10000 brownout=1
The bus is Ready and at FULL rated voltage, so there was never a real
brownout. The trip value was 50, and the test measured <= minVoltage *
rated reads 10000 <= 50 * 10000 -- true for any voltage at all.
The field is named minVoltagePercent. It is a percent, and we stored it
1:1; our own comment had flagged the missing scale as "a tuning value
(stored 1:1 here until located)". The authored data admits no other
reading -- bhk1 gives the Gyroscope and HUD 50 and the Searchlight 10,
round percents and absurd as raw fractions. Divided by 100 the gyro
trips below 5000V of a 10000V bus, and the Searchlight tolerates far
more sag before complaining, which is the right ordering for a light
versus a gyro.
The whole chain is now verified live in a single run: watcher bound ->
watchdog reads its target's real state (4, Ready) -> impaired false for
the entire run (31 samples, none impaired) -> the gyro sways on
percentageOnNormal instead of its destruction-grade base. Zero faults.
Provenance recorded honestly in the notes: the binary's scale SITE was
not located in code, so the /100 is inferred from the field name plus
unambiguous authored data, not claimed as a byte-verified decode.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
CydandClaude Fable 5
b1e9a09a6e