Dragon SpX-2 (CRS2) - Falcon 9 v1.0 - Canaveral SLC-40 - 01.03.2013 15:10 UTC

[Старый]

zeaman пишет:
А вот представьте, что не будь этого ЧП, мы бы уже зевая смотрели процесс ме-е-е-едленного причаливания...

Благодаря этому ЧП теперь вся страна (Россия) знает что есть такая компания СпейсИкс и такой корабль Драгон. Вчера все уши прожужжали что у него не включились двигатели и он завис. Кто сегодня смотрел ящик - о стыковке то хоть сообщили?

[Старый]

Росчирикался ВалериJ. И чего стыковки Союзов и Прогрессов не вызывают у него таких восторгов?

[Valerij]

С опозданием еще два поста из этого блога ради красивых фоток:
   

Dragon successfully berthed to ISS for three-week Stay
March 3, 2013
   

   
Following Dragon's early arrival at ISS on Sunday, the Spacecraft was successfully berthed to the Harmony Module of the International Space Station. Right after successfully capturing Dragon at 10:31 UTC with Canadarm2, the ISS crew members reconfigured the robotic arm to allow ROBO Controllers inside Mission Control to take control of the arm and start berthing operations.
   

   
 Once the ground had control, the robotic arm was configured to move Dragon up to the nadir Common Berthing Mechanism on Node 2. Teams had to wait for sunrise to begin a survey of Dragon's Common Berthing Mechanism using external ISS cameras.

 Afterwards, ROBO Controllers began the maneuver to the pre-install position about 3.5 Meters fr om the Harmony Hatch to allow the crew to make an additional visual inspection of the Common Berthing Mechanism. They also took high-resolution images that were downlinked to Earth to give flight controllers a chance to examine the area as well. There are three redundant rubber O-Rings on the CBM that need to be intact to form a pressure seal between Dragon and ISS.

 No damage or debris were found and teams were able to give a GO for berthing. The vehicle was moved to the ready to latch position, being slowly maneuvered by the Station's robotic arm to limit acceleration in order to keep forces on the arm within tolerance. "Nice to see Canadarm 2 moving Dragon into alignment for berthing. Looks great," said Canadian Space Agency Astronaut Chris Hadfield. Using the Node 2 Centerline Berthing Camera System, ROBO controllers precisely aligned Dragon with Harmony's nadir CBM that is facing the Earth. MCC-X commanded Dragon's solar arrays to their position for docked operations in order to continue berthing procedures.

 Once in the RTL position, teams verified that Dragon was in the proper position. Alignment was by the book and all four Ready-To-Latch-Indicators switched to Green indicating that Dragon was in the proper position for installation on the Harmony Module.

Chris Hadfield, Sunday's lead CBM Operator, and the rest of the USOS crew were standing by inside Harmony, starting to firmly attach Dragon to ISS on MCC Go. Four latches were closed to achieve first stage capture at 13:44 UTC. When First Stage Capture was complete, the Station's Robotic Arm was commanded to go limp to set the stage for Second Stage Capture. For second stage capture, four sets of four bolts were driven in a choreographed manner to secure Dragon in place.

Second Stage Capture came at 13:56 UTC and Dragon officially became a part of the Space Station for its three-week stay. Because Dragon made an early arrival and teams worked efficiently during berthing, the crew members can get a head start on hatch opening operations.

Initial operations were originally planned for Sunday with hatch opening on Monday, but because the crew is far ahead of the timeline, hatch opening late on Sunday is not out of the question.
   

   
Before the crew can go ahead and start vestibule pressurization, mission controllers will perform about one hour of final 'bolt loading' to adjust the torque on each of the 16 bolts to the nominal values.  The vestibule between the hatches of Harmony and Dragon will be pressurized and a series of leak checks will start to make sure the seal between ISS and the Spacecraft is tight. When leak checks are complete, Mission Control will give a go for Harmony Hatch Opening. This will set the stage for vestibule outfitting. This task is going to be performed by all three USOS crew members, Kevin Ford, Tom Marshburn and Chris Hadfield. They will remove Harmony's thermal and MMOD cover to access the vestibule area and start demating four Control Panel Assemblies that were used to drive bolts to berth Dragon. Later, Power and Data jumpers as well as IMV (Intermodule Ventilation) Ducts will be installed to hook Dragon up to ISS command and power.

