summaryrefslogtreecommitdiff
path: root/GroundSupport.mdwn
blob: 5559949d37e0f9597ebe80611fec773fee75ed73 (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
# <a name="LV1/1b Ground Support"></a> LV1/1b Ground Support

The important components of the ground support systems are [[LaunchControl]], [[GroundSupport#Telemetry]], and video from [[AmateurTelevision]].

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

LV1B's telemetry downlink was a 19.2Kbps downlink-only radio modem transmitting a [[custom protocol|GroundSupport/LV1BTelemetryPacketSpec.html]]. The recieving end on the ground logged all of the data for later analysis, and displayed a slightly-processed subset of the information in a graphical interface called RocketView. For LV2, we'd like to use a faster connection for telemetry, particularly [[WiFi]].

The important components of the telemetry system are the [[FlightComputerSoftware]] and the [[RocketView]].

> Changing how we get our telemetry to the ground doesn't mean we can't reuse
>
> LV1B
>
> 's protocol and Rocketview, but I think at least the protocol is worth replacing. Our experience with the protocol we designed for
>
> LV1B
>
> was that it was relatively complex to implement a decoder for it. Since we have a new network protocol which carries all of the information our telemetry should have (see
>
> [[CanMuxer]]
>
> ), I'd like to use that protocol.
>
> On the other hand, Rocketview successfully isolated the protocol implementation from the rest of the code, so it probably represents a good base to build LV2's telemetry display software on.
>
> -- [[JameySharp]] - 17 Dec 2001

----
Attachments:

- [[RELAYCONTROLV1.4.DSN]]
- [[RELAYCONTROLV1.4.pcb]]