aiden/Sony-rcp
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

run 9

Browse Source
This commit is contained in:
Aiden
2026-05-13 16:41:19 +10:00
parent 4e8be74dd9
commit 27cc85e1c1
8 changed files with 151 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

52
docs/discovery-notes.md
View File

@@ -3034,3 +3034,55 @@ python scripts/serial_button_response_test.py --port COM5 --duration 15 --prompt
This test is deliberately secondary. Run it only after the `0x45` family
repeats, so any change can be attributed to the follow-up rather than to the
initial CALL echo timing.
### 2026-05-13 CALL 60-100 ms Repeat Result
Captures:
- `captures/rcp-buttons-call-exact-echo-delay-60ms.txt`
- `captures/rcp-buttons-call-exact-echo-delay-70ms.txt`
- `captures/rcp-buttons-call-exact-echo-delay-80ms-v2.txt`
- `captures/rcp-buttons-call-exact-echo-delay-90ms.txt`
- `captures/rcp-buttons-call-exact-echo-delay-100ms.txt`
Observed result:
| Delay | Result |
| --- | --- |
| 60 ms | no `0x45` response |
| 70 ms | no `0x45` response |
| 80 ms repeat | no `0x45` response |
| 90 ms | no `0x45` response |
| 100 ms | no `0x45` response |
Interpretation:
- The `07 80 45 30 D0 78` response from the earlier 80 ms run did not repeat in
the 80 ms repeat or nearby 60-100 ms bracket.
- The trigger is not controlled by the simple delay between CALL high detection
and the two-frame echo pair alone.
- A more likely variable is the spacing between the host's CALL-high echo and
CALL-low echo, or the RCP's internal heartbeat/call-scan phase when the echo
pair arrives.
Next test direction:
- Keep the initial response delay fixed near the values that have produced hits
before, but vary the spacing between the two echoed CALL frames.
Tooling note:
- `scripts/serial_button_response_test.py` now supports
`--response-frame-interval`, which inserts a delay between multiple
`--response-frame` values sent for the same observed button event.
Inter-frame timing ladder:
```powershell
python scripts/serial_button_response_test.py --port COM5 --duration 15 --prompt --respond-to-call --respond-once --response-delay 0.05 --response-frame-interval 0.02 --response-frame "00 00 15 80 00 CF" --response-frame "00 00 15 00 00 4F" --watch-frame "07 80 45 20 D0 68" --watch-frame "07 80 45 30 D0 78" --log captures/rcp-buttons-call-frame-gap-20ms.txt
python scripts/serial_button_response_test.py --port COM5 --duration 15 --prompt --respond-to-call --respond-once --response-delay 0.05 --response-frame-interval 0.05 --response-frame "00 00 15 80 00 CF" --response-frame "00 00 15 00 00 4F" --watch-frame "07 80 45 20 D0 68" --watch-frame "07 80 45 30 D0 78" --log captures/rcp-buttons-call-frame-gap-50ms.txt
python scripts/serial_button_response_test.py --port COM5 --duration 15 --prompt --respond-to-call --respond-once --response-delay 0.05 --response-frame-interval 0.08 --response-frame "00 00 15 80 00 CF" --response-frame "00 00 15 00 00 4F" --watch-frame "07 80 45 20 D0 68" --watch-frame "07 80 45 30 D0 78" --log captures/rcp-buttons-call-frame-gap-80ms.txt
python scripts/serial_button_response_test.py --port COM5 --duration 15 --prompt --respond-to-call --respond-once --response-delay 0.08 --response-frame-interval 0.05 --response-frame "00 00 15 80 00 CF" --response-frame "00 00 15 00 00 4F" --watch-frame "07 80 45 20 D0 68" --watch-frame "07 80 45 30 D0 78" --log captures/rcp-buttons-call-delay-80ms-frame-gap-50ms.txt
```
For each run, power-cycle first and use the same roughly 2 second CALL hold.