Oppy Sw/hw Problems |
Oppy Sw/hw Problems |
Oct 16 2005, 12:12 PM
Post
#16
|
|
Member Group: Members Posts: 710 Joined: 28-September 04 Member No.: 99 |
Sol 609:
Sol 614: Opportunity hasn't moved. So what happened to all those drive commands the last few days? |
|
|
Oct 16 2005, 12:20 PM
Post
#17
|
|
Member Group: Members Posts: 362 Joined: 12-June 05 From: Kiama, Australia Member No.: 409 |
|
|
|
Guest_Sunspot_* |
Oct 16 2005, 12:21 PM
Post
#18
|
Guests |
Obviouosly something went wrong the last few sols...... but at least we know the rover is transmitting data again. Today is another planned drive day.
Also I dont think there were any images transmitted from Spirit on sol 634 - they've only just arrived. |
|
|
Oct 16 2005, 12:33 PM
Post
#19
|
|
Member Group: Members Posts: 710 Joined: 28-September 04 Member No.: 99 |
|
|
|
Oct 16 2005, 12:39 PM
Post
#20
|
|
Member Group: Members Posts: 362 Joined: 12-June 05 From: Kiama, Australia Member No.: 409 |
|
|
|
Oct 17 2005, 03:17 AM
Post
#21
|
|
Senior Member Group: Members Posts: 1887 Joined: 20-November 04 From: Iowa Member No.: 110 |
From Steve Squyeres latest update
QUOTE Unfortunately, it was a week of frustration over on the Opportunity side of Mars. You get good luck and bad luck in this game, just like anything else, and we've had more than our share of bad luck at Meridiani lately.
First there was the unexpected drive partway into something we called Telluride Dune, a little drift that was nasty enough that it triggered our slip-check alarm and stopped a drive. Fair enough; that's the way things are supposed to work when the going gets dangerous in this kind of terrain. No sooner did we back out of that, though, than we got hit by another of the mystery reboots that Opportunity has encountered a few times in the past several months. This was different from what hit us on Sol 596... that one we understand and can trace to a simple bug in the software. But this one we don't understand yet, and it cost us a couple more sols. And then, just as soon as we recovered from that, we had a minor problem at one of the Deep Space Network stations and lost two more sols. Not a good week. Each event was benign individually, and each was unrelated to the others. So it really was nothing other than a run of bad luck, for a rover that's had more than its share of good luck. Still, the end result was a week in which we made zero progress toward the Mogollon Rim, so we're going to try to really get things moving in the week ahead. One good piece of news is that this latest mystery reboot was almost identical to one that happened a couple of months ago... and somewhere in that fact may lie the clue that'll help us figure it out. The reboots do no harm to the vehicle, and we've gotten very good at recovering from them. But they cost us sols when they happen, and that's never a good thing. So we're working hard on this one. |
|
|
Oct 17 2005, 07:54 AM
Post
#22
|
|
Senior Member Group: Moderator Posts: 4279 Joined: 19-April 05 From: .br at .es Member No.: 253 |
Ok, those are the bad news.
The good ones are that Oppy has definitely moved on sol 615. Edited: Quite a few images from the new site are available at Exploratorium but the tracking web reports all drive related navcam and pancam images have been already downlinked. Edited#2: The move was about 20m Westward. |
|
|
Oct 17 2005, 01:30 PM
Post
#23
|
|
Junior Member Group: Members Posts: 45 Joined: 25-March 05 Member No.: 216 |
<glass half full>
Nothing terminal with Oppy. </glass half full> -------------------- My Open Office Website: http://www.openofficetips.com
|
|
|
Oct 17 2005, 03:06 PM
Post
#24
|
|
Member Group: Members Posts: 311 Joined: 31-August 05 From: Florida & Texas, USA Member No.: 482 |
QUOTE (avkillick @ Oct 17 2005, 07:30 AM) Considering the reboots are almost certainly to blame of software bugs, they have nothing to do with age. Aside from a lame wheel-motor and a spent hunk of cesium, Oppy is still spry and exhuberant. I'm surpized by the outages at DSN; seems like several failures in a row. Maybe they need some refurbishment? That could be a huge deal for a mission like Cassini or Deep Impact, where data buffering on the probe is very limited and the targets are often 1-shot passes. I guess I should dig up my digerdoo and light a nice fire, like the shaman from All The Right Stuff. Hey, it worked for Spirit's first reboot! |
|
|
Oct 17 2005, 03:17 PM
Post
#25
|
|
Senior Member Group: Members Posts: 1636 Joined: 9-May 05 From: Lima, Peru Member No.: 385 |
The Spirit is not experiencing any software bug like Opportunity. I am thinking that the software logaritm of Opportunity must be different than Spirit. Maybe, it has an additional logic for sleepage computing and any avoidance manouvers related to that.
Rodolfo |
|
|
Oct 17 2005, 03:37 PM
Post
#26
|
|
Dublin Correspondent Group: Admin Posts: 1799 Joined: 28-March 05 From: Celbridge, Ireland Member No.: 220 |
QUOTE (RNeuhaus @ Oct 17 2005, 04:17 PM) The Spirit is not experiencing any software bug like Opportunity. I am thinking that the software logaritm of Opportunity must be different than Spirit. Maybe, it has an additional logic for sleepage computing and any avoidance manouvers related to that. Rodolfo Don't think so - both are running the same version of the flight software. The environments and use cases are different though and there are operational parameters that differe between the two so situations arise on Oppy that don't arise on Spirit (and vice versa). What is very different between the two is the day to day sequencing. It's very easy to see how a bug might be triggerred by a set of procedures on Oppy that never occurs on Spirit. |
|
|
Oct 17 2005, 08:53 PM
Post
#27
|
|
Member Group: Members Posts: 866 Joined: 15-March 05 From: Santa Cruz, CA Member No.: 196 |
...then again the 'software bug' might be precipitated by environmental factors such as voltage irregularities perhaps caused by temperature variations or static charges on weathered components, and these may originate in wires or smaller componenets that arent monitored by the onboard software and so might have nothing at all to do with any software flaw (other than the ability of the software to adapt to such conditions without rebooting, which might not be desireable 'capability' anyway).
Can they monitor all aspects of all parts between critical components? IOt sounds like a lot of extra complexity and weight to include. Theyve got the basics covered but is there a signifficant unknown factor about many smaller componenets? Unless they have ways of determining such things with all parts of the rover, we may be seeing propogated effects of physical breakdown of as-yet unknown components the rover. |
|
|
Oct 17 2005, 09:06 PM
Post
#28
|
|
Senior Member Group: Members Posts: 1636 Joined: 9-May 05 From: Lima, Peru Member No.: 385 |
The software bug is still unclear up to Sqyures who wrote in his Athena's publication that nobody has clear understand of this case. This is still under an investigation.
Fair enough; that's the way things are supposed to work when the going gets dangerous in this kind of terrain. No sooner did we back out of that, though, than we got hit by another of the mystery reboots that Opportunity has encountered a few times in the past several months. This was different from what hit us on Sol 596... that one we understand and can trace to a simple bug in the software. But this one we don't understand yet, and it cost us a couple more sols.. It is probably not caused by software flawless but by an environment factor.... An fancy idea is that close Erebus might have a strong magnetic field caused by an strange meteoro that might be causing troubles to the electronic devices... Rodolfo |
|
|
Oct 17 2005, 09:56 PM
Post
#29
|
|
Dublin Correspondent Group: Admin Posts: 1799 Joined: 28-March 05 From: Celbridge, Ireland Member No.: 220 |
QUOTE (atomoid @ Oct 17 2005, 09:53 PM) Can they monitor all aspects of all parts between critical components? IOt sounds like a lot of extra complexity and weight to include. There's not enough hard data to be sure but the occassional hint indicates that they have enough engineering data to identify the location of shorts, stuck switches, under performing heaters and the like. They certainly have shown the ability to profile current changes that happen when steering actuators get stuck, wheels slip, heaters remain stuck and thereby identify the precise cause of those types of problems. The daily reports show that they were able to identify the "cleaning" events based on a 5% change in power output vs predicted output. I think it's reasonable to assume that they can tell immediately (well by the next downlink) if any of the powered devices are working incorrectly. Overall I'd say that they have a fair idea about the wear and tear but that doesn't mean that there aren't some wild cards - the intermittent problems with the Mini-TES show that they don't have absolute knowledge of the health of every single component. This is pretty telling though - : QUOTE .. One good piece of news is that this latest mystery reboot was almost identical to one that happened a couple of months ago... and somewhere in that fact may lie the clue that'll help us figure it out. The reboots do no harm to the vehicle, and we've gotten very good at recovering from them. That makes me think that he believes they have enough data now to root cause this too. |
|
|
Oct 17 2005, 10:10 PM
Post
#30
|
|
Senior Member Group: Members Posts: 2998 Joined: 30-October 04 Member No.: 105 |
QUOTE Don't think so - both are running the same version of the flight software. The environments and use cases are different though and there are operational parameters that differ... Aren't the hazard avoidance routines in Oppy modified for driving across the rippled environment? That could be a critical difference. --Bill -------------------- |
|
|
Lo-Fi Version | Time is now: 27th May 2024 - 02:29 PM |
RULES AND GUIDELINES Please read the Forum Rules and Guidelines before posting. IMAGE COPYRIGHT |
OPINIONS AND MODERATION Opinions expressed on UnmannedSpaceflight.com are those of the individual posters and do not necessarily reflect the opinions of UnmannedSpaceflight.com or The Planetary Society. The all-volunteer UnmannedSpaceflight.com moderation team is wholly independent of The Planetary Society. The Planetary Society has no influence over decisions made by the UnmannedSpaceflight.com moderators. |
SUPPORT THE FORUM Unmannedspaceflight.com is funded by the Planetary Society. Please consider supporting our work and many other projects by donating to the Society or becoming a member. |