Advanced Search
Search Results
112 total results found
Software Design
System description The two RFI Monitoring Payloads will have the same purpose: Detect any unexpected RF Signal (Interference) in their corresponding band, and to report them to ground to be further analyzed. In order to do that, the hardware in charge of doing...
Subsystem Description
Functional Architecture The communications subsystem is responsible for telecommand reception and telemetry transmission. Being so that the functionality of the satellite's control from the Earth ground station completely relies on the COMMS subsystem. Therefo...
Subsystem Verification Test - SSV
Test Description and Objectives The objective of this test is to validate the correct operations of the P/L2 L-band RFI monitoring payload board layout, the quality of the data acquisition process, as well as the deployment and operation metrics of the Helical...
Hardware Design
Design Choices Up next is provided a table including the most important components of the COMMS subsystem. In the following sections is found information about each one of them as well as the overall design of the system. Quick Facts Table Specification Va...
Subsystem Verification (SSV)
The purpose of this section is to conduct a complete test of the COMMS subsystem following the soldering of the board or after completing environmental tests. These tests are essential to ensure that the COMMS subsystem hardware is functioning as intended. The...
Software Design
COMMS Software is integrated within the MCU and designed as a state machine that transitions mainly due to the recival and transmission events. Most of the relevant code is encapsulated within the COMMS Task, in terms of FreeRTOS structure. The software is the...
Hardware Tests as Run
DOCUMENT SCOPE The aim of this document is to clearly explain the tests performed during the delevolpment of the subsystem. This document is based on current but also previous versions both of hardware and software and as such be followed with care. ANTENNA M...
Software Tests as Run
DOCUMENT SCOPE The aim of this document is to clearly explain the tests performed during the delevolpment of the subsystem. This document is based on current but also previous versions both of hardware and software and as such be followed with care. Tiny GS t...
Subsystem Description
Functional Architecture Conceptually, the On-board Computer (OBC) acts as the brain governing the spacecraft, serving as the central component within the overall architecture of this system. It plays a pivotal role in a complex system that accommodates the fol...
Hardware Design
Design Choices Up next is provided a table including the most important information of the OBC. In the following sections is found information about each one of them as well as the overall design of the system. Quick Facts Table Component Value Microco...
Software Design
Overview As introduced in the previous sections, the On-board Computer (OBC) is responsible for governing the entire spacecraft. Since only one microcontroller is used to control the various subsystems and GPIOs, it is crucial to ensure efficient and robust pe...
RFI-5G Mission Analysis and Requirements
Project description This project is performed as part of the IEEE Geoscience and Remote Sensing/Frequency Allocations in Remote Sensing (GRSS/FARS) Technical Committee project to monitor the spectrum with the 24 GHz water vapor band and the low part of the 5G ...
RFI-5G Payload block diagrams
FE Block Diagram Power Supply Block Diagram Signal Conditioning Block Diagram 4. General block diagram
Antenna Design
INTRODUCTION The goal of PoCat payload 3 is to identify Radio Frequency Interference (RFI) in the lower Ka-band (24-25 GHz). A patch antenna is chosen as the resonant element for its lightweight, 2D design, and reduced size due to the inverse frequency-wavelen...
Subsystem Verification (SSV)
The SSV of the OBC consists of two main components: hardware and software. Hardware Validation The hardware validation begins with an electrical check. The first step is to visually inspect the soldered board for marks, scratches, significant soldering errors,...
Tests as Run
DOCUMENT SCOPE The aim of this document is to clearly explain the tests performed during the delevolpment of the subsystem. This document is based on current but also previous versions both of hardware and software and as such be followed with care. TEST 1: E...
Data Acquisition
Parameters: struct rfi5gParameters{ char* name; uint32_t timestamp; uint32_t temperature; uint32_t startFrequency; } Constants General Constants #define N_SAMPLES 1000 #define NUM_FREQ 62 #define R 10 N_SAMPLES: Number of samples to capture in o...
EGSE - Wiring and Setup
The main objective of this section is to document and explain how to proceed with the wiring of the different parts of the EGSE to use it correctly. Additionally, it will explain the fundamentals for operating it properly. The EGSE does not have all the SSVs i...
EGSE - Design Specifications
Document scope This document specifies the electronic and mechanical aspects necessary to understand and operate the Electronic Ground Support Equipment. Specification and objectives of the EGSE are defined, as well as the board components and power modes avai...
COMMS Antenna deployer
Introduction The antenna deployment mechanism will consist of two elements: a dyneema string attached to the end of the COMMS antenna, and a low-impedance resistor mounted on a lateral board. The dyneema string will wrap around the satellite as illustrated in ...