MrEff@lemmy.world to science@lemmy.world · 7 months agoVoyager 1 contact restoredwww.usatoday.comexternal-linkmessage-square38fedilinkarrow-up1569arrow-down16file-textcross-posted to: astronomy@mander.xyzspace@lemmy.world
arrow-up1563arrow-down1external-linkVoyager 1 contact restoredwww.usatoday.comMrEff@lemmy.world to science@lemmy.world · 7 months agomessage-square38fedilinkfile-textcross-posted to: astronomy@mander.xyzspace@lemmy.world
minus-squareKaryoplasma@discuss.tchncs.delinkfedilinkarrow-up34·7 months agoThe problem was that Voyager sent junk data back to us due to a memory fault. It was still responsive to receive updates from Earth and to pings. Pinging Voyager 1 takes about 2 days, so testing updates is naturally quite slow.
minus-squarehalcyoncmdr@lemmy.worldlinkfedilinkEnglisharrow-up20·7 months agoNot only round trip time, the hardware only supports bandwidth of 160bps at this range. Down from the 21.6kbps at launch.
The problem was that Voyager sent junk data back to us due to a memory fault. It was still responsive to receive updates from Earth and to pings.
Pinging Voyager 1 takes about 2 days, so testing updates is naturally quite slow.
Not only round trip time, the hardware only supports bandwidth of 160bps at this range. Down from the 21.6kbps at launch.