4 ms·
Lots of motion in the frame -> high bandwidth requirements.
by wolf550e 11y ago
Lots of motion in the frame -> high bandwidth requirements.
- mikeash 11y agoThat might cause the video to go funky, but it shouldn't cut the feed. My guess is that the satellite dish or other communications hardware gets upset when the first stage effectively takes a flamethrower to it.
- robszumski 11y agoThe issue is vibration which throws the uplink out of alignment with the receiver.
- deleted 11y ago[deleted]
- NickNameNick 11y agoOr just shakes it a lot.
- ChuckMcM 11y agoSeems a likely explanation. Its the engineer in my that goes wild here though, I think "why not have the uplink on a smaller flotation unit being held in place by a sea anchor? Or given the amount of time needed to monitor the return is relatively short (you know to the minute when it "should" touch down) could you launch the uplink on a hex a copter so that it could stand off from the barge, free of vibrations while the rocket landed? How about a 2.4Ghz cross link to an independent platform with its own uplink? How about using a towed fiber optic cable to a remote relay station away from the barge? Etc. I totally understand that this is a small (and in the larger picture unimportant) part of the mission, but the problem calls to me :-)
- eps 11y agoYou can stick a NAS into a bouy, connect it to the drone ship with a long-ass network cable and have a petabyte of storage over a 1Gbps link that will survive anything that may happen to the drone ship.
- rbanffy 11y agoThe ship itself is pretty strong.
- knowaveragejoe 11y agoA petabyte over a 1Gbps link would take ~94 days and is probably far more than what is necessary, so I'm not sure why that's included here.