When it came time to select my senior design project it seemed fitting to do something along the lines of avionics since I had been working as a software engineer at an avionics manufacturer for four years. So I chose to design a rocket avionics card that would monitor flight characteristics, deploy two parachutes at the proper time, and help you find the rocket once it returned to the ground. Once the design was done and made it through the standard review process design by my professor, it was time to build and test the system. Due to the usual issues associated with supply chains I was already well behind schedule by the time the parts arrived and I began assembling the hardware. It basically came down to having 48 hours to assemble the circuit, test the software that I had mostly completed but never tested, and package the system into a payload bay for a high powered rocket launch. Since the launch event was coordinated with a local amateur rocketry club and the next event was well after my project due date, I could not miss the deadline or I would not be graduating that year. Needless to say, the phrase "failure is not an option" was forefront in my mind over that 48 hour period!
Once I had the circuit assembled and had the USB communication link between it and my computer, I thought the rest was going to be smooth sailing. Any engineer reading this is probably laughing hysterically at this point since "smooth sailing" prior to an upcoming deadline is a fantasy held only by overly optimistic junior engineers. With only a day left, I began working the bugs out of my code and got the various features of the device working. After a short time I could save data from the pressure sensor and accelerometer to the EEPROM and dump that data over the USB port to the PC and I could manually force the electrical outputs that were designed to ignite the parachute deployment charges to cycle on and off. Everything seemed to be working great so off I went to the university's physics department to use the pressure chamber to test my system.
Upon arriving at the pressure chamber I learned that it had broken the day before and it was the only chamber on campus. I now had no way to test if my algorithms to convert the sensor data through the ADC inputs were correct. If they were wrong then the parachute charges would be ignited at the wrong time which would present a serious safety threat to launch attendees. If I could not find a way to test the system then I would not be able to launch it and graduate the following month. So I did what any smart engineer would do at this point; ask an even smarter engineer for their advice.
In this specific case, I drove over to my parents' house and consulted with my dad who was designing circuits long before I was even born. We needed to find or create a pressure chamber of some sort that would fit my circuit card and test it from ground level up to at least 20,000 feet ASL (which, in Central Florida, also happens to be 20,000 feet AGL). While we were sitting at the table brainstorming ideas my mom was working on canning (i.e. jarring) tomatoes from the recent harvest of their garden. Tomatoes... Jarring... Glass Jars... Eureka!
With only 10 hours left before I had to be at the launch event we began hacking together a pressure chamber using two glass masonry jars, a few valves, and an automotive vacuum pump. One jar was the reservoir and the other held the avionics card. A little bit of physics and math determined the algorithm used to find the pressure needed in the reservoir to equalize with the other jar that represented a specific altitude. Thus, using the pump and valve system, we were able to simulate a rocket's accent and decent by creating a vacuum in the jar with the circuit card and then equalizing it with the normal atmospheric air around it. Using this hacked together pressure chamber I found a few bugs in my algorithm and was able to fix them prior to the launch event.
After a successful flight and a few weeks of documentation writing, I presented my design along with the masonry jar pressure chamber to the senior design judges at the university's showcase event. A few of the judges were actual rocket scientists from NASA and they really enjoyed the story behind the pressure chamber. In the end, my project won the Best in Show award in the Computer Engineering category and it was all thanks to a jar full of tomatoes.
Terry Reinert is a software engineer, karate instructor, and amateur photographer residing in Central Florida.
Nice story! This reminds me of when I used to enter science and engineering fairs in high school. I'd always end up madly soldering, rewriting and debugging C or VHDL code and redoing results on the night before judging... and almost missing flights too. One time I even got some new (literally) last-minute circuit boards shipped to the hotel I was staying in, haha. Those were some fun days.
There is an innovation some way or other behind every success. I felt the tension of meeting the deadline while going through the story. Nice one! May be next time you should add some buffer in your plan for tackling the things not happening as expected :)
Some of the details are good lessons...
Supply chain - yes, parts will be late. Count on it.
Broken pressure chamber - test equipment will fail when needed most.
Seek help with a smarter engineer - Dad in this case, but very good advice. AKA Mentoring.
Make do with jerry-rigged equipment if necessary. Better than no equipment.
Make that deadline in spite of all setbacks. Hiring managers will be impressed.
Murphy's Law supersedes all others.
Good story, Terry. You'll go far.
This tale certainly points out the value of a diversified education, or at least, diversified experience. If one were a very narrow-path specialist, then all of the other helpers as mentioned by Bob, above, would indeed be required. This story shows why the broader experiences in engineering are needed. Good job on the vacuum chamber part, by the way.
I am sure that the canned solution was needed to preserve your graduation! A good story and an great illustration of common sense intersecting with necessity. The project does sound overly ambitious to me also.
If you were doing this senior design project by yourself, it was seriously over-scoped. Where was your advisor? Did the fellow have any experience bending metal, or was he a basic theorist? I'm glad you drove the project to completion, but some of your grief load was out of your hands... well, all's well that ends well, I suppose.
Join our online Radio Show on Friday 11th July starting at 2:00pm Eastern, when EETimes editor of all things fun and interesting, Max Maxfield, and embedded systems expert, Jack Ganssle, will debate as to just what is, and is not, and embedded system.