pcb
This commit is contained in:
Aiden
@@ -7686,6 +7686,260 @@ It may still require:
|
||||
- a missing hardware/state signal on another wire
|
||||
- or a specific startup family we have touched indirectly but not yet maintained
|
||||
|
||||
### HE33: Maintain The Startup-Beacon Families
|
||||
|
||||
Goal:
|
||||
|
||||
- Follow the strongest new HE32 clue directly.
|
||||
- Treat the startup-beacon families as possible **maintained classes** rather
|
||||
than merely one-shot opening responses.
|
||||
|
||||
Working idea:
|
||||
|
||||
- `90` and `AF` increasingly look like startup beacons or mode/class selectors.
|
||||
- In HE32 we immediately switched from those beacon effects into `E8`/`EC` page
|
||||
traffic.
|
||||
- That may have been too eager.
|
||||
- Instead, try:
|
||||
- open `64 40 30 C9`, `E4 40 30 49`, `0D 04 AB 7F`, or `0D 04 EB 3F`
|
||||
- then maintain **that class**
|
||||
- and only optionally add heartbeat alongside it
|
||||
|
||||
What would count as a hit:
|
||||
|
||||
- the startup family reappears or stays reusable
|
||||
- a new recurring non-heartbeat family appears later in the same run
|
||||
- the panel visibly changes state
|
||||
- `CONNECT NOT ACT` behavior changes while the maintained class is running
|
||||
|
||||
Checksums for host-shaped maintained-class frames:
|
||||
|
||||
- host `64 40 30` -> `00 00 64 40 30 0E`
|
||||
- host `E4 40 30` -> `00 00 E4 40 30 8E`
|
||||
- host `0D 04 AB` -> `00 00 0D 04 AB F8`
|
||||
- host `0D 04 EB` -> `00 00 0D 04 EB B8`
|
||||
|
||||
#### HE33a: Repeated `90` beacon, then maintain `64 40 30`
|
||||
|
||||
Hypothesis:
|
||||
|
||||
- `64 40 30` may be the real maintained class after `90`, not an intermediate
|
||||
page on the way to `E8`.
|
||||
|
||||
```powershell
|
||||
python scripts/serial_sequence_probe.py --port COM5 --prompt --prompt-screen --pre-read 0.5 --frame "00 00 90 00 80 4A" --frame "00 00 90 00 80 4A" --frame "00 00 64 40 30 0E" --frame "00 00 64 40 30 0E" --frame "00 00 64 40 30 0E" --frame "00 00 64 40 30 0E" --read-after-frame 0.15 --frame-interval 0.25 --read-after-group 3.0 --log captures/rcp-he33-90-then-644030.txt
|
||||
```
|
||||
|
||||
#### HE33b: Repeated `90` beacon, then maintain `E4 40 30`
|
||||
|
||||
Hypothesis:
|
||||
|
||||
- The alternate `90` beacon branch may want `E4 40 30` as its maintained class.
|
||||
|
||||
```powershell
|
||||
python scripts/serial_sequence_probe.py --port COM5 --prompt --prompt-screen --pre-read 0.5 --frame "00 00 90 00 80 4A" --frame "00 00 90 00 80 4A" --frame "00 00 E4 40 30 8E" --frame "00 00 E4 40 30 8E" --frame "00 00 E4 40 30 8E" --frame "00 00 E4 40 30 8E" --read-after-frame 0.15 --frame-interval 0.25 --read-after-group 3.0 --log captures/rcp-he33-90-then-e44030.txt
|
||||
```
|
||||
|
||||
#### HE33c: `A0 -> 90`, then maintain `64 40 30`
|
||||
|
||||
Hypothesis:
|
||||
|
||||
- `A0 -> 90` may be a more deterministic way to enter the `64 40 30` startup
|
||||
family than bare repeated `90`.
|
||||
|
||||
```powershell
|
||||
python scripts/serial_sequence_probe.py --port COM5 --prompt --prompt-screen --pre-read 0.5 --frame "00 00 A0 00 80 7A" --frame "00 00 90 00 80 4A" --frame "00 00 64 40 30 0E" --frame "00 00 64 40 30 0E" --frame "00 00 64 40 30 0E" --frame "00 00 00 00 80 DA" --frame "00 00 64 40 30 0E" --read-after-frame 0.15 --frame-interval 0.25 --read-after-group 3.0 --log captures/rcp-he33-a0-90-then-644030.txt
|
||||
```
|
||||
|
||||
#### HE33d: Repeated `AF` beacon, then maintain `0D 04 EB`
|
||||
|
||||
Hypothesis:
|
||||
|
||||
- The repeated-`AF` startup branch may want the `0D 04 EB` class maintained.
|
||||
|
||||
```powershell
|
||||
python scripts/serial_sequence_probe.py --port COM5 --prompt --prompt-screen --pre-read 0.5 --frame "00 00 AF 00 80 75" --frame "00 00 AF 00 80 75" --frame "00 00 0D 04 EB B8" --frame "00 00 0D 04 EB B8" --frame "00 00 0D 04 EB B8" --frame "00 00 0D 04 EB B8" --read-after-frame 0.15 --frame-interval 0.25 --read-after-group 3.0 --log captures/rcp-he33-af-then-0d04eb.txt
|
||||
```
|
||||
|
||||
#### HE33e: `A0 -> AF`, then maintain `0D 04 AB`
|
||||
|
||||
Hypothesis:
|
||||
|
||||
- `A0 -> AF` may open a slightly different startup/status class than repeated
|
||||
`AF`, and it may want `0D 04 AB` instead of `0D 04 EB`.
|
||||
|
||||
```powershell
|
||||
python scripts/serial_sequence_probe.py --port COM5 --prompt --prompt-screen --pre-read 0.5 --frame "00 00 A0 00 80 7A" --frame "00 00 AF 00 80 75" --frame "00 00 0D 04 AB F8" --frame "00 00 0D 04 AB F8" --frame "00 00 0D 04 AB F8" --frame "00 00 00 00 80 DA" --frame "00 00 0D 04 AB F8" --read-after-frame 0.15 --frame-interval 0.25 --read-after-group 3.0 --log captures/rcp-he33-a0-af-then-0d04ab.txt
|
||||
```
|
||||
|
||||
#### HE33f: `90` startup family with heartbeat interleaved
|
||||
|
||||
Hypothesis:
|
||||
|
||||
- The maintained class may still need a low-rate host-presence heartbeat beside
|
||||
it, even if the page-class itself is the important thing.
|
||||
|
||||
```powershell
|
||||
python scripts/serial_sequence_probe.py --port COM5 --prompt --prompt-screen --pre-read 0.5 --frame "00 00 90 00 80 4A" --frame "00 00 90 00 80 4A" --frame "00 00 64 40 30 0E" --frame "00 00 00 00 80 DA" --frame "00 00 64 40 30 0E" --frame "00 00 00 00 80 DA" --frame "00 00 64 40 30 0E" --read-after-frame 0.15 --frame-interval 0.25 --read-after-group 3.0 --log captures/rcp-he33-90-644030-with-heartbeat.txt
|
||||
```
|
||||
|
||||
#### HE33g: `AF` startup family with heartbeat interleaved
|
||||
|
||||
Hypothesis:
|
||||
|
||||
- Same logic as above, but for the `AF`-derived startup family.
|
||||
|
||||
```powershell
|
||||
python scripts/serial_sequence_probe.py --port COM5 --prompt --prompt-screen --pre-read 0.5 --frame "00 00 AF 00 80 75" --frame "00 00 AF 00 80 75" --frame "00 00 0D 04 EB B8" --frame "00 00 00 00 80 DA" --frame "00 00 0D 04 EB B8" --frame "00 00 00 00 80 DA" --frame "00 00 0D 04 EB B8" --read-after-frame 0.15 --frame-interval 0.25 --read-after-group 3.0 --log captures/rcp-he33-af-0d04eb-with-heartbeat.txt
|
||||
```
|
||||
|
||||
Recommended order:
|
||||
|
||||
1. `HE33a` repeated `90`, then `64 40 30`
|
||||
2. `HE33c` `A0 -> 90`, then `64 40 30`
|
||||
3. `HE33d` repeated `AF`, then `0D 04 EB`
|
||||
4. `HE33e` `A0 -> AF`, then `0D 04 AB`
|
||||
5. `HE33f` `90` family with heartbeat
|
||||
6. `HE33g` `AF` family with heartbeat
|
||||
7. `HE33b` repeated `90`, then `E4 40 30`
|
||||
|
||||
Reasoning:
|
||||
|
||||
- `64 40 30` looks like the strongest `90`-side startup family so far.
|
||||
- `0D 04 AB/EB` is the matching `AF`-side family.
|
||||
- The cleanest question first is simply:
|
||||
can maintaining those classes do anything at all?
|
||||
|
||||
### HE33 Results
|
||||
|
||||
Practical outcome:
|
||||
|
||||
- No visible panel wake-up.
|
||||
- No useful LCD change beyond the already familiar inactive behavior.
|
||||
- Maintaining the startup-beacon families did **not** turn them into live
|
||||
reusable session classes.
|
||||
|
||||
Serial outcome:
|
||||
|
||||
- The beacon families themselves are real and reproducible.
|
||||
- But once opened, host-shaped maintenance of those same families mostly just
|
||||
drained the initial one-shot response and then fell back to
|
||||
heartbeat-compatible traffic.
|
||||
|
||||
#### HE33a: repeated `90`, then maintain `64 40 30`
|
||||
|
||||
Observed:
|
||||
|
||||
- second `90` produced:
|
||||
- `07 80 64 40 30 C9`
|
||||
- first host `64 40 30` produced one more:
|
||||
- `07 80 64 40 30 C9`
|
||||
- later host `64 40 30` frames were heartbeat-compatible only
|
||||
|
||||
Interpretation:
|
||||
|
||||
- `64 40 30` is a real startup-family surface.
|
||||
- But simply maintaining host `64 40 30` does not keep that branch open.
|
||||
|
||||
#### HE33b: repeated `90`, then maintain `E4 40 30`
|
||||
|
||||
Observed:
|
||||
|
||||
- repeated `90` still opened:
|
||||
- `07 80 64 40 30 C9`
|
||||
- host `E4 40 30` did **not** pivot it into a stable `E4`-maintained state
|
||||
- later traffic was heartbeat-compatible only
|
||||
|
||||
Interpretation:
|
||||
|
||||
- The `90` beacon can still prefer `64` on this run.
|
||||
- Host `E4 40 30` did not make the alternate `E4` startup family reusable.
|
||||
|
||||
#### HE33c: `A0 -> 90`, then maintain `64 40 30`
|
||||
|
||||
Observed:
|
||||
|
||||
- `A0 -> 90` produced:
|
||||
- `07 80 64 40 30 C9`
|
||||
- later host `64 40 30` frames were heartbeat-compatible only
|
||||
|
||||
Interpretation:
|
||||
|
||||
- `A0 -> 90` is still a clean opener for the `64` family.
|
||||
- But, again, the family did not become maintainable as a live background
|
||||
class.
|
||||
|
||||
#### HE33d: repeated `AF`, then maintain `0D 04 EB`
|
||||
|
||||
Observed:
|
||||
|
||||
- repeated `AF` produced:
|
||||
- `07 80 0D 04 AB 7F`
|
||||
- `07 80 0D 04 AB 7F`
|
||||
- first host `0D 04 EB` drained one more:
|
||||
- `07 80 0D 04 AB 7F`
|
||||
- later host `0D 04 EB` frames were heartbeat-compatible only
|
||||
|
||||
Interpretation:
|
||||
|
||||
- On this run, repeated `AF` did **not** prefer the older `EB`-suffixed
|
||||
startup family; it stayed on the `AB` family instead.
|
||||
- That makes the `AF` startup side look more slippery than the `90` side.
|
||||
|
||||
#### HE33e: `A0 -> AF`, then maintain `0D 04 AB`
|
||||
|
||||
Observed:
|
||||
|
||||
- `A0 -> AF` produced repeated:
|
||||
- `07 80 0D 04 AB 7F`
|
||||
- host `0D 04 AB` continued to drain more `AB` responses briefly
|
||||
- then the run collapsed back to heartbeat-compatible traffic
|
||||
|
||||
Interpretation:
|
||||
|
||||
- `A0 -> AF` remains the cleanest opener for the `AB` startup family.
|
||||
- It is stronger than the bare repeated-`AF` case, but still not enough to
|
||||
create a sustained live session layer.
|
||||
|
||||
#### HE33f: `90` family with heartbeat interleaved
|
||||
|
||||
Observed:
|
||||
|
||||
- repeated `90` produced:
|
||||
- `07 80 64 40 30 C9`
|
||||
- `07 80 64 40 30 C9`
|
||||
- host `64 40 30` plus heartbeat still fell back to heartbeat-compatible
|
||||
traffic after that
|
||||
|
||||
Interpretation:
|
||||
|
||||
- Interleaving heartbeat did not make the `64` family maintainable.
|
||||
|
||||
#### HE33g: `AF` family with heartbeat interleaved
|
||||
|
||||
Observed:
|
||||
|
||||
- repeated `AF` produced:
|
||||
- `07 80 0D 04 AB 7F`
|
||||
- host `0D 04 EB` plus heartbeat did not reopen a live `EB`/`AB` maintained
|
||||
branch
|
||||
|
||||
Interpretation:
|
||||
|
||||
- Heartbeat beside the `AF` startup family also did not help.
|
||||
|
||||
HE33 conclusion:
|
||||
|
||||
- The `90`/`AF` startup-beacon families are real, but they still behave like
|
||||
one-shot startup surfaces rather than the missing maintained wake/session
|
||||
stream.
|
||||
- `90` is the cleaner side:
|
||||
- it repeatedly lands on `64 40 30`
|
||||
- `AF` is the sloppier side:
|
||||
- it can land on `AB` or `EB`, and on this pass it mostly preferred `AB`
|
||||
- Maintaining those family classes directly did not wake the panel, did not
|
||||
make later traffic reusable, and did not create a stable active state.
|
||||
|
||||
### 2026-05-13 CAM POWER Context Retests
|
||||
|
||||
Goal:
|
||||
|
||||
Reference in New Issue
Block a user