OPS-SAT was a CubeSat by the European Space Agency (ESA), intended to demonstrate the improvements in mission control capabilities that will arise when satellites can fly more powerful on-board computers. The mission had the objective to break the cycle of "has never flown, will never fly" in the area of satellite control. It was the first CubeSat operated directly by ESA.[1]
The satellite had an experimental computer that is ten times more powerful than traditional ESA on-board computers. This on-board computer provided an experimental platform to run software experiments on board. One innovative concept was the deployment of space software in the form of apps. This concept was enabled by the NanoSat MO Framework (NMF) and allowed Apps to be uploaded to the spacecraft and then started on board. This was a new concept that ESA has successfully demonstrated in space.[6]
OPS-SAT was launched at 08:54:20 UTC on 18 December 2019, exactly twenty-four hours later than originally planned. The satellite deorbited on 22 May 2024.[7] During its descent, ESA collaborated with amateur radio enthusiasts to collect as much data as possible, observing the effects on the satellite as it passed through the Earth's lower atmosphere.[8]
OPS-SAT provided an in-orbit test-bed environment for the deployment of different experiments to test new protocols, new algorithms, and new techniques. The satellite was designed to be robust and no single point of failure should exist, so that it was always possible to recover the spacecraft if something went wrong with one of the software experiments. The robustness of the basic satellite itself allowed ESA flight control teams to upload and try out new, innovative control software submitted by experimenters.
The Experimental Platform of OPS-SAT was where experiments were executed. It had two Critical Link MityARM 5CSX in cold redundancy (if one failed, the second one was used). These had a Dual-core 800 MHz ARM Cortex-A9 processor, an Altera Cyclone V FPGA, 1 GB DDR3 RAM, and an external mass memory device with 8 GB.[9]
ESA's aim was to remove as many barriers to experimentation as possible. For example, there was little to no paperwork, ESOC's infrastructure was set up to do automated tests on the experiments, with the aim of reducing the overheads close to zero. Additionally, the experiments could be easily developed in form of apps using the NanoSat MO Framework.
First space mission dedicated to operational technology.[6]
First nanosatellite directly owned and operated by ESA.[6]
First in-orbit laboratory where the public can load and test software/firmware.[12]
First ESA mission directly controllable in real-time over the internet by the public.[13]
First mission to offer an on-board environment (NMF) that allows the easy development of apps for upload and execution, comparable to the concept of modern smartphones.[14]
First ESA mission to reconfigure an in-orbit FPGA on a daily basis.[11]
First mission commanded with Europe’s next-generation mission control system EGS-CC.[15]
First in-orbit decoding and processing of ground-based emergency beacons.[16]
First ground-to-space API access of an in-orbit hosted Software-as-a-Service (SaaS) application.[17]
The most innovative concept in OPS-SAT was the deployment of space software in the form of apps. The European Space Agency in collaboration with Graz University of Technology investigated and developed the NanoSat MO Framework.[30]
The NanoSat MO Framework (NMF) is a software framework for nanosatellites based on CCSDS Mission Operations services. It includes a Software Development Kit (SDK) to develop experiments as NMF Apps which can then be installed, started, and stopped in space. The framework also includes monitoring and control capabilities for the apps which will allow experimenters from the ground to take control of their software when it is running in space.[31]
The OPS-SAT system image comes with the NanoSat MO Framework which interfaces with all of the OPS-SAT payload systems and provides it in the form of services to the experimenter application. The NanoSat MO Framework allows simple integration of other libraries and applications. During the development of the experiments, the NMF SDK can be used and it includes a simulator, providing most of the platform functionalities accessible to the experimenter. The simulator allows developers to make their NMF Apps without the need to access an advanced satellite testbed hardware platform.
^ abMarszk, Dominik; Evans, David; Mladenov, Tom; Labrèche, Georges; Zelenevskiy, Vladimir; Shiradhonkar, Vasundhara (2022). MO Services and CFDP in Action on OPS-SAT. Small Satellite Conference. Retrieved 21 January 2024.
Launches are separated by dots ( • ), payloads by commas ( , ), multiple names for the same satellite by slashes ( / ). Crewed flights are underlined. Launch failures are marked with the † sign. Payloads deployed from other spacecraft are (enclosed in parentheses).
