{"id":781225,"date":"2024-04-22T21:56:53","date_gmt":"2024-04-23T02:56:53","guid":{"rendered":"https:\/\/spaceweekly.com\/?p=781225"},"modified":"2024-04-22T21:56:53","modified_gmt":"2024-04-23T02:56:53","slug":"nasa-restores-communications-with-voyager-1","status":"publish","type":"post","link":"https:\/\/spaceweekly.com\/?p=781225","title":{"rendered":"NASA Restores Communications with Voyager 1"},"content":{"rendered":"<p> <br \/>\n<\/p>\n<div>\n<p>The venerable Voyager 1 spacecraft is finally phoning home again. This is much to the relief of mission engineers, scientists, and Voyager fans around the world.<\/p>\n<p><span id=\"more-166733\"\/><\/p>\n<p>On November 14, 2023, the aging spacecraft began sending what amounted to a string of gibberish back to Earth. It appeared to be getting commands from Earth and seemed to be operating okay. It just wasn\u2019t returning any useful science and engineering data. The team engineers began diagnostic testing to figure out if the spacecraft\u2019s onboard computer was giving up the ghost. They also wanted to know if there was some other issue going on.<\/p>\n<p>It wasn\u2019t completely surprising that Voyager 1 would have issues, after all. And, this isn\u2019t the first time Voyager 1 has sent back garbly data. It\u2019s been traversing space since its launch in 1977. Currently, the spacecraft is rushing away from the Solar System toward interstellar space. The spacecraft systems will eventually fail due to age and lack of power. But, people have always held out hope for them to last as long as possible. That\u2019s because Voyager 1 is probing unexplored regions of space.<\/p>\n<h3 class=\"wp-block-heading\" id=\"h-what-happened-to-voyager-1\">What Happened to Voyager 1?<\/h3>\n<p>The diagnostic testing led the engineering team at NASA\u2019s Jet Propulsion Laboratory to look at old engineering documents and manuals for the onboard computers. Eventually, they found that the flight data subsystem (FDS) was having an issue. In the spacecraft\u2019s data handling pipeline, this system takes information from the instruments and packages it into a data stream for the long trip back to Earth.<\/p>\n<p>It turns out that the FDS has a bit of a memory problem. The engineers found this out by poking at the computer\u2014literally sending a \u201cpoke\u201d command to Voyager 1. That prompted the FDS to disgorge a readout of its memory\u2014including the software code and other code values. The readout showed that about 3 percent of the FDS memory is corrupted due to a single chip failing. That\u2019s just enough to keep the computer from doing its normal work of packaging science and engineering data. Unfortunately, engineers can\u2019t replace the chip. No repair is possible, so the technical team devised a workaround. <\/p>\n<h3 class=\"wp-block-heading\" id=\"h-fixing-the-faulty-code-and-chip\">Fixing the Faulty Code and Chip<\/h3>\n<p>So, how did engineers reach across 24 billion kilometers of space to restore communication with Voyager 1? They focused on a specific part of the computer. The loss of the code on that failed chip made it impossible for the computer to do its job. So, they figured out a way to divide the code into sections and store them in various locations around the FDS. Then they had to make the sections work together to do their original job.<\/p>\n<p>They started out by taking the code that packages engineering data and moving it to a safe spot in FDS. Then they sent some commands to the spacecraft for the FDS to do some tasks. That worked because, on April 20th, they heard back from the spacecraft with clear, intelligible data. Now, they just need to do the same thing with other bits of code so that the spacecraft can send back both engineering and science data.<\/p>\n<div class=\"wp-block-image\">\n<figure class=\"aligncenter size-full\"><figcaption class=\"wp-element-caption\">The Voyager 1 flight team members celebrate in a conference room at NASA\u2019s Jet Propulsion Laboratory on April 20 after receiving confirmation that their repair to the spacecraft\u2019s FDS worked. Credit: NASA\/JPL-Caltech<\/figcaption><\/figure>\n<\/div>\n<p>For now, at least, the science and engineering teams can check the spacecraft\u2019s health and its systems. Once they relocate the other bits of code and test them after being moved, they should be able to start receiving science data again. This could take several weeks to accomplish. They\u2019re communicating with a spacecraft that\u2019s 22.5 light-hours away, so having a lengthy diagnostic conversation with Voyager is going to take some time. This isn\u2019t the only problem engineers have had to contend with recently with Voyager 1. In October 2023, they worked to overcome a fuel flow problem affecting its thrusters.<\/p>\n<h3 class=\"wp-block-heading\" id=\"h-voyager-1-into-history\">Voyager 1 Into History<\/h3>\n<p>Voyager 1 was launched on a planetary flyby trajectory on September 5, 1977. It passed by Jupiter in March 1979 and Saturn in November 1980. The mission then morphed into an extended period of exploration and exited the heliopause in 2012. On its way out of the Solar System, the spacecraft also \u201clooked back\u201d at Earth. Now, it\u2019s exploring the interstellar medium but has not yet traversed the Oort Cloud, the outermost portion of the Solar System. <\/p>\n<figure class=\"wp-block-image aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"576\" src=\"https:\/\/www.universetoday.com\/wp-content\/uploads\/2020\/02\/Pale-Blue-dot-1024x576.jpg\" alt=\"This updated version of the iconic &quot;Pale Blue Dot&quot; image taken by the Voyager 1 spacecraft uses modern image-processing software and techniques to revisit the well-known Voyager view while attempting to respect the original data and intent of those who planned the images.&#10;Credit: NASA\/JPL-Caltech\" class=\"wp-image-144994\" srcset=\"https:\/\/www.universetoday.com\/wp-content\/uploads\/2020\/02\/Pale-Blue-dot-1024x576.jpg 1024w, https:\/\/www.universetoday.com\/wp-content\/uploads\/2020\/02\/Pale-Blue-dot-580x326.jpg 580w, https:\/\/www.universetoday.com\/wp-content\/uploads\/2020\/02\/Pale-Blue-dot-250x141.jpg 250w, https:\/\/www.universetoday.com\/wp-content\/uploads\/2020\/02\/Pale-Blue-dot-768x432.jpg 768w, https:\/\/www.universetoday.com\/wp-content\/uploads\/2020\/02\/Pale-Blue-dot.jpg 1400w\" sizes=\"auto, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 543px, 580px\"\/><figcaption class=\"wp-element-caption\">This updated version of the iconic \u201cPale Blue Dot\u201d image taken by the Voyager 1 spacecraft uses modern image-processing software and techniques to revisit the well-known Voyager view while attempting to respect the original data and intent of those who planned the images.<br \/>\nCredit: NASA\/JPL-Caltech<\/figcaption><\/figure>\n<p>Several of Voyager 1\u2019s science instruments are shut down, including its ultraviolet spectrometer, the plasma subsystem, planetary radio astronomy instrument, and scan platform. In the not-too-distant future, more instruments will be powered down, along with the data tape recorder, the gyroscopes, and other systems will be off. Sometime in the next decade, the spacecraft won\u2019t have enough power to keep anything running, and that is when we\u2019ll finally lose contact with Voyager 1. <\/p>\n<p>This will probably happen by the mid-2030s, and by that time, Voyager 1 will have been \u201cin service\u201d for around 55 years. Along with its twin, Voyager 2, this spacecraft opened up exploration of the outer solar system and interstellar space. They\u2019ll continue out to the stars, their last mission being as a calling card to any civilizations that might find them in the distant future.<\/p>\n<h4 class=\"wp-block-heading\" id=\"h-for-more-information\">For More Information<\/h4>\n<p>NASA\u2019s Voyager 1 Resumes Sending Engineering Updates to Earth<br \/>Engineers Pinpoint Cause of Voyager 1 Issue, Are Working on Solution<\/p>\n<div class=\"sharedaddy sd-block sd-like jetpack-likes-widget-wrapper jetpack-likes-widget-unloaded\" id=\"like-post-wrapper-24000880-166733-662721ff7f7fe\" data-src=\"https:\/\/widgets.wp.com\/likes\/?ver=13.2#blog_id=24000880&amp;post_id=166733&amp;origin=www.universetoday.com&amp;obj_id=24000880-166733-662721ff7f7fe&amp;n=1\" data-name=\"like-post-frame-24000880-166733-662721ff7f7fe\" data-title=\"Like or Reblog\">\n<h3 class=\"sd-title\">Like this:<\/h3>\n<p><span class=\"button\"><span>Like<\/span><\/span> <span class=\"loading\">Loading&#8230;<\/span><\/p>\n<p><span class=\"sd-text-color\"\/><\/div>\n<\/p><\/div>\n<p><br \/>\n<br \/><a href=\"https:\/\/www.universetoday.com\/166733\/nasa-restores-communications-with-voyager-1\/?rand=772204\">Source link <\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>The venerable Voyager 1 spacecraft is finally phoning home again. This is much to the relief of mission engineers, scientists, and Voyager fans around the world. On November 14, 2023,&hellip; <\/p>\n","protected":false},"author":1,"featured_media":781226,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[13],"tags":[],"class_list":["post-781225","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-genaero"],"_links":{"self":[{"href":"https:\/\/spaceweekly.com\/index.php?rest_route=\/wp\/v2\/posts\/781225","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/spaceweekly.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/spaceweekly.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/spaceweekly.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/spaceweekly.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=781225"}],"version-history":[{"count":0,"href":"https:\/\/spaceweekly.com\/index.php?rest_route=\/wp\/v2\/posts\/781225\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/spaceweekly.com\/index.php?rest_route=\/wp\/v2\/media\/781226"}],"wp:attachment":[{"href":"https:\/\/spaceweekly.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=781225"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/spaceweekly.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=781225"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/spaceweekly.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=781225"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}