Attitude and Thrust controllers, Flight Guidance System

The block diagram below presents the CSN  F9’s flight control system. The ship’s Inertial Navigation Units (INUs) collect and feed the necessary real-time inputs (attitude, location, velocity, mass, center of mass location, moments of inertia). The flight planner provides the reference trajectory data for the flight guidance system (master autopilot).

CSN F9 space frigate: Flight Control system
 
At the center of the system the attitude and thrust controllers effectively command the ship’s thrusters.
 
← The pilot configures the whole flight controller by selecting the respective attitude and thrust modes.  The flight guidance autopilot automatically engages according to the selecting settings and reference flight plan schedule.
  • The Attitude Controller is a feedback system that manages the ship’s pitch, roll and yaw angles using MRU rotational thrust (torque) and thrust vectoring on the main engine when available.
  • The Thrust Controller translates the pilot and flight guidance inputs into commands to the MRUs (linear thrust) and fusion controller (main engine thrust).
  • The Flight Guidance System is the ship’s master autopilot. When active it takes dynamic command of the attitude and thrust controllers to maintain or bring back the ship on to the loaded reference trajectory. The small central panel below the AIM attitude selector provides information on its current state, estimated current error (aggregated as [m]) and the currently applied thrust corrections.
  • Although the attitude controller’s user inputs are split into two ROLL and AIM (pitch + yaw) selectors, it internally operates as a unified 3-axis system. Its stability parameters are automatically adjusted depending on the allocated thrust (torque) and estimated moments of inertia. The “∫ε” symbol on the front panel (top-right of the AIM selector) indicates that an additional integrator has been activated to optimize the pursuit performance.

  • By default (“thrust axis” button) the ship’s reference frame is defined using the main thrust axis (~ main nozzle to center of mass) and not the geometrical longitudinal axis. This is to dynamically compensate for mass imbalances from the main LH2 tanks (primarily).

  • Tracking a point under acceleration from multiple forces (thrust, gravity) is not an easy task for regular feedback systems such as PIDs. As a result the flight guidance system is based on a Model Predictive Control approach. In practice it uses a model of the current flight conditions to search for thrust commands that would minimize the ship’s position and velocity error when propagated some time ahead in the future. This process is continuously repeated several time per (real word) second.

Maneuvering Reaction Units (MRU)

MRUs are arrays of magnetoplasmadynamic thrusters, using hydrogen plasma as propellant and drawing their power from the ship’s main ec bus. They complement the main engine for all high-precision low-ΔV maneuvers:
  • Attitude control
  • Course corrections
  • Station keeping / relative flight

  • The Maneuvering Systems panel (helm station) regroups the MRU related controls.
  • The LIN and ROT sliders divide the total thrust between the linear (translation) and rotational (attitude) modes respectively,
    with LIN + ROT ≤ 100% (e.g. 20% / 20% is a valid setting that limits the total allocated thrust).
  • The Power Saturation slider controls the allocated electrical power as a function of the commanded thrust. The default setting will offer better ISP at low thrust as a trade-off with power consumption.

Note: the term “maneuvering” may be misleading considering that MRUs are powerful engines in their own right and can draw large amounts of electrical power from the ship’s electrical system. Due to their relatively low ISP they may also consume large amounts of hydrogen and significantly affect the overall ΔV budget.
As a general rule: the lower the commanded MRU thrust and impulse, the better.

Primary Flight Controls and Instruments

The main CSN F9’s flight controls are located in the Helm Station:

CSN F9 space frigate: primary flight controls
  • Attitude and Thrust command panel (top)
    The primary inputs governing the ship’s attitude (roll, aim = pitch + yaw) and thrust mode. The flight guidance system (full autopilot) automatically engages based on your settings and the loaded flight plan.

  • Nav Orb (bottom left)
    Displays various pointers and the current orbital frame of reference with respect to the ship’s reference frame:
    + prograde = along the ship’s velocity vector (“forward”)
    + normal = along the normal to the orbital plane (“up”)
    + radial = in the orbital plane at right angle from the velocity vector (“right”, away from the parent celestial body)

  • Orbit Display (bottom right)
    Indicates the current orbital elements and provides a 3D view of the ship on its orbit with respect to the parent body.

Flight Control Modes

The flight control matrix presents a summary of the available modes. From left to right:

  • The mode and its intended use.
  • Whether the main thrust is produced by the main engine or the MRUs.
  • The corresponding Attitude and Thrust settings to be selected on the front helm panel.
  • Whether the flight guidance system is active for the mode or not.

