Project Overview
Briefly describe the project's goals and its context (for Launch, this will be a competition, onboarding, or R&D)
Table of Contents
Pages
Goals
Goal | Reason |
|---|---|
Contain and Support a Soda Can During Flight | Learn how a carbonated beverage will behave after experience launch conditions. |
Use a Party Payload Including Lights and a Speaker | Expose delicate electronics to launch conditions. |
Utilize a Reefed Parachute In Recovery | Test a single-bay deployment system for future use. |
Deploy a Smoke Flare at Apogee | Develop a method of mixing and deploying a smoke flare for aid in locating rockets on the ground. |
Open Recovery Bay at Apogee and Disreef Parachute | Recovery of the rocket. |
Track Rocket Position | Aid in locating the rocket after flight. |
Reach 6,000 ft. | Apogee goal. |
Gather Telemetry Data During Flight | Verify success of reefed parachute and collect information about the rocket’s performance. |
Post-mortem
Project is still in progress.
Design overview
Payloads
Payload Requirements
Mission requirements
Requirement | Reason | Verification |
|---|---|---|
Party Components | To achieve the goal of a fun rocket with lights and music | Test |
Internal Power | To be independent from avionics | Design |
Removable Bulkhead | To be able to place components in payload at launch | Design |
URRG Requirements
Requirement | Reason | Verification |
|---|---|---|
All components of the rocket must be recovered, and no part of the rocket can be intentionally ballistic | URRG Safety | Analysis |
Interface Requirements
Source(s) | Requirement | Reason | Verification |
|---|---|---|---|
Structures | Polycarb inner diameter of 3.5 in and outer diameter of 4 in | To stay within design constraints given. | Design |
Design
The Payload of the FLDSMDFR contains several delicate electronic components contained within a polycarbonate section of tube. Going from the bottom up these components are: a speaker, a camera, fairy lights. In between the speaker and cameral there is a centering ring (originally designed to be a bulkhead with a door on it) that does not allow the camera to fall onto the speaker.
Post-mortem
Despite the overall breakup of the rocket, all electronic components of the payload survived the launch. The speaker is heavily damaged and its buttons no longer work as intended, but it is still able to play sound and continues to be able to pull said audio from the SD card inside. The camera has residue on its lens, but is otherwise completely operational. The fairy lights are fully operational. The payload as a whole worked as intended despite a severely off-nominal launch.
Avionics
Avionics Requirements
Mission Requirements
Derived from the goals.
Requirement | Reason | Verification |
|---|---|---|
Track Rocket Location | Aid in Recovery of the Rocket | Test |
Gather Data: Altitude, Acceleration, Velocity | Verify success of reefed parachute and collect information about the rocket’s performance | Test |
Provide Ejection Signals to the Smoke Flare, Deployment Charges | Ensure safe descent of the rocket and ignition of smoke flare | Test |
Flight Computers are Redundant and Independent | Ensure that the flight computers and e-matches work in case of a single failure | Design |
URRG Requirements
Describe what an external organization (probably ESRA, URRG, or EH&S) requires of this one.
Requirement | Reason | Verification |
|---|---|---|
All components of the rocket must be safely recovered, and no part of the rocket can be intentionally ballistic | Safety | Design |
Interface Requirements
Describe what other subsystems require of this one.
Source(s) | Requirement | Reason | Verification |
|---|---|---|---|
Recovery | Smoke Flare Deploys | Send deployment signals to the smoke flare for recovery of the rocket | Test |
Recovery | Deployment Signal to Deployment charges | Successfully deploy the parachute | Test |
Structures | Structures Polycarb Interface (Difference of inner diameters of 3.85” and 3.5”) | Ensure Avionics Bay fits in the rocket and does not interfere with other sections | Design |
Design
This should describe high-level distinguishing features of this subsystem. If this project is recurring (Space Race or IREC), focus on the items you judge would be important to tell the next year's team, especially specific improvements over previous years.
The Avionics Bay used 2x Eggtimer Quarks powered by 2x 7.4V 2000mAh Li-ion Batteries. The flight computers were wired entirely independently.
For tracking, the Avionics Bay used 1x Eggfinder Mini TX powered by 1x 7.4V 2000mAh Li-ion Battery to transmit signals from the rocket, and 1x Eggfinder Dongle RX connected to a laptop to recieve signals on the ground.
For Data Logging, the Avionics Bay used 1x Adafruit Feather M0 Adalogger powered by 1x 3.7V 2000mAh Li-ion Battery. The datalogger system utilized two breakout boards, 1x Adafruit BME280 to record temperature and pressure (and thereby altitude) and 1x Adafruit ICM-20948 9-DoF IMU to record acceleration, rotation, and orientation. All data recorded would be written to 1x 4GB microSD Card hot glued into the mainboard.
Post-mortem
Due in part to the catastrophic nature of the rocket’s launch, the only avionics system operating when the rocket was launched was the tracking system.
Despite the unanticipated forces applied to the avionics bay during the flight, the tracking system continued operating through its entirety, eventually successfully reporting the final coordinates of the avionics bay (42.700473°, -77.194522°).
Over the course of the flight the avionics bay experienced multiple structural failures. The most important to note is that several of the battery mounts sheared off such that they no longer constrained the Li-ion batteries. This is potentially due to the orientation of the layer lines in the 3D prints combined with the higher than anticipated forces. It is worth examining layer line orientation in the future to reduce the chances of loose Li-ion batteries in rocket, successful or not. The attachment keeping the avionics bay constrained to the polycarb tube also sheared, though this is likely due primarily to the higher than anticipated forces, and likely could not have been reasonably mitigated.
Aside from flight complications, assembly of the avionics bay should have been given more design considerations. Some screws and nuts were placed in tight spaces, making accessing them for assembly and disassembly difficult, though not impossible.
Additionally, integration of the avionics bay with the rest of the rocket should also have been given more design considerations, as integration while the e-matches were connected was difficult, though again not impossible.
In the future, when evaluating whether or not to turn off avionics systems:
It must not be done while the igniter is still in the motor.
The decision should be made in the context of the battery life of the avionics systems contrasted with the expected delay.
Structures
Structures Requirements
Mission Requirements
Derived from the goals.
Requirement | Reason | Verification |
|---|---|---|
URRG Requirements
Describe what an external organization (probably ESRA, URRG, or EH&S) requires of this one.
Requirement | Reason | Verification |
|---|---|---|
Interface Requirements
Describe what other subsystems require of this one.
Source(s) | Requirement | Reason | Verification |
|---|---|---|---|
Design
This should describe high-level distinguishing features of this subsystem. If this project is recurring (Space Race or IREC), focus on the items you judge would be important to tell the next year's team, especially specific improvements over previous years.
Post-mortem
In Progress
Recovery
Recovery Requirements
Mission Requirements
Derived from the goals.
Requirement | Reason | Verification |
|---|---|---|
URRG Requirements
Describe what an external organization (probably ESRA, URRG, or EH&S) requires of this one.
Requirement | Reason | Verification |
|---|---|---|
Interface Requirements
Describe what other subsystems require of this one.
Source(s) | Requirement | Reason | Verification |
|---|---|---|---|
Design
This should describe high-level distinguishing features of this subsystem. If this project is recurring (Space Race or IREC), focus on the items you judge would be important to tell the next year's team, especially specific improvements over previous years.
Post-mortem
In Progress