SNN

Planning autonomous surface missions on ocean worlds

Toward autonomous surface missions on ocean worlds
Artist’s concept image of a spacecraft lander with a robot arm on the surface of Europa. Credits: NASA/JPL – Caltech

Through advanced autonomy testbed programs, NASA is setting the groundwork for one of its top priorities—the search for signs of life and potentially habitable bodies in our solar system and beyond. The prime destinations for such exploration are bodies containing liquid water, such as Jupiter’s moon Europa and Saturn’s moon Enceladus.

Initial missions to the surfaces of these “ocean worlds” will be robotic and require a high degree of onboard autonomy due to long Earth-communication lags and blackouts, harsh surface environments, and limited battery life.

Technologies that can enable spacecraft autonomy generally fall under the umbrella of Artificial Intelligence (AI) and have been evolving rapidly in recent years. Many such technologies, including machine learning, causal reasoning, and generative AI, are being advanced at non-NASA institutions.

NASA started a program in 2018 to take advantage of these advancements to enable future icy world missions. It sponsored the development of the physical Ocean Worlds Lander Autonomy Testbed (OWLAT) at NASA’s Jet Propulsion Laboratory in Southern California and the virtual Ocean Worlds Autonomy Testbed for Exploration, Research, and Simulation (OceanWATERS) at NASA’s Ames Research Center in Silicon Valley, California.

NASA solicited applications for its Autonomous Robotics Research for Ocean Worlds (ARROW) program in 2020, and for the Concepts for Ocean worlds Life Detection Technology (COLDTech) program in 2021.

Six research teams, based at universities and companies throughout the United States, were chosen to develop and demonstrate autonomy solutions on OWLAT and OceanWATERS. These two- to three-year projects are now complete and have addressed a wide variety of autonomy challenges faced by potential ocean world surface missions.

OWLAT

OWLAT is designed to simulate a spacecraft lander with a robotic arm for science operations on an ocean world body. The overall OWLAT architecture including hardware and software components is shown in Figure 1. Each of the OWLAT components is detailed below.

Figure 1. The software and hardware components of the Ocean Worlds Lander Autonomy Testbed and the relationships between them. Credit: NASA/JPL – Caltech

The hardware version of OWLAT (shown in Figure 2) is designed to physically simulate motions of a lander as operations are performed in a low-gravity environment using a six degrees-of-freedom (DOF) Stewart platform. A seven DOF robot arm is mounted on the lander to perform sampling and other science operations that interact with the environment. A camera mounted on a pan-and-tilt unit is used for perception.

The testbed also has a suite of onboard force/torque sensors to measure motion and reaction forces as the lander interacts with the environment. Control algorithms implemented on the testbed enable it to exhibit dynamics behavior as if it were a lightweight arm on a lander operating in different gravitational environments.

Figure 2. The Ocean Worlds Lander Autonomy Testbed. A scoop is mounted to the end of the testbed robot arm. Credit: NASA/JPL – Caltech

The team also developed a set of tools and instruments (shown in Figure 3) to enable the performance of science operations using the testbed. These various tools can be mounted to the end of the robot arm via a quick-connect-disconnect mechanism. The testbed workspace where sampling and other science operations are conducted incorporates an environment designed to represent the scene and surface simulant material potentially found on ocean worlds.

Figure 3. Tools and instruments designed to be used with the testbed. Credit: NASA/JPL – Caltech

The software-only version of OWLAT models, visualizes, and provides telemetry from a high-fidelity dynamics simulator based on the Dynamics And Real-Time Simulation (DARTS) physics engine developed at JPL. It replicates the behavior of the physical testbed in response to commands and provides telemetry to the autonomy software. A visualization from the simulator is shown in Figure 4.







https://scx2.b-cdn.net/gfx/video/2024/toward-autonomous-surf.mp4
Figure 4. The dynamics simulator visualization showing the deployment and performance of the scooping operation.  Credit: NASA/JPL – Caltech

Discover the latest in science, tech, and space with over 100,000 subscribers who rely on Phys.org for daily insights.
Sign up for our free newsletter and get updates on breakthroughs,
innovations, and research that matter—daily or weekly.


