-
#20
by
Norm Hartnett
on 14 Jun, 2007 14:22
-
psloss - 14/6/2007 6:02 AM
I posted a couple of messages at the end of the FD6 thread relaying status, but not at home anymore, so I can't follow space-to-ground.
Bill Harwood also posted an update:
http://www.cbsnews.com/network/news/space/current.html
Great stuff psloss! Thanks, I managed to fall asleep.
It will be interesting to see what develops but I am fairly upbeat on the possible recovery.
-
#21
by
rosbif73
on 14 Jun, 2007 14:23
-
FD7 Execute packageGood Morning Atlantis!
Incredible day yesterday with EVA2 and the 2B retract. We will continue with the 2B retract
today as well as prepare for the revised EVA3, which includes the OMS pod blanket repair.
Keep up the great work!
-
#22
by
shuttlefan
on 14 Jun, 2007 14:24
-
bsegal - 14/6/2007 9:15 AM
Right - normally the reboot is automatic, but that didn't happen this time. This appears to be the first time that the ISS has (had) been without any lanes for a significant period ot time. Sounds like from the commentary this AM that they've recovered one lane overnight, are continuing to troubleshoot, and have asked shuttle to preserve some power to preserve the option of staying an additional day. Russian controllers last night were speculating the problem related to how the power from the new arrays was being routed to ISS - guess something akin to spoiled milk. Managers continued to express optimism that it would all get worked out, but they had to admit the option - however slim at this point - that if they couldn't get it figured out, abandoning the ISS was an option on the table.
How many of you out there would say this is the most serious problem the ISS has encountered thusfar?
-
#23
by
Chris Bergin
on 14 Jun, 2007 14:25
-
A bit of Travis wake-up music. Nice.
-
#24
by
whitewatcher
on 14 Jun, 2007 14:28
-
Norm Hartnett - 14/6/2007 4:22 PM
It will be interesting to see what develops but I am fairly upbeat on the possible recovery.
I would say it depends .... S/W or H/W faulty?
S/W: Upload a previous, well tested version or similar solution.
H/W: Workaround by S/W or R&R or manual repair.
If H/W is the source of trouble and R&R is required, they'll probably have to abandon the station.
If they are not able to trace down the source, they'll have to abandon, too.
Lack of redundancy .... CMGs are no standalone systems by design.
-
#25
by
YesRushGen
on 14 Jun, 2007 14:33
-
bsegal - 14/6/2007 10:15 AM
...Managers continued to express optimism that it would all get worked out, but they had to admit the option - however slim at this point - that if they couldn't get it figured out, abandoning the ISS was an option on the table.
Under this scenario, does "abondon" imply permanent abondonment? Or would this be temporary, to allow time to work the problem from the ground without endangering a crew?
-
#26
by
marsavian
on 14 Jun, 2007 14:33
-
Seems to me that after/if this is sorted, backup to the Russian computers are needed in the long-term as this looks a weak spot in the software systems. Dreadful to think the ISS is relying on 3 windows PCs for its continued existence !
-
#27
by
Norm Hartnett
on 14 Jun, 2007 14:37
-
hancider - 14/6/2007 6:49 AM
Hi guys thanks for the great coverage but can anyone tell me what the status is of the P6 retract as far as bays still deployed and also if they have the SARJ rolling yet on S4. I would really appreciate it. Thanks.
As Chris said 18-18 1/2 still out but SARJ could roll with that. Except that there is a problem with the DLAs. There is either a hardware or software cross connect that is causing commands to DLA2 to activate DLA1. At this time it is unknown if commands to DLA1 are affecting DLA2. All launch locks have been removed and all but one (?) of the launch restraints have been released. There is also some question on whether DLA2 is properly installed due to the above cross connect.
Anyone got corrections to that?
-
#28
by
rosbif73
on 14 Jun, 2007 14:38
-
marsavian - 14/6/2007 4:33 PM
Seems to me that after/if this is sorted, backup to the Russian computers are needed in the long-term as this looks a weak spot in the software systems. Dreadful to think the ISS is relying on 3 windows PCs for its continued existence !
Not Windows PCs but a fault-tolerant system provided by ESA (as mentioned earlier in this thread by JimO) and running software developed by RSC Energia. See for example
http://www.esa.int/esapub/bulletin/bullet93/GRAF.pdf
-
#29
by
whitewatcher
on 14 Jun, 2007 14:38
-
Under this scenario, does "abondon" imply permanent abondonment? Or would this be temporary, to allow time to work the problem from the ground without endangering a crew?
Depends on the demage. There are delicate systems installed on the station and the attitude control indirectly manages their exposure to sunlight (=radiation&heat).
Maybe 2-3 astronauts use the docked sojus as a lifeboat for a few days to give ground engineers more time.
-
#30
by
Chandonn
on 14 Jun, 2007 14:39
-
As previously mentioned, the best course of action is to see what's changed: ie S3/4. As I recall, there was an issue of an aborted Progess reboost after the addition of P3/4. Sounds like a similar issue to me: as the station gets larger, it gets harder to account for all the changes made in its mass, power, etc. Remember, this is the largest space station ever constructed. It's just a matter of getting all the bugs out...
-
#31
by
Norm Hartnett
on 14 Jun, 2007 14:41
-
whitewatcher - 14/6/2007 7:38 AM
Under this scenario, does "abondon" imply permanent abondonment? Or would this be temporary, to allow time to work the problem from the ground without endangering a crew?
Depends on the demage. There are delicate systems installed on the station and the attitude control indirectly manages their exposure to sunlight (=radiation&heat).
Maybe 2-3 astronauts use the docked sojus as a lifeboat for a few days to give ground engineers more time.
They have two Progress and one Soyus docked, could these provide some short term attitude control?
-
#32
by
Avron
on 14 Jun, 2007 14:42
-
With all the powerdowns in work... will KU be dropped as well?
-
#33
by
DaveS
on 14 Jun, 2007 14:43
-
Chandonn - 14/6/2007 4:39 PM
As previously mentioned, the best course of action is to see what's changed: ie S3/4. As I recall, there was an issue of an aborted Progess reboost after the addition of P3/4.
That was just due to miscalculations on the Russians part as they failed to realize that the cg of the station had changed. Once that was fixed, the brun went nominal.
-
#34
by
Norm Hartnett
on 14 Jun, 2007 14:45
-
DaveS - 14/6/2007 7:43 AM
the brun went nominal.
LOL with all this computer chat I'm thinking brun... brun? are they using assembly language? Oh
burn LOL
-
#35
by
Chris Bergin
on 14 Jun, 2007 14:46
-
Extra dock day being approved right now.
-
#36
by
Chandonn
on 14 Jun, 2007 14:46
-
DaveS - 14/6/2007 10:43 AM
Chandonn - 14/6/2007 4:39 PM
As previously mentioned, the best course of action is to see what's changed: ie S3/4. As I recall, there was an issue of an aborted Progess reboost after the addition of P3/4.
That was just due to miscalculations on the Russians part as they failed to realize that the cg of the station had changed. Once that was fixed, the brun went nominal.
exactly. I'm just commenting that it's a similar type of problem, not the same problem. ie, most likely, something's been missed on the S3/4 addition, or not been accounted for fully.
-
#37
by
Chris Bergin
on 14 Jun, 2007 14:48
-
"currently running on less than 12 kW to try to squeeze an extra docked day while ISS reviews attitude control problems."
-
#38
by
Lee Jay
on 14 Jun, 2007 14:54
-
This is a *contingency* docked day in case it takes an extra day to get the Russian system up and running again, right?
-
#39
by
bsegal
on 14 Jun, 2007 15:00
-
For those who are interested, ULA's webcast for today's NRO launch just went active. T-8 minutes. Some range issues being worked, but expect them to clear.
