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
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
|
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>TeleGPS Owner's Manual</title><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="book"><div class="titlepage"><div><div><h1 class="title"><a name="idp34092416"></a>TeleGPS Owner's Manual</h1></div><div><h2 class="subtitle">A recording GPS tracker</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Keith</span> <span class="surname">Packard</span></h3></div></div><div><p class="copyright">Copyright © 2014 Bdale Garbee and Keith Packard</p></div><div><div class="legalnotice"><a name="idp60435168"></a><p>
This document is released under the terms of the
<a class="ulink" href="http://creativecommons.org/licenses/by-sa/3.0/" target="_top">
Creative Commons ShareAlike 3.0
</a>
license.
</p></div></div><div><div class="revhistory"><table style="border-style:solid; width:100%;" summary="Revision History"><tr><th align="left" valign="top" colspan="2"><b>Revision History</b></th></tr><tr><td align="left">Revision 1.4.1</td><td align="left">20 June 2014</td></tr><tr><td align="left" colspan="2">
Minor release fixing some installation bugs.
</td></tr><tr><td align="left">Revision 1.4</td><td align="left">13 June 2014</td></tr><tr><td align="left" colspan="2">
Initial release
</td></tr></table></div></div></div><hr></div><div class="dedication"><div class="titlepage"><div><div><h1 class="title"><a name="idp60440208"></a>Acknowledgements</h1></div></div></div><p>
Have fun using these products, and we hope to meet all of you
out on the rocket flight line somewhere.
</p><div class="literallayout"><p><br>
Bdale Garbee, KB0G<br>
NAR #87103, TRA #12201<br>
<br>
Keith Packard, KD7SQG<br>
NAR #88757, TRA #12200<br>
</p></div><p>
</p></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="chapter"><a href="#idp60442576">1. Quick Start Guide</a></span></dt><dt><span class="chapter"><a href="#idp61322976">2. Handling Precautions</a></span></dt><dt><span class="chapter"><a href="#idp61325872">3. TeleGPS Hardware</a></span></dt><dd><dl><dt><span class="section"><a href="#idp61326544">1. Hooking Up Lithium Polymer Batteries</a></span></dt><dt><span class="section"><a href="#idp61329472">2. On-board Data Recording</a></span></dt><dt><span class="section"><a href="#idp61333680">3. Installation</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp60611120">4. System Operation</a></span></dt><dd><dl><dt><span class="section"><a href="#idp60611792">1. GFSK Telemetry</a></span></dt><dt><span class="section"><a href="#idp60614720">2. APRS</a></span></dt><dt><span class="section"><a href="#idp60452976">3. Configurable Parameters</a></span></dt><dd><dl><dt><span class="section"><a href="#idp60454304">3.1. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp60456432">3.2. Callsign</a></span></dt><dt><span class="section"><a href="#idp60457616">3.3. Telemetry/RDF/APRS Enable</a></span></dt><dt><span class="section"><a href="#idp60458944">3.4. APRS Interval</a></span></dt><dt><span class="section"><a href="#idp60460448">3.5. Maximum Flight Log</a></span></dt><dt><span class="section"><a href="#idp60462048">3.6. Logging Trigger Motion</a></span></dt><dt><span class="section"><a href="#idp60463376">3.7. Position Reporting Interval</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#idp60465024">5. TeleGPS Application</a></span></dt><dd><dl><dt><span class="section"><a href="#idp60466608">1. Telemetry Monitoring</a></span></dt><dd><dl><dt><span class="section"><a href="#idp65947584">1.1. Map</a></span></dt><dt><span class="section"><a href="#idp65953616">1.2. Location</a></span></dt><dt><span class="section"><a href="#idp65956928">1.3. Status</a></span></dt><dt><span class="section"><a href="#idp65960480">1.4. Table</a></span></dt></dl></dd><dt><span class="section"><a href="#idp65964528">2. TeleGPS Menus</a></span></dt><dd><dl><dt><span class="section"><a href="#idp65972624">2.1. New Window</a></span></dt><dt><span class="section"><a href="#idp65973952">2.2. Graph Data</a></span></dt><dt><span class="section"><a href="#idp65990624">2.3. Export Data</a></span></dt><dt><span class="section"><a href="#idp65996688">2.4. Load Maps</a></span></dt><dt><span class="section"><a href="#idp66010688">2.5. Preferences</a></span></dt><dt><span class="section"><a href="#idp66031072">2.6. Close</a></span></dt><dt><span class="section"><a href="#idp66032368">2.7. Exit</a></span></dt><dt><span class="section"><a href="#idp66033632">2.8. Connect Device</a></span></dt><dt><span class="section"><a href="#idp66037296">2.9. Disconnect</a></span></dt><dt><span class="section"><a href="#idp66038560">2.10. Scan Channels</a></span></dt><dt><span class="section"><a href="#idp66042240">2.11. Download Data</a></span></dt><dt><span class="section"><a href="#idp66045408">2.12. Configure Device</a></span></dt><dt><span class="section"><a href="#idp64831824">2.13. Flash Device</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#idp63308272">6. Updating Device Firmware</a></span></dt><dd><dl><dt><span class="section"><a href="#idp66058400">1.
Updating TeleGPS Firmware
</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp66067760">7. Technical Information</a></span></dt><dd><dl><dt><span class="section"><a href="#idp66068432">1. GPS Receiver</a></span></dt><dt><span class="section"><a href="#idp66071744">2. Micro-controller</a></span></dt><dt><span class="section"><a href="#idp66073072">3. Lithium Polymer Battery</a></span></dt><dt><span class="section"><a href="#idp66074336">4. Mechanical Considerations</a></span></dt><dt><span class="section"><a href="#idp66075664">5. On-board data storage</a></span></dt></dl></dd><dt><span class="appendix"><a href="#idp66077120">A. Release Notes</a></span></dt></dl></div><div class="list-of-tables"><p><b>List of Tables</b></p><dl><dt>4.1. <a href="#idp60617744">Altus Metrum APRS Comments</a></dt></dl></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp60442576"></a>Chapter 1. Quick Start Guide</h1></div></div></div><p>
TeleGPS is designed to be easy to use. Requiring no external
components, flying takes just a few steps.
</p><p>
First, download and install the software from <a class="ulink" href="http://altusmetrum.org/AltOS" target="_top">http://altusmetrum.org/AltOS</a>. This will make sure that
you have the right device drivers installed.
</p><p>
Next, plug in the battery and USB cable and connect TeleGPS to
your computer. This will charge the battery and allow you to
configure the device.
</p><p>
Start the TeleGPS application and set the callsign and frequency
on your TeleGPS device; refer to the Configure TeleGPS section
in the TeleGPS Application chapter for instructions.
</p><p>
Unplug TeleGPS when the battery charger light goes green. This
will enable the radio and logging portions of the TeleGPS
firmware.
</p><p>
Connect TeleDongle to your computer and start TeleGPS or start
AltosDroid on your android device and connect to TeleBT. Set the
frequency to match the TeleGPS and you should be receiving telemetry.
</p></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp61322976"></a>Chapter 2. Handling Precautions</h1></div></div></div><p>
All Altus Metrum products are sophisticated electronic devices.
When handled gently and properly installed in an air-frame, they
will deliver impressive results. However, as with all electronic
devices, there are some precautions you must take.
</p><p>
The Lithium polymer batteries have an
extraordinary power density. This is great because we can fly with
much less battery mass... but if they are punctured
or their contacts are allowed to short, they can and will release their
energy very rapidly!
Thus we recommend that you take some care when handling TeleGPS
to keep conductive material from coming in contact with the exposed metal elements.
</p><p>
As with all other rocketry electronics, Altus Metrum devices must
be protected from exposure to corrosive motor exhaust and ejection
charge gasses.
</p></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp61325872"></a>Chapter 3. TeleGPS Hardware</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp61326544">1. Hooking Up Lithium Polymer Batteries</a></span></dt><dt><span class="section"><a href="#idp61329472">2. On-board Data Recording</a></span></dt><dt><span class="section"><a href="#idp61333680">3. Installation</a></span></dt></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp61326544"></a>1. Hooking Up Lithium Polymer Batteries</h2></div></div></div><p>
TeleGPS has a two pin JST PH series connector to connect up
a single-cell Lithium Polymer cell (3.7V nominal). You can
purchase matching batteries from the Altus Metrum store, or
other vendors, or you can make your own. Pin 1 of the
connector is positive, pin 2 is negative. Spark Fun sells a
cable with the connector attached, which they call a <a class="ulink" href="https://www.sparkfun.com/products/9914" target="_top">JST Jumper 2
Wire Assembly</a>.
</p><p>
Many RC vendors also sell lithium polymer batteries with
this same connector. All that we have found use the opposite
polarity, and if you use them that way, you will damage or
destroy TeleGPS.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp61329472"></a>2. On-board Data Recording</h2></div></div></div><p>
TeleGPS logs GPS data at a user-configurable rate. Data are
logged to a 2MB on-board flash memory part, which can be
partitioned into several equal-sized blocks, one for each
flight. 64kB of this storage are reserved to hold
configuration data, leaving 1984kB for flight data.
</p><p>
The on-board flash is partitioned into separate flight logs,
each of a fixed maximum size. Increase the maximum size of
each log and you reduce the number of flights that can be
stored. Decrease the size and you can store more flights.
</p><p>
To compute the amount of space needed for a single log, you
can divide the expected time (in seconds) by the sample period
(by default, 1 second per sample) and then multiply the result
by 32 bytes per sample. For instance, a sample period of 1
second and a flight lasting one hour will take 32 * 3600 =
115200 bytes. TeleGPS does try to reduce log space used by not
recording position information when it isn't moving, so actual
space consumed may be less than this.
</p><p>
The default size allows for four flights of 496kB each, which
provides over four hours of logging at 1 sample per second.
</p><p>
TeleGPS will not overwrite existing flight data, so be sure to
download flight data and erase it from the onboard flash
before it fills up. TeleGPS will still report telemetry even
if memory is full, so the only thing you will lose is the
on-board data log.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp61333680"></a>3. Installation</h2></div></div></div><p>
The battery connectors are a standard 2-pin JST connector and
match batteries sold by Spark Fun. These batteries are
single-cell Lithium Polymer batteries that nominally provide 3.7
volts. Other vendors sell similar batteries for RC aircraft
using mating connectors, however the polarity for those is
generally reversed from the batteries used by Altus Metrum
products. In particular, the Tenergy batteries supplied for use
in Featherweight flight computers are not compatible with Altus
Metrum flight computers or battery chargers. <span class="emphasis"><em>Check
polarity and voltage before connecting any battery not purchased
from Altus Metrum or Spark Fun.</em></span>
</p><p>
TeleGPS uses an integrate GPS patch antenna and won't
receive GPS signals if installed inside a metal or carbon
fiber compartment. Test GPS reception and telemetry
transmission with the system installed and all other
electronics powered up to verify signal reception and make
sure there isn't any interference from other systems.
</p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp60611120"></a>Chapter 4. System Operation</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp60611792">1. GFSK Telemetry</a></span></dt><dt><span class="section"><a href="#idp60614720">2. APRS</a></span></dt><dt><span class="section"><a href="#idp60452976">3. Configurable Parameters</a></span></dt><dd><dl><dt><span class="section"><a href="#idp60454304">3.1. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp60456432">3.2. Callsign</a></span></dt><dt><span class="section"><a href="#idp60457616">3.3. Telemetry/RDF/APRS Enable</a></span></dt><dt><span class="section"><a href="#idp60458944">3.4. APRS Interval</a></span></dt><dt><span class="section"><a href="#idp60460448">3.5. Maximum Flight Log</a></span></dt><dt><span class="section"><a href="#idp60462048">3.6. Logging Trigger Motion</a></span></dt><dt><span class="section"><a href="#idp60463376">3.7. Position Reporting Interval</a></span></dt></dl></dd></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp60611792"></a>1. GFSK Telemetry</h2></div></div></div><p>
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.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp60614720"></a>2. APRS</h2></div></div></div><p>
TeleGPS can send APRS if desired, and the
interval between APRS packets can be configured. As each APRS
packet takes a full second to transmit, we recommend an
interval of at least 5 seconds to avoid consuming too much
battery power or radio channel bandwidth. You can configure
the APRS interval using AltosUI; that process is described in
the Configure Altimeter section of the AltosUI chapter.
</p><p>
AltOS uses the APRS compressed position report data format,
which provides for higher position precision and shorter
packets than the original APRS format. It also includes
altitude data, which is invaluable when tracking rockets. We
haven't found a receiver which doesn't handle compressed
positions, but it's just possible that you have one, so if you
have an older device that can receive the raw packets but
isn't displaying position information, it's possible that this
is the cause.
</p><p>
The APRS packet format includes a comment field that can have
arbitrary text in it. AltOS uses this to send status
information about the flight computer. It sends four fields as
shown in the following table.
</p><div class="table"><a name="idp60617744"></a><p class="title"><b>Table 4.1. Altus Metrum APRS Comments</b></p><div class="table-contents"><table summary="Altus Metrum APRS Comments" border="1"><colgroup><col align="center" class="Field"><col align="center" class="Example"><col align="center" class="Description"></colgroup><thead><tr><th align="center">Field</th><th align="center">Example</th><th align="center">Description</th></tr></thead><tbody><tr><td align="center">1</td><td align="center">L</td><td align="center">GPS Status U for unlocked, L for locked</td></tr><tr><td align="center">2</td><td align="center">6</td><td align="center">Number of Satellites in View</td></tr><tr><td align="center">3</td><td align="center">B4.0</td><td align="center">Battery Voltage</td></tr></tbody></table></div></div><br class="table-break"><p>
Here's an example of an APRS comment showing GPS lock with 6
satellites in view and a battery at 4.0V.
</p><pre class="screen">
L6 B4.0
</pre><p>
</p><p>
Make sure your primary battery is above 3.8V and GPS is locked
with at least 5 or 6 satellites in view before starting. If GPS
is switching between L and U regularly, then it doesn't have a
good lock and you should wait until it becomes stable.
</p><p>
If the GPS receiver loses lock, the APRS data transmitted will
contain the last position for which GPS lock was
available. You can tell that this has happened by noticing
that the GPS status character switches from 'L' to 'U'. Before
GPS has locked, APRS will transmit zero for latitude,
longitude and altitude.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp60452976"></a>3. Configurable Parameters</h2></div></div></div><p>
Configuring TeleGPS is very
simple; the few configurable parameters can all be set
using the TeleGPS application over USB. Read
the Configure TeleGPS section in the TeleGPS Software chapter below
for more information.
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp60454304"></a>3.1. Radio Frequency</h3></div></div></div><p>
Altus Metrum boards support radio frequencies in the 70cm
band. By default, the configuration interface provides a
list of 10 “standard” frequencies in 100kHz channels starting at
434.550MHz. However, the firmware supports use of
any 50kHz multiple within the 70cm band. At any given
launch, we highly recommend coordinating when and by whom each
frequency will be used to avoid interference. And of course, both
TeleGPS and the receiver must be configured to the same
frequency to successfully communicate with each other.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp60456432"></a>3.2. Callsign</h3></div></div></div><p>
This sets the callsign used for telemetry and APRS to
identify the device.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp60457616"></a>3.3. Telemetry/RDF/APRS Enable</h3></div></div></div><p>
You can completely disable the radio, if necessary, leaving
TeleGPS only logging data to internal memory.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp60458944"></a>3.4. APRS Interval</h3></div></div></div><p>
This selects how often APRS packets are transmitted. Set
this to zero to disable APRS without also disabling the
regular telemetry and RDF transmissions. As APRS takes a
full second to transmit a single position report, we
recommend sending packets no more than once every 5 seconds.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp60460448"></a>3.5. Maximum Flight Log</h3></div></div></div><p>
Changing this value will set the maximum amount of flight
log storage that an individual flight will use. The
available storage is divided into as many flights of the
specified size as can fit in the available space. You can
download and erase individual flight logs. If you fill up
the available storage, future flights will not get logged
until you erase some of the stored ones.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp60462048"></a>3.6. Logging Trigger Motion</h3></div></div></div><p>
If TeleGPS moves less than this distance over a long period
of time, it will not log that location, saving storage space.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp60463376"></a>3.7. Position Reporting Interval</h3></div></div></div><p>
This sets how often TeleGPS reports position information via
telemetry and to the on-board log. Reducing this value will
save power and logging memory consumption.
</p></div></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp60465024"></a>Chapter 5. TeleGPS Application</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp60466608">1. Telemetry Monitoring</a></span></dt><dd><dl><dt><span class="section"><a href="#idp65947584">1.1. Map</a></span></dt><dt><span class="section"><a href="#idp65953616">1.2. Location</a></span></dt><dt><span class="section"><a href="#idp65956928">1.3. Status</a></span></dt><dt><span class="section"><a href="#idp65960480">1.4. Table</a></span></dt></dl></dd><dt><span class="section"><a href="#idp65964528">2. TeleGPS Menus</a></span></dt><dd><dl><dt><span class="section"><a href="#idp65972624">2.1. New Window</a></span></dt><dt><span class="section"><a href="#idp65973952">2.2. Graph Data</a></span></dt><dt><span class="section"><a href="#idp65990624">2.3. Export Data</a></span></dt><dt><span class="section"><a href="#idp65996688">2.4. Load Maps</a></span></dt><dt><span class="section"><a href="#idp66010688">2.5. Preferences</a></span></dt><dt><span class="section"><a href="#idp66031072">2.6. Close</a></span></dt><dt><span class="section"><a href="#idp66032368">2.7. Exit</a></span></dt><dt><span class="section"><a href="#idp66033632">2.8. Connect Device</a></span></dt><dt><span class="section"><a href="#idp66037296">2.9. Disconnect</a></span></dt><dt><span class="section"><a href="#idp66038560">2.10. Scan Channels</a></span></dt><dt><span class="section"><a href="#idp66042240">2.11. Download Data</a></span></dt><dt><span class="section"><a href="#idp66045408">2.12. Configure Device</a></span></dt><dt><span class="section"><a href="#idp64831824">2.13. Flash Device</a></span></dt></dl></dd></dl></div><p>
The TeleGPS application provides a graphical user interface for
interacting with the Altus Metrum product family. TeleGPS can
monitor telemetry data, configure devices and many other
tasks. The primary interface window is for displaying data
received over the telemetry link. There are additional
tasks available from the main window menu bar. This chapter
is split into sections, each of which documents one of the tasks
provided from the top-level toolbar.
</p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp60466608"></a>1. Telemetry Monitoring</h2></div></div></div><p>
This is the window brought up when you start the
application. If you have a TeleDongle device connected to the
computer, it will automatically be selected for telemetry monitoring
</p><p>
All telemetry data received are automatically recorded in
suitable log files. The name of the files includes the current
date and TeleGPS serial and flight numbers.
</p><p>
The radio frequency being monitored by the TeleDongle device
is displayed at the top of the window. You can configure the
frequency by clicking on the frequency box and selecting the
desired frequency. The TeleGPS application remembers the last
frequency selected for each TeleDongle and selects that
automatically the next time you use that device.
</p><p>
Below the TeleDongle frequency selector, the window contains a few
significant pieces of information about the altimeter providing
the telemetry data stream:
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>The configured call-sign</p></li><li class="listitem"><p>The device serial number</p></li><li class="listitem"><p>The flight number. TeleGPS remembers how many
times it has flown.
</p></li><li class="listitem"><p>
The Received Signal Strength Indicator value. This lets
you know how strong a signal TeleDongle is receiving. The
radio inside TeleDongle operates down to about -100dBm;
weaker signals may not be receivable. The packet link uses
error detection and correction techniques which prevent
incorrect data from being reported.
</p></li><li class="listitem"><p>
The age of the displayed data, in seconds since the last
successfully received telemetry packet. In normal operation
this will stay in the low single digits. If the number starts
counting up, then you are no longer receiving data over the radio
link from the flight computer.
</p></li></ul></div><p>
Finally, the largest portion of the window contains a set of
tabs, each of which contain some information about the TeleGPS
board. The final 'table' tab displays many of the raw telemetry
values in one place in a spreadsheet-like format.
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp65947584"></a>1.1. Map</h3></div></div></div><p>
The Map tab shows the TeleGPS track over time on top of map
data making it easy to locate the device.
</p><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="495"><tr><td><img src="telegps-map.png" width="495"></td></tr></table></div></div><p>
The map's default scale is approximately 3m (10ft) per pixel. The map
can be dragged using the left mouse button. The map will attempt
to keep the rocket roughly centered while data is being received.
</p><p>
You can adjust the style of map and the zoom level with
buttons on the right side of the map window. You can draw a
line on the map by moving the mouse over the map with a
button other than the left one pressed, or by pressing the
left button while also holding down the shift key. The
length of the line in real-world units will be shown at the
start of the line.
</p><p>
Images are fetched automatically via the Google Maps Static API,
and cached on disk for reuse. If map images cannot be downloaded,
the rocket's path will be traced on a dark gray background
instead.
</p><p>
You can pre-load images for your favorite launch sites
before you leave home; check out the 'Preload Maps' section below.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp65953616"></a>1.2. Location</h3></div></div></div><p>
The Location tab shows the raw GPS data received from TeleGPS.
</p><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="495"><tr><td><img src="telegps-location.png" width="495"></td></tr></table></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp65956928"></a>1.3. Status</h3></div></div></div><p>
The Status tab shows data relative to the location of
TeleGPS when the application first received telemetry from
it.
</p><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="495"><tr><td><img src="telegps-status.png" width="495"></td></tr></table></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp65960480"></a>1.4. Table</h3></div></div></div><p>
The Table tab shows detailed information about the GPS
receiver
</p><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="495"><tr><td><img src="telegps-table.png" width="495"></td></tr></table></div></div></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp65964528"></a>2. TeleGPS Menus</h2></div></div></div><p>
TeleGPS has three or four menus at the top of the window:
</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">File</span></dt><dd><p>
New Window, Graph Data, Export Data, Load Maps, Preferences, Close and Exit
</p></dd><dt><span class="term">Monitor</span></dt><dd><p>
Connect Device, Disconnect and Scan Channels
</p></dd><dt><span class="term">Device</span></dt><dd><p>
Download Data, Configure Device and Flash Device
</p></dd><dt><span class="term">Frequency</span></dt><dd><p>
This shows the current monitoring frequency with a
drop-down menu listing other configured
frequencies. You can change the set of frequencies
shown here from the Preferences dialog. This menu is
only shown when the TeleGPS application is connected
to a TeleDongle or TeleBT device.
</p></dd></dl></div><p>
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp65972624"></a>2.1. New Window</h3></div></div></div><p>
This creates another telemetry monitoring window, in case
you have multiple TeleDongle devices connected to the
computer.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp65973952"></a>2.2. Graph Data</h3></div></div></div><p>
This brings up a file dialog to load a saved log, either
a .telem file of recorded telemetry or .eeprom of saved
data from on-board memory. It looks a bit like the flight
monitoring window, using a selection of tabs to show
different views of the saved data.
</p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp65975296"></a>2.2.1. Graph</h4></div></div></div><p>
The Graph tab shows a plot of the the GPS data
collected. The X axis is time in seconds; there are a
variety of Y axes available for different kinds of data.
</p><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="540"><tr><td><img src="telegps-graph-graph.png" width="540"></td></tr></table></div></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp65979104"></a>2.2.2. Configure Graph</h4></div></div></div><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="540"><tr><td><img src="telegps-graph-configure.png" width="540"></td></tr></table></div></div><p>
This selects which graph elements to show, and, at the
bottom, lets you switch between metric and imperial units
</p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp65982880"></a>2.2.3. Statistics</h4></div></div></div><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="540"><tr><td><img src="telegps-graph-stats.png" width="540"></td></tr></table></div></div><p>
Shows overall data computed from the flight.
</p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp65986496"></a>2.2.4. Map</h4></div></div></div><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="540"><tr><td><img src="telegps-graph-map.png" width="540"></td></tr></table></div></div><p>
Shows a map of the area overlaid with the GPS track. As with
the telemetry monitoring window, you can select the style
of map and zoom level using buttons along the side;
you can scroll the map by dragging within the map pressing
the left button and you can draw a line to measure
distances using either the left button with the shift key,
or any other button.
</p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp65990624"></a>2.3. Export Data</h3></div></div></div><p>
This tool takes the raw data files and makes them available for
external analysis. When you select this button, you are prompted to
select a data file, which can be either a .eeprom or .telem.
The .eeprom files contain higher resolution and more continuous data,
while .telem files contain receiver signal strength information.
Next, a second dialog appears which is used to select
where to write the resulting file. It has a selector to choose
between CSV and KML file formats.
</p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp65992768"></a>2.3.1. Comma Separated Value Format</h4></div></div></div><p>
This is a text file containing the data in a form suitable for
import into a spreadsheet or other external data analysis
tool. The first few lines of the file contain the version and
configuration information from TeleGPS, then
there is a single header line which labels all of the
fields. All of these lines start with a '#' character which
many tools can be configured to skip over.
</p><p>
The remaining lines of the file contain the data, with each
field separated by a comma and at least one space. All of
the sensor values are converted to standard units, with the
barometric data reported in both pressure, altitude and
height above pad units.
</p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp65995200"></a>2.3.2. Keyhole Markup Language (for Google Earth)</h4></div></div></div><p>
This is the format used by Google Earth to provide an overlay
within that application. With this, you can use Google Earth to
see the whole flight path in 3D.
</p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp65996688"></a>2.4. Load Maps</h3></div></div></div><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="468"><tr><td><img src="load-maps.png" width="468"></td></tr></table></div></div><p>
Before using TeleGPS, you can use Load Maps to load map data
in case you don't have access to the internet while
receiving telemetry.
</p><p>
There's a drop-down menu of rocket launch sites we know
about; if your favorites aren't there, please let us know
the lat/lon and name of the site. The contents of this list
are actually downloaded from our server at run-time, so as
new sites are sent in, they'll get automatically added to
this list. If the launch site isn't in the list, you can
manually enter the lat/lon values
</p><p>
There are four different kinds of maps you can view; you can
select which to download by selecting as many as you like from
the available types:
</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">Hybrid</span></dt><dd><p>
A combination of satellite imagery and road data. This
is the default view.
</p></dd><dt><span class="term">Satellite</span></dt><dd><p>
Just the satellite imagery without any annotation.
</p></dd><dt><span class="term">Roadmap</span></dt><dd><p>
Roads, political boundaries and a few geographic features.
</p></dd><dt><span class="term">Terrain</span></dt><dd><p>
Contour intervals and shading that show hills and
valleys.
</p></dd></dl></div><p>
</p><p>
You can specify the range of zoom levels to download; smaller
numbers show more area with less resolution. The default
level, 0, shows about 3m/pixel. One zoom level change
doubles or halves that number.
</p><p>
The Tile Radius value sets how large an area around the center
point to download. Each tile is 512x512 pixels, and the
'radius' value specifies how many tiles away from the center
will be downloaded. Specify a radius of 0 and you get only the
center tile. A radius of 1 loads a 3x3 grid, centered on the
specified location.
</p><p>
Clicking the 'Load Map' button will fetch images from Google
Maps; note that Google limits how many images you can fetch at
once, so if you load more than one launch site, you may get
some gray areas in the map which indicate that Google is tired
of sending data to you. Try again later.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp66010688"></a>2.5. Preferences</h3></div></div></div><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="216"><tr><td><img src="telegps-preferences.png" width="216"></td></tr></table></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp66013824"></a>2.5.1. Voice Settings</h4></div></div></div><p>
AltosUI provides voice announcements during flight so that you
can keep your eyes on the sky and still get information about
the current flight status. However, sometimes you don't want
to hear them.
</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">Enable</span></dt><dd><p>Turns all voice announcements on and off</p></dd><dt><span class="term">Test Voice</span></dt><dd><p>
Plays a short message allowing you to verify
that the audio system is working and the volume settings
are reasonable
</p></dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp66018944"></a>2.5.2. Log Directory</h4></div></div></div><p>
AltosUI logs all telemetry data and saves all TeleMetrum flash
data to this directory. This directory is also used as the
staring point when selecting data files for display or export.
</p><p>
Click on the directory name to bring up a directory choosing
dialog, select a new directory and click 'Select Directory' to
change where AltosUI reads and writes data files.
</p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp66021008"></a>2.5.3. Callsign</h4></div></div></div><p>
This value is transmitted in each command packet sent from
TeleDongle and received from an altimeter. It is not used in
telemetry mode, as the callsign configured in the altimeter board
is included in all telemetry packets. Configure this
with the AltosUI operators call sign as needed to comply with
your local radio regulations.
</p><p>
Note that to successfully command a flight computer over the radio
(to configure the altimeter, monitor idle, or fire pyro charges),
the callsign configured here must exactly match the callsign
configured in the flight computer. This matching is case
sensitive.
</p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp66023312"></a>2.5.4. Imperial Units</h4></div></div></div><p>
This switches between metric units (meters) and imperial
units (feet and miles). This affects the display of values
use during flight monitoring, configuration, data graphing
and all of the voice announcements. It does not change the
units used when exporting to CSV files, those are always
produced in metric units.
</p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp66024864"></a>2.5.5. Serial Debug</h4></div></div></div><p>
This causes all communication with a connected device to be
dumped to the console from which AltosUI was started. If
you've started it from an icon or menu entry, the output
will simply be discarded. This mode can be useful to debug
various serial communication issues.
</p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp66026400"></a>2.5.6. Font Size</h4></div></div></div><p>
Selects the set of fonts used in the flight monitor
window. Choose between the small, medium and large sets.
</p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp66027728"></a>2.5.7. Look & Feel</h4></div></div></div><p>
Adjust the style of the windows. By default, the TeleGPS
application attempts to blend in with the native style.
</p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp66029056"></a>2.5.8. Manage Frequencies</h4></div></div></div><p>
This brings up a dialog where you can configure the set of
frequencies shown in the various frequency menus. You can
add as many as you like, or even reconfigure the default
set. Changing this list does not affect the frequency
settings of any devices, it only changes the set of
frequencies shown in the menus.
</p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp66031072"></a>2.6. Close</h3></div></div></div><p>
This closes the current window, leaving any other windows
open and the application running.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp66032368"></a>2.7. Exit</h3></div></div></div><p>
This closes all TeleGPS windows and terminates the application.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp66033632"></a>2.8. Connect Device</h3></div></div></div><p>
Selecting this item brings up a dialog box listing all of
the connected TeleDongle devices. When you choose one of
these, AltosUI will display telemetry data as received by
the selected TeleDongle device.
</p><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="279"><tr><td><img src="device-selection.png" width="279"></td></tr></table></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp66037296"></a>2.9. Disconnect</h3></div></div></div><p>
Disconnects the currently connected TeleDongle or TeleBT
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp66038560"></a>2.10. Scan Channels</h3></div></div></div><p>
Scans the configured set of frequencies looking for
telemetry signals. A list of all of the discovered signals
is show; selecting one of those and clicking on 'Monitor'
will select that frequency in the associated TeleGPS
application window.
</p><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="279"><tr><td><img src="telegps-scan.png" width="279"></td></tr></table></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp66042240"></a>2.11. Download Data</h3></div></div></div><p>
TeleGPS records data to its internal flash memory.
On-board data is recorded at the same rate as telemetry
but is not subject to radio drop-outs. As
such, it generally provides a more complete and precise record.
The 'Download Data' menu entry allows you to read the
flash memory and write it to disk.
</p><p>
Select the 'Download Data' menu entry to bring up a list of
connected TeleGPS devices. After the device has been
selected, a dialog showing the data stored in the
device will be shown allowing you to select which entries to
download and which to delete. You must erase flights in order for the space they
consume to be reused by another track. This prevents
accidentally losing data if you neglect to download
data before starting TeleGPS again. Note that if there is no more
space available in the device, then no data will be recorded.
</p><p>
The file name for each data log is computed automatically
from the recorded date, altimeter serial number and flight
number information.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp66045408"></a>2.12. Configure Device</h3></div></div></div><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="324"><tr><td><img src="telegps-configure.png" width="324"></td></tr></table></div></div><p>
Select this button and then select any connected TeleGPS
device from the list provided.
</p><p>
The first few lines of the dialog provide information about the
connected device, including the product name,
software version and hardware serial number. Below that are the
individual configuration entries.
</p><p>
At the bottom of the dialog, there are four buttons:
</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">Save</span></dt><dd><p>
This writes any changes to the
configuration parameter block in flash memory. If you don't
press this button, any changes you make will be lost.
</p></dd><dt><span class="term">Reset</span></dt><dd><p>
This resets the dialog to the most recently saved values,
erasing any changes you have made.
</p></dd><dt><span class="term">Reboot</span></dt><dd><p>
This reboots the device. This will restart logging for
a new flight number, if any log information has been
saved for the current flight.
</p></dd><dt><span class="term">Close</span></dt><dd><p>
This closes the dialog. Any unsaved changes will be
lost.
</p></dd></dl></div><p>
The rest of the dialog contains the parameters to be configured.
</p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp63831792"></a>2.12.1. Frequency</h4></div></div></div><p>
This configures which of the frequencies to use for both
telemetry and packet command mode. Note that if you set this
value via packet command mode, the TeleDongle frequency will
also be automatically reconfigured to match so that
communication will continue afterwards.
</p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp63587264"></a>2.12.2. RF Calibration</h4></div></div></div><p>
The radios in every Altus Metrum device are calibrated at the
factory to ensure that they transmit and receive on the
specified frequency. If you need to you can adjust the calibration
by changing this value. Do not do this without understanding what
the value means, read the appendix on calibration and/or the source
code for more information. To change a TeleDongle's calibration,
you must reprogram the unit completely.
</p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp64336224"></a>2.12.3. Telemetry/RDF/APRS Enable</h4></div></div></div><p>
Enables the radio for transmission during flight. When
disabled, the radio will not transmit anything during flight
at all.
</p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp62178976"></a>2.12.4. APRS Interval</h4></div></div></div><p>
How often to transmit GPS information via APRS (in
seconds). When set to zero, APRS transmission is
disabled. This option is available on TeleMetrum v2 and
TeleMega boards. TeleMetrum v1 boards cannot transmit APRS
packets. Note that a single APRS packet takes nearly a full
second to transmit, so enabling this option will prevent
sending any other telemetry during that time.
</p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp63605184"></a>2.12.5. Callsign</h4></div></div></div><p>
This sets the call sign included in each telemetry packet. Set this
as needed to conform to your local radio regulations.
</p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp64195792"></a>2.12.6. Maximum Log Size</h4></div></div></div><p>
This sets the space (in kilobytes) allocated for each data
log. The available space will be divided into chunks of this
size. A smaller value will allow more logs to be stored,
a larger value will record data for longer times.
</p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp63537840"></a>2.12.7. Logging Trigger Motion</h4></div></div></div><p>
If TeleGPS moves less than this distance over a long period
of time, it will not log that location, saving storage space.
</p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp63009520"></a>2.12.8. Position Reporting Interval</h4></div></div></div><p>
This sets how often TeleGPS reports position information via
telemetry and to the on-board log. Reducing this value will
save power and logging memory consumption.
</p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp64831824"></a>2.13. Flash Device</h3></div></div></div><p>
This reprograms TeleGPS devices with new firmware. Please
read the directions for flashing devices in the Updating
Device Firmware chapter below.
</p></div></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp63308272"></a>Chapter 6. Updating Device Firmware</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp66058400">1.
Updating TeleGPS Firmware
</a></span></dt></dl></div><p>
TeleGPS is programmed directly over its USB connectors.
</p><p>
You may wish to begin by ensuring you have current firmware images.
These are distributed as part of the TeleGPS software bundle that
also includes the TeleGPS ground station program. Newer ground
station versions typically work fine with older firmware versions,
so you don't need to update your devices just to try out new
software features. You can always download the most recent
version from <a class="ulink" href="http://www.altusmetrum.org/AltOS/" target="_top">http://www.altusmetrum.org/AltOS/</a>.
</p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp66058400"></a>1.
Updating TeleGPS Firmware
</h2></div></div></div><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>
Attach a battery and power switch to the target
device. Power up the device.
</p></li><li class="listitem"><p>
Using a Micro USB cable, connect the target device to your
computer's USB socket.
</p></li><li class="listitem"><p>
Run TeleGPS, and select 'Flash Device' from the Device menu.
</p></li><li class="listitem"><p>
Select the target device in the Device Selection dialog.
</p></li><li class="listitem"><p>
Select the image you want to flash to the device, which
should have a name in the form
<product>-v<product-version>-<software-version>.ihx, such
as TeleGPS-v1.0-1.4.0.ihx.
</p></li><li class="listitem"><p>
Make sure the configuration parameters are reasonable
looking. If the serial number and/or RF configuration
values aren't right, you'll need to change them.
</p></li><li class="listitem"><p>
Hit the 'OK' button and the software should proceed to flash
the device with new firmware, showing a progress bar.
</p></li><li class="listitem"><p>
Verify that the device is working by using the 'Configure
Altimeter' item to check over the configuration.
</p></li></ol></div></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp66067760"></a>Chapter 7. Technical Information</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp66068432">1. GPS Receiver</a></span></dt><dt><span class="section"><a href="#idp66071744">2. Micro-controller</a></span></dt><dt><span class="section"><a href="#idp66073072">3. Lithium Polymer Battery</a></span></dt><dt><span class="section"><a href="#idp66074336">4. Mechanical Considerations</a></span></dt><dt><span class="section"><a href="#idp66075664">5. On-board data storage</a></span></dt></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp66068432"></a>1. GPS Receiver</h2></div></div></div><p>
TeleGPS uses the u-Blox Max-7Q GPS receiver.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp66071744"></a>2. Micro-controller</h2></div></div></div><p>
TeleGPS uses an NXP LPC11U14 micro-controller. This tiny
CPU contains 32kB of flash for the application and 4kB of RAM for
temporary data storage.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp66073072"></a>3. Lithium Polymer Battery</h2></div></div></div><p>
Shipping restrictions may prevent us from including a battery
battery with TeleGPS.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp66074336"></a>4. Mechanical Considerations</h2></div></div></div><p>
TeleGPS is designed to be rugged enough for typical rocketry
applications. The 4 mounting holes on the board are sized for
use with 4-40 or M3 screws.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp66075664"></a>5. On-board data storage</h2></div></div></div><p>
TeleGPS has 2MB of non-volatile storage, separate from the
code storage memory. The TeleGPS firmware uses this to log
information during flight.
</p></div></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a name="idp66077120"></a>Appendix A. Release Notes</h1></div></div></div><div class="simplesect"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp66077760"></a>Version 1.41</h2></div></div></div><p>
Version 1.4.1 is a minor release. It fixes install issues on
Windows and provides the missing TeleMetrum V2.0 firmware. There
aren't any changes to the firmware or host applications at
all. All Windows users will want to upgrade to get the signed
driver, but Mac and Linux users who do not need the TeleMetrum
V2.0 firmware image will not need to upgrade.
</p><p>
Windows Install Fixes
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Provide signed Windows driver files. This should avoid any need to
disable driver signature checking on Windows 7 or 8.
</p></li><li class="listitem"><p>
Fix Java version detection and download. Previously, the
installer would only look for Java 6 or 7 and insist on
downloading its own Java bits if there was something else
installed. Furthermore, the 64-bit Java link provided didn't
work for anyone other than Keith, making it impossible to
install AltOS on any machine with Java SE 8 installed.
</p></li></ul></div><p>
</p><p>
Other Fixes
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Include 1.4 firmware for TeleMetrum V2.0. None of the
installers shipped this file. Now it's included in the AltOS
packages for Linux, Mac and Windows.
</p></li><li class="listitem"><p>
Include Google Application Key for map downloading. The 1.4
release didn't have this key in the released version of the
software, making map downloading fail for most people.
</p></li></ul></div><p>
</p></div><div class="simplesect"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp66079360"></a>Version 1.4</h2></div></div></div><p>
Version 1.4 is a major release. It includes support for our new
TeleGPS product, new features and bug fixes in in the flight
software for all our boards and the AltosUI ground station
</p><p>
AltOS New Features
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Add support for TeleGPS boards.
</p></li><li class="listitem"><p>
Replace the 'dit dit dit' tones at startup with the current
battery voltage, measured in tenths of a volt. This lets you
check the battery voltage without needing telemetry, which
is especially useful on EasyMini.
</p></li><li class="listitem"><p>
Change state beeping to "Farnsworth spacing", which means
they're quite a bit faster than before, and so they take
less time to send.
</p></li><li class="listitem"><p>
Make the beeper tone configurable, making it possible to
distinguish between two Altus Metrum products in the same ebay.
</p></li><li class="listitem"><p>
Make the firing time for extra pyro channels configurable,
allowing longer (or shorter) than the default 50ms. Only relevant
for TeleMega at this time.
</p></li></ul></div><p>
</p><p>
AltOS Fixes
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Fix bug preventing the selection of the 'Flight State After'
mode in pyro configuration.
</p></li><li class="listitem"><p>
Fix bug where erasing flights would reset the flight number
to 2 on TeleMega and TeleMetrum v2.
</p></li><li class="listitem"><p>
Fix u-Blox GPS driver to mark course and speed data as being
present.
</p></li></ul></div><p>
</p><p>
AltosUI New Features
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Add zooming and new content types (terrain and road maps) to
map view. Change map storage format from PNG to Jpeg, which
saves a huge amount of disk space. You will need to
re-download all of your pre-loaded map images.
</p></li><li class="listitem"><p>
Add a distance measuring device to the maps view. Select
this by using any button other than the left one, or by
pressing shift or control on the keyboard while using the
left button.
</p></li><li class="listitem"><p>
Add new 'Ignitor' tab to the flight monitor display for
TeleMega's extra ignitors.
</p></li><li class="listitem"><p>
Increase the width of data lines in the graphs to make them
easier to read.
</p></li><li class="listitem"><p>
Add additional ignitor firing marks and voltages to the
graph so you can see when the ignitors fired, along with
the ignitor voltages.
</p></li><li class="listitem"><p>
Add GPS course, ground speed and climb rate as optional
graph elements.
</p></li></ul></div><p>
</p><p>
AltosUI Fixes
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
When flashing new firmware, re-try opening the device as
sometimes it takes a while for the underlying operating
system to recognize that the device has rebooted in
preparation for the flashing operation.
</p></li><li class="listitem"><p>
Hide Tilt Angle in ascent tab for devices that don't have a gyro.
</p></li><li class="listitem"><p>
Filter out speed and acceleration spikes caused by ejection
charge firing when computing the maximum values. This
provides a more accurate reading of those maximums.
</p></li><li class="listitem"><p>
Fix EasyMini voltage displays. Early EasyMini prototypes
used a 3.0V regulator, and AltosUI still used that value as
the basis of the computation. Production EasyMini boards
have always shipped with a 3.3V regulator. Also, purple
EasyMini boards sensed the battery voltage past the blocking
diode, resulting in a drop of about 150mV from the true
battery voltage. Compensate for that when displaying the
value.
</p></li><li class="listitem"><p>
Display error message when trying to configure maximum
flight log size while the flight computer still has flight
data stored.
</p></li><li class="listitem"><p>
Handle TeleMetrum and TeleMini eeprom files generated with
pre-1.0 firmware. Those ancient versions didn't report the
log format, so just use the product name instead.
</p></li></ul></div><p>
</p><p>
TeleGPS Application
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
New application designed for use with TeleGPS boards.
</p></li><li class="listitem"><p>
Shares code with AltosUI, mostly just trimmed down to focus
on TeleGPS-related functions.
</p></li></ul></div><p>
</p><p>
Documentation changes
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Re-create the drill template images; they should print
correctly from Firefox at least. Ship these as individual
PDF files so they're easy to print.
</p></li><li class="listitem"><p>
Add a description of the 'Apogee Lockout' setting, which
prevents the apogee charge from firing for a configurable
amount of time after boost.
</p></li></ul></div><p>
</p></div></div></div></body></html>
|