Note: the APP sub-modes are presented below.

Plan then Fly

There is no such thing as approximate space flight if one wants to get anywhere. Typical trips involve a few jumps and tenths of trajectory legs and maneuvers. At each step any small position or worse velocity error will always accumulate and eventually make the following steps irrelevant. This is why it is much more efficient to plan first and then to use the flight guidance system to stay on track all along to the destination.

For simple orbit adjustments or when the tactical situation imposes quick reactions the orbit display can provide a quick overview of the evolving trajectory. However this is not a safe method: lose focus while manually lowering a periapsis on MRU thrust close to an atmosphere and your flight engineer would better master the fast fusion spool-up techniques or you are in really big trouble…

The following video presents the CSN F9’s flight control systems in a simple example burn.

Approach modes (relative flight)

Flying in the vicinity of a space station is a very delicate operation. The limited available thrust with respect to the ship’s mass requires considerable anticipation of  the motion and a constant control over position, velocity and attitude (especially when docking). Typically coming to a rest from a relative approach velocity of 20 m/s (72 km/h, 45 mph) will take about 100 s and 1 km. In a full 3D environment, without any dampening and in the presence of drift forces (differential gravity effects) manual piloting is extremely difficult and exhausting.
As a consequence the CSN F9’s flight  controller provides all the necessary assistance for safe operations.

When the THRUST controller is in the “APP” mode a specific set of flight controls is displayed:

CSN F9: Approach flight controls
  • Central console
    Provides information about the approach controller state, toggles for navigation visualization aids and the docking port controls.
  • Relative Flight control panel
    Features all the necessary controls to set the reference object (“anchor”), execute translations in its vicinity and dock to one of its docking ports.
  • 3D view
    Displays a schematic view and information about the ship with respect to the reference object.

Reference Frame and Origin

Approach modes are flown relatively to a selected object, a space station most of the time. Its center of mass is the origin for all coordinates, and its orbital frame is used as reference:

  • the Y axis is set along the prograde direction of the orbit (direction of the velocity vector),
  • the Z axis is given by the oriented normal to the orbital plane,
  • the X axis derives from Y and Z (and generally points away in a radial direction from the orbited celestial body).

However since all operations are centered on the reference object it is more convenient to express locations and command translations using the cylindrical coordinates (r, α, z) where:

  • r is the distance from the Z axis,
  • α measures the clockwise angle from the Y axis (defined as “0°”),
  • z is the altitude w.r.t the orbital plane (positive above).

Restricted Flight Areas

Space facilities are protected against collisions by virtual Non-Flying-Zones. For space stations this generally includes a capsule (cylinder with hemispherical caps) around the main station’s body, supplemented by volumes around the additional obstacles:
  • space elevator cable,
  • orbital ring and link cable,
  • planetary rings.

In approach mode the flight controller constantly monitors the ship’s location and velocity and will automatically take control and brake to a stop in case or imminent violation. It will also attempt to return to authorized space in case of effective trespassing.

Docking ports can only be accessed through a narrow corridor (of conical shape) extending from the port to the corresponding Docking Ingress Point (the DIP lies outside of the station’s restricted area).

Navigation Data

Facilities must provide the necessary flight information (restricted areas and docking ports) via a radio link. The process follows an automated protocol on the NavData channel set. The relative flight panel’s anchor section provides simple controls to easily set a comms unit slot as required and send a navdata request.

Approach Control Modes

The approach control matrix provides a summary of the related flight modes. From left to right:

  • Mode designation,
  • Command inputs,
  • Description and additional notes.

Note: the mode selector sets the displayed inputs (at its right) as required:

Translation velocity and MRU thrust

The desired velocity for all translations is set using the selector at the top right of the relative flight panel. The default is 3 m/s, please note that the ΔV cost of all moves heavily depends on this setting.
The flight controller will use all of the available linear thrust as needed (and which depends on the number of active MRUs and “LIN” slider allocation on the “Maneuvering Systems” panel).

Engagement process

The procedure requires two steps:

  1. Prepare then select the desired operation, which then becomes the “pending” APP mode,
  2. Press the “engage” control so that the pending mode becomes active.

Most operations automatically prepare a subsequent pending mode: for instance the controller will plan to “HOLD” at the destination of a (r, α, z) translation. This step can also be automatic, for instance a “STOP” always engages a “HOLD”, whatever the pending mode.

NB: the main overall “APP” thrust mode should remain engaged during all relative flight operations.

How-to: approach, departure and jump execution videos