- \n
- STS-119 LIVE UPDATES<\/li>\n
- L2 STS-119 Section (Extensive)<\/li>\n
- Click here to Join L2<\/li>\n<\/ul>\n
Currently, engineers are loading cryogenic reactants into Discovery\u2019s fuel cell storage tanks.<\/p>\n
Only four issues have been reported since picking up the count, two of which related to human error at the pad. Only one of the problem reports required discussion \u2013 on this occasion with the flight crew.<\/p>\n
\u201cThe forward mission timer (MET) has an LED segment that is on and should be off \u2013 in work with troubleshooting of the problem. So far all troubleshooting possible has had no effect and the segment remains on,\u201d noted processing information on L2.<\/p>\n
Aerospace industry analysis
<\/path>Spaceflight news subscription <\/path>Space Technology <\/path>\n (adsbygoogle = window.adsbygoogle || []).push({});<\/p>\n
\u201cThe segment in question is in the 10\u2019s position of the hours display and during this mission would probably display a 0,1, or 2 which all use that segment. Discussions are now revolving around whether an R&R will be needed or whether the flight crew can live with the problem if they have a good aft display.\u201d<\/p>\n
The main topic at the MMT meeting related to STS-124\u2019s issue with Discovery\u2019s Left OMS Secondary TVC (Thrust Vector Control \u2013 or gimbal) controller\u2019s \u2018failure to null in both pitch and yaw\u2019. The controller in question was since removed and replaced during Discovery\u2019s flow inside her Orbiter Processing Facility (OPF).<\/p>\n
No mission impacts resulted from the issue during STS-126, with the OMS 2, NC1 and de-orbit burns performed with two engines without a problem, due to the health of the primary controllers. Interestingly, the issue appeared to resolve itself ahead of re-entry.<\/p>\n
While engineers were unable to recreate the issue inside the OPF, a concern has been noted with the potential for the controller\u2019s circuit card ability to \u201cmove\u201d, which may have caused the problem during STS-124. The MMT discussed the findings at length during their Monday meeting.<\/p>\n
\u201cOMS Engine Gimbal Controller Potential Circuit Card Movement: During STS-124, the left orbital maneuvering engine (OME) secondary pitch\/yaw gimbal indication failed. The secondary controller was assessed to be most probable cause and was removed and replaced,\u201d outlined the Orbiter Project\u2019s L-2 MMT presentation (all the L-2 MMT presentations are available on L2).<\/p>\n
![\"a28\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2009\/03\/a28.jpg\" "\\"a28\\"")
The system consists of two gimbal actuators (pitch and yaw), which provide thrust vector control for each of the orbiter\u2019s two OMS engines. Each actuator consists of redundant electro-mechanical drive units and electronic controllers.<\/p>\nA linear position transducer provides position feedback to the controller from the actuator.<\/p>\n
In order to provide redundancy, \u201ctwo controller units (of identical design) for each engine provide a back up closed loop system, with one controller for primary (active) pitch and yaw motors and one controller for secondary (standby) pitch and yaw motors.\u201d<\/p>\n
Each controller contains separate pitch and yaw channels which control power, logic and driver functions Internally, each controller contains six circuit boards, a mother board and two power inverters to dissipate heat.<\/p>\n
\u201cRecent failure analysis on the controller found that: The Viton rubber foam inside the cover (that provides hold-down force on the circuit cards) took a compression set. Three of the six circuit cards in the controller were unseated and raised approximately 1\/16\u201d to 1\/8\u201d.\u201d<\/p>\n
![\"a34\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2009\/03\/a34.jpg\" "\\"a34\\"")
The aforementioned Viton foam rubber provides a hold-down force when the cover is installed to help maintain card pin engagement in the sockets. No other lock down feature to hold cards in place less frictional forces from the pins\/sockets and card guides.<\/p>\n\u201cConcern: Potential for circuit card movement in the OMS controller resulting in open circuit failure due to contact separation,\u201d added the MMT presentation. \u201cLoss of OMS thrust vector control (TVC) for one engine requires two independent failures of both primary and secondary controllers.\u201d<\/p>\n
\u201cPost-flight troubleshooting on the vehicle did not reproduce the failure. Standby feedback signals and main bus drops were nominal. LH OMS secondary controller was assessed to be the most likely cause of the intermittent failure, and was removed for failure analysis (F\/A). F\/A testing at vendor reproduced erratic pitch and yaw position signals during y-axis vibration testing (x- and z-axis vibration was nominal).\u201d<\/p>\n
During the F\/A testing at the vendor, circuit assessments showed that if the A6 card (power source for the controller) was loose, it could result in failure signature similar to the one on STS-124. Thus the concern relates to the possibility the issue on STS-124 could repeat during STS-119.<\/p>\n
Although the controller may perform without a problem, the MMT ensured they had good flight rationale by carrying out a risk assessment \u2013 thanks to the redundancy in the system, known as \u201cmultiple-failure-tolerant.\u201d<\/p>\n
The MMT pre-empted the plan of action, based on one or more controllers failing during the mission \u2013 most likely during the vibrations of ascent \u2013 as part of the risk assessment.<\/p>\n
![\"a41\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2009\/03\/a41.jpg\" "\\"a41\\"")
\u201cRisk Assessment: Since failure occurred in ascent vibration, this is most likely timeframe for failure. Should failure occur after powered flight, OMS engine can be re-positioned through c.g (Center of Gravity) to prevent loss of OMS engine function,\u201d added the MMT presentation.<\/p>\n\u201cOMS system is multiple-failure-tolerant for OMS controller ascent failure. One controller failure (or two in different pods): Gimbal control on affected engine remains through redundant controller. Full deorbit capability still exists: Both OMEs and +X primary thrusters.<\/p>\n
\u201cFlight Rules direct that at first opportunity, engine re-positioned to fire through nominal EOM c.g. to protect for next controller failure. Increases propellant usage and potential for lost mission objectives.<\/p>\n
\u201cTwo controller failures in same pod: 2 other deorbit methods: (1) Other OME and (2) +X primary thrusters. Will require redlining RCS (Reaction Control System) propellant for deorbit if engine considered failed. If engine parked through deorbit c.g., some extra prop usage required (more prop\/less mission).<\/p>\n
\u201cThird controller failure (loss of one OME; other still has one good controller). Still 2 other deorbit methods: (1) Other OME and (2) +X primary thrusters. If engine parked through deorbit c.g., some extra prop usage required (more prop\/less mission). If OME not parked, could be Next PLS (Primary Landing Site) due to loss in deorbit redundancy.<\/p>\n
\u201cFourth controller failure: Still have deorbit capability with four +X thrusters. Would be Next PLS due to loss in deorbit redundancy.\u201d<\/p>\n
Thanks to the ability to avoid mission impacts \u2013 via a similar event to that observed during STS-124 \u2013 flight rationale was forthcoming for STS-119.<\/p>\n
![\"a5\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2009\/03\/a5.jpg\" "\\"a5\\"")
\u201cFlight Rationale for STS-119: Identified effects of controller failure due to card disengagement are 2R3. No output from controller. Controller drives affected gimbal to stop due to loss of feedback signal. Multiple controller failures in a single flight is highly unlikely based on extensive flight history,\u201d added the presentation.<\/p>\n\u201cOnly single failure to date. Other controllers of similar or older age and more flights have not failed.<\/p>\n
\u201cAscent acceleration will tend to keep cards seated in primary controllers due to their orientation. Differences in orientation of primary & secondary controllers reduce likelihood of common effect from launch vibration environment<\/p>\n
\u201cSingle controller failure has no significant mission effect. Unlike deorbit redundancy exists with PRCS thrusters.\u201d<\/p>\n
A plan was previously created during STS-124, in the event of concerns relating to the nozzle being parked in a protruding positon, which could cause damage during re-entry.<\/p>\n
Most important, none of the potential issues that could arise from another failure would be deemed as a safety risk to the vehicle or crew.<\/p>\n
L2 members<\/em><\/em>: Documentation \u2013 from which the above article has quoted snippets \u2013 is available in full in the related L2 sections, now over 4000 gbs in size.<\/em><\/em><\/p>\n","protected":false},"excerpt":{"rendered":"
Engineers are currently working no serious issues with the Discovery, as the Mission Management Team (MMT) sailed through L-2 ahead of STS-119\u2019s opening launch attempt on Wednesday. The main topic of conversation related to an issue with Discovery\u2019s OMS (Orbital Maneuvering System) Engine Gimbal Controller during her previous flight, STS-124. The orbiter aft closeout\/aft confidence […]<\/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":[9197,3479,9123],"class_list":["post-41165","post","type-post","status-publish","format-standard","hentry","category-news","tag-mmt","tag-oms","tag-sts-119"],"acf":[],"_links":{"self":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts\/41165"}],"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=41165"}],"version-history":[{"count":0,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts\/41165\/revisions"}],"wp:attachment":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/media?parent=41165"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/categories?post=41165"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/tags?post=41165"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}