How adam-kabbara/rsx-cansat-2025 works
Main Components
• Hardware (Circuit Designs and PCBs): This includes all KiCad projects – your custom symbols, footprints, 3D models, and the various PCB boards (Buzzer, CanSat Sensor Board, CanSat Camera Board, Power Management). Represent this section as a “Hardware/Electronic Designs” module.
• Firmware & Sensor Setup: In folders such as full_sensor_setup, sensor_testing (with subprojects for Arduino sketches, PlatformIO projects for ESP32, etc.), and telemetry_source. These pieces represent your embedded code that interfaces directly with the sensors and actuators.
• Ground Station Software: Located in ground_station_source. This is a separate desktop application (with a .msi installer and an executable) meant to connect via a communication port for monitoring CanSat telemetry.
• Calculations/Simulations: The calculations folder (with Jupyter Notebooks) can be depicted as the analytical or simulation layer to validate or analyze sensor data and performance.
• Communication/Telemetry: The telemetry_source component likely handles the routing, formatting, and possibly pre-processing of sensor data before it is transmitted to the ground station.
Relationships and Interactions
• The “Hardware/Electronic Designs” layer acts as the foundation by providing PCB designs that integrate sensors, microcontrollers, and power management circuits.
• The firmware projects (in full_sensor_setup, sensor_testing, telemetry_source and other ESP32/Arduino projects) run on the various hardware modules. They read sensor data, control actuators, and communicate wirelessly (or via serial/USB) with the ground station.
• The ground station software receives telemetry information (likely via a wireless or serial connection) and displays or processes the sensor data.
• The calculations layer supports simulation/analysis that might validate sensor performance or support design decisions.
Architectural Patterns and Design Principles
• Modularity: Each major subsystem (circuit designs, firmware, ground station) is organized into its own folder, which reflects a modular design concept.
• Separation of Concerns: The repository clearly separates hardware designs from firmware and from user-facing software, which is a best practice in system architecture.
• Iterative Development: The presence of different sensor testing setups, backups of PCB projects, and multiple versions of test code indicates an iterative, experimental approach to hardware-software integration.
• Standardized Tooling: Use of KiCad for hardware design and PlatformIO/Arduino for firmware, as well as Python for the GUI, which helps keep environments consistent and maintainable.
Relevant Technologies, Frameworks, or Libraries
• KiCad – for PCB design (schematics, footprints, 3D models, Gerber files).
• Arduino/PlatformIO – for developing microcontroller firmware targeting ESP32 and possibly other boards.
• Python (with a requirements.txt and setup.py in the ground station folder) – for the ground station GUI.
• Jupyter Notebook – used in the calculations directory for analysis and simulation.
• Communication interfaces such as serial and possibly wireless (related to telemetry).
Final Recommendation
Hardware/Design → Firmware/Data Acquisition → Telemetry/Data Processing → Ground Station Display/Control