One thing is clear. If you are going to put a small satellite into orbit, you need an on-board computer (OBC). In the same way that you can't drive a car without an engine, an OBC is a must for any CubeSat mission.
The on-board computer is essential for proper in-orbit operation. If something goes wrong in this area, the satellite will not be able to perform the mission for which it was designed. Therefore, before selecting an OBC for a CubeSat mission, it is necessary to have a thorough understanding of the needs of the project, assess the requirements to be met by the on-board computer and study the compatibility with the rest of the subsystems associated with the management of a small satellite.
We will begin by analysing the environment in which the OBC operates and its relationship with other key components in the operations phase. In this article, we will focus on the command and data management subsystem, which is considered to be the core of the satellite and relies on three elements that are essential to any mission:
- On-board computer (OBC). This is the brain of the satellite, responsible for processing mission commands and coordinating all other subsystems, including the payload.
- Telemetry, Tracking and Command (TTC). The function of the TTC is to allow communication to and from the satellite, as well as the control of certain parameters, such as the angular position, distance, or altitude of the CubeSat, which make it possible to detect if there has been any type of incident that affects its operation.
- Software. Responsible for the logic and programming of the satellite, whether on-board software (OBSW) or a software development kit (SDK) is used.
The integration of these three elements is a necessary part of the design, integration, verification and operation of any satellite.
What tasks are related to the command and data handling subsystem?
The command and data management subsystem performs many tasks critical to the proper functioning of the satellite, without which the CubeSat would not be able to fulfil its mission once in orbit.
Its main functions include the following:
- Sending information related to the satellite's internal management and payload.
- Receiving mission commands and transmitting them to the rest of the CubeSat subsystems.
- Processing telemetry and telecommand information.
- Controlling the time synchronisation of the satellite for communication with the ground station or with other satellites in the constellation.
- Managing the storage and processing of information on the satellite.
- Executing commands directly from mission control on the ground or via programmable lists
- Controlling all satellite subsystems, including the payload.
- Monitoring and managing the satellite thanks to the Fault Detection, Isolation, and Reconfiguration (FDIR) system, responsible for diagnostics and troubleshooting.
Photo: Shielding a command and data handling subsystem - Alén Space
Is it possible to integrate OBC, TTC and software in one single module?
The possibility of integrating the components that form the core of a satellite (OBC, TTC and software) into a single module can be an important aid to any mission. Shorter turnaround times, miniaturisation of electronic components and cost savings are the basis of the revolution that has come with small satellites. Every centimetre counts and every day that can be accelerated in the CubeSat development schedule is one day less taken to reach space.
Therefore, the integration in a single product of all these elements related to the command and data management subsystem, with all that this implies, is relevant:
- Reduced development time. While integration with other parts of the satellite (platform, payload, etc.) will be necessary, having an all-in-one solution for the command and data management subsystem saves time in the design and assembly, integration and verification phases (AIV).
- Less volume and mass. Integration means space savings in the hardware and let's not forget that in a CubeSat everything has to be measured to the millimetre.
- Lower cost. This factor is closely related to the previous points: a shorter development time and a reduction in the volume and mass of the satellite can have a direct impact on the costs associated with its development and launch.
- Increased reliability. A seamless interoperability solution between the OBC and the TTC is desirable, thanks to a joint design of these components and the inclusion of FDIR system (Fault Discovery, Isolation and Recovery) to safeguard the integrity of the entire satellite.
In a satellite, the on-board computer must control all other subsystems. To achieve this, seamless integration is required, which must be done mechanically with programming interfaces, communication protocols and software. The use of standards, such as ECSS, can facilitate the design and integration phases, but full verification will always be necessary to ensure the correct functioning of the whole system.
As we have just seen, it is now possible to have this guaranteed through a product that integrates everything in a single module. These solutions fit perfectly with the needs of most CubeSat missions, which seek to miniaturise their components, accelerate satellite development, and economise costs as much as possible.
How does the all-in-one TRISKEL solution work?
When selecting the essential components of a small satellite, several factors and constraints are taken into account, but the key is to maintain compatibility between the different subsystems.
With TRISKEL, Alén Space provides a Plug-and-Play (PnP) product which integrates OBC, TTC and, optionally, an SDK for developing software on its own or an OBSW based on the Packet Utilization Standard (PUS) of the European Space Agency (ESA) on a single motherboard. It is a solution that avoids compatibility problems between suppliers and is perfectly adapted to different types of projects, without the need for extra configurations.
Photo: TRISKEL - OBC, TTC and OBSW in one single module
As the on-board computer is a key component in the operation of a CubeSat, it must be carefully selected to be compatible with the rest of the subsystems. In this respect, TRISKEL provides an optimal solution that brings together the most essential systems in a single hardware. Would you like to know more?
