- \n
- STS-135 LIVE Updates<\/li>\n
- L2 STS-135 Section<\/li>\n
- Click here to Join L2<\/li>\n<\/ul>\n
All orbiter systems are performing as required, with the Emergency, Environmental and Consumables Operation Manager (EECOM) reporting to the Mission Evaluation Room (MER): \u201cAll Life Support Systems are normal: Total GN2 Qty: 214.9 lbm. Total Waste Qty: 42.7 percent 73.7 lbm. Supply Water Total Qty: 460.9 lbm. CWC #11 Fill complete and filled with ~93.7 lbm of supply water.\u201d<\/p>\n
Atlantis\u2019 propulsion systems are in good shape, with 25 of the 38 primary thrusters having already been fired during the mission, ahead of a full set of thruster firings during the EOM-1 (End Of Mission) checkout.<\/p>\n
![\"\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2011\/07\/A416.jpg\" "\\"A4\\"")
One vernier thruster \u2013 namely L5L \u2013 is noted to have a low chamber pressure. However, even if this thruster eventually fails, it will hold no impact to the mission.<\/p>\n\u201cSince vernier activation on FD1 (Flight Day 1), thruster L5L\u2019s chamber pressure has been consistently lower than previous flights: Nominal peak Pc > 100 psia. For short pulses or elevated prop temps Pc as low as ~75 psia (this is) not unusual,\u201d noted a 43 page Orbiter Project Office (OPO) presentation (L2).<\/p>\n
Rocket launch schedules
<\/path>Spaceflight <\/path>Space Shuttle <\/path>\n (adsbygoogle = window.adsbygoogle || []).push({});<\/p>\n
\u201cSTS-135\/L5L peak Pc (chamber pressure) 103 psia; was as low as 76 psia on FD3 (Flight Day 3). For comparison, STS-125\/R5R peak Pc ~ 96 psia; was as low as 48 psia on FD2.\u201d<\/p>\n
The depth of evaluation is not unusual for orbiter engineering teams, but it\u2019s also a sign of a lack of any other issue of note to evaluate on Atlantis\u2019 propulsion systems.<\/p>\n
Based on previous flight history, engineers do not expect the thruster to fail, as much as such an incident would not prove to be challenging for Atlantis.<\/p>\n
![\"\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2011\/07\/A611.jpg\" "\\"A6\\"")
\u201cCurrent Status: Pc signature through docking did not change; average Pc is still ~100 psia for extended firings. Appears it may be performance problem. Based on past low Pc cases, L5L fail-off extremely unlikely,\u201d added the presentation, which noted the thruster will still remain in use.<\/p>\n\u201cCriticality\/consequences of loss of thruster. Loss of verns while docked (all verniers required for docked attitude control). Could affect reboost (not currently planned), maneuver to undock, undock attitude hold. Has no impact for Orbiter alone \u2013 vernier control still possible with remaining five jets. Manual flying would require Alt DAP (Digital Auto Pilot) (e.g., flyaround).<\/p>\n
\u201cRecommendations: Continue to use jet unless fails off. Remove thruster valves post-flight.\u201d<\/p>\n
The only notable issue with Atlantis has been with her GPCs, with GPC-3 failing before rendezvous with the ISS \u2013 prior to being recovered, and GPC-4 failing during the crew sleep period after Flight Day 7 had been completed. This computer has also now recovered.<\/p>\n
STS-135 Specific Articles: http:\/\/www.nasaspaceflight.com\/tag\/sts-135\/<\/p>\n
There are five identical GPCs aboard the orbiter. Each GPC is composed of two separate units, a central processor unit and an input\/output processor. All five GPCs are IBM AP-101 computers. Each CPU and IOP contains a memory area for storing software and data. These memory areas are collectively referred to as the GPC\u2019s main memory.<\/p>\n
![\"\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2011\/07\/A772.jpg\" "\\"A77\\"")
The hardware controls for the GPCs are located on panel O6. Each computer reads the position of its corresponding output, initial program load (IPL) and mode switches from discrete input lines that go directly to the GPC. Each GPC also has an output and mode talkback indicator on panel O6 that are driven from GPC output discretes.<\/p>\nEach GPC receives run, stby, or halt discrete inputs from its mode switch on panel O6, which determines whether that GPC can process software.<\/p>\n
It was a \u201cswitch tease\u201d on that panel when GPC-3 was physically turned on during the set expansion task for rendezvous, which caused the computer to temporarily join the common set prior to then failing out. GPC-3 was recovered following a dump and an IPL \u2013 effectively rebooting the computer, which has shown no signs of issues since.<\/p>\n
A problem was first noticed with GPC-4 when Atlantis annunciated the problem with via a master alarm, resulting in Commander Chris Ferguson being awoken, prior to heading over to the orbiter to evaluate the issue. The GPC in question was running system management software.<\/p>\n
![\"\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2011\/07\/A56111.jpg\" "\\"A5611\\"")
The STS-135 planning shift teams at the Johnson Space Center (JSC) were immediately on the case, with a set of instructions sent up to the crew to attempt a resolution of the problem.<\/p>\n\u201cTo attempt recovery of GPC 4, work GPC FRP-1. This procedure will dump GPC 1 as well as dump and IPL GPC 4. If GPC 4 is recovered, this will freeze-dry GPC 4,\u201d opened a highly technical set of instructions in one presentation (L2).<\/p>\n
Commander Ferguson ably followed the instructions from the ground, starting GPC-2 to take over the System Management (SM) task GPC-4 was running, allowing him to turn GPC-4 off. He then returned to his sleep period.<\/p>\n
In the morning, the crew performed what is known as \u201chardware-initiated, standalone memory\u201d (HISAM) tasks on GPC-1, prior to carrying out the same procedure on GPC-4. This was followed by an IPL task, prior to the \u2018freeze dried\u2019 procedure being carried out on the computer. During these tasks, a data dump from the troublesome GPC was sent to the ground for evaluation.<\/p>\n
![\"\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2011\/07\/A95.jpg\" "\\"A9\\"")
\u201cGPC 4 (SM) failed during crew sleep. GPC 2 was brought online and configured for SM. GPC 4 was powered OFF,\u201d explained a second presentation (L2). \u201cGPC 1 HISAM was performed following crew wakeup. GPC 4 HISAM was performed. Data Dump first look shows: CPU Store Protect Error, PC 1 Timer Interrupt.<\/p>\n\u201cGPC 4 was IPL\u2019ed and added to Redundant Set in G2. GPC 4 was freeze dried in G2 and put in STBY.\u201d<\/p>\n
No specific root cause has been revealed at this stage, although teams are confident that the incident was a \u201csingle event upset\u201d meaning GPC-4 is effectively still a healthy machine.<\/p>\n
As to what the \u201csingle event upset\u201d could have been, documentation shows analysis is still in work, although in the list of contributing factors is a \u201cCoronal Mass Ejection (CME)\u201d from the Sun.<\/p>\n
\u201cAnalysis of Memory Dump continues. MOD investigating any contributing factors: South Atlantic Anomaly (SAA), Coronal Mass Ejection (CME), Stored Program Command (SPC). history review for similar failure signatures. Discussions on any Confidence Runs prior to deorbit prep. MOD discussing Entry configurations.\u201d<\/p>\n
![\"\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2011\/07\/A329.jpg\" "\\"A3\\"")
Interestingly, docked photos from NASA \u2013 prior to GPC-4\u2019s issues \u2013 show Atlantis attached to the ISS as aurora borealis (Northern Lights) and\/or aurora australis (Southern Lights) lit up the backdrop of Earth \u2013 an effect of CMEs\/Solar activity.<\/p>\nIt is understood these photos were taken a matter of hours prior to GPC-4 failing.<\/p>\n
While orbiter\u2019s have five GPCs, one of the computers runs software designed by a different vendor than the other four \u2013 in order to protect against a commonality failure of all five computers. Technically, an orbiter can function and re-enter on just one GPC, although the preference is too have two GPCs running, with two more in standby mode.<\/p>\n
Currently, all five GPCs are deemed to be in good working condition, following the troubleshooting. Future updates on the root cause of GPC-4\u2019s incident will be provided when information is available.<\/p>\n
To read about Atlantis and her sisters \u2013 from birth, processing, every single mission, through to retirement, click here for the links:
\nhttp:\/\/forum.nasaspaceflight.com\/index.php?topic=25837.0<\/p>\n(Images: Via L2 content and NASA.gov. Further articles on STS-135 will be produced during and after her mission, driven by L2\u2032s STS-135 Special Section which is following the mission at MMT\/MER level, surrounded by a wealth of FRR\/PRCB\/MER\/MMT and SSP documentation\/pressentations, videos, images and more.<\/p>\n
(As with all recent missions, L2 is providing full exclusive level mission coverage, available no where else on the internet. To join L2, click here: http:\/\/www.nasaspaceflight.com\/l2\/)<\/p>\n","protected":false},"excerpt":{"rendered":"
Teams on the ground are working through possible root causes into the temporary failure of one of Atlantis\u2019 General Purpose Computers (GPC-4), with a Coronal Mass Ejection (CME) listed as one of three potential contributing factors. The computer now appears to be functioning normally, as Atlantis and her crew head into the final part of […]<\/p>\n","protected":false},"author":1,"featured_media":29592,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":"","_links_to":"","_links_to_target":""},"categories":[2],"tags":[3659],"class_list":["post-40376","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news","tag-sts-135"],"acf":[],"_links":{"self":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts\/40376"}],"collection":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/comments?post=40376"}],"version-history":[{"count":0,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts\/40376\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/media\/29592"}],"wp:attachment":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/media?parent=40376"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/categories?post=40376"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/tags?post=40376"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}