Depending on the crew's schedule, they will either pause operations to go for Dragon hatch opening on Monday or press ahead to open hatches late in their day on Sunday.

Once both Hatches are open, the crew will perform air sampling as part of initial ingress operations wearing protective gear as they inspect the interior of the Dragon for any damage or Foreign Object Debris. During initial ingress, the Russian crew members of ISS will assist with air sampling operations.

When the first survey is complete, the crew will have to leave Dragon for 20 minutes to allow its air to mix with that of ISS to make it safe to enter the spacecraft without protective gear to complete outfitting and begin nominal docked operations.
   

Dragon Captured by Space Station Robotic Arm after "early late Arrival"
March 3, 2013
   

   
The SpaceX Dragon has arrived at the International Space Station, being captured by the Station's robotic arm on Sunday, March 3 - just 24 hours later than originally planned following Dragon's bumpy first day in orbit and the speedy recovery of the vehicle by SpaceX Mission Controllers. Canadarm2, controlled by Kevin Ford and Tom Marshburn, grappled Dragon at 10:31 UTC, marking the start of Dragon's three-week stay at ISS.

 After being approved for rendezvous on Saturday, Dragon was commanded to perform a umber of orbital maneuvers to achieve the proper position to begin its rendezvous sequence with the Space Station, starting out in a position behind and below the Space Station. A Height Adjust/Coelliptic Burn pair allowed Dragon to enter the ISS Communications Zone, a 28-Kilometer area around the Space Station where direct Relative GPS and UHF Communications were established between the two spacecraft. Using relative GPS data, Dragon constantly monitored its position relative to the Space Station during its initial approach.

 As Dragon coasted to a point 2.5 Kilometers below and behind ISS, the vehicle established UHF communications with the orbiting outpost. When reaching that point 2.5km below the Station, Dragon performed another Height Adjust Maneuver to increase its altitude and get closer to ISS. Two mid-course correction burns were executed to refine the vehicle's trajectory ahead of the subsequent Coelliptic Burn that placed Dragon in a position 1.4 Kilometers below and behind ISS.

 At this point, Dragon conducted its Approach Initiation Burn. This firing of the vehicle's Draco engines placed the spacecraft on a trajectory to intercept the Station's R-Bar. The R-Bar is an imaginary line fr om the Space Station to the center of the Earth, meaning that any vehicle that is on the R-Bar is directly below ISS.

 Before Dragon entered the Approach Ellipsoid that has a vertical radius of 1 Kilometer and a horizontal radius of 2 Kilometers, teams inside MCC-X (SpaceX Mission Control, Hawthorne) and MCC-H (NASA Mission Control, Houston) were polled for a GO/No GO to press ahead with the rendezvous.

At a distance of 1,000 meters, the USOS crew members aboard ISS, Kevin Ford, Tom Marshburn and Chris Hadfield, started to monitor the vehicle. They were located inside the Cupola with its Robotics Work Station (RWS) powered up and the Crew Command Panel (CCP) set up to interact with Dragon during RNDZ operations. The CCP and RWS inside Cupola as well as the backup RWS were configured on Friday and Saturday in anticipation of Dragon's arrival.
   

   
The crew members communicated with Dragon via the CUCU - the Commercial Orbital Transportation Services (COTS) Ultra High Frequency (UHF) Communication Unit (CUCU). This unit is used to send UHF-Commands to Dragon during proximity operations which then responds accordingly. The Commercial Communications Infrastructure aboard ISS was set up while the Space Shuttle was still flying - bringing components including the CUCU to the Station in 2009. Testing of the System was underway in 2010 and was used for Proximity Operations for the first time in 2012 for Dragon C2+.

It took Dragon about 50 minutes to reach the R-Bar during which the vehicle performed Mid-Course Corrections 3&4. R-Bar acquisition was as planned at a point 350 meters below ISS. Subsequently, Dragon performed a 180-degree Yaw maneuver to have its nose facing the opposite direction for eventual abort maneuvers during final approach. When the 5-minute maneuver was complete, Dragon advanced 100 more meters to the 250-meter hold point at which it arrived at 8:53 UTC. Once starting this planned hold, Mission Controllers at NASA's ISS Mission Control Center and SpaceX Flight Controllers in MCC-X, Hawthorne, California, were starting an assessment of all involved systems.

Dragon's proximity navigation instruments that are part of DragonEye inside the GNC Bay of the vehicle underwent a verification to make sure they were calibrated correctly and provided valid data. The instrument suite includes a LIDAR (Light Detection And Ranging) Imager and a thermal Instrument that are used to acquire range, range rate and relative position data of Dragon and ISS. LIDAR measures the time it takes for a single laser pulse fr om the sensor to reach a target and bounce back to provide three-dimensional images of its Field of View. Dragon has a redundant LIDAR system. The thermal imagers acquire Infrared Imagery of the space station. These images are used to provide additional navigation data concerning relative position between the spacecraft that is compared with LIDAR data to make sure Dragon has accurate navigation information.
   

   
All systems checked out well and Dragon was allowed to re-start its approach at 9:05 UTC. As Dragon gently approached ISS, sticking to the R-Bar, it entered the 200-meter Keep Out Sphere. The KOS  is a zone around the space station wh ere the highest safety requirements must be met by visiting vehicles in order to proceed inside. During Dragon's slow approach, the crew members inside the Cupola were ready to send Hold, Retreat or Abort Commands in the event of a problem with the Dragon.

The approach from 250 to 30 meters proceeded smoothly and took about 44 minutes. At the 30-meter mark, Dragon reached its next hold point. While Dragon was holding, teams at MCC-X and MCC-H completed a status check and controllers were polled before allowing Dragon to go to its Capture Point.

At 10:05 UTC, Dragon initiated its final approach and used its Draco thrusters that pulsed gently to reach a very small relative velocity. Dragon arrived at the Capture Point at 10:22 UTC and stopped its approach, using small Draco pulses to keep itself stable.

Mission Controllers performed one final verification of Dragon's navigation sensors, making sure that Dragon did not show any motion relative to ISS. Dragon was commanded to Free Drift, and so was ISS, to prevent any thruster firings during the capture sequence. Kevin Ford was flying Canadarm2 from the Cupola Robotics Work Station, being supported by Tom Marshburn and Chris Hadfield. Ford armed the Capture Command to track the Grapple Fixture of Dragon via the Latching End Effector (LEE) camera to make adjustments to precisely align the LEE with Dragon's grapple fixture. Once the GO for capture was given and the LEE was aligned, Ford drove the arm to place the LEE over the Grapple Fixture and initiate the Capture Sequence.
   

   
Capture was confirmed at 10:31 UTC and Candarm2 had a firm grip of the Dragon - arriving one day later than planned after a flawless rendezvous following the earlier issues of the flight. Capture occurred one hour ahead of the re-planned timeline and there were no unplanned holds during the entire rendezvous sequence as Dragon performed by the book. At the time of capture, ISS was flying 410 Kilometers above northern Ukraine. Dragon capture came 1 day 19 hours and 22 minutes into the SpX-2 mission.

Mission Control congratulated the crew on a successful capture. Expedition 34 Commander Kevin Ford replied: "Let me just say congratulations to the SpaceX and Dragon team in Houston and in California. - As they say, it's not wh ere you start but wh ere you finish that counts. You guys really finished this one on the mark. You're aboard, and we've got lots of science on there to bring aboard and get done, so congratulations to all of you."
   

   
With Dragon grappled, teams will be wasting no time, pressing into berthing operations once SpaceX has complete required commanding to reconfigure the Dragon for berthing. The berthing operation will be performed by ROBO Controllers inside Mission Control while the crew provides support when needed.

