Generalized onboard/internal command and messaging framework
-
Project and Master Subjects 2026-2027
- GNSS-R: GNSS jamming and spoofing detection and localization from space
- GNSS-R: Maritime surveilance with GNSS-R
- GNSS-R/GNSS-RFI Embedded system and processing pipeline
- Software system for new smallsat camera systems
- Automatic gain control for RF front end on GNSS RFI satellite payload
- Deployment of a telescope onboard a CubeSat
- Maritime Surveillance form Space: On-board ship-detection with an RGB camera on HYPSO2
- Generalized onboard/internal command and messaging framework
- Define a CubeSat bus architecture for a GNSS RFI mission
- Energy Budgeting for Dynamic Targeting
- Dynamic image target generation for the HYPSO satellites
- Design and Testing of a Strobing Illumination System for an Underwater Hyperspectral Camera
- LEO SatCom Signals of Opportunity for positioning, navigation and timing (PNT)
- yr.no for GNSS: Real-time service providing GNSS interference coverage
- Past Projects
Generalized onboard/internal command and messaging framework
Project description
For sending commands to the payload of our satellites (HYPSO-1 and HYPSO-2), we use our own specifically designed tools. One of them is a command line interface (CLI) that translates text-based human readable input to binary data messages and transmits them via a connected interface. This tool has served us well, but it is also constrained and unflexible in certain regards. We need better frameworks for exchanging data between sub-systems (or between processes in one sub-system) to increase autonomy and operational efficiency.
Example limitations of our existing tools are: They do not allow us to translate the human readable text commands to binary messages, without also sending them via some interface at the same time. In addition, we would like to be able to exchange underlying protocols without much effort. In our case, going from CSP1.0 (Cubesat Space Protocol) to CSP2.0 or LSTS IMC is not currently possible without modifying code in a lot of places.
Tasks and expected outcomes
This project is about designing and implementing a new, more modular, software framework to replace our existing tools. This task has a large amount of creative design freedom, while being informed by the requirements of the SmallSat Lab. Example taks:
- Define a framework that can extend the hypso-cli
- Example problem: converting hypso-cli to CSP2.0 would require a lot of small and repetitive code changes. This is because the command set is not implemented modularly enough.Therefore, the architecture should be improved first.
- Look into alternatives (e.g. LSTS IMC, ROS2, IMCpy)
Who we are looking for
We are seeking a highly motivated final year student in Electronics, Cybernetics or a related field with an interest in digital systems and design, embedded systems, computer systems and similar.
The student should be OK with spending most of their time on research and coding and only a small degree of hands-on activities with electronic hardware. The student will work in close collaboration with the scientific staff and existing infrastructure at the NTNU SmallSat Lab.
How we work
The student will be part of the NTNU SmallSat lab, a lab which typically hosts 10-20 master's student per semester. At the NTNU SmallSat Lab we encourage collaboration and try to get our group to help each other. To facilitate this, we as well as arrange common lunches and workshops where the students and supervisors can learn from each other. In some project we also implement a development process.
Contact: Dennis Langer