Autonomous Rendezvous, Proximity Operations, & Docking (RPOD) Testbed

As space assets grow in strategic and commercial value, operators need reliable ways to monitor, approach, inspect, and protect them. Nations and commercial operators are deploying maneuverable inspector spacecraft and large constellations for space domain awareness and defensive operations. Each trend creates the same technical need: a spacecraft that can autonomously characterize a nearby object and decide whether to approach, hold, or evade.

This project focuses on development of a low-cost, ground-based testbed for autonomous rendezvous, proximity operations, and docking (RPOD). The testbed focuses on space domain awareness: characterizing potential orbital threats and executing protective approach, inspection, and evasion maneuvers. The testbed pairs caster-based vehicles tracked by motion capture with simulation. This lets us test autonomy and sensing algorithms repeatedly and cheaply before building higher-fidelity hardware. Developing and validating a ground testbed for RPOD algorithms lets us repeat approach, tracking, and evasion trials at low cost and low risk. It also lets us change hardware as the design matures instead of committing early to one propulsion or structural system. A close approach can read as inspection or as a threat depending on intent and context, so our threat-characterization logic must state its assumptions explicitly.

 

Name of research group, project, or lab
Computing in Spaceflight Lab
Logistics Information:
Project categories
Aerospace and Mechanical Engineering
Computer Science & Engineering
Student ranks applicable
Senior
Student qualifications

Completion of CSE 40522 -Computer Engineering Capstone Design and project-based experience with spaceflight computing.

Hours per week
2 credits / 6-12 hours
3 credits / 12+ hours
Compensation
Research for Credit
Number of openings
6
Techniques learned

The testbed has two layers. Physical vehicles on a tabletop move under autonomous control while a motion-capture system tracks their positions in real time. A simulation environment models the orbital context and the phases we cannot reproduce physically, running in the loop with the vehicles. Our first phase will fix which RPOD phases run on hardware, and which run in simulation.

We selected caster-based vehicles for the initial testbed because they allow a multi-vehicle system within an undergraduate budget and require no specialized floor or compressed-air infrastructure. Caster friction prevents faithful reproduction of drag-free orbital dynamics and contact behavior, so this phase does not attempt to validate thruster-based control or capture dynamics. Instead, it validates the autonomy and sensing stack: motion-capture-based relative navigation, threat characterization from telemetry, approach and evasion decision logic, and guidance algorithms running in the loop with simulation. The software will be built around a hardware abstraction layer, so the same stack can later run on air-bearing vehicles for higher-fidelity dynamics testing.

Contact Information:
Mentor
mmorri22@nd.edu
Associate Teaching Professor
Name of project director or principal investigator
Matthew Morrison
Email address of project director or principal investigator
matt.morrison@nd.edu
6 sp. | 0 appl.
Hours per week
2 credits / 6-12 hours (+1)
2 credits / 6-12 hours3 credits / 12+ hours
Project categories
Aerospace and Mechanical Engineering (+1)
Aerospace and Mechanical EngineeringComputer Science & Engineering