>It happened so fast that there were only a few bits of telemetry between "everything normal" and "no signal".
SpaceX also had an architecture that added a lot of latency to their telemetry transmission (IIRC basically Ethernet bufferbloat)
>It happened so fast that there were only a few bits of telemetry between "everything normal" and "no signal".
SpaceX also had an architecture that added a lot of latency to their telemetry transmission (IIRC basically Ethernet bufferbloat)
This is a good article about Amos-6: https://www.americaspace.com/2017/01/02/spacex-closes-amos-6...
"Investigators scoured more than 3,000 channels of video and telemetry data covering a very brief timeline of events – there were just 93 milliseconds from the first sign of anomalous data to the loss of the second stage, followed by loss of the vehicle."
I haven't seen anything about latency--are you sure that's a problem in the telemetry stack?