summaryrefslogtreecommitdiff
path: root/doc/telegps-system-operation.inc
diff options
context:
space:
mode:
authorBdale Garbee <bdale@gag.com>2016-01-10 19:04:49 -0700
committerBdale Garbee <bdale@gag.com>2016-01-10 19:04:49 -0700
commit70e9064ca962dfd345f8a342afa130f969606553 (patch)
treee8e374912df403e7e237aecbd1ec0a19fa6c5c42 /doc/telegps-system-operation.inc
parent489d22f448d9927533e90da4d16c5a332a234a8d (diff)
parent73ce3f73526edfabccd3b98e6e67de6d82a84b63 (diff)
Merge branch 'master' into branch-1.6
Diffstat (limited to 'doc/telegps-system-operation.inc')
-rw-r--r--doc/telegps-system-operation.inc30
1 files changed, 30 insertions, 0 deletions
diff --git a/doc/telegps-system-operation.inc b/doc/telegps-system-operation.inc
new file mode 100644
index 00000000..c9fce7f0
--- /dev/null
+++ b/doc/telegps-system-operation.inc
@@ -0,0 +1,30 @@
+[appendix]
+== TeleGPS System Operation
+
+ === GFSK Telemetry
+
+ TeleGPS's native telemetry system doesn't use a
+ 'normal packet radio' mode like APRS because it's not
+ very efficient. The GFSK modulation we use is FSK
+ with the base-band pulses passed through a Gaussian
+ filter before they go into the modulator to limit the
+ transmitted bandwidth. When combined with forward
+ error correction and interleaving, this allows us to
+ have a very robust 19.2 kilobit data link with only
+ 10-40 milliwatts of transmit power, a whip antenna in
+ the rocket, and a hand-held Yagi on the ground. We've
+ had flights to above 21k feet AGL with great
+ reception, and calculations suggest we should be good
+ to well over 40k feet AGL with a 5-element yagi on the
+ ground with our 10mW units and over 100k feet AGL with
+ the 40mW devices.
+
+ :aprsdevices: TeleGPS
+ :configure_section: _configure_device
+ include::aprs-operation.raw[]
+
+ === Configurable Parameters
+
+ Configuring TeleGPS is very simple; the few configurable
+ parameters can all be set using the TeleGPS application over
+ USB. Check out <<_configure_device>>.