STS-119 is one day away from the opening launch attempt, with only a few issues of note are being worked on by engineers out at Pad 39A. One ealier issue that has been resolved related to the Seat Detailed Test Objective (DTO), which will gather information on Thrust Oscillation (TO) for Ares I. Meanwhile, two members of Expedition 18 have completed EVA-21A.<\/p>\n
\nThe main item of troubleshooting relates to an auto cycle valve on the Mobile Launch Platform (MLP) which suffered an electrical issue. A back-up solution is in place, should troubleshooting fail to correct the problem.<\/p>\n
\u201cHigh point bleed valve A100739 did not respond during auto-cycling,\u201d noted processing information on L2. \u201cThe valve is located on MLP 1 side 1. Will begin troubleshooting following their final preps.\u201d<\/p>\n
Two other issues \u2013 one related to leaky valves that will require replacement \u2013 are both deemed minor and are in the process of being corrected.<\/p>\n
\u201cDuring S0071 bottle fill to 3500 psi. The A75004 transducer increased to 2520 psi,\u201d added processing information. \u201cNo increase was expected. MPS (Main Propulsion System) believes valves A74896 and A74983 are slightly leaking and the present plan is to replace both during PRSD (Power Reactant Storage and Distributation) offload.<\/p>\n
\u201cHydrogen LD36 sensor peaked at 5200 ppm S\/B no more than 4000 ppm. Detected during data review. Will recalibrate sensor on 1st shift.\u201d<\/p>\n
![\"a29\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2009\/03\/a29.jpg\" "\\"a29\\"")
The crew seat DTO is part of Constellation\u2019s efforts to complete a mitigation plan for the issue of Thrust Oscillation with Ares I. In order to gather data during ascent, accelerometers have been placed on the back of the MS1 (Mission Specialist 1), MS3, and MS5 seats.<\/p>\n
*Click here for articles on Ares I Thrust Oscillation*<\/p>\n
Company News (adsbygoogle = window.adsbygoogle || []).push({});<\/p>\n As part of the DTO, all middeck crewmembers will perform a cue card visual assessment to determine what can and cannot be read on the cue cards because of launch vibrations.<\/p>\n During early morning checks, one of the accelerometers failed to configure properly, due to an issue with its battery.<\/p>\n \u201cSeat DTO unit 1017 will not configure for flight programming. ISL believes battery R&R is required and is looking for spares,\u201d noted processing information. \u201cConstraint is to Ascent Switch List.\u201d<\/p>\n The unit received a new battery and was properly configured for Wednesday\u2019s flight during the first shift on Tuesday.<\/p>\n With Discovery past the half way mark in her S0007 launch countdown, the next major event will be the retraction of the Rotating Service Structure (RSS) at 1am local time.<\/p>\n On Monday, the Mission Management Team (MMT) cleared Discovery to continue the countdown through to a target 9:20pm launch on Wednesday, following flight rationale for Discovery\u2019s OMS (Orbital Maneuvering System) Engine Gimbal Controller, which suffered an anomaly during her previous STS-124 mission.<\/p>\n The clearance for flight was a minor issue compared to the months of work on ensuring flight rationale was forthcoming for the Flow Control Valve (FCV) issue, which gained another mention in the review of Monday\u2019s MMT meeting.<\/p>\n Click here for NASASpaceflight.com articles on the FCV issue since STS-126.<\/p>\n \u201cExcellent progress was made on the Main Propulsion System Flow Control Valve flight rationale, presented at the Agency Level I Delta FRR on Friday, 3\/6,\u201d noted the memo.<\/p>\n \u201cThe primary piece of the flight rationale is that the poppets installed on OV103 have no detectable cracks. In addition, analysis and testing were performed to characterize the likelihood and consequences of the hazards associated with a poppet failure and deemed sufficiently low risk to fly STS-119.<\/p>\n \u201cAt the L-2 MMT, the OMS engine gimbal controller failure analysis and flight rationale were reviewed and accepted. An issue with the ISS battery charger was also reviewed but is not a constraint to launch.<\/p>\n \u201cAll polled go to proceed with launch on 3\/11. Launch and landing weather forecasts look favorable. It\u2019s good to be back in a launch count! Stay focused and let\u2019s have an excellent mission!\u201d<\/p>\n The reference to the ISS battery charger is related to an EMU (EVA Mobility Unit) 16V Battery, which failed to hold its charge. The issue has been found to be related to an open circuit on one of four BCs (ISS Battery Chargers), namely BC3.<\/p>\n \u201cForward Work ICBs (2074, 2075) planned for charge operations on Saturday will be accomplished using -6 Mid-deck Charger,\u201d noted an associated presentation on L2. Fault tree is being matured to identify root cause of BC4 anomaly.<\/p>\n \u201cBest Case Outcome: Return of BC3 to nominal operational status. Troubleshooting. On-Orbit troubleshooting required to verify BCM parameter tables and open circuit voltage on ICB 2037 using BC3 and BC4.\u201d<\/p>\n No mission impact for either STS-119 or the ISS will be encountered, with five additional batteries all in good working order.<\/p>\n On the ISS, Expedition 18 Commander Mike Fincke and Flight Engineer Yury Lonchakov have completed their EVA, which included the installation of a European materials science experiment.<\/p>\n The EXPOSE-R experiment \u2013 which was located on the hull of the Zvezda service module \u2013 will allow for short and long-term exposure to space conditions and solar UV-radiation.<\/p>\n It was originally installed on Zvezda during the December spacewalk but had to be removed and brought back inside the station because of a cable problem.<\/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":" STS-119 is one day away from the opening launch attempt, with only a few issues of note are being worked on by engineers out at Pad 39A. One ealier issue that has been resolved related to the Seat Detailed Test Objective (DTO), which will gather information on Thrust Oscillation (TO) for Ares I. Meanwhile, two members […]<\/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":[233,9123],"class_list":["post-41164","post","type-post","status-publish","format-standard","hentry","category-news","tag-iss","tag-sts-119"],"acf":[],"_links":{"self":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts\/41164"}],"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=41164"}],"version-history":[{"count":0,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts\/41164\/revisions"}],"wp:attachment":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/media?parent=41164"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/categories?post=41164"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/tags?post=41164"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}See Also<\/h4>\n
\n
![\"a35\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2009\/03\/a35.jpg\" "\\"a35\\"")
A unit of four battery chargers is located on the ISS, which is used to charge items from the battery pack on the pistol grip tool, to the EMUs. Due to the aforementioned issue, two of those chargers, BC3 and BC4 have been taken off line for troubleshooting.<\/p>\n