Terrestrial Rovers in Space Analog Testing: How Labs Simulate Planetary Missions

TL;DR: Planetary rover analog testing uses terrestrial robots and Earth-based sites to rehearse mission operations, validate autonomy stacks, and stress-test hardware before flight. Analog campaigns can reproduce terrain morphology, communication latency, energy budgets, and crew workflows with useful fidelity. They cannot fully reproduce reduced gravity, authentic regolith mechanics, vacuum, or radiation. Small ROS 2 platforms like Leo Rover can serve as low-cost surrogates for procedure development, operator training, and autonomy research.

Why planetary rover analog testing matters before flight

Flight hardware is expensive, schedule-constrained, and unforgiving. Before a rover leaves Earth, teams need to answer engineering questions that simulation alone cannot close: how operators react under communication delay, how a perception pipeline behaves on unmodeled terrain, how a thermal cycle affects a drivetrain after a hundred kilometers of driving. Planetary rover analog testing is the practice of running those experiments on Earth with representative robots, representative environments, and representative operational constraints.

An analog test is not a demo. It is a controlled trial with a hypothesis, a scenario, defined success criteria, and a data collection plan. The fidelity you need depends on what you are testing. A traverse-planning algorithm may only require accurate terrain geometry. A crew procedure may require a full mission control loop with imposed latency. Understanding what you can and cannot simulate is the first step in designing a useful campaign.

What an analog test actually looks like: terrain, scenario, link delay, energy

A typical analog campaign has four constraints that shape everything else: the terrain, the operational scenario, the communication link, and the energy budget.

Terrain selection

Analog sites are chosen for geological or morphological similarity to the target body. Well-known examples include the Atacama Desert in Chile (dry, Mars-like soils, used for trials involving Carnegie Mellon’s Zoë rover), Rio Tinto in Spain (acidic mineralogy relevant to astrobiology, used in the MARTE project), Devon Island in the Canadian Arctic (impact crater, used by the Haughton-Mars Project), the Mojave Desert, Utah’s Mars Desert Research Station, and Lanzarote, which is used by ESA’s PANGAEA program. Indoor “Mars yards” at JPL, DLR, and other institutions provide repeatable conditions with graded slopes, sand pits, and controlled lighting for perception testing.

Scenario design

A scenario specifies mission phases, objectives, and off-nominal events. A traverse scenario might require the rover to reach three waypoints, acquire panoramas at each, and return within a fixed sol budget. Injected faults (wheel slip, sensor dropout, unexpected obstacle) test fault detection and recovery. Scenarios are usually written as ConOps documents and executed against a timeline.

Communication latency and bandwidth

Real Mars round-trip light time varies between roughly 6 and 44 minutes depending on orbital geometry (source: NASA JPL Deep Space Network documentation). Analog tests emulate this with software delay layers on the telemetry and command links. Bandwidth caps are also imposed, forcing operators to prioritize data products and rely on onboard autonomy rather than teleoperation. In ROS 2 setups, tools like tc (Linux traffic control) or dedicated bridge nodes can throttle DDS traffic between the rover and the operations network.

Energy constraints

Solar-powered rovers operate under strict energy budgets. Analog tests reproduce this by limiting battery capacity, scheduling activities around simulated solar availability, and forcing power-aware planning. Teams log watt-hours per meter traversed and per science observation to validate energy models.

What you can reproduce on Earth, and what you cannot

Analog testing is powerful because much of what makes planetary operations hard is not physics but process. However, honest program planning requires acknowledging the fidelity gap.

What terrestrial analog testing reproduces well:

• Terrain geometry: slopes, rocks, sand traps, and obstacle distributions can be matched to orbital and lander imagery of the target site.
• Operational cadence: mission-day or sol-based planning, uplink and downlink windows, and tactical timelines can be reproduced.
• Communication delay and bandwidth: software-imposed latency and throttling replicate the cognitive and procedural impact on operators.
• Autonomy software: perception, SLAM, path planning, and fault management stacks can be exercised end-to-end using the same ROS 2 code architecture intended for flight-like hardware.
• Human factors: crew procedures, EVA-rover coordination, and mission control workflows.

What cannot be reproduced on Earth without specialized facilities:

• Reduced gravity: Mars gravity is approximately 0.38 g and Lunar gravity approximately 0.16 g (source: NASA planetary fact sheets). This changes traction, wheel sinkage, suspension dynamics, and center-of-gravity margins. Parabolic flights and gravity-offload rigs give partial coverage but not sustained traverse testing.
• Authentic regolith mechanics: lunar regolith is angular, electrostatically charged, and abrasive in ways terrestrial simulants (JSC-1A, LHS-1, MGS-1) approximate but do not fully match. Vacuum-exposed regolith behaves differently from material that can be handled in an open sandbox.
• Vacuum and thermal extremes: outgassing, cold-welding, and thermal cycling across approximately −173 °C to +127 °C lunar surface temperatures require vacuum chambers, not open terrain. Actual surface temperatures vary substantially by location, illumination, and terrain.
• Radiation: galactic cosmic rays and solar particle events affect electronics and materials in ways that require specialized radiation testing and are ultimately verified in the relevant space environment.
• Lighting geometry: the Sun is an effectively directional source with no atmospheric scatter on the Moon, producing extreme shadow contrast that terrestrial daylight rarely matches. Indoor Mars yards with controlled lighting come closer.

How small terrestrial rovers fit into analog campaigns

