IPB

Welcome Guest ( Log In | Register )

16 Pages V   1 2 3 > »   
Reply to this topicStart new topic
Strange Mi Images
dot.dk
post Nov 26 2005, 09:39 AM
Post #1


Member
***

Group: Members
Posts: 577
Joined: 5-November 04
From: Denmark
Member No.: 107



All the latest MI images from Opportunity shows this part of the rover:

http://qt.exploratorium.edu/mars/opportuni...KCP2957M1M1.JPG

The only thing I can think of is that it is an image taken with the IDD stowed.

Actually the front hazcam pictures confirms this. What can the reason for this be? huh.gif

A problem with the IDD so it didn't unstow, but somehow the MI carried out its tasks? blink.gif


--------------------
"I want to make as many people as possible feel like they are part of this adventure. We are going to give everybody a sense of what exploring the surface of another world is really like"
- Steven Squyres
Go to the top of the page
 
+Quote Post
Bill Harris
post Nov 26 2005, 12:27 PM
Post #2


Senior Member
****

Group: Members
Posts: 2344
Joined: 30-October 04
Member No.: 105



Does not look good, dot.dk. Those "odd" MI images were taken first over a period of an hour and then again 4 hours later. It does look like the IDD won't unstow and the dust cover is still in place.

Let me dig and find the planned task sequence for that Sol.

--Bill


--------------------
Go to the top of the page
 
+Quote Post
Bill Harris
post Nov 26 2005, 12:46 PM
Post #3


Senior Member
****

Group: Members
Posts: 2344
Joined: 30-October 04
Member No.: 105



From http://marswatch.astro.cornell.edu/merweb/merweb.pl , here is part of the tracking report:



1. What new EDRs from ANY sol were received on sol 654?

Number of EDRs received by sol, sequence number, and image type:

Sol Seq.Ver ETH ESF EDN EFF ERP Tot Description
--- -------- --- --- --- --- --- ---- -----------
654 p2936.02 1 0 0 1 0 2 mi_open_minloss2_LUT3_veryhigh
654 p2936.02 1 0 0 1 0 2 mi_open_minloss2_LUT3_veryhigh
654 p2936.02 1 0 0 1 0 2 mi_open_minloss2_LUT3_veryhigh
654 p2936.02 1 0 0 1 0 2 mi_open_minloss2_LUT3_veryhigh
654 p2936.02 1 0 0 1 0 2 mi_open_minloss2_LUT3_veryhigh
654 p2936.02 1 0 0 1 0 2 mi_open_minloss2_LUT3_veryhigh
654 p2936.02 1 0 0 1 0 2 mi_open_minloss2_LUT3_veryhigh
654 p2936.02 1 0 0 1 0 2 mi_open_minloss2_LUT3_veryhigh
654 p2936.02 1 0 0 1 0 2 mi_open_minloss2_LUT3_veryhigh
654 p2936.02 1 0 0 1 0 2 mi_open_minloss2_LUT3_veryhigh
654 p2956.02 1 0 0 1 0 2 mi_open_minloss2_LUT3_high_DNTH2000
<snip>


I don't know what the interpretation of this is, so I'll leave it to others.

--Bill


--------------------
Go to the top of the page
 
+Quote Post
Decepticon
post Nov 26 2005, 12:49 PM
Post #4


Senior Member
****

Group: Members
Posts: 1156
Joined: 25-November 04
Member No.: 114



Are there anymore pics like this?
Go to the top of the page
 
+Quote Post
Guest_Sunspot_*
post Nov 26 2005, 01:34 PM
Post #5





Guests






If the sequence to deploy and carefully postion the IDD arm hadn't worked, would the sequence designed to take the images have started? I would have thought it wouldn't - just a guess though.

6. What unexpected sequences ran? (that is, sequences we did not enter in the SSF
list file /home/mersci/pan/B/ops/Sol_all_seq_list.txt)

No unexpected sequences run.

Thats the only problem with the pancam tracking site - lots of information, we just dont know how to interpret much of it lol.

Also......I don't think i've seen so many MI's taken in a single sol as this one. blink.gif
Go to the top of the page
 
+Quote Post
Jeff7
post Nov 26 2005, 05:17 PM
Post #6


Member
***

Group: Members
Posts: 477
Joined: 2-March 05
Member No.: 180



Maybe they're checking for changes in dust deposition over a period of time? blink.gif
Even that seems an odd way to do it though, and not very effective. Wonder if someone just forgot a command when programming the sequence.
Go to the top of the page
 
+Quote Post
Guest_Sunspot_*
post Nov 26 2005, 05:26 PM
Post #7





Guests






We've been at this site for about 3 days, and the IDD hasn't been deployed yet which seems a little unusual to me, its normally deployed almost immediately. Maybe those images were intended to see if there was any reason why it waas stuck blink.gif blink.gif
Go to the top of the page
 
+Quote Post
OWW
post Nov 26 2005, 06:39 PM
Post #8


Member
***

Group: Members
Posts: 691
Joined: 28-September 04
Member No.: 99



