Oryx is a modular flight software tool developed for the mission control of small satellites. It manages all satellite tasks – namely, processing telecommands sent by the operators, monitoring the power budget, executing pre-defined schedules, managing emergencies and handling data from all the sensors on board.

Oryx utilises a modular framework based on building blocks to support the rapid development of the mission’s software by using a vast library of components (e.g. logging, scheduling, testing and communication).

The on-board software exposes an API that can be accessed through Lua scripts, providing access to selected sensors and peripherals.

Oryx is part of the Smart Mission Ecosystem – hardware, software and AI-powered algorithms.

Oryx is built out of 3 key elements.

Development Tools – systems simulators and a suite of automated tests which enable comprehensive testing of the flight software either by running locally on the PC (using QEmu) or by connecting to the hardware engineering model (using the Oasis EGSE board).

Oasis EGSE – a single-board, CubeSat PC-104 compatible EGSE that serves as an interface between the PC-running simulators and the hardware engineering model. It enables the execution of integration tests, which use actual hardware connections between satellite components (I2C, CAN, UART, SPI).

The Software Development Kit (SDK) – a set of libraries written in C++ containing crucial on-board services for telemetry and telecommand, a hardware abstraction layer and a library of drivers for popular systems. The most important elements of the SDK are:

  • Scheduler – used to run scheduled and automated jobs that can be time-triggered or initiated by any other telemetry values. Furthermore, it is extensible with the Scripting Engine.
  • The Scripting Engine – a Lua-based service which enables the running of precompiled Lua scripts on board. All internal APIs are exposed to the Lua module to give the possibility of evolving the mission objective and automated jobs without the necessity of reuploading the entire flight software.
  • COMM Protocols – a set of libraries implementing CCSDS-compatible communication channels for telecommands and telemetry with built-in security.
  • The Drivers Library – a set of pre-existing drivers for popular nano- and small-satellite systems.

The following subsystems are currently supported off-the-shelf:

  • Leopard DPU by KP Labs
  • Antelope OBC by KP Labs
  • Kryten M3 by AAC Clyde Space
  • EPS (STARBUCK) + Batteries by AAC Clyde Space
  • ADCS by AAC Clyde Space
  • UHF Transceiver by CPUT
  • IMTQ by ISIS
  • ANT module by ISIS
  • uCam III camera module by 4D Systems
  • Q20 HD GPS by QinetiQ and all NMEA-based receivers
  • EWC27-SRX X/S Transceiver by Syrlinks

Customized drivers can be cretated for components that are not currently supported by Oryx.

The video below is a presentation by KP Labs from the 2021 satsearch webinar: "a guide to advanced data processing and AI for satellite missions". For more information about the webinar, and to see footage of the entire event, please click here here

The video below is footage of a live demo on KP Labs' flight software reliability and the company's Oryx OBCS with satsearch.

Disclaimer: satsearch is not responsible for any mistakes on this page, although we do our best to ensure correctness. Please report any mistakes to us.

Last updated: 2023-11-18

Oryx - Modular on-board software




lead time1
1 to 6 mo

1. Depending on customization requirements.


from our blog

Go to blog

An overview of on-board computer (OBC) systems available on the global space marketplace

Sun sensors - an overview of systems available on the global marketplace for space

S-band antennas on the global marketplace for space