{"id":779081,"date":"2024-03-18T06:37:53","date_gmt":"2024-03-18T11:37:53","guid":{"rendered":"http:\/\/spaceweekly.com\/?p=779081"},"modified":"2024-03-18T06:37:53","modified_gmt":"2024-03-18T11:37:53","slug":"voyager-1-spacecraft-has-sent-a-partly-decipherable-message","status":"publish","type":"post","link":"https:\/\/spaceweekly.com\/?p=779081","title":{"rendered":"Voyager 1 spacecraft has sent a (partly) decipherable message"},"content":{"rendered":"<p> <br \/>\n<\/p>\n<div>\n<figure id=\"attachment_468772\" aria-describedby=\"caption-attachment-468772\" style=\"width: 800px\" class=\"wp-caption alignnone\"><figcaption id=\"caption-attachment-468772\" class=\"wp-caption-text\">Artist\u2019s concept shows Voyager 1 against a starry background. The spacecraft, launched in 1977, is no longer in our solar system. But it still communicates with Earth, and in November 2023 it started sending back gibberish. Now NASA engineers says they\u2019ve been able to decipher a new message that Voyager 1 sent in March. Image via Caltech\/ NASA-JPL.<\/figcaption><\/figure>\n<ul>\n<li><strong>NASA\u2019s Voyager 1 spacecraft<\/strong> launched from Earth in 1977. It passed out of the heliosphere \u2013 or sphere of our sun\u2019s influence \u2013 in 2012. In all that time, Voyager 1 has been communicating with Earth.<\/li>\n<li><strong>But since November 2023<\/strong> \u2013 though still sending radio signals back to Earth \u2013 Voyager 1 has been sending back only gibberish.<\/li>\n<li><strong>Some hope appeared in early March 2024<\/strong>, however, after NASA engineers tried a special command, called a \u201cpoke\u201d by the team. Following the \u201cpoke,\u201d the team was able to decipher a message from the spacecraft, although with difficulty.<\/li>\n<\/ul>\n<p>NASA published this original article on March 13, 2024. Edits by EarthSky.<\/p>\n<h3>Voyager 1 is starting to make some sense<\/h3>\n<p>Since November 2023, NASA\u2019s Voyager 1 spacecraft has been sending a steady radio signal to Earth, but the signal does not contain usable data. The source of the issue appears to be with one of three onboard computers \u2013 the flight data subsystem, or FDS \u2013 which is responsible for packaging the science and engineering data before it\u2019s sent to Earth by the telemetry modulation unit (a data encoder).<\/p>\n<p>Please help EarthSky keep going! Our annual crowd-funder is going on now. PLEASE DONATE today to continue enjoying updates on your cosmos and world.<\/p>\n<p>On March 3, the Voyager mission team saw activity from one section of the FDS that differed from the rest of the computer\u2019s unreadable data stream. The new signal was still not in the format used by Voyager 1 when the FDS is working properly, so the team wasn\u2019t initially sure what to make of it. But an engineer with the agency\u2019s Deep Space Network, which operates the radio antennas that communicate with both Voyagers and other spacecraft traveling to the moon and beyond, was able to decode the new signal and found that it contains a readout of the entire FDS memory.<\/p>\n<p>The FDS memory includes its code, or instructions for what to do, as well as variables, or values used in the code that can change based on commands or the spacecraft\u2019s status. It also contains science or engineering data for downlink. The team will compare this readout to the one that came down before the issue arose and look for discrepancies in the code and the variables to potentially find the source of the ongoing issue.<\/p>\n<p>This new signal resulted from a command sent to Voyager 1 on March 1. Called a \u201cpoke\u201d by the team, the command is meant to gently prompt the FDS to try different sequences in its software package in case the issue could be resolved by going around a corrupted section.<\/p>\n<h3>2-way communication takes a long time<\/h3>\n<p>Because Voyager 1 is more than 15 billion miles (24 billion kilometers) from Earth, it takes 22.5 hours for a radio signal to reach the spacecraft. And then it\u2019s another 22.5 hours for the probe\u2019s response to reach antennas on the ground. So the team received the results of the command on March 3. On March 7, engineers began working to decode the data. Finally, on March 10, they determined that it contains a memory readout.<\/p>\n<p>The team is analyzing the readout. Using that information to devise a potential solution and attempt to put it into action will take time.<\/p>\n<p>Bottom line: The Voyager 1 spacecraft \u2013 which launched in 1977 and has now traveled out of our solar system \u2013 started sending gibberish back to Earth in November. Now engineers have sent it a \u201cpoke\u201d and received a message they\u2019ve been able to decipher.<\/p>\n<p>Via NASA<\/p>\n<p>Read more: Why are the Voyager spacecraft getting closer to Earth?<\/p>\n<p>Read more: SETI finds sign of intelligence, and it\u2019s our own Voyager 1<\/p>\n<p><span class=\"cp-load-after-post\"\/><\/div>\n<div>\n<div class=\"post-author\">\n<h4>EarthSky Voices<\/h4>\n<p>                    View Articles\n                  <\/p><\/div>\n<div class=\"post-tags\">\n<h6 data-udy-fe=\"text_7c58270d\">About the Author:<\/h6>\n<p>Members of the EarthSky community &#8211; including scientists, as well as science and nature writers from across the globe &#8211; weigh in on what&#8217;s important to them.<\/p>\n<\/p><\/div>\n<\/p><\/div>\n<p><br \/>\n<br \/><a href=\"https:\/\/earthsky.org\/space\/voyager-1-message-decipher-progress\/?rand=772280\">Source link <\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Artist\u2019s concept shows Voyager 1 against a starry background. The spacecraft, launched in 1977, is no longer in our solar system. But it still communicates with Earth, and in November&hellip; <\/p>\n","protected":false},"author":1,"featured_media":779082,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[46],"tags":[],"class_list":["post-779081","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-earth-sky"],"_links":{"self":[{"href":"https:\/\/spaceweekly.com\/index.php?rest_route=\/wp\/v2\/posts\/779081","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=779081"}],"version-history":[{"count":0,"href":"https:\/\/spaceweekly.com\/index.php?rest_route=\/wp\/v2\/posts\/779081\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/spaceweekly.com\/index.php?rest_route=\/wp\/v2\/media\/779082"}],"wp:attachment":[{"href":"https:\/\/spaceweekly.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=779081"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/spaceweekly.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=779081"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/spaceweekly.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=779081"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}