You are potentially overlooking application level latency, just because the packets arrive in 50ms time does not mean the video latency is upper bounded to that. I think 100-200ms is more realistic.
If your one way network latency is 50ms, it takes 150ms minimum to send a packet on 1.5x round trips which is necessary to confirm round trip connectivity and notify the other party. If you can assume clocks are synchronized you can send packets one way in 50ms to confirm connectivity and latency.
> Usually that will involve either slamming the brakes on hard or gently, depending if there is an obstacle ahead or someone following behind.
you’re specifically in a situation in which the car has failed, so im not sure how you can assume the car will make these kinds of decisions correctly.
> I personally think they should just update the stack so they can do realtime control.
Lets assume video latency of 100-200ms can be achieved, its still potentially dangerous. There are however some companies i am aware of in certain countries that are doing it anyway!
Even if glass to glass latency was 1ms, perhaps its not a technological issue but a PR issue. Maybe they don’t want news headlines about people driving cars with mario kart steering wheels or it’s easier to get regulatory approval by reassuring the public they will do the safest thing possibly.