Newer
■
■
■
■
■
■
■
■
■
■
Older
29 lines
|
1.442kb
| 1 |
# Software |
|
| 2 | ||
| 3 |
Archive vendor or third-party software related to supported USB meter models here. |
|
| 4 | ||
| 5 |
Recommended contents: |
|
| 6 | ||
| 7 |
- Android applications |
|
| 8 |
- PC software packages |
|
| 9 |
- extracted binaries or installers when legally safe to preserve |
|
| 10 |
- companion notes about supported models, versions, and observed protocol hints |
|
| 11 | ||
| 12 |
Current status: |
|
| 13 | ||
| 14 |
- Android applications imported from the `UM24` archive |
|
| 15 |
- Android application imported from the `TC66` archive |
|
| 16 |
- PC software archives inspected locally but intentionally excluded from the repository because they are bulky and unlikely to be used by the current app |
|
| 17 |
- font file from the archive intentionally not imported for now because it does not appear device-specific |
|
| 18 | ||
| 19 |
Working note: |
|
| 20 | ||
| 21 |
- some imported software artifacts appear branded at the RuiDeng family level rather than clearly tied to a single model |
|
| 22 |
- until deeper reverse engineering confirms scope, treat them as potentially relevant to `UM24C`, `UM25C`, and `UM34C` |
|
| 23 |
- the `TC66` archive also contains TC66-specific software artifacts that should be treated as a separate line unless overlap is later confirmed |
|
| 24 | ||
| 25 |
Retention note: |
|
| 26 | ||
| 27 |
- prefer keeping software artifacts that are small enough to clone comfortably and directly useful for protocol or workflow analysis |
|
| 28 |
- keep metadata notes for larger archives even when the archive itself stays out of git |
|
| 29 |
- for now, that means Android artifacts stay in-repo, while PC software stays documented but untracked |