Strange Mi Images Options

[Guest_BruceMoomaw_*]

They have had a large number of rather mysterious computer resets recently on MER-B, according to Doug McCuistion. (Some of them seem to be associated with the Mini-TES, for which reason it is now infrequently used.)

[Tesheiner]

According to the planned sequences, sol 655 would be dedicated to the Mossbauer Spectrometer, but once again the IDD is missing in the hazcam pics.

http://marsrovers.jpl.nasa.gov/gallery/all...CP1131L0M1.HTML

---
655 p1131.04 2 0 2 0 0 4 f_haz_idd_mb_doc_512x512x1bpp_vhigh
---

[Guest_Sunspot_*]

We just have to accept that this far into the mission things are likely to breakdown But loosing 4 science instruments at once is a major blow.

[Tesheiner]

I'm of the opinion that this "hiccup" is related to a sequencing error.
But we (me at least) don't have enough information to be sure.

I think the best will be just to wait for some news update from JPL and/or Cornell.

[Toma B]

Of course there is always a good side in this situation...

I know this might anger some of you guys...but if IDD arm is permanently stuck , then Opportunity will just have to drive a lot more...and maybe drive all the way to that awesome Victoria crater which is great isn't it?

[Tesheiner]

Someone at the "other" forum remarked that something similar happened to Spirit on sol 150.
Here is the MER status report about the issue: http://marsrovers.jpl.nasa.gov/mission/sta...All.html#sol148

Spirit used its alpha particle X-ray spectrometer and Mössbauer spectrometer to observe a rock called "Joshua" on sol 150. Unfortunately, the rest of the sol's planned work with the instrument deployment device did not take place because of a command anomaly, which made Spirit think that a collision between the rock abrasion tool and the forearm might occur. Therefore, the tool change and all subsequent arm motions were prevented for the rest of the sol.

Spirit was back to business on sol 151, and finished observing Joshua and the science magnets with the tools on the instrument deployment device. After that, the rover was off, and successfully completed a 73-meter (240 feet) drive toward the Columbia Hills.

[Cugel]

Someone at the "other" forum remarked that something similar happened to Spirit on sol 150.
Here is the MER status report about the issue: http://marsrovers.jpl.nasa.gov/mission/sta...All.html#sol148

Hope you're right, but how similar is similar?
Did Spirit take 56 identical MI images in a stowed position?

[Bill Harris]

Thanks, Tesheiner, I seemed to recall an earlier anomaly but couldn't remember the details.

To confirm what we have assumed what we see, I found an MI image from Sol 002 taken with the IDD stowed; it shows the same objects in the field of view that we see now. The dust cover was open, so the image is clearer (I suspect that the dust cover now has a coating of dust). The right front wheel can be seen in the background as this image was taken before the wheels were unfolded into the working position.

Interesting to browse those first images...

--Bill

[Tesheiner]

OT: Look how clean is that wheel!

[Bill Harris]

OT^2 : But considering that the wheel has turned over 5000 times during 4Km of travel, it is quite unworn today!

--Bill

[Guest_Edward Schmitz_*]

The difference in the previous anomoly is that the sequence aborted. In this case we have 50+ images of the rover. If the arm were simply stuck, it shouldn't have done anything else.

Something else is happening. I'm voting for poorly constructed sequence.

ed

[edstrick]

Note that this problem has occurred during the 4 day Thanksgiving Holiday Weekend in the US. I assume they parked both rovers at nice outcrops and planned LONG Mossbauer integrations and the like... basically a 4 or 5 day pre-programmed sequence so people could have most of the weekend off.

[Toma B]

Note that this problem has occurred during the 4 day Thanksgiving Holiday Weekend in the US.  I assume they parked both rovers at nice outcrops and planned LONG Mossbauer integrations and the like... basically a 4 or 5 day pre-programmed sequence so people could have most of the weekend off.

AAAARRRRGGGHHHH!!!!!!
So is that waisting precious time or what...nobody looked at raw images , nobody to react because they are on holiday?
I'm not trying to start another "They deserve a rest once in a while" discusion , just thinking how many of you guys would sacrifice your holidays so that you can be in control of vehicle on Mars...I would...
Yes I know that it's not "just sit back and drive" but these guys are so privileged few who can DRIVE ROVERS ON ANOTHER PLANET...I would sell my soul to &$*#@ and work 365 days a year , without salary or food to have their job...are they looking for rover drivers?

[Enrique Bunbury]

Note that this problem has occurred during the 4 day Thanksgiving Holiday Weekend in the US.  I assume they parked both rovers at nice outcrops and planned LONG Mossbauer integrations and the like... basically a 4 or 5 day pre-programmed sequence so people could have most of the weekend off.

OMG! xDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD

[edstrick]

Uh.... (imagined conversation)

Spouse to Rover Driver: "Either you figure some way to drive that (expletive deleted) thing over a clifF, or I'm getting a divorce. 90 days is one thing, but nearly two years and no end in sight, I'va HAD IT!"

It's not as though they were sitting there doing nothing.. It's just a decidedly unfortunate time for a glitch.