Link-drop section: attach the ignition remark to the PD reset
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -149,9 +149,9 @@ re-dialling is the client's job. Noticing the loss and redelivering is the Orin'
|
|||||||
|
|
||||||
Measured on the USB path (tablet ↔ PD hub ↔ Orin, 2026-10-09): cutting PD power
|
Measured on the USB path (tablet ↔ PD hub ↔ Orin, 2026-10-09): cutting PD power
|
||||||
resets the hub's data port, and the link is back within ~3.5 s with no
|
resets the hub's data port, and the link is back within ~3.5 s with no
|
||||||
intervention. Longer outages measured early on were the tablet sleeping on
|
intervention. In the car that happens at every ignition change, cranking
|
||||||
battery, not the link. In the car this happens at every ignition
|
included. Longer outages measured early on were the tablet sleeping on battery,
|
||||||
change. Design for it as normal operation. Requirements, not yet implemented:
|
not the link. Design for drops as normal operation. Requirements, not yet implemented:
|
||||||
|
|
||||||
- **Failure detection on the Orin.** An app-level heartbeat with a timeout of a
|
- **Failure detection on the Orin.** An app-level heartbeat with a timeout of a
|
||||||
few seconds, not TCP alone. A connection on a link that went down can stay
|
few seconds, not TCP alone. A connection on a link that went down can stay
|
||||||
|
|||||||
Reference in New Issue
Block a user