I competed in NASA's University Student Launch Initiative. This was a year long competition based around launching a rocket close to a predicted altitude, then deploying a scientific payload. We successfully completed all of NASA's design reviews and test flight, leading to a nominal rocket flight in Huntsville. Our rocket reached 4,266 ft (the goal was 4500) and our payload correctly transmitted all possible scientific data.
The team won the Rookie Award (for the highest scoring rookie team) and the Relativity Space 3D Printing Award!
I served as the electronics and software lead, the systems integration engineer as well as the treasurer for the larger club. I also wrote a significant portion of the payload software and contributed to the design of the rocket and payload.
Our rocket ready to launch after completing checkout
Lifting off in Huntsville
Recovery!
My team preparing to launch in Huntsville
I served as the electronics and software team lead, as well as the systems integration engineer.
I led the development of high level project goals for the entire year. I based these goals in the teams capabilities, while providing reach areas for the team innovate in. All primary and secondary goals were accomplished.
As the systems integration engineer I worked with the other group leads to ensure that the rocket came together smoothly. I made architecture decisions, pushing for the team to have a simple but capable rocket. I prioritized redundancy, having fallback solutions to the team's more complex goals.
I led the 15 member electronics and software group. I held bi-weekly meetings, distributed the work amongst members, reviewed work, compiled documentation and ensured deadlines were met. I made sure every active member had a significant contribution to the final rocket that flew in Huntsville.
NASA's process involves writing extensive documentation and planning carefully. As part of this, I developed FMEA for the entire project, looking at the risks and mitigations for risks to personnel, equipment, the environment and the project.
I wrote and tracked extensive requirements for the rocket's systems. I developed testing verification procedures, and ensured they were followed.
This enabled the team to have a safe and successful season. The team works with explosives, dangerous machines, and flying rockets. I worked to create a safe environment for everyone.
Part of the FMEA documentation
Some payload requirements
Modulation test output
I wrote the software framework that the entire team used. The software ran on SAMD21 microcontrollers. The framework was based on using C++ features like inheritance and templates, while strictly not using dynamic memory.
I wrote software that modulated data in 1200 Hz and 2200 Hz tones, which were played into the microphone port of a handled radio. This involved using hardware timers to allow for sin waves to be generated by the MCU's DAC.
I was closely involved in the design process for the team's payload and rocket. I defined high level architecture for the rocket, including the payload location and deployment mechanism. I reviewed detailed design with other engineers in the club to iterate and improve their designs.
We prioritized using different materials effectively: 3D printed parts were often used to achieve complex geometry while fiberglass or metal parts took the structural loads.
I also worked with another engineer in the club to design a PCB to control the payload. The PCB included a GPS, FLASH memory, a high current burn wire driver, a SAMD21 microcontroller, a barometer and an IMU.
3D flight profile
Pressure spike from pyrotechnic charge in payload sepeartion
After ground tests and test flights I analyzed data. I calculated flight parameters, such as landing velocity, accelerations sustained, and drift to ensure safe flights.
I categorized pressure spikes during flight events, which drove the filter design in software to prevent false positives.