{"id":16980,"date":"2024-03-15T00:46:16","date_gmt":"2024-03-15T00:46:16","guid":{"rendered":"https:\/\/shareperformanceinsight.com\/index.php\/2024\/03\/15\/aging-voyager-1-sends-back-surprising-response-after-poke-from-earth\/"},"modified":"2024-03-15T00:46:16","modified_gmt":"2024-03-15T00:46:16","slug":"aging-voyager-1-sends-back-surprising-response-after-poke-from-earth","status":"publish","type":"post","link":"https:\/\/shareperformanceinsight.com\/index.php\/2024\/03\/15\/aging-voyager-1-sends-back-surprising-response-after-poke-from-earth\/","title":{"rendered":"Aging Voyager 1 sends back surprising response after \u2018poke\u2019 from Earth"},"content":{"rendered":"<div>\n<p class=\"paragraph inline-placeholder\">            Engineers have sent a \u201cpoke\u201d to the Voyager 1 probe and received a potentially encouraging response as they hope to fix a communication issue with the aging spacecraft that has persisted for five months.    <\/p>\n<p class=\"paragraph inline-placeholder\">            Launched in 1977, Voyager 1 and its twin, Voyager 2, are venturing through uncharted cosmic territory along the outer reaches of the solar system.    <\/p>\n<p class=\"paragraph inline-placeholder\">            While Voyager 1 has continued to relay a steady radio signal to its mission control team on Earth, that signal has not carried any usable data since November, which has pointed to an issue with one of the spacecraft\u2019s three onboard computers.    <\/p>\n<p class=\"paragraph inline-placeholder\">            A new signal recently received from the spacecraft suggests that the NASA mission team may be making progress in its quest to understand what Voyager 1 is experiencing. Voyager 1 is currently the farthest spacecraft from Earth at about 15 billion miles (24 billion kilometers) away.    <\/p>\n<div class=\"related-content_full-width related-content_full-width--article\">\n<div class=\"related-content_full-width__image image__related-content\">            <\/div>\n<p class=\"related-content_full-width__headline\">            <span class=\"related-content_full-width__title-text\">Related article<\/span>      <span class=\"related-content_full-width__headline-text\">See the new \u2018golden record\u2019 launching to an ocean world this year<\/span>    <\/p>\n<\/div>\n<p class=\"paragraph inline-placeholder\">            Meanwhile, Voyager 2 has traveled more than 12.6 billion miles (20.3 billion kilometers) from our planet. Both are in interstellar space and are the only spacecraft ever to operate beyond the heliosphere, the sun\u2019s bubble of magnetic fields and particles that extends well beyond the orbit of Pluto.    <\/p>\n<p class=\"paragraph inline-placeholder\">            Initially designed to last five years, the Voyager probes are the two longest-operating spacecraft in history. Their exceptionally long life spans mean that both spacecraft have provided additional insights about our solar system and beyond after achieving their preliminary goals of flying by Jupiter, Saturn, Uranus and Neptune decades ago.    <\/p>\n<p class=\"paragraph inline-placeholder\">            But both probes have faced challenges along the way as they age.    <\/p>\n<h3 class=\"subheader\">    Cosmic communication breakdown<\/h3>\n<p class=\"paragraph inline-placeholder\">            The mission team first noticed the communication issue with Voyager 1 on November 14, 2023, when the flight data system\u2019s telemetry modulation unit began sending a repeating pattern of code.    <\/p>\n<p class=\"paragraph inline-placeholder\">            Voyager 1\u2019s flight data system collects information from the spacecraft\u2019s science instruments and bundles it with engineering data that reflects the current health status of Voyager 1. Mission control on Earth receives that data in binary code, or a series of ones and zeroes.    <\/p>\n<p class=\"paragraph inline-placeholder\">            But since November, Voyager 1\u2019s flight data system has been stuck in a loop.    <\/p>\n<p class=\"paragraph inline-placeholder\">            The spacecraft can still receive and carry out commands transmitted from the mission team, but a problem with that telecommunications unit meant no science or engineering data from Voyager 1 was transmitting to Earth.    <\/p>\n<p class=\"paragraph inline-placeholder\">            Since discovering the issue, the mission team has attempted sending commands to restart the computer system and learn more about the underlying cause of the issue.    <\/p>\n<p class=\"paragraph inline-placeholder\">            The team sent a command, called a \u201cpoke,\u201d to Voyager 1 on March 1 to get the flight data system to run different software sequences in case some type of glitch was causing the issue.    <\/p>\n<div class=\"related-content_full-width related-content_full-width--article\">\n<div class=\"related-content_full-width__image image__related-content\">            <\/div>\n<p class=\"related-content_full-width__headline\">            <span class=\"related-content_full-width__title-text\">Related article<\/span>      <span class=\"related-content_full-width__headline-text\">One of the most iconic pieces of space exploration history goes up for auction<\/span>    <\/p>\n<\/div>\n<p class=\"paragraph inline-placeholder\">            On March 3, the team noticed that activity from one part of the flight data system stood out from the rest of the garbled data. While the signal wasn\u2019t in the format the Voyager team is used to when the flight data system is functioning as expected, an engineer with NASA\u2019s Deep Space Network was able to decode it.    <\/p>\n<p class=\"paragraph inline-placeholder\">            The Deep Space Network is a system of radio antennas on Earth that help the agency communicate with the Voyager probes and other spacecraft exploring our solar system.    <\/p>\n<p class=\"paragraph inline-placeholder\">            The decoded signal included a readout of the entire flight data system\u2019s memory, according to an update NASA shared.    <\/p>\n<p class=\"paragraph inline-placeholder\">            \u201cThe (flight data system) 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,\u201d according to a NASA blog post. \u201cIt 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.\u201d    <\/p>\n<h3 class=\"subheader\">    How the Voyager probes keep going<\/h3>\n<p class=\"paragraph inline-placeholder\">            Voyager 1 is so far away that it takes 22.5 hours for commands sent from Earth to reach the spacecraft. Additionally, the team must wait 45 hours to receive a response. Currently, the team is analyzing Voyager 1\u2019s memory readout after initially beginning the decoding process on March 7 and finding the readout three days later.    <\/p>\n<p class=\"paragraph inline-placeholder\">            \u201cUsing that information to devise a potential solution and attempt to put it into action will take time,\u201d according to the space agency.    <\/p>\n<div class=\"related-content_full-width related-content_full-width--article\">\n<div class=\"related-content_full-width__image image__related-content\">            <\/div>\n<p class=\"related-content_full-width__headline\">            <span class=\"related-content_full-width__title-text\">Related article<\/span>      <span class=\"related-content_full-width__headline-text\">Color-corrected images reveal accurate portraits of Uranus and Neptune<\/span>    <\/p>\n<\/div>\n<p class=\"paragraph inline-placeholder\">            The last time Voyager 1 experienced a similar, but not identical, issue with the flight data system was in 1981, and the current problem does not appear to be connected to other glitches the spacecraft has experienced in recent years.    <\/p>\n<p class=\"paragraph inline-placeholder\">            Over time, both spacecraft have encountered unexpected issues and dropouts, including a seven-month period in 2020 when Voyager 2 couldn\u2019t communicate with Earth. In August 2023, the mission team used a long-shot \u201cshout\u201d technique to restore communications with Voyager 2 after a command inadvertently oriented the spacecraft\u2019s antenna in the wrong direction.    <\/p>\n\n<div>This post appeared first on cnn.com<\/div>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>Engineers have sent a \u201cpoke\u201d to the Voyager 1 probe and received a potentially encouraging response as they hope to fix a communication issue with the aging spacecraft that has persisted for five months. Launched in 1977, Voyager 1 and its twin, Voyager 2, are venturing through uncharted cosmic territory along the outer reaches of <\/p>\n","protected":false},"author":0,"featured_media":16981,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[23],"tags":[],"class_list":{"0":"post-16980","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-world"},"_links":{"self":[{"href":"https:\/\/shareperformanceinsight.com\/index.php\/wp-json\/wp\/v2\/posts\/16980","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/shareperformanceinsight.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/shareperformanceinsight.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"replies":[{"embeddable":true,"href":"https:\/\/shareperformanceinsight.com\/index.php\/wp-json\/wp\/v2\/comments?post=16980"}],"version-history":[{"count":0,"href":"https:\/\/shareperformanceinsight.com\/index.php\/wp-json\/wp\/v2\/posts\/16980\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/shareperformanceinsight.com\/index.php\/wp-json\/wp\/v2\/media\/16981"}],"wp:attachment":[{"href":"https:\/\/shareperformanceinsight.com\/index.php\/wp-json\/wp\/v2\/media?parent=16980"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/shareperformanceinsight.com\/index.php\/wp-json\/wp\/v2\/categories?post=16980"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/shareperformanceinsight.com\/index.php\/wp-json\/wp\/v2\/tags?post=16980"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}