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. dylan6+2H1[view] [source] 2023-07-31 18:50:13
>>hutzli+79
reminds me of the time I forgot i was on a remote connection, and could not figure out why the thing quit responding when i typed eth0 down
◧◩◪
3. ryanis+Ko8[view] [source] 2023-08-02 16:14:34
>>dylan6+2H1
Heh, this reminds me of my ~10 year old self. I had unknowingly infected my family PC with some form of malware, but no knowledge of AV software. I guessed, incorrectly, that perhaps the OS developers would have been smart enough to disallow users from deleting OS owned/managed files. So I went around finding and deleting everything that looked remotely official, including C:\Windows\System32. To my surprise, it worked. Until I rebooted :(
[go to top]