summaryrefslogtreecommitdiff
path: root/OMSIList.mdwn
blob: 2e81d21a3876b05ab1983fe85c2588762a81c77d (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
# <a name="July 17th, 2004:OMSI Space Day D"></a> July 17th, 2004: [OMSI Space Day](http://www.omsi.edu/visit) Demonstration

The main PSAS sign up page, along with a list of things to bring, is at: [[OmsiSpaceDay2004]]

### <a name="Goals"></a> Goals

Here's our arbitrary goal to have working by then, in priority:

1. Camera broadcasting over ATV to ATV receiver.
2. Fake FC status display on ATV overlay.
3. Actual honest to god GPS data on the overlay.
4. Rocketview up and running displaying data.
5. Interaction with the launch tower to "launch" the rocket

So what does this mean for the software:

Sort of in order:

**Flight Computer:**

- Some skeleton version of `sequencer` which starts from `init` and goes to `LaunchDetect`.
  - Turns on CAN nodes: ATV, GPS, IMU
  - Some interaction with the launch tower via APS/umbilical (sets rocketready)
- Smart processing
  - GPS processing (done)
  - GPS to ATV processing: ATV code done, leave it in place? It needs a new FCFIFO process
  - `uncanny` up and running in some form

**Launch Tower:**

- `uncanny` up and running in some form
- `launchcontrol` up and running, which can relay CAN messages via the LTC to the LT relay node

**Ground Station:**

- `rocketview` up and running, displaying IMU (done) and GPS data