Reactive Rendezvous and Docking Sequencer
National Aeronautics and Space Administration
Agency Tracking Number:
Solicitation Topic Code:
Small Business Information
Blue Sun Enterprise, Inc.
1942 Broadway Street, Suite 314, Boulder, CO, 80302-5233
Socially and Economically Disadvantaged:
AbstractMars Sample Return poses some of the most challenging operational activities of any NASA deep space mission. Rendezvous of a vehicle with a sample canister in order to return the canister to Earth requires a variety of complex mathematical processing on a changing data set, coupled with the need to safely and effectively handle a large range of off-nominal conditions and spacecraft faults. Light speed delay isolates the spacecraft from real-time operator intervention, while inertial and situational uncertainties demand reactivity not required of typical spacecraft sequencing systems. These mission features call for a new class of sequence capability: Reactive Rendezvous and Docking Sequencer (RRDS). RRDS melds the rule-based reactivity needed for rendezvous and docking with sequence characteristics common to more traditional missions. Rules watch for conditions in order to react to the current situation, allowing a wide range of complex activities and safety-related responses to be concisely represented without complex procedural programming. Built atop JPL's VML 2.1, RRDS uses state machines to react to a variety potential conditions simultaneously. Conditions include out-of-envelope inertial behavior, hardware malfunctions, flight software errors, and ground wave-off, among others. Responsibility for commanding elements aboard the spacecraft is divided among state machines called managers, coordinated together by a flight director which the ground commands. Underlying flight software for navigation, thruster allocation, inertial checking, attitude estimation and control, contact detection, docking mechanisms, and the like receive direction from the managers. This mediated control causes the system to reactively operate in modes with proper ordering of activities. Reactive operations are represented explicitly by states and transitions defining the managers, and do not require use of explicitly timed activities.
* information listed above is at the time of submission.