The Ground Segment (GS) provides a web interface to centralize commanding and coordinations of the Flight Software (FS). It compiles commands and groups files to be uplinked to the FS when requested to, and it is meant to be used for both the development and operations phases of a payload by the user.
Below you will find an overview of the different tabs.
The Home tab provides a quick overview of the following points:
Current Compute Usage: shows in a pie chart the total execution time for each compute node (i.e. MPU, GPU or FPGA) used on-board.
Weekly Downlink Overview: shows in a graph chart the total size of downlinked data in bytes for the last week.
Current Downlink Usage: shows the total amount of data downlinked since the start of operations.
This values will be resetted before the operations start.
The Commander tab is where users will request for commands to be executed on the DPhi Space FS. The commands that are supported are explained in Commands.
The Command Sequence Editor allows the user to create command sequences.
The Command Files lists all the created command files. The user can update, delete or activate them. When a command file is activated, they will be tagged for execution when requested by the FS Interface, which will fetch the activated command files and send them to the running FS instance.
TODO
The Files tab allows a user to upload files to the GS, which will be sent to the FS if request, and gives an overview of the following files :
-Uploaded Files Files uploaded to the GS by the user. They can be deleted, downloaded or requested to be uplinked.
-Downlinked Files Files that have been downlinked from the FS by a previous command execution. The files can be requested to be downlinked by either the On-Board Files downlink button below or by the downlink command in a command sequence.
-On-Board Files Files that are in the user’s volume in the FS. The user can request to delete them or downlink them if needed, which will be done on the next command sequence execution.
The Docker Images tab allows user to request Docker Images to be loaded on the FS. It is strongly advised to do this early in development. The requested Docker Images need to support OS/ARCH linux/arm64 or linux/aarch64. This link provides a list of all the Docker Images in Docker Hub that support this architecture.
The Profile tab provides a simple overview of the user’s account information.
Now we have everything to interface with the Flight Software: