-
ULA Completes CCDev Emergency Detection System Abort Demonstration
by
Chris Bergin
on 08 Feb, 2011 14:50
-
ULA Completes CCDev Emergency Detection System Abort Demonstration
Details to be Presented at Upcoming Space Transportation Conference
Denver, Colo. (Feb. 8, 2011) – United Launch Alliance (ULA) completed the most significant portion of the final milestone for its Commercial Crew Development Emergency Detection System (EDS) project last month, demonstrating the EDS test bed in ULA’s Denver Launch Support Center using the high fidelity Systems Integration Laboratory (SIL).
During testing last year, several abort simulation runs were successfully generated that illustrate the EDS abort detection capability for a wide range of anomalous launch vehicle conditions, both slow and quick to evolve into a catastrophic event. As soon as EDS detected the anomalous condition, the launch vehicle issued a command to the spacecraft to separate and initiate the abort escape sequence. As part of the demonstration, launch vehicle and spacecraft were animated using a high fidelity simulation tool to provide a visualization of the abort sequence once it had been initiated. Various combinations of the launch vehicle and winged and capsule type spacecraft were used during the simulated abort sequence.
Approximately 50 representatives from the spacecraft and NASA community attended including NASA crew members and MOD support.
Other accomplishments achieved to-date for the CCDev EDS Development and Demonstration activities include:
successfully completed milestones 1, 2 and 3 on schedule, encompassing the kick off, requirements review and a conceptual design review for the EDS architecture and abort demonstration task;
completed reconfiguration of the SIL test bed with a prototype EDS flight processor ahead of schedule and with significantly less modifications than anticipated;
added enhanced capabilities to the SIL hardware configuration abort demo, allowing crew intervention using the abort inhibit and manual abort options;
developed and demonstrated crew display technology during an actual launch (AV-019) with NASA flight and ground controller crew members;
completed the development and testing of the fault detection algorithms that were selected to demonstrate the selected abort scenario cases ahead of schedule;
initiated SC interface requirements development with several SC contractor on CCDev and others interested in using Atlas as well; and
performed a significant amount of fault coverage assessment for both Atlas and Delta configurations.
ULA program management, engineering, test and mission support functions are headquartered in Denver, Colo. Manufacturing, assembly, and integration operations are located at Decatur, Ala., Harlingen, Texas, and San Diego, Calif. Launch operations are located at Cape Canaveral Air Force Station, Fla., and Vandenberg Air Force Base, Calif.
-
#1
by
Namechange User
on 08 Feb, 2011 14:53
-
Cool. And in reality that should be about all that is needed. Of course we obviously need a spaceship.
-
#2
by
TexasRED
on 08 Feb, 2011 15:23
-
This is good, surprised not getting more attention.
-
#3
by
Namechange User
on 08 Feb, 2011 15:27
-
This is good, surprised not getting more attention.
True but when there is nobody to unfairly accuse and tear down just for the sake of it, no conclusions to jump to, etc this is what happens.
-
#4
by
Robotbeat
on 08 Feb, 2011 15:38
-
Cool. And in reality that should be about all that is needed. Of course we obviously need a spaceship.
Very cool!
-
#5
by
Ronsmytheiii
on 08 Feb, 2011 15:54
-
So what else is there to do for the CCDev work, and EDS to get to flight ready condition?
-
#6
by
Namechange User
on 08 Feb, 2011 15:56
-
So what else is there to do for the CCDev work, and EDS to get to flight ready condition?
No idea. One thing I can imagine is appropriate ICDs etc to make sure the spacecraft can actually "understand and talk" to the EDS system.
-
#7
by
robertross
on 08 Feb, 2011 16:40
-
What can I say, ULA knows their stuff.
Good job guys & gals.
-
#8
by
Alpha Control
on 08 Feb, 2011 16:49
-
Great to see tangible progress on this.
-
#9
by
EE Scott
on 08 Feb, 2011 17:05
-
I'm waiting and wondering about next steps now...I don't see how this can be tested in-flight unless ULA would get a contract for CLV services.
-
#10
by
ugordan
on 08 Feb, 2011 18:07
-
It can be tested in flight in passive mode, tapped onto the vehicle sensors and chugging along, but not being able to "abort" any of the unmanned flights it would be flown on first.
-
#11
by
Danny Dot
on 08 Feb, 2011 21:00
-
Any details on what parameters were used to declare an abort?
-
#12
by
ugordan
on 09 Feb, 2011 08:43
-
-
#13
by
Robotbeat
on 09 Feb, 2011 14:25
-
-
#14
by
TexasRED
on 09 Feb, 2011 14:38
-
-
#15
by
yg1968
on 09 Feb, 2011 16:24
-
-
#16
by
yg1968
on 16 Feb, 2011 16:08
-
-
#17
by
Ronsmytheiii
on 16 Feb, 2011 16:24
-
This screenshot and the SFN article confirm that ULA is baselining the Atlas 402 version, wonder how long/how much money that will take to get the Dual engine Centaur
-
#18
by
yg1968
on 16 Feb, 2011 16:25
-
-
#19
by
Robotbeat
on 16 Feb, 2011 16:35
-
-
#20
by
Lars_J
on 16 Feb, 2011 17:20
-
-
#21
by
Namechange User
on 16 Feb, 2011 17:27
-
-
#22
by
yg1968
on 16 Feb, 2011 17:48
-
If anyone else having issues with the video loaded from flash\browser here is a direct link so can just save as...
http://www.ulalaunch.com/site/Video/videos/CCDev_YIR2010.wmv
Cool stuff. Starting to get stoked to see what Orion really looks like sitting on a D4. And all the others too.
This video of a simulation of an astronaut in an Atlas V is also worth watching:
http://www.ulalaunch.com/site/Video/videos/NASTAR_Feb2011.wmv
Well I hope an astronaut would never be "in" an Atlas V, simulation or not.
OK, I have edited my original post accordingly. From the video, it looks to be the CST-100. But I imagine that the experience would be similar for other spacecrafts.
-
#23
by
Downix
on 16 Feb, 2011 18:22
-
This screenshot and the SFN article confirm that ULA is baselining the Atlas 402 version, wonder how long/how much money that will take to get the Dual engine Centaur
Since Feb 21, 2003. First launch of the existing Centaur tank in a dual-engine configuration was done on an Atlas III for Echostar VII. This did utilize the older Centaur control systems, however. But, the basic configuration has been flown already. There will need to be some work to adapt the new systems to the configuration, but as ULA insists that they developed them with the configuration in mind, I have no reason to doubt them.
(Discovered this last week)
-
#24
by
Jason1701
on 16 Feb, 2011 20:33
-
This screenshot and the SFN article confirm that ULA is baselining the Atlas 402 version, wonder how long/how much money that will take to get the Dual engine Centaur
Since Feb 21, 2003. First launch of the existing Centaur tank in a dual-engine configuration was done on an Atlas III for Echostar VII. This did utilize the older Centaur control systems, however. But, the basic configuration has been flown already. There will need to be some work to adapt the new systems to the configuration, but as ULA insists that they developed them with the configuration in mind, I have no reason to doubt them.
(Discovered this last week)
Any idea how much the double-engine configuration will cost per unit, or compared to the single-engine version?
-
#25
by
kevin-rf
on 17 Feb, 2011 00:07
-
If the vehicle does not have a payload fairing, how can it be called an Atlas 402 vs. an Atlas 502? Is it because the Centaur is exposed to the aero environment and has the load path of the 402 vs. the fully encapsulated and hung Centaur in the 502?
-
#26
by
Downix
on 17 Feb, 2011 00:35
-
If the vehicle does not have a payload fairing, how can it be called an Atlas 402 vs. an Atlas 502? Is it because the Centaur is exposed to the aero environment and has the load path of the 402 vs. the fully encapsulated and hung Centaur in the 502?
right
-
#27
by
Lars_J
on 17 Feb, 2011 00:36
-
Perhaps it will be called the Atlas 002?
