zlacker

[return to "NASA mistakenly severs communication to Voyager 2"]
1. hutzli+79[view] [source] 2023-07-31 11:41:35
>>belter+(OP)
In short, it was remote bricked, by giving it commands to rotate a bit. After successfully executing those commands - no further commands could be received, as now the antennas are not facing earth anymore.

But luckily it automatically readjust itself to earth automatically every half year exactly for these events. So on 15.10 we will know, if it is really lost. In either case, the end of its mission is near anyway, because the nuclear batteries are near its end.

edit: Nasa has a blog post on this https://blogs.nasa.gov/sunspot/2023/07/28/mission-update-voy...

◧◩
2. polite+mt[view] [source] 2023-07-31 13:51:45
>>hutzli+79
This link from NASA mentions the October 15 date:

https://www.jpl.nasa.gov/news/nasa-mission-update-voyager-2-...

◧◩◪
3. hutzli+Au[view] [source] 2023-07-31 13:56:19
>>polite+mt
The text and link I provided mention it as well, but I am now not sure, if giving 15.10 as a date was maybe confusing for non europeans (or non germans, I am a bit lost who uses what date format)...
◧◩◪◨
4. Nexxxe+qx2[view] [source] 2023-07-31 23:38:20
>>hutzli+Au
2023-10-15 would be pretty universal.

ISO 8601 works for everyone.

It avoids confusing the Americans who otherwise put the month in the wrong place.

It avoids being ambiguous for everyone who may otherwise be worried that it was written by an American with the month in the wrong place, when the day is less than 13.

2023-10-09 is the 9th of October and it's clear to everyone regardless.

It also has the benefit of sorting chronologically if sorted "by name" when used in a filename as it's largest unit on the left, smallest on the right.

[go to top]