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
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
1440
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452
1453
1454
1455
1456
1457
1458
1459
1460
1461
1462
1463
1464
1465
1466
1467
1468
1469
1470
1471
1472
1473
1474
1475
1476
1477
1478
1479
1480
1481
1482
1483
1484
1485
1486
1487
1488
1489
1490
1491
1492
1493
1494
1495
1496
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508
1509
1510
1511
1512
1513
1514
1515
1516
1517
1518
1519
1520
1521
1522
1523
1524
1525
1526
1527
1528
1529
1530
1531
1532
1533
1534
1535
1536
1537
1538
1539
1540
1541
1542
1543
1544
1545
1546
1547
1548
1549
1550
1551
1552
1553
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564
1565
1566
1567
1568
1569
1570
1571
1572
1573
1574
1575
1576
1577
1578
1579
1580
1581
1582
1583
1584
1585
1586
1587
1588
1589
1590
1591
1592
1593
1594
1595
1596
1597
1598
1599
1600
1601
1602
1603
1604
1605
1606
1607
1608
1609
1610
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620
1621
1622
1623
1624
1625
1626
1627
1628
1629
1630
1631
1632
1633
1634
1635
1636
1637
1638
1639
1640
1641
1642
1643
1644
1645
1646
1647
1648
1649
1650
1651
1652
1653
1654
1655
1656
1657
1658
1659
1660
1661
1662
1663
1664
1665
1666
1667
1668
1669
1670
1671
1672
1673
1674
1675
1676
1677
1678
1679
1680
1681
1682
1683
1684
1685
1686
1687
1688
1689
1690
1691
1692
1693
1694
1695
1696
1697
1698
1699
1700
1701
1702
1703
1704
1705
1706
1707
1708
1709
1710
1711
1712
1713
1714
1715
1716
1717
1718
1719
1720
1721
1722
1723
1724
1725
1726
1727
1728
1729
1730
1731
1732
1733
1734
1735
1736
1737
1738
1739
1740
1741
1742
1743
1744
1745
1746
1747
1748
1749
1750
1751
1752
1753
1754
1755
1756
1757
1758
1759
1760
1761
1762
1763
1764
1765
1766
1767
1768
1769
1770
1771
1772
1773
1774
1775
1776
1777
1778
1779
1780
1781
1782
1783
1784
1785
1786
1787
1788
1789
1790
1791
1792
1793
1794
1795
1796
1797
1798
1799
1800
1801
1802
1803
1804
1805
1806
1807
1808
1809
1810
1811
1812
1813
1814
1815
1816
1817
1818
1819
1820
1821
1822
1823
1824
1825
1826
1827
1828
1829
1830
1831
1832
1833
1834
1835
1836
1837
1838
1839
1840
1841
1842
1843
1844
1845
1846
1847
1848
1849
1850
1851
1852
1853
1854
1855
1856
1857
1858
1859
1860
1861
1862
1863
1864
1865
1866
1867
1868
1869
1870
1871
1872
1873
1874
1875
1876
1877
1878
1879
1880
1881
1882
1883
1884
1885
1886
1887
1888
1889
1890
1891
1892
1893
1894
1895
1896
1897
1898
1899
1900
1901
1902
1903
1904
1905
1906
1907
1908
1909
1910
1911
1912
1913
1914
1915
1916
1917
1918
1919
1920
1921
1922
1923
1924
1925
1926
1927
1928
1929
1930
1931
1932
1933
1934
1935
1936
1937
1938
1939
1940
1941
1942
1943
1944
1945
1946
1947
1948
1949
1950
1951
1952
1953
1954
1955
1956
1957
1958
1959
1960
1961
1962
1963
1964
1965
1966
1967
1968
1969
1970
1971
1972
1973
1974
1975
1976
1977
1978
1979
1980
1981
1982
1983
1984
1985
1986
1987
1988
1989
1990
1991
1992
1993
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
2027
2028
2029
2030
2031
2032
2033
2034
2035
2036
2037
2038
2039
2040
2041
2042
2043
2044
2045
2046
2047
2048
2049
2050
2051
2052
2053
2054
2055
2056
2057
2058
2059
2060
2061
2062
2063
2064
2065
2066
2067
2068
2069
2070
2071
2072
2073
2074
2075
2076
2077
2078
2079
2080
2081
2082
2083
2084
2085
2086
2087
2088
2089
2090
2091
2092
2093
2094
2095
2096
2097
2098
2099
2100
2101
2102
2103
2104
2105
2106
2107
2108
2109
2110
2111
2112
2113
2114
2115
2116
2117
2118
2119
2120
2121
2122
2123
2124
2125
2126
2127
2128
2129
2130
2131
2132
2133
2134
2135
2136
2137
2138
2139
2140
2141
2142
2143
2144
2145
2146
2147
2148
2149
2150
2151
2152
2153
2154
2155
2156
2157
2158
2159
2160
2161
2162
2163
2164
2165
2166
2167
2168
2169
2170
2171
2172
2173
2174
2175
2176
2177
2178
2179
2180
2181
2182
2183
2184
2185
2186
2187
2188
2189
2190
2191
2192
2193
2194
2195
2196
2197
2198
2199
2200
2201
2202
2203
2204
2205
2206
2207
2208
2209
2210
2211
2212
2213
2214
2215
2216
2217
2218
2219
2220
2221
2222
2223
2224
2225
2226
2227
2228
2229
2230
2231
2232
2233
2234
2235
2236
2237
2238
2239
2240
2241
2242
2243
2244
2245
2246
2247
2248
2249
2250
2251
2252
2253
2254
2255
2256
2257
2258
2259
2260
2261
2262
2263
2264
2265
2266
2267
2268
2269
2270
2271
2272
2273
2274
2275
2276
2277
2278
2279
2280
2281
2282
2283
2284
2285
2286
2287
2288
2289
2290
2291
2292
2293
2294
2295
2296
2297
2298
2299
2300
2301
2302
2303
2304
2305
2306
2307
2308
2309
2310
2311
2312
2313
2314
2315
2316
2317
2318
2319
2320
2321
2322
2323
2324
2325
2326
2327
2328
2329
2330
2331
2332
2333
2334
2335
2336
2337
2338
2339
2340
2341
2342
2343
2344
2345
2346
2347
2348
2349
2350
2351
2352
2353
2354
2355
2356
2357
2358
2359
2360
2361
2362
2363
2364
2365
2366
2367
2368
2369
2370
2371
2372
2373
2374
2375
2376
2377
2378
2379
2380
2381
2382
2383
2384
2385
2386
2387
2388
2389
2390
2391
2392
2393
2394
2395
2396
2397
2398
2399
2400
2401
2402
2403
2404
2405
2406
2407
2408
2409
2410
2411
2412
2413
2414
2415
2416
2417
2418
2419
2420
2421
2422
2423
2424
2425
2426
2427
2428
2429
2430
2431
2432
2433
2434
2435
2436
2437
2438
2439
2440
2441
2442
2443
2444
2445
2446
2447
2448
2449
2450
2451
2452
2453
2454
2455
2456
2457
2458
2459
2460
2461
2462
2463
2464
2465
2466
2467
2468
2469
2470
2471
2472
2473
2474
2475
2476
2477
2478
2479
2480
2481
2482
2483
2484
2485
2486
2487
2488
2489
2490
2491
2492
2493
2494
2495
2496
2497
2498
2499
2500
2501
2502
2503
2504
2505
2506
2507
2508
2509
2510
2511
2512
2513
2514
2515
2516
2517
2518
2519
2520
2521
2522
2523
2524
2525
2526
2527
2528
2529
2530
2531
2532
2533
2534
2535
2536
2537
2538
2539
2540
2541
2542
2543
2544
2545
2546
2547
2548
2549
2550
2551
2552
2553
2554
2555
2556
2557
2558
2559
2560
2561
2562
2563
2564
2565
2566
2567
2568
2569
2570
2571
2572
2573
2574
2575
2576
2577
2578
2579
2580
2581
2582
2583
2584
2585
2586
2587
2588
2589
2590
2591
2592
2593
2594
2595
2596
2597
2598
2599
2600
2601
2602
2603
2604
2605
2606
2607
2608
2609
2610
2611
2612
2613
2614
2615
2616
2617
2618
2619
2620
2621
2622
2623
2624
2625
2626
2627
2628
2629
2630
2631
2632
2633
2634
2635
2636
2637
2638
2639
2640
2641
2642
2643
2644
2645
2646
2647
2648
2649
2650
2651
2652
2653
2654
2655
2656
2657
2658
2659
2660
2661
2662
2663
2664
2665
2666
2667
2668
2669
2670
2671
2672
2673
2674
2675
2676
2677
2678
2679
2680
2681
2682
2683
2684
2685
2686
2687
2688
2689
2690
2691
2692
2693
2694
2695
2696
2697
2698
2699
2700
2701
2702
2703
2704
2705
2706
2707
2708
2709
2710
2711
2712
2713
2714
2715
2716
2717
2718
2719
2720
2721
2722
2723
2724
2725
2726
2727
2728
2729
2730
2731
2732
2733
2734
2735
2736
2737
2738
2739
2740
2741
2742
2743
2744
2745
2746
2747
2748
2749
2750
2751
2752
2753
2754
2755
2756
2757
2758
2759
2760
2761
2762
2763
2764
2765
2766
2767
2768
2769
2770
2771
2772
2773
2774
2775
2776
2777
2778
2779
2780
2781
2782
2783
2784
2785
2786
2787
2788
2789
2790
2791
2792
2793
2794
2795
2796
2797
2798
2799
2800
2801
2802
2803
2804
2805
2806
2807
2808
2809
2810
2811
2812
2813
2814
2815
2816
2817
2818
2819
2820
2821
2822
2823
2824
2825
2826
2827
2828
2829
2830
2831
2832
2833
2834
2835
2836
2837
2838
2839
2840
2841
2842
2843
2844
2845
2846
2847
2848
2849
2850
2851
2852
2853
2854
2855
2856
2857
2858
2859
2860
2861
2862
2863
2864
2865
2866
2867
2868
2869
2870
2871
2872
2873
2874
2875
2876
2877
2878
2879
2880
2881
2882
2883
2884
2885
2886
2887
2888
2889
2890
2891
2892
2893
2894
2895
2896
2897
2898
2899
2900
2901
2902
2903
2904
2905
2906
2907
2908
2909
2910
2911
2912
2913
2914
2915
2916
2917
2918
2919
2920
2921
2922
2923
2924
2925
2926
2927
2928
2929
2930
2931
2932
2933
2934
2935
2936
2937
2938
2939
2940
2941
2942
2943
2944
2945
2946
2947
2948
2949
2950
2951
2952
2953
2954
2955
2956
2957
2958
2959
2960
2961
2962
2963
2964
2965
2966
2967
2968
2969
2970
2971
2972
2973
2974
2975
2976
2977
2978
2979
2980
2981
2982
2983
2984
2985
2986
2987
2988
2989
2990
2991
2992
2993
2994
2995
2996
2997
2998
2999
3000
3001
3002
3003
3004
3005
3006
3007
3008
3009
3010
3011
3012
3013
3014
3015
3016
3017
3018
3019
3020
3021
3022
3023
3024
3025
3026
3027
3028
3029
3030
3031
3032
3033
3034
3035
3036
3037
3038
3039
3040
3041
3042
3043
3044
3045
3046
3047
3048
3049
3050
3051
3052
3053
3054
3055
3056
3057
3058
3059
3060
3061
3062
3063
3064
3065
3066
3067
3068
3069
3070
3071
3072
3073
3074
3075
3076
3077
3078
3079
3080
3081
3082
3083
3084
3085
3086
3087
3088
3089
3090
3091
3092
3093
3094
3095
3096
3097
3098
3099
3100
3101
3102
3103
3104
3105
3106
3107
3108
3109
3110
3111
3112
3113
3114
3115
3116
3117
3118
3119
3120
3121
3122
3123
3124
3125
3126
3127
3128
3129
3130
3131
3132
3133
3134
3135
3136
3137
3138
3139
3140
3141
3142
3143
3144
3145
3146
3147
3148
3149
3150
3151
3152
3153
3154
3155
3156
3157
3158
3159
3160
3161
3162
3163
3164
3165
3166
3167
3168
3169
3170
3171
3172
3173
3174
3175
3176
3177
3178
3179
3180
3181
3182
3183
3184
3185
3186
3187
3188
3189
3190
3191
3192
3193
3194
3195
3196
3197
3198
3199
3200
3201
3202
3203
3204
3205
3206
3207
3208
3209
3210
3211
3212
3213
3214
3215
3216
3217
3218
3219
3220
3221
3222
3223
3224
3225
3226
3227
3228
3229
3230
3231
3232
3233
3234
3235
3236
3237
3238
3239
3240
3241
3242
3243
3244
3245
3246
3247
3248
3249
3250
3251
3252
3253
3254
3255
3256
3257
3258
3259
3260
3261
3262
3263
3264
3265
3266
3267
3268
3269
3270
3271
3272
3273
3274
3275
3276
3277
3278
3279
3280
3281
3282
3283
3284
3285
3286
3287
3288
3289
3290
3291
3292
3293
3294
3295
3296
3297
3298
3299
3300
3301
3302
3303
3304
3305
3306
3307
3308
3309
3310
3311
3312
3313
3314
3315
3316
3317
3318
3319
3320
3321
3322
3323
3324
3325
3326
3327
3328
3329
3330
3331
3332
3333
3334
3335
3336
3337
3338
3339
3340
3341
3342
3343
3344
3345
3346
3347
3348
3349
3350
3351
3352
3353
3354
3355
3356
3357
3358
3359
3360
3361
3362
3363
3364
3365
3366
3367
3368
3369
3370
3371
3372
3373
3374
3375
3376
3377
3378
3379
3380
3381
3382
3383
3384
3385
3386
3387
3388
3389
3390
3391
3392
3393
3394
3395
3396
3397
3398
3399
3400
3401
3402
3403
3404
3405
3406
3407
3408
3409
3410
3411
3412
3413
3414
3415
3416
3417
3418
3419
3420
3421
3422
3423
3424
3425
3426
3427
3428
3429
3430
3431
3432
3433
3434
3435
3436
3437
3438
3439
3440
3441
3442
3443
3444
3445
3446
3447
3448
3449
3450
3451
3452
3453
3454
3455
3456
3457
3458
3459
3460
3461
3462
3463
3464
3465
3466
3467
3468
3469
3470
3471
3472
3473
3474
3475
3476
3477
3478
3479
3480
3481
3482
3483
3484
3485
3486
3487
3488
3489
3490
3491
3492
3493
3494
3495
3496
3497
3498
3499
3500
3501
3502
3503
3504
3505
3506
3507
3508
3509
3510
3511
3512
3513
3514
3515
3516
3517
3518
3519
3520
3521
3522
3523
3524
3525
3526
3527
3528
3529
3530
3531
3532
3533
3534
3535
3536
3537
3538
3539
3540
3541
3542
3543
3544
3545
3546
3547
3548
3549
3550
3551
3552
3553
3554
3555
3556
3557
3558
3559
3560
3561
3562
3563
3564
3565
3566
3567
3568
3569
3570
3571
3572
3573
3574
3575
3576
3577
3578
3579
3580
3581
3582
3583
3584
3585
3586
3587
3588
3589
3590
3591
3592
3593
3594
3595
3596
3597
3598
3599
3600
3601
3602
3603
3604
3605
3606
3607
3608
3609
3610
3611
3612
3613
3614
3615
3616
3617
3618
3619
3620
3621
3622
3623
3624
3625
3626
3627
3628
3629
3630
3631
3632
3633
3634
3635
3636
3637
3638
3639
3640
3641
3642
3643
3644
3645
3646
3647
3648
3649
3650
3651
3652
3653
3654
3655
3656
3657
3658
3659
3660
3661
3662
3663
3664
3665
3666
3667
3668
3669
3670
3671
3672
3673
3674
3675
3676
3677
3678
3679
3680
3681
3682
3683
3684
3685
3686
3687
3688
3689
3690
3691
3692
3693
3694
3695
3696
3697
3698
3699
3700
3701
3702
3703
3704
3705
3706
3707
3708
3709
3710
3711
3712
3713
3714
3715
3716
3717
3718
3719
3720
3721
3722
3723
3724
3725
3726
3727
3728
3729
3730
3731
3732
3733
3734
3735
3736
3737
3738
3739
3740
3741
3742
3743
3744
3745
3746
3747
3748
3749
3750
3751
3752
3753
3754
3755
3756
3757
3758
3759
3760
3761
3762
3763
3764
3765
3766
3767
3768
3769
3770
3771
3772
3773
3774
3775
3776
3777
3778
3779
3780
3781
3782
3783
3784
3785
3786
3787
3788
3789
3790
3791
3792
3793
3794
3795
3796
3797
3798
3799
3800
3801
3802
3803
3804
3805
3806
3807
3808
3809
3810
3811
3812
3813
3814
3815
3816
3817
3818
3819
3820
3821
|
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>The Altus Metrum System</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="idp16901520"></a>The Altus Metrum System</h1></div><div><h2 class="subtitle">An Owner's Manual for Altus Metrum Rocketry Electronics</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Bdale</span> <span class="surname">Garbee</span></h3></div></div><div><div class="author"><h3 class="author"><span class="firstname">Keith</span> <span class="surname">Packard</span></h3></div></div><div><div class="author"><h3 class="author"><span class="firstname">Bob</span> <span class="surname">Finch</span></h3></div></div><div><div class="author"><h3 class="author"><span class="firstname">Anthony</span> <span class="surname">Towns</span></h3></div></div><div><p class="copyright">Copyright © 2014 Bdale Garbee and Keith Packard</p></div><div><div class="legalnotice"><a name="idp43234368"></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.5</td><td align="left">6 September 2014</td></tr><tr><td align="left" colspan="2">
Major release adding EasyMega support.
</td></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">15 June 2014</td></tr><tr><td align="left" colspan="2">
Major release adding TeleGPS support.
</td></tr><tr><td align="left">Revision 1.3.2</td><td align="left">24 January 2014</td></tr><tr><td align="left" colspan="2">
Bug fixes for TeleMega and AltosUI.
</td></tr><tr><td align="left">Revision 1.3.1</td><td align="left">21 January 2014</td></tr><tr><td align="left" colspan="2">
Bug fixes for TeleMega and TeleMetrum v2.0 along with a few
small UI improvements.
</td></tr><tr><td align="left">Revision 1.3</td><td align="left">12 November 2013</td></tr><tr><td align="left" colspan="2">
Updated for software version 1.3. Version 1.3 adds support
for TeleMega, TeleMetrum v2.0, TeleMini v2.0 and EasyMini
and fixes bugs in AltosUI and the AltOS firmware.
</td></tr><tr><td align="left">Revision 1.2.1</td><td align="left">21 May 2013</td></tr><tr><td align="left" colspan="2">
Updated for software version 1.2. Version 1.2 adds support
for TeleBT and AltosDroid. It also adds a few minor features
and fixes bugs in AltosUI and the AltOS firmware.
</td></tr><tr><td align="left">Revision 1.2</td><td align="left">18 April 2013</td></tr><tr><td align="left" colspan="2">
Updated for software version 1.2. Version 1.2 adds support
for MicroPeak and the MicroPeak USB interface.
</td></tr><tr><td align="left">Revision 1.1.1</td><td align="left">16 September 2012</td></tr><tr><td align="left" colspan="2">
Updated for software version 1.1.1 Version 1.1.1 fixes a few
bugs found in version 1.1.
</td></tr><tr><td align="left">Revision 1.1</td><td align="left">13 September 2012</td></tr><tr><td align="left" colspan="2">
Updated for software version 1.1. Version 1.1 has new
features but is otherwise compatible with version 1.0.
</td></tr><tr><td align="left">Revision 1.0</td><td align="left">24 August 2011</td></tr><tr><td align="left" colspan="2">
Updated for software version 1.0. Note that 1.0 represents a
telemetry format change, meaning both ends of a link
(TeleMetrum/TeleMini and TeleDongle) must be updated or
communications will fail.
</td></tr><tr><td align="left">Revision 0.9</td><td align="left">18 January 2011</td></tr><tr><td align="left" colspan="2">
Updated for software version 0.9. Note that 0.9 represents a
telemetry format change, meaning both ends of a link (TeleMetrum and
TeleDongle) must be updated or communications will fail.
</td></tr><tr><td align="left">Revision 0.8</td><td align="left">24 November 2010</td></tr><tr><td align="left" colspan="2">Updated for software version 0.8 </td></tr></table></div></div></div><hr></div><div class="dedication"><div class="titlepage"><div><div><h1 class="title"><a name="idp43407920"></a>Acknowledgments</h1></div></div></div><p>
Thanks to Bob Finch, W9YA, NAR 12965, TRA 12350 for writing “The
Mere-Mortals Quick Start/Usage Guide to the Altus Metrum Starter
Kit” which formed the basis of the original Getting Started chapter
in this manual. Bob was one of our first customers for a production
TeleMetrum, and his continued enthusiasm and contributions
are immensely gratifying and highly appreciated!
</p><p>
And thanks to Anthony (AJ) Towns for major contributions including
the AltosUI graphing and site map code and associated documentation.
Free software means that our customers and friends can become our
collaborators, and we certainly appreciate this level of
contribution!
</p><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="#idp43412128">1. Introduction and Overview</a></span></dt><dt><span class="chapter"><a href="#idp43239632">2. Getting Started</a></span></dt><dt><span class="chapter"><a href="#idp43249600">3. Handling Precautions</a></span></dt><dt><span class="chapter"><a href="#idp43255088">4. Altus Metrum Hardware</a></span></dt><dd><dl><dt><span class="section"><a href="#idp43255760">1. General Usage Instructions</a></span></dt><dd><dl><dt><span class="section"><a href="#idp43257728">1.1. Hooking Up Lithium Polymer Batteries</a></span></dt><dt><span class="section"><a href="#idp43260736">1.2. Hooking Up Pyro Charges</a></span></dt><dt><span class="section"><a href="#idp43262816">1.3. Hooking Up a Power Switch</a></span></dt><dt><span class="section"><a href="#idp43266032">1.4. Using a Separate Pyro Battery</a></span></dt><dt><span class="section"><a href="#idp43268544">1.5. Using a Different Kind of Battery</a></span></dt></dl></dd><dt><span class="section"><a href="#idp43270288">2. Specifications</a></span></dt><dt><span class="section"><a href="#idp48828432">3. TeleMetrum</a></span></dt><dd><dl><dt><span class="section"><a href="#idp48831824">3.1. TeleMetrum Screw Terminals</a></span></dt><dt><span class="section"><a href="#idp48861136">3.2. Using a Separate Pyro Battery with TeleMetrum</a></span></dt><dt><span class="section"><a href="#idp48864384">3.3. Using an Active Switch with TeleMetrum</a></span></dt></dl></dd><dt><span class="section"><a href="#idp48866512">4. TeleMini v1.0</a></span></dt><dd><dl><dt><span class="section"><a href="#idp48871408">4.1. TeleMini v1.0 Screw Terminals</a></span></dt><dt><span class="section"><a href="#idp48890752">4.2. Using a Separate Pyro Battery with TeleMini v1.0</a></span></dt><dt><span class="section"><a href="#idp48894128">4.3. Using an Active Switch with TeleMini v1.0</a></span></dt></dl></dd><dt><span class="section"><a href="#idp48896336">5. TeleMini v2.0</a></span></dt><dd><dl><dt><span class="section"><a href="#idp48900352">5.1. TeleMini v2.0 Screw Terminals</a></span></dt><dt><span class="section"><a href="#idp48922736">5.2. Using a Separate Pyro Battery with TeleMini v2.0</a></span></dt><dt><span class="section"><a href="#idp48925936">5.3. Using an Active Switch with TeleMini v2.0</a></span></dt></dl></dd><dt><span class="section"><a href="#idp48928032">6. EasyMini</a></span></dt><dd><dl><dt><span class="section"><a href="#idp48931888">6.1. EasyMini Screw Terminals</a></span></dt><dt><span class="section"><a href="#idp48954272">6.2. Using a Separate Pyro Battery with EasyMini</a></span></dt><dt><span class="section"><a href="#idp48957456">6.3. Using an Active Switch with EasyMini</a></span></dt></dl></dd><dt><span class="section"><a href="#idp48959552">7. TeleMega</a></span></dt><dd><dl><dt><span class="section"><a href="#idp48963520">7.1. TeleMega Screw Terminals</a></span></dt><dt><span class="section"><a href="#idp49001024">7.2. Using a Separate Pyro Battery with TeleMega</a></span></dt><dt><span class="section"><a href="#idp49002624">7.3. Using Only One Battery With TeleMega</a></span></dt><dt><span class="section"><a href="#idp49004544">7.4. Using an Active Switch with TeleMega</a></span></dt></dl></dd><dt><span class="section"><a href="#idp49006592">8. EasyMega</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49010560">8.1. EasyMega Screw Terminals</a></span></dt><dt><span class="section"><a href="#idp49048064">8.2. Using a Separate Pyro Battery with EasyMega</a></span></dt><dt><span class="section"><a href="#idp49049664">8.3. Using Only One Battery With EasyMega</a></span></dt><dt><span class="section"><a href="#idp49051584">8.4. Using an Active Switch with EasyMega</a></span></dt></dl></dd><dt><span class="section"><a href="#idp49053632">9. Flight Data Recording</a></span></dt><dt><span class="section"><a href="#idp49084400">10. Installation</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp49091680">5. System Operation</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49092320">1. Firmware Modes </a></span></dt><dt><span class="section"><a href="#idp49160720">2. GPS </a></span></dt><dt><span class="section"><a href="#idp49163504">3. Controlling An Altimeter Over The Radio Link</a></span></dt><dt><span class="section"><a href="#idp49174800">4. Ground Testing </a></span></dt><dt><span class="section"><a href="#idp49177552">5. Radio Link </a></span></dt><dt><span class="section"><a href="#idp49181552">6. APRS</a></span></dt><dt><span class="section"><a href="#idp49205872">7. Configurable Parameters</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49207792">7.1. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp49209840">7.2. Callsign</a></span></dt><dt><span class="section"><a href="#idp49211376">7.3. Telemetry/RDF/APRS Enable</a></span></dt><dt><span class="section"><a href="#idp49212672">7.4. Telemetry baud rate</a></span></dt><dt><span class="section"><a href="#idp49214240">7.5. APRS Interval</a></span></dt><dt><span class="section"><a href="#idp49215712">7.6. APRS SSID</a></span></dt><dt><span class="section"><a href="#idp49217056">7.7. Apogee Delay</a></span></dt><dt><span class="section"><a href="#idp49219648">7.8. Apogee Lockout</a></span></dt><dt><span class="section"><a href="#idp49221376">7.9. Main Deployment Altitude</a></span></dt><dt><span class="section"><a href="#idp49223072">7.10. Maximum Flight Log</a></span></dt><dt><span class="section"><a href="#idp49225216">7.11. Ignite Mode</a></span></dt><dt><span class="section"><a href="#idp49227328">7.12. Pad Orientation</a></span></dt><dt><span class="section"><a href="#idp49229568">7.13. Configurable Pyro Channels</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#idp49252176">6. AltosUI</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49255792">1. Monitor Flight</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49268512">1.1. Launch Pad</a></span></dt><dt><span class="section"><a href="#idp49284800">1.2. Ascent</a></span></dt><dt><span class="section"><a href="#idp49290256">1.3. Descent</a></span></dt><dt><span class="section"><a href="#idp49297120">1.4. Landed</a></span></dt><dt><span class="section"><a href="#idp49303552">1.5. Table</a></span></dt><dt><span class="section"><a href="#idp49307136">1.6. Site Map</a></span></dt><dt><span class="section"><a href="#idp49313856">1.7. Ignitor</a></span></dt></dl></dd><dt><span class="section"><a href="#idp49317632">2. Save Flight Data</a></span></dt><dt><span class="section"><a href="#idp49321584">3. Replay Flight</a></span></dt><dt><span class="section"><a href="#idp49323616">4. Graph Data</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49326000">4.1. Flight Graph</a></span></dt><dt><span class="section"><a href="#idp49330448">4.2. Configure Graph</a></span></dt><dt><span class="section"><a href="#idp49334112">4.3. Flight Statistics</a></span></dt><dt><span class="section"><a href="#idp49337632">4.4. Map</a></span></dt></dl></dd><dt><span class="section"><a href="#idp49341488">5. Export Data</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49343056">5.1. Comma Separated Value Format</a></span></dt><dt><span class="section"><a href="#idp49345408">5.2. Keyhole Markup Language (for Google Earth)</a></span></dt></dl></dd><dt><span class="section"><a href="#idp49346896">6. Configure Altimeter</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49359200">6.1. Main Deploy Altitude</a></span></dt><dt><span class="section"><a href="#idp49360768">6.2. Apogee Delay</a></span></dt><dt><span class="section"><a href="#idp49362384">6.3. Apogee Lockoug</a></span></dt><dt><span class="section"><a href="#idp49364112">6.4. Frequency</a></span></dt><dt><span class="section"><a href="#idp49365616">6.5. RF Calibration</a></span></dt><dt><span class="section"><a href="#idp49367264">6.6. Telemetry/RDF/APRS Enable</a></span></dt><dt><span class="section"><a href="#idp49368560">6.7. Telemetry baud rate</a></span></dt><dt><span class="section"><a href="#idp49370128">6.8. APRS Interval</a></span></dt><dt><span class="section"><a href="#idp49371696">6.9. APRS SSID</a></span></dt><dt><span class="section"><a href="#idp49373024">6.10. Callsign</a></span></dt><dt><span class="section"><a href="#idp49374336">6.11. Maximum Flight Log Size</a></span></dt><dt><span class="section"><a href="#idp49375776">6.12. Ignitor Firing Mode</a></span></dt><dt><span class="section"><a href="#idp49382688">6.13. Pad Orientation</a></span></dt><dt><span class="section"><a href="#idp49387920">6.14. Beeper Frequency</a></span></dt><dt><span class="section"><a href="#idp49389376">6.15. Configure Pyro Channels</a></span></dt></dl></dd><dt><span class="section"><a href="#idp49395760">7. Configure AltosUI</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49399264">7.1. Voice Settings</a></span></dt><dt><span class="section"><a href="#idp49404288">7.2. Log Directory</a></span></dt><dt><span class="section"><a href="#idp49406288">7.3. Callsign</a></span></dt><dt><span class="section"><a href="#idp49408528">7.4. Imperial Units</a></span></dt><dt><span class="section"><a href="#idp49410032">7.5. Font Size</a></span></dt><dt><span class="section"><a href="#idp49411312">7.6. Serial Debug</a></span></dt><dt><span class="section"><a href="#idp49412816">7.7. Manage Frequencies</a></span></dt></dl></dd><dt><span class="section"><a href="#idp49414448">8. Configure Groundstation</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49425568">8.1. Frequency</a></span></dt><dt><span class="section"><a href="#idp49427136">8.2. RF Calibration</a></span></dt><dt><span class="section"><a href="#idp49428656">8.3. Telemetry Rate</a></span></dt></dl></dd><dt><span class="section"><a href="#idp49430128">9. Flash Image</a></span></dt><dt><span class="section"><a href="#idp49431776">10. Fire Igniter</a></span></dt><dt><span class="section"><a href="#idp49437408">11. Scan Channels</a></span></dt><dt><span class="section"><a href="#idp49441632">12. Load Maps</a></span></dt><dt><span class="section"><a href="#idp49455600">13. Monitor Idle</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp49457696">7. AltosDroid</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49460080">1. Installing AltosDroid</a></span></dt><dt><span class="section"><a href="#idp49462016">2. Connecting to TeleBT</a></span></dt><dt><span class="section"><a href="#idp49464016">3. Configuring AltosDroid</a></span></dt><dt><span class="section"><a href="#idp49465472">4. AltosDroid Flight Monitoring</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49466784">4.1. Pad</a></span></dt></dl></dd><dt><span class="section"><a href="#idp49480336">5. Downloading Flight Logs</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp49482000">8. Using Altus Metrum Products</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49482640">1. Being Legal</a></span></dt><dt><span class="section"><a href="#idp49484544">2. In the Rocket</a></span></dt><dt><span class="section"><a href="#idp49487072">3. On the Ground</a></span></dt><dt><span class="section"><a href="#idp49500464">4. Data Analysis</a></span></dt><dt><span class="section"><a href="#idp49503008">5. Future Plans</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp49506848">9. Altimeter Installation Recommendations</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49508304">1. Mounting the Altimeter</a></span></dt><dt><span class="section"><a href="#idp49513136">2. Dealing with the Antenna</a></span></dt><dt><span class="section"><a href="#idp49518704">3. Preserving GPS Reception</a></span></dt><dt><span class="section"><a href="#idp49523488">4. Radio Frequency Interference</a></span></dt><dt><span class="section"><a href="#idp49531056">5. The Barometric Sensor</a></span></dt><dt><span class="section"><a href="#idp49533856">6. Ground Testing</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp49537024">10. Updating Device Firmware</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49541072">1.
Updating TeleMega, TeleMetrum v2, EasyMega or EasyMini Firmware
</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49550144">1.1. Recovering From Self-Flashing Failure</a></span></dt></dl></dd><dt><span class="section"><a href="#idp49568720">2. Pair Programming</a></span></dt><dt><span class="section"><a href="#idp49570160">3. Updating TeleMetrum v1.x Firmware</a></span></dt><dt><span class="section"><a href="#idp49583360">4. Updating TeleMini Firmware</a></span></dt><dt><span class="section"><a href="#idp49596912">5. Updating TeleDongle Firmware</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp49613536">11. Hardware Specifications</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49614176">1.
TeleMega Specifications
</a></span></dt><dt><span class="section"><a href="#idp49625648">2.
EasyMega Specifications
</a></span></dt><dt><span class="section"><a href="#idp49635392">3.
TeleMetrum v2 Specifications
</a></span></dt><dt><span class="section"><a href="#idp49645952">4. TeleMetrum v1 Specifications</a></span></dt><dt><span class="section"><a href="#idp49656512">5.
TeleMini v2.0 Specifications
</a></span></dt><dt><span class="section"><a href="#idp49665344">6.
TeleMini v1.0 Specifications
</a></span></dt><dt><span class="section"><a href="#idp49674144">7.
EasyMini Specifications
</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp49682256">12. FAQ</a></span></dt><dt><span class="appendix"><a href="#idp49691104">A. Notes for Older Software</a></span></dt><dt><span class="appendix"><a href="#idp49713504">B. Drill Templates</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49714672">1. TeleMega template</a></span></dt><dt><span class="section"><a href="#idp49731360">2. EasyMega template</a></span></dt><dt><span class="section"><a href="#idp49735744">3. TeleMetrum template</a></span></dt><dt><span class="section"><a href="#idp49740128">4. TeleMini v2/EasyMini template</a></span></dt><dt><span class="section"><a href="#idp49744528">5. TeleMini v1 template</a></span></dt></dl></dd><dt><span class="appendix"><a href="#idp49749040">C. Calibration</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49750592">1. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp49755136">2. TeleMetrum, TeleMega and EasyMega Accelerometers</a></span></dt></dl></dd><dt><span class="appendix"><a href="#idp49760816">D. 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="#idp48750064">Altus Metrum Electronics</a></dt><dt>4.2. <a href="#idp48804240">Altus Metrum Boards</a></dt><dt>4.3. <a href="#idp43191248">TeleMetrum Screw Terminals</a></dt><dt>4.4. <a href="#idp48872848">TeleMini v1.0 Connections</a></dt><dt>4.5. <a href="#idp48901760">TeleMini v2.0 Connections</a></dt><dt>4.6. <a href="#idp48933296">EasyMini Connections</a></dt><dt>4.7. <a href="#idp48964688">TeleMega Screw Terminals</a></dt><dt>4.8. <a href="#idp49011728">EasyMega Screw Terminals</a></dt><dt>4.9. <a href="#idp49055040">Data Storage on Altus Metrum altimeters</a></dt><dt>5.1. <a href="#idp49097680">AltOS Modes</a></dt><dt>5.2. <a href="#idp49134768">Pad/Idle Indications</a></dt><dt>5.3. <a href="#idp49185360">Altus Metrum APRS Comments</a></dt></dl></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp43412128"></a>Chapter 1. Introduction and Overview</h1></div></div></div><p>
Welcome to the Altus Metrum community! Our circuits and software reflect
our passion for both hobby rocketry and Free Software. We hope their
capabilities and performance will delight you in every way, but by
releasing all of our hardware and software designs under open licenses,
we also hope to empower you to take as active a role in our collective
future as you wish!
</p><p>
The first device created for our community was TeleMetrum, a dual
deploy altimeter with fully integrated GPS and radio telemetry
as standard features, and a “companion interface” that will
support optional capabilities in the future. The latest version
of TeleMetrum, v2.0, has all of the same features but with
improved sensors and radio to offer increased performance.
</p><p>
Our second device was TeleMini, a dual deploy altimeter with
radio telemetry and radio direction finding. The first version
of this device was only 13mm by 38mm (½ inch by 1½ inches) and
could fit easily in an 18mm air-frame. The latest version, v2.0,
includes a beeper, USB data download and extended on-board
flight logging, along with an improved barometric sensor.
</p><p>
TeleMega is our most sophisticated device, including six pyro
channels (four of which are fully programmable), integrated GPS,
integrated gyroscopes for staging/air-start inhibit and high
performance telemetry.
</p><p>
EasyMini is a dual-deploy altimeter with logging and built-in
USB data download.
</p><p>
EasyMega is essentially a TeleMega board with the GPS receiver
and telemetry transmitter removed. It offers the same 6 pyro
channels and integrated gyroscopes for staging/air-start inhibit.
</p><p>
TeleDongle was our first ground station, providing a USB to RF
interfaces for communicating with the altimeters. Combined with
your choice of antenna and notebook computer, TeleDongle and our
associated user interface software form a complete ground
station capable of logging and displaying in-flight telemetry,
aiding rocket recovery, then processing and archiving flight
data for analysis and review.
</p><p>
For a slightly more portable ground station experience that also
provides direct rocket recovery support, TeleBT offers flight
monitoring and data logging using a Bluetooth™ connection between
the receiver and an Android device that has the AltosDroid
application installed from the Google Play store.
</p><p>
More products will be added to the Altus Metrum family over time, and
we currently envision that this will be a single, comprehensive manual
for the entire product family.
</p></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp43239632"></a>Chapter 2. Getting Started</h1></div></div></div><p>
The first thing to do after you check the inventory of parts in your
“starter kit” is to charge the battery.
</p><p>
For TeleMetrum, TeleMega and EasyMega, the battery can be charged by plugging it into the
corresponding socket of the device and then using the USB
cable to plug the flight computer into your computer's USB socket. The
on-board circuitry will charge the battery whenever it is plugged
in, because the on-off switch does NOT control the
charging circuitry.
</p><p>
On TeleMetrum v1 boards, when the GPS chip is initially
searching for satellites, TeleMetrum will consume more current
than it pulls from the USB port, so the battery must be
attached in order to get satellite lock. Once GPS is locked,
the current consumption goes back down enough to enable charging
while running. So it's a good idea to fully charge the battery
as your first item of business so there is no issue getting and
maintaining satellite lock. The yellow charge indicator led
will go out when the battery is nearly full and the charger goes
to trickle charge. It can take several hours to fully recharge a
deeply discharged battery.
</p><p>
TeleMetrum v2.0, TeleMega and EasyMega use a higher power battery charger,
allowing them to charge the battery while running the board at
maximum power. When the battery is charging, or when the board
is consuming a lot of power, the red LED will be lit. When the
battery is fully charged, the green LED will be lit. When the
battery is damaged or missing, both LEDs will be lit, which
appears yellow.
</p><p>
The Lithium Polymer TeleMini and EasyMini battery can be charged by
disconnecting it from the board and plugging it into a
standalone battery charger such as the LipoCharger product
included in TeleMini Starter Kits, and connecting that via a USB
cable to a laptop or other USB power source.
</p><p>
You can also choose to use another battery with TeleMini v2.0
and EasyMini, anything supplying between 4 and 12 volts should
work fine (like a standard 9V battery), but if you are planning
to fire pyro charges, ground testing is required to verify that
the battery supplies enough current to fire your chosen e-matches.
</p><p>
The other active device in the starter kit is the TeleDongle USB to
RF interface. If you plug it in to your Mac or Linux computer it should
“just work”, showing up as a serial port device. Windows systems need
driver information that is part of the AltOS download to know that the
existing USB modem driver will work. We therefore recommend installing
our software before plugging in TeleDongle if you are using a Windows
computer. If you are using an older version of Linux and are having
problems, try moving to a fresher kernel (2.6.33 or newer).
</p><p>
Next you should obtain and install the AltOS software. The AltOS
distribution includes the AltosUI ground station program, current
firmware
images for all of the hardware, and a number of standalone
utilities that are rarely needed. Pre-built binary packages are
available for Linux, Microsoft Windows, and recent MacOSX
versions. Full source code and build instructions are also
available. The latest version may always be downloaded from
<a class="ulink" href="http://altusmetrum.org/AltOS" target="_top">http://altusmetrum.org/AltOS</a>.
</p><p>
If you're using a TeleBT instead of the TeleDongle, you'll want to
install the AltosDroid application from the Google Play store on an
Android device. You don't need a data plan to use AltosDroid, but
without network access, the Map view will be less useful as it
won't contain any map data. You can also use TeleBT connected
over USB with your laptop computer; it acts exactly like a
TeleDongle. Anywhere this manual talks about TeleDongle, you can
also read that as 'and TeleBT when connected via USB'.
</p></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp43249600"></a>Chapter 3. 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 rechargeable batteries have an
extraordinary power density. This is great because we can fly with
much less battery mass than if we used alkaline batteries or previous
generation rechargeable batteries... but if they are punctured
or their leads are allowed to short, they can and will release their
energy very rapidly!
Thus we recommend that you take some care when handling our batteries
and consider giving them some extra protection in your air-frame. We
often wrap them in suitable scraps of closed-cell packing foam before
strapping them down, for example.
</p><p>
The barometric sensors used on all of our flight computers are
sensitive to sunlight. In normal mounting situations, the baro sensor
and all of the other surface mount components
are “down” towards whatever the underlying mounting surface is, so
this is not normally a problem. Please consider this when designing an
installation in an air-frame with a see-through plastic payload bay. It
is particularly important to
consider this with TeleMini v1.0, both because the baro sensor is on the
“top” of the board, and because many model rockets with payload bays
use clear plastic for the payload bay! Replacing these with an opaque
cardboard tube, painting them, or wrapping them with a layer of masking
tape are all reasonable approaches to keep the sensor out of direct
sunlight.
</p><p>
The barometric sensor sampling port must be able to “breathe”,
both by not being covered by foam or tape or other materials that might
directly block the hole on the top of the sensor, and also by having a
suitable static vent to outside air.
</p><p>
As with all other rocketry electronics, Altus Metrum altimeters 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="idp43255088"></a>Chapter 4. Altus Metrum Hardware</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp43255760">1. General Usage Instructions</a></span></dt><dd><dl><dt><span class="section"><a href="#idp43257728">1.1. Hooking Up Lithium Polymer Batteries</a></span></dt><dt><span class="section"><a href="#idp43260736">1.2. Hooking Up Pyro Charges</a></span></dt><dt><span class="section"><a href="#idp43262816">1.3. Hooking Up a Power Switch</a></span></dt><dt><span class="section"><a href="#idp43266032">1.4. Using a Separate Pyro Battery</a></span></dt><dt><span class="section"><a href="#idp43268544">1.5. Using a Different Kind of Battery</a></span></dt></dl></dd><dt><span class="section"><a href="#idp43270288">2. Specifications</a></span></dt><dt><span class="section"><a href="#idp48828432">3. TeleMetrum</a></span></dt><dd><dl><dt><span class="section"><a href="#idp48831824">3.1. TeleMetrum Screw Terminals</a></span></dt><dt><span class="section"><a href="#idp48861136">3.2. Using a Separate Pyro Battery with TeleMetrum</a></span></dt><dt><span class="section"><a href="#idp48864384">3.3. Using an Active Switch with TeleMetrum</a></span></dt></dl></dd><dt><span class="section"><a href="#idp48866512">4. TeleMini v1.0</a></span></dt><dd><dl><dt><span class="section"><a href="#idp48871408">4.1. TeleMini v1.0 Screw Terminals</a></span></dt><dt><span class="section"><a href="#idp48890752">4.2. Using a Separate Pyro Battery with TeleMini v1.0</a></span></dt><dt><span class="section"><a href="#idp48894128">4.3. Using an Active Switch with TeleMini v1.0</a></span></dt></dl></dd><dt><span class="section"><a href="#idp48896336">5. TeleMini v2.0</a></span></dt><dd><dl><dt><span class="section"><a href="#idp48900352">5.1. TeleMini v2.0 Screw Terminals</a></span></dt><dt><span class="section"><a href="#idp48922736">5.2. Using a Separate Pyro Battery with TeleMini v2.0</a></span></dt><dt><span class="section"><a href="#idp48925936">5.3. Using an Active Switch with TeleMini v2.0</a></span></dt></dl></dd><dt><span class="section"><a href="#idp48928032">6. EasyMini</a></span></dt><dd><dl><dt><span class="section"><a href="#idp48931888">6.1. EasyMini Screw Terminals</a></span></dt><dt><span class="section"><a href="#idp48954272">6.2. Using a Separate Pyro Battery with EasyMini</a></span></dt><dt><span class="section"><a href="#idp48957456">6.3. Using an Active Switch with EasyMini</a></span></dt></dl></dd><dt><span class="section"><a href="#idp48959552">7. TeleMega</a></span></dt><dd><dl><dt><span class="section"><a href="#idp48963520">7.1. TeleMega Screw Terminals</a></span></dt><dt><span class="section"><a href="#idp49001024">7.2. Using a Separate Pyro Battery with TeleMega</a></span></dt><dt><span class="section"><a href="#idp49002624">7.3. Using Only One Battery With TeleMega</a></span></dt><dt><span class="section"><a href="#idp49004544">7.4. Using an Active Switch with TeleMega</a></span></dt></dl></dd><dt><span class="section"><a href="#idp49006592">8. EasyMega</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49010560">8.1. EasyMega Screw Terminals</a></span></dt><dt><span class="section"><a href="#idp49048064">8.2. Using a Separate Pyro Battery with EasyMega</a></span></dt><dt><span class="section"><a href="#idp49049664">8.3. Using Only One Battery With EasyMega</a></span></dt><dt><span class="section"><a href="#idp49051584">8.4. Using an Active Switch with EasyMega</a></span></dt></dl></dd><dt><span class="section"><a href="#idp49053632">9. Flight Data Recording</a></span></dt><dt><span class="section"><a href="#idp49084400">10. Installation</a></span></dt></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp43255760"></a>1. General Usage Instructions</h2></div></div></div><p>
Here are general instructions for hooking up an Altus Metrum
flight computer. Instructions specific to each model will be
found in the section devoted to that model below.
</p><p>
To prevent electrical interference from affecting the
operation of the flight computer, it's important to always
twist pairs of wires connected to the board. Twist the switch
leads, the pyro leads and the battery leads. This reduces
interference through a mechanism called common mode rejection.
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp43257728"></a>1.1. Hooking Up Lithium Polymer Batteries</h3></div></div></div><p>
All Altus Metrum flight computers have 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 the flight computer.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp43260736"></a>1.2. Hooking Up Pyro Charges</h3></div></div></div><p>
Altus Metrum flight computers always have two screws for
each pyro charge. This means you shouldn't need to put two
wires into a screw terminal or connect leads from pyro
charges together externally.
</p><p>
On the flight computer, one lead from each charge is hooked
to the positive battery terminal through the power switch.
The other lead is connected through the pyro circuit, which
is connected to the negative battery terminal when the pyro
circuit is fired.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp43262816"></a>1.3. Hooking Up a Power Switch</h3></div></div></div><p>
Altus Metrum flight computers need an external power switch
to turn them on. This disconnects both the computer and the
pyro charges from the battery, preventing the charges from
firing when in the Off position. The switch is in-line with
the positive battery terminal.
</p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp43264192"></a>1.3.1. Using an External Active Switch Circuit</h4></div></div></div><p>
You can use an active switch circuit, such as the
Featherweight Magnetic Switch, with any Altus Metrum
flight computer. These require three connections, one to
the battery, one to the positive power input on the flight
computer and one to ground. Find instructions on how to
hook these up for each flight computer below. The follow
the instructions that come with your active switch to
connect it up.
</p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp43266032"></a>1.4. Using a Separate Pyro Battery</h3></div></div></div><p>
As mentioned above in the section on hooking up pyro
charges, one lead for each of the pyro charges is connected
through the power switch directly to the positive battery
terminal. The other lead is connected to the pyro circuit,
which connects it to the negative battery terminal when the
pyro circuit is fired. The pyro circuit on all of the flight
computers is designed to handle up to 16V.
</p><p>
To use a separate pyro battery, connect the negative pyro
battery terminal to the flight computer ground terminal,
the positive battery terminal to the igniter and the other
igniter lead to the negative pyro terminal on the flight
computer. When the pyro channel fires, it will complete the
circuit between the negative pyro terminal and the ground
terminal, firing the igniter. Specific instructions on how
to hook this up will be found in each section below.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp43268544"></a>1.5. Using a Different Kind of Battery</h3></div></div></div><p>
EasyMini and TeleMini v2 are designed to use either a
lithium polymer battery or any other battery producing
between 4 and 12 volts, such as a rectangular 9V
battery. TeleMega, EasyMega and TeleMetrum are not designed for this,
and must only be powered by a lithium polymer battery. Find
instructions on how to use other batteries in the EasyMini
and TeleMini sections below.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp43270288"></a>2. Specifications</h2></div></div></div><p>
Here's the full set of Altus Metrum products, both in
production and retired.
</p><div class="table"><a name="idp48750064"></a><p class="title"><b>Table 4.1. Altus Metrum Electronics</b></p><div class="table-contents"><table summary="Altus Metrum Electronics" border="1"><colgroup><col align="center" class="Device"><col align="center" class="Barometer"><col align="center" class="Z-axis accelerometer"><col align="center" class="GPS"><col align="center" class="3D sensors"><col align="center" class="Storage"><col align="center" class="RF"><col align="center" class="Battery"></colgroup><thead><tr><th align="center">Device</th><th align="center">Barometer</th><th align="center">Z-axis accelerometer</th><th align="center">GPS</th><th align="center">3D sensors</th><th align="center">Storage</th><th align="center">RF Output</th><th align="center">Battery</th></tr></thead><tbody><tr><td align="center">TeleMetrum v1.0</td><td align="center"><p>MP3H6115 10km (33k')</p></td><td align="center"><p>MMA2202 50g</p></td><td align="center">SkyTraq</td><td align="center">-</td><td align="center">1MB</td><td align="center">10mW</td><td align="center">3.7V</td></tr><tr><td align="center">TeleMetrum v1.1</td><td align="center"><p>MP3H6115 10km (33k')</p></td><td align="center"><p>MMA2202 50g</p></td><td align="center">SkyTraq</td><td align="center">-</td><td align="center">2MB</td><td align="center">10mW</td><td align="center">3.7V</td></tr><tr><td align="center">TeleMetrum v1.2</td><td align="center"><p>MP3H6115 10km (33k')</p></td><td align="center"><p>ADXL78 70g</p></td><td align="center">SkyTraq</td><td align="center">-</td><td align="center">2MB</td><td align="center">10mW</td><td align="center">3.7V</td></tr><tr><td align="center">TeleMetrum v2.0</td><td align="center"><p>MS5607 30km (100k')</p></td><td align="center"><p>MMA6555 102g</p></td><td align="center">uBlox Max-7Q</td><td align="center">-</td><td align="center">8MB</td><td align="center">40mW</td><td align="center">3.7V</td></tr><tr><td align="center"><p>TeleMini v1.0</p></td><td align="center"><p>MP3H6115 10km (33k')</p></td><td align="center">-</td><td align="center">-</td><td align="center">-</td><td align="center">5kB</td><td align="center">10mW</td><td align="center">3.7V</td></tr><tr><td align="center">TeleMini v2.0</td><td align="center"><p>MS5607 30km (100k')</p></td><td align="center">-</td><td align="center">-</td><td align="center">-</td><td align="center">1MB</td><td align="center">10mW</td><td align="center">3.7-12V</td></tr><tr><td align="center">EasyMini v1.0</td><td align="center"><p>MS5607 30km (100k')</p></td><td align="center">-</td><td align="center">-</td><td align="center">-</td><td align="center">1MB</td><td align="center">-</td><td align="center">3.7-12V</td></tr><tr><td align="center">TeleMega v1.0</td><td align="center"><p>MS5607 30km (100k')</p></td><td align="center"><p>MMA6555 102g</p></td><td align="center">uBlox Max-7Q</td><td align="center"><p>MPU6000 HMC5883</p></td><td align="center">8MB</td><td align="center">40mW</td><td align="center">3.7V</td></tr><tr><td align="center">EasyMega v1.0</td><td align="center"><p>MS5607 30km (100k')</p></td><td align="center"><p>MMA6555 102g</p></td><td align="center">-</td><td align="center"><p>MPU6000 HMC5883</p></td><td align="center">8MB</td><td align="center">-</td><td align="center">3.7V</td></tr></tbody></table></div></div><br class="table-break"><div class="table"><a name="idp48804240"></a><p class="title"><b>Table 4.2. Altus Metrum Boards</b></p><div class="table-contents"><table summary="Altus Metrum Boards" border="1"><colgroup><col align="center" class="Device"><col align="center" class="Connectors"><col align="center" class="Screw Terminals"><col align="center" class="Width"><col align="center" class="Length"><col align="center" class="Tube Size"></colgroup><thead><tr><th align="center">Device</th><th align="center">Connectors</th><th align="center">Screw Terminals</th><th align="center">Width</th><th align="center">Length</th><th align="center">Tube Size</th></tr></thead><tbody><tr><td align="center">TeleMetrum</td><td align="center"><p>
Antenna
Debug
Companion
USB
Battery
</p></td><td align="center"><p>Apogee pyro Main pyro Switch</p></td><td align="center">1 inch (2.54cm)</td><td align="center">2 ¾ inch (6.99cm)</td><td align="center">29mm coupler</td></tr><tr><td align="center"><p>TeleMini v1.0</p></td><td align="center"><p>
Antenna
Debug
Battery
</p></td><td align="center"><p>
Apogee pyro
Main pyro
</p></td><td align="center">½ inch (1.27cm)</td><td align="center">1½ inch (3.81cm)</td><td align="center">18mm coupler</td></tr><tr><td align="center">TeleMini v2.0</td><td align="center"><p>
Antenna
Debug
USB
Battery
</p></td><td align="center"><p>
Apogee pyro
Main pyro
Battery
Switch
</p></td><td align="center">0.8 inch (2.03cm)</td><td align="center">1½ inch (3.81cm)</td><td align="center">24mm coupler</td></tr><tr><td align="center">EasyMini</td><td align="center"><p>
Debug
USB
Battery
</p></td><td align="center"><p>
Apogee pyro
Main pyro
Battery
Switch
</p></td><td align="center">0.8 inch (2.03cm)</td><td align="center">1½ inch (3.81cm)</td><td align="center">24mm coupler</td></tr><tr><td align="center">TeleMega</td><td align="center"><p>
Antenna
Debug
Companion
USB
Battery
</p></td><td align="center"><p>
Apogee pyro
Main pyro
Pyro A-D
Switch
Pyro battery
</p></td><td align="center">1¼ inch (3.18cm)</td><td align="center">3¼ inch (8.26cm)</td><td align="center">38mm coupler</td></tr><tr><td align="center">EasyMega</td><td align="center"><p>
Debug
Companion
USB
Battery
</p></td><td align="center"><p>
Apogee pyro
Main pyro
Pyro A-D
Switch
Pyro battery
</p></td><td align="center">1¼ inch (3.18cm)</td><td align="center">2¼ inch (5.62cm)</td><td align="center">38mm coupler</td></tr></tbody></table></div></div><br class="table-break"></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp48828432"></a>3. TeleMetrum</h2></div></div></div><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="telemetrum-v1.1-thside.jpg" width="495"></td></tr></table></div></div><p>
TeleMetrum is a 1 inch by 2¾ inch circuit board. It was designed to
fit inside coupler for 29mm air-frame tubing, but using it in a tube that
small in diameter may require some creativity in mounting and wiring
to succeed! The presence of an accelerometer means TeleMetrum should
be aligned along the flight axis of the airframe, and by default the ¼
wave UHF wire antenna should be on the nose-cone end of the board. The
antenna wire is about 7 inches long, and wiring for a power switch and
the e-matches for apogee and main ejection charges depart from the
fin can end of the board, meaning an ideal “simple” avionics
bay for TeleMetrum should have at least 10 inches of interior length.
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp48831824"></a>3.1. TeleMetrum Screw Terminals</h3></div></div></div><p>
TeleMetrum has six screw terminals on the end of the board
opposite the telemetry antenna. Two are for the power
switch, and two each for the apogee and main igniter
circuits. Using the picture above and starting from the top,
the terminals are as follows:
</p><div class="table"><a name="idp43191248"></a><p class="title"><b>Table 4.3. TeleMetrum Screw Terminals</b></p><div class="table-contents"><table summary="TeleMetrum Screw Terminals" border="1"><colgroup><col align="center" class="Pin #"><col align="center" class="Pin Name"><col align="left" class="Description"></colgroup><thead><tr><th align="center">Terminal #</th><th align="center">Terminal Name</th><th align="center">Description</th></tr></thead><tbody><tr><td align="center">1</td><td align="center">Switch Output</td><td align="left">Switch connection to flight computer</td></tr><tr><td align="center">2</td><td align="center">Switch Input</td><td align="left">Switch connection to positive battery terminal</td></tr><tr><td align="center">3</td><td align="center">Main +</td><td align="left">Main pyro channel common connection to battery +</td></tr><tr><td align="center">4</td><td align="center">Main -</td><td align="left">Main pyro channel connection to pyro circuit</td></tr><tr><td align="center">5</td><td align="center">Apogee +</td><td align="left">Apogee pyro channel common connection to battery +</td></tr><tr><td align="center">6</td><td align="center">Apogee -</td><td align="left">Apogee pyro channel connection to pyro circuit</td></tr></tbody></table></div></div><br class="table-break"></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp48861136"></a>3.2. Using a Separate Pyro Battery with TeleMetrum</h3></div></div></div><p>
As described above, using an external pyro battery involves
connecting the negative battery terminal to the flight
computer ground, connecting the positive battery terminal to
one of the igniter leads and connecting the other igniter
lead to the per-channel pyro circuit connection.
</p><p>
To connect the negative battery terminal to the TeleMetrum
ground, insert a small piece of wire, 24 to 28 gauge
stranded, into the GND hole just above the screw terminal
strip and solder it in place.
</p><p>
Connecting the positive battery terminal to the pyro
charges must be done separate from TeleMetrum, by soldering
them together or using some other connector.
</p><p>
The other lead from each pyro charge is then inserted into
the appropriate per-pyro channel screw terminal (terminal 4 for the
Main charge, terminal 6 for the Apogee charge).
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp48864384"></a>3.3. Using an Active Switch with TeleMetrum</h3></div></div></div><p>
As explained above, an external active switch requires three
connections, one to the positive battery terminal, one to
the flight computer positive input and one to ground.
</p><p>
The positive battery terminal is available on screw terminal
2, the positive flight computer input is on terminal 1. To
hook a lead to ground, solder a piece of wire, 24 to 28
gauge stranded, to the GND hole just above terminal 1.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp48866512"></a>4. TeleMini v1.0</h2></div></div></div><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="telemini-v1-top.jpg" width="495"></td></tr></table></div></div><p>
TeleMini v1.0 is ½ inches by 1½ inches. It was
designed to fit inside an 18mm air-frame tube, but using it in
a tube that small in diameter may require some creativity in
mounting and wiring to succeed! Since there is no
accelerometer, TeleMini can be mounted in any convenient
orientation. The default ¼ wave UHF wire antenna attached to
the center of one end of the board is about 7 inches long. Two
wires for the power switch are connected to holes in the
middle of the board. Screw terminals for the e-matches for
apogee and main ejection charges depart from the other end of
the board, meaning an ideal “simple” avionics bay for TeleMini
should have at least 9 inches of interior length.
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp48871408"></a>4.1. TeleMini v1.0 Screw Terminals</h3></div></div></div><p>
TeleMini v1.0 has four screw terminals on the end of the
board opposite the telemetry antenna. Two are for the apogee
and two are for main igniter circuits. There are also wires
soldered to the board for the power switch. Using the
picture above and starting from the top for the terminals
and from the left for the power switch wires, the
connections are as follows:
</p><div class="table"><a name="idp48872848"></a><p class="title"><b>Table 4.4. TeleMini v1.0 Connections</b></p><div class="table-contents"><table summary="TeleMini v1.0 Connections" border="1"><colgroup><col align="center" class="Pin #"><col align="center" class="Pin Name"><col align="left" class="Description"></colgroup><thead><tr><th align="center">Terminal #</th><th align="center">Terminal Name</th><th align="center">Description</th></tr></thead><tbody><tr><td align="center">1</td><td align="center">Apogee -</td><td align="left">Apogee pyro channel connection to pyro circuit</td></tr><tr><td align="center">2</td><td align="center">Apogee +</td><td align="left">Apogee pyro channel common connection to battery +</td></tr><tr><td align="center">3</td><td align="center">Main -</td><td align="left">Main pyro channel connection to pyro circuit</td></tr><tr><td align="center">4</td><td align="center">Main +</td><td align="left">Main pyro channel common connection to battery +</td></tr><tr><td align="center">Left</td><td align="center">Switch Output</td><td align="left">Switch connection to flight computer</td></tr><tr><td align="center">Right</td><td align="center">Switch Input</td><td align="left">Switch connection to positive battery terminal</td></tr></tbody></table></div></div><br class="table-break"></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp48890752"></a>4.2. Using a Separate Pyro Battery with TeleMini v1.0</h3></div></div></div><p>
As described above, using an external pyro battery involves
connecting the negative battery terminal to the flight
computer ground, connecting the positive battery terminal to
one of the igniter leads and connecting the other igniter
lead to the per-channel pyro circuit connection. Because
there is no solid ground connection to use on TeleMini, this
is not recommended.
</p><p>
The only available ground connection on TeleMini v1.0 are
the two mounting holes next to the telemetry
antenna. Somehow connect a small piece of wire to one of
those holes and hook it to the negative pyro battery terminal.
</p><p>
Connecting the positive battery terminal to the pyro
charges must be done separate from TeleMini v1.0, by soldering
them together or using some other connector.
</p><p>
The other lead from each pyro charge is then inserted into
the appropriate per-pyro channel screw terminal (terminal 3 for the
Main charge, terminal 1 for the Apogee charge).
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp48894128"></a>4.3. Using an Active Switch with TeleMini v1.0</h3></div></div></div><p>
As explained above, an external active switch requires three
connections, one to the positive battery terminal, one to
the flight computer positive input and one to ground. Again,
because TeleMini doesn't have any good ground connection,
this is not recommended.
</p><p>
The positive battery terminal is available on the Right
power switch wire, the positive flight computer input is on
the left power switch wire. Hook a lead to either of the
mounting holes for a ground connection.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp48896336"></a>5. TeleMini v2.0</h2></div></div></div><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="telemini-v2-top.jpg" width="495"></td></tr></table></div></div><p>
TeleMini v2.0 is 0.8 inches by 1½ inches. It adds more
on-board data logging memory, a built-in USB connector and
screw terminals for the battery and power switch. The larger
board fits in a 24mm coupler. There's also a battery connector
for a LiPo battery if you want to use one of those.
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp48900352"></a>5.1. TeleMini v2.0 Screw Terminals</h3></div></div></div><p>
TeleMini v2.0 has two sets of four screw terminals on the end of the
board opposite the telemetry antenna. Using the picture
above, the top four have connections for the main pyro
circuit and an external battery and the bottom four have
connections for the apogee pyro circuit and the power
switch. Counting from the left, the connections are as follows:
</p><div class="table"><a name="idp48901760"></a><p class="title"><b>Table 4.5. TeleMini v2.0 Connections</b></p><div class="table-contents"><table summary="TeleMini v2.0 Connections" border="1"><colgroup><col align="center" class="Pin #"><col align="center" class="Pin Name"><col align="left" class="Description"></colgroup><thead><tr><th align="center">Terminal #</th><th align="center">Terminal Name</th><th align="center">Description</th></tr></thead><tbody><tr><td align="center">Top 1</td><td align="center">Main -</td><td align="left">Main pyro channel connection to pyro circuit</td></tr><tr><td align="center">Top 2</td><td align="center">Main +</td><td align="left">Main pyro channel common connection to battery +</td></tr><tr><td align="center">Top 3</td><td align="center">Battery +</td><td align="left">Positive external battery terminal</td></tr><tr><td align="center">Top 4</td><td align="center">Battery -</td><td align="left">Negative external battery terminal</td></tr><tr><td align="center">Bottom 1</td><td align="center">Apogee -</td><td align="left">Apogee pyro channel connection to pyro circuit</td></tr><tr><td align="center">Bottom 2</td><td align="center">Apogee +</td><td align="left">Apogee pyro channel common connection to
battery +</td></tr><tr><td align="center">Bottom 3</td><td align="center">Switch Output</td><td align="left">Switch connection to flight computer</td></tr><tr><td align="center">Bottom 4</td><td align="center">Switch Input</td><td align="left">Switch connection to positive battery terminal</td></tr></tbody></table></div></div><br class="table-break"></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp48922736"></a>5.2. Using a Separate Pyro Battery with TeleMini v2.0</h3></div></div></div><p>
As described above, using an external pyro battery involves
connecting the negative battery terminal to the flight
computer ground, connecting the positive battery terminal to
one of the igniter leads and connecting the other igniter
lead to the per-channel pyro circuit connection.
</p><p>
To connect the negative pyro battery terminal to TeleMini
ground, connect it to the negative external battery
connection, top terminal 4.
</p><p>
Connecting the positive battery terminal to the pyro
charges must be done separate from TeleMini v2.0, by soldering
them together or using some other connector.
</p><p>
The other lead from each pyro charge is then inserted into
the appropriate per-pyro channel screw terminal (top
terminal 1 for the Main charge, bottom terminal 1 for the
Apogee charge).
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp48925936"></a>5.3. Using an Active Switch with TeleMini v2.0</h3></div></div></div><p>
As explained above, an external active switch requires three
connections, one to the positive battery terminal, one to
the flight computer positive input and one to ground. Use
the negative external battery connection, top terminal 4 for
ground.
</p><p>
The positive battery terminal is available on bottom
terminal 4, the positive flight computer input is on the
bottom terminal 3.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp48928032"></a>6. EasyMini</h2></div></div></div><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="easymini-top.jpg" width="495"></td></tr></table></div></div><p>
EasyMini is built on a 0.8 inch by 1½ inch circuit board. It's
designed to fit in a 24mm coupler tube. The connectors and
screw terminals match TeleMini v2.0, so you can easily swap between
EasyMini and TeleMini.
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp48931888"></a>6.1. EasyMini Screw Terminals</h3></div></div></div><p>
EasyMini has two sets of four screw terminals on the end of the
board opposite the telemetry antenna. Using the picture
above, the top four have connections for the main pyro
circuit and an external battery and the bottom four have
connections for the apogee pyro circuit and the power
switch. Counting from the left, the connections are as follows:
</p><div class="table"><a name="idp48933296"></a><p class="title"><b>Table 4.6. EasyMini Connections</b></p><div class="table-contents"><table summary="EasyMini Connections" border="1"><colgroup><col align="center" class="Pin #"><col align="center" class="Pin Name"><col align="left" class="Description"></colgroup><thead><tr><th align="center">Terminal #</th><th align="center">Terminal Name</th><th align="center">Description</th></tr></thead><tbody><tr><td align="center">Top 1</td><td align="center">Main -</td><td align="left">Main pyro channel connection to pyro circuit</td></tr><tr><td align="center">Top 2</td><td align="center">Main +</td><td align="left">Main pyro channel common connection to battery +</td></tr><tr><td align="center">Top 3</td><td align="center">Battery +</td><td align="left">Positive external battery terminal</td></tr><tr><td align="center">Top 4</td><td align="center">Battery -</td><td align="left">Negative external battery terminal</td></tr><tr><td align="center">Bottom 1</td><td align="center">Apogee -</td><td align="left">Apogee pyro channel connection to pyro circuit</td></tr><tr><td align="center">Bottom 2</td><td align="center">Apogee +</td><td align="left">Apogee pyro channel common connection to
battery +</td></tr><tr><td align="center">Bottom 3</td><td align="center">Switch Output</td><td align="left">Switch connection to flight computer</td></tr><tr><td align="center">Bottom 4</td><td align="center">Switch Input</td><td align="left">Switch connection to positive battery terminal</td></tr></tbody></table></div></div><br class="table-break"></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp48954272"></a>6.2. Using a Separate Pyro Battery with EasyMini</h3></div></div></div><p>
As described above, using an external pyro battery involves
connecting the negative battery terminal to the flight
computer ground, connecting the positive battery terminal to
one of the igniter leads and connecting the other igniter
lead to the per-channel pyro circuit connection.
</p><p>
To connect the negative pyro battery terminal to TeleMini
ground, connect it to the negative external battery
connection, top terminal 4.
</p><p>
Connecting the positive battery terminal to the pyro
charges must be done separate from EasyMini, by soldering
them together or using some other connector.
</p><p>
The other lead from each pyro charge is then inserted into
the appropriate per-pyro channel screw terminal (top
terminal 1 for the Main charge, bottom terminal 1 for the
Apogee charge).
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp48957456"></a>6.3. Using an Active Switch with EasyMini</h3></div></div></div><p>
As explained above, an external active switch requires three
connections, one to the positive battery terminal, one to
the flight computer positive input and one to ground. Use
the negative external battery connection, top terminal 4 for
ground.
</p><p>
The positive battery terminal is available on bottom
terminal 4, the positive flight computer input is on the
bottom terminal 3.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp48959552"></a>7. TeleMega</h2></div></div></div><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="telemega-v1.0-top.jpg" width="495"></td></tr></table></div></div><p>
TeleMega is a 1¼ inch by 3¼ inch circuit board. It was
designed to easily fit in a 38mm coupler. Like TeleMetrum,
TeleMega has an accelerometer and so it must be mounted so that
the board is aligned with the flight axis. It can be mounted
either antenna up or down.
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp48963520"></a>7.1. TeleMega Screw Terminals</h3></div></div></div><p>
TeleMega has two sets of nine screw terminals on the end of
the board opposite the telemetry antenna. They are as follows:
</p><div class="table"><a name="idp48964688"></a><p class="title"><b>Table 4.7. TeleMega Screw Terminals</b></p><div class="table-contents"><table summary="TeleMega Screw Terminals" border="1"><colgroup><col align="center" class="Pin #"><col align="center" class="Pin Name"><col align="left" class="Description"></colgroup><thead><tr><th align="center">Terminal #</th><th align="center">Terminal Name</th><th align="center">Description</th></tr></thead><tbody><tr><td align="center">Top 1</td><td align="center">Switch Input</td><td align="left">Switch connection to positive battery terminal</td></tr><tr><td align="center">Top 2</td><td align="center">Switch Output</td><td align="left">Switch connection to flight computer</td></tr><tr><td align="center">Top 3</td><td align="center">GND</td><td align="left">Ground connection for use with external active switch</td></tr><tr><td align="center">Top 4</td><td align="center">Main -</td><td align="left">Main pyro channel connection to pyro circuit</td></tr><tr><td align="center">Top 5</td><td align="center">Main +</td><td align="left">Main pyro channel common connection to battery +</td></tr><tr><td align="center">Top 6</td><td align="center">Apogee -</td><td align="left">Apogee pyro channel connection to pyro circuit</td></tr><tr><td align="center">Top 7</td><td align="center">Apogee +</td><td align="left">Apogee pyro channel common connection to battery +</td></tr><tr><td align="center">Top 8</td><td align="center">D -</td><td align="left">D pyro channel connection to pyro circuit</td></tr><tr><td align="center">Top 9</td><td align="center">D +</td><td align="left">D pyro channel common connection to battery +</td></tr><tr><td align="center">Bottom 1</td><td align="center">GND</td><td align="left">Ground connection for negative pyro battery terminal</td></tr><tr><td align="center">Bottom 2</td><td align="center">Pyro</td><td align="left">Positive pyro battery terminal</td></tr><tr><td align="center">Bottom 3</td><td align="center">Lipo</td><td align="left">
Power switch output. Use to connect main battery to
pyro battery input
</td></tr><tr><td align="center">Bottom 4</td><td align="center">A -</td><td align="left">A pyro channel connection to pyro circuit</td></tr><tr><td align="center">Bottom 5</td><td align="center">A +</td><td align="left">A pyro channel common connection to battery +</td></tr><tr><td align="center">Bottom 6</td><td align="center">B -</td><td align="left">B pyro channel connection to pyro circuit</td></tr><tr><td align="center">Bottom 7</td><td align="center">B +</td><td align="left">B pyro channel common connection to battery +</td></tr><tr><td align="center">Bottom 8</td><td align="center">C -</td><td align="left">C pyro channel connection to pyro circuit</td></tr><tr><td align="center">Bottom 9</td><td align="center">C +</td><td align="left">C pyro channel common connection to battery +</td></tr></tbody></table></div></div><br class="table-break"></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49001024"></a>7.2. Using a Separate Pyro Battery with TeleMega</h3></div></div></div><p>
TeleMega provides explicit support for an external pyro
battery. All that is required is to remove the jumper
between the lipo terminal (Bottom 3) and the pyro terminal
(Bottom 2). Then hook the negative pyro battery terminal to ground
(Bottom 1) and the positive pyro battery to the pyro battery
input (Bottom 2). You can then use the existing pyro screw
terminals to hook up all of the pyro charges.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49002624"></a>7.3. Using Only One Battery With TeleMega</h3></div></div></div><p>
Because TeleMega has built-in support for a separate pyro
battery, if you want to fly with just one battery running
both the computer and firing the charges, you need to
connect the flight computer battery to the pyro
circuit. TeleMega has two screw terminals for this—hook a
wire from the Lipo terminal (Bottom 3) to the Pyro terminal
(Bottom 2).
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49004544"></a>7.4. Using an Active Switch with TeleMega</h3></div></div></div><p>
As explained above, an external active switch requires three
connections, one to the positive battery terminal, one to
the flight computer positive input and one to ground.
</p><p>
The positive battery terminal is available on Top terminal
1, the positive flight computer input is on Top terminal
2. Ground is on Top terminal 3.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49006592"></a>8. EasyMega</h2></div></div></div><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="405"><tr><td><img src="easymega-v1.0-top.jpg" width="405"></td></tr></table></div></div><p>
EasyMega is a 1¼ inch by 2¼ inch circuit board. It was
designed to easily fit in a 38mm coupler. Like TeleMetrum,
EasyMega has an accelerometer and so it must be mounted so that
the board is aligned with the flight axis. It can be mounted
either antenna up or down.
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49010560"></a>8.1. EasyMega Screw Terminals</h3></div></div></div><p>
EasyMega has two sets of nine screw terminals on the end of
the board opposite the telemetry antenna. They are as follows:
</p><div class="table"><a name="idp49011728"></a><p class="title"><b>Table 4.8. EasyMega Screw Terminals</b></p><div class="table-contents"><table summary="EasyMega Screw Terminals" border="1"><colgroup><col align="center" class="Pin #"><col align="center" class="Pin Name"><col align="left" class="Description"></colgroup><thead><tr><th align="center">Terminal #</th><th align="center">Terminal Name</th><th align="center">Description</th></tr></thead><tbody><tr><td align="center">Top 1</td><td align="center">Switch Input</td><td align="left">Switch connection to positive battery terminal</td></tr><tr><td align="center">Top 2</td><td align="center">Switch Output</td><td align="left">Switch connection to flight computer</td></tr><tr><td align="center">Top 3</td><td align="center">GND</td><td align="left">Ground connection for use with external active switch</td></tr><tr><td align="center">Top 4</td><td align="center">Main -</td><td align="left">Main pyro channel connection to pyro circuit</td></tr><tr><td align="center">Top 5</td><td align="center">Main +</td><td align="left">Main pyro channel common connection to battery +</td></tr><tr><td align="center">Top 6</td><td align="center">Apogee -</td><td align="left">Apogee pyro channel connection to pyro circuit</td></tr><tr><td align="center">Top 7</td><td align="center">Apogee +</td><td align="left">Apogee pyro channel common connection to battery +</td></tr><tr><td align="center">Top 8</td><td align="center">D -</td><td align="left">D pyro channel connection to pyro circuit</td></tr><tr><td align="center">Top 9</td><td align="center">D +</td><td align="left">D pyro channel common connection to battery +</td></tr><tr><td align="center">Bottom 1</td><td align="center">GND</td><td align="left">Ground connection for negative pyro battery terminal</td></tr><tr><td align="center">Bottom 2</td><td align="center">Pyro</td><td align="left">Positive pyro battery terminal</td></tr><tr><td align="center">Bottom 3</td><td align="center">Lipo</td><td align="left">
Power switch output. Use to connect main battery to
pyro battery input
</td></tr><tr><td align="center">Bottom 4</td><td align="center">A -</td><td align="left">A pyro channel connection to pyro circuit</td></tr><tr><td align="center">Bottom 5</td><td align="center">A +</td><td align="left">A pyro channel common connection to battery +</td></tr><tr><td align="center">Bottom 6</td><td align="center">B -</td><td align="left">B pyro channel connection to pyro circuit</td></tr><tr><td align="center">Bottom 7</td><td align="center">B +</td><td align="left">B pyro channel common connection to battery +</td></tr><tr><td align="center">Bottom 8</td><td align="center">C -</td><td align="left">C pyro channel connection to pyro circuit</td></tr><tr><td align="center">Bottom 9</td><td align="center">C +</td><td align="left">C pyro channel common connection to battery +</td></tr></tbody></table></div></div><br class="table-break"></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49048064"></a>8.2. Using a Separate Pyro Battery with EasyMega</h3></div></div></div><p>
EasyMega provides explicit support for an external pyro
battery. All that is required is to remove the jumper
between the lipo terminal (Bottom 3) and the pyro terminal
(Bottom 2). Then hook the negative pyro battery terminal to ground
(Bottom 1) and the positive pyro battery to the pyro battery
input (Bottom 2). You can then use the existing pyro screw
terminals to hook up all of the pyro charges.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49049664"></a>8.3. Using Only One Battery With EasyMega</h3></div></div></div><p>
Because EasyMega has built-in support for a separate pyro
battery, if you want to fly with just one battery running
both the computer and firing the charges, you need to
connect the flight computer battery to the pyro
circuit. EasyMega has two screw terminals for this—hook a
wire from the Lipo terminal (Bottom 3) to the Pyro terminal
(Bottom 2).
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49051584"></a>8.4. Using an Active Switch with EasyMega</h3></div></div></div><p>
As explained above, an external active switch requires three
connections, one to the positive battery terminal, one to
the flight computer positive input and one to ground.
</p><p>
The positive battery terminal is available on Top terminal
1, the positive flight computer input is on Top terminal
2. Ground is on Top terminal 3.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49053632"></a>9. Flight Data Recording</h2></div></div></div><p>
Each flight computer logs data at 100 samples per second
during ascent and 10 samples per second during descent, except
for TeleMini v1.0, which records ascent at 10 samples per
second and descent at 1 sample per second. Data are logged to
an on-board flash memory part, which can be partitioned into
several equal-sized blocks, one for each flight.
</p><div class="table"><a name="idp49055040"></a><p class="title"><b>Table 4.9. Data Storage on Altus Metrum altimeters</b></p><div class="table-contents"><table summary="Data Storage on Altus Metrum altimeters" border="1"><colgroup><col align="center" class="Device"><col align="center" class="Bytes per sample"><col align="center" class="Total storage"><col align="center" class="Minutes of full-rate"></colgroup><thead><tr><th align="center">Device</th><th align="center">Bytes per Sample</th><th align="center">Total Storage</th><th align="center">Minutes at Full Rate</th></tr></thead><tbody><tr><td align="center">TeleMetrum v1.0</td><td align="center">8</td><td align="center">1MB</td><td align="center">20</td></tr><tr><td align="center">TeleMetrum v1.1 v1.2</td><td align="center">8</td><td align="center">2MB</td><td align="center">40</td></tr><tr><td align="center">TeleMetrum v2.0</td><td align="center">16</td><td align="center">8MB</td><td align="center">80</td></tr><tr><td align="center">TeleMini v1.0</td><td align="center">2</td><td align="center">5kB</td><td align="center">4</td></tr><tr><td align="center">TeleMini v2.0</td><td align="center">16</td><td align="center">1MB</td><td align="center">10</td></tr><tr><td align="center">EasyMini</td><td align="center">16</td><td align="center">1MB</td><td align="center">10</td></tr><tr><td align="center">TeleMega</td><td align="center">32</td><td align="center">8MB</td><td align="center">40</td></tr><tr><td align="center">EasyMega</td><td align="center">32</td><td align="center">8MB</td><td align="center">40</td></tr></tbody></table></div></div><br class="table-break"><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>
Configuration data is also stored in the flash memory on
TeleMetrum v1.x, TeleMini and EasyMini. This consumes 64kB
of flash space. This configuration space is not available
for storing flight log data. TeleMetrum v2.0, TeleMega and EasyMega
store configuration data in a bit of eeprom available within
the processor chip, leaving that space available in flash for
more flight data.
</p><p>
To compute the amount of space needed for a single flight, you
can multiply the expected ascent time (in seconds) by 100
times bytes-per-sample, multiply the expected descent time (in
seconds) by 10 times the bytes per sample and add the two
together. That will slightly under-estimate the storage (in
bytes) needed for the flight. For instance, a TeleMetrum v2.0 flight spending
20 seconds in ascent and 150 seconds in descent will take
about (20 * 1600) + (150 * 160) = 56000 bytes of storage. You
could store dozens of these flights in the on-board flash.
</p><p>
The default size allows for several flights on each flight
computer, except for TeleMini v1.0, which only holds data for a
single flight. You can adjust the size.
</p><p>
Altus Metrum flight computers will not overwrite existing
flight data, so be sure to download flight data and erase it
from the flight computer before it fills up. The flight
computer will still successfully control the flight even if it
cannot log data, so the only thing you will lose is the data.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49084400"></a>10. Installation</h2></div></div></div><p>
A typical installation involves attaching
only a suitable battery, a single pole switch for
power on/off, and two pairs of wires connecting e-matches for the
apogee and main ejection charges. All Altus Metrum products are
designed for use with single-cell batteries with 3.7 volts
nominal. TeleMini v2.0 and EasyMini may also be used with other
batteries as long as they supply between 4 and 12 volts.
</p><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>
By default, we use the unregulated output of the battery directly
to fire ejection charges. This works marvelously with standard
low-current e-matches like the J-Tek from MJG Technologies, and with
Quest Q2G2 igniters. However, if you want or need to use a separate
pyro battery, check out the “External Pyro Battery” section in this
manual for instructions on how to wire that up. The altimeters are
designed to work with an external pyro battery of no more than 15 volts.
</p><p>
Ejection charges are wired directly to the screw terminal block
at the aft end of the altimeter. You'll need a very small straight
blade screwdriver for these screws, such as you might find in a
jeweler's screwdriver set.
</p><p>
Except for TeleMini v1.0, the flight computers also use the
screw terminal block for the power switch leads. On TeleMini v1.0,
the power switch leads are soldered directly to the board and
can be connected directly to a switch.
</p><p>
For most air-frames, the integrated antennas are more than
adequate. However, if you are installing in a carbon-fiber or
metal electronics bay which is opaque to RF signals, you may need to
use off-board external antennas instead. In this case, you can
replace the stock UHF antenna wire with an edge-launched SMA connector,
and, on TeleMetrum v1, you can unplug the integrated GPS
antenna and select an appropriate off-board GPS antenna with
cable terminating in a U.FL connector.
</p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp49091680"></a>Chapter 5. 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="#idp49092320">1. Firmware Modes </a></span></dt><dt><span class="section"><a href="#idp49160720">2. GPS </a></span></dt><dt><span class="section"><a href="#idp49163504">3. Controlling An Altimeter Over The Radio Link</a></span></dt><dt><span class="section"><a href="#idp49174800">4. Ground Testing </a></span></dt><dt><span class="section"><a href="#idp49177552">5. Radio Link </a></span></dt><dt><span class="section"><a href="#idp49181552">6. APRS</a></span></dt><dt><span class="section"><a href="#idp49205872">7. Configurable Parameters</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49207792">7.1. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp49209840">7.2. Callsign</a></span></dt><dt><span class="section"><a href="#idp49211376">7.3. Telemetry/RDF/APRS Enable</a></span></dt><dt><span class="section"><a href="#idp49212672">7.4. Telemetry baud rate</a></span></dt><dt><span class="section"><a href="#idp49214240">7.5. APRS Interval</a></span></dt><dt><span class="section"><a href="#idp49215712">7.6. APRS SSID</a></span></dt><dt><span class="section"><a href="#idp49217056">7.7. Apogee Delay</a></span></dt><dt><span class="section"><a href="#idp49219648">7.8. Apogee Lockout</a></span></dt><dt><span class="section"><a href="#idp49221376">7.9. Main Deployment Altitude</a></span></dt><dt><span class="section"><a href="#idp49223072">7.10. Maximum Flight Log</a></span></dt><dt><span class="section"><a href="#idp49225216">7.11. Ignite Mode</a></span></dt><dt><span class="section"><a href="#idp49227328">7.12. Pad Orientation</a></span></dt><dt><span class="section"><a href="#idp49229568">7.13. Configurable Pyro Channels</a></span></dt></dl></dd></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49092320"></a>1. Firmware Modes </h2></div></div></div><p>
The AltOS firmware build for the altimeters has two
fundamental modes, “idle” and “flight”. Which of these modes
the firmware operates in is determined at start up time. For
TeleMetrum, TeleMega and EasyMega, which have accelerometers, the mode is
controlled by the orientation of the
rocket (well, actually the board, of course...) at the time
power is switched on. If the rocket is “nose up”, then
the flight computer assumes it's on a rail or rod being prepared for
launch, so the firmware chooses flight mode. However, if the
rocket is more or less horizontal, the firmware instead enters
idle mode. Since TeleMini v2.0 and EasyMini don't have an
accelerometer we can use to determine orientation, “idle” mode
is selected if the board is connected via USB to a computer,
otherwise the board enters “flight” mode. TeleMini v1.0
selects “idle” mode if it receives a command packet within the
first five seconds of operation.
</p><p>
At power on, the altimeter will beep out the battery voltage
to the nearest tenth of a volt. Each digit is represented by
a sequence of short “dit” beeps, with a pause between
digits. A zero digit is represented with one long “dah”
beep. Then there will be a short pause while the altimeter
completes initialization and self test, and decides which mode
to enter next.
</p><p>
Here's a short summary of all of the modes and the beeping (or
flashing, in the case of TeleMini v1) that accompanies each
mode. In the description of the beeping pattern, “dit” means a
short beep while "dah" means a long beep (three times as
long). “Brap” means a long dissonant tone.
</p><div class="table"><a name="idp49097680"></a><p class="title"><b>Table 5.1. AltOS Modes</b></p><div class="table-contents"><table summary="AltOS Modes" border="1"><colgroup><col align="center" class="Mode Name"><col align="center" class="Letter"><col align="center" class="Beeps"><col align="center" class="Description"></colgroup><thead><tr><th align="center">Mode Name</th><th align="center">Abbreviation</th><th align="center">Beeps</th><th align="center">Description</th></tr></thead><tbody><tr><td align="center">Startup</td><td align="center">S</td><td align="center">battery voltage in decivolts</td><td align="center">
<p>
Calibrating sensors, detecting orientation.
</p>
</td></tr><tr><td align="center">Idle</td><td align="center">I</td><td align="center">dit dit</td><td align="center">
<p>
Ready to accept commands over USB or radio link.
</p>
</td></tr><tr><td align="center">Pad</td><td align="center">P</td><td align="center">dit dah dah dit</td><td align="center">
<p>
Waiting for launch. Not listening for commands.
</p>
</td></tr><tr><td align="center">Boost</td><td align="center">B</td><td align="center">dah dit dit dit</td><td align="center">
<p>
Accelerating upwards.
</p>
</td></tr><tr><td align="center">Fast</td><td align="center">F</td><td align="center">dit dit dah dit</td><td align="center">
<p>
Decelerating, but moving faster than 200m/s.
</p>
</td></tr><tr><td align="center">Coast</td><td align="center">C</td><td align="center">dah dit dah dit</td><td align="center">
<p>
Decelerating, moving slower than 200m/s
</p>
</td></tr><tr><td align="center">Drogue</td><td align="center">D</td><td align="center">dah dit dit</td><td align="center">
<p>
Descending after apogee. Above main height.
</p>
</td></tr><tr><td align="center">Main</td><td align="center">M</td><td align="center">dah dah</td><td align="center">
<p>
Descending. Below main height.
</p>
</td></tr><tr><td align="center">Landed</td><td align="center">L</td><td align="center">dit dah dit dit</td><td align="center">
<p>
Stable altitude for at least ten seconds.
</p>
</td></tr><tr><td align="center">Sensor error</td><td align="center">X</td><td align="center">dah dit dit dah</td><td align="center">
<p>
Error detected during sensor calibration.
</p>
</td></tr></tbody></table></div></div><p><br class="table-break">
</p><p>
In flight or “pad” mode, the altimeter engages the flight
state machine, goes into transmit-only mode to send telemetry,
and waits for launch to be detected. Flight mode is indicated
by an “di-dah-dah-dit” (“P” for pad) on the beeper or lights,
followed by beeps or flashes indicating the state of the
pyrotechnic igniter continuity. One beep/flash indicates
apogee continuity, two beeps/flashes indicate main continuity,
three beeps/flashes indicate both apogee and main continuity,
and one longer “brap” sound which is made by rapidly
alternating between two tones indicates no continuity. For a
dual deploy flight, make sure you're getting three beeps or
flashes before launching! For apogee-only or motor eject
flights, do what makes sense.
</p><p>
If idle mode is entered, you will hear an audible “di-dit” or
see two short flashes (“I” for idle), and the flight state
machine is disengaged, thus no ejection charges will fire.
The altimeters also listen for the radio link when in idle
mode for requests sent via TeleDongle. Commands can be issued
in idle mode over either USB or the radio link
equivalently. TeleMini v1.0 only has the radio link. Idle
mode is useful for configuring the altimeter, for extracting
data from the on-board storage chip after flight, and for
ground testing pyro charges.
</p><p>
In “Idle” and “Pad” modes, once the mode indication
beeps/flashes and continuity indication has been sent, if
there is no space available to log the flight in on-board
memory, the flight computer will emit a warbling tone (much
slower than the “no continuity tone”)
</p><p>
Here's a summary of all of the “pad” and “idle” mode indications.
</p><div class="table"><a name="idp49134768"></a><p class="title"><b>Table 5.2. Pad/Idle Indications</b></p><div class="table-contents"><table summary="Pad/Idle Indications" border="1"><colgroup><col align="center" class="Name"><col align="center" class="Beeps"><col align="center" class="Description"></colgroup><thead><tr><th align="center">Name</th><th align="center">Beeps</th><th align="center">Description</th></tr></thead><tbody><tr><td align="center">Neither</td><td align="center">brap</td><td align="center">
<p>
No continuity detected on either apogee or main
igniters.
</p>
</td></tr><tr><td align="center">Apogee</td><td align="center">dit</td><td align="center">
<p>
Continuity detected only on apogee igniter.
</p>
</td></tr><tr><td align="center">Main</td><td align="center">dit dit</td><td align="center">
<p>
Continuity detected only on main igniter.
</p>
</td></tr><tr><td align="center">Both</td><td align="center">dit dit dit</td><td align="center">
<p>
Continuity detected on both igniters.
</p>
</td></tr><tr><td align="center">Storage Full</td><td align="center">warble</td><td align="center">
<p>
On-board data logging storage is full. This will
not prevent the flight computer from safely
controlling the flight or transmitting telemetry
signals, but no record of the flight will be
stored in on-board flash.
</p>
</td></tr></tbody></table></div></div><p><br class="table-break">
</p><p>
Once landed, the flight computer will signal that by emitting
the “Landed” sound described above, after which it will beep
out the apogee height (in meters). Each digit is represented
by a sequence of short “dit” beeps, with a pause between
digits. A zero digit is represented with one long “dah”
beep. The flight computer will continue to report landed mode
and beep out the maximum height until turned off.
</p><p>
One “neat trick” of particular value when TeleMetrum, TeleMega
or EasyMega are used with
very large air-frames, is that you can power the board up while the
rocket is horizontal, such that it comes up in idle mode. Then you can
raise the air-frame to launch position, and issue a 'reset' command
via TeleDongle over the radio link to cause the altimeter to reboot and
come up in flight mode. This is much safer than standing on the top
step of a rickety step-ladder or hanging off the side of a launch
tower with a screw-driver trying to turn on your avionics before
installing igniters!
</p><p>
TeleMini v1.0 is configured solely via the radio link. Of course, that
means you need to know the TeleMini radio configuration values
or you won't be able to communicate with it. For situations
when you don't have the radio configuration values, TeleMini v1.0
offers an 'emergency recovery' mode. In this mode, TeleMini is
configured as follows:
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Sets the radio frequency to 434.550MHz
</p></li><li class="listitem"><p>
Sets the radio calibration back to the factory value.
</p></li><li class="listitem"><p>
Sets the callsign to N0CALL
</p></li><li class="listitem"><p>
Does not go to 'pad' mode after five seconds.
</p></li></ul></div><p>
</p><p>
To get into 'emergency recovery' mode, first find the row of
four small holes opposite the switch wiring. Using a short
piece of small gauge wire, connect the outer two holes
together, then power TeleMini up. Once the red LED is lit,
disconnect the wire and the board should signal that it's in
'idle' mode after the initial five second startup period.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49160720"></a>2. GPS </h2></div></div></div><p>
TeleMetrum and TeleMega include a complete GPS receiver. A
complete explanation of how GPS works is beyond the scope of
this manual, but the bottom line is that the GPS receiver
needs to lock onto at least four satellites to obtain a solid
3 dimensional position fix and know what time it is.
</p><p>
The flight computers provide backup power to the GPS chip any time a
battery is connected. This allows the receiver to “warm start” on
the launch rail much faster than if every power-on were a GPS
“cold start”. In typical operations, powering up
on the flight line in idle mode while performing final air-frame
preparation will be sufficient to allow the GPS receiver to cold
start and acquire lock. Then the board can be powered down during
RSO review and installation on a launch rod or rail. When the board
is turned back on, the GPS system should lock very quickly, typically
long before igniter installation and return to the flight line are
complete.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49163504"></a>3. Controlling An Altimeter Over The Radio Link</h2></div></div></div><p>
One of the unique features of the Altus Metrum system is the
ability to create a two way command link between TeleDongle
and an altimeter using the digital radio transceivers
built into each device. This allows you to interact with the
altimeter from afar, as if it were directly connected to the
computer.
</p><p>
Any operation which can be performed with a flight computer can
either be done with the device directly connected to the
computer via the USB cable, or through the radio
link. TeleMini v1.0 doesn't provide a USB connector and so it is
always communicated with over radio. Select the appropriate
TeleDongle device when the list of devices is presented and
AltosUI will interact with an altimeter over the radio link.
</p><p>
One oddity in the current interface is how AltosUI selects the
frequency for radio communications. Instead of providing
an interface to specifically configure the frequency, it uses
whatever frequency was most recently selected for the target
TeleDongle device in Monitor Flight mode. If you haven't ever
used that mode with the TeleDongle in question, select the
Monitor Flight button from the top level UI, and pick the
appropriate TeleDongle device. Once the flight monitoring
window is open, select the desired frequency and then close it
down again. All radio communications will now use that frequency.
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Save Flight Data—Recover flight data from the rocket without
opening it up.
</p></li><li class="listitem"><p>
Configure altimeter apogee delays, main deploy heights
and additional pyro event conditions
to respond to changing launch conditions. You can also
'reboot' the altimeter. Use this to remotely enable the
flight computer by turning TeleMetrum or TeleMega on in “idle” mode,
then once the air-frame is oriented for launch, you can
reboot the altimeter and have it restart in pad mode
without having to climb the scary ladder.
</p></li><li class="listitem"><p>
Fire Igniters—Test your deployment charges without snaking
wires out through holes in the air-frame. Simply assemble the
rocket as if for flight with the apogee and main charges
loaded, then remotely command the altimeter to fire the
igniters.
</p></li></ul></div><p>
Operation over the radio link for configuring an altimeter, ground
testing igniters, and so forth uses the same RF frequencies as flight
telemetry. To configure the desired TeleDongle frequency, select
the monitor flight tab, then use the frequency selector and
close the window before performing other desired radio operations.
</p><p>
The flight computers only enable radio commanding in 'idle' mode.
TeleMetrum and TeleMega use the accelerometer to detect which orientation they
start up in, so make sure you have the flight computer lying horizontally when you turn
it on. Otherwise, it will start in 'pad' mode ready for
flight, and will not be listening for command packets from TeleDongle.
</p><p>
TeleMini listens for a command packet for five seconds after
first being turned on, if it doesn't hear anything, it enters
'pad' mode, ready for flight and will no longer listen for
command packets. The easiest way to connect to TeleMini is to
initiate the command and select the TeleDongle device. At this
point, the TeleDongle will be attempting to communicate with
the TeleMini. Now turn TeleMini on, and it should immediately
start communicating with the TeleDongle and the desired
operation can be performed.
</p><p>
You can monitor the operation of the radio link by watching the
lights on the devices. The red LED will flash each time a packet
is transmitted, while the green LED will light up on TeleDongle when
it is waiting to receive a packet from the altimeter.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49174800"></a>4. Ground Testing </h2></div></div></div><p>
An important aspect of preparing a rocket using electronic deployment
for flight is ground testing the recovery system. Thanks
to the bi-directional radio link central to the Altus Metrum system,
this can be accomplished in a TeleMega, TeleMetrum or TeleMini equipped rocket
with less work than you may be accustomed to with other systems. It
can even be fun!
</p><p>
Just prep the rocket for flight, then power up the altimeter
in “idle” mode (placing air-frame horizontal for TeleMetrum or TeleMega, or
selecting the Configure Altimeter tab for TeleMini). This will cause
the firmware to go into “idle” mode, in which the normal flight
state machine is disabled and charges will not fire without
manual command. You can now command the altimeter to fire the apogee
or main charges from a safe distance using your computer and
TeleDongle and the Fire Igniter tab to complete ejection testing.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49177552"></a>5. Radio Link </h2></div></div></div><p>
Our flight computers all incorporate an RF transceiver, but
it's not a full duplex system... each end can only be transmitting or
receiving at any given moment. So we had to decide how to manage the
link.
</p><p>
By design, the altimeter firmware listens for the radio link when
it's in “idle mode”, which
allows us to use the radio link to configure the rocket, do things like
ejection tests, and extract data after a flight without having to
crack open the air-frame. However, when the board is in “flight
mode”, the altimeter only
transmits and doesn't listen at all. That's because we want to put
ultimate priority on event detection and getting telemetry out of
the rocket through
the radio in case the rocket crashes and we aren't able to extract
data later...
</p><p>
We don't generally use a 'normal packet radio' mode like APRS
because they're just too inefficient. 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. We hope to fly boards to higher altitudes over
time, and would of course appreciate customer feedback on
performance in higher altitude flights!
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49181552"></a>6. APRS</h2></div></div></div><p>
TeleMetrum v2.0 and TeleMega 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>
APRS packets include an SSID (Secondary Station Identifier)
field that allows one operator to have multiple
transmitters. AltOS allows you to set this to a single digit
from 0 to 9, allowing you to fly multiple transmitters at the
same time while keeping the identify of each one separate in
the receiver. By default, the SSID is set to the last digit of
the device serial number.
</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="idp49185360"></a><p class="title"><b>Table 5.3. 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">Altimeter Battery Voltage</td></tr><tr><td align="center">4</td><td align="center">A3.7</td><td align="center">Apogee Igniter Voltage</td></tr><tr><td align="center">5</td><td align="center">M3.7</td><td align="center">Main Igniter Voltage</td></tr><tr><td align="center">6</td><td align="center">1286</td><td align="center">Device Serial Number</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, a primary battery at 4.0V, and
apogee and main igniters both at 3.7V from device 1286.
</p><pre class="screen">
L6 B4.0 A3.7 M3.7 1286
</pre><p>
</p><p>
Make sure your primary battery is above 3.8V, any connected
igniters are above 3.5V and GPS is locked with at least 5 or 6
satellites in view before flying. 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="idp49205872"></a>7. Configurable Parameters</h2></div></div></div><p>
Configuring an Altus Metrum altimeter for flight is very
simple. Even on our baro-only TeleMini and EasyMini boards,
the use of a Kalman filter means there is no need to set a
“mach delay”. The few configurable parameters can all be set
using AltosUI over USB or or radio link via TeleDongle. Read
the Configure Altimeter section in the AltosUI chapter below
for more information.
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49207792"></a>7.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
altimeter and TeleDongle 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="idp49209840"></a>7.2. Callsign</h3></div></div></div><p>
This sets the callsign used for telemetry, APRS and the
packet link. For telemetry and APRS, this is used to
identify the device. For the packet link, the callsign must
match that configured in AltosUI or the link will not
work. This is to prevent accidental configuration of another
Altus Metrum flight computer operating on the same frequency nearby.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49211376"></a>7.3. Telemetry/RDF/APRS Enable</h3></div></div></div><p>
You can completely disable the radio while in flight, if
necessary. This doesn't disable the packet link in idle
mode.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49212672"></a>7.4. Telemetry baud rate</h3></div></div></div><p>
This sets the modulation bit rate for data transmission for
both telemetry and packet link mode. Lower bit
rates will increase range while reducing the amount of data
that can be sent and increasing battery consumption. All
telemetry is done using a rate 1/2 constraint 4 convolution
code, so the actual data transmission rate is 1/2 of the
modulation bit rate specified here.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49214240"></a>7.5. 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="idp49215712"></a>7.6. APRS SSID</h3></div></div></div><p>
This selects the SSID reported in APRS packets. By default,
it is set to the last digit of the serial number, but you
can change this to any value from 0 to 9.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49217056"></a>7.7. Apogee Delay</h3></div></div></div><p>
Apogee delay is the number of seconds after the altimeter detects flight
apogee that the drogue charge should be fired. In most cases, this
should be left at the default of 0. However, if you are flying
redundant electronics such as for an L3 certification, you may wish
to set one of your altimeters to a positive delay so that both
primary and backup pyrotechnic charges do not fire simultaneously.
</p><p>
The Altus Metrum apogee detection algorithm fires exactly at
apogee. If you are also flying an altimeter like the
PerfectFlite MAWD, which only supports selecting 0 or 1
seconds of apogee delay, you may wish to set the MAWD to 0
seconds delay and set the TeleMetrum to fire your backup 2
or 3 seconds later to avoid any chance of both charges
firing simultaneously. We've flown several air-frames this
way quite happily, including Keith's successful L3 cert.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49219648"></a>7.8. Apogee Lockout</h3></div></div></div><p>
Apogee lockout is the number of seconds after boost where
the flight computer will not fire the apogee charge, even if
the rocket appears to be at apogee. This is often called
'Mach Delay', as it is intended to prevent a flight computer
from unintentionally firing apogee charges due to the pressure
spike that occurrs across a mach transition. Altus Metrum
flight computers include a Kalman filter which is not fooled
by this sharp pressure increase, and so this setting should
be left at the default value of zero to disable it.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49221376"></a>7.9. Main Deployment Altitude</h3></div></div></div><p>
By default, the altimeter will fire the main deployment charge at an
elevation of 250 meters (about 820 feet) above ground. We think this
is a good elevation for most air-frames, but feel free to change this
to suit. In particular, if you are flying two altimeters, you may
wish to set the
deployment elevation for the backup altimeter to be something lower
than the primary so that both pyrotechnic charges don't fire
simultaneously.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49223072"></a>7.10. 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><p>
Even though our flight computers (except TeleMini v1.0) can store
multiple flights, we strongly recommend downloading and saving
flight data after each flight.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49225216"></a>7.11. Ignite Mode</h3></div></div></div><p>
Instead of firing one charge at apogee and another charge at
a fixed height above the ground, you can configure the
altimeter to fire both at apogee or both during
descent. This was added to support an airframe Bdale designed that
had two altimeters, one in the fin can and one in the nose.
</p><p>
Providing the ability to use both igniters for apogee or
main allows some level of redundancy without needing two
flight computers. In Redundant Apogee or Redundant Main
mode, the two charges will be fired two seconds apart.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49227328"></a>7.12. Pad Orientation</h3></div></div></div><p>
TeleMetrum, TeleMega and EasyMega measure acceleration along the axis
of the board. Which way the board is oriented affects the
sign of the acceleration value. Instead of trying to guess
which way the board is mounted in the air frame, the
altimeter must be explicitly configured for either Antenna
Up or Antenna Down. The default, Antenna Up, expects the end
of the board connected to the 70cm antenna to be nearest the
nose of the rocket, with the end containing the screw
terminals nearest the tail.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49229568"></a>7.13. Configurable Pyro Channels</h3></div></div></div><p>
In addition to the usual Apogee and Main pyro channels,
TeleMega and EasyMega have four additional channels that can be configured
to activate when various flight conditions are
satisfied. You can select as many conditions as necessary;
all of them must be met in order to activate the
channel. The conditions available are:
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Acceleration away from the ground. Select a value, and
then choose whether acceleration should be above or
below that value. Acceleration is positive upwards, so
accelerating towards the ground would produce negative
numbers. Acceleration during descent is noisy and
inaccurate, so be careful when using it during these
phases of the flight.
</p></li><li class="listitem"><p>
Vertical speed. Select a value, and then choose whether
vertical speed should be above or below that
value. Speed is positive upwards, so moving towards the
ground would produce negative numbers. Speed during
descent is a bit noisy and so be careful when using it
during these phases of the flight.
</p></li><li class="listitem"><p>
Height. Select a value, and then choose whether the
height above the launch pad should be above or below
that value.
</p></li><li class="listitem"><p>
Orientation. TeleMega and EasyMega contain a 3-axis gyroscope and
accelerometer which is used to measure the current
angle. Note that this angle is not the change in angle
from the launch pad, but rather absolute relative to
gravity; the 3-axis accelerometer is used to compute the
angle of the rocket on the launch pad and initialize the
system. Because this value is computed by integrating
rate gyros, it gets progressively less accurate as the
flight goes on. It should have an accumulated error of
less than 0.2°/second (after 10 seconds of flight, the
error should be less than 2°).
</p><p>
The usual use of the orientation configuration is to
ensure that the rocket is traveling mostly upwards when
deciding whether to ignite air starts or additional
stages. For that, choose a reasonable maximum angle
(like 20°) and set the motor igniter to require an angle
of less than that value.
</p></li><li class="listitem"><p>
Flight Time. Time since boost was detected. Select a
value and choose whether to activate the pyro channel
before or after that amount of time.
</p></li><li class="listitem"><p>
Ascending. A simple test saying whether the rocket is
going up or not. This is exactly equivalent to testing
whether the speed is > 0.
</p></li><li class="listitem"><p>
Descending. A simple test saying whether the rocket is
going down or not. This is exactly equivalent to testing
whether the speed is < 0.
</p></li><li class="listitem"><p>
After Motor. The flight software counts each time the
rocket starts accelerating (presumably due to a motor or
motors igniting). Use this value to count ignitions for
multi-staged or multi-airstart launches.
</p></li><li class="listitem"><p>
Delay. This value doesn't perform any checks, instead it
inserts a delay between the time when the other
parameters become true and when the pyro channel is
activated.
</p></li><li class="listitem"><p>
Flight State. The flight software tracks the flight
through a sequence of states:
</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>
Boost. The motor has lit and the rocket is
accelerating upwards.
</p></li><li class="listitem"><p>
Fast. The motor has burned out and the rocket is
decelerating, but it is going faster than 200m/s.
</p></li><li class="listitem"><p>
Coast. The rocket is still moving upwards and
decelerating, but the speed is less than 200m/s.
</p></li><li class="listitem"><p>
Drogue. The rocket has reached apogee and is heading
back down, but is above the configured Main
altitude.
</p></li><li class="listitem"><p>
Main. The rocket is still descending, and is below
the Main altitude
</p></li><li class="listitem"><p>
Landed. The rocket is no longer moving.
</p></li></ol></div><p>
</p><p>
You can select a state to limit when the pyro channel
may activate; note that the check is based on when the
rocket transitions <span class="emphasis"><em>into</em></span> the state, and so checking for
“greater than Boost” means that the rocket is currently
in boost or some later state.
</p><p>
When a motor burns out, the rocket enters either Fast or
Coast state (depending on how fast it is moving). If the
computer detects upwards acceleration again, it will
move back to Boost state.
</p></li></ul></div></div></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp49252176"></a>Chapter 6. AltosUI</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp49255792">1. Monitor Flight</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49268512">1.1. Launch Pad</a></span></dt><dt><span class="section"><a href="#idp49284800">1.2. Ascent</a></span></dt><dt><span class="section"><a href="#idp49290256">1.3. Descent</a></span></dt><dt><span class="section"><a href="#idp49297120">1.4. Landed</a></span></dt><dt><span class="section"><a href="#idp49303552">1.5. Table</a></span></dt><dt><span class="section"><a href="#idp49307136">1.6. Site Map</a></span></dt><dt><span class="section"><a href="#idp49313856">1.7. Ignitor</a></span></dt></dl></dd><dt><span class="section"><a href="#idp49317632">2. Save Flight Data</a></span></dt><dt><span class="section"><a href="#idp49321584">3. Replay Flight</a></span></dt><dt><span class="section"><a href="#idp49323616">4. Graph Data</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49326000">4.1. Flight Graph</a></span></dt><dt><span class="section"><a href="#idp49330448">4.2. Configure Graph</a></span></dt><dt><span class="section"><a href="#idp49334112">4.3. Flight Statistics</a></span></dt><dt><span class="section"><a href="#idp49337632">4.4. Map</a></span></dt></dl></dd><dt><span class="section"><a href="#idp49341488">5. Export Data</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49343056">5.1. Comma Separated Value Format</a></span></dt><dt><span class="section"><a href="#idp49345408">5.2. Keyhole Markup Language (for Google Earth)</a></span></dt></dl></dd><dt><span class="section"><a href="#idp49346896">6. Configure Altimeter</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49359200">6.1. Main Deploy Altitude</a></span></dt><dt><span class="section"><a href="#idp49360768">6.2. Apogee Delay</a></span></dt><dt><span class="section"><a href="#idp49362384">6.3. Apogee Lockoug</a></span></dt><dt><span class="section"><a href="#idp49364112">6.4. Frequency</a></span></dt><dt><span class="section"><a href="#idp49365616">6.5. RF Calibration</a></span></dt><dt><span class="section"><a href="#idp49367264">6.6. Telemetry/RDF/APRS Enable</a></span></dt><dt><span class="section"><a href="#idp49368560">6.7. Telemetry baud rate</a></span></dt><dt><span class="section"><a href="#idp49370128">6.8. APRS Interval</a></span></dt><dt><span class="section"><a href="#idp49371696">6.9. APRS SSID</a></span></dt><dt><span class="section"><a href="#idp49373024">6.10. Callsign</a></span></dt><dt><span class="section"><a href="#idp49374336">6.11. Maximum Flight Log Size</a></span></dt><dt><span class="section"><a href="#idp49375776">6.12. Ignitor Firing Mode</a></span></dt><dt><span class="section"><a href="#idp49382688">6.13. Pad Orientation</a></span></dt><dt><span class="section"><a href="#idp49387920">6.14. Beeper Frequency</a></span></dt><dt><span class="section"><a href="#idp49389376">6.15. Configure Pyro Channels</a></span></dt></dl></dd><dt><span class="section"><a href="#idp49395760">7. Configure AltosUI</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49399264">7.1. Voice Settings</a></span></dt><dt><span class="section"><a href="#idp49404288">7.2. Log Directory</a></span></dt><dt><span class="section"><a href="#idp49406288">7.3. Callsign</a></span></dt><dt><span class="section"><a href="#idp49408528">7.4. Imperial Units</a></span></dt><dt><span class="section"><a href="#idp49410032">7.5. Font Size</a></span></dt><dt><span class="section"><a href="#idp49411312">7.6. Serial Debug</a></span></dt><dt><span class="section"><a href="#idp49412816">7.7. Manage Frequencies</a></span></dt></dl></dd><dt><span class="section"><a href="#idp49414448">8. Configure Groundstation</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49425568">8.1. Frequency</a></span></dt><dt><span class="section"><a href="#idp49427136">8.2. RF Calibration</a></span></dt><dt><span class="section"><a href="#idp49428656">8.3. Telemetry Rate</a></span></dt></dl></dd><dt><span class="section"><a href="#idp49430128">9. Flash Image</a></span></dt><dt><span class="section"><a href="#idp49431776">10. Fire Igniter</a></span></dt><dt><span class="section"><a href="#idp49437408">11. Scan Channels</a></span></dt><dt><span class="section"><a href="#idp49441632">12. Load Maps</a></span></dt><dt><span class="section"><a href="#idp49455600">13. Monitor Idle</a></span></dt></dl></div><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="414"><tr><td><img src="altosui.png" width="414"></td></tr></table></div></div><p>
The AltosUI program provides a graphical user interface for
interacting with the Altus Metrum product family. AltosUI can
monitor telemetry data, configure devices and many other
tasks. The primary interface window provides a selection of
buttons, one for each major activity in the system. 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="idp49255792"></a>1. Monitor Flight</h2></div><div><h3 class="subtitle">Receive, Record and Display Telemetry Data</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 create a window to 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><p>
All telemetry data received are automatically recorded in
suitable log files. The name of the files includes the current
date and rocket 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. AltosUI 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. Each altimeter remembers how many
times it has flown.
</p></li><li class="listitem"><p>
The rocket flight state. Each flight passes through several
states including Pad, Boost, Fast, Coast, Drogue, Main and
Landed.
</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 -99dBm;
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 rocket.
They're arranged in 'flight order' so that as the flight
progresses, the selected tab automatically switches to display
data relevant to the current state of the flight. You can select
other tabs at any time. The final 'table' tab displays all 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="idp49268512"></a>1.1. Launch Pad</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="495"><tr><td><img src="launch-pad.png" width="495"></td></tr></table></div></div><p>
The 'Launch Pad' tab shows information used to decide when the
rocket is ready for flight. The first elements include red/green
indicators, if any of these is red, you'll want to evaluate
whether the rocket is ready to launch:
</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">Battery Voltage</span></dt><dd><p>
This indicates whether the Li-Po battery powering the
flight computer has sufficient charge to last for
the duration of the flight. A value of more than
3.8V is required for a 'GO' status.
</p></dd><dt><span class="term">Apogee Igniter Voltage</span></dt><dd><p>
This indicates whether the apogee
igniter has continuity. If the igniter has a low
resistance, then the voltage measured here will be close
to the Li-Po battery voltage. A value greater than 3.2V is
required for a 'GO' status.
</p></dd><dt><span class="term">Main Igniter Voltage</span></dt><dd><p>
This indicates whether the main
igniter has continuity. If the igniter has a low
resistance, then the voltage measured here will be close
to the Li-Po battery voltage. A value greater than 3.2V is
required for a 'GO' status.
</p></dd><dt><span class="term">On-board Data Logging</span></dt><dd><p>
This indicates whether there is
space remaining on-board to store flight data for the
upcoming flight. If you've downloaded data, but failed
to erase flights, there may not be any space
left. Most of our flight computers can store multiple
flights, depending on the configured maximum flight log
size. TeleMini v1.0 stores only a single flight, so it
will need to be
downloaded and erased after each flight to capture
data. This only affects on-board flight logging; the
altimeter will still transmit telemetry and fire
ejection charges at the proper times even if the flight
data storage is full.
</p></dd><dt><span class="term">GPS Locked</span></dt><dd><p>
For a TeleMetrum or TeleMega device, this indicates whether the GPS receiver is
currently able to compute position information. GPS requires
at least 4 satellites to compute an accurate position.
</p></dd><dt><span class="term">GPS Ready</span></dt><dd><p>
For a TeleMetrum or TeleMega device, this indicates whether GPS has reported at least
10 consecutive positions without losing lock. This ensures
that the GPS receiver has reliable reception from the
satellites.
</p></dd></dl></div><p>
</p><p>
The Launchpad tab also shows the computed launch pad position
and altitude, averaging many reported positions to improve the
accuracy of the fix.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49284800"></a>1.2. Ascent</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="495"><tr><td><img src="ascent.png" width="495"></td></tr></table></div></div><p>
This tab is shown during Boost, Fast and Coast
phases. The information displayed here helps monitor the
rocket as it heads towards apogee.
</p><p>
The height, speed, acceleration and tilt are shown along
with the maximum values for each of them. This allows you to
quickly answer the most commonly asked questions you'll hear
during flight.
</p><p>
The current latitude and longitude reported by the GPS are
also shown. Note that under high acceleration, these values
may not get updated as the GPS receiver loses position
fix. Once the rocket starts coasting, the receiver should
start reporting position again.
</p><p>
Finally, the current igniter voltages are reported as in the
Launch Pad tab. This can help diagnose deployment failures
caused by wiring which comes loose under high acceleration.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49290256"></a>1.3. Descent</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="495"><tr><td><img src="descent.png" width="495"></td></tr></table></div></div><p>
Once the rocket has reached apogee and (we hope) activated the
apogee charge, attention switches to tracking the rocket on
the way back to the ground, and for dual-deploy flights,
waiting for the main charge to fire.
</p><p>
To monitor whether the apogee charge operated correctly, the
current descent rate is reported along with the current
height. Good descent rates vary based on the choice of recovery
components, but generally range from 15-30m/s on drogue and should
be below 10m/s when under the main parachute in a dual-deploy flight.
</p><p>
With GPS-equipped flight computers, you can locate the rocket in the
sky using the elevation and bearing information to figure
out where to look. Elevation is in degrees above the
horizon. Bearing is reported in degrees relative to true
north. Range can help figure out how big the rocket will
appear. Ground Distance shows how far it is to a point
directly under the rocket and can help figure out where the
rocket is likely to land. Note that all of these values are
relative to the pad location. If the elevation is near 90°,
the rocket is over the pad, not over you.
</p><p>
Finally, the igniter voltages are reported in this tab as
well, both to monitor the main charge as well as to see what
the status of the apogee charge is. Note that some commercial
e-matches are designed to retain continuity even after being
fired, and will continue to show as green or return from red to
green after firing.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49297120"></a>1.4. Landed</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="495"><tr><td><img src="landed.png" width="495"></td></tr></table></div></div><p>
Once the rocket is on the ground, attention switches to
recovery. While the radio signal is often lost once the
rocket is on the ground, the last reported GPS position is
generally within a short distance of the actual landing location.
</p><p>
The last reported GPS position is reported both by
latitude and longitude as well as a bearing and distance from
the launch pad. The distance should give you a good idea of
whether to walk or hitch a ride. Take the reported
latitude and longitude and enter them into your hand-held GPS
unit and have that compute a track to the landing location.
</p><p>
Our flight computers will continue to transmit RDF
tones after landing, allowing you to locate the rocket by
following the radio signal if necessary. You may need to get
away from the clutter of the flight line, or even get up on
a hill (or your neighbor's RV roof) to receive the RDF signal.
</p><p>
The maximum height, speed and acceleration reported
during the flight are displayed for your admiring observers.
The accuracy of these immediate values depends on the quality
of your radio link and how many packets were received.
Recovering the on-board data after flight may yield
more precise results.
</p><p>
To get more detailed information about the flight, you can
click on the 'Graph Flight' button which will bring up a
graph window for the current flight.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49303552"></a>1.5. Table</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="495"><tr><td><img src="table.png" width="495"></td></tr></table></div></div><p>
The table view shows all of the data available from the
flight computer. Probably the most useful data on
this tab is the detailed GPS information, which includes
horizontal dilution of precision information, and
information about the signal being received from the satellites.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49307136"></a>1.6. Site Map</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="495"><tr><td><img src="site-map.png" width="495"></td></tr></table></div></div><p>
When the TeleMetrum has a GPS fix, the Site Map tab will map
the rocket's position to make it easier for you to locate the
rocket, both while it is in the air, and when it has landed. The
rocket's state is indicated by color: white for pad, red for
boost, pink for fast, yellow for coast, light blue for drogue,
dark blue for main, and black for landed.
</p><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="idp49313856"></a>1.7. Ignitor</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="495"><tr><td><img src="ignitor.png" width="495"></td></tr></table></div></div><p>
TeleMega includes four additional programmable pyro
channels. The Ignitor tab shows whether each of them has
continuity. If an ignitor has a low resistance, then the
voltage measured here will be close to the pyro battery
voltage. A value greater than 3.2V is required for a 'GO'
status.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49317632"></a>2. Save Flight Data</h2></div></div></div><p>
The altimeter records flight data to its internal flash memory.
TeleMetrum data is recorded at a much higher rate than the telemetry
system can handle, and is not subject to radio drop-outs. As
such, it provides a more complete and precise record of the
flight. The 'Save Flight Data' button allows you to read the
flash memory and write it to disk.
</p><p>
Clicking on the 'Save Flight Data' button brings up a list of
connected flight computers and TeleDongle devices. If you select a
flight computer, the flight data will be downloaded from that
device directly. If you select a TeleDongle device, flight data
will be downloaded from a flight computer over radio link via the
specified TeleDongle. See the chapter on Controlling An Altimeter
Over The Radio Link for more information.
</p><p>
After the device has been selected, a dialog showing the
flight data saved in the device will be shown allowing you to
select which flights to download and which to delete. With
version 0.9 or newer firmware, you must erase flights in order
for the space they consume to be reused by another
flight. This prevents accidentally losing flight data
if you neglect to download data before flying again. Note that
if there is no more space available in the device, then no
data will be recorded during the next flight.
</p><p>
The file name for each flight log is computed automatically
from the recorded flight date, altimeter serial number and
flight number information.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49321584"></a>3. Replay Flight</h2></div></div></div><p>
Select this button and you are prompted to select a flight
record file, either a .telem file recording telemetry data or a
.eeprom file containing flight data saved from the altimeter
flash memory.
</p><p>
Once a flight record is selected, the flight monitor interface
is displayed and the flight is re-enacted in real time. Check
the Monitor Flight chapter above to learn how this window operates.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49323616"></a>4. Graph Data</h2></div></div></div><p>
Select this button and you are prompted to select a flight
record file, either a .telem file recording telemetry data or a
.eeprom file containing flight data saved from
flash memory.
</p><p>
Note that telemetry files will generally produce poor graphs
due to the lower sampling rate and missed telemetry packets.
Use saved flight data in .eeprom files for graphing where possible.
</p><p>
Once a flight record is selected, a window with multiple tabs is
opened.
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49326000"></a>4.1. Flight Graph</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="540"><tr><td><img src="graph.png" width="540"></td></tr></table></div></div><p>
By default, the graph contains acceleration (blue),
velocity (green) and altitude (red).
</p><p>
The graph can be zoomed into a particular area by clicking and
dragging down and to the right. Once zoomed, the graph can be
reset by clicking and dragging up and to the left. Holding down
control and clicking and dragging allows the graph to be panned.
The right mouse button causes a pop-up menu to be displayed, giving
you the option save or print the plot.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49330448"></a>4.2. Configure Graph</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="540"><tr><td><img src="graph-configure.png" width="540"></td></tr></table></div></div><p>
This selects which graph elements to show, and, at the
very bottom, lets you switch between metric and
imperial units
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49334112"></a>4.3. Flight Statistics</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="540"><tr><td><img src="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><h3 class="title"><a name="idp49337632"></a>4.4. Map</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="540"><tr><td><img src="graph-map.png" width="540"></td></tr></table></div></div><p>
Shows a satellite image of the flight area overlaid
with the path of the flight. The red concentric
circles mark the launch pad, the black concentric
circles mark the landing location.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49341488"></a>5. Export Data</h2></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 flight 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><h3 class="title"><a name="idp49343056"></a>5.1. Comma Separated Value Format</h3></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 the altimeter, 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><h3 class="title"><a name="idp49345408"></a>5.2. Keyhole Markup Language (for Google Earth)</h3></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><h2 class="title" style="clear: both"><a name="idp49346896"></a>6. Configure Altimeter</h2></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="configure-altimeter.png" width="324"></td></tr></table></div></div><p>
Select this button and then select either an altimeter or
TeleDongle Device from the list provided. Selecting a TeleDongle
device will use the radio link to configure a remote altimeter.
</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. Use this to
switch from idle to pad mode by rebooting once the rocket is
oriented for flight, or to confirm changes you think you saved
are really saved.
</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><h3 class="title"><a name="idp49359200"></a>6.1. Main Deploy Altitude</h3></div></div></div><p>
This sets the altitude (above the recorded pad altitude) at
which the 'main' igniter will fire. The drop-down menu shows
some common values, but you can edit the text directly and
choose whatever you like. If the apogee charge fires below
this altitude, then the main charge will fire two seconds
after the apogee charge fires.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49360768"></a>6.2. Apogee Delay</h3></div></div></div><p>
When flying redundant electronics, it's often important to
ensure that multiple apogee charges don't fire at precisely
the same time, as that can over pressurize the apogee deployment
bay and cause a structural failure of the air-frame. The Apogee
Delay parameter tells the flight computer to fire the apogee
charge a certain number of seconds after apogee has been
detected.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49362384"></a>6.3. Apogee Lockoug</h3></div></div></div><p>
Apogee lockout is the number of seconds after boost where
the flight computer will not fire the apogee charge, even if
the rocket appears to be at apogee. This is often called
'Mach Delay', as it is intended to prevent a flight computer
from unintentionally firing apogee charges due to the pressure
spike that occurrs across a mach transition. Altus Metrum
flight computers include a Kalman filter which is not fooled
by this sharp pressure increase, and so this setting should
be left at the default value of zero to disable it.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49364112"></a>6.4. Frequency</h3></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><h3 class="title"><a name="idp49365616"></a>6.5. RF Calibration</h3></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><h3 class="title"><a name="idp49367264"></a>6.6. Telemetry/RDF/APRS Enable</h3></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><h3 class="title"><a name="idp49368560"></a>6.7. Telemetry baud rate</h3></div></div></div><p>
This sets the modulation bit rate for data transmission for
both telemetry and packet link mode. Lower bit
rates will increase range while reducing the amount of data
that can be sent and increasing battery consumption. All
telemetry is done using a rate 1/2 constraint 4 convolution
code, so the actual data transmission rate is 1/2 of the
modulation bit rate specified here.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49370128"></a>6.8. APRS Interval</h3></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><h3 class="title"><a name="idp49371696"></a>6.9. APRS SSID</h3></div></div></div><p>
Which SSID to report in APRS packets. By default, this is
set to the last digit of the serial number, but can be
configured to any value from 0 to 9.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49373024"></a>6.10. Callsign</h3></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><h3 class="title"><a name="idp49374336"></a>6.11. Maximum Flight Log Size</h3></div></div></div><p>
This sets the space (in kilobytes) allocated for each flight
log. The available space will be divided into chunks of this
size. A smaller value will allow more flights to be stored,
a larger value will record data from longer flights.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49375776"></a>6.12. Ignitor Firing Mode</h3></div></div></div><p>
This configuration parameter allows the two standard ignitor
channels (Apogee and Main) to be used in different
configurations.
</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">Dual Deploy</span></dt><dd><p>
This is the usual mode of operation; the
'apogee' channel is fired at apogee and the 'main'
channel at the height above ground specified by the
'Main Deploy Altitude' during descent.
</p></dd><dt><span class="term">Redundant Apogee</span></dt><dd><p>
This fires both channels at
apogee, the 'apogee' channel first followed after a two second
delay by the 'main' channel.
</p></dd><dt><span class="term">Redundant Main</span></dt><dd><p>
This fires both channels at the
height above ground specified by the Main Deploy
Altitude setting during descent. The 'apogee'
channel is fired first, followed after a two second
delay by the 'main' channel.
</p></dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49382688"></a>6.13. Pad Orientation</h3></div></div></div><p>
Because they include accelerometers, TeleMetrum,
TeleMega and EasyMega are sensitive to the orientation of the board. By
default, they expect the antenna end to point forward. This
parameter allows that default to be changed, permitting the
board to be mounted with the antenna pointing aft instead.
</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">Antenna Up</span></dt><dd><p>
In this mode, the antenna end of the
flight computer must point forward, in line with the
expected flight path.
</p></dd><dt><span class="term">Antenna Down</span></dt><dd><p>
In this mode, the antenna end of the
flight computer must point aft, in line with the
expected flight path.
</p></dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49387920"></a>6.14. Beeper Frequency</h3></div></div></div><p>
The beeper on all Altus Metrum flight computers works best
at 4000Hz, however if you have more than one flight computer
in a single airframe, having all of them sound at the same
frequency can be confusing. This parameter lets you adjust
the base beeper frequency value.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49389376"></a>6.15. Configure Pyro Channels</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="540"><tr><td><img src="configure-pyro.png" width="540"></td></tr></table></div></div><p>
This opens a separate window to configure the additional
pyro channels available on TeleMega and EasyMega. One column is
presented for each channel. Each row represents a single
parameter, if enabled the parameter must meet the specified
test for the pyro channel to be fired. See the Pyro Channels
section in the System Operation chapter above for a
description of these parameters.
</p><p>
Select conditions and set the related value; the pyro
channel will be activated when <span class="emphasis"><em>all</em></span> of the
conditions are met. Each pyro channel has a separate set of
configuration values, so you can use different values for
the same condition with different channels.
</p><p>
At the bottom of the window, the 'Pyro Firing Time'
configuration sets the length of time (in seconds) which
each of these pyro channels will fire for.
</p><p>
Once you have selected the appropriate configuration for all
of the necessary pyro channels, you can save the pyro
configuration along with the rest of the flight computer
configuration by pressing the 'Save' button in the main
Configure Flight Computer window.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49395760"></a>7. Configure AltosUI</h2></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="configure-altosui.png" width="216"></td></tr></table></div></div><p>
This button presents a dialog so that you can configure the AltosUI global settings.
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49399264"></a>7.1. Voice Settings</h3></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><h3 class="title"><a name="idp49404288"></a>7.2. Log Directory</h3></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><h3 class="title"><a name="idp49406288"></a>7.3. Callsign</h3></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><h3 class="title"><a name="idp49408528"></a>7.4. Imperial Units</h3></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><h3 class="title"><a name="idp49410032"></a>7.5. Font Size</h3></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><h3 class="title"><a name="idp49411312"></a>7.6. Serial Debug</h3></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><h3 class="title"><a name="idp49412816"></a>7.7. Manage Frequencies</h3></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><h2 class="title" style="clear: both"><a name="idp49414448"></a>8. Configure Groundstation</h2></div></div></div><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="configure-groundstation.png" width="279"></td></tr></table></div></div><p>
Select this button and then select a TeleDongle or TeleBT 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>
Note that TeleDongle and TeleBT don't save any configuration
data, the settings here are recorded on the local machine in
the Java preferences database. Moving the device to
another machine, or using a different user account on the same
machine will cause settings made here to have no effect.
</p><p>
At the bottom of the dialog, there are three buttons:
</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">Save</span></dt><dd><p>
This writes any changes to the
local Java preferences file. 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">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><h3 class="title"><a name="idp49425568"></a>8.1. Frequency</h3></div></div></div><p>
This configures the frequency to use for both telemetry and
packet command mode. Set this before starting any operation
involving packet command mode so that it will use the right
frequency. Telemetry monitoring mode also provides a menu to
change the frequency, and that menu also sets the same Java
preference value used here.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49427136"></a>8.2. RF Calibration</h3></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. To change a TeleDongle or TeleBT's calibration,
you must reprogram the unit completely, so this entry simply
shows the current value and doesn't allow any changes.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49428656"></a>8.3. Telemetry Rate</h3></div></div></div><p>
This lets you match the telemetry and packet link rate from
the transmitter. If they don't match, the device won't
receive any data.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49430128"></a>9. Flash Image</h2></div></div></div><p>
This reprograms Altus Metrum devices with new
firmware. TeleMetrum v1.x, TeleDongle, TeleMini and TeleBT are
all reprogrammed by using another similar unit as a
programming dongle (pair programming). TeleMega, EasyMega, TeleMetrum v2
and EasyMini are all programmed directly over their USB ports
(self programming). Please read the directions for flashing
devices in the Updating Device Firmware chapter below.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49431776"></a>10. Fire Igniter</h2></div></div></div><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="108"><tr><td><img src="fire-igniter.png" width="108"></td></tr></table></div></div><p>
This activates the igniter circuits in the flight computer to help
test recovery systems deployment. Because this command can operate
over the Packet Command Link, you can prepare the rocket as
for flight and then test the recovery system without needing
to snake wires inside the air-frame.
</p><p>
Selecting the 'Fire Igniter' button brings up the usual device
selection dialog. Pick the desired device. This brings up another
window which shows the current continuity test status for all
of the pyro channels.
</p><p>
Next, select the desired igniter to fire. This will enable the
'Arm' button.
</p><p>
Select the 'Arm' button. This enables the 'Fire' button. The
word 'Arm' is replaced by a countdown timer indicating that
you have 10 seconds to press the 'Fire' button or the system
will deactivate, at which point you start over again at
selecting the desired igniter.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49437408"></a>11. Scan Channels</h2></div></div></div><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="288"><tr><td><img src="scan-channels.png" width="288"></td></tr></table></div></div><p>
This listens for telemetry packets on all of the configured
frequencies, displaying information about each device it
receives a packet from. You can select which of the baud rates
and telemetry formats should be tried; by default, it only listens
at 38400 baud with the standard telemetry format used in v1.0 and later
firmware.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49441632"></a>12. Load Maps</h2></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 heading out to a new launch site, you can use this to
load satellite images in case you don't have internet
connectivity at the site. This loads a fairly large area
around the launch site, which should cover any flight you're likely to make.
</p><p>
There's a drop-down menu of 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><h2 class="title" style="clear: both"><a name="idp49455600"></a>13. Monitor Idle</h2></div></div></div><p>
This brings up a dialog similar to the Monitor Flight UI,
except it works with the altimeter in “idle” mode by sending
query commands to discover the current state rather than
listening for telemetry packets. Because this uses command
mode, it needs to have the TeleDongle and flight computer
callsigns match exactly. If you can receive telemetry, but
cannot manage to run Monitor Idle, then it's very likely that
your callsigns are different in some way.
</p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp49457696"></a>Chapter 7. AltosDroid</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp49460080">1. Installing AltosDroid</a></span></dt><dt><span class="section"><a href="#idp49462016">2. Connecting to TeleBT</a></span></dt><dt><span class="section"><a href="#idp49464016">3. Configuring AltosDroid</a></span></dt><dt><span class="section"><a href="#idp49465472">4. AltosDroid Flight Monitoring</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49466784">4.1. Pad</a></span></dt></dl></dd><dt><span class="section"><a href="#idp49480336">5. Downloading Flight Logs</a></span></dt></dl></div><p>
AltosDroid provides the same flight monitoring capabilities as
AltosUI, but runs on Android devices and is designed to connect
to a TeleBT receiver over Bluetooth™. AltosDroid monitors
telemetry data, logging it to internal storage in the Android
device, and presents that data in a UI the same way the 'Monitor
Flight' window does in AltosUI.
</p><p>
This manual will explain how to configure AltosDroid, connect
to TeleBT, operate the flight monitoring interface and describe
what the displayed data means.
</p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49460080"></a>1. Installing AltosDroid</h2></div></div></div><p>
AltosDroid is available from the Google Play store. To install
it on your Android device, open the Google Play Store
application and search for “altosdroid”. Make sure you don't
have a space between “altos” and “droid” or you probably won't
find what you want. That should bring you to the right page
from which you can download and install the application.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49462016"></a>2. Connecting to TeleBT</h2></div></div></div><p>
Press the Android 'Menu' button or soft-key to see the
configuration options available. Select the 'Connect a device'
option and then the 'Scan for devices' entry at the bottom to
look for your TeleBT device. Select your device, and when it
asks for the code, enter '1234'.
</p><p>
Subsequent connections will not require you to enter that
code, and your 'paired' device will appear in the list without
scanning.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49464016"></a>3. Configuring AltosDroid</h2></div></div></div><p>
The only configuration option available for AltosDroid is
which frequency to listen on. Press the Android 'Menu' button
or soft-key and pick the 'Select radio frequency' entry. That
brings up a menu of pre-set radio frequencies; pick the one
which matches your altimeter.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49465472"></a>4. AltosDroid Flight Monitoring</h2></div></div></div><p>
AltosDroid is designed to mimic the AltosUI flight monitoring
display, providing separate tabs for each stage of your rocket
flight along with a tab containing a map of the local area
with icons marking the current location of the altimeter and
the Android device.
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49466784"></a>4.1. Pad</h3></div></div></div><p>
The 'Launch Pad' tab shows information used to decide when the
rocket is ready for flight. The first elements include red/green
indicators, if any of these is red, you'll want to evaluate
whether the rocket is ready to launch:
</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">Battery Voltage</span></dt><dd><p>
This indicates whether the Li-Po battery
powering the TeleMetrum has sufficient charge to last for
the duration of the flight. A value of more than
3.8V is required for a 'GO' status.
</p></dd><dt><span class="term">Apogee Igniter Voltage</span></dt><dd><p>
This indicates whether the apogee
igniter has continuity. If the igniter has a low
resistance, then the voltage measured here will be close
to the Li-Po battery voltage. A value greater than 3.2V is
required for a 'GO' status.
</p></dd><dt><span class="term">Main Igniter Voltage</span></dt><dd><p>
This indicates whether the main
igniter has continuity. If the igniter has a low
resistance, then the voltage measured here will be close
to the Li-Po battery voltage. A value greater than 3.2V is
required for a 'GO' status.
</p></dd><dt><span class="term">On-board Data Logging</span></dt><dd><p>
This indicates whether there is
space remaining on-board to store flight data for the
upcoming flight. If you've downloaded data, but failed
to erase flights, there may not be any space
left. TeleMetrum can store multiple flights, depending
on the configured maximum flight log size. TeleMini
stores only a single flight, so it will need to be
downloaded and erased after each flight to capture
data. This only affects on-board flight logging; the
altimeter will still transmit telemetry and fire
ejection charges at the proper times.
</p></dd><dt><span class="term">GPS Locked</span></dt><dd><p>
For a TeleMetrum or TeleMega device, this indicates whether the GPS receiver is
currently able to compute position information. GPS requires
at least 4 satellites to compute an accurate position.
</p></dd><dt><span class="term">GPS Ready</span></dt><dd><p>
For a TeleMetrum or TeleMega device, this indicates whether GPS has reported at least
10 consecutive positions without losing lock. This ensures
that the GPS receiver has reliable reception from the
satellites.
</p></dd></dl></div><p>
</p><p>
The Launchpad tab also shows the computed launch pad position
and altitude, averaging many reported positions to improve the
accuracy of the fix.
</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49480336"></a>5. Downloading Flight Logs</h2></div></div></div><p>
AltosDroid always saves every bit of telemetry data it
receives. To download that to a computer for use with AltosUI,
simply remove the SD card from your Android device, or connect
your device to your computer's USB port and browse the files
on that device. You will find '.telem' files in the TeleMetrum
directory that will work with AltosUI directly.
</p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp49482000"></a>Chapter 8. Using Altus Metrum Products</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp49482640">1. Being Legal</a></span></dt><dt><span class="section"><a href="#idp49484544">2. In the Rocket</a></span></dt><dt><span class="section"><a href="#idp49487072">3. On the Ground</a></span></dt><dt><span class="section"><a href="#idp49500464">4. Data Analysis</a></span></dt><dt><span class="section"><a href="#idp49503008">5. Future Plans</a></span></dt></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49482640"></a>1. Being Legal</h2></div></div></div><p>
First off, in the US, you need an <a class="ulink" href="http://www.altusmetrum.org/Radio/" target="_top">amateur radio license</a> or
other authorization to legally operate the radio transmitters that are part
of our products.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49484544"></a>2. In the Rocket</h2></div></div></div><p>
In the rocket itself, you just need a flight computer and
a single-cell, 3.7 volt nominal Li-Po rechargeable battery. An
850mAh battery weighs less than a 9V alkaline battery, and will
run a TeleMetrum, TeleMega or EasyMega for hours.
A 110mAh battery weighs less than a triple A battery and is a good
choice for use with TeleMini or EasyMini.
</p><p>
By default, we ship TeleMini, TeleMetrum and TeleMega flight computers with a simple wire antenna.
If your electronics bay or the air-frame it resides within is made
of carbon fiber, which is opaque to RF signals, you may prefer to
install an SMA connector so that you can run a coaxial cable to an
antenna mounted elsewhere in the rocket. However, note that the
GPS antenna is fixed on all current products, so you really want
to install the flight computer in a bay made of RF-transparent
materials if at all possible.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49487072"></a>3. On the Ground</h2></div></div></div><p>
To receive the data stream from the rocket, you need an antenna and short
feed-line connected to one of our <a class="ulink" href="http://www.altusmetrum.org/TeleDongle/" target="_top">TeleDongle</a> units. If possible, use an SMA to BNC
adapter instead of feedline between the antenna feedpoint and
TeleDongle, as this will give you the best performance. The
TeleDongle in turn plugs directly into the USB port on a notebook
computer. Because TeleDongle looks like a simple serial port, your computer
does not require special device drivers... just plug it in.
</p><p>
The GUI tool, AltosUI, is written in Java and runs across
Linux, Mac OS and Windows. There's also a suite of C tools
for Linux which can perform most of the same tasks.
</p><p>
Alternatively, a TeleBT attached with an SMA to BNC adapter at the
feed point of a hand-held yagi used in conjunction with an Android
device running AltosDroid makes an outstanding ground station.
</p><p>
After the flight, you can use the radio link to extract the more detailed data
logged in either TeleMetrum or TeleMini devices, or you can use a mini USB cable to plug into the
TeleMetrum board directly. Pulling out the data without having to open up
the rocket is pretty cool! A USB cable is also how you charge the Li-Po
battery, so you'll want one of those anyway... the same cable used by lots
of digital cameras and other modern electronic stuff will work fine.
</p><p>
If your rocket lands out of sight, you may enjoy having a hand-held
GPS receiver, so that you can put in a way-point for the last
reported rocket position before touch-down. This makes looking for
your rocket a lot like Geo-Caching... just go to the way-point and
look around starting from there. AltosDroid on an Android device
with GPS receiver works great for this, too!
</p><p>
You may also enjoy having a ham radio “HT” that covers the 70cm band... you
can use that with your antenna to direction-find the rocket on the ground
the same way you can use a Walston or Beeline tracker. This can be handy
if the rocket is hiding in sage brush or a tree, or if the last GPS position
doesn't get you close enough because the rocket dropped into a canyon, or
the wind is blowing it across a dry lake bed, or something like that... Keith
currently uses a Yaesu FT1D, Bdale has a Yaesu VX-7R, which
is a nicer radio in most ways but doesn't support APRS.
</p><p>
So, to recap, on the ground the hardware you'll need includes:
</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>
an antenna and feed-line or adapter
</p></li><li class="listitem"><p>
a TeleDongle
</p></li><li class="listitem"><p>
a notebook computer
</p></li><li class="listitem"><p>
optionally, a hand-held GPS receiver
</p></li><li class="listitem"><p>
optionally, an HT or receiver covering 435 MHz
</p></li></ol></div><p>
</p><p>
The best hand-held commercial directional antennas we've found for radio
direction finding rockets are from
<a class="ulink" href="http://www.arrowantennas.com/" target="_top">
Arrow Antennas.
</a>
The 440-3 and 440-5 are both good choices for finding a
TeleMetrum- or TeleMini- equipped rocket when used with a suitable
70cm HT. TeleDongle and an SMA to BNC adapter fit perfectly
between the driven element and reflector of Arrow antennas.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49500464"></a>4. Data Analysis</h2></div></div></div><p>
Our software makes it easy to log the data from each flight, both the
telemetry received during the flight itself, and the more
complete data log recorded in the flash memory on the altimeter
board. Once this data is on your computer, our post-flight tools make it
easy to quickly get to the numbers everyone wants, like apogee altitude,
max acceleration, and max velocity. You can also generate and view a
standard set of plots showing the altitude, acceleration, and
velocity of the rocket during flight. And you can even export a TeleMetrum data file
usable with Google Maps and Google Earth for visualizing the flight path
in two or three dimensions!
</p><p>
Our ultimate goal is to emit a set of files for each flight that can be
published as a web page per flight, or just viewed on your local disk with
a web browser.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49503008"></a>5. Future Plans</h2></div></div></div><p>
We have designed and prototyped several “companion boards” that
can attach to the companion connector on TeleMetrum,
TeleMega and EasyMega
flight computers to collect more data, provide more pyro channels,
and so forth. We do not yet know if or when any of these boards
will be produced in enough quantity to sell. If you have specific
interests for data collection or control of events in your rockets
beyond the capabilities of our existing productions, please let
us know!
</p><p>
Because all of our work is open, both the hardware designs and the
software, if you have some great idea for an addition to the current
Altus Metrum family, feel free to dive in and help! Or let us know
what you'd like to see that we aren't already working on, and maybe
we'll get excited about it too...
</p><p>
Watch our
<a class="ulink" href="http://altusmetrum.org/" target="_top">web site</a> for more news
and information as our family of products evolves!
</p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp49506848"></a>Chapter 9. Altimeter Installation Recommendations</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp49508304">1. Mounting the Altimeter</a></span></dt><dt><span class="section"><a href="#idp49513136">2. Dealing with the Antenna</a></span></dt><dt><span class="section"><a href="#idp49518704">3. Preserving GPS Reception</a></span></dt><dt><span class="section"><a href="#idp49523488">4. Radio Frequency Interference</a></span></dt><dt><span class="section"><a href="#idp49531056">5. The Barometric Sensor</a></span></dt><dt><span class="section"><a href="#idp49533856">6. Ground Testing</a></span></dt></dl></div><p>
Building high-power rockets that fly safely is hard enough. Mix
in some sophisticated electronics and a bunch of radio energy
and some creativity and/or compromise may be required. This chapter
contains some suggestions about how to install Altus Metrum
products into a rocket air-frame, including how to safely and
reliably mix a variety of electronics into the same air-frame.
</p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49508304"></a>1. Mounting the Altimeter</h2></div></div></div><p>
The first consideration is to ensure that the altimeter is
securely fastened to the air-frame. For most of our products, we
prefer nylon standoffs and nylon screws; they're good to at least 50G
and cannot cause any electrical issues on the board. Metal screws
and standoffs are fine, too, just be careful to avoid electrical
shorts! For TeleMini v1.0, we usually cut small pieces of 1/16 inch
balsa to fit
under the screw holes, and then take 2x56 nylon screws and
screw them through the TeleMini mounting holes, through the
balsa and into the underlying material.
</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>
Make sure accelerometer-equipped products like TeleMetrum,
TeleMega and EasyMega are aligned precisely along the axis of
acceleration so that the accelerometer can accurately
capture data during the flight.
</p></li><li class="listitem"><p>
Watch for any metal touching components on the
board. Shorting out connections on the bottom of the board
can cause the altimeter to fail during flight.
</p></li></ol></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49513136"></a>2. Dealing with the Antenna</h2></div></div></div><p>
The antenna supplied is just a piece of solid, insulated,
wire. If it gets damaged or broken, it can be easily
replaced. It should be kept straight and not cut; bending or
cutting it will change the resonant frequency and/or
impedance, making it a less efficient radiator and thus
reducing the range of the telemetry signal.
</p><p>
Keeping metal away from the antenna will provide better range
and a more even radiation pattern. In most rockets, it's not
entirely possible to isolate the antenna from metal
components; there are often bolts, all-thread and wires from other
electronics to contend with. Just be aware that the more stuff
like this around the antenna, the lower the range.
</p><p>
Make sure the antenna is not inside a tube made or covered
with conducting material. Carbon fiber is the most common
culprit here -- CF is a good conductor and will effectively
shield the antenna, dramatically reducing signal strength and
range. Metallic flake paint is another effective shielding
material which should be avoided around any antennas.
</p><p>
If the ebay is large enough, it can be convenient to simply
mount the altimeter at one end and stretch the antenna out
inside. Taping the antenna to the sled can keep it straight
under acceleration. If there are metal rods, keep the
antenna as far away as possible.
</p><p>
For a shorter ebay, it's quite practical to have the antenna
run through a bulkhead and into an adjacent bay. Drill a small
hole in the bulkhead, pass the antenna wire through it and
then seal it up with glue or clay. We've also used acrylic
tubing to create a cavity for the antenna wire. This works a
bit better in that the antenna is known to stay straight and
not get folded by recovery components in the bay. Angle the
tubing towards the side wall of the rocket and it ends up
consuming very little space.
</p><p>
If you need to place the UHF antenna at a distance from the
altimeter, you can replace the antenna with an edge-mounted
SMA connector, and then run 50Ω coax from the board to the
antenna. Building a remote antenna is beyond the scope of this
manual.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49518704"></a>3. Preserving GPS Reception</h2></div></div></div><p>
The GPS antenna and receiver used in TeleMetrum and TeleMega is
highly sensitive and normally have no trouble tracking enough
satellites to provide accurate position information for
recovering the rocket. However, there are many ways the GPS signal
can end up attenuated, negatively affecting GPS performance.
</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>
Conductive tubing or coatings. Carbon fiber and metal
tubing, or metallic paint will all dramatically attenuate the
GPS signal. We've never heard of anyone successfully
receiving GPS from inside these materials.
</p></li><li class="listitem"><p>
Metal components near the GPS patch antenna. These will
de-tune the patch antenna, changing the resonant frequency
away from the L1 carrier and reduce the effectiveness of the
antenna. You can place as much stuff as you like beneath the
antenna as that's covered with a ground plane. But, keep
wires and metal out from above the patch antenna.
</p></li></ol></div><p>
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49523488"></a>4. Radio Frequency Interference</h2></div></div></div><p>
Any altimeter will generate RFI; the digital circuits use
high-frequency clocks that spray radio interference across a
wide band. Altus Metrum altimeters generate intentional radio
signals as well, increasing the amount of RF energy around the board.
</p><p>
Rocketry altimeters also use precise sensors measuring air
pressure and acceleration. Tiny changes in voltage can cause
these sensor readings to vary by a huge amount. When the
sensors start mis-reporting data, the altimeter can either
fire the igniters at the wrong time, or not fire them at all.
</p><p>
Voltages are induced when radio frequency energy is
transmitted from one circuit to another. Here are things that
influence the induced voltage and current:
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Keep wires from different circuits apart. Moving circuits
further apart will reduce RFI.
</p></li><li class="listitem"><p>
Avoid parallel wires from different circuits. The longer two
wires run parallel to one another, the larger the amount of
transferred energy. Cross wires at right angles to reduce
RFI.
</p></li><li class="listitem"><p>
Twist wires from the same circuits. Two wires the same
distance from the transmitter will get the same amount of
induced energy which will then cancel out. Any time you have
a wire pair running together, twist the pair together to
even out distances and reduce RFI. For altimeters, this
includes battery leads, switch hookups and igniter
circuits.
</p></li><li class="listitem"><p>
Avoid resonant lengths. Know what frequencies are present
in the environment and avoid having wire lengths near a
natural resonant length. Altus Metrum products transmit on the
70cm amateur band, so you should avoid lengths that are a
simple ratio of that length; essentially any multiple of ¼
of the wavelength (17.5cm).
</p></li></ul></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49531056"></a>5. The Barometric Sensor</h2></div></div></div><p>
Altusmetrum altimeters measure altitude with a barometric
sensor, essentially measuring the amount of air above the
rocket to figure out how high it is. A large number of
measurements are taken as the altimeter initializes itself to
figure out the pad altitude. Subsequent measurements are then
used to compute the height above the pad.
</p><p>
To accurately measure atmospheric pressure, the ebay
containing the altimeter must be vented outside the
air-frame. The vent must be placed in a region of linear
airflow, have smooth edges, and away from areas of increasing or
decreasing pressure.
</p><p>
All barometric sensors are quite sensitive to chemical damage from
the products of APCP or BP combustion, so make sure the ebay is
carefully sealed from any compartment which contains ejection
charges or motors.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49533856"></a>6. Ground Testing</h2></div></div></div><p>
The most important aspect of any installation is careful
ground testing. Bringing an air-frame up to the LCO table which
hasn't been ground tested can lead to delays or ejection
charges firing on the pad, or, even worse, a recovery system
failure.
</p><p>
Do a 'full systems' test that includes wiring up all igniters
without any BP and turning on all of the electronics in flight
mode. This will catch any mistakes in wiring and any residual
RFI issues that might accidentally fire igniters at the wrong
time. Let the air-frame sit for several minutes, checking for
adequate telemetry signal strength and GPS lock. If any igniters
fire unexpectedly, find and resolve the issue before loading any
BP charges!
</p><p>
Ground test the ejection charges. Prepare the rocket for
flight, loading ejection charges and igniters. Completely
assemble the air-frame and then use the 'Fire Igniters'
interface through a TeleDongle to command each charge to
fire. Make sure the charge is sufficient to robustly separate
the air-frame and deploy the recovery system.
</p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp49537024"></a>Chapter 10. 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="#idp49541072">1.
Updating TeleMega, TeleMetrum v2, EasyMega or EasyMini Firmware
</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49550144">1.1. Recovering From Self-Flashing Failure</a></span></dt></dl></dd><dt><span class="section"><a href="#idp49568720">2. Pair Programming</a></span></dt><dt><span class="section"><a href="#idp49570160">3. Updating TeleMetrum v1.x Firmware</a></span></dt><dt><span class="section"><a href="#idp49583360">4. Updating TeleMini Firmware</a></span></dt><dt><span class="section"><a href="#idp49596912">5. Updating TeleDongle Firmware</a></span></dt></dl></div><p>
TeleMega, TeleMetrum v2, EasyMega and EasyMini are all programmed directly
over their USB connectors (self programming). TeleMetrum v1, TeleMini and
TeleDongle are all programmed by using another device as a
programmer (pair programming). It's important to recognize which
kind of devices you have before trying to reprogram them.
</p><p>
You may wish to begin by ensuring you have current firmware images.
These are distributed as part of the AltOS software bundle that
also includes the AltosUI 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><p>
If you need to update the firmware on a TeleDongle, we recommend
updating the altimeter first, before updating TeleDongle. However,
note that TeleDongle rarely need to be updated. Any firmware version
1.0.1 or later will work, version 1.2.1 may have improved receiver
performance slightly.
</p><p>
Self-programmable devices (TeleMega, TeleMetrum v2, EasyMega and EasyMini)
are reprogrammed by connecting them to your computer over USB
</p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49541072"></a>1.
Updating TeleMega, TeleMetrum v2, EasyMega or EasyMini 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 AltosUI, and select 'Flash Image' from the File 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 TeleMega-v1.0-1.3.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 class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49550144"></a>1.1. Recovering From Self-Flashing Failure</h3></div></div></div><p>
If the firmware loading fails, it can leave the device
unable to boot. Not to worry, you can force the device to
start the boot loader instead, which will let you try to
flash the device again.
</p><p>
On each device, connecting two pins from one of the exposed
connectors will force the boot loader to start, even if the
regular operating system has been corrupted in some way.
</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">TeleMega</span></dt><dd><p>
Connect pin 6 and pin 1 of the companion connector. Pin 1
can be identified by the square pad around it, and then
the pins could sequentially across the board. Be very
careful to <span class="emphasis"><em>not</em></span> short pin 8 to
anything as that is connected directly to the battery. Pin
7 carries 3.3V and the board will crash if that is
connected to pin 1, but shouldn't damage the board.
</p></dd><dt><span class="term">EasyMega</span></dt><dd><p>
Connect pin 6 and pin 1 of the companion connector. Pin 1
can be identified by the square pad around it, and then
the pins could sequentially across the board. Be very
careful to <span class="emphasis"><em>not</em></span> short pin 8 to
anything as that is connected directly to the battery. Pin
7 carries 3.3V and the board will crash if that is
connected to pin 1, but shouldn't damage the board.
</p></dd><dt><span class="term">TeleMetrum v2</span></dt><dd><p>
Connect pin 6 and pin 1 of the companion connector. Pin 1
can be identified by the square pad around it, and then
the pins could sequentially across the board. Be very
careful to <span class="emphasis"><em>not</em></span> short pin 8 to
anything as that is connected directly to the battery. Pin
7 carries 3.3V and the board will crash if that is
connected to pin 1, but shouldn't damage the board.
</p></dd><dt><span class="term">EasyMini</span></dt><dd><p>
Connect pin 6 and pin 1 of the debug connector, which is
the six holes next to the beeper. Pin 1 can be identified
by the square pad around it, and then the pins could
sequentially across the board, making Pin 6 the one on the
other end of the row.
</p></dd></dl></div><p>
Once you've located the right pins:
</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>
Turn the altimeter power off.
</p></li><li class="listitem"><p>
Connect a battery.
</p></li><li class="listitem"><p>
Connect the indicated terminals together with a short
piece of wire. Take care not to accidentally connect
anything else.
</p></li><li class="listitem"><p>
Connect USB
</p></li><li class="listitem"><p>
Turn the board power on.
</p></li><li class="listitem"><p>
The board should now be visible over USB as 'AltosFlash'
and be ready to receive firmware.
</p></li><li class="listitem"><p>
Once the board has been powered up, you can remove the
piece of wire.
</p></li></ol></div></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49568720"></a>2. Pair Programming</h2></div></div></div><p>
The big concept to understand is that you have to use a
TeleMega, TeleMetrum or TeleDongle as a programmer to update a
pair programmed device. Due to limited memory resources in the
cc1111, we don't support programming directly over USB for these
devices.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49570160"></a>3. Updating TeleMetrum v1.x Firmware</h2></div></div></div><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>
Find the 'programming cable' that you got as part of the starter
kit, that has a red 8-pin MicroMaTch connector on one end and a
red 4-pin MicroMaTch connector on the other end.
</p></li><li class="listitem"><p>
Take the 2 screws out of the TeleDongle case to get access
to the circuit board.
</p></li><li class="listitem"><p>
Plug the 8-pin end of the programming cable to the
matching connector on the TeleDongle, and the 4-pin end to the
matching connector on the TeleMetrum.
Note that each MicroMaTch connector has an alignment pin that
goes through a hole in the PC board when you have the cable
oriented correctly.
</p></li><li class="listitem"><p>
Attach a battery to the TeleMetrum board.
</p></li><li class="listitem"><p>
Plug the TeleDongle into your computer's USB port, and power
up the TeleMetrum.
</p></li><li class="listitem"><p>
Run AltosUI, and select 'Flash Image' from the File menu.
</p></li><li class="listitem"><p>
Pick the TeleDongle device from the list, identifying it as the
programming device.
</p></li><li class="listitem"><p>
Select the image you want put on the TeleMetrum, which should have a
name in the form telemetrum-v1.2-1.0.0.ihx. It should be visible
in the default directory, if not you may have to poke around
your system to find it.
</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 TeleMetrum with new firmware, showing a progress bar.
</p></li><li class="listitem"><p>
Confirm that the TeleMetrum board seems to have updated OK, which you
can do by plugging in to it over USB and using a terminal program
to connect to the board and issue the 'v' command to check
the version, etc.
</p></li><li class="listitem"><p>
If something goes wrong, give it another try.
</p></li></ol></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49583360"></a>4. Updating TeleMini Firmware</h2></div></div></div><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>
You'll need a special 'programming cable' to reprogram the
TeleMini. You can make your own using an 8-pin MicroMaTch
connector on one end and a set of four pins on the other.
</p></li><li class="listitem"><p>
Take the 2 screws out of the TeleDongle case to get access
to the circuit board.
</p></li><li class="listitem"><p>
Plug the 8-pin end of the programming cable to the matching
connector on the TeleDongle, and the 4-pins into the holes
in the TeleMini circuit board. Note that the MicroMaTch
connector has an alignment pin that goes through a hole in
the PC board when you have the cable oriented correctly, and
that pin 1 on the TeleMini board is marked with a square pad
while the other pins have round pads.
</p></li><li class="listitem"><p>
Attach a battery to the TeleMini board.
</p></li><li class="listitem"><p>
Plug the TeleDongle into your computer's USB port, and power
up the TeleMini
</p></li><li class="listitem"><p>
Run AltosUI, and select 'Flash Image' from the File menu.
</p></li><li class="listitem"><p>
Pick the TeleDongle device from the list, identifying it as the
programming device.
</p></li><li class="listitem"><p>
Select the image you want put on the TeleMini, which should have a
name in the form telemini-v1.0-1.0.0.ihx. It should be visible
in the default directory, if not you may have to poke around
your system to find it.
</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 TeleMini with new firmware, showing a progress bar.
</p></li><li class="listitem"><p>
Confirm that the TeleMini board seems to have updated OK, which you
can do by configuring it over the radio link through the TeleDongle, or
letting it come up in “flight” mode and listening for telemetry.
</p></li><li class="listitem"><p>
If something goes wrong, give it another try.
</p></li></ol></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49596912"></a>5. Updating TeleDongle Firmware</h2></div></div></div><p>
Updating TeleDongle's firmware is just like updating TeleMetrum or TeleMini
firmware, but you use either a TeleMetrum or another TeleDongle as the programmer.
</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>
Find the 'programming cable' that you got as part of the starter
kit, that has a red 8-pin MicroMaTch connector on one end and a
red 4-pin MicroMaTch connector on the other end.
</p></li><li class="listitem"><p>
Find the USB cable that you got as part of the starter kit, and
plug the “mini” end in to the mating connector on TeleMetrum or TeleDongle.
</p></li><li class="listitem"><p>
Take the 2 screws out of the TeleDongle case to get access
to the circuit board.
</p></li><li class="listitem"><p>
Plug the 8-pin end of the programming cable to the
matching connector on the programmer, and the 4-pin end to the
matching connector on the TeleDongle.
Note that each MicroMaTch connector has an alignment pin that
goes through a hole in the PC board when you have the cable
oriented correctly.
</p></li><li class="listitem"><p>
Attach a battery to the TeleMetrum board if you're using one.
</p></li><li class="listitem"><p>
Plug both the programmer and the TeleDongle into your computer's USB
ports, and power up the programmer.
</p></li><li class="listitem"><p>
Run AltosUI, and select 'Flash Image' from the File menu.
</p></li><li class="listitem"><p>
Pick the programmer device from the list, identifying it as the
programming device.
</p></li><li class="listitem"><p>
Select the image you want put on the TeleDongle, which should have a
name in the form teledongle-v0.2-1.0.0.ihx. It should be visible
in the default directory, if not you may have to poke around
your system to find it.
</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. The TeleDongle
serial number is on the “bottom” of the circuit board, and can
usually be read through the translucent blue plastic case without
needing to remove the board from the case.
</p></li><li class="listitem"><p>
Hit the 'OK' button and the software should proceed to flash
the TeleDongle with new firmware, showing a progress bar.
</p></li><li class="listitem"><p>
Confirm that the TeleDongle board seems to have updated OK, which you
can do by plugging in to it over USB and using a terminal program
to connect to the board and issue the 'v' command to check
the version, etc. Once you're happy, remove the programming cable
and put the cover back on the TeleDongle.
</p></li><li class="listitem"><p>
If something goes wrong, give it another try.
</p></li></ol></div><p>
Be careful removing the programming cable from the locking 8-pin
connector on TeleMetrum. You'll need a fingernail or perhaps a thin
screwdriver or knife blade to gently pry the locking ears out
slightly to extract the connector. We used a locking connector on
TeleMetrum to help ensure that the cabling to companion boards
used in a rocket don't ever come loose accidentally in flight.
</p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp49613536"></a>Chapter 11. Hardware Specifications</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp49614176">1.
TeleMega Specifications
</a></span></dt><dt><span class="section"><a href="#idp49625648">2.
EasyMega Specifications
</a></span></dt><dt><span class="section"><a href="#idp49635392">3.
TeleMetrum v2 Specifications
</a></span></dt><dt><span class="section"><a href="#idp49645952">4. TeleMetrum v1 Specifications</a></span></dt><dt><span class="section"><a href="#idp49656512">5.
TeleMini v2.0 Specifications
</a></span></dt><dt><span class="section"><a href="#idp49665344">6.
TeleMini v1.0 Specifications
</a></span></dt><dt><span class="section"><a href="#idp49674144">7.
EasyMini Specifications
</a></span></dt></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49614176"></a>1.
TeleMega Specifications
</h2></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Recording altimeter for model rocketry.
</p></li><li class="listitem"><p>
Supports dual deployment and four auxiliary pyro channels
(a total of 6 events).
</p></li><li class="listitem"><p>
70cm 40mW ham-band transceiver for telemetry down-link.
</p></li><li class="listitem"><p>
Barometric pressure sensor good to 100k feet MSL.
</p></li><li class="listitem"><p>
1-axis high-g accelerometer for motor characterization, capable of
+/- 102g.
</p></li><li class="listitem"><p>
9-axis IMU including integrated 3-axis accelerometer,
3-axis gyroscope and 3-axis magnetometer.
</p></li><li class="listitem"><p>
On-board, integrated uBlox Max 7 GPS receiver with 5Hz update rate capability.
</p></li><li class="listitem"><p>
On-board 8 Megabyte non-volatile memory for flight data storage.
</p></li><li class="listitem"><p>
USB interface for battery charging, configuration, and data recovery.
</p></li><li class="listitem"><p>
Fully integrated support for Li-Po rechargeable batteries.
</p></li><li class="listitem"><p>
Can use either main system Li-Po or optional separate pyro battery
to fire e-matches.
</p></li><li class="listitem"><p>
3.25 x 1.25 inch board designed to fit inside 38mm air-frame coupler tube.
</p></li></ul></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49625648"></a>2.
EasyMega Specifications
</h2></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Recording altimeter for model rocketry.
</p></li><li class="listitem"><p>
Supports dual deployment and four auxiliary pyro channels
(a total of 6 events).
</p></li><li class="listitem"><p>
Barometric pressure sensor good to 100k feet MSL.
</p></li><li class="listitem"><p>
1-axis high-g accelerometer for motor characterization, capable of
+/- 102g.
</p></li><li class="listitem"><p>
9-axis IMU including integrated 3-axis accelerometer,
3-axis gyroscope and 3-axis magnetometer.
</p></li><li class="listitem"><p>
On-board 8 Megabyte non-volatile memory for flight data storage.
</p></li><li class="listitem"><p>
USB interface for battery charging, configuration, and data recovery.
</p></li><li class="listitem"><p>
Fully integrated support for Li-Po rechargeable batteries.
</p></li><li class="listitem"><p>
Can use either main system Li-Po or optional separate pyro battery
to fire e-matches.
</p></li><li class="listitem"><p>
1.25 x 1.25 inch board designed to fit inside 38mm air-frame coupler tube.
</p></li></ul></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49635392"></a>3.
TeleMetrum v2 Specifications
</h2></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Recording altimeter for model rocketry.
</p></li><li class="listitem"><p>
Supports dual deployment (can fire 2 ejection charges).
</p></li><li class="listitem"><p>
70cm, 40mW ham-band transceiver for telemetry down-link.
</p></li><li class="listitem"><p>
Barometric pressure sensor good to 100k feet MSL.
</p></li><li class="listitem"><p>
1-axis high-g accelerometer for motor characterization, capable of
+/- 102g.
</p></li><li class="listitem"><p>
On-board, integrated uBlox Max 7 GPS receiver with 5Hz update rate capability.
</p></li><li class="listitem"><p>
On-board 8 Megabyte non-volatile memory for flight data storage.
</p></li><li class="listitem"><p>
USB interface for battery charging, configuration, and data recovery.
</p></li><li class="listitem"><p>
Fully integrated support for Li-Po rechargeable batteries.
</p></li><li class="listitem"><p>
Uses Li-Po to fire e-matches, can be modified to support
optional separate pyro battery if needed.
</p></li><li class="listitem"><p>
2.75 x 1 inch board designed to fit inside 29mm air-frame coupler tube.
</p></li></ul></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49645952"></a>4. TeleMetrum v1 Specifications</h2></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Recording altimeter for model rocketry.
</p></li><li class="listitem"><p>
Supports dual deployment (can fire 2 ejection charges).
</p></li><li class="listitem"><p>
70cm, 10mW ham-band transceiver for telemetry down-link.
</p></li><li class="listitem"><p>
Barometric pressure sensor good to 45k feet MSL.
</p></li><li class="listitem"><p>
1-axis high-g accelerometer for motor characterization, capable of
+/- 50g using default part.
</p></li><li class="listitem"><p>
On-board, integrated GPS receiver with 5Hz update rate capability.
</p></li><li class="listitem"><p>
On-board 1 megabyte non-volatile memory for flight data storage.
</p></li><li class="listitem"><p>
USB interface for battery charging, configuration, and data recovery.
</p></li><li class="listitem"><p>
Fully integrated support for Li-Po rechargeable batteries.
</p></li><li class="listitem"><p>
Uses Li-Po to fire e-matches, can be modified to support
optional separate pyro battery if needed.
</p></li><li class="listitem"><p>
2.75 x 1 inch board designed to fit inside 29mm air-frame coupler tube.
</p></li></ul></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49656512"></a>5.
TeleMini v2.0 Specifications
</h2></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Recording altimeter for model rocketry.
</p></li><li class="listitem"><p>
Supports dual deployment (can fire 2 ejection charges).
</p></li><li class="listitem"><p>
70cm, 10mW ham-band transceiver for telemetry down-link.
</p></li><li class="listitem"><p>
Barometric pressure sensor good to 100k feet MSL.
</p></li><li class="listitem"><p>
On-board 1 megabyte non-volatile memory for flight data storage.
</p></li><li class="listitem"><p>
USB interface for configuration, and data recovery.
</p></li><li class="listitem"><p>
Support for Li-Po rechargeable batteries (using an
external charger), or any 3.7-15V external battery.
</p></li><li class="listitem"><p>
Uses Li-Po to fire e-matches, can be modified to support
optional separate pyro battery if needed.
</p></li><li class="listitem"><p>
1.5 x .8 inch board designed to fit inside 24mm air-frame coupler tube.
</p></li></ul></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49665344"></a>6.
TeleMini v1.0 Specifications
</h2></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Recording altimeter for model rocketry.
</p></li><li class="listitem"><p>
Supports dual deployment (can fire 2 ejection charges).
</p></li><li class="listitem"><p>
70cm, 10mW ham-band transceiver for telemetry down-link.
</p></li><li class="listitem"><p>
Barometric pressure sensor good to 45k feet MSL.
</p></li><li class="listitem"><p>
On-board 5 kilobyte non-volatile memory for flight data storage.
</p></li><li class="listitem"><p>
RF interface for configuration, and data recovery.
</p></li><li class="listitem"><p>
Support for Li-Po rechargeable batteries, using an external charger.
</p></li><li class="listitem"><p>
Uses Li-Po to fire e-matches, can be modified to support
optional separate pyro battery if needed.
</p></li><li class="listitem"><p>
1.5 x .5 inch board designed to fit inside 18mm air-frame coupler tube.
</p></li></ul></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49674144"></a>7.
EasyMini Specifications
</h2></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Recording altimeter for model rocketry.
</p></li><li class="listitem"><p>
Supports dual deployment (can fire 2 ejection charges).
</p></li><li class="listitem"><p>
Barometric pressure sensor good to 100k feet MSL.
</p></li><li class="listitem"><p>
On-board 1 megabyte non-volatile memory for flight data storage.
</p></li><li class="listitem"><p>
USB interface for configuration, and data recovery.
</p></li><li class="listitem"><p>
Support for Li-Po rechargeable batteries (using an
external charger), or any 3.7-15V external battery.
</p></li><li class="listitem"><p>
Uses Li-Po to fire e-matches, can be modified to support
optional separate pyro battery if needed.
</p></li><li class="listitem"><p>
1.5 x .8 inch board designed to fit inside 24mm air-frame coupler tube.
</p></li></ul></div></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp49682256"></a>Chapter 12. FAQ</h1></div></div></div><p>
<span class="emphasis"><em>TeleMetrum seems to shut off when disconnected from the
computer.</em></span>
Make sure the battery is adequately charged. Remember the
unit will pull more power than the USB port can deliver before the
GPS enters “locked” mode. The battery charges best when TeleMetrum
is turned off.
</p><p>
<span class="emphasis"><em>It's impossible to stop the TeleDongle when it's in “p” mode, I have
to unplug the USB cable? </em></span>
Make sure you have tried to “escape out” of
this mode. If this doesn't work the reboot procedure for the
TeleDongle *is* to simply unplug it. 'cu' however will retain it's
outgoing buffer IF your “escape out” ('~~') does not work.
At this point using either 'ao-view' (or possibly
'cutemon') instead of 'cu' will 'clear' the issue and allow renewed
communication.
</p><p>
<span class="emphasis"><em>The amber LED (on the TeleMetrum) lights up when both
battery and USB are connected. Does this mean it's charging?
</em></span>
Yes, the yellow LED indicates the charging at the 'regular' rate.
If the led is out but the unit is still plugged into a USB port,
then the battery is being charged at a 'trickle' rate.
</p><p>
<span class="emphasis"><em>There are no “dit-dah-dah-dit” sound or lights like the manual
mentions?</em></span>
That's the “pad” mode. Weak batteries might be the problem.
It is also possible that the flight computer is horizontal and the
output
is instead a “dit-dit” meaning 'idle'. For TeleMini, it's possible that
it received a command packet which would have left it in “pad” mode.
</p><p>
<span class="emphasis"><em>How do I save flight data?</em></span>
Live telemetry is written to file(s) whenever AltosUI is connected
to the TeleDongle. The file area defaults to ~/TeleMetrum
but is easily changed using the menus in AltosUI. The files that
are written end in '.telem'. The after-flight
data-dumped files will end in .eeprom and represent continuous data
unlike the .telem files that are subject to losses
along the RF data path.
See the above instructions on what and how to save the eeprom stored
data after physically retrieving your altimeter. Make sure to save
the on-board data after each flight; while the TeleMetrum can store
multiple flights, you never know when you'll lose the altimeter...
</p></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a name="idp49691104"></a>Appendix A. Notes for Older Software</h1></div></div></div><p>
<span class="emphasis"><em>
Before AltosUI was written, using Altus Metrum devices required
some finesse with the Linux command line. There was a limited
GUI tool, ao-view, which provided functionality similar to the
Monitor Flight window in AltosUI, but everything else was a
fairly 80's experience. This appendix includes documentation for
using that software.
</em></span>
</p><p>
Both TeleMetrum and TeleDongle can be directly communicated
with using USB ports. The first thing you should try after getting
both units plugged into to your computer's USB port(s) is to run
'ao-list' from a terminal-window to see what port-device-name each
device has been assigned by the operating system.
You will need this information to access the devices via their
respective on-board firmware and data using other command line
programs in the AltOS software suite.
</p><p>
TeleMini can be communicated with through a TeleDongle device
over the radio link. When first booted, TeleMini listens for a
TeleDongle device and if it receives a packet, it goes into
'idle' mode. Otherwise, it goes into 'pad' mode and waits to be
launched. The easiest way to get it talking is to start the
communication link on the TeleDongle and the power up the
TeleMini board.
</p><p>
To access the device's firmware for configuration you need a terminal
program such as you would use to talk to a modem. The software
authors prefer using the program 'cu' which comes from the UUCP package
on most Unix-like systems such as Linux. An example command line for
cu might be 'cu -l /dev/ttyACM0', substituting the correct number
indicated from running the
ao-list program. Another reasonable terminal program for Linux is
'cutecom'. The default 'escape'
character used by CU (i.e. the character you use to
issue commands to cu itself instead of sending the command as input
to the connected device) is a '~'. You will need this for use in
only two different ways during normal operations. First is to exit
the program by sending a '~.' which is called a 'escape-disconnect'
and allows you to close-out from 'cu'. The
second use will be outlined later.
</p><p>
All of the Altus Metrum devices share the concept of a two level
command set in their firmware.
The first layer has several single letter commands. Once
you are using 'cu' (or 'cutecom') sending (typing) a '?'
returns a full list of these
commands. The second level are configuration sub-commands accessed
using the 'c' command, for
instance typing 'c?' will give you this second level of commands
(all of which require the
letter 'c' to access). Please note that most configuration options
are stored only in Flash memory; TeleDongle doesn't provide any storage
for these options and so they'll all be lost when you unplug it.
</p><p>
Try setting these configuration ('c' or second level menu) values. A good
place to start is by setting your call sign. By default, the boards
use 'N0CALL' which is cute, but not exactly legal!
Spend a few minutes getting comfortable with the units, their
firmware, and 'cu' (or possibly 'cutecom').
For instance, try to send
(type) a 'c r 2' and verify the channel change by sending a 'c s'.
Verify you can connect and disconnect from the units while in your
terminal program by sending the escape-disconnect mentioned above.
</p><p>
To set the radio frequency, use the 'c R' command to specify the
radio transceiver configuration parameter. This parameter is computed
using the desired frequency, 'F', the radio calibration parameter, 'C' (showed by the 'c s' command) and
the standard calibration reference frequency, 'S', (normally 434.550MHz):
</p><pre class="programlisting">
R = F / S * C
</pre><p>
Round the result to the nearest integer value.
As with all 'c' sub-commands, follow this with a 'c w' to write the
change to the parameter block in the on-board flash on
your altimeter board if you want the change to stay in place across reboots.
</p><p>
To set the apogee delay, use the 'c d' command.
As with all 'c' sub-commands, follow this with a 'c w' to write the
change to the parameter block in the on-board DataFlash chip.
</p><p>
To set the main deployment altitude, use the 'c m' command.
As with all 'c' sub-commands, follow this with a 'c w' to write the
change to the parameter block in the on-board DataFlash chip.
</p><p>
To calibrate the radio frequency, connect the UHF antenna port to a
frequency counter, set the board to 434.550MHz, and use the 'C'
command to generate a CW carrier. Wait for the transmitter temperature
to stabilize and the frequency to settle down.
Then, divide 434.550 MHz by the
measured frequency and multiply by the current radio cal value show
in the 'c s' command. For an unprogrammed board, the default value
is 1186611 for cc1111 based products and 7119667 for cc1120
based products. Take the resulting integer and program it using the 'c f'
command. Testing with the 'C' command again should show a carrier
within a few tens of Hertz of the intended frequency.
As with all 'c' sub-commands, follow this with a 'c w' to write the
change to the configuration memory.
</p><p>
Note that the 'reboot' command, which is very useful on the altimeters,
will likely just cause problems with the dongle. The *correct* way
to reset the dongle is just to unplug and re-plug it.
</p><p>
A fun thing to do at the launch site and something you can do while
learning how to use these units is to play with the radio link access
between an altimeter and the TeleDongle. Be aware that you *must* create
some physical separation between the devices, otherwise the link will
not function due to signal overload in the receivers in each device.
</p><p>
Now might be a good time to take a break and read the rest of this
manual, particularly about the two “modes” that the altimeters
can be placed in. TeleMetrum uses the position of the device when booting
up will determine whether the unit is in “pad” or “idle” mode. TeleMini
enters “idle” mode when it receives a command packet within the first 5 seconds
of being powered up, otherwise it enters “pad” mode.
</p><p>
You can access an altimeter in idle mode from the TeleDongle's USB
connection using the radio link
by issuing a 'p' command to the TeleDongle. Practice connecting and
disconnecting ('~~' while using 'cu') from the altimeter. If
you cannot escape out of the “p” command, (by using a '~~' when in
CU) then it is likely that your kernel has issues. Try a newer version.
</p><p>
Using this radio link allows you to configure the altimeter, test
fire e-matches and igniters from the flight line, check pyro-match
continuity and so forth. You can leave the unit turned on while it
is in 'idle mode' and then place the
rocket vertically on the launch pad, walk away and then issue a
reboot command. The altimeter will reboot and start sending data
having changed to the “pad” mode. If the TeleDongle is not receiving
this data, you can disconnect 'cu' from the TeleDongle using the
procedures mentioned above and THEN connect to the TeleDongle from
inside 'ao-view'. If this doesn't work, disconnect from the
TeleDongle, unplug it, and try again after plugging it back in.
</p><p>
In order to reduce the chance of accidental firing of pyrotechnic
charges, the command to fire a charge is intentionally somewhat
difficult to type, and the built-in help is slightly cryptic to
prevent accidental echoing of characters from the help text back at
the board from firing a charge. The command to fire the apogee
drogue charge is 'i DoIt drogue' and the command to fire the main
charge is 'i DoIt main'.
</p><p>
On TeleMetrum, the GPS will eventually find enough satellites, lock in on them,
and 'ao-view' will both auditorily announce and visually indicate
that GPS is ready.
Now you can launch knowing that you have a good data path and
good satellite lock for flight data and recovery. Remember
you MUST tell ao-view to connect to the TeleDongle explicitly in
order for ao-view to be able to receive data.
</p><p>
The altimeters provide RDF (radio direction finding) tones on
the pad, during descent and after landing. These can be used to
locate the rocket using a directional antenna; the signal
strength providing an indication of the direction from receiver to rocket.
</p><p>
TeleMetrum also provides GPS tracking data, which can further simplify
locating the rocket once it has landed. (The last good GPS data
received before touch-down will be on the data screen of 'ao-view'.)
</p><p>
Once you have recovered the rocket you can download the eeprom
contents using either 'ao-dumplog' (or possibly 'ao-eeprom'), over
either a USB cable or over the radio link using TeleDongle.
And by following the man page for 'ao-postflight' you can create
various data output reports, graphs, and even KML data to see the
flight trajectory in Google-earth. (Moving the viewing angle making
sure to connect the yellow lines while in Google-earth is the proper
technique.)
</p><p>
As for ao-view.... some things are in the menu but don't do anything
very useful. The developers have stopped working on ao-view to focus
on a new, cross-platform ground station program. So ao-view may or
may not be updated in the future. Mostly you just use
the Log and Device menus. It has a wonderful display of the incoming
flight data and I am sure you will enjoy what it has to say to you
once you enable the voice output!
</p></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a name="idp49713504"></a>Appendix B. Drill Templates</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp49714672">1. TeleMega template</a></span></dt><dt><span class="section"><a href="#idp49731360">2. EasyMega template</a></span></dt><dt><span class="section"><a href="#idp49735744">3. TeleMetrum template</a></span></dt><dt><span class="section"><a href="#idp49740128">4. TeleMini v2/EasyMini template</a></span></dt><dt><span class="section"><a href="#idp49744528">5. TeleMini v1 template</a></span></dt></dl></div><p>
These images, when printed, provide precise templates for the
mounting holes in Altus Metrum flight computers
</p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49714672"></a>1. TeleMega template</h2></div></div></div><p>
TeleMega has overall dimensions of 1.250 x 3.250 inches, and
the mounting holes are sized for use with 4-40 or M3 screws.
</p><div class="informalfigure"><div class="mediaobject" align="center"><a name="TeleMegaTemplate"></a><object type="image/svg+xml" data="telemega.svg" align="middle"></object></div></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49731360"></a>2. EasyMega template</h2></div></div></div><p>
EasyMega has overall dimensions of 1.250 x 2.250 inches, and
the mounting holes are sized for use with 4-40 or M3 screws.
</p><div class="informalfigure"><div class="mediaobject" align="center"><a name="EasyMegaTemplate"></a><object type="image/svg+xml" data="easymega.svg" align="middle"></object></div></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49735744"></a>3. TeleMetrum template</h2></div></div></div><p>
TeleMetrum has overall dimensions of 1.000 x 2.750 inches, and the
mounting holes are sized for use with 4-40 or M3 screws.
</p><div class="informalfigure"><div class="mediaobject" align="center"><a name="TeleMetrumTemplate"></a><object type="image/svg+xml" data="telemetrum.svg" align="middle"></object></div></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49740128"></a>4. TeleMini v2/EasyMini template</h2></div></div></div><p>
TeleMini v2 and EasyMini have overall dimensions of 0.800 x 1.500 inches, and the
mounting holes are sized for use with 4-40 or M3 screws.
</p><div class="informalfigure"><div class="mediaobject" align="center"><a name="MiniTemplate"></a><object type="image/svg+xml" data="easymini.svg" align="middle"></object></div></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49744528"></a>5. TeleMini v1 template</h2></div></div></div><p>
TeleMini has overall dimensions of 0.500 x 1.500 inches, and the
mounting holes are sized for use with 2-56 or M2 screws.
</p><div class="informalfigure"><div class="mediaobject" align="center"><a name="TeleMiniTemplate"></a><object type="image/svg+xml" data="telemini.svg" align="middle"></object></div></div></div></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a name="idp49749040"></a>Appendix C. Calibration</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp49750592">1. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp49755136">2. TeleMetrum, TeleMega and EasyMega Accelerometers</a></span></dt></dl></div><p>
There are only two calibrations required for TeleMetrum and
TeleMega, and only one for EasyMega, TeleDongle, TeleMini and EasyMini.
All boards are shipped from the factory pre-calibrated, but
the procedures are documented here in case they are ever
needed. Re-calibration is not supported by AltosUI, you must
connect to the board with a serial terminal program and
interact directly with the on-board command interpreter to
effect calibration.
</p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49750592"></a>1. Radio Frequency</h2></div></div></div><p>
The radio frequency is synthesized from a clock based on the
crystal on the board. The actual frequency of this oscillator
must be measured to generate a calibration constant. While our
GFSK modulation
bandwidth is wide enough to allow boards to communicate even when
their oscillators are not on exactly the same frequency, performance
is best when they are closely matched.
Radio frequency calibration requires a calibrated frequency counter.
Fortunately, once set, the variation in frequency due to aging and
temperature changes is small enough that re-calibration by customers
should generally not be required.
</p><p>
To calibrate the radio frequency, connect the UHF antenna
port to a frequency counter, set the board to 434.550MHz,
and use the 'C' command in the on-board command interpreter
to generate a CW carrier. For USB-enabled boards, this is
best done over USB. For TeleMini v1, note that the only way
to escape the 'C' command is via power cycle since the board
will no longer be listening for commands once it starts
generating a CW carrier.
</p><p>
Wait for the transmitter temperature to stabilize and the frequency
to settle down. Then, divide 434.550 MHz by the
measured frequency and multiply by the current radio cal value show
in the 'c s' command. For an unprogrammed board, the default value
is 1186611. Take the resulting integer and program it using the 'c f'
command. Testing with the 'C' command again should show a carrier
within a few tens of Hertz of the intended frequency.
As with all 'c' sub-commands, follow this with a 'c w' to write the
change to the parameter block in the on-board storage chip.
</p><p>
Note that any time you re-do the radio frequency calibration, the
radio frequency is reset to the default 434.550 Mhz. If you want
to use another frequency, you will have to set that again after
calibration is completed.
</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49755136"></a>2. TeleMetrum, TeleMega and EasyMega Accelerometers</h2></div></div></div><p>
While barometric sensors are factory-calibrated,
accelerometers are not, and so each must be calibrated once
installed in a flight computer. Explicitly calibrating the
accelerometers also allows us to load any compatible device.
We perform a two-point calibration using gravity.
</p><p>
To calibrate the acceleration sensor, use the 'c a 0' command. You
will be prompted to orient the board vertically with the UHF antenna
up and press a key, then to orient the board vertically with the
UHF antenna down and press a key. Note that the accuracy of this
calibration depends primarily on how perfectly vertical and still
the board is held during the cal process. As with all 'c'
sub-commands, follow this with a 'c w' to write the
change to the parameter block in the on-board DataFlash chip.
</p><p>
The +1g and -1g calibration points are included in each telemetry
frame and are part of the header stored in onboard flash to be
downloaded after flight. We always store and return raw ADC
samples for each sensor... so nothing is permanently “lost” or
“damaged” if the calibration is poor.
</p><p>
In the unlikely event an accel cal goes badly, it is possible
that TeleMetrum, TeleMega or EasyMega may always come up in 'pad mode'
and as such not be listening to either the USB or radio link.
If that happens, there is a special hook in the firmware to
force the board back in to 'idle mode' so you can re-do the
cal. To use this hook, you just need to ground the SPI clock
pin at power-on. This pin is available as pin 2 on the 8-pin
companion connector, and pin 1 is ground. So either
carefully install a fine-gauge wire jumper between the two
pins closest to the index hole end of the 8-pin connector, or
plug in the programming cable to the 8-pin connector and use
a small screwdriver or similar to short the two pins closest
to the index post on the 4-pin end of the programming cable,
and power up the board. It should come up in 'idle mode'
(two beeps), allowing a re-cal.
</p></div></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a name="idp49760816"></a>Appendix D. Release Notes</h1></div></div></div><div class="simplesect"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49761456"></a>Version 1.4.1</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="idp49763056"></a>Version 1.5</h2></div></div></div><p>
Version 1.5 is a major release. It includes support for our new
EasyMega 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 EasyMega boards.
</p></li><li class="listitem"><p>
Make the APRS SSID be configurable. This lets you track
different rockets on the same receiver without getting
things mixed up.
</p></li><li class="listitem"><p>
Report extra pyro channel continuity state on EasyMega and
TeleMega via the beeper. This lets you easily verify flight
readiness on these boards after powering up the electronics
on the rail.
</p></li><li class="listitem"><p>
Add lower telemetry data rates (2400 and 9600 bps) to
increase telemetry radio range. This reduces the amount of
data received as well as increasing battery consumption in
the transmitter.
</p></li><li class="listitem"><p>
Change TeleGPS to have only a single log, and append new
data to it rather than using seperate per-flight logs. This
avoids accidentally filling up log storage by turning
TeleGPS on/off several times.
</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>
Increase the maximum range for altitude values from +/-32767m
to +/-2147483647m, allowing the flight computers to function
correctly above the 32km level.
</p></li><li class="listitem"><p>
Continuously test pyro firing conditions during delay stage,
inhibiting the pyro channel if the test fails. This prevents
firing pyro charges where the conditions were good before
the delay, but become bad before the delay expires.
</p></li><li class="listitem"><p>
Allow negative numbers in pyro configuration values. This
lets you specify things like descending speed or
deceleration.
</p></li></ul></div><p>
</p><p>
AltosUI and TeleGPS New Features
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Support telemetry baud rate selection. Adds menus to
the flight monitoring and configuration for baud rate
selection.
</p></li><li class="listitem"><p>
Support APRS SSID configuration.
</p></li><li class="listitem"><p>
Integrate with file managers. This provides icons for all of
our file types and associates our application with the files
so that using a file manager to open a AltOS data file
results in launching our application.
</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>
Make the 'Graph' button on the landed tab work again.
</p></li><li class="listitem"><p>
Make tests for Java on Windows a bit smarter, and also
provide the user with the option to skip installing Java for
cases where we just can't figure out what version is installed.
</p></li></ul></div><p>
</p></div><div class="simplesect"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49764656"></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 class="simplesect"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49766160"></a>Version 1.3.2</h2></div></div></div><p>
Version 1.3.2 is a minor release. It includes small bug fixes for
the TeleMega flight software and AltosUI ground station
</p><p>
AltOS Firmware Changes
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
On TeleMega, limit number of logged GPS status information
to 12 satellites. That's all there is room for in the log
structure.
</p></li><li class="listitem"><p>
Improve APRS behavior. Remembers last known GPS position and
keeps sending that if we lose GPS lock. Marks
locked/unlocked by sending L/U in the APRS comment field
along with the number of sats in view and voltages.
</p></li></ul></div><p>
</p><p>
AltosUI changes
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
If the TeleMega flight firmware reports that it has logged
information about more than 12 satellites, don't believe it
as the log only holds 12 satellite records.
</p></li><li class="listitem"><p>
Track the maximum height as computed from GPS altitude
data and report that in the flight summary data.
</p></li><li class="listitem"><p>
Use letters (A, B, C, D) for alternate pyro channel names
instead of numbers (0, 1, 2, 3) in the Fire Igniter dialog.
</p></li></ul></div><p>
</p></div><div class="simplesect"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49767664"></a>Version 1.3.1</h2></div></div></div><p>
Version 1.3.1 is a minor release. It improves support for TeleMega,
TeleMetrum v2.0, TeleMini v2.0 and EasyMini.
</p><p>
AltOS Firmware Changes
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Improve sensor boot code. If sensors fail to self-test, the
device will still boot up and check for pad/idle modes. If
in idle mode, the device will warn the user with a distinct
beep, if in Pad mode, the unit will operate as best it
can. Also, the Z-axis accelerometer now uses the factory
calibration values instead of re-calibrating on the pad each
time. This avoids accidental boost detect when moving the
device around while in Pad mode.
</p></li><li class="listitem"><p>
Fix antenna-down mode accelerometer configuration. Antenna
down mode wasn't working because the accelerometer
calibration values were getting re-computed incorrectly in
inverted mode.
</p></li><li class="listitem"><p>
Improved APRS mode. Now uses compressed position format for
smaller data size, improved precision and to include
altitude data as well as latitude and longitude. Also added
battery and pyro voltage reports in the APRS comment field
so you can confirm that the unit is ready for launch.
</p></li></ul></div><p>
</p><p>
AltosUI changes
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Display additional TeleMega sensor values in real
units. Make all of these values available for
plotting. Display TeleMega orientation value in the Ascent
and Table tabs.
</p></li><li class="listitem"><p>
Support additional TeleMega pyro channels in the Fire
Igniter dialog. This lets you do remote testing of all of
the channels, rather than just Apogee and Main.
</p></li><li class="listitem"><p>
Limit data rate when downloading satellite images from
Google to make sure we stay within their limits so that all
of the map tiles download successfully.
</p></li></ul></div><p>
</p></div><div class="simplesect"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49769168"></a>Version 1.3</h2></div></div></div><p>
Version 1.3 is a major release. It adds support for TeleMega,
TeleMetrum v2.0, TeleMini v2.0 and EasyMini.
</p><p>
AltOS Firmware Changes
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Add STM32L processor support. This includes enhancements to
the scheduler to support products with many threads.
</p></li><li class="listitem"><p>
Add NXP LPC11U14 processor support.
</p></li><li class="listitem"><p>
Support additional pyro channels. These are configurable
through the UI to handle air starts, staging, additional
recovery events and external devices such as cameras.
</p></li><li class="listitem"><p>
Add 3-axis gyro support for orientation tracking. This
integrates the gyros to compute the angle from vertical during
flight, allowing the additional pyro events to be controlled
by this value.
</p></li><li class="listitem"><p>
Many more device drivers, including u-Blox Max 7Q GPS,
Freescale MMA6555 digital single-axis accelerometer,
Invensense MPU6000 3-axis accelerometer + 3 axis gyro,
Honeywell HMC5883 3-axis magnetic sensor and the TI CC1120 and
CC115L digital FM transceivers
</p></li></ul></div><p>
</p><p>
AltosUI changes
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Support TeleMega, TeleMetrum v2.0, TeleMini v2.0 and EasyMini telemetry and log formats.
</p></li><li class="listitem"><p>
Use preferred units for main deployment height configuration,
instead of always doing configuration in meters.
</p></li></ul></div><p>
</p><p>
MicroPeak UI changes
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Add 'Download' button to menu bar.
</p></li><li class="listitem"><p>
Save the last log directory and offer that as the default for new downloads
</p></li></ul></div><p>
</p></div><div class="simplesect"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49770672"></a>Version 1.2.1</h2></div></div></div><p>
Version 1.2.1 is a minor release. It adds support for TeleBT and
the AltosDroid application, provides several new features in
AltosUI and fixes some bugs in the AltOS firmware.
</p><p>
AltOS Firmware Changes
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Add support for TeleBT
</p></li><li class="listitem"><p>
In TeleMini recovery mode (when booted with the outer two
debug pins connected together), the radio parameters are also
set back to defaults (434.550MHz, N0CALL, factory radio cal).
</p></li><li class="listitem"><p>
Add support for reflashing the SkyTraq GPS chips. This
requires special host-side code which currently only exists
for Linux.
</p></li><li class="listitem"><p>
Correct Kalman filter model error covariance matrix. The
values used previously assumed continuous measurements instead
of discrete measurements.
</p></li><li class="listitem"><p>
Fix some bugs in the USB driver for TeleMetrum and TeleDongle
that affected Windows users.
</p></li><li class="listitem"><p>
Adjusted the automatic gain control parameters that affect
receive performance for TeleDongle. Field tests indicate that this
may improve receive performance somewhat.
</p></li></ul></div><p>
</p><p>
AltosUI Changes
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Handle missing GPS lock in 'Descent' tab. Previously, if the
GPS position of the pad was unknown, an exception would be
raised, breaking the Descent tab contents.
</p></li><li class="listitem"><p>
Improve the graph, adding tool-tips to show values near the
cursor and making the displayed set of values configurable,
adding all of the flight data as options while leaving the
default settings alone so that the graph starts by showing
height, speed and acceleration.
</p></li><li class="listitem"><p>
Make the initial position of the AltosUI top level window
configurable. Along with this change, the other windows will
pop up at 'sensible' places now, instead of on top of one
another.
</p></li><li class="listitem"><p>
Add callsign to Monitor idle window and connecting
dialogs. This makes it clear which callsign is being used so
that the operator will be aware that it must match the flight
computer value or no communication will work.
</p></li><li class="listitem"><p>
When downloading flight data, display the block number so that
the user has some sense of progress. Unfortunately, we don't
know how many blocks will need to be downloaded, but at least
it isn't just sitting there doing nothing for a long time.
</p></li><li class="listitem"><p>
Add GPS data and a map to the graph window. This lets you see
a complete summary of the flight without needing to 'replay'
the whole thing.
</p></li></ul></div><p>
</p></div><div class="simplesect"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49772176"></a>Version 1.2</h2></div></div></div><p>
Version 1.2 is a major release. It adds support for MicroPeak and
the MicroPeak USB adapter.
</p><p>
AltOS Firmware Changes
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Add MicroPeak support. This includes support for the ATtiny85
processor and adaptations to the core code to allow for
devices too small to run the multi-tasking scheduler.
</p></li></ul></div><p>
</p><p>
MicroPeak UI changes
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Added this new application
</p></li></ul></div><p>
</p><p>
Distribution Changes
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Distribute Mac OS X packages in disk image ('.dmg') format to
greatly simplify installation.
</p></li><li class="listitem"><p>
Provide version numbers for the shared Java libraries to
ensure that upgrades work properly, and to allow for multiple
Altus Metrum software packages to be installed in the same
directory at the same time.
</p></li></ul></div><p>
</p></div><div class="simplesect"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49773680"></a>Version 1.1.1</h2></div></div></div><p>
Version 1.1.1 is a bug-fix release. It fixes a couple of bugs in
AltosUI and one firmware bug that affects TeleMetrum version 1.0
boards. Thanks to Bob Brown for help diagnosing the Google Earth
file export issue, and for suggesting the addition of the Ground
Distance value in the Descent tab.
</p><p>
AltOS Firmware Changes
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
TeleMetrum v1.0 boards use the AT45DB081D flash memory part to
store flight data, which is different from later TeleMetrum
boards. The AltOS v1.1 driver for this chip couldn't erase
memory, leaving it impossible to delete flight data or update
configuration values. This bug doesn't affect newer TeleMetrum
boards, and it doesn't affect the safety of rockets flying
version 1.1 firmware.
</p></li></ul></div><p>
</p><p>
AltosUI Changes
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Creating a Google Earth file (KML) from on-board flight data
(EEPROM) would generate an empty file. The code responsible
for reading the EEPROM file wasn't ever setting the GPS valid
bits, and so the KML export code thought there was no GPS data
in the file.
</p></li><li class="listitem"><p>
The “Landed” tab was displaying all values in metric units,
even when AltosUI was configured to display imperial
units. Somehow I just missed this tab when doing the units stuff.
</p></li><li class="listitem"><p>
The “Descent” tab displays the range to the rocket, which is a
combination of the over-the-ground distance to the rockets
current latitude/longitude and the height of the rocket. As
such, it's useful for knowing how far away the rocket is, but
difficult to use when estimating where the rocket might
eventually land. A new “Ground Distance” field has been added
which displays the distance to a spot right underneath the
rocket.
</p></li><li class="listitem"><p>
Sensor data wasn't being displayed for TeleMini flight
computers in Monitor Idle mode, including things like battery
voltage. The code that picked which kinds of data to fetch
from the flight computer was missing a check for TeleMini when
deciding whether to fetch the analog sensor data.
</p></li></ul></div><p>
</p></div><div class="simplesect"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49775184"></a>Version 1.1</h2></div></div></div><p>
Version 1.1 is a minor release. It provides a few new features in AltosUI
and the AltOS firmware and fixes bugs.
</p><p>
AltOS Firmware Changes
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Add apogee-lockout value. Overrides the apogee detection logic to
prevent incorrect apogee charge firing.
</p></li><li class="listitem"><p>
Fix a bug where the data reported in telemetry packets was
from 320ms ago.
</p></li><li class="listitem"><p>
Force the radio frequency to 434.550MHz when the debug clock
pin is connected to ground at boot time. This provides a way
to talk to a TeleMini which is configured to some unknown frequency.
</p></li><li class="listitem"><p>
Provide RSSI values for Monitor Idle mode. This makes it easy to check radio
range without needing to go to flight mode.
</p></li><li class="listitem"><p>
Fix a bug which caused the old received telemetry packets to
be retransmitted over the USB link when the radio was turned
off and back on.
</p></li></ul></div><p>
</p><p>
AltosUI Changes
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Fix a bug that caused GPS ready to happen too quickly. The
software was using every telemetry packet to signal new GPS
data, which caused GPS ready to be signalled after 10 packets
instead of 10 GPS updates.
</p></li><li class="listitem"><p>
Fix Google Earth data export to work with recent versions. The
google earth file loading code got a lot pickier, requiring
some minor white space changes in the export code.
</p></li><li class="listitem"><p>
Make the look-n-feel configurable, providing a choice from
the available options.
</p></li><li class="listitem"><p>
Add an 'Age' element to mark how long since a telemetry packet
has been received. Useful to quickly gauge whether
communications with the rocket are still active.
</p></li><li class="listitem"><p>
Add 'Configure Ground Station' dialog to set the radio
frequency used by a particular TeleDongle without having to go
through the flight monitor UI.
</p></li><li class="listitem"><p>
Add configuration for the new apogee-lockout value. A menu provides a list of
reasonable values, or the value can be set by hand.
</p></li><li class="listitem"><p>
Changed how flight data are downloaded. Now there's an initial
dialog asking which flights to download, and after that
finishes, a second dialog comes up asking which flights to delete.
</p></li><li class="listitem"><p>
Re-compute time spent in each state for the flight graph; this
figures out the actual boost and landing times instead of
using the conservative values provide by the flight
electronics. This improves the accuracy of the boost
acceleration and main descent rate computations.
</p></li><li class="listitem"><p>
Make AltosUI run on Mac OS Lion. The default Java heap space
was dramatically reduced for this release causing much of the
UI to fail randomly. This most often affected the satellite
mapping download and displays.
</p></li><li class="listitem"><p>
Change how data are displayed in the 'table' tab of the flight
monitoring window. This eliminates entries duplicated from the
header and adds both current altitude and pad altitude, which
are useful in 'Monitor Idle' mode.
</p></li><li class="listitem"><p>
Add Imperial units mode to present data in feet instead of
meters.
</p></li></ul></div><p>
</p></div><div class="simplesect"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49776688"></a>Version 1.0.1</h2></div></div></div><p>
Version 1.0.1 is a major release, adding support for the TeleMini
device and lots of new AltosUI features
</p><p>
AltOS Firmware Changes
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Add TeleMini v1.0 support. Firmware images for TeleMini are
included in AltOS releases.
</p></li><li class="listitem"><p>
Change telemetry to be encoded in multiple 32-byte packets. This
enables support for TeleMini and other devices without requiring
further updates to the TeleDongle firmware.
</p></li><li class="listitem"><p>
Support operation of TeleMetrum with the antenna pointing
aft. Previous firmware versions required the antenna to be
pointing upwards, now there is a configuration option allowing
the antenna to point aft, to aid installation in some airframes.
</p></li><li class="listitem"><p>
Ability to disable telemetry. For airframes where an antenna
just isn't possible, or where radio transmissions might cause
trouble with other electronics, there's a configuration option
to disable all telemetry. Note that the board will still
enable the radio link in idle mode.
</p></li><li class="listitem"><p>
Arbitrary frequency selection. The radios in Altus Metrum
devices can be programmed to a wide range of frequencies, so
instead of limiting devices to 10 pre-selected 'channels', the
new firmware allows the user to choose any frequency in the
70cm band. Note that the RF matching circuit on the boards is
tuned for around 435MHz, so frequencies far from that may
reduce the available range.
</p></li><li class="listitem"><p>
Kalman-filter based flight-tracking. The model based sensor
fusion approach of a Kalman filter means that AltOS now
computes apogee much more accurately than before, generally
within a fraction of a second. In addition, this approach
allows the baro-only TeleMini device to correctly identify
Mach transitions, avoiding the error-prone selection of a Mach
delay.
</p></li></ul></div><p>
</p><p>
AltosUI Changes
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Wait for altimeter when using packet mode. Instead of quicly
timing out when trying to initialize a packet mode
configuration connection, AltosUI now waits indefinitely for
the remote device to appear, providing a cancel button should
the user get bored. This is necessary as the TeleMini can only
be placed in "Idle" mode if AltosUI is polling it.
</p></li><li class="listitem"><p>
Add main/apogee voltage graphs to the data plot. This provides
a visual indication if the igniters fail before being fired.
</p></li><li class="listitem"><p>
Scan for altimeter devices by watching the defined telemetry
frequencies. This avoids the problem of remembering what
frequency a device was configured to use, which is especially
important with TeleMini which does not include a USB connection.
</p></li><li class="listitem"><p>
Monitor altimeter state in "Idle" mode. This provides much of
the information presented in the "Pad" dialog from the Monitor
Flight command, monitoring the igniters, battery and GPS
status withing requiring the flight computer to be armed and
ready for flight.
</p></li><li class="listitem"><p>
Pre-load map images from home. For those launch sites which
don't provide free Wi-Fi, this allows you to download the
necessary satellite images given the location of the launch
site. A list of known launch sites is maintained at
altusmetrum.org which AltosUI downloads to populate a menu; if
you've got a launch site not on that list, please send the
name of it, latitude and longitude along with a link to the
web site of the controlling club to the altusmetrum mailing list.
</p></li><li class="listitem"><p>
Flight statistics are now displayed in the Graph data
window. These include max height/speed/accel, average descent
rates and a few other bits of information. The Graph Data
window can now be reached from the 'Landed' tab in the Monitor
Flight window so you can immediately see the results of a
flight.
</p></li></ul></div><p>
</p></div><div class="simplesect"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49778192"></a>Version 0.9.2</h2></div></div></div><p>
Version 0.9.2 is an AltosUI bug-fix release, with no firmware changes.
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Fix plotting problems due to missing file in the Mac OS install image.
</p></li><li class="listitem"><p>
Always read whole eeprom blocks, mark empty records invalid, display parsing errors to user.
</p></li><li class="listitem"><p>
Add software version to Configure AltosUI dialog
</p></li></ul></div></div><div class="simplesect"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49779696"></a>Version 0.9</h2></div></div></div><p>
Version 0.9 adds a few new firmware features and accompanying
AltosUI changes, along with new hardware support.
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Support for TeleMetrum v1.1 hardware. Sources for the flash
memory part used in v1.0 dried up, so v1.1 uses a different part
which required a new driver and support for explicit flight log
erasing.
</p></li><li class="listitem"><p>
Multiple flight log support. This stores more than one flight
log in the on-board flash memory. It also requires the user to
explicitly erase flights so that you won't lose flight logs just
because you fly the same board twice in one day.
</p></li><li class="listitem"><p>
Telemetry support for devices with serial number >=
256. Previous versions used a telemetry packet format that
provided only 8 bits for the device serial number. This change
requires that both ends of the telemetry link be running the 0.9
firmware or they will not communicate.
</p></li></ul></div></div><div class="simplesect"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49781200"></a>Version 0.8</h2></div></div></div><p>
Version 0.8 offers a major upgrade in the AltosUI
interface. Significant new features include:
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Post-flight graphing tool. This lets you explore the behaviour
of your rocket after flight with a scroll-able and zoom-able
chart showing the altitude, speed and acceleration of the
airframe along with events recorded by the flight computer. You
can export graphs to PNG files, or print them directly.
</p></li><li class="listitem"><p>
Real-time moving map which overlays the in-progress flight on
satellite imagery fetched from Google Maps. This lets you see in
pictures where your rocket has landed, allowing you to plan
recovery activities more accurately.
</p></li><li class="listitem"><p>
Wireless recovery system testing. Prep your rocket for flight
and test fire the deployment charges to make sure things work as
expected. All without threading wires through holes in your
airframe.
</p></li><li class="listitem"><p>
Optimized flight status displays. Each flight state now has it's
own custom 'tab' in the flight monitoring window so you can
focus on the most important details. Pre-flight, the system
shows a set of red/green status indicators for battery voltage,
apogee/main igniter continutity and GPS reception. Wait until
they're all green and your rocket is ready for flight. There are
also tabs for ascent, descent and landing along with the
original tabular view of the data.
</p></li><li class="listitem"><p>
Monitor multiple flights simultaneously. If you have more than
one TeleDongle, you can monitor a flight with each one on the
same computer.
</p></li><li class="listitem"><p>
Automatic flight monitoring at startup. Plug TeleDongle into the
machine before starting AltosUI and it will automatically
connect to it and prepare to monitor a flight.
</p></li><li class="listitem"><p>
Exports Google Earth flight tracks. Using the Keyhole Markup
Language (.kml) file format, this provides a 3D view of your
rocket flight through the Google Earth program.
</p></li></ul></div></div><div class="simplesect"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49782704"></a>Version 0.7.1</h2></div></div></div><p>
Version 0.7.1 is the first release containing our new cross-platform Java-based user interface. AltosUI can:
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Receive and log telemetry from a connected TeleDongle
device. All data received is saved to log files named with the
current date and the connected rocket serial and flight
numbers. There is no mode in which telemetry data will not be
saved.
</p></li><li class="listitem"><p>
Download logged data from TeleMetrum devices, either through a
direct USB connection or over the air through a TeleDongle
device.
</p></li><li class="listitem"><p>
Configure a TeleMetrum device, setting the radio channel,
callsign, apogee delay and main deploy height. This can be done
through either a USB connection or over a radio link via a
TeleDongle device.
</p></li><li class="listitem"><p>
Replay a flight in real-time. This takes a saved telemetry log
or eeprom download and replays it through the user interface so
you can relive your favorite rocket flights.
</p></li><li class="listitem"><p>
Reprogram Altus Metrum devices. Using an Altus Metrum device
connected via USB, another Altus Metrum device can be
reprogrammed using the supplied programming cable between the
two devices.
</p></li><li class="listitem"><p>
Export Flight data to a comma-separated-values file. This takes
either telemetry or on-board flight data and generates data
suitable for use in external applications. All data is exported
using standard units so that no device-specific knowledge is
needed to handle the data.
</p></li><li class="listitem"><p>
Speak to you during the flight. Instead of spending the flight
hunched over your laptop looking at the screen, enjoy the view
while the computer tells you what’s going on up there. During
ascent, you hear the current flight state and altitude
information. During descent, you get azimuth, elevation and
range information to try and help you find your rocket in the
air. Once on the ground, the direction and distance are
reported.
</p></li></ul></div></div></div></div></body></html>
|