For the berthing, the grappled Dragon will be moved to a pre-install set-up position at a distance of about 3.5 Meters to the module so that engineering photos can be acquired through the Node 2 Window as part of a visual inspection of the spacecraft's Common Berthing Mechanism and associated O-Rings to make sure no damage or debris is in the area.
   

   
Also in that position, Dragon rotates its solar arrays for proper sun-pointing during its docked mission. Then, Dragon will be moved to the pre-berthing position at the nadir (Earth-facing) Common Berthing Mechanism on the Harmony Module. The Node-2 CBM underwent final reconfigurations on Saturday after Dragon had been approved for the Rendezvous.

The CBM petals were opened and inspections were performed late on Saturday using external ISS cameras to make sure the berthing interface was in good condition.

Once in its berthing position, four Ready to Latch Indicators will be used to verify that the Spacecraft is in the correct position and ready for berthing.

Procedures will begin to perform first stage capture of the Vehicle and allow the SSRMS to go limp. To structurally attach Dragon to ISS, four sets of four Bolts are driven in a choreographed manner to install the spacecraft. Afterwards, second stage capture will be performed and Dragon will be secured in place forming a hard-mate between Station and the Spacecraft marking the official start of docked operations.
   

http://www.spaceflight101.com/dragon-crs-2-spx-2-mission-updates.html
   
Сорри за простыню.

[Valerij]

Старый пишет:
Росчирикался ВалериJ. И чего стыковки Союзов и Прогрессов не вызывают у него таких восторгов?

Старый, еще как вызывают, не нужно обвинять меня в непатриотизме. Но наши не делают из происходящего шоу, зрелища, вы это знаете лучше меня. Просто - повезло, я дома и ноут под руками. Да и мое "чирикание" в этой теме больше было связано не со стыковкой Дракона, а с внутрифорумными событиями. Не люблю хамов.

[Salo]

Прол пишет:
Ждем такого же репортажа о стыковке "Союзов" и "Прогрессов" в 2014 г.  

Это об чём? Полагаете у Союзов и Прогрессов должны забарахлить ДУ? Их должны ловить манипулятором? Картинки над Россией быть не должно?

[Salo]

Valerij пишет:

Старый пишет:
Росчирикался ВалериJ. И чего стыковки Союзов и Прогрессов не вызывают у него таких восторгов?

Старый, еще как вызывают, не нужно обвинять меня в непатриотизме. Но наши не делают из происходящего шоу, зрелища, вы это знаете лучше меня. Просто - повезло, я дома и ноут под руками. Да и мое "чирикание" в этой теме больше было связано не со стыковкой Дракона, а с внутрифорумными событиями. Не люблю хамов.

Если стыковка будет длиться 3 часа Вы прийдёте в аналогичный восторг? Вас не устраивает быстрота процесса?

[Salo]

Valerij пишет:
   
Сорри за простыню.

Вставьте спойлер.

[Старый]

Valerij пишет:
 Старый, еще как вызывают, не нужно обвинять меня в непатриотизме. 

Почему непатриотизме? Стыковки Шаттлов, АТВ и Коноторей кажется тоже не вызывают у вас такого восхищения?

[Прол]

Salo пишет:

Прол пишет:
Ждем такого же репортажа о стыковке "Союзов" и "Прогрессов" в 2014 г.

Это об чём? Полагаете у Союзов и Прогрессов должны забарахлить ДУ? Их должны ловить манипулятором? Картинки над Россией быть не должно?

Боже упаси! Это о появлении на "Союзах" и "Прогрессах" аппаратуры для работы через "Лучи".

[Прол]

Старый пишет:

ilan пишет:
А видеосвязи с МКС над Украиной (и Россией) нету.

А чего, ТДРСС над ними не работает?

Над Индийским океаном 2 работающих ТДРСа. С чего взяли, что нет связи над Украиной и Россией?

[Salo]

Прол пишет:

Salo пишет:

Прол пишет:
Ждем такого же репортажа о стыковке "Союзов" и "Прогрессов" в 2014 г.

Это об чём? Полагаете у Союзов и Прогрессов должны забарахлить ДУ? Их должны ловить манипулятором? Картинки над Россией быть не должно?

