I clicked the next event to go to deorbit on STS-1 and this happened(http://i288.photobucket.com/albums/ll174/brian_beard1/SSM07_zpsauqbht14.png)
I was under the impression that malfunctions were not modeled into the program.
FC3 stack temp was off scale high, so I shut it down and landed safely.
I had no idea that failures were simulated in SSM2007. I wonder what could have caused FC3 to do that.
Wow, of all the times I have flown a SSMS mission I have never seen a failure, I thought the whole process was 'on rails' so to speak. Like I know you can shut the fuel cells down and get consequences but I didnt know things would actually fail on their own from normal use.
Quote from: Cras on July 29, 2015, 02:21:33 AM
Wow, of all the times I have flown a SSMS mission I have never seen a failure, I thought the whole process was 'on rails' so to speak. Like I know you can shut the fuel cells down and get consequences but I didnt know things would actually fail on their own from normal use.
I thought there were no random failures built into the program and I would suspect that this isn't the result of a "random" failure but more likely the result of a pilot (astronaut) error. Its been a while, but I recall being able to simulate some failures by incorrect procedures (ex. putting a switch in the wrong position). There are some procedures that will halt the program if performed incorrectly. However, I have found some incorrect procedures that will permit the program to continue and will result in a warning light/message.
i was following shutdown procedures on STS-27 (the LACROSSE mission) and I turned ON the coolant loops per the shutdown check list and got a Freon loop C/W