The flight computer is responsible for the operation of rocket core functionality. It triggers actuators such as igniters, valves, and recovery systems. It also logs flight data. All functions must be precision timed to within 5ms, and all in-flight functions are critical.
November 31: Research and select components based on weighted criteria, have them ordered
December 31: Begin testing performance of individual components and coding, use breadboards - prototyping deliverable for each subsystem (for purchasing, will need additional timeline)
January 31: Assemble board (expect two to three iterations)
February 28: Integration testing
Our initial testing will be performed on campus for any components/software that we obtain. We will test individual components for both functionality and reliability, as well as perform integration testing on the entire board.
Initially, working hands-on with the existing solution/prototype will be useful to understanding what our final product will remember, with obvious improvements from the original board.
Testing will be performed on campus at Stevens.