Image to the left shows Cygnus in red achieving berthing to the ISS on Saturday.
Some complications to get to the success with different teams and locations around the globe. Worth the read - and to know that Russian engines are used.
(Images: via NASA, ULA, Orbital ATK and Jacques van Oene/Spacepatches.nl – also L2 Artist Nathan Koga – plus L2’s Cygnus Section – Containing presentations, videos, a vast set of unreleased hi-res images, interactive high-level updates and more, with additional images via Orbital ATK and NASA)
It's from a very detailed article written on March 25, 2016 by Chris Gebhardt, Chris Bergin and William Graham that appeared on NASA Spaceflight.com
https://www.nasaspaceflight.com/2016/03/cygnus-final-atlas-iss/
Cygnus OA-6 Arrival:
Immediately following launch, Cygnus – named S.S. Rick Husband – successfully entered its target orbit and deployed its lightweight solar arrays.
Since then, Orbital ATK mission controllers in Dulles, Virginia, spent the early days of Cygnus’ mission uploading and executing the first of a series of rendezvous phasing burns (called DV – Delta Velocity burns) to refine the S.S. Rick Husband’s trajectory toward the Station.
The first DV burn occurred on Wednesday, lasted approximately 10 minutes, and was designed to raise Cygnus from its initial near-circular 230km orbit to the 400km orbit of the ISS.
A similarly long DV burn followed, again to raise Cygnus to its proper orbital altitude.
This was then followed by a planned phasing burn to align Cygnus into the exact orbital corridor of the Station and then by a final set of DV burns on Friday to bring Cygnus to its “Go/No-Go for Joint-Ops” decision point, which it reached roughly 5hrs prior to capture at approximately 01:40 EDT Saturday.
Once Cygnus received the “go” from MCC-H (Mission Control Center – Houston) for Joint Ops, Cygnus slowly approached the Station to the Joint Targeting Reference Point (JTRP), which it arrived at just over 3hrs prior to capture – at approximately 03:30 EDT
From this point until capture and berthing, every step of the rendezvous required a strong communications link through the JEM (Japanese Experiment Module) PROX system between Cygnus, the ISS, and ground controllers.
This communication structure ensured the ability to manually abort – or at least retreat – Cygnus’ approach to the Station in the event of a problem with the spacecraft or the ISS.
Once at the JTRP, Cygnus stopped relative motion with the ISS and awaited a second Go/No-Go decision from MCC-H.
At this point, Cygnus was in the Joint Operations Phase (JOPS) of approach, as overviewed in documentation acquired by L2..
Approximately 3hrs before capture, and with MCC-H providing a “go” to proceed, Cygnus performed the first of four ADV thruster burns (ADV1) to begin moving closer to Station.
During these proximity ADV burns, Cygnus – until capture – made use of the TriDAR vision system designed by Canadian company Neptec with the support of NASA and the Canadian Space Agency.
TriDAR – tested during several Space Shuttle missions and used by SpaceX’s Dragon – will provide Cygnus controllers with real-time visual guidance for navigation, rendezvous and docking procedures.
After Cygnus’ completed her first two ADV burns, the ISS maneuvered to capture attitude – a 5 minute process that took place just over 2hrs prior to targeted capture time.
Then, with just under 2hrs to go until capture, MCC-H issued another Go/No-Go decision regarding two more ADV burns for Cygnus, which took the spacecraft to its 250m hold point below the ISS.
An hour later, MCC-H gave the “go” for Cygnus to depart the 250m hold point and enter the Keep Out Sphere (KOS) of the ISS.Cygnus then pulsed its thrusters and enter the KOS.
Up until this point, Orbital ATK controllers at their facility in Dulles had full control over Cygnus.Once Cygnus entered the KOS, NASA controllers at MCC-H joined the Orbital ATK team for the tricky rendezvous and berthing of Cygnus.Just under half an hour prior to capture, Cygnus arrived at the 30m Hold Point.
Atlas V Launch:
The veteran Atlas V rocket launched on its first attempt at the opening of the available window on Tuesday, lighting up the sky as she gracefully departed SLC-41 at Cape Canaveral.Vulcan:
Despite Atlas V’s impressive track record, ULA is preparing to bring a new rocket online by the end of the decade.
Due in part to geopolitical and US political considerations regarding Russian-built engines for the Atlas V fleet and also to increasing competition from SpaceX, ULA announced in September 2014 that it had entered into a partnership with Blue Origin to develop a new series of liquid oxygen and methane engines for a new first stage booster.
The Vulcan is designed to launch with dual Blue Origin BE-4 engines. However, Aerojet Rocketdyne is also developing the AR1 engine which could power the Vulcan Centaur.
ULA notes that their strategic partnership for American main engines – along with Orbital ATK for the solid rocket boosters and RUAG Space for domestically-produced composite structures – enables collaborative development of Vulcan to maximize the value of this new launch capability.
“Vulcan Centaur will revolutionize spaceflight and provide affordable, reliable access to space with an American main engine,” added Mark Peller, ULA’s program manager for major development.
No comments:
Post a Comment