Newer
■
■
■
■
■
■
■
■
■
■
Older
30 lines
|
0.691kb
| 1 |
# Payload Notes |
|
| 2 | ||
| 3 |
Use this folder for protocol-level findings. |
|
| 4 | ||
| 5 |
Examples: |
|
| 6 | ||
| 7 |
- packet captures |
|
| 8 |
- field maps |
|
| 9 |
- command and response notes |
|
| 10 |
- unknown byte ranges |
|
| 11 |
- per-model payload differences |
|
| 12 | ||
| 13 |
For each note, prefer recording: |
|
| 14 | ||
| 15 |
- model |
|
| 16 |
- firmware or hardware revision if known |
|
| 17 |
- sample payload |
|
| 18 |
- decoded meaning |
|
| 19 |
- confidence level |
|
| 20 | ||
| 21 |
## Collected Notes |
|
| 22 | ||
| 23 |
### `UM24C-UM25C-UM34C from floriandotorg-um24c.md` |
|
| 24 | ||
| 25 |
- external protocol notes for the UM family |
|
| 26 | ||
| 27 |
### `TC66C Transport and Payload Working Note.md` |
|
| 28 | ||
| 29 |
- implementation-oriented note derived from the TC66 manuals and the current app code |
|
| 30 |
- captures current transport assumptions, command surface, encrypted snapshot framing, and decoded field map |