![]() |
![]() |
![]() ![]()
|
![]() |
![]() Telemetry restored with Russian computers BY WILLIAM HARWOOD STORY WRITTEN FOR CBS NEWS "SPACE PLACE" & USED WITH PERMISSION Posted: June 14, 2007 Russian engineers cut off U.S. power and attempted to restart critical computers in the Zvezda command module of the international space station today using power from Russian systems. While the system showed a "heartbeat," flight controllers said, they were unable to coax the machines into rebooting during a pass over Russian ground stations. One orbit later, however, engineers were able to re-establish communications with a central computer in the command module and through it, another computer in the Zarya propulsion and storage module. And for the first time since the trouble began earlier this week, engineers began receiving a full stream of telemetry from the station to help troubleshoot the issue. The station's guidance and navigation computers must be restarted before the shuttle Atlantis undocks next week to provide the necessary control over critical systems. All three guidance computers, along with three command-and-control computers, crashed earlier this week amid work by the Atlantis astronauts to install a new U.S. solar power array. Russian engineers said Wednesday the new array, which generates some 22 kilowatts of usable electricity, might have caused a subtle change in the station's power grid that, in turn, affected the control computers. So far, that remains speculation. "In Moscow, they've been working overnight with their team in order to come up with a troubleshooting plan," NASA flight director Holly Ridings said early today. "They were able to re-establish communications with the central computer. Downstream of that, they have re-established communications with the computer in the FGB (Zarya). Certainly, a lot of good progress overnight by our Russian colleagues." Earlier today, space station commander Fyodor Yurckikhin and flight engieneer Oleg Kotov tried to help flight controllers diagnose the problem, looking for signs of any patterns in flashing error messages. The computers seemed locked in a reboot cycle. "Fyodor, I'm sorry, but so far here on the ground we haven't come together with a brainstorm," mission control, speaking through an interpreter, radioed the station. "Yes, I understand," Yurchikhin replied. "Hopefully we'll find a decision." "Well, that's a highly desirable outcome!" Yurchikhin joked. "Are you up by yourself, or is Oleg next to you?" mission control asked. "Of course he is up and running, of course he is worried," Yurchikhin said. "Guys, we are truly sorry." The Russian space agency does not have its own communications satellites. To troubleshoot the computer problem, Russian engineers have to wait until the station is within line-of-site of Russian ground stations to downlink telemetry and beam up commands. During a communications pass around 7 a.m., flight controllers reported some success, telling the cosmonauts "at last, for a change, after many hours without telemetry we finally have telemetry downstream." "Well, that's great news," Yurchikhin replied. "I feel much better." "Of course, I understand." A few moments later, around 7:23 a.m., a fire alarm sounded in the Zarya module as the Russians were attempting to switch the crew's Soyuz lifeboat from internal power to station power. The Soyuz was put on internal power late Wednesday as a precaution. A fire alarm sounded in the Zarya module Tuesday when the computer problems first began occurring. There were no signs of a fire then or this morning.
|
![]() |
![]() |
![]() |
![]() ![]() |
||||||||||||||||||||
MISSION INDEX |