aiden/h8-536-decoder
1
0
Fork 0
Code Activity

otehr lamps

Browse Source
This commit is contained in:
Aiden
2026-05-26 18:25:03 +10:00
parent 566b4ab108
commit c007f2180c
11 changed files with 1376 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
docs/pt2-protocol.md
View File

@@ -673,6 +673,18 @@ The first gated watch capture produced a new periodic active-state response:
After treating those as expected gated refresh traffic, the capture had zero novel frames. A direct search found no known CALL/CAM POWER frames in that log. So the gated setup changed the session/status response shape, but it did not yet prove that physical controls beyond the already-known autonomous buttons are reporting.
## Lamp Selector Mapping
Bench lamp sweeps now prove that several panel outputs are directly driven by command-0 selector writes while `CONNECT: OK` is alive. The current detailed map lives in `docs/pt2-lamp-selector-map.md`.
Newest confirmed behavior:
- `lamp-known-button-selector-probe` made CAM, CALL, BARS, MASTER, and camera tally outputs flash individually.
- `0x0007 = 0x8000/0x0000` is the strongest CAM POWER lamp candidate.
- `0x0015 = 0x8000/0x0000` is the strongest CALL lamp candidate.
- Neighbor selectors `0x0012`, `0x0013`, `0x0016`, `0x0017`, `0x0018`, and `0x001A` likely contain BARS/MASTER/tally red/green assignments, pending isolation.
- A broader status sweep made KNEE AUTO flash; candidate selectors are `0x0003`, `0x0040`, `0x0081`, `0x0092`, `0x00A7`, `0x00B7`, `0x00B9`, and `0x0110`.
## What Is Still Unknown
- The official PT2 names for commands and selectors.