NASA SBIR 2009 Solicitation
FORM B - PROPOSAL SUMMARY
|PHASE 1 CONTRACT NUMBER:
||Rendezvous and Docking Technologies for Orbiting Sample Capture
||Reactive Rendezvous and Docking Sequencer
SMALL BUSINESS CONCERN (Firm Name, Mail Address, City/State/Zip, Phone)
Blue Sun Enterprise, Inc.
1942 Broadway Street, Suite 314
Boulder, CO 80302 - 5233
PRINCIPAL INVESTIGATOR/PROJECT MANAGER (Name, E-mail, Mail Address, City/State/Zip, Phone)
1942 Broadway Street, Suite 314
Boulder, CO 80302 - 5233
Estimated Technology Readiness Level (TRL) at beginning and end of contract:
TECHNICAL ABSTRACT (Limit 2000 characters, approximately 200 words)
Mars 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. Responsibility for commanding elements aboard the spacecraft is divided among sequenced 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.
Phase II of this SBIR will produce a Class B version of the underlaying VML 2.2 flight software capable of executing the RRDS state machines. It will also produce Class C versions of the associated VML compiler and Offline VM execution system for deployment onto flight projects.
POTENTIAL NASA COMMERCIAL APPLICATIONS (Limit 1500 characters, approximately 150 words)
RRDS may be applied to a variety of commercial missions reactively operating spacecraft in complex scenarios, like deep space missions retrieving samples from a variety of planetary bodies, comets, asteroids, or moons. RRDS could also be used on uncrewed cargo flights to a space station or assembly site.
Executable state machines provided by VML 2.2 allow many kinds of autonomy to be created, outside of the RRDS realm. These include:
reactive fault protection which is cheaper to develop and more transparent in operation than a flight software implementation
autonomy for self-directed orbital missions requiring limited operational interaction with controllers, reducing personnel costs
autonomy for self-directed comet / asteroid sampling missions requiring limited operational interaction with controllers, reducing DSN time and personnel costs
on-board replanning to compensate for degraded and failed systems in a high radiation, remote environment like Europa orbit
autonomy for landed vehicles and rovers, reducing the risk to the mission and simplifying mission operations
target-of-opportunity science collection in earth-orbiting or deep space environments, allowing detected events to result in further detailed observations (e.g. detected volcanic activity leading to
taking a raster of images)
expert systems for guiding remote experiments in real-time based on observed environmental
POTENTIAL NON-NASA COMMERCIAL APPLICATIONS (Limit 1500 characters, approximately 150 words)
VML 2.2 allows autonomy to be created for commercial low earth orbiting observation missions that would permit targets of opportunity for observations to be identified and acted upon. Autonomy in this regime could also simplify spacecraft operations by allowing onboard systems to make more decisions, and
reduce the need for off-shift operations personnel.
Many of the NASA commercial applications listed above also have potential terrestrial applications. VML 2.2 autonomy capabilities could be applied to autonomous vehicle control, manufacturing process controllers, airborne systems, and remote science stations with limited contact time. The state-machine approach has an advantage over autocoded systems in that the embedded software is not unique for every flight software load, reducing risk and enhancing system insight.
TECHNOLOGY TAXONOMY MAPPING (NASA's technology taxonomy has been developed by the SBIR-STTR program to disseminate awareness of proposed and awarded R/R&D in the agency. It is a listing of over 100 technologies, sorted into broad categories, of interest to NASA.)
Attitude Determination and Control
Autonomous Control and Monitoring
Autonomous Reasoning/Artificial Intelligence
Guidance, Navigation, and Control
On-Board Computing and Data Management
Operations Concepts and Requirements
Software Development Environments
Form Generated on 08-06-10 17:29