summaryrefslogtreecommitdiff
path: root/WorkshopNotes16Dec01.mdwn
blob: ac05242915d9b82c9206b47015bae3b5be4c8bad (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
**Workshop Notes Sun 16 Dec 2001**

James convened a work party at his home, accompanied with food and homebrew beer and tea.

**Attendees:** Bart, Tim, Paul, James, Jamey, Larry

**Important deadlines:**

- Bart suggested that we should work toward the following rough dates:

<center>
  <table border=1 cellpadding=0 cellspacing=0>
    <tr>
      <th bgcolor="#99CCCC"><strong> Date </strong></th>
      <th bgcolor="#99CCCC"><strong> What </strong></th>
    </tr>
    <tr>
      <td> Mar 18 </td>
      <td> HW Freeze </td>
    </tr>
    <tr>
      <td> Apr 01 </td>
      <td> SW Freeze </td>
    </tr>
    <tr>
      <td> Apr 01 </td>
      <td> Logistics plan complete </td>
    </tr>
    <tr>
      <td> Apr 15 </td>
      <td> Launch date </td>
    </tr>
  </table>
</center>

----

**Work breakdown:**

**Logistics (complete plan Apr 1)**

- Safety plan
- Launch (operations) checklist
- Support equipment checklist (incl. food, tents, etc.)
- Responsibility assignments

**Software (complete April 1)**

- LV1b code could be dissected - Functional decomposition:
  - Ground control &amp; Tower
    - Jamey - wants to reuse stuff from LV1
    - New stuff 802.11 rocket link
    - Complete requirements spec needed
    - Design completion &amp; implementation completion
    - Bart can assist CS300
  - Avionics
    - ACTION: Larry write a software objectives document
    - ACTION: Larry work on (high-level) software design document.
    - Flight Computer
      - Operating system
      - application code
        - CAN driver
        - CAN demuxer
        - Protocol stack
        - Radio
    - CAN Nodes
      - Software (Paul)
      - Pyro, Uplink, GPS, IMU, Umbilical, Battery, ATV, Telemetry
  - Functional requirements specifications
    - down in one piece, communications
  - Functional sw life cycle decomposition
  - Larry volunteered as general software manager
  - ACTION: Larry will provide a task breakdown &amp; schedule for software. James will assist.

**Hardware:**

- Power systems are an interest: Ground &amp; Rocket
  - Tim says proposal to uncase a laptop battery, or primary lithium
  - James observes this is a risk reduction activity, need to load the work in the front of the schedule. Should select technology.
  - ACTION: Tim &amp; Andrew determine if rechargable doable by Feb 11, otherwise we bail to primary lithium
- Radio hardware: Rocket, Ground, Tower
  - What's Glenn's availability? Who knows?
  - Need Andrew &amp; Glenn to provide input
  - Risk: does 802.11 work, high speeds &amp; high altitude
  - Would like to be able to fall back to simpler slower radio earlier in the project
  - Can we test and select a technology by Jan 14?
- Avionics
  - FC is specced and seems adequate
  - CAN nodes seem to be well-understood technology &amp; tasks
- Payload
  - are we launching others ? power &amp;needs
- Mounting hardware, cabling
  - Tim says HW team will spec a card cage
  - Andrew and Tim both busy at the moment
  - What bus? phy
  - The evil rat's nest
  - ACTION: Andrew ask Matt Rupert whether he wants to be involved
  - Shake-n-bake time available said Andrew \* Ground control: Tower, Ground
  - Jamey says current thing works okay, not much has changed
  - Bart says let's replace the hoorible bridge w/wireless
  - Want a PROJECT laptop instead.
  - Jamey can manage this
  - Make cord be farther away from the wire -- Tim
  - Bart will review safety interlocks
  - Make sure VCR gets turned on this time

**Systems area:**

- Systems requirements needed
  - lots of things cross over --
  - James can take systems requirements and schedule things
    - examples
      - last launch interlock (hw, safety)
      - radio/antenna/power
      - vcr thing
      - battery vs. shore power things
    - mission requirements (objectives?)
      - goals, objectives, evaluation criteria
      - airframe stability
      - ask andrew for an outline (bryan, matt)

----

**General discussion**

- Bart - we need more hardware people
- Amy has chemistry... hmmm, find a way to have her contribute
- Tim says Steve?!? recruitable
- Ask Andrew to recruit more help -- grad students? Perhaps his highest priority
- James - post-tek folks? ex: switch to turn on/off vcr
- Tim - ex: autonomous recovery project?
- Critical-path stuff
- Bart - this needs to be mostly a psu club

**Action items**

- At this point, need Larry, Jamey to come with thier documents and add meat to the skeleton.
- James to take on system-level and top-level stuff, especially edge cases
- Bart is safety king, needs to come up with his stuff and documents
  - fire extinguishers, hard hats, headsup times, lawndart plan

**Flight sequencing model**

- Does this belong at mission requirements or sw requirements or not
- Need to recruit Ray to find out what we can learn from rocket industry
- We want to do things the right way.. not necessary amateur or industry
- Tim observes the flight state maps to the fault tree
  - it couples to avionics, safety, and other stuff

**LV1b code**

- Jamey asked for it, Andrew refused (it's ugly)
- Bart says cough it up, fuzzball
- Actually this came from Tim's thing, then with Andrew then LV1, LV1b...

**What else can we do?**

- Simulate and model everything? Industrial. Costly.
- Can we simulate can-bus in software? Maybe Jamey can get an ACM person.
- Jamey deliver us a head for January.

**Launch dates**

- April? Should have backup plan if we can't go with Tripoli.. say 4 weeks after.
- A bigger motor could give us a reason for aNOTHER launch. Is it an objective? Could oregon do a &gt;15K foot launch?
- Ask Ray to get in touch with senators, representatives to get military contacts to launch in a MOA. Permissions and support (chasing rockets)

- We need to understand airframe team stuff... rate of descent, so we know about site selection.
- Drafts of objectives &amp; specifications by January 14th... to reasonable level of detail.

-- [[JamesPerkins]] - 17 Dec 2001 <br />