• About PSAS
• Get Involved!
• Schedule
• Projects
• Presentations
• Mailing lists
• Contact us

• Teams
  • Airframe
  • Avionics
  • Communications
  • Ground
  • Payload
  • Propulsion
  • Rocket Science
  • Safety
  • Software
  • Uncertainty
  • Regulation
  • PSU Student Club

Friday, February 3rd, 2006

Present: Sarah, Jacob, Glenn, (then later) Andrew and Mark

Agenda:

• Capstone team meeting - should we meet before the presentation?
• start 1:30pm in FAB 160-10, may move to FAB 155 at 2pm
• present project proposal to industry sponsor and faculty advisor (and whoever else shows up)

Minutes:

• We started working in the engineerig round table area then moved to FAB 155 with the InFocus projector. We determined which parts of the presentation each member will present and then timed the actual presentation. Jacob was about 5 min, Sarah was about 6 min, and Glenn was about 17 min! (Glenn blabbers too much!). The organization was changed to balance out the load better.
• We presented the proposal to Mark and he though it was very good.
• Notes taken during the post-presentation discussion:
  • Mark suggested we provide in the schedule:
  • Time to write up a formal written test plan. The test plan should cover "category testing" to be done with details.
  • Time to review test plan.
  • Need to describe what hardware and software is needed for testing. Where will we get it if we don't have it, and how long will it take and cost to acquire.
  • Mark asked we get these additions to him before we complete the design decisions.
  • In the PDS we should indicate what the requirements of the microcontroller are (we have done this). I think this was just a side note of something to be aware of.
  • Break down schematic design into chunks smaller than 14 days. Mark suggests three 5 day chunks.
  • Include time to digest other team parts. This may not be highly important if we are working closely together with our parts, but becomes real important if members go off to do their parts alone.
  • Need an API in the white paper and engineering notebook.
  • Use other Node developers (e.g. Markus) as white paper guinea pigs of the API. (Sarah; No guinea pigs will be harmed in this project! ;) )
  • Document how to get the tool chain up and running.
  • Allow time in the schedule to get tool chain up and running on individual workstations.

Note:

• • Mark has about 40 Telos Motes; They are available for development. Ask Mark for info about them.