IPB

Welcome Guest ( Log In | Register )

11 Pages V  « < 9 10 11  
Reply to this topicStart new topic
Matijevic Hill detailed survey, Sol 3153 - 3290
Vultur
post Apr 24 2013, 11:53 PM
Post #151


Member
***

Group: Members
Posts: 202
Joined: 9-September 08
Member No.: 4334



Ah, ok, so it's about commands being received reliably, not that pointing the comm equipment at the Sun would damage it. That makes much more sense, thanks.
Go to the top of the page
 
+Quote Post
Gerald
post Apr 25 2013, 12:14 PM
Post #152


Senior Member
****

Group: Members
Posts: 2346
Joined: 7-December 12
Member No.: 6780



QUOTE (TheAnt @ Apr 24 2013, 06:55 PM) *
Indeed, even though the Sun is relatively quiet in the band used for radio communication, a single outburst could change a command into something quite undesirable. And on top of it the operators would have a very hard time to know which command have been randomly changed.

Don't they add CRC32 or CRC64 checksums to the code blocks to be shure that only correctly transmitted commands will be executed, with a fallback strategy in case the command sequence is corrupted?
Go to the top of the page
 
+Quote Post
PaulH51
post Apr 25 2013, 01:04 PM
Post #153


Senior Member
****

Group: Members
Posts: 2425
Joined: 30-January 13
From: Penang, Malaysia.
Member No.: 6853



QUOTE (Gerald @ Apr 25 2013, 08:14 PM) *
Don't they add CRC32 or CRC64 checksums to the code blocks to be sure that only correctly transmitted commands will be executed

I am sure check sums are utilized for commands as well as all of the returned data strings, but this is a classic example of the ultra cautious 'belt and suspenders approach'. Frustrating for this community of observers, but when all factors are taken into consideration it was probably the only sensible option.
Go to the top of the page
 
+Quote Post
djellison
post Apr 25 2013, 02:03 PM
Post #154


Founder
****

Group: Chairman
Posts: 14431
Joined: 8-February 04
Member No.: 1



QUOTE (Gerald @ Apr 25 2013, 05:14 AM) *
Don't they add CRC32 or CRC64 checksums to the code blocks to be shure that only correctly transmitted commands will be executed, with a fallback strategy in case the command sequence is corrupted?


If you look at the Descanso website I linked to above, you will find all the details you could want regarding DSN protocols.

However- even error checking/correction does not solve the problem. You radiate a command load - the spacecraft identifies it as 'bad'. That command load could have been very important - it could have been something to prevent the spacecraft doing something to harm itself in someway . If the spacecraft doesn't accept it - you are quite probably in a worse situation. You radiate commands because you want the spacecraft to do something. Imagine the MSL side-B swop, or MER-B flash anomaly - but with the added complexity of unreliable communications.

There is a less obvious benefit of this strategy - conjunction offers up an opportunity for spacecraft operations teams to have a little down time. It's very very hard for a lot of flight-ops people to find time for vacations etc. Projects also can not afford enough personel to staff up enough to have redundancy for every job required on the mission. Conjunction offers a chance for people to catch up on other responsibilities, or take a well earned break.
Go to the top of the page
 
+Quote Post
Gerald
post Apr 25 2013, 05:38 PM
Post #155


Senior Member
****

Group: Members
Posts: 2346
Joined: 7-December 12
Member No.: 6780



It makes no sense to try to transmit commands during solar conjunction. I don't question the down time at all.

And thank you very much for the link to the paper! It seems to accept a Bit Error Rate (BER) of below 1e-6 for the transmission (section 5.5), meaning up to 8 errors in a Mega byte.
So in most cases important commands will be successful, if accepted by the decoder.
But during normal operations it might be better just to refuse (rare) corrupted command sequences, e.g. containing a sign error in an arm moving command, to prevent damage. I'm with PaulH51 at this point, they'll likely do it.
Might be important command sequences are sent twice (executed once, of course), in the case one copy is corrupted.
But that's not clear to me from the MRO paper.
Go to the top of the page
 
+Quote Post
Bill Harris
post May 28 2013, 04:17 AM
Post #156


Senior Member
****

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



The PS Update/Summary of some important LPSC papers on this leg of the Traverse:

http://www.planetary.org/explore/space-top...ter-so-far.html

--Bill



--------------------
Go to the top of the page
 
+Quote Post
serpens
post May 29 2013, 11:31 PM
Post #157


Senior Member
****

Group: Members
Posts: 1043
Joined: 17-February 09
Member No.: 4605



With respect to the newberries, Ray Arvidson and Ken Herkenhoff keep all options open and seem to weight lapilli and precipitated concretions equal favorites. But based on Brad Jolliff’s analysis Steve Squyres indicates that they are probably diagenetic concretions although possibly predating the Endeavour impact. I guess we will never know for sure.
Go to the top of the page
 
+Quote Post
scalbers
post Jun 10 2013, 04:52 PM
Post #158


Senior Member
****

Group: Members
Posts: 1624
Joined: 5-March 05
From: Boulder, CO
Member No.: 184



QUOTE (PaulM @ Apr 23 2013, 11:42 AM) *
If Ray's mapping is objective then I presume that a computer program could be written to extend the map of smectite clay outcrops over a much larger area.

Such a map would allow it to be decided which side of the rim Oppy should explore as it heads South. If I remember rightly, clays have been detected both on the West side and on the East side of the hills of the rim and so in the long run a decision must be made which set of clay deposits to examine.



I recall Ray talking about principal component analysis at a recent AGU conference. Unsure if it can/is being applied in this case.


--------------------
Steve [ my home page and planetary maps page ]
Go to the top of the page
 
+Quote Post

11 Pages V  « < 9 10 11
Reply to this topicStart new topic

 



RSS Lo-Fi Version Time is now: 18th April 2024 - 11:07 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 funded by the Planetary Society. Please consider supporting our work and many other projects by donating to the Society or becoming a member.