The autonomy software module shown at the top in Figure 1 interacts with the testbed through a Robot Operating System (ROS)-based interface to issue commands and receive telemetry. This interface is defined to be identical to the OceanWATERS interface. Commands received from the autonomy module are processed through the dispatcher/scheduler/controller module (blue box in Figure 1) and used to command either the physical hardware version of the testbed or the dynamics simulation (software version) of the testbed.

Sensor information from the operation of either the software-only or physical testbed is reported back to the autonomy module using a defined telemetry interface. A safety and performance monitoring and evaluation software module (red box in Figure 1) ensures that the testbed is kept within its operating bounds. Any commands causing out of bounds behavior and anomalies are reported as faults to the autonomy software module.

OceanWATERS

At the time of the OceanWATERS project’s inception, Jupiter’s moon Europa was planetary science’s first choice in searching for life. Based on ROS, OceanWATERS is a software tool that provides a visual and physical simulation of a robotic lander on the surface of Europa (see Figure 5).

Figure 5. Screenshot of OceanWATERS. Credit: NASA/JPL – Caltech

OceanWATERS realistically simulates Europa’s celestial sphere and sunlight, both direct and indirect. Because we don’t yet have detailed information about the surface of Europa, users can select from terrain models with a variety of surface and material properties. One of these models is a digital replication of a portion of the Atacama Desert in Chile, an area considered a potential Earth-analog for some extraterrestrial surfaces.

JPL’s Europa Lander Study of 2016, a guiding document for the development of OceanWATERS, describes a planetary lander whose purpose is collecting subsurface regolith/ice samples, analyzing them with onboard science instruments, and transmitting results of the analysis to Earth.

The simulated lander in OceanWATERS has an antenna mast that pans and tilts; attached to it are stereo cameras and spotlights. It has a 6 degree-of-freedom arm with two interchangeable end effectors—a grinder designed for digging trenches, and a scoop for collecting ground material. The lander is powered by a simulated non-rechargeable battery pack. Power consumption, the battery’s state, and its remaining life are regularly predicted with the Generic Software Architecture for Prognostics (GSAP) tool.

To simulate degraded or broken subsystems, a variety of faults (e.g., a frozen arm joint or overheating battery) can be “injected” into the simulation by the user; some faults can also occur “naturally” as the simulation progresses, e.g., if components become over-stressed. All the operations and telemetry (data measurements) of the lander are accessible via an interface that external autonomy software modules can use to command the lander and understand its state. (OceanWATERS and OWLAT share a unified autonomy interface based on ROS.)

The OceanWATERS package includes one basic autonomy module, a facility for executing plans (autonomy specifications) written in the PLan EXecution Interchange Language, or PLEXIL. PLEXIL and GSAP are both open-source software packages developed at Ames and available on GitHub, as is OceanWATERS.

Mission operations that can be simulated by OceanWATERS include visually surveying the landing site, poking at the ground to determine its hardness, digging a trench, and scooping ground material that can be discarded or deposited in a sample collection bin. Communication with Earth, sample analysis, and other operations of a real lander mission, are not presently modeled in OceanWATERS except for their estimated power consumption. Figure 6 is a video of OceanWATERS running a sample mission scenario using the Atacama-based terrain model.







https://scx2.b-cdn.net/gfx/video/2024/toward-autonomous-surf-1.mp4
Figure 6. Screenshot of OceanWATERS lander on a terrain modeled from the Atacama Desert. A scoop operation has just been completed. Credit: NASA/JPL – Caltech

Because of Earth’s distance from the ocean worlds and the resulting communication lag, a planetary lander should be programmed with at least enough information to begin its mission. But there will be situation-specific challenges that will require onboard intelligence, such as deciding exactly where and how to collect samples, dealing with unexpected issues and hardware faults, and prioritizing operations based on remaining power.

Results

All six of the research teams used OceanWATERS to develop ocean world lander autonomy technology and three of those teams also used OWLAT. The products of these efforts were published in technical papers, and resulted in the development of software that may be used or adapted for actual ocean world lander missions in the future.

Provided by
NASA


Citation:
Planning autonomous surface missions on ocean worlds (2024, December 4)
retrieved 4 December 2024
from https://phys.org/news/2024-12-autonomous-surface-missions-ocean-worlds.html
This document is subject to copyright. Apart from any fair dealing for the purpose of private study or research, no
part may be reproduced without the written permission. The content is provided for information purposes only.
Exit mobile version