yukart/orin-nano-env-setup
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

USB report: timed replug repeat (~15 s to stable)

Browse Source 
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
mikkeli
2026-10-09 00:29:15 +09:00
parent 264cc68ff2
commit b7f19c85fb
1 changed files with 3 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/impl/reports/USB-TABLET-LINK.md
+3
View File
@@ -109,6 +109,9 @@ Three PD unplug/replug cycles while pinging the tablet every 0.5 s:
charging), then re-creates its USB network once. **The Orin's interface state does not reveal this outage**, so only an charging), then re-creates its USB network once. **The Orin's interface state does not reveal this outage**, so only an
application-level heartbeat catches it. application-level heartbeat catches it.
- Exact replug time isn't known; the first failed ping is used as its marker. - Exact replug time isn't known; the first failed ping is used as its marker.
- Repeat (plug-in at ~00:27:12): the tablet was silent for 7.8 s with the Orin's link up, then one gadget reconnect (00:27:25.1–27.0)
and a fresh `DHCPDISCOVER`; about **15 s** to stable. Replug consistently costs more than unplug (3.5 s).
- At ignition, accessory power drops during cranking, so a start is likely to produce both edges back to back (not tested in the car yet).
Consequence: in the car, expect a link outage of up to about 12 s at every ignition change. That is a requirement for the services Consequence: in the car, expect a link outage of up to about 12 s at every ignition change. That is a requirement for the services
(failure detection and redelivery; project-yukart ARCHITECTURE decision 24), not something to fix in the host setup. (failure detection and redelivery; project-yukart ARCHITECTURE decision 24), not something to fix in the host setup.