Differences
This shows you the differences between two versions of the page.
|
pm:prj2026:bianca.popa1106:darius.constantin04 [2026/05/25 03:07] darius.constantin04 [Hardware Design] |
pm:prj2026:bianca.popa1106:darius.constantin04 [2026/05/25 06:25] (current) darius.constantin04 [References & Bibliography] |
||
|---|---|---|---|
| Line 47: | Line 47: | ||
| ====== Software Design (Firmware) ====== | ====== Software Design (Firmware) ====== | ||
| + | [[https://github.com/Darius-Constantin/Artemis3|GitHub]] | ||
| ===== Development Environment ===== | ===== Development Environment ===== | ||
| The firmware for both the Base Station (Launch Controller) and the Rocket Payload (Flight Computer) is developed using **PlatformIO** running on the Arduino framework. This environment was chosen because it easily manages cross-architecture compilation. PlatformIO’s ''platformio.ini'' configuration files allow for strict library dependency tracking and custom build flags (such as enabling hardware USB CDC on the C3 chip) without manual makefiles. | The firmware for both the Base Station (Launch Controller) and the Rocket Payload (Flight Computer) is developed using **PlatformIO** running on the Arduino framework. This environment was chosen because it easily manages cross-architecture compilation. PlatformIO’s ''platformio.ini'' configuration files allow for strict library dependency tracking and custom build flags (such as enabling hardware USB CDC on the C3 chip) without manual makefiles. | ||
| Line 87: | Line 88: | ||
| ===== Results ===== | ===== Results ===== | ||
| + | The development of the Dual-ESP32 Telemetry and Launch System resulted in a highly robust electronic and software architecture. While the project faced significant challenges regarding cross-architecture RF compatibility and mechanical physics, the core objective of building a real-time, bidirectional aerospace tether was successfully achieved. | ||
| + | |||
| + | ===== 1. RF Link and Telemetry (Bluetooth Low Energy) ===== | ||
| + | Initially, the system was designed around the ESP-NOW protocol. However, extensive bare-metal hardware testing revealed a physical incompatibility and transmit amplifier limitation on the ESP32-C3 Supermini's architecture when communicating with the base station. | ||
| + | By pivoting to a Bluetooth Low Energy client-server architecture, the system achieved a tethered connection. The Base Station successfully scans the 2.4GHz spectrum, automatically pairs with the "KINDER_ROCKET" payload upon power-up, and maintains a stable connection capable of receiving continuous 4-byte float altitude updates without dropping packets. | ||
| + | |||
| + | ===== 2. Payload and Power Systems ===== | ||
| + | The severe size and weight constraints of the Kinder egg capsule required a custom power delivery solution. Standard coin cells failed to deliver the 300mA burst current required by the BLE radio, triggering the ESP32's brownout detector. | ||
| + | This was overcome by engineering a custom stacked LR44 alkaline battery pack wrapped under high vinyl tension. This solution successfully maintained a stable 4.5V supply to the payload's voltage regulator, ensuring the BMP280 barometric sensor and BLE transmitter remained powered even during high-frequency data transmission. | ||
| + | |||
| + | ===== 3. Base Station and FSM Execution ===== | ||
| + | The Base Station's Finite State Machine (FSM) executed perfectly during testing. | ||
| + | * **Dynamic UI:** The IPS display accurately transitioned through the ''SCANNING'', ''HOLD'', ''T-Minus'', and ''FLIGHT'' states based on both BLE connection status and physical switch inputs. | ||
| + | * **Abort Logic:** The MPU6050 accelerometer, paired with the Exponential Moving Average (EMA) low-pass filter, successfully ignored the high-frequency vibration of the haptic countdown motor. It only triggered the ''ABORT'' state when the launch pad experienced genuine, heavy physical disruption. | ||
| + | |||
| + | ===== 4. Mechanical Launch & Simulated Flight Testing ===== | ||
| + | Due to timeline constraints and the physical phenomenon of spring buckling, the mechanical spring-loaded silo was not finalized in time for a kinetic launch. The extreme compression required for the payload caused the spring to deflect laterally against the curved base of the Kinder capsule. | ||
| + | |||
| + | However, the complete software and telemetry stack was successfully validated. | ||
| + | By arming the Base Station and manually launching the Kinder egg payload by hand (throwing it vertically to simulate the flight profile), the laucnh sequence was executed flawlessly. | ||
| ===== Conclusions ===== | ===== Conclusions ===== | ||
| + | The electronic architecture, RF communication, and mission software are 100% flight-ready, laying a robust foundation for future mechanical launcher iterations. | ||
| ===== References & Bibliography ===== | ===== References & Bibliography ===== | ||
| + | [[https://github.com/orgs/micropython/discussions/15455|This GitHub issue]] was particularly revealing that most ESP32-C3 Superminis suffer from poor antenna construction, potentially the reason why ESP-NOW did not behave as expected. | ||
