Nautilus - Flight Dynamics and Spacecraft Autonomy
nautilus nautilus nautilus nautilus nautilus nautilus nautilus nautilus

0

Loading ...

Functional architecture

  • 01

    Dedicated processing unit

    Custom onboard processing unit, entirely designed and developed by Nautilus, optimized to host and execute EON's software.

  • 02

    GNSS drop-in replacement

    Integrated GNSS receiver providing raw measurements required for onboard processing.

  • 03

    Navigation & Collision avoidance, onboard

    GNSS-based onboard POD and collision avoidance proprietary algorithms. Onboard, minimizing interactions with the ground.

  • 04

    Inter-satellite link

    Embedded LoRA communication module enabling peer-to-peer data exchange between devices.

    - 'TRL Level: 5'
    - 'Development status: Active development'

TRL Level: 5 | Development status: Active development
Concept of operations

How EON flies your satellite.

From integration on the ground to an avoidance manoeuvre executed in orbit — four phases, no ground pass required in between.

Why EON

One change onboard.
Four consequences on the ground.

Move the flight dynamics onboard, and the rest of your operations change with it

Step 01

Onboard Navigation and Collision Avoidance

EON determines its own orbit, assesses conjunction risk, and plans its own manoeuvres with minimal ground station intervention.

50-60%
Step 02

Minimized ground workload

Routine orbit determination and manoeuvre planning leave the ground team. They supervise the fleet instead of running the loop for every satellite.

Step 03

Efficient propellant use

Fresh measurements, onboard. Reduced number of false positives, relative OD with other secondaries: fewer maneuvers, when they matter.

Step 04

Scale with the fleet

Satellites share orbit data peer-to-peer, so accuracy improves as the fleet grows. Going from five satellites to fifty multiplies the operations, not the operators.

01

Navigation onboard

EON determines its own orbit, plans its own manoeuvres and assesses conjunction risk directly on the spacecraft — no ground station in the routine loop.

02

No ground pass to wait for

A conjunction is handled when the risk appears, not when the next contact window allows.

03
50–60%

Less ground workload

Routine orbit determination and manoeuvre planning leave the ground team. They supervise the fleet instead of running the loop for every satellite.

04

Less propellant burned

The onboard camera refines the secondary object's orbit and cuts false positives, so fewer avoidance manoeuvres are executed.

05

Scales with the fleet

Satellites share orbit data peer-to-peer, so accuracy improves as the fleet grows. Going from five satellites to fifty multiplies the operations, not the operators.

Technical datasheet

Under 1U. Under 3 W.

A PC104-footprint unit integrating the navigation computer, GNSS reception and the inter-satellite link in a single enclosure.

EON flight unit, top view ~90 mm ~96 mm
< 1U PC104 footprint
< 3 W Power
L1 + L5 GNSS bands
Physical
Form factor
PC104 footprint, < 1U
Footprint
~90 × 96 mm
Volume
< 0.3U
Mass
< 150 g
Power consumption
< 3 W
Navigation & processing
GNSS receiver
L1, L5
Processor
COTS MCU, STM32H7
Storage
16 GB
Communication & electrical
Inter-satellite link
LoRa, UHF band
Power supply
Redundant
Interfaces
Connectors
SMA, DB9 — fixed to PCB
Mounting
Enclosure mounting