QUOTE (Sunspot @ Nov 26 2005, 05:26 PM)
We've been at this site for about 3 days, and the IDD hasn't been deployed yet which seems a little unusual to me, its normally deployed almost immediately.  Maybe those images were intended to see if there was any reason why it waas stuck  blink.gif  blink.gif
*


I don't think so. The reason they took those front hazcam pics is that the IDD is supposed to do its stuff. And who needs 33 MI-pictures of the same area for an inspection?
I think the computer sees some restriction for the arm and therefore doesn't move it. Either that, or the arm is stuck for some reason. huh.gif Let's wait and see what happens after the weekend.
Go to the top of the page
 
+Quote Post
Cugel
post Nov 27 2005, 02:36 PM
Post #9


Member
***

Group: Members
Posts: 153
Joined: 11-December 04
Member No.: 120



Even more MI pictures came down.... all the same.
On the forward hazcam pictures of yesterday you can see some small position changes in the arm. But the pictures of today show no movement (let alone deployment) of the arm at all. I think we can 'officially' declare an emergency situation here.
Start speculating about the value of this mission without the IDD?
We still have pancam and MiniTes of course.
Go to the top of the page
 
+Quote Post
Bill Harris
post Nov 27 2005, 02:53 PM
Post #10


Senior Member
****

Group: Members
Posts: 2344
Joined: 30-October 04
Member No.: 105



The mission is valuable. Oppy still has mobility and the Haz-, Nav- and Pancams. We've simply misplaced our handlens and scratch-plate. There may be a solution to this problem, but for the time being, the arm be stuck...

--Bill


--------------------
Go to the top of the page
 
+Quote Post
akuo
post Nov 27 2005, 04:24 PM
Post #11


Member
***

Group: Members
Posts: 436
Joined: 24-March 04
From: Finland
Member No.: 63



A bit early to declare emegency without any info from JPL. It might be a simple sequencing error by the mission planners, after which they let Oppy be as she is for the weekend because of holidays and the weekend. Even if there was a problem, they probably wouldn't start debugging it until monday.


--------------------
Antti Kuosmanen
Go to the top of the page
 
+Quote Post
RNeuhaus
post Nov 27 2005, 05:20 PM
Post #12


Senior Member
****

Group: Members
Posts: 1636
Joined: 9-May 05
From: Lima, Peru
Member No.: 385



The Oppy might have experienced any problems with the IDD and have performed a safety reset: SAFE MODE. After this reset, it will clear any software bug that might have stuck the arms and facilite the engineering rover to analyze the origins of the problem.

I don't think that the arms might have been broken because of any strike on the surface because the IDD is is proctected by the safety margin algorithm software. I think it so. It is logical to incorporate that software to MER in order to protect of the valuable instrument against any accident strikes on the surface.

Hope that won't ham to the instruments of the arm then.

Rodolfo
Go to the top of the page
 
+Quote Post
Guest_Edward Schmitz_*
post Nov 27 2005, 07:41 PM
Post #13





Guests






It is more likely a sequence problem than a hardware problem. If the arm didn't do what it was instructed to do, the sequence would have been aborted. Let's wait and see what JPL has to say before we get too worried.
Go to the top of the page
 
+Quote Post
tty
post Nov 27 2005, 08:01 PM
Post #14


Member
***

Group: Members
Posts: 683
Joined: 20-April 05
From: Sweden
Member No.: 273



On the other hand there have been a couple of glitches with Opportunity's IDD before, which might be due to hardware problems (cable fraying) (see Steve Squyres transcript). I suppose this would make JPL extra cautious before trying anything if there are problems. Having the IDD stick in the folded position would be bad, but not catastrophic. Having it stick in the deployed position would be much worse. unsure.gif

tty
Go to the top of the page
 
+Quote Post
CosmicRocker
post Nov 28 2005, 03:50 AM
Post #15


Senior Member
****

Group: Members
Posts: 2222
Joined: 1-December 04
From: Marble Falls, Texas, USA
Member No.: 116



I'm not sure what this means, or if it even means anything. I won't suggest this is anything significant, because I can't interpret a lot of the stuff in the pancam tracking reports. But I went back to the last sol when MIs were taken, Sol 649. There was an "unexpected sequence," but it seems to be associated with a front hazcam image. However, that image was from command sequence P1110, which is always for front hazcam shots of the IDD in action.

Can anyone else interpret the tracking report better than I can? Any ideas?


--------------------
...Tom
Go to the top of the page
 
+Quote Post

16 Pages V   1 2 3 > » 
Reply to this topicStart new topic

 



RSS Lo-Fi Version Time is now: 1st September 2014 - 01:46 PM
RULES AND GUIDELINES
Please read the Forum Rules and Guidelines before posting.

IMAGE COPYRIGHT
Images posted on UnmannedSpaceflight.com may be copyrighted. Do not reproduce without permission. Read here for further information on space images and 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 a project of the Planetary Society and is funded by donations from visitors and members. Help keep this forum up and running by contributing here.