![\"\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2011\/07\/A324.jpg\" "\\"A3\\"")
This task, along with activation and ingress operations for the start of cargo transfer operations, was completed up to two hours ahead of schedule.<\/p>\nThe Mission Management Team (MMT) have approved the extension of the STS-135 mission by one day, thanks to Atlantis\u2019 healthy cryo margins. The extension will provide additional time for transfers to and from the Raffaello Multi-Purpose Logistics Module (MPLM) which was berthed on the International Space Station (ISS) on Monday, along with supporting additional ISS tasks from the Station\u2019s \u201cJob Jar\u201d.<\/p>\n
STS-135 Latest:<\/p>\n
As Atlantis and her crew press through the opening phase of the docked mission, Flight Day 4 was highlighted by the Canadarm2 robotic arm unberth of the Raffaello Multi-Purpose Logistics Module from Atlantis\u2019 payload bay, prior to being installed on the nadir port of Harmony.<\/p>\n
This task, along with activation and ingress operations for the start of cargo transfer operations, was completed up to two hours ahead of schedule.<\/p>\n
With load master Sandy Magnus coordinating operations, transfers began in earnest, with a carefully choreographed plan of action, involving both the location of the item to be removed from the MPLM, its relevant location on station, and the priority of the item to be moved.<\/p>\n
Atlantis\u2019 performance continues to be exemplary, with no major issues being evaluated by the Mission Evaluation Room (MER) \u2013 in fact, officially, the MER have a list containing a grand total of zero items, and a small list of very minor issues known as \u201cfunnies\u201d.<\/p>\n
\u201cMER Items: No problems. Funnies: APU (Auxiliary Power Unit) 2 drain line pressure increase. (FD1),\u201d noted some of the examples on the latest information from the Mission Management Team (MMT) on L2. Wing Leading Edge Sensor dropped out prematurely.\u201d<\/p>\n
The minor issue with the Wing Leading Edge Impact Detection System (WLEIDS) Sensor \u2013 used to monitor Micro Meteoroid\/Orbital Debris (MM\/OD) impacts on the wings during certain phases of on orbit operations \u2013 came during the NC-3 burn period of the flight, when the unit failed to complete a command, and provided a local time out error message.<\/p>\n
NASA educational resources (adsbygoogle = window.adsbygoogle || []).push({});<\/p>\n STS-135 Specific Articles: http:\/\/www.nasaspaceflight.com\/tag\/sts-135\/<\/p>\n \u201cOn FD3, the unit was then successfully programmed for Group 1 Start 1 monitoring to cover the elevated MM\/OD RCC (Reinforced Carbon Carbon) risk period during the dump, RPM (R-Bar Pitch Maneuver) and Docking period. A diagnostic command was sent to the unit after it had been programmed and it also successfully went through. During the 1st hourly On-Orbit Summary check, the unit experienced another local time-out error message.\u201d<\/p>\n The MER team added that if the sensor continues to be non-responsive, they will lose Group 1 Port Wing coverage for upper Port Chine\/RCC Panel 1 Interface, 2 and 3 RCC Panel Interface, 5 and 6 RCC Panel Interface and this will affect Impact Indication assessment for Port Wing RCC panels 2 and 3 with regards to the multi sensor ratio criteria.<\/p>\n Possible root causes to consider are: low battery level, battery component damage or broken\/cold solder joints, antenna damage, firmware bug, damaged 4MHz timing crystal, or even local RF interference issue between sensor and the sensor-side relay based on its location. It could even have been caused by the unit being \u201clocked up\u201d between modes and needs a hard reset to recover.<\/p>\n However, this is no concern to the teams on the ground, nor does it hold any mission impact, given this is what\u2019s known as a Critical 3 system, as opposed to a Critical 1 or 2 system.<\/p>\n \u201cIf all sensors were to fail there are no safety impacts,\u201d added the MER presentation. \u201cThis system is deemed crit 3 and poses no critical threat to the crew, mission, or vehicle. Sensor data is not used to make critical decisions based off of impacts.\u201d<\/p>\n The main item of interest for this flight so far related to the loss of GPC-3 (General Purpose Computer) on Flight Day 3.<\/p>\n GPC-3 returned to action via the IPL and dump tasks \u2013 an effective reload of software into the computer \u2013 during the early part of Flight Day 4, with MMT chair LeRoy Cain noting GPC 3 is now perfectly healthy, before confirming the problem was caused by a \u201cswitch tease issue\u201d.<\/p>\n This relates to when the computer was physically turned on during the set expansion task for rendezvous, with the switch failing to seat properly, causing the computer to temporarily join the common set prior to then failing out.\u201d<\/p>\n With these minor issues nothing more than topics for evaluation, the MMT\u2019s main decision on Monday was based on Atlantis\u2019 ability to remain at the Station for one extra day.<\/p>\n Given she already has well over a day of margin on her consumables \u2013 otherwise known as cryo reactants margins for her Fuel Cells \u2013 the decision was relatively easy, with Mr Cain expecting the vehicle to undock from the ISS with another half day\u2019s worth of cryos in reserve.<\/p>\n \u201cTowards the end of the docked mission we expect to have another half a day,\u201d noted Mr Cain, prior to noting the key calculation in ensuring the margin. \u201cWe know how much power we need for the systems and then we calculate how much reactants we need to produce this much power.\u201d<\/p>\n Even before Atlantis launched, teams were working on power saving options, given the ISS program had already inquired about the possibility of allowing Atlantis and her crew to stay on board for an extra day \u2013 due to the amount of help the four person crew could provide for the orbital outpost, during this final shuttle mission.<\/p>\n \u201cAdditional unstow unpack and place for station items, we also have some ISS systems item we can help on,\u201d Mr Cain noted as part of the extra tasks the STS-135 crew will be able to assist with. \u201cSet up and configure some cargo (we\u2019ve brought) up, and some general \u2018job jar\u2019 items on station. Have some 70 items in total, teams are off prioritising the list.<\/p>\n With a new EOM (End Of Mission) target, Mr Cain noted that he does not believe \u2013 at this stage \u2013 that any orbit adjustments will be required for the new return date of Atlantis.<\/p>\n \u201cNothing in the preliminary looks. Flight dynamics are evaluating,\u201d the MMT chair added in response to a question from NASASpaceflight.com\u2019s Philip Sloss. \u201cDon\u2019t think we need an orbit adjustment for any of the landing opportunities on the 21st.\u201d<\/p>\n Providing the opening opportunity is taken, Atlantis is scheduled to conduct her deorbit burn at 04:52 Eastern on the 21st, which will result in a landing on the Shuttle Landing Facility (SLF) in Florida at 5:56am, marking the end of the 30 year Space Shuttle Program.<\/p>\n To read about Atlantis and her sisters \u2013 from birth, processing, every single mission, through to retirement, click here for the links: (Images: Via L2 content (Lead Image and final image from L2\u2019s 400mm, 800mm, 1000mm STS-135 RPM image dump (600mb+ in size) and NASA.gov.)<\/p>\n 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":" The Mission Management Team (MMT) have approved the extension of the STS-135 mission by one day, thanks to Atlantis\u2019 healthy cryo margins. The extension will provide additional time for transfers to and from the Raffaello Multi-Purpose Logistics Module (MPLM) which was berthed on the International Space Station (ISS) on Monday, along with supporting additional ISS […]<\/p>\n","protected":false},"author":1,"featured_media":29573,"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-40392","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\/40392"}],"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=40392"}],"version-history":[{"count":0,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts\/40392\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/media\/29573"}],"wp:attachment":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/media?parent=40392"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/categories?post=40392"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/tags?post=40392"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}![\"\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2011\/07\/A651.jpg\" "\\"A65\\"")
\u201cDiagnostic file commands were then uplinked to sensor 1080 in an effort to help determine if the unit had programmed successfully; however, the diagnostic attempt failed 3 consecutive times and returned with a local time out error message each time,\u201d noted the MER report into the issue (L2).<\/p>\nSee Also<\/h4>\n
\n
![\"\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2011\/07\/A49.jpg\" "\\"A4\\"")
\u201cGPC 3 down due to switch tease. Rendezvous was conducted using 2 GPCs rather than the nominal 3 GPCs,\u201d added the status notes. \u201cGPC will be re-IPL (Initial Program Load) post docking (min 3 days).\u201d<\/p>\n![\"\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2011\/07\/linktoarticlestopleechingheh1.gif\" "\\"linktoarticlestopleechingheh1\\"")
This is impressive, not least because Atlantis \u2013 unlike her sisters \u2013 does not have the power-saving Station-to-Shuttle Power Transfer System (SSPTS). (Image left via L2, from STS-134)<\/p>\n![\"\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2011\/07\/A78.jpg\" "\\"A7\\"")
\u201cThe flight planners will generate a +1 day flight plan which will be added on FD 8. Some items will move ahead and behind as a function of which tasks get implemented on which days. Initial publication of +1 day timeline is probably already being reviewed by the flight team, it will get iterated on still though.\u201d<\/p>\n
\nhttp:\/\/forum.nasaspaceflight.com\/index.php?topic=25837.0<\/p>\n