Боже упаси! Это о появлении на "Союзах" и "Прогрессах" аппаратуры для работы через "Лучи".

И какое отношение это имеет к репортажу? НАСА ТВ Вас не устраивает?

[Прол]

Salo пишет:

Прол пишет:

Salo пишет:

Прол пишет:
Ждем такого же репортажа о стыковке "Союзов" и "Прогрессов" в 2014 г.

Это об чём? Полагаете у Союзов и Прогрессов должны забарахлить ДУ? Их должны ловить манипулятором? Картинки над Россией быть не должно?

Боже упаси! Это о появлении на "Союзах" и "Прогрессах" аппаратуры для работы через "Лучи".

И какое отношение это имеет к репортажу? НАСА ТВ Вас не устраивает?

НАСА ТВ устраивает. Не устраивает Роскосмос ТВ.

[Salo]

Прол пишет:
НАСА ТВ устраивает. Не устаивает Роскосмос ТВ.

Ну тут Луч не помошник.

[Сеян]

Прол пишет:

Старый пишет:

ilan пишет:
А видеосвязи с МКС над Украиной (и Россией) нету.

А чего, ТДРСС над ними не работает?

Над Индийским океаном 2 работающих ТДРСа. С чего взяли, что нет связи над Украиной и Россией?

Возможно "осколок" пропаганды. 
Ещё обратил внимание, когда станция проходит над Россией в большинстве случаев интернет-трансляцию видео Земли с МКС выключают, (хотя может это субъективно   ).

[Прол]

Salo пишет:

Прол пишет:
НАСА ТВ устраивает. Не устаивает Роскосмос ТВ.

Ну тут Луч не помошник.

Согласен. Наличие "Лучей" и абонентской аппаратуры условие необходимое, но недостаточное .

[ronatu]

Victor123 пишет:

ronatu пишет:
 Правильно сказать: РАДУЕТ

Вот и ronatu проснулся. Как спалось?

Эх, если б спалось....
Старость не радость.

[avmich]

Back-stabber пишет:

sychbird пишет:
Да поздравить стоит. И с успешным запуском и с классным двухдневным шоу и с умением решать траблы.    

Тумблером пощёлкать тыды-сюды? Да, мастаки...
Не нюхали ещё паццанятки пороху, ох не нюхали....  

Глядишь, и не понюхают . Не всем же на своих ошибках учиться, кому-то и на чужих.

Порох нюхать - это не всегда полезно .

[avmich]

LRV_75 пишет:

Valerij пишет:
Видите, сколько проблем решено, или глаза тем паяльником уже выжгли? Так что паяльник вам может пригодиться, раз сидеть на нем нравится.

Да, да, полезный запуск. Почаще заходите сюда и Вы поймете проблемы полета на Марс еще на НОО    А паяльник готов, не переживайте  

Роман, мне нравится Ваш прогресс . Так, глядишь, и привыкнете к частной космонавтике. Не сразу, не быстро, но...

[avmich]

Штуцер пишет:

Valerij пишет:

Back-stabber пишет:
Тумблером пощёлкать тыды-сюды? Да, мастаки...
Не нюхали ещё паццанятки пороху, ох не нюхали....

Зато такие, как вы и понюхать шансов не имеют.

Что такой злой, Valerij?  
Уж не сам ли Маск скрывается за этим ником?  

Ай-яй-яй, Штуцер, нехорошо получается. Обзывать учителей злыми - глупышом остаться. Не берите пример с двоечников.

[avmich]

Yutani пишет:

Salo пишет:
Его не было бы вообще.

Никуда бы он не делся!

Тут постоянно забывают, что Фалькон-1 Элон в основном на свои собственные деньги делал. Выложить несколько десятков миллионов из кармана без всяких контрактов с НАСА - потому что какие уж тут контракты, ничего нет - это может человек, работающий вдолгую. Без НАСА были бы и Фалькон-9, и Драгон - только не сразу и не такими бы, но НАСА должно было бы совсем уж республиканским (т.е. нерыночным выше атмосферы) быть, чтобы не сотрудничать со СпейсЭксом.