Skip to content

Topology

Jump to bottom
Jonathan Michel edited this page Feb 3, 2021 · 4 revisions

WorkInProgress

TODO

  • Clear explanation on current implementation progress
  • Explain components roles
  • Explain Project & Deployment

F' Reference topology

The following diagram presents the F' Ref Topology. It is an example of an application containing F' core component (in Blue) with custom Ref components (in Green).

Check the F' Getting started tutorial for a better hands on to F´ with this topology.

Orange components are the ones added during F' tutorials: Math tutorial and Gps tutorial.

FS - F' topology - Ref Click here for a better resolution (SVG)

CHESS FS Topology

Overview

The CHESS Topology is based on the Ref one. Each payload is handled by a F' component and connected to a specific driver depending on payloads communication requirements. The following diagram presents the design of the final implementation for the CHESS FS.

At this day, only the EPS and ADCS components have been implemented. Their corresponding drivers are over IP in order to connect them to software simulators.

FS - F' topology - overview Click here for a better resolution (SVG)

Full topology

The following diagram presents the full CHESS Topology thought for the final flight software implementation.

FS - F' topology - CHESS Click here for a better resolution (SVG)

PUS support

Current flight software can be run with or without PUS support. Previous diagrams do not present PUS usage. When enabled, the connection between the GroundInterface component and the TlmChan & ActiveLogger components slighty differs. Furthermore, a PUS stack is added in the GroundInterface and the TlmChan component.

FS - F' topology - PUS VS GDS

Click here for a better resolution (SVG)

Clone this wiki locally