Not every analog test needs a full flight-mass prototype. Small, low-cost UGVs serve as surrogates for procedure development, autonomy research, and operator training. A platform like the Leo Rover provides a four-wheeled ROS 2 robot with a documented API and payload capacity for sensor suites such as stereo cameras, IMUs, LiDAR, or spectrometers.

Typical uses in analog work include:

• Testing autonomy stacks (Nav2, SLAM Toolbox, custom planners) on outdoor terrain before porting to larger platforms.
• Running student and early-career missions where teams practice the full plan-execute-review loop under imposed latency.
• Prototyping science payload integration and data pipelines.
• Field-testing communication architectures, including mesh networks and store-and-forward relays.

Because ROS 2 is widely used in space robotics research, code and workflows developed on a small rover can be adapted to larger analog or flight-precursor platforms, although hardware interfaces and real-time requirements may require additional work. Fictionlab documents integration patterns and reference stacks aimed at research applications, including analog mission scenarios.

Which institutions run planetary rover analog testing

Analog campaigns are run by space agencies, universities, and independent research groups. A non-exhaustive list of programs and facilities, including some that are historical or have evolved over time:

• NASA: JPL Mars Yard, Ames Research Center field-analog research, and Johnson Space Center’s Desert RATS program and its successor exploration field tests.
• ESA: PANGAEA and PANGAEA-X in Lanzarote, ExoMars rover operations and testing at ALTEC in Turin, and the Planetary Robotics Laboratory at ESTEC.
• DLR: the German Aerospace Center operates a Planetary Exploration Lab and has run ROBEX and ARCHES campaigns on Mount Etna.
• CSA: the Canadian Space Agency supports analog deployments in the Canadian Arctic and operates a Mars Yard in Saint-Hubert.
• JAXA and CNSA conduct terrestrial testing for lunar and Mars exploration technologies.
• Universities: Carnegie Mellon (Zoë and other field robots), ETH Zurich (ANYmal on lunar analog terrain), the University of Bremen, and DFKI’s Robotics Innovation Center, among many others.

Programs like the Mars Desert Research Station (operated by the Mars Society) and the University of North Dakota’s Inflatable Lunar/Mars Analog Habitat host mixed crewed and robotic scenarios that let smaller teams participate without agency-scale budgets.

How to design a useful analog test

A defensible analog campaign follows a few practical rules. Define the hypothesis first: what specific question about the flight system are you answering? Choose the minimum fidelity that answers it. If you are validating a path planner, you do not need a vacuum chamber. If you are validating a wheel design, you need regolith simulant and slope, not link delay.

Instrument everything. Log all ROS 2 topics with ros2 bag, timestamp every operator action, and record video of both the rover and the control room. Post-campaign analysis is where most of the value is captured. Publish or archive your data: analog datasets from Atacama, Devon Island, and Etna have become reference material for the community.

Finally, treat off-nominal events as first-class test objectives. A rover that completes a perfect traverse teaches you less than one that gets stuck and recovers under a 20-minute delay.

Frequently asked questions

What is the difference between an analog mission and a field test?

A field test validates hardware or software in a realistic environment. An analog mission adds mission operations: timelines, delayed communication, science planning, and sometimes a crewed element. Many analog missions include field tests, but not all field tests are analog missions.

How is communication delay implemented in a ROS 2 setup?

Most teams use Linux tc netem to add fixed or variable latency on the network interface between the rover and the operations LAN, or run a dedicated relay node that buffers and releases messages on a schedule. DDS discovery may be kept on a separate low-latency channel when the test focuses on application workflows; if network behavior itself is under test, discovery should be included in the delay model.

Can you simulate Mars gravity for wheel testing?

Partially. Gravity-offload rigs using overhead cables or counterweights reduce effective vehicle weight and are used at JPL and DLR. They introduce their own dynamics and are limited to constrained workspaces. Parabolic flights give seconds of reduced gravity, useful for deployment mechanisms but not sustained driving.

Which regolith simulants are standard?

For the Moon, JSC-1A (historically), LHS-1 and LMS-1 from Exolith Lab, and NU-LHT variants from NASA are commonly used. For Mars, MGS-1 (Exolith), MMS, and JSC Mars-1A are used. Each captures different aspects (mineralogy, particle size distribution, mechanical properties) and none is a full match. Selection depends on the test objective.

Do small rovers like Leo Rover produce useful analog data?

Yes, for autonomy, operations, and training objectives. They are not substitutes for flight-mass prototypes when testing mechanical scaling, thermal behavior, or high-payload science instruments. They can serve as the first step in a graduated test program.

How long does a typical analog campaign last?

Deployments range from a few days for focused field tests to multi-week campaigns such as Desert RATS and other extended crewed analog missions. Longer campaigns allow crew rotation, procedure iteration, and off-nominal scenario coverage that short trips cannot.

What ROS 2 packages are commonly used?

Nav2 for navigation, SLAM Toolbox or RTAB-Map for mapping, robot_localization for sensor fusion, and rosbag2 for data capture. Mission-level orchestration is often handled with behavior trees (BehaviorTree.CPP) or custom state machines. Simulation counterparts run in Gazebo or Isaac Sim.

Take the next step

If your team is planning analog work for lunar or Mars mission development, autonomy research, or operator training, explore how Fictionlab supports space-sector projects at fictionlab.pl/applications/space. You will find integration references, payload options, and examples of research applications for Leo Rover.