this post was submitted on 23 Apr 2024
43 points (100.0% liked)

NASA

1007 readers
13 users here now

Anything related to the NASA (National Aeronautics and Space Administration); the latest news, events, current and future missions, and more.

Note: This community is an unofficial forum and is unaffiliated with NASA or the U.S. government.

Rules

  1. Be respectful and inclusive.
  2. No harassment, hate speech, or trolling.
  3. Engage in constructive discussions.
  4. Share relevant content.
  5. Follow guidelines and moderators' instructions.
  6. Use appropriate language and tone.
  7. Report violations.
  8. Foster a continuous learning environment.

founded 2 years ago
MODERATORS
top 2 comments
sorted by: hot top controversial new old
[–] [email protected] 10 points 7 months ago

The team discovered that a single chip responsible for storing a portion of the FDS memory — including some of the FDS computer’s software code — isn’t working. The loss of that code rendered the science and engineering data unusable. Unable to repair the chip, the team decided to place the affected code elsewhere in the FDS memory. But no single location is large enough to hold the section of code in its entirety.

So they devised a plan to divide the affected code into sections and store those sections in different places in the FDS. To make this plan work, they also needed to adjust those code sections to ensure, for example, that they all still function as a whole. Any references to the location of that code in other parts of the FDS memory needed to be updated as well.

The team started by singling out the code responsible for packaging the spacecraft’s engineering data. They sent it to its new location in the FDS memory on April 18. A radio signal takes about 22 ½ hours to reach Voyager 1, which is over 15 billion miles (24 billion kilometers) from Earth, and another 22 ½ hours for a signal to come back to Earth. When the mission flight team heard back from the spacecraft on April 20, they saw that the modification worked: For the first time in five months, they have been able to check the health and status of the spacecraft.

I find this insane. That you can essentially perform impromptu remote surgery on an object 15 billion miles away, moving at nearly 40,000 mph, and you do this by shuffling code around in a way it was never meant to do. Science be crazy, man!

[–] [email protected] 4 points 7 months ago

Amazing!

Yet still out of transporter range.