Voyager 2 stopped communicating two weeks ago when controllers sent the wrong command to the 46-year-old spacecraft and tilted its antenna away from Earth.
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. Voyager 2’s antenna needed to be shifted a mere 2%.
The long shot paid off. On Friday, the spacecraft started returning data again, according to officials at California’s Jet Propulsion Laboratory. The two-week outage was believed to be the longest NASA had gone without hearing from Voyager 2, Dodd said.
日本 最新ニュース, 日本 見出し
Similar News:他のニュース ソースから収集した、これに似たニュース記事を読むこともできます。
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…
続きを読む »
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.
続きを読む »
NASA reconnects with Voyager after weeks of silenceNASA’s Voyager 2 spacecraft is back in contact after flight controllers corrected a mistake that had led to weeks of silence
続きを読む »
NASA restores contact with Voyager 2 spacecraft after weeks of silence from interstellar spaceNASA’s Voyager 2 spacecraft is back in contact again, after flight controllers corrected a mistake that had led to weeks of silence.
続きを読む »
NASA reestablishes contact with Voyager 2 spacecraft after weeks of silenceAfter weeks of silence following a mistake, NASA scientists say they've restored full communications with the agency's Voyager 2 spacecraft, located billions of miles away.
続きを読む »
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.
続きを読む »