It looks like you're using an Ad Blocker.
Please white-list or disable AboveTopSecret.com in your ad-blocking tool.
Some features of ATS will be disabled while you continue to use an ad-blocker.
The spacecraft experienced a computer reset on Tuesday apparently related to star-identifying software in the attitude control system. The reset put the spacecraft briefly into a precautionary safe mode. Engineers restored it to normal operational status for functions other than attitude control while planning resumption of star-guided attitude control.
Diagnostic work continues in response to the reset triggered by use of star-identifying software on the spacecraft on Nov. 29.
The spacecraft itself has redundant main computers. While the spacecraft is operating on the "A side" computer, engineers are beginning test runs of the star-identifying software on the redundant "B side" computer to check whether it is susceptible to the same reset behavior.
The inertial measurement unit is used as an alternative to the spacecraft's onboard celestial navigation system due to an earlier computer reset.
I agree with you, It's easier to fake it getting lost than it is spending all the time and effort to blur, pixelate and otherwise obfuscate photos.
Originally posted by Vandalour
make our tax founded merchandise disappear by faking a malfunction, and then use it to some exploration of something they would like to keep to themselves.
just like Phobos 2 space probe and The Mars Observer in 1994
Originally posted by abeverage
Although hitting mars with a probe has a bad track record, this is the 4th straight failure for Russia. The USA has not done too bad so I do often wonder if they plan some of these missions to go dark and become a black-ops mission.
Look at Phobos-grunt (There is a monolith on that moon)
Polar Lander (Some evidence of liquid water and possibly life).
Now the MSL purpose to find life...well let's be honest to analyze the life that is there.
Diagnostic work continues in response to the reset triggered by use of star-identifying software on the spacecraft on Nov. 29. In tests at JPL, that behavior has been reproduced a few times out of thousands of test runs on a duplicate of the spacecraft's computer, but no resets were triggered during similar testing on another duplicate.
Engineers restored it to normal operational status for functions other than attitude control while planning resumption of star-guided attitude control.
The Jan. 11 maneuver has been planned to use the spacecraft's inertial measurement unit to measure the spacecraft's orientation and acceleration during the maneuver. A calibration maneuver using the gyroscope-containing inertial measurement unit was completed successfully on Dec. 21. The inertial measurement unit is used as an alternative to the spacecraft's onboard celestial navigation system due to an earlier computer reset.
Originally posted by Ophiuchus 13
reply to post by Nicolas Flamel
Need some miniture R2D2 type bots to go with launched crafts to do manual fixes in space.
Pathfinder had Software Errors ➜ Symptoms Software did total system resets Symptoms noticed soon after Pathfinder started collecting meteorological data Some data lost each time ➜ Cause 3 Process threads, with bus access via mutual exclusion locks (mutexs): High priority: Information Bus Manager Low priority: Meteorological Data Gathering Task Medium priority: Communications Task Priority Inversion: Low priority task gets mutex to transfer data to the bus High priority task blocked until mutex is released Medium priority task pre-empts low priority task Eventually a watchdog timer notices Bus Manager hasn’t run for some time… ➜ Factors Very hard to diagnose: Hard to reproduce Need full tracing switched on to analyze what happened Was experienced a couple of times in pre-flight testing Never reproduced or explained Hence testers assumed it was a hardware glitch