Phobos-Grunt Failure Due to Computer Problems, Cosmic Rays

[/caption]

Roscosmos said today that a computer malfunction caused by cosmic rays was the reason for the failure of the Phobos-Grunt spacecraft. Additionally, ‘counterfeit’ chips in the computer may have played a role, said Federal Space Agency (Roscosmos) head Vladimir Popovkin. The original mission was to do a sample return from Mars’ largest moon, but the spacecraft crashed back to Earth on January 15 after the rocket failed to send it out of Earth orbit shortly after the launch in November. This determination comes from a study done by a commission led by Yuri Koptev, former head of the Russian Space Agency.

“There was a restart of the two sets of on-board computer system so [it] moved to the highest energy saving mode and the standby command,” said Popovkin, quoted by the Russian RIA Novosti news agency. “The most likely reason is the impact of heavy charged space particles.”

A Russian scientist was also quoted by RIA Novosti that the outcome of the accident investigation should not be cause for dismissals and resignations as much as a “lesson to developers of new interplanetary spacecraft,” said Alexander Zakharov, scientific secretary of Institute of Space Research, which developed instruments and the scientific program the station.

Some officials from Roscosmos had threatened the jobs of those involved with the mission.

As far as the counterfeit computer chips, Popovkin said the components were imported. “The cause probably is in this,” he said. Reportedly, NASA and the U.S. Defense Department has also encountered counterfeit products, according to an article in Itar-Tass.

Anatoly Zak at RussianSpaceWeb.com reported more in detail about possible shortcomings in the design of the probe’s flight control system, called the BKU, saying that “the most likely culprit in the failure of the probe’s propulsion unit to ignite soon after it had entered orbit on November 9 was a programming error in the flight control system.”

Zak said an industry source revealed that the commission studying the failure “concluded that the mission failure was the result of the design error and the lack in the ground testing of BKU,” adding that “its shortcomings had been well documented long before the ill-fated launch.” The BKU was the the main computer and the “brain” of the spacecraft.

Additionally, Zak reported that the most probable cause was a “simultaneous robooting of two operational processors in the main computer” and the computers “could crash as a result of errors in their software or as a result of some external reasons, such as electromagnetic incompatibility,” industry sources said.

The assertion that “foreign radars” had possibly caused the malfunction was apparently tested by the company that built the Phobos-Grunt probe, NPO Lavochkin, with no problems coming from simulated radar interference.

“With all external failure scenarios effectively debunked, the most probable cause of the failure was narrowed down to the lack of integrated testing,” Zak reported.

Roscosmos also indicated they may try again to send a sample return mission to Phobos.

As to the probability of any pieces of the original Phobos-Grunt spacecraft surviving the fiery re-entry through Earth’s atmosphere, most experts agree that most of the debris ended up in the Pacific Ocean. However, some debris may have fallen onto regions of Chile and possibly Argentina.

Luciano Anselmo from the Space Flight Dynamics Laboratory (ISTI/CNR) in Pisa, Italy left a comment on a previous Universe Today article saying that the Phobos-LIFE capsule, which was designed to survive re-entry “should have impacted the ground approximately 820 km eastward along the trajectory and 15 minutes later (w.r.t. the 80 km ‘entry’ point), with a velocity around 70 km/h.”

However, Anselmo added that “based on the orbit data available from the different sources involved, our estimation of the final uncertainty is plus/minus 12 minutes. Other observations, or the lack of them, both from the ground or from space, might be used to reduce such uncertainty, but nothing of reliable and unclassified has been provided so far, to my knowledge.”

Sources: RIA Novosti, RussianSpaceWeb.com, Itar-Tass

8 Replies to “Phobos-Grunt Failure Due to Computer Problems, Cosmic Rays”

    1. You can’t shield well from CR, at least not without adding a lot of weight, cost and development time.* Instead these systems use “best pick” of circuits and, as you may have noticed, reboot-able systems.

      Seems the project forgot to consider the unlikely event of an early CR failure before the coasting phase. If they then picked lousy circuits, which guaranteed an early CR failure, we have what they describe now.

      ———————-
      * Such designs are a must for near Jupiter missions though, pushing the boundary of what can be done.

  1. 70 km an hour for an hard, small, streamlined object like the Phobos Life Capsul??? Apparently, you can jump from space with only a couple fractures and a twisted ankle!

    1. Only if you’re made of soil! That speed is tolerable for a hardened container that carries an inanimate soil sample.

      1. Methinks you two missed the point. That speed is incredibly slow! I can nearly get my bicycle to that speed! If HUMAN terminal velocity is twice that of the soil return sample then something here is amiss.

    2. The terminal velocity for a human may be some ~ 100 – 150 km/h if you spread eagle.* (Some ~ 200 km/h if you tear drop, IIRC.)

      People have survived such t.v. falls when parachutes haven’t worked. (Typically WWII stories with no chutes, burned chutes or what have you.)

      _Some_ people. Don’t try it “at home”!

      ——————
      That is by the way why “wind fall” tunnels work to hover people, you can easily whip up more air speed than you need.

  2. It must be inexperience of the construction team if they look for cheap import circuits, because then there is no guarantee that they are the high-quality sort used for space (aka “radiation hardened”).

    Or, more likely, some bean counter forced a cheap solution or a project resource problem forced a fast solution.

    In any case that would explain the double reboot, from sensitive barely working “counterfeit” or counterfeit circuits.

Comments are closed.