NASA’s Perseverance Mars rover
Discussion
Eric Mc said:
I cannot recall of any attempt by anyone to sabotage a space probe by messing about with its software.
NASA has upgraded programmes and made running repairs on spacecraft software by uploading software when necessary.
Yep, but organisations tend not to publish attempts, and only publish actual breaches when required to do so through regulations etc and even then, the bare minimum so i'm not sure how much info would be in the public domain anyway. NASA has upgraded programmes and made running repairs on spacecraft software by uploading software when necessary.
Also the past is not necessarily a guide to the future. I'd imagine that NASA take technology security of the entire operational process pretty seriously, or at least have a good understanding of existing and emerging threats for the life span of a particular project. I'd just love to know the details, which (to my first point) orgs tend not to publish that either.
CrutyRammers said:
I'm not sure whether to be encouraged or despairing to see that what must be the most rigid, process driven, Tested to the nth degree, bit of software, still ends up needing a last minute patch before go live.
Presumably so anyway. Perhaps its something environmental which has shown up and once they got some actual data relayed back, they re-ran the tests and found that it would require updated data or logic in order to be a success. It's really not unusual for things designed and tested to death to fail in different ways when deployed for real. At least they had contingencies in place.
From this it says they send software to the rover then to the base station which is on the rover then to the chopper.
https://mars.nasa.gov/technology/helicopter/status...
The base station is the gold coloured unit circled in blue
From this it says they send software to the rover then to the base station which is on the rover then to the chopper.
https://mars.nasa.gov/technology/helicopter/status...
The base station is the gold coloured unit circled in blue
Can I say something like: Yes, all this st is thought about and stuff done to deal with and mitigate...and ppl just nod and say ok. Without it descending into the usual PH rancour, questioning and demands of evidence?
If anybody wants to be really bored about aero/space software go and read Q-80 and/or 178C. No, I mean really really bored!
If anybody wants to be really bored about aero/space software go and read Q-80 and/or 178C. No, I mean really really bored!
DeejRC said:
Can I say something like: Yes, all this st is thought about and stuff done to deal with and mitigate...and ppl just nod and say ok. Without it descending into the usual PH rancour, questioning and demands of evidence?
If anybody wants to be really bored about aero/space software go and read Q-80 and/or 178C. No, I mean really really bored!
What are you on about? who is demanding evidence? If anybody wants to be really bored about aero/space software go and read Q-80 and/or 178C. No, I mean really really bored!
bmwmike said:
What are you on about? who is demanding evidence?
I confess I didn't really understand Deej's post.Mine was supposed to be light-hearted. Working in software myself, it's sadly far too common for apparently obvious bugs to only become apparent just as things go live. The usual answer to that is for more rigourous processes around changes and testing. To see something which surely has the most rigourous processes and testing suffer the same issues...well it partly makes me sad, but also, a little vindicated.
AW111 said:
Very tense atmosphere there as the data came in - I found myself holding my breath there for a while.
Years of your life/career on a success or fail after having been caught out a week ago with a software problem.That team can now hope to move on to bigger things in the future.
Gassing Station | Science! | Top of Page | What's New | My Stuff