Challenges of robotic space exploration
Explore the source record for details and available documents.
SEARCH · Search NASA
Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.
Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.
Explore the source record for details and available documents.
NASA’s “Volatiles Investigating Polar Exploration Rover” (VIPER) will be the first robotic mission to prospect for water ice near the south pole of the Moon in late 2023 on a 100-Earth-day mission. The information that the VIPER rover provides will help improve understanding of the composition, distribution, and accessibility of Lunar polar volatiles and will help determine how the Moon’s resources can support future human space exploration. VIPER, however, represents a radical departure from the way that NASA has traditionally developed planetary robotic missions. A key consequence of these differences is that estimating the cost of VIPER’s rover software is challenging and complex.For example, VIPER is being developed using management procedures typically applied to NASA research and technology projects, rather than space flight programs. In addition, key portions of the rover’s software are being designed as ground software to run on mission control computers (rather than on-board the rover as flight software as with prior planetary missions) taking advantage of continuous, interactive data communications between the Moon and Earth and higher performance computing available on the ground. Moreover, the rover’s software is being engineered using Agile software development practices and incorporates a significant amount of open-source, rather than following traditional (spiral, waterfall, etc.) development methods and in-house code. In this paper, we present an innovative process to estimate the life cycle cost of VIPER’s rover software. We first describe how we modeled the architecture and code counts for three software elements: Rover Flight Software (RFSW), Rover Ground Software (RGSW), and Rover Simulation Software (RSIM). We then discuss key challenges and unique aspects of our approach, such as the lack of Lunar rover analogies, the need to integrate and test large open source software, and the strategies developed to account for use of non-space flight management practices and the impact of the COVID-19 pandemic. We conclude with a summary of our results, including cumulative distribution, nearest neighbors and cluster analysis, as well as heuristics used to confirm the reasonableness of the cost estimate.
The future of space exploration lies in cooperative autonomous systems. Ensuring their high integrity remains a challenge. The Robust Software Engineering group at NASA Ames Research Center has been developing the Troupe project to explore the challenges with developing and assuring high integrity of cooperative autonomous robotic systems. In particular, Troupe aims to develop a swarm of autonomous rovers capable of mapping unknown terrain and assure their high integrity using the advanced V&V tools developed in the group. In this paper, we present the evolution of the design of Troupe. We focus on the lessons learned in developing and assuring the rover swarm using core Flight System (cFS). In particular, we discuss the benefits and challenges in applying model-based development to develop the rover swarm.
The future of space exploration lies in cooperative autonomous systems. Ensuring their high integrity remains a challenge. The Robust Software Engineering group at NASA Ames Research Center has been developing the Troupe project to explore the challenges with developing and assuring high integrity of cooperative autonomous robotic systems. In particular, Troupe aims to develop a swarm of autonomous rovers capable of mapping unknown terrain and assure their high integrity using the advanced V&V tools developed in the group. In this paper, we present the evolution of the design of Troupe. We focus on the lessons learned in developing and assuring the rover swarm using core Flight System (cFS). In particular, we discuss the benefits and challenges in applying model-based development to develop the rover swarm.
After five years on the International Space Station (ISS), the Astrobee Research Facility, has completed over 160 Test Sessions logging over 1200 hours of operations. Managed by the NASA ISS Program OZ office and supported by NASA Ames Research Center (ARC) in California, the Astrobee Team currently maintains two identical free-flying Astrobee robots and a Docking Station for research on the ISS. As a technology demonstration platform, the Astrobee Robots are available for Guest Scientists to use for a spectrum of research capabilities. Using ambient air on the ISS, propelled by battery-operated fans, Astrobee is designed to autonomously operate throughout most of the USOS (US Orbital Segment), with the objective of minimizing the need for astronaut support. Astrobee carries a suite of six cameras, a two degree-of-freedom (DOF) arm with a gripper that can grasp ISS handrails and other objects, and three payload bays that provide power and data for guest science hardware. Astrobee can autonomously execute hours-long flight plans or be tele-operated from the ground. While the Astrobee Team continues to improve mapping and autonomous flight capabilities, one of the main goals of Astrobee Robots is to provide research opportunities for Guest Scientists. The Astrobee Robot Software (ARS) makes extensive use of the open-source Robot Operating System (ROS). The ARS can be used interchangeably with an Astrobee Simulator or as Astrobee’s onboard software. ARS features include autonomous docking and perching, real-time teleoperations from the ground, plan based autonomous tasks, multi Astrobee communication, among other capabilities. Through simulation software and ground testing laboratories, the Astrobee Team is available to support Guest Scientists during development and testing and lead real-time ISS operations. The Astrobee Team and Guest Scientists have completed research including Astrobatics maneuvers, RFID and sound sensing capabilities, Gecko materials studies, student Robotics Programming Challenges, and Free Flyer formation flight investigations. Current science with the Astrobee Robots is investigating new docking capabilities through software only research as well as testing new docking hardware installed on the Astrobees. The Astrobee Team and other researchers at NASA Ames continue to explore robotics applications for future NASA missions such as Gateway and potential experiments involving human-robot interactions. Continued advanced mapping resolution capabilities, and high-resolution panoramic imagery also remains areas of research. Exciting in development research involves docking for rendezvous proximity operation (CLINGERS), multi resolution 3D scanning (MRS), space debris removal in microgravity (REACCH). This presentation will mainly focus on completed research over the past year and current science being performed on the Astrobees. This presentation will also focus on how a Guest Scientist/Researcher progresses from conception to running their science on the Astrobees on the ISS, as well as discuss the Astrobee Facility resources available for supporting ground testing and real-time ISS operations.
In the development of intelligent systems that interact with humans, there is often confusion between how the system functions with respect to the humans it interacts with and how it interfaces with those humans. The former is a much deeper challenge than the latter it requires a system-level understanding of evolving human roles as well as an understanding of what humans need to know (and when) in order to perform their tasks. This talk will focus on some of the challenges in getting this right as well as on the type of research and development that results in successful human-autonomy teaming. Brief Bio: Dr. Alonso Vera is Chief of the Human Systems Integration Division at NASA Ames Research Center. His expertise is in human-computer interaction, information systems, artificial intelligence, and computational human performance modeling. He has led the design, development and deployment of mission software systems across NASA robotic and human space flight missions, including Mars Exploration Rovers, Phoenix Mars Lander, ISS, Constellation, and Exploration Systems. Dr. Vera received a Bachelor of Science with First Class Honors from McGill University in 1985 and a Ph.D. from Cornell University in 1991. He went on to a Post-Doctoral Fellowship in the School of Computer Science at Carnegie Mellon University from 1990-93.
Unmanned Aerial Vehicles (UAV) are fundamental components in several aspects of research at NASA Langley, such as flight dynamics, mission-driven airframe design, airspace integration demonstrations, atmospheric science projects, and more. In particular, NASA Langley Research Center (Langley) is using UAVs to develop and demonstrate innovative capabilities that meet the autonomy and robotics challenges that are anticipated in science, space exploration, and aeronautics. These capabilities will enable new NASA missions such as asteroid rendezvous and retrieval (ARRM), Mars exploration, in-situ resource utilization (ISRU), pollution measurements in historically inaccessible areas, and the integration of UAVs into our everyday lives all missions of increasing complexity, distance, pace, and/or accessibility. Building on decades of NASA experience and success in the design, fabrication, and integration of robust and reliable automated systems for space and aeronautics, Langley Autonomy Incubator seeks to bridge the gap between automation and autonomy by enabling safe autonomous operations via onboard sensing and perception systems in both data-rich and data-deprived environments. The Autonomy Incubator is focused on the challenge of mobility and manipulation in dynamic and unstructured environments by integrating technologies such as computer vision, visual odometry, real-time mapping, path planning, object detection and avoidance, object classification, adaptive control, sensor fusion, machine learning, and natural human-machine teaming. These technologies are implemented in an architectural framework developed in-house for easy integration and interoperability of cutting-edge hardware and software.
The Lunar Gateway is a deep space orbiting outpost being developed by NASA in partnership with ESA and other domestic and international partners. It is a critical component of NASA’s Artemis program supporting long-term human exploration of the moon and is designed to be refueled, requiring the on-orbit transfer of propellants. The first two modules of Gateway to be launched will be the Power and Propulsion Element (PPE) and the Habitation and Logistics Outpost (HALO). The PPE contains the bipropellant chemical and electrical propulsion systems that will provide attitude control and orbit raising capability for Gateway. The reaction control system (RCS) utilizes monomethylhydrazine (MMH) and mixed oxides of nitrogen-3 (MON-3) as the fuel and oxidizer, respectively. Helium is used as a pressurant. The Advanced Electric Propulsion Systems (AEPS) and Busek hall thrusters that comprise the solar electric propulsion (SEP) system use xenon as the propellent. The ESPRIT Refueling Module, provided by ESA, will supply the propellant refueling function to Gateway’s propulsion systems. On-orbit refueling is a complex, technically challenging operation that is key to enabling sustainable crewed Lunar and Martian exploration. Numerous systems may be involved in the refueling operation. Also numerous systems are required to enable the successful ability for Gateway to refuel such as, SEP, RCS, Structure & Mechanisms (S&M), Guidance, Navigation and Control (GNC), Thermal, Software, Vehicle System Manager (VSM), Flight Ops, Extra Vehicular Robotics (EVR), Communication and Tracking (C&T), Avionics, and more. This paper will detail the design architecture, concept of operations, and challenges associated with the Gateway refueling system. The methodologies used in Gateway will be compared to those implemented in OSAM-1 and the best practices documented by AIAA and CONFERS (Consortium For Execution Of Rendezvous And Servicing Operations).
Space missions with small crews extending over several years with time-delay preventing normal conversations with people on earth will raise many challenges for training. Of special interest are possible three-year missions to Mars, requiring refresher instruction and learning new skills based on unexpected problems with machines and environmental conditions. For example, the crew will be required to monitor and repair more complex life support systems for air and water recycling than we even know how to build today. Highly educated astronauts, often with several doctorate degrees, require a very different mode of interaction than we have developed for school children or even typical college students. Explanation methods may need to differ-using analogies and techniques from different domains-depending on whether the astronaut is an astrophysicist, a pilot, or a geologist.Virtual reality (e.g., for Hubble repair missions) and "integrated" simulations (involving role-playing and emphasizing failure scenarios) are the most common advanced forms of instruction used in space flight today. The emphasis is on collaborative, embodied interaction with the same workstations and tools used in practice (e.g., a cockpit simulator). Otherwise, computerized instructional technology used by NASA is not model-based or tutorial in nature. This discussion will review some of the key instructional methods used at NASA over the past two decades and consider why ITS methods have not been exploited. Some of the problems and opportunities for training for Mars missions are examined, including how using robots in exploration activities will help but raise new training problems. These ideas will be illustrated with examples from the BrahmsVE system in which a browser- based virtual reality display with avatars allows interacting with a distributed multiagent system, in which agents can be people, robots, or software programs. Using BrahmsVE may provide a way for astronauts to interact with proxies of people who serve as instructional coaches on Mars.
During the course of transition from the Space Shuttle and International Space Station programs to the Orion and Journey to Mars exploration programs, a generic flexible multibody dynamics formulation and associated software implementation has evolved to meet an ever changing set of requirements at the NASA Johnson Space Center (JSC). Challenging problems related to large transitional topologies and robotic free-flyer vehicle capture/ release, contact dynamics, and exploration missions concept evaluation through simulation (e.g., asteroid surface operations) have driven this continued development. Coupled with this need is the requirement to oftentimes support human spaceflight operations in real-time. Moreover, it has been desirable to allow even more rapid prototyping of on-orbit manipulator and spacecraft systems, to support less complex infrastructure software for massively integrated simulations, to yield further computational efficiencies, and to take advantage of recent advances and availability of multi-core computing platforms. Since engineering analysis, procedures development, and crew familiarity/training for human spaceflight is fundamental to JSC's charter, there is also a strong desire to share and reuse models in both the non-realtime and real-time domains, with the goal of retaining as much multibody dynamics fidelity as possible. Three specific enhancements are reviewed here: (1) linked list organization to address large transitional topologies, (2) body level model order reduction, and (3) parallel formulation/implementation. This paper provides a detailed overview of these primary updates to JSC's flexible multibody dynamics algorithms as well as a comparison of numerical results to previous formulations and associated software.
Keeping track of sequences onboard a spacecraft is challenging. When reviewing Event Verification Records (EVRs) of sequence executions on the Mars Exploration Rover (MER), operators often found themselves wondering which version of a named sequence the EVR corresponded to. The lack of this information drastically impacts the operators diagnostic capabilities as well as their situational awareness with respect to the commands the spacecraft has executed, since the EVRs do not provide argument values or explanatory comments. Having this information immediately available can be instrumental in diagnosing critical events and can significantly enhance the overall safety of the spacecraft. This software provides auditing capability that can eliminate that uncertainty while diagnosing critical conditions. Furthermore, the Restful interface provides a simple way for sequencing tools to automatically retrieve binary compiled sequence SCMFs (Space Command Message Files) on demand. It also enables developers to change the underlying database, while maintaining the same interface to the existing applications. The logging capabilities are also beneficial to operators when they are trying to recall how they solved a similar problem many days ago: this software enables automatic recovery of SCMF and RML (Robot Markup Language) sequence files directly from the command EVRs, eliminating the need for people to find and validate the corresponding sequences. To address the lack of auditing capability for sequences onboard a spacecraft during earlier missions, extensive logging support was added on the Mars Science Laboratory (MSL) sequencing server. This server is responsible for generating all MSL binary SCMFs from RML input sequences. The sequencing server logs every SCMF it generates into a MySQL database, as well as the high-level RML file and dictionary name inputs used to create the SCMF. The SCMF is then indexed by a hash value that is automatically included in all command EVRs by the onboard flight software. Second, both the binary SCMF result and the RML input file can be retrieved simply by specifying the hash to a Restful web interface. This interface enables command line tools as well as large sophisticated programs to download the SCMF and RMLs on-demand from the database, enabling a vast array of tools to be built on top of it. One such command line tool can retrieve and display RML files, or annotate a list of EVRs by interleaving them with the original sequence commands. This software has been integrated with the MSL sequencing pipeline where it will serve sequences useful in diagnostics, debugging, and situational awareness throughout the mission.