Control Number: 202511
Indiana Aerospace University
Department of Aerospace Engineering
IAU Town Center, Lapu-Lapu City, Cebu, Philippines 6015
Philippine Can Satellite Rocket Competition 2025
CanSat + Rocket Category
Critical Design Review (CDR)
Real-Time Can-Satellite Landing Prediction
Members:
Jarabe, Ceilla Maria N.
Orbiso, Christian Phil B.
Pastrano, Royce Judill D.
Pogoy, Khim Prospher C.
Revelo, Joshua C.
Ucat, Karl Hendrix M.
1
TABLE OF CONTENTS
I.
Introduction
i.
II.
III.
IV.
V.
VI.
VII.
VIII.
IX.
Team Organization and Roles
Mission Overview
i.
Rocket Mission
ii.
Primary Mission
iii.
Secondary Mission
Project Planning
Rocket Design
i.
Rocket Structural Design
ii.
Electrical Design
iii.
Software Design
iv.
Recovery Design
CanSat Design
i.
CanSat Structural Design
ii.
Electrical Design
iii.
Software Design
iv.
Recovery Design
Testing
Detailed Budget
Outreach Conducted
Progress Report
2
I.
Introduction
This Critical Design Review (CDR) documents the Aromaz team's design and mission plans for the
Philippine Can Satellite Rocket Competition 2025. It details team organization, roles, and the
development of the Aromaz rocket and CanSat. The CDR presents mission objectives, design
specifications, initial testing results, and budget. It serves to ensure project adherence during the
competition.
i.
Team Organization and Roles
The Aromaz team is divided into the Rocket and CanSat Teams. The Rocket Team designs and
builds the rocket using composite materials, and develops the rocket's recovery systems. The
CanSat Team manages the CanSat's internal and external systems, including PCB design,
programming, testing, parachute system oversight, and 3D modeling of the main CanSat
structure.
Figure 1. Organizational Chart
3
II.
Mission Overview
The CanSat's mission is to replicate the functions of a real satellite. It must incorporate essential
satellite components such as power systems, sensors, and a communication system. The Aromaz
rocket serves as the launch vehicle for the CanSat, utilizing a specially designed rocket motor
developed by the IAU AE Research and Development Team. Ensuring the CanSat fits within the
rocket's payload section and that both the drogue and main parachutes are correctly sized is
crucial for a safe and controlled recovery.
Mission success is defined by:
a.
b.
c.
d.
e.
f.
Ensure successful descent of the CanSat without damaging internal sensors.
Log sensor data accurately onto the SD card for post-analysis.
Deploy the nose cone chute, CanSat, and drogue parachute at rocket apogee.
Deploy the main parachute at 800 feet during descent.
Execute CanSat ejection via the flight computer.
Achieve safe recovery of the CanSat post-mission.
i.
Rocket Mission
The Aromaz rocket features a timer-based ejection system managed by the flight computer,
which arms the ejection system at an altitude of 300 feet. This is achieved through a timer set to
approximately 11.9 seconds, based on optimal delay simulations, though a 10-second timer can
also be utilized as an estimate. The flight computer continuously monitors the rocket's altitude
using data from the MS5611 pressure sensor, which plays a critical role in determining when to
initiate the ejection sequence by influencing the timer's activation.
The MS5611 pressure sensor (see Table 1) provides real-time altitude data, ensuring precise
timing for the ejection process. According to OpenRocket simulation data, the rocket undergoes
powered flight, reaching approximately 346 feet (105 meters) before transitioning into coasting
flight. During this phase, it continues to ascend until it reaches apogee—the highest point in its
trajectory. At apogee, the nose cone parachute deploys, ejecting the CanSat with its bright green
parachute for easy identification during descent. Shortly after the nose cone deployment, the
drogue chute is released to stabilize the rocket's descent.
To ensure a safe recovery of all structural components, the rocket's main parachute is ejected at
an altitude of 800 feet during descent. This sequence is carefully designed to protect the rocket's
integrity and ensure its reusability. The CanSat and rocket descend separately, with the CanSat
equipped with its parachute system for independent landing. The rocket recovery system uses
orange parachutes for clear differentiation from the CanSat's bright green parachute.
4
Figure 2. Rocket Mission Phases
i.
Primary Mission
The CanSat's primary mission is to gather atmospheric pressure, altitude, temperature, and GPS
coordinates. It also monitors the SD-Card Module's status and logs elapsed time since activation.
This data acquisition is achieved through integrated sensors, including the MS5611 pressure
sensor, a temperature sensor (NTC Thermistor), and a GPS module, managed by the Teensy 4.0
microcontroller (see Table 1 for a list of primary mission components). The sensors were carefully
selected to fit the CanSat. The Teensy 4.0 was selected due to its memory capabilities, which are
suitable for both the primary and secondary missions. Initial testing determined that the Arduino
Nano had limited memory, and the ESP32 Module would require too much space. The structural
design, as seen in Figure 11, ensures that these components are securely packed inside the
CanSat's allocated volume. The data will be logged onto the SD Card for competition rules but is
readily transmitted via the HC-12 Module. The logged data can be used for troubleshooting and
to check for accuracy.
5
Table 1. Primary Mission Components
Item
1.
2.
3.
4.
Description
Figure
Function
The Teensy 4.0 serves as
the CanSat's central
microcontroller, managing
sensor data acquisition,
data logging, and
communication with the
ground station.
Teensy 4.0
The HC-12 module
provides reliable, longrange wireless
communication between
the CanSat and the ground
station for real-time data
transmission.
HC-12 Transceiver
The NTC thermistor
measures temperature by
exhibiting a negative
temperature coefficient,
decreasing resistance as
temperature increases.
NTC Thermistor
The MS5611 provides
essential atmospheric
data, simultaneously
measuring temperature,
and pressure, and
calculating altitude for
environmental monitoring.
MS5611 Pressure
Sensor
6
5.
6.
7.
8.
Micro SD-Card
Module
The Micro SD Card Module
provides non-volatile
storage, enabling the
microcontroller to record
sensor data and other
mission-critical
information for later
retrieval.
GT-U7 GPS
Module
The GT-U7 GPS Module
provides the CanSat with
accurate latitude and
longitude coordinates for
location tracking using
GNSS satellite signals.
Buzzer
The buzzer generates
auditory signals for
various alerts, status
indications, and signals
CanSat's data
transmission, aiding in
locating the rocket postlanding.
LED
The LED serves as a visual
indicator, emitting light to
signal specific states or
events within the CanSat
system, and also acts as
an indicator of altitude
post-flight.
7
ii.
Secondary Mission
The CanSat Landing Prediction UI serves as the ground station interface for the secondary mission
of real-time landing prediction. The system processes telemetry data through serial
communication at a baud rate of 2400 to predict the CanSat’s next position. The UI displays
mission-critical data in three main sections. The header shows real-time mission parameters
including pressure, temperature, speed, and elapsed time. The main content area uses a threecolumn layout for data visualization. Column 1 shows 3D orientation and GPS mapping. Column
2 displays sensor telemetry and GPS coordinates. Column 3 features the 3D flight path with a
predicted trajectory.
The system processes two data streams from the CanSat sensors. Environmental data comes
from the MS5611 pressure sensor (0-2000 hPa, -1000 to 10000m altitude) and GPS module (±90°
latitude, ±180° longitude). Motion data is provided by the MPU6050, measuring acceleration
(±20g) and rotation (±2000°/s) across three axes.
The system includes error handling, data validation, and connection monitoring features. It
maintains a rolling buffer of 100 data points for prediction calculations and can export data for
post-mission analysis.
The UI features a dark theme for optimal visibility and includes system control functions such as
data saving, system checks, and connection management through an intuitive button interface
in the bottom footer. Wind data can be input manually through a dedicated panel, with a visual
compass indicator for direction reference.
Table 2. Secondary Mission Component
Item
1.
Description
Figure
Function
The MPU6050 is an
IMU providing
acceleration data
along the X, Y, and Z
axes, as well as
gyroscope data for
angular rates
around the X, Y, and
Z axes.
MPU6050
8
Figure 3. CanSat Landing Prediction UI
The algorithm employs a sophisticated physics-based approach to calculate the expected landing
location during descent. The system utilizes fundamental physical constants including
gravitational acceleration (g = 9.81 m/s²) and air density (ρ = 1.225 kg/m³ at sea level), combined
with the CanSat's specific parameters: mass of 350g, height of 115mm, and diameter of 66mm.
Critical to the calculation is the drag coefficients of both the CanSat body (𝐶𝑑 = 0.47) and its
parachute (𝐶𝑑 = 1.5), along with their respective cross-sectional areas of 0.003419 m² (CanSat
area) and 0.07624 m² (parachute area).
The algorithm begins by calculating the terminal velocity, which is derived from the equilibrium
of gravitational
and
drag
forces.
This calculation uses the
force
balance
1
equation where mg equals the drag force (2 𝜌𝑣²𝐶𝑑 𝐴). The terminal velocity equation is solved
2𝑚𝑔
as 𝑣 = √𝜌𝐴𝐶 ,
incorporating both the
𝑑
CanSat
and
parachute
drag characteristics.
This terminal velocity serves as a crucial parameter in the descent predictions.
The trajectory prediction implements a time-stepped numerical integration approach with 0.1second intervals. At each time step, the algorithm calculates the total drag force using the
1
equation 𝐹 = 2 𝜌𝑣 2 (𝐶𝑑1 𝐴1 + 𝐶𝑑 2 𝐴2 ), where the subscripts denote the CanSat and parachute
parameters respectively.
This force is
then
9
converted
to
acceleration components,
incorporating wind effects through vector addition of wind velocity components (𝑣𝑥 = 𝑣𝑤𝑖𝑛𝑑 ∗
cos(𝜃) , 𝑣𝑦 = 𝑣𝑤𝑖𝑛𝑑 ∗ sin(𝜃)).
Position updates are calculated using standard kinematic equations, where new positions are
1
determined by 𝑥 = 𝑥0 + 𝑣𝑥 ∗ ∆𝑡 + 2 ∗ 𝑎𝑥 ∗ ∆𝑡 2 ,
1
𝑦 = 𝑦0 + 𝑣𝑦 ∗ ∆𝑡 + 2 ∗ 𝑎𝑦 ∗ ∆𝑡 2 ,
and 𝑧 = 𝑧 0 – 𝑣𝑡 ∗ ∆𝑡 for the vertical component. The algorithm processes real-time input data
from multiple sources: GPS coordinates provide the current position, the MPU6050
supplies acceleration and rotation data, and the MS5611 provides pressure and altitude
measurements. Wind parameters are manually input and integrated into the calculations.
The prediction system maintains accuracy through several mechanisms. It uses a rolling buffer of
100 data points for smoothing and validation, updates predictions every 3 seconds, and accounts
for various error sources including GPS accuracy (±2.5m), wind measurement uncertainty, and
atmospheric variations. This comprehensive approach enables real-time trajectory updates while
balancing computational efficiency with prediction accuracy. The mathematical model's
reliability is enhanced by continuous validation against actual descent data, allowing for real-time
refinement of the landing prediction.
III.
Project Planning
The project commenced with the design of the rocket using OpenRocket software, followed by
the fabrication of components from composites. Initial testing of the CanSat components was
conducted at the end of 2024, with a specific focus on integrating the Arduino Nano. It became
evident that the Arduino code scripts designated for the primary mission, when combined with
the DMP scripts for the MPU6050, exceeded the memory capacity of the Arduino Nano.
Consequently, a decision was made to transition to the Teensy 4.0 microcontroller, which offered
enhanced memory capabilities.
Table 3. Project Timeline
Phase
Timeline
Key Deliverables
Rocket Design &
Fabrication
Sept-Oct
2024
Material selection, final OpenRocket design, and
initial composite molds.
CanSat Preliminary
Design
Nov-Dec
2024
Operational breadboard integration of
components and the initial concept for the
secondary mission.
10
CanSat Early Testing
Jan-Feb
2025
The initial PCB to test the new components,
involving the Teensy 4.0, and the initial secondary
mission testing
Rocket Manufacturing
Sept 2024Feb 2025
Assembly of rocket components, decals, and
recovery system.
CanSat Finalization
Jan-Mar
2025
Final CanSat PCB and CanSat Structure.
CanSat Ground Testing
Feb-Mar
2025
Initial CanSat data.
Finalization of Landing
Prediction Algorithm
Mar-Apr
2025
Operational Python UI
Rocket & CanSat Launch
TBD
Flight test, data collection, and evaluation of
mission success criteria.
Post-Flight Data Analysis
& Reporting
TBD
Data processing and flight performance
assessment
IV.
Rocket Design
The Aromaz rocket was first designed in OpenRocket, a free, fully featured model rocket
simulator that enables the design and simulation of rockets before building and launching them.
The nose cone is 3D printed with PLA filament, ensuring lightweight and durable construction.
The upper and lower body tubes, along with the rocket fins, are fabricated from composite
materials. Additionally, the avionics bay is also 3D printed. The composite structures are then
smoothened by varying grits of sandpaper, with the application of body filler to remove any
uneven textures that can affect the rocket’s aerodynamics.
i. Rocket Structural Design
The design constraints for the Aromaz rocket specify a total mass of less than 5.5 kg, including
the motors, and require a stability margin of 1.3 to 1.7. The specific weights of the components
11
are as follows: the nose cone weighs 250 g, the lower body tube is 480 g, the upper body tube is
350 g, and the avionics bay has a mass of 670 g.
The nose cone is an ogival shape, with a shoulder that fits it to the upper body tube. The shoulder
must have the same diameter as the inner diameter of the upper body tube. A buzzer will also
be fitted inside the nose cone, and a parachute, which assist in recovery. It is then connected to
the upper body tube (55cm), which is slightly smaller than the lower body tube (80cm). Inside
the upper body tube are the CanSat, two pistons, and the drogue chute. When the ejection
system activates, it pushes on these pistons, which start the sequence of the nose cone chute
deploying, then the ejection of the CanSat, and then the deployment of the drogue chute. At the
center is the avionics bay. It is designed so that the structure contains a tube coupler, which
allows the lower and upper body tubes to join. Inside the avionics bay, is the rocket’s flight
computer controlling the ejection system.
Figure 4. Rocket Design (a) Finished 3D View, (b) Skeleton View
The lower body tube contains the main parachute. The parachute will be pushed out and
deployed using two pistons near the inner tube. The inner tube is where the rocket motor setup
will be fitted. It is secured to the lower body tube using two 3D-printed centering rings, where
the outer diameter is the inner diameter of the lower body tube. The distance between the two
centering rings is where the shoulder for the rocket fins will be placed.
12
(a) Body Tube
(b) Avionics Bay
(c) Nose Cone
(d) Lower Body Tube
Figure 5. Rocket Structure
The OpenRocket analysis places the CP (131cm) near the motor and the CG (114cm) in
the lower body tube. The design meets the 5.5 kg weight limit (weight with motor is 5324 g) and
has a stability margin of 1.52 (within the 1.3-1.7 range). Simulations in OpenRocket as shown in
Figure 5 use a 998 Ns impulse motor to estimate an apogee of 951 meters, a max velocity of 180
m/s, and a max acceleration of 179 m/s². The simulated time to apogee is 13.3 seconds, with an
optimal delay of 11.9 seconds and a total flight time of 73.3 seconds.
(a) Vertical Motion vs. Time
(b) Stability vs. Time
Figure 6. OpenRocket Simulations
13
ii.
Electrical Design
The flight computer, designed in EasyEDA, is responsible for the core functionality of the reliable
triggering of the rocket's ejection system sequence. It manages power distribution to all onboard
components, handles data transmission from sensors, and activates the mechanisms for
parachute deployment. The main microcontroller is the ESP32 Module, which is powered by a
power setup similar to the CanSat.
The ESP32 monitors the altitude using the MS5611 and uses its on-chip flash memory to save
data without the need for an external SD Card Module. It controls the ejection system using four
terminal blocks, where the top two eject the nose cone chute, CanSat, and the drogue chute. The
bottom two handle the ejection of the main parachute. This is possible by the use of transistors,
which allow the flight computer to selectively activate the ejection charges at the appropriate
times during the flight by acting as switches that control the current flowing to those charges.
Figure 7. Flight Computer (a) PCB Layout, (b) Fabricated PCB
14
Figure 8. Flight Computer Schematic
Table 4. Flight Computer Components
Item
Description
1.
ESP32 Module
The main microcontroller for the flight
computer.
MS5611 Pressure
Sensor
It measures temperature by using an onchip temperature sensor to compensate
for temperature-dependent variations in
the pressure signal.
3.
LED
A small semiconductor device that emits
light when current flows through it, is
used as an indicator.
4.
Buzzer
Produces alerts and auditory signals.
2.
Figure
15
Function
5.
Amplifies electrical signals to higher
values.
Transistor
Table 5. Power Setup Components
Item
Description
Figure
Function
1.
Capacitor
Smooth out voltage fluctuations and
potential noise.
2.
L7805CV Voltage
Regulator
Steps down the battery voltage to a
steady 5V.
3.
Terminal Block
Connects the flight computer to the
external ejection systems, and the
battery.
4.
Diode
Protects the circuit from reverse
polarity.
iii.
Software Design
The main microcontroller for the flight computer is the ESP32 Module. The flight computer will
have various phases corresponding to the state of the mission. Before launch, the flight computer
will be in its initial state, recording and saving data, while the MS5611 continually monitors
altitude. As the rocket reaches 300ft, it begins the timer. This can use a function like millis which
is a non-blocking way for the microcontroller to track time.
Once the timer ends, the ejection system is activated, where two transistors amplify the signal
to their respective terminal blocks, the two at the top. These are then connected to the ejection
charges, which eject the nose cone chute, the CanSat, and the drogue chute. At this point, the
rocket has reached apogee, and will then start to descend, thus the need for deployment of the
parachutes. The flight computer keeps monitoring the altitude again. Once the rocket descends
to 800 feet, the same process occurs but for the bottom two terminal blocks.
16
Figure 9. Flight Computer Flowchart
iv.
Recovery Design
The recovery system is designed to ensure a steady descent of the rocket components following
deployment. It incorporates parachutes strategically located in the nose cone and both the upper
and lower body tubes, facilitating a safe recovery of all parts.
a. Main Parachute Calculations
Main Chute Diameter
Lower Body Tube = 1253 g
Avionics Bay = 464 g
Launch Lug = 6 g
Centering Ring = 80 g
Motor Nozzle = 247 g
Rocket Piston = 110 g
Motor Bulkhead = 200 g
17
Aluminum Casing = 490 g
SRM Holder= 130 g
→ Total= 3000g
𝐷=√
8(9.80065)(3)
3.2808𝑓𝑡
=
0.3192620903𝑚
∗
= 1.047447836 ft
(1.225)(1.5)(20)2 𝜋
1𝑚
𝐷 = 1.047447836 + (1.047447836 ∗ (0.20)) = 𝟏. 𝟐𝟓𝟔𝟗𝟑𝟕𝟒𝟎𝟒 𝐟𝐭
Spill Hole & Parachute String
𝑆𝑝 = 1.256937404 ∗ (0.2) = 𝟎. 𝟐𝟓𝟏𝟑𝟖𝟕𝟒𝟖𝟎𝟖 𝐟𝐭
𝑃 𝑠𝑡𝑟 = 1.256937404 ∗ (1.5) = 𝟏. 𝟖𝟖𝟓𝟒𝟎𝟔𝟏𝟎𝟓 𝐟𝐭
b. Drogue Chute Calculations
Drogue Chute Diameter
Ejection System = 334 g
Lower = 340g
→ Total = 674g
8(9.80065)(0.674)
3.2808ft
D=√
=
0.1513270875m
∗
= 0.4964799619 ft
(1.225)(1.5)(20)2 π
1m
D = 0.4964799619 + (0.4964799619 ∗ (0.20)) = 𝟎. 𝟓𝟗𝟓𝟕𝟕𝟓𝟗𝟓𝟒 𝐟𝐭
Spill Hole & Parachute String
𝑆𝑝 = 0.595775954 ∗ (0.2) = 𝟎. 𝟏𝟏𝟗𝟏𝟓𝟓𝟏𝟗𝟎𝟖 𝐟𝐭
𝑃 𝑠𝑡𝑟 = 0.595775954 * (1.5) = 0.893663931 ft
c. Nose Cone Parachute Calculations
Nose Cone Chute Diameter
Nose Cone = 234 g
D=√
8(9.80065)(0.234)
3.2808ft
= 0.08580115684 m ∗
= 0.2814998674 ft
2
(1.225)(1.5)(20) π
1m
𝐷 = 0.2814998674 + (0.2814998674 ∗ (0.20)) = 𝟎. 𝟑𝟑𝟕𝟕𝟗𝟗𝟖𝟒𝟎𝟗 𝐟𝐭
18
Spill Hole & Parachute String
𝑆𝑝 = 0.3377998409 ∗ (0.2) = 𝟎. 𝟎𝟔𝟕𝟓𝟓𝟗𝟗𝟔𝟖𝟏𝟖 𝐟𝐭
𝑃 𝑠𝑡𝑟 = 0.3377998409 ∗ (1.5) = 𝟎. 𝟓𝟐𝟔𝟓𝟔𝟓𝟐𝟔𝟖𝐟𝐭
(a) Nose Cone
(b) Upper Body Tube
(c) Lower Body Tube
Figure 10. Rocket Parachutes
V.
CanSat Design
The CanSat structure was modeled using Fusion 360, where all the 3D-printed parts were
modeled. The first step was to follow the design constraints per the ESA guidelines, which is to
fit all the components in the size of a standard soda can (115mm height and 66mm diameter).
i. CanSat Structural Design
The structure features a PLA-printed outer shell and an inner compartment. The outer shell’s
inner diameter is enough that the inner compartment can slide inside it. At the top, there are
two holes where two screws with washers can lock the inner compartment to the outer shell.
Inside the inner shell is the CanSat PCB. The PCB will be screwed onto the inner compartment by
drilling holes and fitting screws in them.
At the back is where the Li-Ion battery will be placed. Four clamps hold the battery in place. The
bottom of the inner compartment is a rectangle-shaped hole which is where the wires connected
to the terminal block pass through to access the battery and switch. The switch is locked in an
equal-sized rectangle at the bottom of the structure, where the switch is pushed up enough that
any force from the bottom cannot hit the switch and accidentally turn the CanSat off. The top of
the inner compartment is where the GT-U7 antenna will be secured.
The top of the outer shell features four holes where the parachute string can pass through. It
has enough space to tie the paracord using cable ties to make sure the CanSat does not swing
too much during descent.
19
(a) CanSat Sizing
(b) Cross Section
(c) PCB View
Figure 11. CanSat Structural Design
Figure 12. Structure Isometric View
20
(d) Battery Pack
ii.
Electrical Design
The CanSat’s PCB was designed in EasyEDA. The design features connections on the top and
bottom layers of the PCB. This is to centralize the MPU6050 on the PCB and arrange the sensors
accordingly without the concern of hard connections if it is limited to the bottom layer only. The
CanSat will utilize a power setup connected to the Li-Io battery. This is done by the use of a
terminal block. It is connected to two 0.33uF capacitors and an L7805CV voltage regulator. This
powers the CanSat but also supplies clean 5V power directly to the HC-12 Transceiver.
Figure 13. Can-Satellite Circuit Diagram Layout
Figure 14. CanSat Block Diagram
21
iii.
Software Design
The CanSat is fitted with the Teensy 4.0 as its main microcontroller. The team opted to use this
model as the Teensy is smaller than the Arduino Nano, with more GPIO pins, and a higher flash
memory. This ensures that the main CanSat script does not exceed the memory of the
microcontroller, which would render it unable to program.
The CanSat will have two main phases, the initialization and loop phase. The initialization phase
is where it checks the status of all the sensors fitted. This ensures that the Teensy can read data
sufficiently while transmitting the data and logging it at the same time. The loop phase is where
the Teensy continually reads from the sensors. The HC-12 Module will utilize a baud rate of 2400
to balance the range (at least 1km) with transmission speed. Initial tests conducted showed that
using a baud of 1200 would induce the data to “fall behind” with the transmission rate. This
indicates that despite the added range, the transmission rate would be too slow, and can also
induce errors for the Python UI.
The importance of the initialization phase is that it halts the programming if one sensor does not
initialize correctly. The CanSat reads data only after these checks.
Figure 15. CanSat Main Flowchart
22
iv.
Recovery Design
To recover the CanSat after deployment, a hemispherical parachute with a drag coefficient of 1.5
is used. A safe descent rate is necessary to provide a safe landing while also avoiding a speed that
would allow the CanSat to drift too far away due to weather conditions. With this, the
requirements are for the CanSat to have a landing velocity of 7 meters per second.
a. Parachute Sizing
For the calculation of the parachute area, the assumptions are:




