1. Team Name Ballooning Flight Readiness Review (this is a bare-bones template – reorder the slides and/or make it fancier if you wish, but be sure to address at least the items listed here) (plan to speak for 7 – 8 minutes – don’t go overtime, but if your presentation is too short then add more content) (share the speaking time approximately equally, even if that means that not everyone does the same number of slides)
Include a photo of all the team members
and your payload (finished or under construction)
Team Members Full Names
Class Number and Date

2. Introduction to Payload
Introduce your classmates to your payload using at least one labeled diagram. This can be hand-drawn or made using a CAD program. In this diagram the components may just be (labeled) “lumps” that occupy volume – you don’t need to draw them in a detailed way.
Point out the features that make your payload interesting/unique. Mention how your camera, in particular, will complement the cameras on the other payloads flying on the same stack as yours.

3. Construction Photographs
Show some photos of your construction process. Each photo should have a short caption. Include (at least) a photo of the physical box construction, working on the Arduino/wiring, and working with the off-the-shelf components (Neulogs and/or GoPro Session camera).

4. Ready-to-Fly Payload
End with photos showing the finished payload. Include at least one exterior view and at least one interior view (i.e. with the top open). Label the components that are visible. (Components do not have to be zip-tied in, as of this point in time.)
ASIDE: Have the payload in hand but be sure the slides also “stand alone” – that is, if someone (in the future) sees the slides but not the actual payload, they should still be able to understand what you built.

5. Parts List
List the materials and components used in your payload. Don’t read through this whole list but do take at least 30 seconds (or so) to point out some of the things that are most interesting (or most unique).
On this list next to each major part include a dollar value (I will send out this information). Include a total dollar value for the whole payload.
Include a total weight in pound and/or ounces of the finished payload, including rigging. (Optional – include mass in kilograms as well.)

6. Neulog Sensor Suite
List the sensors you will fly and how fast they will log. (The plan is to set all sensors to log data once every second for up to 5 hours.)
For sensors which are orientation sensitive such as magnetometers, accelerometers, light and UV sensors, etc., indicate how they are oriented.
Indicate which sensors are mounted so they can “see” outside and which are fully inside the box.
State any special features (e.g. point the range finder toward a fixed target; have an audio siren for the sound sensor to listen to; etc.)

7. Arduino Hardware and Wiring
List the Ardunio sensors you will be flying and which Arduino pins they will be attached to. (e.g. Geiger counter: GND, 5V, pin D4)
Show a general wiring diagram for the Arduino system (this can be the one shown in class or else one that you have drawn yourself).
Explain what each LED means when it flashes.
OPTIONAL: Add more details to the general wiring diagram indicating which pins are used by the GPS, the XBEE radio, the data-logging shield, and each of the sensors. If you expand the wiring diagram, keep it neat so that it remains readable.

8. Arduino Programming
State (a) the data logging plan, (i.e. read and log sensor data and flash the DATA LED once every 5 seconds), (b) the automatic-radio-beaconing plan (i.e. send out every 55th data point and flash the XBEE LED), (c) the in-flight commanding plan (i.e. when the XBEE received the command “insert text here” do the following…), and (d) your team’s contribution to the “data-reliability project” (i.e. Record all sensor data in 3 independent files on the SD card and compare the 3 files post-flight. Check if the error rate increases during the high-radiation part (i.e. the highest part) of the flight.).

9. Team Organization
Draw an organizational figure (AKA an “Org chart”) indicating who actually did what on your payload build. This is a graphic, not just a text list. Be sure to indicate (at least) who is the “lead” on the various categories that I asked about earlier (by ).