| ▲ | jacquesm 4 hours ago | ||||||||||||||||
What an impressive project. > Next up was maneuvering from our LEO drop-off altitude down to VLEO, where it would be safe to eject the telescope contamination cover Why would it be unsafe to do this earlier? > We had been tracking intermittent memory issues in our TT&C radio throughout the mission, working around them as they appeared. Our best theory is that one of these issues escalated in a way that corrupted onboard memory and is preventing reboots. We've tried several recovery approaches. So far, none have worked, and the likelihood of recovery looks low at this point. Seems to be a pretty big problem as well, I wonder what their ideas are to diagnose the root cause here. It all sounds a bit overoptimistic, but that may just be my interpretation. | |||||||||||||||||
| ▲ | Alasater 3 hours ago | parent | next [-] | ||||||||||||||||
Space safety for sure on the cover, although I'm not sure we'll have that cover for future launches because it was less than easy to coordinate with the FCC on where to eject it. The radio came from a supplier who has been investigating the issue. We had concerns with their NAND and ECC implementation, and we weren’t able to fully root-cause it with them. Going forward, we’ll be building our own radios, which will make it easier to test, iterate, and resolve issues like this internally, or at least be able to trace possible latch ups or destructive failures and implement the right levels of redundancy. | |||||||||||||||||
| |||||||||||||||||
| ▲ | MobiusHorizons 4 hours ago | parent | prev [-] | ||||||||||||||||
I think they want to get low enough that the jettisoned cover will not stay in orbit long or run into anything. | |||||||||||||||||
| |||||||||||||||||