The target weight of the CanSat structure is 350g (with sensors and added weights, in case
the initial weight is less than the minimum of 300g).
The parachute generates only drag but no lift.
The aimed rate of descent is 7 meters per second.
The parachute is semi-spherical, using a drag coefficient of 1.5.
b. Parachute Calculation
With the assumptions above, the calculations begin by balancing the upward and downward
forces. The upward force is the drag of the parachute pushing upwards, while the weight of the
CanSat, which is pushing downwards, is the downward force.
𝑚𝑐𝑎𝑛𝑠𝑎𝑡 ∗ 𝑔0 =
1
∗ 𝜌 ∗ 𝑉 2 𝑙𝑎𝑛𝑑𝑖𝑛𝑔 ∗ 𝐴 ∗ 𝐶𝑑
2
Rearranging for area gives:
𝐴=
2 ∗ 𝑚𝑐𝑎𝑛𝑠𝑎𝑡 ∗ 𝑔0
𝜌 ∗ 𝑉 2 𝑙𝑎𝑛𝑑𝑖𝑛𝑔 ∗ 𝐶𝑑
CanSat Parachute Radius:
𝐴
𝑟= √
𝜋
Calculate for Parachute Diameter:
2 ∗ 0.350 𝑘𝑔 ∗ 9.80665
𝐴=
1.225
𝑘𝑔
𝑚
∗ (7 2 ) ∗ 1.5
3
𝑚
𝑠
23
𝑚
𝑠 2 = 𝟎. 𝟎𝟕𝟔𝟐𝟒𝟐𝟏𝟕𝟔𝟖𝟕 𝐦𝟐
0.07624217687𝑚2
r= √
= 𝟎. 𝟏𝟓𝟓𝟕𝟖𝟑𝟗𝟒𝟖𝟔 𝐦
𝜋
D = 2r = 2(0.1557839486𝑚) = 0.3115678972 𝑚
D = 0.3115678972𝑚 + (0.3115678972𝑚 ∗ (0.20)) = 0.37388 m
3.2808𝑓𝑡
0.37388 𝑚 ∗
= 𝟏. 𝟐𝟐𝟔𝟔 𝐟𝐭
1𝑚
Spill Hole & Parachute String
𝑆𝑝 = 1.2266 ft ∗ (0.2) = 𝟎. 𝟐𝟒𝟓𝟑𝟐 𝐟𝐭
𝑃𝑠𝑡𝑟 = 1.2266 ft ∗ (1.5) = 𝟏. 𝟖𝟑𝟗𝟗 𝐟𝐭
VI.
Testing
Preliminary CanSat testing was conducted to evaluate key sensors for the Primary Mission. One
of the main goals was to verify the HC-12's ability to transmit data at one transmission per
second. The HC-12 used a baud rate of 2400. Both HC-12 units operated on channel 044
(approximately 450.6 MHz). This frequency was selected because it is less susceptible to
interference, ensuring reliable communication.
The first test was walking around and away from the receiving HC-12. The recorded distance was
at least 250 meters. Initially, the receiving HC-12 was able to collect data, but as the distance
increased (at least 100 meters), it cut off. When the CanSat is in proximity, the transmission works
as required. The GT-U7 GPS Module works as required, it achieves satellite lock in at least 2
minutes at a cold start. The CanSat also sends data in rows, and a part of this is checking if the
CanSat sends data in the correct format.
The CanSat sends data in this arrangement:
Row 1 (Primary Mission):
Pressure | Altitude | MS5611 Temp | NTC Temp | Latitude | Longitude | SD Card Status |
Elapsed Time
Row 2 (Secondary Mission):
Accel X| Accel Y | Accel Z | Gyro X | Gyro Y | Gyro Z
24
Figure 16. Initial Data Transmission Results
Figure 17. Initial Testing Results (GPS) via GPS Visualizer
25
The CanSat must log data in a format that ensures it is easy to synthesize for post-study analysis.
There is a tendency for the CanSat to send data in two rows, which causes the data to be logged
in two rows, making it difficult to copy the values for the graphs. This is solved by logging all the
values in one row with each data in its cell. This is also possible by logging the data using the CSV
(Comma-Separated Variable) file extension instead of a text file (txt).
Figure 18. SD-Card Logging in CSV file
In addition to communication testing, initial assessments were conducted on the MS5611 and
the NTC Thermistor to evaluate their accuracy and consistency in measuring and correlating
critical data points, including pressure, altitude variations, and temperature fluctuations. The
sensors must validate these relationships similar to the ISA Standard Atmosphere 1976. Figure
19 shows the inverse relationship between pressure and altitude.
Figure 19. Pressure vs. Altitude Graph
26
Figure 20. Temperature Graph
Figure 20 shows the temperature outputs from both the MS5611 and the NTC Thermistor. The
graphs show that the NTC thermistor generally reports higher temperatures than the MS5611
temperature sensor, potentially because the NTC is more exposed to ambient temperature while
the MS5611 may be influenced by the temperature of other internal components.
Aside from the primary mission, tests were conducted for the secondary mission’s components.
The Python UI must be able to synthesize the data from the CanSat and predict its next position
correctly. A test for the LED sequence was also conducted. This was done by making each LED
glow per 1 meter instead of 1000ft using the same code. This proved successful as well.
Figure 21. Functional Python UI
27
Figure 22. Functional LED Sequence
VII.
Detailed Budget
Table 6. CanSat Components Budget
Quantity
Unit
Description
Price
(including
shipping
fees)
Total Price
(including
shipping
fees)
1
GT-U7 GPS
Module
A quicker alternative to the Neo6M GPS Module purchased online
from Shopee.
PHP 364
PHP 364
1
MPU6050
The support element of the
secondary mission. It was obtained
via Shopee.
PHP 148
PHP 148
1
Teensy 4.0
The Teensy 4.0 was chosen for its
enhanced speed and memory,
PHP 1999
PHP 1999
28
addressing the limitations of the
Arduino Nano.
8
Fabricated
PCB
The ability to use fabricated PCBs
stems from fabrication processes
that are confined to the bottom
layer, allowing designs to be
created without the need for jumper
wires.
PHP 77
PHP 676
Total Price
PHP 3187
Table 7. Rocket Detailed Budget
Quantity
Unit
Description
Price
Total
Price
1
3D Printed
Avionics Bay
(670g)
This is the PLA-printed housing for the
ejection system and flight computer. It is
printed in the IAU RND department.
PHP
720
PHP 720
12
Rocket Decals
These stickers are placed outside to
enhance the rocket's aesthetics.
PHP 83
PHP996
2
Swivel Hook
(small)
This is the swivel for the CanSat and drogue PHP 27
parachute.
PHP 54
1
Medium
Swivel Hook
This is the swivel for the nose cone.
29
PHP 47
PHP 47
1
Large Swivel
Hook
This is the swivel for the main parachute.
PHP 57
PHP 57
Total
Price
PHP
1874
VIII. Outreach Conducted
The outreach initiative comprises a workshop or seminar specially designed for the Timber City
Academy STARS Club, which includes students from basic education, senior high school, and
educators in Butuan City, Philippines. This event aims to inspire and educate participants about
contemporary developments in space technology, the fundamental principles of CanSats and
rockets, and the objectives of the CanSat competition. The workshop was conducted virtually
using platforms such as Zoom or Google Meet, ensuring an accessible and engaging experience
for all attendees.
The primary objectives of this initiative include promoting interest in aerospace-related academic
and professional fields, encouraging active participation in STEM (Science, Technology,
Engineering, and Mathematics) activities—specifically the CanSat competition—and sharing
experiential insights from second- and third-year Bachelor of Science in Aerospace Engineering
(BSAE) students from Indiana Aerospace University.
The workshop's structure encompassed several critical components. The event commenced with
an introductory segment, followed by a series of informative sessions that addressed various
topics, including the historical development and societal implications of space technology, the
applications and components of CanSats, and the fundamental mechanics of rocketry. A
significant aspect of the workshop was the personal narratives shared by the speakers, who
discussed their experiences as aerospace engineering students, including the challenges they
faced and the opportunities available through their academic pursuits. The workshop culminated
in a question-and-answer session, allowing participants to engage directly with the experts about
CanSats, rocketry, and the broader field of aerospace engineering.
The anticipated outcome of this outreach initiative includes heightened awareness of aerospace
engineering principles and CanSat fundamentals, inspiring students to consider careers in
30
aerospace-related fields, and strengthening connections between Indiana Aerospace University
and Timber City Academy. By fostering STEM education and highlighting practical applications
within the realm of aerospace engineering, this workshop aims to inspire the next generation of
innovators while underscoring the leadership role of Indiana Aerospace University students in
advancing aerospace education.
IX.
Progress Report
The primary mission was successful, as the CanSat was able to transmit data in the correct format
and two rows as planned. The switch has been positioned to be inside the CanSat structure
enough to prevent accidental shutdown during launch. Additionally, the parachute is securely
attached to the CanSat to minimize unnecessary swinging during descent.
The secondary mission is now 90% complete, needing only a few final refinements. The
mathematical foundation for the algorithm has been established, and preliminary tests have
been conducted to validate its performance. The structure of the CanSat and the PCB have been
finalized, and the sensors are functioning correctly. There are no issues with the two HC-12
Transceivers; they are only waiting for the final frequency for the competition, with channel 044
(450.6 MHz) currently in use. There is only the concern of the data transmission cutting off at
short distances, thus it will be a concern worth looking at.
All the components for the Aromaz rocket have been gathered, including the rocket pistons, SRM
holder plates, the avionics bay, and the integration of the buzzer into the nose cone. The
fabricated PCB for the flight computer has just arrived, and the next step will be to solder the
components. The programming for the timer-based system is yet to be tested by the IAU RND.
31