NASA’s Voyager 2 spacecraft is back in contact after flight controllers corrected a mistake that had led to weeks of silence
Voyager 2's antenna needed to be shifted a mere 2 degrees. It took more than 18 hours for the command to reach Voyager 2 — more than 12 billion miles away — and another 18 hours to hear back. / Photo: NASA
Hurtling ever deeper into interstellar space billions of miles away, Voyager 2 stopped communicating two weeks ago and there was no contact with the spacecraft until Friday this week. On Wednesday, NASA’s Deep Space Network sent a new command in hopes of repointing the antenna, using the highest-powered transmitter at the huge radio dish antenna in Australia.
Deutschland Neuesten Nachrichten, Deutschland Schlagzeilen
Similar News:Sie können auch ähnliche Nachrichten wie diese lesen, die wir aus anderen Nachrichtenquellen gesammelt haben.
After weeks of silence, NASA reconnects with Voyager 2On Wednesday, NASA’s Deep Space Network sent a new command in hopes of repointing the antenna, using the highest powered transmitter at the huge radio dish antenna in Australia. Voyager 2&82…
Weiterlesen »
NASA restores contact with Voyager 2 spacecraft after mistake led to weeks of silenceVoyager 2 has been hurtling through space since its launch in 1977 to explore the outer solar system.
Weiterlesen »
NASA’s Jet Propulsion Lab makes contact with Voyager 2 after week of no communicationAfter losing signal with the Voyager 2 space probe for over a week, NASA received a faint signal from the 46-year-old satellite Tuesday.
Weiterlesen »
NASA picks up Voyager 2 probe’s ‘heartbeat,’ tries to get the craft to reorient itselfGiant ground-bound NASA antennas heard a “heartbeat” Tuesday indicating the 1970s-vintage Voyager 2 probe over 12.3 billion miles from Earth was still operational.
Weiterlesen »
NASA relinks with Voyager 2 after fears it would be offline for monthsNASA has successfully “reestablished full communications” with Voyager 2, an interstellar deep space probe which the agency sent offline with a faulty command two weeks ago.
Weiterlesen »