Rocket Team Notes.pdf

0-10m

• Wherever there is an error state, set and print flags
• We want to put the flags into both the flash
  • Assuming the flash and the radio aren’t one of the flags
• We should assume that we have a radio
• Radio link a good idea
• Priority should be confirming that the flash works and that we get back data
• Probably should halt work on HOOTL and other side projects

10-20m

• No test flights
• Pick a lockdown date for code
• Discuss Error State (Flag all errors that happen in prelaunch)
• Get someone to keep track of what's going on with hardware
• Create wiki page that has chart of all Pyxida versions we know of.
  • Record date, version, etc. that we know of 

30-40m

• Camera tasks:
• Hardware part:
  • Building and attaching circuits to firefly and through to spare GPIO on pyxida
  • 'Potting'?
  • Taking test results from the cameras to confirm what operating mode they're in
  • Epoxy light circuit and USB
  • For camera - "Picture will be broken out from the ribbon cable via veroboard"
• Software part:
  • Reading from GPIO the stage
  • Stage will be "high or low - detect a waveform from a digital can"
  • Make a function you can call for initializing camera that "sends on signal wait to see what comes back, send the signal again and wait again, repeat for a certain number of times before it gives up
• Luka: "READ ASANA POSTS AND LIKE THEM" and be more active on asana in general

70-80m

• Create better hardware script (see requirements)

• Test equipment budget $100

• Set aside $800 budget for pyxida hardware (450 spent so far)

80-90m

• need three fully assembled boards; rest for testing

• $50 each plus parts -- $350

• $800 budget for hardware

• groundstation temps - $500?

• extra spending for away team on mountains

• 2 dipoles -- $40-50 each

• reduced the budget by $700

• more batteries

• oxidation problem with pyxida 6

• cover and launch procedures

• flight computer requirements

• away team procedures

• more programmers/debugger - upload firmware