- \n
- STS-134 LIVE UPDATES<\/li>\n
- L2 STS-134 Special Section<\/li>\n
- Click here to Join L2<\/li>\n<\/ul>\n
Endeavour\u2019s PRSD (Power Reactant Storage and Distributation) reactants have also been drained, while the OMBUU (Orbiter Mid Body Umbilical Unit) remains mated to the vehicle. It was during this operation that a new Interim Problem Report (IPR) was charged to STS-134\u2019s flow.<\/p>\n
\u201cNEW IPR 0056: PRSD OMBUU cavity indicated 6000ppm H2 after OMBUU mate and purge activated. Ground safety limits and S0007 limits (30,000ppm) were not violated,\u201d added the NTD. \u201cDuring off load when the helium purge was activated, detected 1200ppm leakage. Data will be gathered from the H2 detector trends and purge rates to help determine actual leak rate.\u201d<\/p>\n
![\"\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2011\/05\/a3.jpg\" "\\"a3\\"")
However, this \u2013 as are many of the IPRs charged during a flow \u2013 is a minor issue, especially when compared to IPR-55 \u2013 the official log name for the Auxiliary Power Unit (APU-1) heater issue, believed to have been caused by a failed hybrid driver in Endeavour\u2019s Aft LCA number 2 (ALCA-2), ultimately resulting in a breach of Launch Commit Criteria (LCC) rules and causing the scrub of the launch.<\/p>\n\u201cLaunch Countdown was scrubbed Friday due to IPR 134V-0055 detected after ET Cryo load. Operations for S0007 continued through the weekend to support a Monday launch attempt until troubleshooting revealed a bad power driver in ALCA2,\u201d outlined a Monday status summary (L2).<\/p>\n
\u201cThe troubleshooting data was presented to the management team on Sunday and a decision was made to scrub\/secure from S0007 in order to fix the anomaly. The management team is expected to meet determine the next launch attempt.\u201d<\/p>\n
Rocket launch schedules
<\/path>Space Technology <\/path>Aerospace & Defense <\/path>\n (adsbygoogle = window.adsbygoogle || []).push({});<\/p>\n
Although no official launch date has been set \u2013 and is unlikely to be set for some days as status on the LCA work is reviewed periodically \u2013 a managerial meeting on Monday afternoon opted to push the provisional launch date out to a NET May 10 target, from the previous May 8 NET target. This date also remains in the balance, given current Kennedy Space Center (KSC) schedules show a launch date target of May 11.<\/p>\n
![\"\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2011\/05\/A10.jpg\" "\\"A10\\"")
The plan is to meet again during the week, ahead of a Friday program-level meeting where managers will assess how the replacement work has progressed \u2013 given there are numerous variables in play, not least on the forensic investigation into the failed LCA, which has not yet been removed from Endeavour\u2019s aft (update pending). The meetings will decide on whether to continue to press for May 10, or slip the target to the 11th or further.<\/p>\nExpanding on the engineering evaluation into the APU heater issue, the NTD overview was careful to caution that the absolute root cause is not yet completely understood, which also plays into the schedule considerations, as a full understanding is likely to be required prior to the integration of the spare LCA unit into Endeavour.<\/p>\n
\u201cIPR 134V-0055 to APU: Initially a single heater string (B) on APU 1 was found to not be operating. The redundant heater leg worked nominally but both heater strings are required. Troubleshooting over the weekend revealed the thermostats were performing nominally and the problem was isolated to a bad power driver within LCA2. The cause for this failure is still not completely understood,\u201d the NTD added.<\/p>\n
STS-134 Specific Articles: http:\/\/www.nasaspaceflight.com\/tag\/sts-134\/<\/p>\n
\u201cThere is a possibility wiring external to the LCA could have contributed to the failure. Therefore, additional troubleshooting will be performed this morning to verify the integrity of the wiring external to the LCA. After troubleshooting is complete, LCA2 will be removed\/replaced. Systems retest is expected to take approximately 48hrs.\u201d<\/p>\n
The methodical approach the engineering and technician teams are taking is typical practice for the numerous elements of the Space Shuttle Program (SSP), something which has served them well during previous troubleshooting efforts, such as with the Flow Control Valves (FCVs), for example.<\/p>\n
So far, this approach has also managed to rule out several elements related to APU heaters as the cause of the failure, with a confirmed focus on the LCA and\/or its directly associated hardware.<\/p>\n
![\"\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2011\/05\/a9.jpg\" "\\"a9\\"")
\u201cTroubleshooting on Saturday 4\/30, the team verified the fuses located in the forward cockpit switch on Panel A12 were good. The team then confirmed the original IPR condition and verified the Thermostat cycled on but saw zero current draw on the heaters string,\u201d added another overview on Monday (L2).<\/p>\n\u201cAt this point, we verified no power output to the heaters, thus the failure is isolated to the ALCA2. The team then proceeded with additional troubleshooting and isolated the failure to the type III hybrid driver located within the Aft ALCA2.\u201d<\/p>\n
Finding a key suspect in the driver resulted in the Engineering Review Board (ERB) making the recommendation that the unit \u2013 or box as it\u2019s sometimes referred to \u2013 needed to be replaced. However, this procedure has been waiting on power output results, as engineers look for a reason as to why the driver has shorted out, such as finding a path into what caused the driver \u2013 which may be a victim, rather than a cause \u2013 to fail.<\/p>\n
![\"\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2011\/05\/A71.jpg\" "\\"A7\\"")
\u201cPrior to ALCA2 R&R, the team is working to validate their previous troubleshooting by verifying the power output at the ALCA2 and by using an external power source and apply 28v to the heaters to validate the heaters string,\u201d the overview continued.<\/p>\n\u201cAfter ALCA R&R, (Electrical Engineers) will hipot all the orbiter wiring and possibly the heaters and thermostats to look for possible shorts that could have cause the ALCA2 drivers to go bad.\u201d<\/p>\n
This element of the evaluations was the main focus of Monday, with breakout boxes installed, while the team completed continuity and isolation checks, along with completing the external power application to the heaters to allow currents to be measured through the heaters.<\/p>\n
Meetings are continuing to take place at an ERB level on the results of the power output checks of the LCA, as the absolute root cause is hunted down.<\/p>\n
Also discussed earlier on Monday were impacts relating to the upcoming LCA retests \u2013 the two day process which will start once the spare LCA is installed. The discussion focused on the impacts to the task of ordnance disconnect for the retesting of the AFT Sep Fire 2 command indicator circuit, which is the driver for ordnance disconnect.<\/p>\n
\u201cThree options were discussed: Option 1: go with full ordnance disconnect including SRB (Solid Rocket Booster) and Ground system. Option 2: partial Ordnance disconnects which excludes SRB and Ground systems. 3rd option: Waive SCAN retest the FWD Sep Fire 2 command indication.\u201d<\/p>\n
The decision taken at the ERB was to press forward with option two, to carry out partial ordnance disconnects, with a caveat that the AFT work is controlled and limited to the monoball and heaters troubleshooting areas.<\/p>\n
(All images via L2, apart from lead image via NASA TV. Extensive coverage is being provided on the news site and forum, driven by the L2 special sections with further articles to follow).<\/p>\n","protected":false},"excerpt":{"rendered":"
NASA managers have internally refined Endeavour\u2019s troubleshooting schedule on Monday, placing STS-134 on a NET (No Earlier Than) launch date of May 10. The schedule continues to be provisional, as engineers press on with the complex work of replacing the Aft \u201cLoad Control Assembly\u201d (ALCA-2) \u2013 the likely cause of the APU 1 heater failure […]<\/p>\n","protected":false},"author":1,"featured_media":0,"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":[9178,3366],"class_list":["post-40464","post","type-post","status-publish","format-standard","hentry","category-news","tag-apu","tag-sts-134"],"acf":[],"_links":{"self":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts\/40464"}],"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=40464"}],"version-history":[{"count":0,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts\/40464\/revisions"}],"wp:attachment":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/media?parent=40464"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/categories?post=40464"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/tags?post=40464"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}