Chaser Control — Docking Without Oscillation

A chaser spacecraft cannot simply point toward a target and accelerate. In orbit, the controller must work with relative dynamics, reduce both separation and closing speed, avoid oscillation, respect control limits, and stay inside a safe approach corridor.

Docking is a control problem, not just a guidance problem.
1. Problem Setup

From CW Motion to Controlled Docking

A chaser spacecraft begins near a target in circular orbit. In the previous CW problem, natural relative motion could oscillate or drift depending on initial conditions. Now the goal changes: can we design a controller that brings the chaser safely to the target?

The core question is whether the chaser can dock without overshoot, oscillation, or excessive control effort.

x

Radial relative position.

y

Along-track relative position.

vx, vy

Relative velocity components.

ux, uy

Control acceleration commands.

2. Physical Meaning

Docking Is Not Straight-Line Motion

Docking is not the same as flying directly toward the target. If the chaser commands motion directly toward the target, orbital coupling can make it overshoot, loop around, or drift along-track.

Important:
In orbit, “go toward the target” is not automatically a safe docking strategy.
3. Controlled CW Equations

Adding Control to Relative Motion

The controller enters the CW equations as acceleration commands in the radial and along-track directions.

$$ \ddot{x} - 2n\dot{y} - 3n^2x = u_x $$ $$ \ddot{y} + 2n\dot{x} = u_y $$

The controller must overcome the natural coupling between radial and along-track motion.

4. Controller Model

PD Control for Docking

The first controller is a simple PD law. Position feedback pulls the chaser toward the target, while velocity feedback damps the closing motion.

$$ u_x = -K_p x - K_d\dot{x} $$ $$ u_y = -K_p y - K_d\dot{y} $$
Too little damping

Oscillation around the target.

Too much gain

Aggressive approach, overshoot, or saturation.

Too little gain

Slow drift and poor docking.

5. Interactive Section 1

Docking Controller Tuning

Adjust the initial condition, controller gains, orbit altitude, control limit, and simulation time. Watch the trajectory, velocity, separation, control commands, effort, and docking status update.

Scenario buttons:


















Toggles:
6. Docking Success Criteria

Docking Is More Than Reaching Zero Position

Docking is successful only if the chaser reaches the target slowly, safely, and without excessive control demand.

successful docking if:
final separation < 1 m
final relative velocity < 0.05 m/s
saturation percentage is not excessive
trajectory remains inside the safety corridor
Final Separation

Waiting...

Final Relative Velocity

Waiting...

Max Separation

Waiting...

Max Overshoot

Waiting...

Control Effort

Waiting...

Saturation Percentage

Waiting...

Docking Status

Waiting...

7. Interactive Section 2

Docking vs Oscillation Scenarios

Use the preset buttons to compare four control behaviours: clean convergence, underdamped oscillation, aggressive overshoot, and weak control drift.

Stable docking

Moderate Kp and good Kd produce clean convergence.

Underdamped oscillation

High Kp and low Kd repeatedly cross the target.

Aggressive overshoot

Very high gain reaches fast but can violate safety limits.

Weak controller drift

Low gains cannot overcome relative dynamics quickly enough.

8. Safety Corridor Visualization

The Path Must Be Safe Too

A controller may reduce separation eventually but still be unsafe if it leaves the docking corridor. The corridor here represents a simple approach rule: while approaching along-track, radial deviation should remain within a bounded safety envelope.

Docking safety insight:
Reaching the target is not enough. The path to the target must also be safe.
9. Control Saturation

When the Controller Asks for More Than the Thruster Can Give

The controller may command more acceleration than the vehicle can physically apply. Saturation clips the commanded acceleration.

$$ u_{actual} = \text{clip}(u_{commanded}, -u_{max}, u_{max}) $$
Max Commanded Acceleration

Waiting...

Max Applied Acceleration

Waiting...

10. Fuel / Control Effort Metric

Docking Also Has a Propellant Cost

A simple control-effort metric estimates how much total acceleration the controller used. Lower control effort suggests less propellant usage, but too little effort may mean slow or unsafe docking.

$$ J_u = \int_0^T \sqrt{u_x^2 + u_y^2}\,dt $$
11. Interactive Section 3

Kp–Kd Gain Map

Controller tuning is not about one magic value. It is about finding a safe stability region. The map classifies gain combinations as successful, oscillatory, slow, or failed/unsafe.

12. Compare Control Strategies

No Control vs PD vs Saturated PD

This overlay links the previous CW page to control design: no control drifts, PD converges, and saturated PD may converge more slowly or fail if control authority is too low.

13. Engineering Interpretation

What the Controller Is Really Doing

Rendezvous meaning

The chaser must remove both relative position and relative velocity.

Control tuning meaning

Kp pulls toward the target. Kd damps closing speed. Good docking needs both.

Orbit meaning

The plant is not flat-space motion. It is shaped by CW orbital dynamics.

Safety meaning

A stable controller can still be unsafe if it overshoots, violates the corridor, or uses too much effort.

14. Final Takeaways

What This Problem Shows

Docking needs damping

Position control alone can create oscillation around the target.

Velocity matters

Low final separation is not enough if closing speed is too high.

Limits matter

Control saturation can turn a good theoretical controller into a poor practical one.

Safety path matters

The trajectory must remain inside an acceptable approach corridor.

15. Next Problem

Formation Flying Stability

Docking focuses on bringing one chaser to one target. Formation flying asks a harder question: can multiple spacecraft maintain a desired relative geometry over time when small errors and disturbances continuously appear?