diff options
88 files changed, 7684 insertions, 6384 deletions
diff --git a/AltOS/doc/altos.pdf b/AltOS/doc/altos.pdf Binary files differindex 0fabebe..84073e1 100644 --- a/AltOS/doc/altos.pdf +++ b/AltOS/doc/altos.pdf diff --git a/AltOS/doc/altusmetrum-oneline.svg b/AltOS/doc/altusmetrum-oneline.svg new file mode 100644 index 0000000..0ed7b6c --- /dev/null +++ b/AltOS/doc/altusmetrum-oneline.svg @@ -0,0 +1,354 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<!-- Created with Inkscape (http://www.inkscape.org/) --> + +<svg + xmlns:dc="http://purl.org/dc/elements/1.1/" + xmlns:cc="http://creativecommons.org/ns#" + xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" + xmlns:svg="http://www.w3.org/2000/svg" + xmlns="http://www.w3.org/2000/svg" + xmlns:xlink="http://www.w3.org/1999/xlink" + xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd" + xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape" + id="svg2" + width="444" + height="98" + version="1.0" + sodipodi:version="0.32" + inkscape:version="0.91 r13725" + sodipodi:docname="altusmetrum-oneline.svg" + inkscape:output_extension="org.inkscape.output.svg.inkscape" + inkscape:export-filename="/home/keithp/src/cc1111/altus-logo/bottom.png" + inkscape:export-xdpi="119.89881" + inkscape:export-ydpi="119.89881"> + <metadata + id="metadata14"> + <rdf:RDF> + <cc:Work + rdf:about=""> + <dc:format>image/svg+xml</dc:format> + <dc:type + rdf:resource="http://purl.org/dc/dcmitype/StillImage" /> + <dc:title></dc:title> + </cc:Work> + </rdf:RDF> + </metadata> + <defs + id="defs12"> + <linearGradient + id="linearGradient4171"> + <stop + id="stop4173" + offset="0" + style="stop-color:#da7000;stop-opacity:1;" /> + <stop + style="stop-color:#a63852;stop-opacity:1;" + offset="0.24528302" + id="stop4175" /> + <stop + id="stop4177" + offset="1" + style="stop-color:#7200a4;stop-opacity:1;" /> + </linearGradient> + <linearGradient + id="linearGradient3165"> + <stop + style="stop-color:#000000;stop-opacity:1;" + offset="0" + id="stop3167" /> + <stop + style="stop-color:#000000;stop-opacity:0;" + offset="1" + id="stop3169" /> + </linearGradient> + <linearGradient + id="linearGradient3177"> + <stop + style="stop-color:#da7000;stop-opacity:1;" + offset="0" + id="stop3179" /> + <stop + id="stop3447" + offset="0.24528302" + style="stop-color:#a63852;stop-opacity:1;" /> + <stop + style="stop-color:#7200a4;stop-opacity:1;" + offset="1" + id="stop3181" /> + </linearGradient> + <linearGradient + id="linearGradient3169"> + <stop + style="stop-color:#ff8a00;stop-opacity:1;" + offset="0" + id="stop3171" /> + <stop + id="stop3445" + offset="0.71698111" + style="stop-color:#c24573;stop-opacity:0.98039216;" /> + <stop + style="stop-color:#8500e7;stop-opacity:0.96078432;" + offset="1" + id="stop3173" /> + </linearGradient> + <inkscape:perspective + sodipodi:type="inkscape:persp3d" + inkscape:vp_x="0 : 121 : 1" + inkscape:vp_y="0 : 1000 : 0" + inkscape:vp_z="191 : 121 : 1" + inkscape:persp3d-origin="95.5 : 80.666667 : 1" + id="perspective16" /> + <radialGradient + inkscape:collect="always" + xlink:href="#linearGradient3169" + id="radialGradient3175" + cx="951.68713" + cy="2305.2668" + fx="951.68713" + fy="2305.2668" + r="951.68701" + gradientTransform="matrix(1,0,0,1.2664529,0,-321.14689)" + gradientUnits="userSpaceOnUse" /> + <linearGradient + inkscape:collect="always" + xlink:href="#linearGradient3177" + id="linearGradient3183" + x1="170.6575" + y1="110.17125" + x2="614.24878" + y2="110.17125" + gradientUnits="userSpaceOnUse" /> + <radialGradient + inkscape:collect="always" + xlink:href="#linearGradient3165" + id="radialGradient3171" + cx="951.68713" + cy="1205.2668" + fx="951.68713" + fy="1205.2668" + r="951.68701" + gradientTransform="matrix(1,0,0,1.2664529,0,-321.14689)" + gradientUnits="userSpaceOnUse" /> + <linearGradient + inkscape:collect="always" + xlink:href="#linearGradient3177" + id="linearGradient3781" + x1="193.16029" + y1="121.50799" + x2="589.83154" + y2="121.50799" + gradientUnits="userSpaceOnUse" /> + <radialGradient + inkscape:collect="always" + xlink:href="#linearGradient3169" + id="radialGradient3008" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1,0,0,1.2664529,0,-321.14689)" + cx="951.68713" + cy="2305.2668" + fx="951.68713" + fy="2305.2668" + r="951.68701" /> + <radialGradient + inkscape:collect="always" + xlink:href="#linearGradient3165" + id="radialGradient3010" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1,0,0,1.2664529,0,-321.14689)" + cx="951.68713" + cy="1205.2668" + fx="951.68713" + fy="1205.2668" + r="951.68701" /> + <radialGradient + inkscape:collect="always" + xlink:href="#linearGradient3169" + id="radialGradient3012" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1,0,0,1.2664529,0,-321.14689)" + cx="951.68713" + cy="2305.2668" + fx="951.68713" + fy="2305.2668" + r="951.68701" /> + <radialGradient + inkscape:collect="always" + xlink:href="#linearGradient3165" + id="radialGradient3014" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1,0,0,1.2664529,0,-321.14689)" + cx="951.68713" + cy="1205.2668" + fx="951.68713" + fy="1205.2668" + r="951.68701" /> + <radialGradient + inkscape:collect="always" + xlink:href="#linearGradient3169" + id="radialGradient3016" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1,0,0,1.2664529,0,-321.14689)" + cx="951.68713" + cy="2305.2668" + fx="951.68713" + fy="2305.2668" + r="951.68701" /> + <radialGradient + inkscape:collect="always" + xlink:href="#linearGradient3165" + id="radialGradient3018" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1,0,0,1.2664529,0,-321.14689)" + cx="951.68713" + cy="1205.2668" + fx="951.68713" + fy="1205.2668" + r="951.68701" /> + <linearGradient + inkscape:collect="always" + xlink:href="#linearGradient4171" + id="linearGradient4229" + x1="47.299" + y1="31.709364" + x2="129.17451" + y2="31.709364" + gradientUnits="userSpaceOnUse" /> + <linearGradient + inkscape:collect="always" + xlink:href="#linearGradient4171" + id="linearGradient4176" + gradientUnits="userSpaceOnUse" + x1="47.299" + y1="31.709364" + x2="129.17451" + y2="31.709364" /> + <linearGradient + inkscape:collect="always" + xlink:href="#linearGradient4171" + id="linearGradient4178" + gradientUnits="userSpaceOnUse" + x1="47.299" + y1="31.709364" + x2="129.17451" + y2="31.709364" /> + <linearGradient + inkscape:collect="always" + xlink:href="#linearGradient4171" + id="linearGradient4180" + gradientUnits="userSpaceOnUse" + x1="47.299" + y1="31.709364" + x2="129.17451" + y2="31.709364" /> + </defs> + <sodipodi:namedview + inkscape:cy="-41.854765" + inkscape:cx="115.51489" + inkscape:zoom="1.7366335" + inkscape:window-height="1404" + inkscape:window-width="1799" + inkscape:pageshadow="2" + inkscape:pageopacity="0.0" + guidetolerance="10.0" + gridtolerance="10.0" + objecttolerance="10.0" + borderopacity="1.0" + bordercolor="#666666" + pagecolor="#ffffff" + id="base" + showgrid="false" + inkscape:window-x="343" + inkscape:window-y="171" + inkscape:current-layer="svg2" + inkscape:window-maximized="0" + fit-margin-top="0" + fit-margin-left="0" + fit-margin-right="0" + fit-margin-bottom="0" + units="px" /> + <g + id="g4218" + style="fill:url(#linearGradient4229);fill-opacity:1" + transform="translate(20.153936,16.360317)"> + <path + d="m 59.744607,35.548307 c 6.934865,0 15.789201,4.210453 17.399081,13.126708 0.619184,3.343596 1.362205,5.139231 4.458127,5.139231 2.167146,0 3.715107,-1.733717 3.715107,-4.953475 0,-1.919472 -1.671798,-13.064791 -9.783114,-28.358645 -3.529351,-6.687191 -5.634578,-9.845031 -9.225847,-9.845031 -4.334291,0 -6.315681,3.15784 -9.845032,9.845031 -8.111315,15.293854 -9.163928,26.439173 -9.163928,28.358645 0,2.972085 0.681102,4.953475 4.024698,4.953475 2.229064,0 3.529351,-1.362206 3.777025,-3.653188 0.433429,-4.148535 1.362205,-10.092705 3.034003,-14.612751 l 1.60988,0 z m 0.247673,-6.191844 c 1.60988,-3.838943 3.653188,-7.55405 6.129926,-11.269156 3.034003,4.829638 5.386904,10.030787 7.244457,15.355773 l -0.123837,0.123837 C 69.156209,30.223321 63.831224,29.356463 60.79722,29.356463 l -0.80494,0 z" + style="font-style:normal;font-variant:normal;font-weight:bold;font-stretch:normal;font-size:61.91843796px;line-height:100%;font-family:'ITC Benguiat Gothic Std';-inkscape-font-specification:'ITC Benguiat Gothic Std Bold';text-align:start;letter-spacing:0px;word-spacing:0px;writing-mode:lr-tb;text-anchor:start;fill:url(#linearGradient4176);fill-opacity:1;stroke:none" + id="path3362" + inkscape:connector-curvature="0" /> + <path + d="m 99.370471,13.62918 c 0,-2.229064 -1.17645,-4.0246989 -3.715106,-4.0246989 -2.538656,0 -3.715106,1.7956349 -3.715106,4.0246989 l 0,36.160367 c 0,2.229064 1.17645,4.024699 3.715106,4.024699 2.538656,0 3.715106,-1.795635 3.715106,-4.024699 l 0,-36.160367 z" + style="font-style:normal;font-variant:normal;font-weight:bold;font-stretch:normal;font-size:61.91843796px;line-height:100%;font-family:'ITC Benguiat Gothic Std';-inkscape-font-specification:'ITC Benguiat Gothic Std Bold';text-align:start;letter-spacing:0px;word-spacing:0px;writing-mode:lr-tb;text-anchor:start;fill:url(#linearGradient4178);fill-opacity:1;stroke:none" + id="path3364" + inkscape:connector-curvature="0" /> + <path + d="m 123.29227,28.861115 c 1.98139,0 3.59127,-1.052613 3.59127,-3.343595 0,-2.290983 -1.60988,-3.343596 -3.59127,-3.343596 l -5.44882,0 0,-5.263067 c 0,-2.229064 -1.17645,-4.024699 -3.71511,-4.024699 -2.53865,0 -3.7151,1.795635 -3.7151,4.024699 l 0,5.263067 -2.10523,0 c -2.04331,0 -3.65319,1.052613 -3.65319,3.343596 0,2.290982 1.60988,3.343595 3.65319,3.343595 l 2.10523,0 0,13.374383 c 0,11.392992 4.33429,11.392992 13.74589,11.392992 3.3436,0 5.01539,-1.114531 5.01539,-3.529351 0,-2.414819 -1.67179,-3.52935 -3.77702,-3.52935 l -3.96278,0 c -2.84825,0 -3.59127,-1.733717 -3.59127,-5.448823 l 0,-12.259851 5.44882,0 z" + style="font-style:normal;font-variant:normal;font-weight:bold;font-stretch:normal;font-size:61.91843796px;line-height:100%;font-family:'ITC Benguiat Gothic Std';-inkscape-font-specification:'ITC Benguiat Gothic Std Bold';text-align:start;letter-spacing:0px;word-spacing:0px;writing-mode:lr-tb;text-anchor:start;fill:url(#linearGradient4180);fill-opacity:1;stroke:none" + id="path3366" + inkscape:connector-curvature="0" /> + </g> + <g + id="g4231" + style="fill:#78079a;fill-opacity:1" + transform="translate(20.153936,16.360317)"> + <path + d="m 158.87506,25.827112 c 0,-2.229064 -1.17645,-4.024699 -3.71511,-4.024699 -2.53865,0 -3.7151,1.795635 -3.7151,4.024699 l 0,12.817116 c 0,5.758415 -2.72442,8.668582 -6.93487,8.668582 -3.3436,0 -5.01539,-2.105227 -5.01539,-6.439518 l 0,-15.04618 c 0,-2.229064 -1.17645,-4.024699 -3.71511,-4.024699 -2.53866,0 -3.71511,1.795635 -3.71511,4.024699 l 0,17.02757 c 0,6.315681 4.3343,11.145319 11.02149,11.145319 3.40551,0 5.88225,-0.990695 8.35899,-3.343596 0,1.547961 1.17645,3.343596 3.7151,3.343596 2.53866,0 3.71511,-1.795635 3.71511,-4.024698 l 0,-24.148191 z" + style="font-style:normal;font-variant:normal;font-weight:bold;font-stretch:normal;font-size:61.91843796px;line-height:100%;font-family:'ITC Benguiat Gothic Std';-inkscape-font-specification:'ITC Benguiat Gothic Std Bold';text-align:start;letter-spacing:0px;word-spacing:0px;writing-mode:lr-tb;text-anchor:start;fill:#78079a;fill-opacity:1;stroke:none" + id="path3368" + inkscape:connector-curvature="0" /> + <path + d="m 179.78124,53.62849 c 6.99678,0 12.19793,-3.15784 12.19793,-10.649971 0,-13.06479 -19.50431,-8.297071 -19.50431,-12.569443 0,-1.486042 1.54796,-1.547961 2.66249,-1.547961 l 10.83573,0 c 1.98139,0 3.59127,-1.052613 3.59127,-3.343595 0,-2.290983 -1.60988,-3.343596 -3.59127,-3.343596 l -10.4023,0 c -6.81103,0 -10.52613,2.538656 -10.52613,8.173234 0,12.940953 19.50431,6.191844 19.50431,12.569443 0,3.343595 -2.3529,4.024698 -5.32499,4.024698 l -11.14532,0 c -2.04331,0 -3.65319,1.052614 -3.65319,3.343596 0,2.290982 1.60988,3.343595 3.65319,3.343595 l 11.70259,0 z" + style="font-style:normal;font-variant:normal;font-weight:bold;font-stretch:normal;font-size:61.91843796px;line-height:100%;font-family:'ITC Benguiat Gothic Std';-inkscape-font-specification:'ITC Benguiat Gothic Std Bold';text-align:start;letter-spacing:0px;word-spacing:0px;writing-mode:lr-tb;text-anchor:start;fill:#78079a;fill-opacity:1;stroke:none" + id="path3370" + inkscape:connector-curvature="0" /> + <path + d="m 216.06544,26.446296 c -2.53866,-3.095922 -4.0247,-7.058702 -6.12993,-12.197932 -0.9907,-2.414819 -2.47674,-3.405514 -4.95348,-3.405514 -4.76771,0 -4.95347,3.653188 -5.94417,9.597358 -1.17645,6.996783 -2.22906,19.132797 -2.22906,26.191499 0,4.334291 0.30959,7.182539 3.83894,7.182539 3.46744,0 3.96278,-2.352901 3.96278,-5.263067 l 0,-9.783114 c 0,-5.386904 0.61919,-10.959563 1.48605,-16.656059 l 0.12383,0 c 0.9907,3.15784 5.51074,13.498219 9.84504,13.498219 4.33429,0 8.85433,-10.340379 9.84503,-13.498219 l 0.12383,0 c 0.86686,5.696496 1.48605,11.269155 1.48605,16.656059 l 0,9.783114 c 0,2.910166 0.49534,5.263067 3.96278,5.263067 3.52935,0 3.83894,-2.848248 3.83894,-7.182539 0,-7.058702 -1.05261,-19.194716 -2.22906,-26.191499 -0.9907,-5.94417 -1.17645,-9.597358 -5.94417,-9.597358 -2.47674,0 -3.96278,0.990695 -4.95348,3.405514 -2.10523,5.13923 -3.59127,9.10201 -6.12992,12.197932 z" + style="font-style:normal;font-variant:normal;font-weight:bold;font-stretch:normal;font-size:61.91843796px;line-height:100%;font-family:'ITC Benguiat Gothic Std';-inkscape-font-specification:'ITC Benguiat Gothic Std Bold';text-align:start;letter-spacing:0px;word-spacing:0px;writing-mode:lr-tb;text-anchor:start;fill:#78079a;fill-opacity:1;stroke:none" + id="path3372" + inkscape:connector-curvature="0" /> + <path + d="m 266.81728,53.62849 c 1.98139,0 3.59127,-1.052613 3.59127,-3.343595 0,-2.290982 -1.60988,-3.343596 -3.59127,-3.343596 l -7.98748,0 c -5.20115,0 -9.59735,-1.547961 -10.0927,-7.368294 l 18.94704,0 c 2.60057,0 3.034,-1.547961 3.034,-3.653188 0,-7.244457 -4.27237,-14.117404 -14.61275,-14.117404 -9.47352,0 -15.54153,7.244458 -15.54153,16.532223 0,9.225848 6.19185,15.293854 17.21333,15.293854 l 9.04009,0 z M 249.23245,34.000346 c 0.86685,-3.715107 3.96278,-6.006089 6.87294,-6.006089 2.91017,0 6.00609,2.290982 6.81103,6.006089 l -13.68397,0 z" + style="font-style:normal;font-variant:normal;font-weight:bold;font-stretch:normal;font-size:61.91843796px;line-height:100%;font-family:'ITC Benguiat Gothic Std';-inkscape-font-specification:'ITC Benguiat Gothic Std Bold';text-align:start;letter-spacing:0px;word-spacing:0px;writing-mode:lr-tb;text-anchor:start;fill:#78079a;fill-opacity:1;stroke:none" + id="path3374" + inkscape:connector-curvature="0" /> + <path + d="m 291.99582,28.861115 c 1.98139,0 3.59127,-1.052613 3.59127,-3.343595 0,-2.290983 -1.60988,-3.343596 -3.59127,-3.343596 l -5.44882,0 0,-5.263067 c 0,-2.229064 -1.17645,-4.024699 -3.7151,-4.024699 -2.53866,0 -3.71511,1.795635 -3.71511,4.024699 l 0,5.263067 -2.10523,0 c -2.04331,0 -3.65319,1.052613 -3.65319,3.343596 0,2.290982 1.60988,3.343595 3.65319,3.343595 l 2.10523,0 0,13.374383 c 0,11.392992 4.33429,11.392992 13.74589,11.392992 3.3436,0 5.0154,-1.114531 5.0154,-3.529351 0,-2.414819 -1.6718,-3.52935 -3.77703,-3.52935 l -3.96278,0 c -2.84825,0 -3.59127,-1.733717 -3.59127,-5.448823 l 0,-12.259851 5.44882,0 z" + style="font-style:normal;font-variant:normal;font-weight:bold;font-stretch:normal;font-size:61.91843796px;line-height:100%;font-family:'ITC Benguiat Gothic Std';-inkscape-font-specification:'ITC Benguiat Gothic Std Bold';text-align:start;letter-spacing:0px;word-spacing:0px;writing-mode:lr-tb;text-anchor:start;fill:#78079a;fill-opacity:1;stroke:none" + id="path3376" + inkscape:connector-curvature="0" /> + <path + d="m 301.26328,49.603792 c 0,2.414819 1.36221,4.210454 3.71511,4.210454 2.3529,0 3.7151,-1.795635 3.7151,-4.210454 l 0,-13.560138 c 0,-5.696496 1.79564,-7.182539 5.44883,-7.182539 2.66249,0 4.27237,-1.114532 4.27237,-3.467432 0,-2.105227 -1.11453,-3.59127 -3.83894,-3.59127 -3.46744,0 -5.82034,1.486043 -6.31568,4.891557 l -0.12384,0 -0.12384,-1.919472 c -0.24767,-2.786329 -1.98139,-2.972085 -3.34359,-2.972085 -2.16715,0 -3.40552,1.238369 -3.40552,3.777025 l 0,24.024354 z" + style="font-style:normal;font-variant:normal;font-weight:bold;font-stretch:normal;font-size:61.91843796px;line-height:100%;font-family:'ITC Benguiat Gothic Std';-inkscape-font-specification:'ITC Benguiat Gothic Std Bold';text-align:start;letter-spacing:0px;word-spacing:0px;writing-mode:lr-tb;text-anchor:start;fill:#78079a;fill-opacity:1;stroke:none" + id="path3378" + inkscape:connector-curvature="0" /> + <path + d="m 348.2584,25.827112 c 0,-2.229064 -1.17645,-4.024699 -3.71511,-4.024699 -2.53866,0 -3.71511,1.795635 -3.71511,4.024699 l 0,12.817116 c 0,5.758415 -2.72441,8.668582 -6.93486,8.668582 -3.3436,0 -5.01539,-2.105227 -5.01539,-6.439518 l 0,-15.04618 c 0,-2.229064 -1.17645,-4.024699 -3.71511,-4.024699 -2.53866,0 -3.71511,1.795635 -3.71511,4.024699 l 0,17.02757 c 0,6.315681 4.33429,11.145319 11.02149,11.145319 3.40551,0 5.88225,-0.990695 8.35898,-3.343596 0,1.547961 1.17645,3.343596 3.71511,3.343596 2.53866,0 3.71511,-1.795635 3.71511,-4.024698 l 0,-24.148191 z" + style="font-style:normal;font-variant:normal;font-weight:bold;font-stretch:normal;font-size:61.91843796px;line-height:100%;font-family:'ITC Benguiat Gothic Std';-inkscape-font-specification:'ITC Benguiat Gothic Std Bold';text-align:start;letter-spacing:0px;word-spacing:0px;writing-mode:lr-tb;text-anchor:start;fill:#78079a;fill-opacity:1;stroke:none" + id="path3380" + inkscape:connector-curvature="0" /> + <path + d="m 355.79019,49.789547 c 0,2.229064 1.17645,4.024699 3.7151,4.024699 2.53866,0 3.71511,-1.795635 3.71511,-4.024699 l 0,-12.631361 c 0,-5.820333 2.66249,-8.668581 5.94417,-8.668581 4.14853,0 5.01539,3.281677 5.01539,7.554049 l 0,13.745893 c 0,2.229064 1.17645,4.024699 3.71511,4.024699 2.53865,0 3.7151,-1.795635 3.7151,-4.024699 l 0,-12.631361 c 0,-5.820333 2.6625,-8.668581 5.94417,-8.668581 4.14854,0 5.0154,3.281677 5.0154,7.554049 l 0,13.745893 c 0,2.229064 1.17645,4.024699 3.7151,4.024699 2.53866,0 3.71511,-1.795635 3.71511,-4.024699 l 0,-16.841815 c 0,-6.315681 -4.33429,-11.145319 -11.02148,-11.145319 -4.08662,0 -7.30638,2.167146 -9.96887,4.643883 -2.84825,-3.529351 -5.07731,-4.643883 -8.66858,-4.643883 -3.03401,0 -5.6965,1.238369 -7.86364,3.343596 0,-1.733716 -1.05262,-3.343596 -3.3436,-3.343596 -2.29098,0 -3.34359,1.60988 -3.34359,3.59127 l 0,24.395864 z" + style="font-style:normal;font-variant:normal;font-weight:bold;font-stretch:normal;font-size:61.91843796px;line-height:100%;font-family:'ITC Benguiat Gothic Std';-inkscape-font-specification:'ITC Benguiat Gothic Std Bold';text-align:start;letter-spacing:0px;word-spacing:0px;writing-mode:lr-tb;text-anchor:start;fill:#78079a;fill-opacity:1;stroke:none" + id="path3382" + inkscape:connector-curvature="0" /> + </g> + <g + transform="matrix(0.02211373,0,0,0.02211373,20.216433,16.77932)" + id="g3" + style="fill:url(#radialGradient3175);fill-opacity:1;stroke:url(#radialGradient3171);stroke-width:1;stroke-miterlimit:4;stroke-dasharray:none"> + <g + transform="translate(20.61545,-27.69425)" + style="fill:url(#radialGradient3016);fill-opacity:1;fill-rule:evenodd;stroke:url(#radialGradient3018);stroke-width:1;stroke-miterlimit:4;stroke-dasharray:none" + id="g5"> + <path + d="m 931.07168,1164.597 248.86992,-331.80265 416.1687,1338.32935 286.6484,267.1042 -520.4224,0 -270.2797,-262.2181 0,-1033.0627 -160.98492,106.6818 -160.98492,-106.6818 0,1033.0627 -270.2797,262.2181 -520.4224,0 286.6484,-267.1042 416.1687,-1338.32935 248.86992,331.80265 z" + id="path7" + style="fill:url(#radialGradient3008);fill-opacity:1;stroke:url(#radialGradient3010);stroke-width:1;stroke-miterlimit:4;stroke-dasharray:none" + inkscape:connector-curvature="0" /> + <path + d="m 931.07168,27.69425 224.03682,720.46517 -63.341,76.00913 L 931.07168,486.3269 770.37586,824.16855 707.03486,748.15942 931.07168,27.69425 Z" + id="path9" + style="fill:url(#radialGradient3012);fill-opacity:1;stroke:url(#radialGradient3014);stroke-width:1;stroke-miterlimit:4;stroke-dasharray:none" + inkscape:connector-curvature="0" /> + </g> + </g> +</svg> diff --git a/AltOS/doc/altusmetrum-revhistory.html b/AltOS/doc/altusmetrum-revhistory.html new file mode 100644 index 0000000..529cf0a --- /dev/null +++ b/AltOS/doc/altusmetrum-revhistory.html @@ -0,0 +1,47 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Revision History</title><link rel="stylesheet" type="text/css" href="am.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.78.1" /></head><body><div class="revhistory"><table style="border-style:solid; width:100%;" summary="Revision History"><tr><th align="left" valign="top" colspan="2"><strong>Revision History</strong></th></tr><tr><td align="left">Revision 1.6.2</td><td align="left">10 January 2016</td></tr><tr><td align="left" colspan="2"> + Minor release adding TeleMega v2.0 support. + </td></tr><tr><td align="left">Revision 1.6.1</td><td align="left">15 July 2015</td></tr><tr><td align="left" colspan="2"> + Minor release adding TeleBT v3.0 support. + </td></tr><tr><td align="left">Revision 1.6</td><td align="left">8 January 2015</td></tr><tr><td align="left" colspan="2"> + Major release adding TeleDongle v3.0 support. + </td></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.2</td><td align="left">17 August 2014</td></tr><tr><td align="left" colspan="2"> + Minor release fixing some Windows installation bugs. + </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 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><tr><td align="left">Revision 0.7.1</td><td align="left">29 September 2010</td></tr><tr><td align="left" colspan="2">Added AltosUI</td></tr></table></div></body></html> diff --git a/AltOS/doc/altusmetrum.html b/AltOS/doc/altusmetrum.html index df2f2b3..2c85d76 100644 --- a/AltOS/doc/altusmetrum.html +++ b/AltOS/doc/altusmetrum.html @@ -1,4222 +1,3075 @@ -<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="idm46789057122240"></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 2015 Bdale Garbee and Keith Packard</p></div><div><div class="legalnotice"><a name="idm46789029905184"></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.6.1</td><td align="left">15 July 2015</td></tr><tr><td align="left" colspan="2"> - Minor release adding TeleBT v3.0 support. - </td></tr><tr><td align="left">Revision 1.6</td><td align="left">8 January 2015</td></tr><tr><td align="left" colspan="2"> - Major release adding TeleDongle v3.0 support. - </td></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="idm46789030789808"></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> -BdaleGarbee,KB0G<br> -NAR#87103,TRA#12201<br> -<br> -KeithPackard,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="#idm46789030785712">1. Introduction and Overview</a></span></dt><dt><span class="chapter"><a href="#idm46789030776640">2. Getting Started</a></span></dt><dt><span class="chapter"><a href="#idm46789027405184">3. Handling Precautions</a></span></dt><dt><span class="chapter"><a href="#idm46789028904096">4. Altus Metrum Hardware</a></span></dt><dd><dl><dt><span class="section"><a href="#idm46789028066704">1. General Usage Instructions</a></span></dt><dd><dl><dt><span class="section"><a href="#idm46789028582128">1.1. Hooking Up Lithium Polymer Batteries</a></span></dt><dt><span class="section"><a href="#idm46789027787840">1.2. Hooking Up Pyro Charges</a></span></dt><dt><span class="section"><a href="#idm46789027264112">1.3. Hooking Up a Power Switch</a></span></dt><dt><span class="section"><a href="#idm46789030826864">1.4. Using a Separate Pyro Battery</a></span></dt><dt><span class="section"><a href="#idm46789030824352">1.5. Using a Different Kind of Battery</a></span></dt></dl></dd><dt><span class="section"><a href="#idm46789025273872">2. Specifications</a></span></dt><dt><span class="section"><a href="#idm46789025180848">3. TeleMetrum</a></span></dt><dd><dl><dt><span class="section"><a href="#idm46789025175952">3.1. TeleMetrum Screw Terminals</a></span></dt><dt><span class="section"><a href="#idm46789025156736">3.2. Using a Separate Pyro Battery with TeleMetrum</a></span></dt><dt><span class="section"><a href="#idm46789025153488">3.3. Using an Active Switch with TeleMetrum</a></span></dt></dl></dd><dt><span class="section"><a href="#idm46789025151360">4. TeleMini v1.0</a></span></dt><dd><dl><dt><span class="section"><a href="#idm46789025146464">4.1. TeleMini v1.0 Screw Terminals</a></span></dt><dt><span class="section"><a href="#idm46789025127120">4.2. Using a Separate Pyro Battery with TeleMini v1.0</a></span></dt><dt><span class="section"><a href="#idm46789025123744">4.3. Using an Active Switch with TeleMini v1.0</a></span></dt></dl></dd><dt><span class="section"><a href="#idm46789025121536">5. TeleMini v2.0</a></span></dt><dd><dl><dt><span class="section"><a href="#idm46789025117520">5.1. TeleMini v2.0 Screw Terminals</a></span></dt><dt><span class="section"><a href="#idm46789025095136">5.2. Using a Separate Pyro Battery with TeleMini v2.0</a></span></dt><dt><span class="section"><a href="#idm46789025091936">5.3. Using an Active Switch with TeleMini v2.0</a></span></dt></dl></dd><dt><span class="section"><a href="#idm46789025089840">6. EasyMini</a></span></dt><dd><dl><dt><span class="section"><a href="#idm46789025085984">6.1. EasyMini Screw Terminals</a></span></dt><dt><span class="section"><a href="#idm46789025063600">6.2. Using a Separate Pyro Battery with EasyMini</a></span></dt><dt><span class="section"><a href="#idm46789025060416">6.3. Using an Active Switch with EasyMini</a></span></dt></dl></dd><dt><span class="section"><a href="#idm46789025058320">7. TeleMega</a></span></dt><dd><dl><dt><span class="section"><a href="#idm46789025054352">7.1. TeleMega Screw Terminals</a></span></dt><dt><span class="section"><a href="#idm46789025016848">7.2. Using a Separate Pyro Battery with TeleMega</a></span></dt><dt><span class="section"><a href="#idm46789025015248">7.3. Using Only One Battery With TeleMega</a></span></dt><dt><span class="section"><a href="#idm46789025013328">7.4. Using an Active Switch with TeleMega</a></span></dt></dl></dd><dt><span class="section"><a href="#idm46789025011280">8. EasyMega</a></span></dt><dd><dl><dt><span class="section"><a href="#idm46789025007312">8.1. EasyMega Screw Terminals</a></span></dt><dt><span class="section"><a href="#idm46789024969808">8.2. Using a Separate Pyro Battery with EasyMega</a></span></dt><dt><span class="section"><a href="#idm46789024968208">8.3. Using Only One Battery With EasyMega</a></span></dt><dt><span class="section"><a href="#idm46789024966288">8.4. Using an Active Switch with EasyMega</a></span></dt></dl></dd><dt><span class="section"><a href="#idm46789024964240">9. Flight Data Recording</a></span></dt><dt><span class="section"><a href="#idm46789024933472">10. Installation</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idm46789024926304">5. System Operation</a></span></dt><dd><dl><dt><span class="section"><a href="#idm46789024925664">1. Firmware Modes </a></span></dt><dt><span class="section"><a href="#idm46789024857168">2. GPS </a></span></dt><dt><span class="section"><a href="#idm46789024854384">3. Controlling An Altimeter Over The Radio Link</a></span></dt><dt><span class="section"><a href="#idm46789024843088">4. Ground Testing </a></span></dt><dt><span class="section"><a href="#idm46789024840336">5. Radio Link </a></span></dt><dt><span class="section"><a href="#idm46789024836336">6. APRS</a></span></dt><dt><span class="section"><a href="#idm46789024812016">7. Configurable Parameters</a></span></dt><dd><dl><dt><span class="section"><a href="#idm46789024810096">7.1. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idm46789024808048">7.2. Callsign</a></span></dt><dt><span class="section"><a href="#idm46789024806512">7.3. Telemetry/RDF/APRS Enable</a></span></dt><dt><span class="section"><a href="#idm46789024805216">7.4. Telemetry baud rate</a></span></dt><dt><span class="section"><a href="#idm46789024803648">7.5. APRS Interval</a></span></dt><dt><span class="section"><a href="#idm46789024802176">7.6. APRS SSID</a></span></dt><dt><span class="section"><a href="#idm46789024800832">7.7. Apogee Delay</a></span></dt><dt><span class="section"><a href="#idm46789024798240">7.8. Apogee Lockout</a></span></dt><dt><span class="section"><a href="#idm46789024796512">7.9. Main Deployment Altitude</a></span></dt><dt><span class="section"><a href="#idm46789024794816">7.10. Maximum Flight Log</a></span></dt><dt><span class="section"><a href="#idm46789024792672">7.11. Ignite Mode</a></span></dt><dt><span class="section"><a href="#idm46789024790560">7.12. Pad Orientation</a></span></dt><dt><span class="section"><a href="#idm46789024788864">7.13. Configurable Pyro Channels</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#idm46789024766256">6. AltosUI</a></span></dt><dd><dl><dt><span class="section"><a href="#idm46789024762640">1. Monitor Flight</a></span></dt><dd><dl><dt><span class="section"><a href="#idm46789024749312">1.1. Launch Pad</a></span></dt><dt><span class="section"><a href="#idm46789024733680">1.2. Ascent</a></span></dt><dt><span class="section"><a href="#idm46789024728224">1.3. Descent</a></span></dt><dt><span class="section"><a href="#idm46789024721360">1.4. Landed</a></span></dt><dt><span class="section"><a href="#idm46789024714928">1.5. Table</a></span></dt><dt><span class="section"><a href="#idm46789024711344">1.6. Site Map</a></span></dt><dt><span class="section"><a href="#idm46789024704592">1.7. Ignitor</a></span></dt></dl></dd><dt><span class="section"><a href="#idm46789024700816">2. Save Flight Data</a></span></dt><dt><span class="section"><a href="#idm46789024696864">3. Replay Flight</a></span></dt><dt><span class="section"><a href="#idm46789024694832">4. Graph Data</a></span></dt><dd><dl><dt><span class="section"><a href="#idm46789024692448">4.1. Flight Graph</a></span></dt><dt><span class="section"><a href="#idm46789024688000">4.2. Configure Graph</a></span></dt><dt><span class="section"><a href="#idm46789024684336">4.3. Flight Statistics</a></span></dt><dt><span class="section"><a href="#idm46789024680816">4.4. Map</a></span></dt></dl></dd><dt><span class="section"><a href="#idm46789024676960">5. Export Data</a></span></dt><dd><dl><dt><span class="section"><a href="#idm46789024675392">5.1. Comma Separated Value Format</a></span></dt><dt><span class="section"><a href="#idm46789024673040">5.2. Keyhole Markup Language (for Google Earth)</a></span></dt></dl></dd><dt><span class="section"><a href="#idm46789024671552">6. Configure Altimeter</a></span></dt><dd><dl><dt><span class="section"><a href="#idm46789024659248">6.1. Main Deploy Altitude</a></span></dt><dt><span class="section"><a href="#idm46789024657680">6.2. Apogee Delay</a></span></dt><dt><span class="section"><a href="#idm46789024656064">6.3. Apogee Lockoug</a></span></dt><dt><span class="section"><a href="#idm46789024653760">6.4. Frequency</a></span></dt><dt><span class="section"><a href="#idm46789024652256">6.5. RF Calibration</a></span></dt><dt><span class="section"><a href="#idm46789024650608">6.6. Telemetry/RDF/APRS Enable</a></span></dt><dt><span class="section"><a href="#idm46789024649312">6.7. Telemetry baud rate</a></span></dt><dt><span class="section"><a href="#idm46789024647744">6.8. APRS Interval</a></span></dt><dt><span class="section"><a href="#idm46789024646176">6.9. APRS SSID</a></span></dt><dt><span class="section"><a href="#idm46789024644848">6.10. Callsign</a></span></dt><dt><span class="section"><a href="#idm46789024643536">6.11. Maximum Flight Log Size</a></span></dt><dt><span class="section"><a href="#idm46789024642096">6.12. Ignitor Firing Mode</a></span></dt><dt><span class="section"><a href="#idm46789024635184">6.13. Pad Orientation</a></span></dt><dt><span class="section"><a href="#idm46789024629952">6.14. Beeper Frequency</a></span></dt><dt><span class="section"><a href="#idm46789024628496">6.15. Configure Pyro Channels</a></span></dt></dl></dd><dt><span class="section"><a href="#idm46789024622112">7. Configure AltosUI</a></span></dt><dd><dl><dt><span class="section"><a href="#idm46789024618608">7.1. Voice Settings</a></span></dt><dt><span class="section"><a href="#idm46789024613584">7.2. Log Directory</a></span></dt><dt><span class="section"><a href="#idm46789024611584">7.3. Callsign</a></span></dt><dt><span class="section"><a href="#idm46789024609344">7.4. Imperial Units</a></span></dt><dt><span class="section"><a href="#idm46789024607840">7.5. Font Size</a></span></dt><dt><span class="section"><a href="#idm46789024606560">7.6. Serial Debug</a></span></dt><dt><span class="section"><a href="#idm46789024605056">7.7. Manage Frequencies</a></span></dt></dl></dd><dt><span class="section"><a href="#idm46789024603424">8. Configure Groundstation</a></span></dt><dd><dl><dt><span class="section"><a href="#idm46789024592304">8.1. Frequency</a></span></dt><dt><span class="section"><a href="#idm46789024590736">8.2. RF Calibration</a></span></dt><dt><span class="section"><a href="#idm46789024589216">8.3. Telemetry Rate</a></span></dt></dl></dd><dt><span class="section"><a href="#idm46789024587744">9. Flash Image</a></span></dt><dt><span class="section"><a href="#idm46789024586080">10. Fire Igniter</a></span></dt><dt><span class="section"><a href="#idm46789024580448">11. Scan Channels</a></span></dt><dt><span class="section"><a href="#idm46789024576576">12. Load Maps</a></span></dt><dt><span class="section"><a href="#idm46789024562512">13. Monitor Idle</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idm46789024557472">7. AltosDroid</a></span></dt><dd><dl><dt><span class="section"><a href="#idm46789024554880">1. Installing AltosDroid</a></span></dt><dt><span class="section"><a href="#idm46789024552944">2. Connecting to TeleBT over Bluetooth™</a></span></dt><dt><span class="section"><a href="#idm46789024550848">3. Connecting to TeleDongle or TeleBT over USB</a></span></dt><dt><span class="section"><a href="#idm46789024549264">4. Configuring AltosDroid</a></span></dt><dd><dl><dt><span class="section"><a href="#idm46789024548128">4.1. Select radio frequency</a></span></dt><dt><span class="section"><a href="#idm46789024546816">4.2. Select data rate</a></span></dt><dt><span class="section"><a href="#idm46789024545424">4.3. Change units</a></span></dt><dt><span class="section"><a href="#idm46789024544272">4.4. Load maps</a></span></dt><dt><span class="section"><a href="#idm46789024542928">4.5. Map type</a></span></dt><dt><span class="section"><a href="#idm46789024541440">4.6. Toggle Online/Offline maps</a></span></dt><dt><span class="section"><a href="#idm46789024540032">4.7. Select Tracker</a></span></dt><dt><span class="section"><a href="#idm46789024538592">4.8. Delete Track</a></span></dt></dl></dd><dt><span class="section"><a href="#idm46789024537232">5. AltosDroid Flight Monitoring</a></span></dt><dd><dl><dt><span class="section"><a href="#idm46789024535920">5.1. Pad</a></span></dt><dt><span class="section"><a href="#idm46789024518464">5.2. Flight</a></span></dt><dt><span class="section"><a href="#idm46789024497344">5.3. Recover</a></span></dt><dt><span class="section"><a href="#idm46789024482000">5.4. Map</a></span></dt></dl></dd><dt><span class="section"><a href="#idm46789024478928">6. Downloading Flight Logs</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idm46789024477280">8. Using Altus Metrum Products</a></span></dt><dd><dl><dt><span class="section"><a href="#idm46789024476640">1. Being Legal</a></span></dt><dt><span class="section"><a href="#idm46789024474736">2. In the Rocket</a></span></dt><dt><span class="section"><a href="#idm46789024472208">3. On the Ground</a></span></dt><dt><span class="section"><a href="#idm46789024458400">4. Data Analysis</a></span></dt><dt><span class="section"><a href="#idm46789024455856">5. Future Plans</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idm46789024451664">9. Altimeter Installation Recommendations</a></span></dt><dd><dl><dt><span class="section"><a href="#idm46789024450208">1. Mounting the Altimeter</a></span></dt><dt><span class="section"><a href="#idm46789024445376">2. Dealing with the Antenna</a></span></dt><dt><span class="section"><a href="#idm46789024439280">3. Preserving GPS Reception</a></span></dt><dt><span class="section"><a href="#idm46789024434496">4. Radio Frequency Interference</a></span></dt><dt><span class="section"><a href="#idm46789024426928">5. The Barometric Sensor</a></span></dt><dt><span class="section"><a href="#idm46789024424128">6. Ground Testing</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idm46789024420960">10. Updating Device Firmware</a></span></dt><dd><dl><dt><span class="section"><a href="#idm46789024416880">1. - Updating TeleMega, TeleMetrum v2, EasyMega, EasyMini or - TeleDongle v3 Firmware - </a></span></dt><dd><dl><dt><span class="section"><a href="#idm46789024407744">1.1. Recovering From Self-Flashing Failure</a></span></dt></dl></dd><dt><span class="section"><a href="#idm46789024387392">2. Pair Programming</a></span></dt><dt><span class="section"><a href="#idm46789024385936">3. Updating TeleMetrum v1.x Firmware</a></span></dt><dt><span class="section"><a href="#idm46789024372672">4. Updating TeleMini Firmware</a></span></dt><dt><span class="section"><a href="#idm46789024359056">5. Updating TeleDongle v0.2 Firmware</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idm46789024342288">11. Hardware Specifications</a></span></dt><dd><dl><dt><span class="section"><a href="#idm46789024341648">1. - TeleMega Specifications - </a></span></dt><dt><span class="section"><a href="#idm46789024330176">2. - EasyMega Specifications - </a></span></dt><dt><span class="section"><a href="#idm46789024320432">3. - TeleMetrum v2 Specifications - </a></span></dt><dt><span class="section"><a href="#idm46789024309872">4. TeleMetrum v1 Specifications</a></span></dt><dt><span class="section"><a href="#idm46789024299312">5. - TeleMini v2.0 Specifications - </a></span></dt><dt><span class="section"><a href="#idm46789024290480">6. - TeleMini v1.0 Specifications - </a></span></dt><dt><span class="section"><a href="#idm46789024281680">7. - EasyMini Specifications - </a></span></dt></dl></dd><dt><span class="chapter"><a href="#idm46789024273568">12. FAQ</a></span></dt><dt><span class="appendix"><a href="#idm46789024264720">A. Notes for Older Software</a></span></dt><dt><span class="appendix"><a href="#idm46789024241856">B. Drill Templates</a></span></dt><dd><dl><dt><span class="section"><a href="#idm46789024240688">1. TeleMega template</a></span></dt><dt><span class="section"><a href="#idm46789024224000">2. EasyMega template</a></span></dt><dt><span class="section"><a href="#idm46789024219616">3. TeleMetrum template</a></span></dt><dt><span class="section"><a href="#idm46789024215232">4. TeleMini v2/EasyMini template</a></span></dt><dt><span class="section"><a href="#idm46789024210832">5. TeleMini v1 template</a></span></dt></dl></dd><dt><span class="appendix"><a href="#idm46789024206320">C. Calibration</a></span></dt><dd><dl><dt><span class="section"><a href="#idm46789024204768">1. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idm46789024200224">2. TeleMetrum, TeleMega and EasyMega Accelerometers</a></span></dt></dl></dd><dt><span class="appendix"><a href="#idm46789024194544">D. Igniter Current</a></span></dt><dd><dl><dt><span class="section"><a href="#idm46789024193280">1. Current Products</a></span></dt><dt><span class="section"><a href="#idm46789024189840">2. Version 1 Products</a></span></dt></dl></dd><dt><span class="appendix"><a href="#idm46789024187504">E. 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="#idm46789025272848">Altus Metrum Electronics</a></dt><dt>4.2. <a href="#idm46789025221600">Altus Metrum Boards</a></dt><dt>4.3. <a href="#idm46789025174640">TeleMetrum Screw Terminals</a></dt><dt>4.4. <a href="#idm46789025145024">TeleMini v1.0 Connections</a></dt><dt>4.5. <a href="#idm46789025116112">TeleMini v2.0 Connections</a></dt><dt>4.6. <a href="#idm46789025084576">EasyMini Connections</a></dt><dt>4.7. <a href="#idm46789025053184">TeleMega Screw Terminals</a></dt><dt>4.8. <a href="#idm46789025006144">EasyMega Screw Terminals</a></dt><dt>4.9. <a href="#idm46789024962832">Data Storage on Altus Metrum altimeters</a></dt><dt>5.1. <a href="#idm46789024920304">AltOS Modes</a></dt><dt>5.2. <a href="#idm46789024883120">Pad/Idle Indications</a></dt><dt>5.3. <a href="#idm46789024832528">Altus Metrum APRS Comments</a></dt></dl></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idm46789030785712"></a>Chapter1.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 v0.2 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. The latest version, TeleDongle - v3, has all new electronics with a higher performance radio - for improved range. - </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="idm46789030776640"></a>Chapter2.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="idm46789027405184"></a>Chapter3.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="idm46789028904096"></a>Chapter4.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="#idm46789028066704">1. General Usage Instructions</a></span></dt><dd><dl><dt><span class="section"><a href="#idm46789028582128">1.1. Hooking Up Lithium Polymer Batteries</a></span></dt><dt><span class="section"><a href="#idm46789027787840">1.2. Hooking Up Pyro Charges</a></span></dt><dt><span class="section"><a href="#idm46789027264112">1.3. Hooking Up a Power Switch</a></span></dt><dt><span class="section"><a href="#idm46789030826864">1.4. Using a Separate Pyro Battery</a></span></dt><dt><span class="section"><a href="#idm46789030824352">1.5. Using a Different Kind of Battery</a></span></dt></dl></dd><dt><span class="section"><a href="#idm46789025273872">2. Specifications</a></span></dt><dt><span class="section"><a href="#idm46789025180848">3. TeleMetrum</a></span></dt><dd><dl><dt><span class="section"><a href="#idm46789025175952">3.1. TeleMetrum Screw Terminals</a></span></dt><dt><span class="section"><a href="#idm46789025156736">3.2. Using a Separate Pyro Battery with TeleMetrum</a></span></dt><dt><span class="section"><a href="#idm46789025153488">3.3. Using an Active Switch with TeleMetrum</a></span></dt></dl></dd><dt><span class="section"><a href="#idm46789025151360">4. TeleMini v1.0</a></span></dt><dd><dl><dt><span class="section"><a href="#idm46789025146464">4.1. TeleMini v1.0 Screw Terminals</a></span></dt><dt><span class="section"><a href="#idm46789025127120">4.2. Using a Separate Pyro Battery with TeleMini v1.0</a></span></dt><dt><span class="section"><a href="#idm46789025123744">4.3. Using an Active Switch with TeleMini v1.0</a></span></dt></dl></dd><dt><span class="section"><a href="#idm46789025121536">5. TeleMini v2.0</a></span></dt><dd><dl><dt><span class="section"><a href="#idm46789025117520">5.1. TeleMini v2.0 Screw Terminals</a></span></dt><dt><span class="section"><a href="#idm46789025095136">5.2. Using a Separate Pyro Battery with TeleMini v2.0</a></span></dt><dt><span class="section"><a href="#idm46789025091936">5.3. Using an Active Switch with TeleMini v2.0</a></span></dt></dl></dd><dt><span class="section"><a href="#idm46789025089840">6. EasyMini</a></span></dt><dd><dl><dt><span class="section"><a href="#idm46789025085984">6.1. EasyMini Screw Terminals</a></span></dt><dt><span class="section"><a href="#idm46789025063600">6.2. Using a Separate Pyro Battery with EasyMini</a></span></dt><dt><span class="section"><a href="#idm46789025060416">6.3. Using an Active Switch with EasyMini</a></span></dt></dl></dd><dt><span class="section"><a href="#idm46789025058320">7. TeleMega</a></span></dt><dd><dl><dt><span class="section"><a href="#idm46789025054352">7.1. TeleMega Screw Terminals</a></span></dt><dt><span class="section"><a href="#idm46789025016848">7.2. Using a Separate Pyro Battery with TeleMega</a></span></dt><dt><span class="section"><a href="#idm46789025015248">7.3. Using Only One Battery With TeleMega</a></span></dt><dt><span class="section"><a href="#idm46789025013328">7.4. Using an Active Switch with TeleMega</a></span></dt></dl></dd><dt><span class="section"><a href="#idm46789025011280">8. EasyMega</a></span></dt><dd><dl><dt><span class="section"><a href="#idm46789025007312">8.1. EasyMega Screw Terminals</a></span></dt><dt><span class="section"><a href="#idm46789024969808">8.2. Using a Separate Pyro Battery with EasyMega</a></span></dt><dt><span class="section"><a href="#idm46789024968208">8.3. Using Only One Battery With EasyMega</a></span></dt><dt><span class="section"><a href="#idm46789024966288">8.4. Using an Active Switch with EasyMega</a></span></dt></dl></dd><dt><span class="section"><a href="#idm46789024964240">9. Flight Data Recording</a></span></dt><dt><span class="section"><a href="#idm46789024933472">10. Installation</a></span></dt></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idm46789028066704"></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="idm46789028582128"></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="idm46789027787840"></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="idm46789027264112"></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="idm46789027475824"></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="idm46789030826864"></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="idm46789030824352"></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="idm46789025273872"></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="idm46789025272848"></a><p class="title"><b>Table4.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="idm46789025221600"></a><p class="title"><b>Table4.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="idm46789025180848"></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="idm46789025175952"></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="idm46789025174640"></a><p class="title"><b>Table4.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="idm46789025156736"></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="idm46789025153488"></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="idm46789025151360"></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="idm46789025146464"></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="idm46789025145024"></a><p class="title"><b>Table4.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="idm46789025127120"></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="idm46789025123744"></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="idm46789025121536"></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="idm46789025117520"></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="idm46789025116112"></a><p class="title"><b>Table4.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="idm46789025095136"></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="idm46789025091936"></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="idm46789025089840"></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="idm46789025085984"></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="idm46789025084576"></a><p class="title"><b>Table4.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="idm46789025063600"></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="idm46789025060416"></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="idm46789025058320"></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="idm46789025054352"></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="idm46789025053184"></a><p class="title"><b>Table4.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="idm46789025016848"></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="idm46789025015248"></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="idm46789025013328"></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="idm46789025011280"></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="idm46789025007312"></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="idm46789025006144"></a><p class="title"><b>Table4.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="idm46789024969808"></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="idm46789024968208"></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="idm46789024966288"></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="idm46789024964240"></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="idm46789024962832"></a><p class="title"><b>Table4.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="idm46789024933472"></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="idm46789024926304"></a>Chapter5.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="#idm46789024925664">1. Firmware Modes </a></span></dt><dt><span class="section"><a href="#idm46789024857168">2. GPS </a></span></dt><dt><span class="section"><a href="#idm46789024854384">3. Controlling An Altimeter Over The Radio Link</a></span></dt><dt><span class="section"><a href="#idm46789024843088">4. Ground Testing </a></span></dt><dt><span class="section"><a href="#idm46789024840336">5. Radio Link </a></span></dt><dt><span class="section"><a href="#idm46789024836336">6. APRS</a></span></dt><dt><span class="section"><a href="#idm46789024812016">7. Configurable Parameters</a></span></dt><dd><dl><dt><span class="section"><a href="#idm46789024810096">7.1. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idm46789024808048">7.2. Callsign</a></span></dt><dt><span class="section"><a href="#idm46789024806512">7.3. Telemetry/RDF/APRS Enable</a></span></dt><dt><span class="section"><a href="#idm46789024805216">7.4. Telemetry baud rate</a></span></dt><dt><span class="section"><a href="#idm46789024803648">7.5. APRS Interval</a></span></dt><dt><span class="section"><a href="#idm46789024802176">7.6. APRS SSID</a></span></dt><dt><span class="section"><a href="#idm46789024800832">7.7. Apogee Delay</a></span></dt><dt><span class="section"><a href="#idm46789024798240">7.8. Apogee Lockout</a></span></dt><dt><span class="section"><a href="#idm46789024796512">7.9. Main Deployment Altitude</a></span></dt><dt><span class="section"><a href="#idm46789024794816">7.10. Maximum Flight Log</a></span></dt><dt><span class="section"><a href="#idm46789024792672">7.11. Ignite Mode</a></span></dt><dt><span class="section"><a href="#idm46789024790560">7.12. Pad Orientation</a></span></dt><dt><span class="section"><a href="#idm46789024788864">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="idm46789024925664"></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="idm46789024920304"></a><p class="title"><b>Table5.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="idm46789024883120"></a><p class="title"><b>Table5.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="idm46789024857168"></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="idm46789024854384"></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="idm46789024843088"></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="idm46789024840336"></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="idm46789024836336"></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="idm46789024832528"></a><p class="title"><b>Table5.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="idm46789024812016"></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="idm46789024810096"></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="idm46789024808048"></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="idm46789024806512"></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="idm46789024805216"></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="idm46789024803648"></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="idm46789024802176"></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="idm46789024800832"></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="idm46789024798240"></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="idm46789024796512"></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="idm46789024794816"></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="idm46789024792672"></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="idm46789024790560"></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="idm46789024788864"></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 and then decelerating - (presumably due to a motor or motors burning). Use this - value 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="idm46789024766256"></a>Chapter6.AltosUI</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idm46789024762640">1. Monitor Flight</a></span></dt><dd><dl><dt><span class="section"><a href="#idm46789024749312">1.1. Launch Pad</a></span></dt><dt><span class="section"><a href="#idm46789024733680">1.2. Ascent</a></span></dt><dt><span class="section"><a href="#idm46789024728224">1.3. Descent</a></span></dt><dt><span class="section"><a href="#idm46789024721360">1.4. Landed</a></span></dt><dt><span class="section"><a href="#idm46789024714928">1.5. Table</a></span></dt><dt><span class="section"><a href="#idm46789024711344">1.6. Site Map</a></span></dt><dt><span class="section"><a href="#idm46789024704592">1.7. Ignitor</a></span></dt></dl></dd><dt><span class="section"><a href="#idm46789024700816">2. Save Flight Data</a></span></dt><dt><span class="section"><a href="#idm46789024696864">3. Replay Flight</a></span></dt><dt><span class="section"><a href="#idm46789024694832">4. Graph Data</a></span></dt><dd><dl><dt><span class="section"><a href="#idm46789024692448">4.1. Flight Graph</a></span></dt><dt><span class="section"><a href="#idm46789024688000">4.2. Configure Graph</a></span></dt><dt><span class="section"><a href="#idm46789024684336">4.3. Flight Statistics</a></span></dt><dt><span class="section"><a href="#idm46789024680816">4.4. Map</a></span></dt></dl></dd><dt><span class="section"><a href="#idm46789024676960">5. Export Data</a></span></dt><dd><dl><dt><span class="section"><a href="#idm46789024675392">5.1. Comma Separated Value Format</a></span></dt><dt><span class="section"><a href="#idm46789024673040">5.2. Keyhole Markup Language (for Google Earth)</a></span></dt></dl></dd><dt><span class="section"><a href="#idm46789024671552">6. Configure Altimeter</a></span></dt><dd><dl><dt><span class="section"><a href="#idm46789024659248">6.1. Main Deploy Altitude</a></span></dt><dt><span class="section"><a href="#idm46789024657680">6.2. Apogee Delay</a></span></dt><dt><span class="section"><a href="#idm46789024656064">6.3. Apogee Lockoug</a></span></dt><dt><span class="section"><a href="#idm46789024653760">6.4. Frequency</a></span></dt><dt><span class="section"><a href="#idm46789024652256">6.5. RF Calibration</a></span></dt><dt><span class="section"><a href="#idm46789024650608">6.6. Telemetry/RDF/APRS Enable</a></span></dt><dt><span class="section"><a href="#idm46789024649312">6.7. Telemetry baud rate</a></span></dt><dt><span class="section"><a href="#idm46789024647744">6.8. APRS Interval</a></span></dt><dt><span class="section"><a href="#idm46789024646176">6.9. APRS SSID</a></span></dt><dt><span class="section"><a href="#idm46789024644848">6.10. Callsign</a></span></dt><dt><span class="section"><a href="#idm46789024643536">6.11. Maximum Flight Log Size</a></span></dt><dt><span class="section"><a href="#idm46789024642096">6.12. Ignitor Firing Mode</a></span></dt><dt><span class="section"><a href="#idm46789024635184">6.13. Pad Orientation</a></span></dt><dt><span class="section"><a href="#idm46789024629952">6.14. Beeper Frequency</a></span></dt><dt><span class="section"><a href="#idm46789024628496">6.15. Configure Pyro Channels</a></span></dt></dl></dd><dt><span class="section"><a href="#idm46789024622112">7. Configure AltosUI</a></span></dt><dd><dl><dt><span class="section"><a href="#idm46789024618608">7.1. Voice Settings</a></span></dt><dt><span class="section"><a href="#idm46789024613584">7.2. Log Directory</a></span></dt><dt><span class="section"><a href="#idm46789024611584">7.3. Callsign</a></span></dt><dt><span class="section"><a href="#idm46789024609344">7.4. Imperial Units</a></span></dt><dt><span class="section"><a href="#idm46789024607840">7.5. Font Size</a></span></dt><dt><span class="section"><a href="#idm46789024606560">7.6. Serial Debug</a></span></dt><dt><span class="section"><a href="#idm46789024605056">7.7. Manage Frequencies</a></span></dt></dl></dd><dt><span class="section"><a href="#idm46789024603424">8. Configure Groundstation</a></span></dt><dd><dl><dt><span class="section"><a href="#idm46789024592304">8.1. Frequency</a></span></dt><dt><span class="section"><a href="#idm46789024590736">8.2. RF Calibration</a></span></dt><dt><span class="section"><a href="#idm46789024589216">8.3. Telemetry Rate</a></span></dt></dl></dd><dt><span class="section"><a href="#idm46789024587744">9. Flash Image</a></span></dt><dt><span class="section"><a href="#idm46789024586080">10. Fire Igniter</a></span></dt><dt><span class="section"><a href="#idm46789024580448">11. Scan Channels</a></span></dt><dt><span class="section"><a href="#idm46789024576576">12. Load Maps</a></span></dt><dt><span class="section"><a href="#idm46789024562512">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="idm46789024762640"></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. At - the default data rate, 38400 bps, in bench testing, the - radio inside TeleDongle v0.2 operates down to about - -106dBm, while the v3 radio works down to about -111dBm. - Weaker signals, or an environment with radio noise may - cause the data to not be received. 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="idm46789024749312"></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="idm46789024733680"></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="idm46789024728224"></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="idm46789024721360"></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="idm46789024714928"></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="idm46789024711344"></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="idm46789024704592"></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="idm46789024700816"></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="idm46789024696864"></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="idm46789024694832"></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="idm46789024692448"></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="idm46789024688000"></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="idm46789024684336"></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="idm46789024680816"></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="idm46789024676960"></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="idm46789024675392"></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="idm46789024673040"></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="idm46789024671552"></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="idm46789024659248"></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="idm46789024657680"></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="idm46789024656064"></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="idm46789024653760"></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="idm46789024652256"></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="idm46789024650608"></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="idm46789024649312"></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="idm46789024647744"></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="idm46789024646176"></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="idm46789024644848"></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="idm46789024643536"></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="idm46789024642096"></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="idm46789024635184"></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="idm46789024629952"></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="idm46789024628496"></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="idm46789024622112"></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="idm46789024618608"></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="idm46789024613584"></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="idm46789024611584"></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="idm46789024609344"></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="idm46789024607840"></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="idm46789024606560"></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="idm46789024605056"></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="idm46789024603424"></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="idm46789024592304"></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="idm46789024590736"></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="idm46789024589216"></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="idm46789024587744"></a>9.Flash Image</h2></div></div></div><p> - This reprograms Altus Metrum devices with new - firmware. TeleMetrum v1.x, TeleDongle v0.2, TeleMini and - TeleBT are all reprogrammed by using another similar unit as a - programming dongle (pair programming). TeleMega, EasyMega, - TeleMetrum v2, EasyMini and TeleDongle v3 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="idm46789024586080"></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="idm46789024580448"></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="idm46789024576576"></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. - </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. Larger zoom levels show more - detail, smaller zoom levels less. - </p><p> - The Map Radius value sets how large an area around the center - point to download. Select a value large enough to cover any - plausible flight from that site. Be aware that loading a large - area with a high maximum zoom level can attempt to download a - lot of data. Loading hybrid maps with a 10km radius at a - minimum zoom of -2 and a maximum zoom of 2 consumes about - 120MB of space. Terrain and road maps consume about 1/10 as - much space as satellite or hybrid maps. - </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="idm46789024562512"></a>13.Monitor Idle</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="monitor-idle.png" width="468"></td></tr></table></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><p> - You can change the frequency and callsign used to communicate - with the flight computer; they must both match the - configuration in the flight computer exactly. - </p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idm46789024557472"></a>Chapter7.AltosDroid</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idm46789024554880">1. Installing AltosDroid</a></span></dt><dt><span class="section"><a href="#idm46789024552944">2. Connecting to TeleBT over Bluetooth™</a></span></dt><dt><span class="section"><a href="#idm46789024550848">3. Connecting to TeleDongle or TeleBT over USB</a></span></dt><dt><span class="section"><a href="#idm46789024549264">4. Configuring AltosDroid</a></span></dt><dd><dl><dt><span class="section"><a href="#idm46789024548128">4.1. Select radio frequency</a></span></dt><dt><span class="section"><a href="#idm46789024546816">4.2. Select data rate</a></span></dt><dt><span class="section"><a href="#idm46789024545424">4.3. Change units</a></span></dt><dt><span class="section"><a href="#idm46789024544272">4.4. Load maps</a></span></dt><dt><span class="section"><a href="#idm46789024542928">4.5. Map type</a></span></dt><dt><span class="section"><a href="#idm46789024541440">4.6. Toggle Online/Offline maps</a></span></dt><dt><span class="section"><a href="#idm46789024540032">4.7. Select Tracker</a></span></dt><dt><span class="section"><a href="#idm46789024538592">4.8. Delete Track</a></span></dt></dl></dd><dt><span class="section"><a href="#idm46789024537232">5. AltosDroid Flight Monitoring</a></span></dt><dd><dl><dt><span class="section"><a href="#idm46789024535920">5.1. Pad</a></span></dt><dt><span class="section"><a href="#idm46789024518464">5.2. Flight</a></span></dt><dt><span class="section"><a href="#idm46789024497344">5.3. Recover</a></span></dt><dt><span class="section"><a href="#idm46789024482000">5.4. Map</a></span></dt></dl></dd><dt><span class="section"><a href="#idm46789024478928">6. Downloading Flight Logs</a></span></dt></dl></div><p> - AltosDroid provides the same flight monitoring capabilities as - AltosUI, but runs on Android devices. AltosDroid is designed to connect - to a TeleBT receiver over Bluetooth™ and (on Android devices supporting - USB On-the-go) TeleDongle and TeleBT devices over USB. AltosDroid monitors - telemetry data, logging it to internal storage in the Android - device, and presents that data in a UI similar to the 'Monitor - Flight' window in AltosUI. - </p><p> - This manual will explain how to configure AltosDroid, connect to - TeleBT or TeleDongle, 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="idm46789024554880"></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="idm46789024552944"></a>2.Connecting to TeleBT over Bluetooth™</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="idm46789024550848"></a>3.Connecting to TeleDongle or TeleBT over USB</h2></div></div></div><p> - Get a special USB On-the-go adapter cable. These cables have a USB - micro-B male connector on one end and a standard A female - connector on the other end. Plug in your TeleDongle or TeleBT - device to the adapter cable and the adapter cable into your - phone and AltosDroid should automatically start up. If it - doesn't, the most likely reason is that your Android device - doesn't support USB On-the-go. - </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idm46789024549264"></a>4.Configuring AltosDroid</h2></div></div></div><p> - There are several configuration and operation parameters - available in the AltosDroid menu. - </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm46789024548128"></a>4.1.Select radio frequency</h3></div></div></div><p> - This selects which frequency to listen on by bringing 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><h3 class="title"><a name="idm46789024546816"></a>4.2.Select data rate</h3></div></div></div><p> - Altus Metrum transmitters can be configured to operate at - lower data rates to improve transmission range. If you have - configured your device to do this, this menu item allows you - to change the receiver to match. - </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm46789024545424"></a>4.3.Change units</h3></div></div></div><p> - This toggles between metric and imperial units. - </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm46789024544272"></a>4.4.Load maps</h3></div></div></div><p> - Brings up a dialog allowing you to download offline map - tiles so that you can have maps available even if you have - no network connectivity at the launch site. - </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm46789024542928"></a>4.5.Map type</h3></div></div></div><p> - Displays a menu of map types and lets you select one. Hybrid - maps include satellite images with a roadmap - overlaid. Satellite maps dispense with the roadmap - overlay. Roadmap shows just the roads. Terrain includes - roads along with shadows indicating changes in elevation, - and other geographical features. - </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm46789024541440"></a>4.6.Toggle Online/Offline maps</h3></div></div></div><p> - Switches between online and offline maps. Online maps will - show a 'move to current position' icon in the upper right - corner, while offline maps will have copyright information - all over the map. Otherwise, they're pretty similar. - </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm46789024540032"></a>4.7.Select Tracker</h3></div></div></div><p> - Switches the information displays to show data for a - different transmitting device. The map will always show all - of the devices in view. Trackers are shown and selected by - serial number, so make sure you note the serial number of - devices in each airframe. - </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm46789024538592"></a>4.8.Delete Track</h3></div></div></div><p> - Deletes all information about a transmitting device. - </p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idm46789024537232"></a>5.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="idm46789024535920"></a>5.1.Pad</h3></div></div></div><p> - The '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><p> - When the pad tab is selected, the voice responses will - include status changes to the igniters and GPS reception, - letting you know if the rocket is still ready for launch. - </p><div class="variablelist"><dl class="variablelist"><dt><span class="term">Battery</span></dt><dd><p> - This indicates whether the Li-Po battery - powering the transmitter 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">Receiver Battery</span></dt><dd><p> - This indicates whether the Li-Po battery - powering the TeleBT 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">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 and TeleMega can store multiple - flights, depending on the configured maximum flight - log size. TeleGPS logs data continuously. 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><dt><span class="term">Apogee Igniter</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</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">Igniter A-D</span></dt><dd><p> - This indicates whether the indicated additional pyro - channel 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></dl></div><p> - The Pad tab also shows the location of the Android device. - </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm46789024518464"></a>5.2.Flight</h3></div></div></div><p> - The 'Flight' tab shows information used to evaluate and spot - a rocket while in flight. It displays speed and height data - to monitor the health of the rocket, along with elevation, - range and bearing to help locate the rocket in the sky. - </p><p> - While the Flight tab is displayed, the voice announcements - will include current speed, height, elevation and bearing - information. - </p><div class="variablelist"><dl class="variablelist"><dt><span class="term">Speed</span></dt><dd><p> - Shows current vertical speed. During descent, the - speed values are averaged over a fairly long time to - try and make them steadier. - </p></dd><dt><span class="term">Height</span></dt><dd><p> - Shows the current height above the launch pad. - </p></dd><dt><span class="term">Max Speed</span></dt><dd><p> - Shows the maximum vertical speed seen during the flight. - </p></dd><dt><span class="term">Max Height</span></dt><dd><p> - Shows the maximum height above launch pad. - </p></dd><dt><span class="term">Elevation</span></dt><dd><p> - This is the angle above the horizon from the android - devices current position. - </p></dd><dt><span class="term">Range</span></dt><dd><p> - The total distance from the android device to the - rocket, including both ground distance and - difference in altitude. Use this to gauge how large - the rocket is likely to appear in the sky. - </p></dd><dt><span class="term">Bearing</span></dt><dd><p> - This is the aziumuth from true north for the rocket - from the android device. Use this in combination - with the Elevation value to help locate the rocket - in the sky, or at least to help point the antenna in - the general direction. This is provided in both - degrees and a compass point (like West South - West). You'll want to know which direction is true - north before launching your rocket. - </p></dd><dt><span class="term">Ground Distance</span></dt><dd><p> - This shows the distance across the ground to the - lat/lon where the rocket is located. Use this to - estimate what is currently under the rocket. - </p></dd><dt><span class="term">Latitude/Longitude</span></dt><dd><p> - Displays the last known location of the rocket. - </p></dd><dt><span class="term">Apogee Igniter</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</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></dl></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm46789024497344"></a>5.3.Recover</h3></div></div></div><p> - The 'Recover' tab shows information used while recovering the - rocket on the ground after flight. - </p><p> - While the Recover tab is displayed, the voice announcements - will include distance along with either bearing or - direction, depending on whether you are moving. - </p><div class="variablelist"><dl class="variablelist"><dt><span class="term">Bearing</span></dt><dd><p> - This is the aziumuth from true north for the rocket - from the android device. Use this in combination - with the Elevation value to help locate the rocket - in the sky, or at least to help point the antenna in - the general direction. This is provided in both - degrees and a compass point (like West South - West). You'll want to know which direction is true - north before launching your rocket. - </p></dd><dt><span class="term">Direction</span></dt><dd><p> - When you are in motion, this provides the angle from - your current direction of motion towards the rocket. - </p></dd><dt><span class="term">Distance</span></dt><dd><p> - Distance over the ground to the rocket. - </p></dd><dt><span class="term">Tar Lat/Tar Lon</span></dt><dd><p> - Displays the last known location of the rocket. - </p></dd><dt><span class="term">My Lat/My Lon</span></dt><dd><p> - Displays the location of the Android device. - </p></dd><dt><span class="term">Max Height</span></dt><dd><p> - Shows the maximum height above launch pad. - </p></dd><dt><span class="term">Max Speed</span></dt><dd><p> - Shows the maximum vertical speed seen during the flight. - </p></dd><dt><span class="term">Max Accel</span></dt><dd><p> - Shows the maximum vertical acceleration seen during the flight. - </p></dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm46789024482000"></a>5.4.Map</h3></div></div></div><p> - The 'Map' tab shows a map of the area around the rocket - being tracked along with information needed to recover it. - </p><p> - On the map itself, icons showing the location of the android - device along with the last known location of each tracker. A - blue line is drawn from the android device location to the - currently selected tracker. - </p><p> - Below the map, the distance and either bearing or direction - along with the lat/lon of the target and the android device - are shown - </p><p> - The Map tab provides the same voice announcements as the - Recover tab. - </p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idm46789024478928"></a>6.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, - 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="idm46789024477280"></a>Chapter8.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="#idm46789024476640">1. Being Legal</a></span></dt><dt><span class="section"><a href="#idm46789024474736">2. In the Rocket</a></span></dt><dt><span class="section"><a href="#idm46789024472208">3. On the Ground</a></span></dt><dt><span class="section"><a href="#idm46789024458400">4. Data Analysis</a></span></dt><dt><span class="section"><a href="#idm46789024455856">5. Future Plans</a></span></dt></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idm46789024476640"></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="idm46789024474736"></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="idm46789024472208"></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="idm46789024458400"></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="idm46789024455856"></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="idm46789024451664"></a>Chapter9.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="#idm46789024450208">1. Mounting the Altimeter</a></span></dt><dt><span class="section"><a href="#idm46789024445376">2. Dealing with the Antenna</a></span></dt><dt><span class="section"><a href="#idm46789024439280">3. Preserving GPS Reception</a></span></dt><dt><span class="section"><a href="#idm46789024434496">4. Radio Frequency Interference</a></span></dt><dt><span class="section"><a href="#idm46789024426928">5. The Barometric Sensor</a></span></dt><dt><span class="section"><a href="#idm46789024424128">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="idm46789024450208"></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="idm46789024445376"></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="idm46789024439280"></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="idm46789024434496"></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="idm46789024426928"></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="idm46789024424128"></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="idm46789024420960"></a>Chapter10.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="#idm46789024416880">1. - Updating TeleMega, TeleMetrum v2, EasyMega, EasyMini or - TeleDongle v3 Firmware - </a></span></dt><dd><dl><dt><span class="section"><a href="#idm46789024407744">1.1. Recovering From Self-Flashing Failure</a></span></dt></dl></dd><dt><span class="section"><a href="#idm46789024387392">2. Pair Programming</a></span></dt><dt><span class="section"><a href="#idm46789024385936">3. Updating TeleMetrum v1.x Firmware</a></span></dt><dt><span class="section"><a href="#idm46789024372672">4. Updating TeleMini Firmware</a></span></dt><dt><span class="section"><a href="#idm46789024359056">5. Updating TeleDongle v0.2 Firmware</a></span></dt></dl></div><p> - TeleMega, TeleMetrum v2, EasyMega, EasyMini and TeleDongle v3 - are all programmed directly over their USB connectors (self - programming). TeleMetrum v1, TeleMini and TeleDongle v0.2 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 v0.2, 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="idm46789024416880"></a>1. - Updating TeleMega, TeleMetrum v2, EasyMega, EasyMini or - TeleDongle v3 Firmware - </h2></div></div></div><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p> - Attach a battery if necessary 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' or 'Configure Groundstation' item to check over - the configuration. - </p></li></ol></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm46789024407744"></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><dt><span class="term">TeleDongle v3</span></dt><dd><p> - Connect pin 32 on the CPU to ground. Pin 32 is closest - to the USB wires on the row of pins towards the center - of the board. Ground is available on the capacitor - next to it, on the end towards the USB wires. - </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="idm46789024387392"></a>2.Pair Programming</h2></div></div></div><p> - The big concept to understand is that you have to use a - TeleMetrum v1.0, TeleBT v1.0 or TeleDongle v0.2 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="idm46789024385936"></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 v0.2 or TeleBT v1.0 - 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 v0.2 or TeleBT v1.0, 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 v0.2 or TeleBT v1.0 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 v0.2 or TeleBT v1.0 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="idm46789024372672"></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 v0.2 or TeleBT v1.0 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 v0.2 or TeleBT v1.0, 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 v0.2 or TeleBT v1.0 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 v0.2 or TeleBT v1.0 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="idm46789024359056"></a>5.Updating TeleDongle v0.2 Firmware</h2></div></div></div><p> - Updating TeleDongle v0.2 firmware is just like updating - TeleMetrum v1.x or TeleMini - firmware, but you use either a TeleMetrum v1.x, TeleDongle - v0.2 or TeleBT v1.0 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 - v1.x, TeleDongle v0.2 or TeleBT v1.0. - </p></li><li class="listitem"><p> - Take the 2 screws out of the TeleDongle v0.2 or TeleBT v1.0 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 v0.2. - 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 v1.x 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 v0.2, 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 v0.2 - 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 v0.2 with new firmware, showing a progress bar. - </p></li><li class="listitem"><p> - Confirm that the TeleDongle v0.2 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 v0.2. - </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="idm46789024342288"></a>Chapter11.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="#idm46789024341648">1. - TeleMega Specifications - </a></span></dt><dt><span class="section"><a href="#idm46789024330176">2. - EasyMega Specifications - </a></span></dt><dt><span class="section"><a href="#idm46789024320432">3. - TeleMetrum v2 Specifications - </a></span></dt><dt><span class="section"><a href="#idm46789024309872">4. TeleMetrum v1 Specifications</a></span></dt><dt><span class="section"><a href="#idm46789024299312">5. - TeleMini v2.0 Specifications - </a></span></dt><dt><span class="section"><a href="#idm46789024290480">6. - TeleMini v1.0 Specifications - </a></span></dt><dt><span class="section"><a href="#idm46789024281680">7. - EasyMini Specifications - </a></span></dt></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idm46789024341648"></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="idm46789024330176"></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="idm46789024320432"></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="idm46789024309872"></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="idm46789024299312"></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="idm46789024290480"></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="idm46789024281680"></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="idm46789024273568"></a>Chapter12.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="idm46789024264720"></a>AppendixA.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="idm46789024241856"></a>AppendixB.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="#idm46789024240688">1. TeleMega template</a></span></dt><dt><span class="section"><a href="#idm46789024224000">2. EasyMega template</a></span></dt><dt><span class="section"><a href="#idm46789024219616">3. TeleMetrum template</a></span></dt><dt><span class="section"><a href="#idm46789024215232">4. TeleMini v2/EasyMini template</a></span></dt><dt><span class="section"><a href="#idm46789024210832">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="idm46789024240688"></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="idm46789024224000"></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="idm46789024219616"></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="idm46789024215232"></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="idm46789024210832"></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="idm46789024206320"></a>AppendixC.Calibration</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idm46789024204768">1. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idm46789024200224">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="idm46789024204768"></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="idm46789024200224"></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="idm46789024194544"></a>AppendixD.Igniter Current</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idm46789024193280">1. Current Products</a></span></dt><dt><span class="section"><a href="#idm46789024189840">2. Version 1 Products</a></span></dt></dl></div><p> - The question "how much igniter current can Altus Metrum products - handle?" comes up fairly frequently. The short answer is "more than - you're likely to need", the remainder of this appendix provides a - longer answer. - </p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idm46789024193280"></a>1.Current Products</h2></div></div></div><p> - The FET switches we're using on all of our current products that - have pyro channels are the Vishay Siliconix Si7232DN. These parts - have exceptionally low Rds(on) values, better than 0.02 ohms! That - means they aren't making a lot of heat... and the limit on current - is "package limited", meaning it's all about how much you can heat - the die before something breaks. - </p><p> - Cutting to the chase, the Si7232DN specs are 25 amps <span class="emphasis"><em>continuous</em></span> at - 20V at a temperature of 25C. In pulsed mode, they're rated for 40A. - However, those specs are a little mis-leading because it really is - all about the heat generated... you can get something like 85A - through one briefly. Note that a typical commercial e-match only - needed about 13 microseconds to fire in tests on my bench a couple - years ago! - </p><p> - So a great plan is to use something like an e-match as the initiator - and build up pyrogen(s) as required to actually light what you're - trying to light... But if you want to use a high-current igniter, - we can probably handle it! - </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idm46789024189840"></a>2.Version 1 Products</h2></div></div></div><p> - The FET switches used on TeleMetrum v1 and TeleMini v1 products - were Fairchild FDS9926A. The Rds(on) values under our operating - conditions are on the order of 0.04 ohms. These parts were rated - for a continuous current-carrying capacity of 6.5A, and a pulsed - current capacity of 20A. - </p><p> - As with the more modern parts, the real limit is based on the heat - generated in the part during the firing interval. So, while the - specs on these parts aren't as good as the ones we use on current - products, they were still great, and we never had a complaint about - current carrying capacity with any of our v1 boards. - </p></div></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a name="idm46789024187504"></a>AppendixE.Release Notes</h1></div></div></div><div class="simplesect"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idm46789024186864"></a>Version 1.6.1</h2></div></div></div><p> - Version 1.6.1 includes support for our updated TeleBT v3.0 - product and bug fixes in in the flight software for all our boards - and ground station interfaces. - </p><p> - AltOS New Features - </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p> - Add support for TeleBT v3.0 boards. - </p></li><li class="listitem"><p> - Add support for uncompressed APRS data, providing support - for older APRS receivers. Uncompressed APRS data is less - precise, takes more bandwidth and doesn't have integrated - altitude data. - </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> - Make TeleDongle and TeleBT more tolerant of data rate - variations from transmitting devices. - </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> - Add map to Monitor Idle display. It's nice to be able to - verify that maps are working, instead of needing to use - Monitor Flight. - </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> - Fix frequency configuration to round values instead of - truncate them, avoiding a common 1kHz error in the setting. - </p></li><li class="listitem"><p> - Turn the Windows stub into a more useful program that can - launch the application with parameters so that file manager - icons work more reliably. - </p></li><li class="listitem"><p> - Force KML export to use a C locale so that numbers are - formatted with '.' instead of ',' for a decimal separator in - non-US locales. - </p></li><li class="listitem"><p> - Preload map tiles based on distance rather than number of - tiles; this means you get the same resolution covering the - entire area, rather than having high resolution near the - center and low resolution further away. - </p></li><li class="listitem"><p> - Allow configuration of frequency and callsign in Monitor - Idle mode. - </p></li><li class="listitem"><p> - Fix layout weirdness when resizing windows on - Windows. Windows shouldn't have giant blank spaces around - the useful content anymore. - </p></li><li class="listitem"><p> - Fix layout weirdness when resizing windows on - Windows. Windows shouldn't have giant blank spaces around - the useful content anymore. - </p></li><li class="listitem"><p> - Use a longer filter for descent speed values. This should - provide something more useful on the display, although it - will take longer to respond to changes now. - </p></li><li class="listitem"><p> - Make Replay Flight run in realtime again. It had been set to - run at 10x speed by mistake. - </p></li></ul></div><p> - </p><p> - AltosDroid New Features - </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p> - Add offline map support using mapping code from AltosUI. - </p></li><li class="listitem"><p> - Support TeleDongle (and TeleBT via USB) on devices - supporting USB On-The-Go. - </p></li><li class="listitem"><p> - Display additional TeleMega pyro channel status in Pad tab. - </p></li><li class="listitem"><p> - Switch between metric and imperial units. - </p></li><li class="listitem"><p> - Monitor TeleBT battery voltage. - </p></li><li class="listitem"><p> - Track multiple devices at the same time, selecting between - them with a menu or using the map. - </p></li><li class="listitem"><p> - Add hybrid, satellite and terrain map types. - </p></li></ul></div><p> - </p><p> - AltosDroid Fixes - </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p> - Use standard Android display conventions so that a menu - button is available in the application title bar. - </p></li><li class="listitem"><p> - Adjust layout to work on large and small screens; shrinking - the go/no-go lights in smaller environments to try and make - everything visible. - </p></li><li class="listitem"><p> - Make voice announcements depend on current tab. - </p></li><li class="listitem"><p> - Compute adjustment to current travel direction while in - motion towards rocket. - </p></li></ul></div><p> - </p></div><div class="simplesect"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idm46789024185264"></a>Version 1.6</h2></div></div></div><p> - Version 1.6 includes support for our updated TeleDongle v3.0 - product and bug fixes in in the flight software for all our boards - and ground station interfaces. - </p><p> - AltOS New Features - </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p> - Add support for TeleDongle v3.0 boards. - </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> - Don't beep out the continuity twice by accident in idle mode. - If the battery voltage report takes longer than the initialiation - sequence, the igniter continuity would get reported twice. - </p></li><li class="listitem"><p> - Record all 32 bits of gyro calibration data in TeleMega and - EasyMega log files. This fixes computation of the gyro rates - in AltosUI. - </p></li><li class="listitem"><p> - Change TeleDongle LED usage. Green LED flashes when valid - packet is received. Red LED flashes when invalid packet is - received. - </p></li><li class="listitem"><p> - Replace LPC11U14 SPI driver with non-interrupt version. The - interrupt code would occasionally wedge on long transfers - if interrupts were blocked for too long. This affects all - released TeleGPS products; if you have a TeleGPS device, - you'll want to reflash the firmware. - </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> - Compute tilt angle from TeleMega and EasyMega log - files. This duplicates the quaternion-based angle tracking - code from the flight firmware inside the ground station - software so that post-flight analysis can include evaluation - of the tilt angle. - </p></li><li class="listitem"><p> - Shows the tool button window when starting with a data file - specified. This means that opening a data file from the file - manager will now bring up the main window to let you operate - the whole 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> - Show the 'Connecting' dialog when using Monitor Idle. Lets - you cancel the Monitor Idle startup when connecting over the - radio link. - </p></li><li class="listitem"><p> - Make 'Monitor Idle' work for TeleGPS devices when connected - over USB. It's nice for testing without needing to broadcast - over the radio. - </p></li><li class="listitem"><p> - Use different Windows API to discover USB devices. This - works better on my Windows 7 box, and will be used if the - older API fails to provide the necessary information. - </p></li><li class="listitem"><p> - Look in more places in the registry to try and identify the - installed Java version on Windows. If you install the - default 32-bit version of Windows on a 64-bit OS, the Java - registry information is hiding \SOFTWARE\Wow6432Node for - some reason. - </p></li><li class="listitem"><p> - Fix file association on Windows by searching for the - javaw.exe program instead of assuming it is in - %SYSTEMROOT%. This makes double-clicking on Altus Metrum - data files in the file manager work correctly. - </p></li><li class="listitem"><p> - When replaying a file, put 'done' in the Age field when we - reach the end of the file, instead of continuing to count forever. - </p></li><li class="listitem"><p> - In the Scan Channels code, wait for five seconds if we see - any packet. This is needed because AltOS now sends the - callsign, serial number and flight number only once every - five seconds these days. - </p></li><li class="listitem"><p> - In the Scan Channels code, reset pending flight state - information each time we change channels. This avoids having - flight computers appear on multiple frequencies by accident. - </p></li></ul></div><p> - </p></div><div class="simplesect"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idm46789024183664"></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="idm46789024182160"></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="idm46789024180656"></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="idm46789024179152"></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="idm46789024177648"></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="idm46789024176144"></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="idm46789024174640"></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="idm46789024173136"></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="idm46789024171632"></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="idm46789024170128"></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="idm46789024168624"></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="idm46789024167120"></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="idm46789024165616"></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="idm46789024164112"></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="idm46789024162608"></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> +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>The Altus Metrum System</title><link rel="stylesheet" type="text/css" href="am.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.78.1" /></head><body><div xml:lang="en" class="book" lang="en"><div class="titlepage"><div><div><h1 class="title"><a id="idm45058136831984"></a>The Altus Metrum System</h1></div><div><h2 class="subtitle">An Owner's Manual for Altus Metrum Rocketry Electronics</h2></div><div><h3 class="corpauthor"> + <span class="inlinemediaobject"><img src="altusmetrum-oneline.svg" width="360" /></span> +</h3></div><div><div class="author"><h3 class="author"><span class="firstname">Bdale</span> <span class="surname">Garbee</span></h3><code class="email"><<a class="email" href="mailto:bdale@gag.com">bdale@gag.com</a>></code></div></div><div><div class="author"><h3 class="author"><span class="firstname">Keith</span> <span class="surname">Packard</span></h3><code class="email"><<a class="email" href="mailto:keithp@keithp.com">keithp@keithp.com</a>></code></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 © 2016 Bdale Garbee and Keith Packard</p></div><div><div class="legalnotice"><a id="idm45058136014592"></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><a href="altusmetrum-revhistory.html">Revision History</a></div></div><hr /></div><div class="dedication"><div class="titlepage"><div><div><h1 class="title"><a id="_acknowledgments"></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="blockquote"><blockquote class="blockquote"><div class="literallayout"><p>Bdale Garbee, KB0G<br /> +NAR #87103, TRA #12201</p></div></blockquote></div><div class="blockquote"><blockquote class="blockquote"><div class="literallayout"><p>Keith Packard, KD7SQG<br /> +NAR #88757, TRA #12200</p></div></blockquote></div></div><div class="toc"><p><strong>Table of Contents</strong></p><dl class="toc"><dt><span class="chapter"><a href="#_introduction_and_overview">1. Introduction and Overview</a></span></dt><dt><span class="chapter"><a href="#_getting_started">2. Getting Started</a></span></dt><dd><dl><dt><span class="section"><a href="#_batteries">2.1. Batteries</a></span></dt><dt><span class="section"><a href="#_ground_station_hardware">2.2. Ground Station Hardware</a></span></dt><dt><span class="section"><a href="#_linux_mac_windows_ground_station_software">2.3. Linux/Mac/Windows Ground Station Software</a></span></dt><dt><span class="section"><a href="#_android_ground_station_software">2.4. Android Ground Station Software</a></span></dt></dl></dd><dt><span class="chapter"><a href="#_using_altus_metrum_hardware">3. Using Altus Metrum Hardware</a></span></dt><dd><dl><dt><span class="section"><a href="#_wiring_and_electrical_interference">3.1. Wiring and Electrical Interference</a></span></dt><dt><span class="section"><a href="#_hooking_up_lithium_polymer_batteries">3.2. Hooking Up Lithium Polymer Batteries</a></span></dt><dt><span class="section"><a href="#_hooking_up_pyro_charges">3.3. Hooking Up Pyro Charges</a></span></dt><dt><span class="section"><a href="#_hooking_up_a_power_switch">3.4. Hooking Up a Power Switch</a></span></dt><dt><span class="section"><a href="#_understanding_beeps">3.5. Understanding Beeps</a></span></dt><dt><span class="section"><a href="#_turning_on_the_power">3.6. Turning On the Power</a></span></dt><dt><span class="section"><a href="#_using_an_external_active_switch_circuit">3.7. Using an External Active Switch Circuit</a></span></dt><dt><span class="section"><a href="#_using_a_separate_pyro_battery">3.8. Using a Separate Pyro Battery</a></span></dt><dt><span class="section"><a href="#_using_a_different_kind_of_battery">3.9. Using a Different Kind of Battery</a></span></dt></dl></dd><dt><span class="chapter"><a href="#_telemetrum">4. TeleMetrum</a></span></dt><dd><dl><dt><span class="section"><a href="#_telemetrum_screw_terminals">4.1. TeleMetrum Screw Terminals</a></span></dt><dt><span class="section"><a href="#_using_a_separate_pyro_battery_with_telemetrum">4.2. Using a Separate Pyro Battery with TeleMetrum</a></span></dt><dt><span class="section"><a href="#_using_an_active_switch_with_telemetrum">4.3. Using an Active Switch with TeleMetrum</a></span></dt></dl></dd><dt><span class="chapter"><a href="#_telemini_v1_0">5. TeleMini v1.0</a></span></dt><dd><dl><dt><span class="section"><a href="#_telemini_v1_0_screw_terminals">5.1. TeleMini v1.0 Screw Terminals</a></span></dt><dt><span class="section"><a href="#_using_a_separate_pyro_battery_with_telemini_v1_0">5.2. Using a Separate Pyro Battery with TeleMini v1.0</a></span></dt><dt><span class="section"><a href="#_using_an_active_switch_with_telemini_v1_0">5.3. Using an Active Switch with TeleMini v1.0</a></span></dt></dl></dd><dt><span class="chapter"><a href="#_easymini">6. EasyMini</a></span></dt><dd><dl><dt><span class="section"><a href="#_easymini_screw_terminals">6.1. EasyMini Screw Terminals</a></span></dt><dt><span class="section"><a href="#_connecting_a_battery_to_easymini">6.2. Connecting A Battery To EasyMini</a></span></dt><dt><span class="section"><a href="#_charging_lithium_batteries">6.3. Charging Lithium Batteries</a></span></dt><dt><span class="section"><a href="#_using_a_separate_pyro_battery_with_easymini">6.4. Using a Separate Pyro Battery with EasyMini</a></span></dt><dt><span class="section"><a href="#_using_an_active_switch_with_easymini">6.5. Using an Active Switch with EasyMini</a></span></dt></dl></dd><dt><span class="chapter"><a href="#_telemega">7. TeleMega</a></span></dt><dd><dl><dt><span class="section"><a href="#_telemega_screw_terminals">7.1. TeleMega Screw Terminals</a></span></dt><dt><span class="section"><a href="#_using_a_separate_pyro_battery_with_telemega">7.2. Using a Separate Pyro Battery with TeleMega</a></span></dt><dt><span class="section"><a href="#_using_only_one_battery_with_telemega">7.3. Using Only One Battery With TeleMega</a></span></dt><dt><span class="section"><a href="#_using_an_active_switch_with_telemega">7.4. Using an Active Switch with TeleMega</a></span></dt></dl></dd><dt><span class="chapter"><a href="#_easymega">8. EasyMega</a></span></dt><dd><dl><dt><span class="section"><a href="#_easymega_screw_terminals">8.1. EasyMega Screw Terminals</a></span></dt><dt><span class="section"><a href="#_using_a_separate_pyro_battery_with_easymega">8.2. Using a Separate Pyro Battery with EasyMega</a></span></dt><dt><span class="section"><a href="#_using_only_one_battery_with_easymega">8.3. Using Only One Battery With EasyMega</a></span></dt><dt><span class="section"><a href="#_using_an_active_switch_with_easymega">8.4. Using an Active Switch with EasyMega</a></span></dt></dl></dd><dt><span class="chapter"><a href="#_installation">9. Installation</a></span></dt><dt><span class="chapter"><a href="#_using_altus_metrum_products">10. Using Altus Metrum Products</a></span></dt><dd><dl><dt><span class="section"><a href="#_being_legal">10.1. Being Legal</a></span></dt><dt><span class="section"><a href="#_in_the_rocket">10.2. In the Rocket</a></span></dt><dt><span class="section"><a href="#_on_the_ground">10.3. On the Ground</a></span></dt><dt><span class="section"><a href="#_data_analysis">10.4. Data Analysis</a></span></dt><dt><span class="section"><a href="#_future_plans">10.5. Future Plans</a></span></dt></dl></dd><dt><span class="chapter"><a href="#_altosui">11. AltosUI</a></span></dt><dd><dl><dt><span class="section"><a href="#_monitor_flight">11.1. Monitor Flight</a></span></dt><dd><dl><dt><span class="section"><a href="#_launch_pad">11.1.1. Launch Pad</a></span></dt><dt><span class="section"><a href="#_ascent">11.1.2. Ascent</a></span></dt><dt><span class="section"><a href="#_descent">11.1.3. Descent</a></span></dt><dt><span class="section"><a href="#_landed">11.1.4. Landed</a></span></dt><dt><span class="section"><a href="#_table">11.1.5. Table</a></span></dt><dt><span class="section"><a href="#_site_map">11.1.6. Site Map</a></span></dt><dt><span class="section"><a href="#_igniter">11.1.7. Igniter</a></span></dt></dl></dd><dt><span class="section"><a href="#_save_flight_data">11.2. Save Flight Data</a></span></dt><dt><span class="section"><a href="#_replay_flight">11.3. Replay Flight</a></span></dt><dt><span class="section"><a href="#_graph_data">11.4. Graph Data</a></span></dt><dd><dl><dt><span class="section"><a href="#_flight_graph">11.4.1. Flight Graph</a></span></dt><dt><span class="section"><a href="#_configure_graph">11.4.2. Configure Graph</a></span></dt><dt><span class="section"><a href="#_flight_statistics">11.4.3. Flight Statistics</a></span></dt><dt><span class="section"><a href="#_map">11.4.4. Map</a></span></dt></dl></dd><dt><span class="section"><a href="#_export_data">11.5. Export Data</a></span></dt><dd><dl><dt><span class="section"><a href="#_comma_separated_value_format">11.5.1. Comma Separated Value Format</a></span></dt><dt><span class="section"><a href="#_keyhole_markup_language_for_google_earth">11.5.2. Keyhole Markup Language (for Google Earth)</a></span></dt></dl></dd><dt><span class="section"><a href="#_configure_altimeter">11.6. Configure Altimeter</a></span></dt><dd><dl><dt><span class="section"><a href="#_main_deploy_altitude">11.6.1. Main Deploy Altitude</a></span></dt><dt><span class="section"><a href="#_apogee_delay">11.6.2. Apogee Delay</a></span></dt><dt><span class="section"><a href="#_apogee_lockout">11.6.3. Apogee Lockout</a></span></dt><dt><span class="section"><a href="#_frequency">11.6.4. Frequency</a></span></dt><dt><span class="section"><a href="#_rf_calibration">11.6.5. RF Calibration</a></span></dt><dt><span class="section"><a href="#_telemetry_rdf_aprs_enable">11.6.6. Telemetry/RDF/APRS Enable</a></span></dt><dt><span class="section"><a href="#_telemetry_baud_rate">11.6.7. Telemetry baud rate</a></span></dt><dt><span class="section"><a href="#_aprs_interval">11.6.8. APRS Interval</a></span></dt><dt><span class="section"><a href="#_aprs_ssid">11.6.9. APRS SSID</a></span></dt><dt><span class="section"><a href="#_aprs_format">11.6.10. APRS Format</a></span></dt><dt><span class="section"><a href="#_callsign">11.6.11. Callsign</a></span></dt><dt><span class="section"><a href="#_maximum_flight_log_size">11.6.12. Maximum Flight Log Size</a></span></dt><dt><span class="section"><a href="#_ignitor_firing_mode">11.6.13. Ignitor Firing Mode</a></span></dt><dt><span class="section"><a href="#_pad_orientation">11.6.14. Pad Orientation</a></span></dt><dt><span class="section"><a href="#_beeper_frequency">11.6.15. Beeper Frequency</a></span></dt><dt><span class="section"><a href="#_logging_trigger_motion">11.6.16. Logging Trigger Motion</a></span></dt><dt><span class="section"><a href="#_position_reporting_interval">11.6.17. Position Reporting Interval</a></span></dt><dt><span class="section"><a href="#_configure_pyro_channels">11.6.18. Configure Pyro Channels</a></span></dt></dl></dd><dt><span class="section"><a href="#_configure_altosui">11.7. Configure AltosUI</a></span></dt><dd><dl><dt><span class="section"><a href="#_voice_settings">11.7.1. Voice Settings</a></span></dt><dt><span class="section"><a href="#_log_directory">11.7.2. Log Directory</a></span></dt><dt><span class="section"><a href="#_callsign_2">11.7.3. Callsign</a></span></dt><dt><span class="section"><a href="#_imperial_units">11.7.4. Imperial Units</a></span></dt><dt><span class="section"><a href="#_serial_debug">11.7.5. Serial Debug</a></span></dt><dt><span class="section"><a href="#_font_size">11.7.6. Font size</a></span></dt><dt><span class="section"><a href="#_look_amp_feel">11.7.7. Look & feel</a></span></dt><dt><span class="section"><a href="#_menu_position">11.7.8. Menu position</a></span></dt><dt><span class="section"><a href="#_map_cache_size">11.7.9. Map Cache Size</a></span></dt><dt><span class="section"><a href="#_manage_frequencies">11.7.10. Manage Frequencies</a></span></dt></dl></dd><dt><span class="section"><a href="#_configure_groundstation">11.8. Configure Groundstation</a></span></dt><dd><dl><dt><span class="section"><a href="#_frequency_2">11.8.1. Frequency</a></span></dt><dt><span class="section"><a href="#_rf_calibration_2">11.8.2. RF Calibration</a></span></dt><dt><span class="section"><a href="#_telemetry_rate">11.8.3. Telemetry Rate</a></span></dt></dl></dd><dt><span class="section"><a href="#_flash_image">11.9. Flash Image</a></span></dt><dt><span class="section"><a href="#_fire_igniter">11.10. Fire Igniter</a></span></dt><dt><span class="section"><a href="#_scan_channels">11.11. Scan Channels</a></span></dt><dt><span class="section"><a href="#_load_maps">11.12. Load Maps</a></span></dt><dt><span class="section"><a href="#_monitor_idle">11.13. Monitor Idle</a></span></dt></dl></dd><dt><span class="chapter"><a href="#_altosdroid">12. AltosDroid</a></span></dt><dd><dl><dt><span class="section"><a href="#_installing_altosdroid">12.1. Installing AltosDroid</a></span></dt><dt><span class="section"><a href="#_charging_telebt_battery">12.2. Charging TeleBT Battery</a></span></dt><dt><span class="section"><a href="#_connecting_to_telebt_over_bluetooth">12.3. Connecting to TeleBT over Bluetooth™</a></span></dt><dt><span class="section"><a href="#_connecting_to_teledongle_or_telebt_over_usb">12.4. Connecting to TeleDongle or TeleBT over USB</a></span></dt><dt><span class="section"><a href="#_configuring_altosdroid">12.5. Configuring AltosDroid</a></span></dt><dt><span class="section"><a href="#_altosdroid_flight_monitoring">12.6. AltosDroid Flight Monitoring</a></span></dt><dt><span class="section"><a href="#_pad">12.7. Pad</a></span></dt><dt><span class="section"><a href="#_flight">12.8. Flight</a></span></dt><dt><span class="section"><a href="#_recover">12.9. Recover</a></span></dt><dt><span class="section"><a href="#_map_2">12.10. Map</a></span></dt><dt><span class="section"><a href="#_downloading_flight_logs">12.11. Downloading Flight Logs</a></span></dt></dl></dd><dt><span class="appendix"><a href="#_system_operation">A. System Operation</a></span></dt><dd><dl><dt><span class="section"><a href="#_firmware_modes">A.1. Firmware Modes</a></span></dt><dt><span class="section"><a href="#_gps">A.2. GPS</a></span></dt><dt><span class="section"><a href="#_controlling_an_altimeter_over_the_radio_link">A.3. Controlling An Altimeter Over The Radio Link</a></span></dt><dt><span class="section"><a href="#_ground_testing">A.4. Ground Testing</a></span></dt><dt><span class="section"><a href="#_radio_link">A.5. Radio Link</a></span></dt><dt><span class="section"><a href="#_aprs">A.6. APRS</a></span></dt><dt><span class="section"><a href="#_configurable_parameters">A.7. Configurable Parameters</a></span></dt></dl></dd><dt><span class="appendix"><a href="#_handling_precautions">B. Handling Precautions</a></span></dt><dt><span class="appendix"><a href="#_updating_device_firmware">C. Updating Device Firmware</a></span></dt><dd><dl><dt><span class="section"><a href="#_updating_telemega_telemetrum_v2_easymega_easymini_or_teledongle_v3_firmware">C.1. Updating TeleMega, TeleMetrum v2, EasyMega, EasyMini or TeleDongle v3 Firmware</a></span></dt><dd><dl><dt><span class="section"><a href="#_recovering_from_self_flashing_failure">C.1.1. Recovering From Self-Flashing Failure</a></span></dt></dl></dd><dt><span class="section"><a href="#_pair_programming">C.2. Pair Programming</a></span></dt><dd><dl><dt><span class="section"><a href="#_updating_telemetrum_v1_x_firmware">C.2.1. Updating TeleMetrum v1.x Firmware</a></span></dt><dt><span class="section"><a href="#_updating_telemini_firmware">C.2.2. Updating TeleMini Firmware</a></span></dt><dt><span class="section"><a href="#_updating_teledongle_v0_2_firmware">C.2.3. Updating TeleDongle v0.2 Firmware</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href="#_flight_data_recording">D. Flight Data Recording</a></span></dt><dt><span class="appendix"><a href="#_altus_metrum_hardware_specifications">E. Altus Metrum Hardware Specifications</a></span></dt><dt><span class="appendix"><a href="#_release_notes">F. Release Notes</a></span></dt><dd><dl><dt><span class="section"><a href="#_release_notes_for_version_1_6_2">F.1. Release Notes for Version 1.6.2</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos">F.1.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_and_telegps_applications">F.1.2. AltosUI and TeleGPS Applications</a></span></dt><dt><span class="section"><a href="#_documentation">F.1.3. Documentation</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_6_1">F.2. Release Notes for Version 1.6.1</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_2">F.2.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_and_telegps_applications_2">F.2.2. AltosUI and TeleGPS Applications</a></span></dt><dt><span class="section"><a href="#_altosdroid_2">F.2.3. AltosDroid</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_6">F.3. Release Notes for Version 1.6</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_3">F.3.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_and_telegps_applications_3">F.3.2. AltosUI and TeleGPS Applications</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_5">F.4. Release Notes for Version 1.5</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_4">F.4.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_and_telegps_applications_4">F.4.2. AltosUI and TeleGPS Applications</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_4_2">F.5. Release Notes for Version 1.4.2</a></span></dt><dd><dl><dt><span class="section"><a href="#_altosui_and_telegps_applications_5">F.5.1. AltosUI and TeleGPS Applications</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_4_1">F.6. Release Notes for Version 1.4.1</a></span></dt><dd><dl><dt><span class="section"><a href="#_altosui_and_telegps_applications_6">F.6.1. AltosUI and TeleGPS Applications:</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_4">F.7. Release Notes for Version 1.4</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_5">F.7.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_application">F.7.2. AltosUI Application</a></span></dt><dt><span class="section"><a href="#_telegps_application">F.7.3. TeleGPS Application</a></span></dt><dt><span class="section"><a href="#_documentation_2">F.7.4. Documentation</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_3_2">F.8. Release Notes for Version 1.3.2</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_6">F.8.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_application_2">F.8.2. AltosUI Application</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_3_1">F.9. Release Notes for Version 1.3.1</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_7">F.9.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_application_3">F.9.2. AltosUI Application</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_3">F.10. Release Notes for Version 1.3</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_8">F.10.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_application_4">F.10.2. AltosUI Application</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_2_1">F.11. Release Notes for Version 1.2.1</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_9">F.11.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_application_5">F.11.2. AltosUI Application</a></span></dt><dt><span class="section"><a href="#_altosdroid_3">F.11.3. AltosDroid</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_2">F.12. Release Notes for Version 1.2</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_10">F.12.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_and_micropeak_application">F.12.2. AltosUI and MicroPeak Application</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_1">F.13. Release Notes for Version 1.1</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_11">F.13.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_2">F.13.2. AltosUI</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_1_2">F.14. Release Notes for Version 1.1</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_12">F.14.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_3">F.14.2. AltosUI</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_0_1">F.15. Release Notes for Version 1.0.1</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_13">F.15.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_application_6">F.15.2. AltosUI Application</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_0_9_2">F.16. Release Notes for Version 0.9.2</a></span></dt><dd><dl><dt><span class="section"><a href="#_altosui_4">F.16.1. AltosUI</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_0_9">F.17. Release Notes for Version 0.9</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_14">F.17.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_application_7">F.17.2. AltosUI Application</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_0_8">F.18. Release Notes for Version 0.8</a></span></dt><dd><dl><dt><span class="section"><a href="#_altosui_application_8">F.18.1. AltosUI Application:</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_0_7_1">F.19. Release Notes for Version 0.7.1</a></span></dt><dd><dl><dt><span class="section"><a href="#_altosui_application_9">F.19.1. AltosUI Application</a></span></dt></dl></dd></dl></dd></dl></div><div class="list-of-figures"><p><strong>List of Figures</strong></p><dl><dt>4.1. <a href="#idm45058137013184">TeleMetrum v2 Board</a></dt><dt>4.2. <a href="#idm45058131219712">TeleMetrum v1 Board</a></dt><dt>5.1. <a href="#idm45058131173360">TeleMini v1.0 Board</a></dt><dt>6.1. <a href="#idm45058131130096">EasyMini Board</a></dt><dt>7.1. <a href="#idm45058131075552">TeleMega Board</a></dt><dt>8.1. <a href="#idm45058130988752">EasyMega Board</a></dt><dt>11.1. <a href="#idm45058130868928">AltosUI Main Window</a></dt><dt>11.2. <a href="#idm45058130863296">Device Selection Dialog</a></dt><dt>11.3. <a href="#idm45058130849200">Monitor Flight Launch Pad View</a></dt><dt>11.4. <a href="#idm45058130830016">Monitor Flight Ascent View</a></dt><dt>11.5. <a href="#idm45058130823280">Monitor Flight Descent View</a></dt><dt>11.6. <a href="#idm45058130815168">Monitor Flight Landed View</a></dt><dt>11.7. <a href="#idm45058130806592">Monitor Flight Table View</a></dt><dt>11.8. <a href="#idm45058130801760">Monitor Flight Site Map View</a></dt><dt>11.9. <a href="#idm45058130793680">Monitor Flight Additional Igniter View</a></dt><dt>11.10. <a href="#idm45058130777360">Flight Data Graph</a></dt><dt>11.11. <a href="#idm45058130771968">Flight Graph Configuration</a></dt><dt>11.12. <a href="#idm45058130767456">Flight Statistics</a></dt><dt>11.13. <a href="#idm45058130763168">Flight Map</a></dt><dt>11.14. <a href="#idm45058130751680">Altimeter Configuration</a></dt><dt>11.15. <a href="#idm45058130694496">Additional Pyro Channel Configuration</a></dt><dt>11.16. <a href="#idm45058130656608">Configure AltosUI Dialog</a></dt><dt>11.17. <a href="#idm45058130628688">Configure Groundstation Dialog</a></dt><dt>11.18. <a href="#idm45058130608144">Fire Igniter Window</a></dt><dt>11.19. <a href="#idm45058130598992">Scan Channels Window</a></dt><dt>11.20. <a href="#idm45058130594176">Load Maps Window</a></dt><dt>11.21. <a href="#idm45058130577728">Monitor Idle Window</a></dt></dl></div><div class="list-of-tables"><p><strong>List of Tables</strong></p><dl><dt>3.1. <a href="#idm45058131365520">AltOS Modes</a></dt><dt>3.2. <a href="#idm45058131311360">Pad/Idle Indications</a></dt><dt>3.3. <a href="#idm45058131285120">Pad Radio Indications</a></dt><dt>4.1. <a href="#idm45058131209152">TeleMetrum Screw Terminals</a></dt><dt>5.1. <a href="#idm45058131166752">TeleMini v1.0 Screw Terminals</a></dt><dt>6.1. <a href="#idm45058131124080">EasyMini Screw Terminals</a></dt><dt>7.1. <a href="#idm45058131066192">TeleMega Screw Terminals</a></dt><dt>8.1. <a href="#idm45058130983408">EasyMega Screw Terminals</a></dt><dt>A.1. <a href="#idm45058130419360">Altus Metrum APRS Comments</a></dt><dt>D.1. <a href="#idm45058130283472">Data Storage on Altus Metrum altimeters</a></dt><dt>E.1. <a href="#idm45058130237152">Altus Metrum Flight Computer Electronics</a></dt><dt>E.2. <a href="#idm45058130154144">Altus Metrum Flight Computer Mechanical Components</a></dt></dl></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="_introduction_and_overview"></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 v0.2 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. The latest version, TeleDongle +v3, has all new electronics with a higher performance radio +for improved range.</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 id="_getting_started"></a>Chapter 2. Getting Started</h1></div></div></div><p>The first thing to do after you open the box is to hook up a +battery and charge it if necessary.</p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_batteries"></a>2.1. Batteries</h2></div></div></div><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. +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 <a class="ulink" href="http://altusmetrum.org/LipoCharger" target="_top">LipoCharger</a>, 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 +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><div class="note" style="margin-left: 0; margin-right: 10%;"><h3 class="title">Note</h3><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></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_ground_station_hardware"></a>2.2. Ground Station Hardware</h2></div></div></div><p>There are two ground stations available, the TeleDongle USB to +RF interface and the TeleBT Bluetooth/USB to RF interface. If +you plug either of these 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></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_linux_mac_windows_ground_station_software"></a>2.3. Linux/Mac/Windows Ground Station Software</h2></div></div></div><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, Mac OSX. 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></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_android_ground_station_software"></a>2.4. Android Ground Station Software</h2></div></div></div><p>TeleBT can also connect to an Android device over +BlueTooth or USB. The +<a class="ulink" href="https://play.google.com/store/apps/details?id=org.altusmetrum.AltosDroid" target="_top">AltosDroid +Android application</a> is available from the +<a class="ulink" href="https://play.google.com" target="_top">Google Play system</a>.</p><p>You don’t need a data plan to use AltosDroid, but +without network access, you’ll want to download +offline map data before wandering away from the +network.</p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="_using_altus_metrum_hardware"></a>Chapter 3. Using Altus Metrum Hardware</h1></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><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_wiring_and_electrical_interference"></a>3.1. Wiring and Electrical Interference</h2></div></div></div><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><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_hooking_up_lithium_polymer_batteries"></a>3.2. Hooking Up Lithium Polymer Batteries</h2></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><div class="warning" style="margin-left: 0; margin-right: 10%;"><h3 class="title">Warning</h3><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><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_hooking_up_pyro_charges"></a>3.3. Hooking Up Pyro Charges</h2></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><h2 class="title" style="clear: both"><a id="_hooking_up_a_power_switch"></a>3.4. Hooking Up a Power Switch</h2></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><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_understanding_beeps"></a>3.5. Understanding Beeps</h2></div></div></div><p>Altus Metrum flight computers include a beeper to +provide information about the state of the system. +TeleMini doesn’t have room for a beeper, so instead it +uses an LED, which works the same, except for every +beep is replaced with the flash of the LED.</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 id="idm45058131365520"></a><p class="title"><strong>Table 3.1. AltOS Modes</strong></p><div class="table-contents"><table summary="AltOS Modes" cellpadding="4px" style="border-collapse: collapse;border-top: 1px solid #78079a; border-bottom: 1px solid #78079a; border-left: 1px solid #78079a; border-right: 1px solid #78079a; "><colgroup><col class="col_1" /><col class="col_2" /><col class="col_3" /><col class="col_4" /></colgroup><tbody><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Mode Name</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Abbreviation</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Beeps</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Description</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Startup</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>S</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>battery voltage in decivolts</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Calibrating sensors, detecting orientation.</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Idle</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>I</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>dit dit</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Ready to accept commands over USB +or radio link.</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Pad</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>P</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>dit dah dah dit</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Waiting for launch. Not listening for commands.</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Boost</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>B</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>dah dit dit dit</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Accelerating upwards.</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Fast</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>F</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>dit dit dah dit</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Decelerating, but moving faster than 200m/s.</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Coast</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>C</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>dah dit dah dit</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Decelerating, moving slower than 200m/s</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Drogue</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>D</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>dah dit dit</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Descending after apogee. Above main height.</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>M</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>dah dah</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Descending. Below main height.</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Landed</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>L</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>dit dah dit dit</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Stable altitude for at least ten seconds.</p></td></tr><tr><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>Sensor error</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>X</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>dah dit dit dah</p></td><td style="" align="left" valign="top"><p>Error detected during sensor calibration.</p></td></tr></tbody></table></div></div><br class="table-break" /><p>Here’s a summary of all of the Pad and Idle mode +indications. In Idle mode, you’ll hear one of these +just once after the two short dits indicating idle +mode. In Pad mode, after the dit dah dah dit +indicating Pad mode, you’ll hear these once every five +seconds.</p><div class="table"><a id="idm45058131311360"></a><p class="title"><strong>Table 3.2. Pad/Idle Indications</strong></p><div class="table-contents"><table summary="Pad/Idle Indications" cellpadding="4px" style="border-collapse: collapse;border-top: 1px solid #78079a; border-bottom: 1px solid #78079a; border-left: 1px solid #78079a; border-right: 1px solid #78079a; "><colgroup><col class="col_1" /><col class="col_2" /><col class="col_3" /></colgroup><thead><tr><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Name </th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Beeps </th><th style="border-bottom: 1px solid #78079a; " align="left" valign="top">Description</th></tr></thead><tbody><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Neither</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>brap</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>No continuity detected on either apogee or main igniters.</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>dit</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Continuity detected only on apogee igniter.</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>dit dit</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Continuity detected only on main igniter.</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Both</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>dit dit dit</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Continuity detected on both igniters.</p></td></tr><tr><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>Storage Full</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>warble</p></td><td style="" align="left" valign="top"><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><br class="table-break" /><p>For devices with a radio transmitter, in addition to +the digital and APRS telemetry signals, you can also +receive audio tones with a standard amateur +70cm FM receiver. While on the pad, you will hear +igniter status once every five seconds.</p><div class="table"><a id="idm45058131285120"></a><p class="title"><strong>Table 3.3. Pad Radio Indications</strong></p><div class="table-contents"><table summary="Pad Radio Indications" cellpadding="4px" style="border-collapse: collapse;border-top: 1px solid #78079a; border-bottom: 1px solid #78079a; border-left: 1px solid #78079a; border-right: 1px solid #78079a; "><colgroup><col class="col_1" /><col class="col_2" /><col class="col_3" /></colgroup><thead><tr><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Name </th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Beeps </th><th style="border-bottom: 1px solid #78079a; " align="left" valign="top">Description</th></tr></thead><tbody><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Neither</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>½ second tone</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>No continuity detected on either apogee or main igniters.</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>dit</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Continuity detected only on apogee igniter.</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>dit dit</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Continuity detected only on main igniter.</p></td></tr><tr><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>Both</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>dit dit dit</p></td><td style="" align="left" valign="top"><p>Continuity detected on both igniters.</p></td></tr></tbody></table></div></div><br class="table-break" /><p>During ascent, the tones will be muted to allow the +telemetry data to consume the full radio bandwidth.</p><p>During descent and after landing, a ½ second tone will +be transmitted every five seconds. This can be used to +find the rocket using RDF techniques when the signal +is too weak to receive GPS information via telemetry +or APRS.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_turning_on_the_power"></a>3.6. Turning On the Power</h2></div></div></div><p>Connect a battery and power switch and turn the switch +to "on". The flight computer will signal power on by +reporting the battery voltage and then perform an internal self +test and sensor calibration.</p><p>Once the self test and calibration are complete, there +are two modes that an Altus Metrum flight computer can +operate in:</p><div class="variablelist"><dl class="variablelist"><dt><span class="term"> +Flight/Pad +</span></dt><dd> +The flight computer is waiting to detect +launch and then fly the rocket. In this mode, the USB +link is +disabled, and the radio goes into transmit-only mode. +The only way to get out of this +mode is to power the flight computer down. +</dd><dt><span class="term"> +Idle +</span></dt><dd> +The flight computer is ready to communicate over USB +and in packet mode over the radio. +You can configure +the flight computer, download data or display +the current state. +</dd></dl></div><p>For flight computers with accelerometers (TeleMetrum, +EasyMega and TeleMega), the mode is selected by the +orientation of the board during the self test +interval. If the board is pointing upwards as if ready +to fly, it will enter Flight/Pad mode. Otherwise, it will +enter Idle mode.</p><p>For EasyMini, if the USB cable is connected to a +computer, it will enter Idle mode. Otherwise, it will +enter Flight/Pad mode.</p><p>For TeleMini v1.0, if a packet link is waiting to +connect when the device is powered on, it will enter +Idle mode, otherwise it will enter Flight/Pad mode.</p><p>You can see in <a class="xref" href="#_understanding_beeps" title="3.5. Understanding Beeps">Section 3.5, “Understanding Beeps”</a> +how to tell which mode the flight computer is in.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_using_an_external_active_switch_circuit"></a>3.7. Using an External Active Switch Circuit</h2></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. Then follow +the instructions that come with your active switch to +connect it up.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_using_a_separate_pyro_battery"></a>3.8. Using a Separate Pyro Battery</h2></div></div></div><p>As mentioned above in <a class="xref" href="#_hooking_up_pyro_charges" title="3.3. Hooking Up Pyro Charges">Section 3.3, “Hooking Up Pyro Charges”</a>, 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 for each flight computer will be found +in the section below for that flight computer.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_using_a_different_kind_of_battery"></a>3.9. Using a Different Kind of Battery</h2></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.</p><div class="warning" style="margin-left: 0; margin-right: 10%;"><h3 class="title">Warning</h3><p>TeleMega, EasyMega and TeleMetrum are only designed to +operate off a single-cell Lithium Polymer battery and +cannot be used with any other kind. Connecting a +different kind of battery to any of these will destroy +the board.</p></div></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="_telemetrum"></a>Chapter 4. TeleMetrum</h1></div></div></div><div class="figure"><a id="idm45058137013184"></a><p class="title"><strong>Figure 4.1. TeleMetrum v2 Board</strong></p><div class="figure-contents"><div class="mediaobject"><img src="telemetrum-v2.0-th.jpg" width="495" alt="telemetrum-v2.0-th.jpg" /></div></div></div><br class="figure-break" /><div class="figure"><a id="idm45058131219712"></a><p class="title"><strong>Figure 4.2. TeleMetrum v1 Board</strong></p><div class="figure-contents"><div class="mediaobject"><img src="telemetrum-v1.1-thside.jpg" width="495" alt="telemetrum-v1.1-thside.jpg" /></div></div></div><br class="figure-break" /><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><p>There are two generations of the TeleMetrum design. The +major changes in the v2 generation are:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +uBlox GPS chip certified for altitude records +</li><li class="listitem"> +Higher power radio (40mW vs 10mW) +</li><li class="listitem"> +APRS support +</li></ul></div><p>Otherwise, they’re the same size, with mounting holes and +screw terminals in the same position.</p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_telemetrum_screw_terminals"></a>4.1. TeleMetrum Screw Terminals</h2></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 id="idm45058131209152"></a><p class="title"><strong>Table 4.1. TeleMetrum Screw Terminals</strong></p><div class="table-contents"><table summary="TeleMetrum Screw Terminals" cellpadding="4px" style="border-collapse: collapse;border-top: 1px solid #78079a; border-bottom: 1px solid #78079a; border-left: 1px solid #78079a; border-right: 1px solid #78079a; "><colgroup><col class="col_1" /><col class="col_2" /><col class="col_3" /></colgroup><thead><tr><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Terminal #</th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Terminal Name</th><th style="border-bottom: 1px solid #78079a; " align="left" valign="top">Description</th></tr></thead><tbody><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>1</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Switch Output</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Switch connection to flight computer</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>2</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Switch Input</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Switch connection to positive battery terminal</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>3</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main +</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main pyro channel common connection to battery</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>4</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main -</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main pyro channel connection to pyro circuit</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>5</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee +</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee pyro channel common connection to battery</p></td></tr><tr><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>6</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>Apogee -</p></td><td style="" align="left" valign="top"><p>Apogee pyro channel connection to pyro circuit</p></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 id="_using_a_separate_pyro_battery_with_telemetrum"></a>4.2. Using a Separate Pyro Battery with TeleMetrum</h2></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><h2 class="title" style="clear: both"><a id="_using_an_active_switch_with_telemetrum"></a>4.3. Using an Active Switch with TeleMetrum</h2></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="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="_telemini_v1_0"></a>Chapter 5. TeleMini v1.0</h1></div></div></div><div class="figure"><a id="idm45058131173360"></a><p class="title"><strong>Figure 5.1. TeleMini v1.0 Board</strong></p><div class="figure-contents"><div class="mediaobject"><img src="telemini-v1-top.jpg" width="495" alt="telemini-v1-top.jpg" /></div></div></div><br class="figure-break" /><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><h2 class="title" style="clear: both"><a id="_telemini_v1_0_screw_terminals"></a>5.1. TeleMini v1.0 Screw Terminals</h2></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 id="idm45058131166752"></a><p class="title"><strong>Table 5.1. TeleMini v1.0 Screw Terminals</strong></p><div class="table-contents"><table summary="TeleMini v1.0 Screw Terminals" cellpadding="4px" style="border-collapse: collapse;border-top: 1px solid #78079a; border-bottom: 1px solid #78079a; border-left: 1px solid #78079a; border-right: 1px solid #78079a; "><colgroup><col class="col_1" /><col class="col_2" /><col class="col_3" /></colgroup><thead><tr><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Terminal #</th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Terminal Name</th><th style="border-bottom: 1px solid #78079a; " align="left" valign="top">Description</th></tr></thead><tbody><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>1</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee -</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee pyro channel connection to pyro circuit</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>2</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee pyro channel common connection to battery</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>3</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main -</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main pyro channel connection to pyro circuit</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>4</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main pyro channel common connection to battery</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Left</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Switch Output</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Switch connection to flight computer</p></td></tr><tr><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>Right</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>Switch Input</p></td><td style="" align="left" valign="top"><p>Switch connection to positive battery terminal</p></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 id="_using_a_separate_pyro_battery_with_telemini_v1_0"></a>5.2. Using a Separate Pyro Battery with TeleMini v1.0</h2></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><h2 class="title" style="clear: both"><a id="_using_an_active_switch_with_telemini_v1_0"></a>5.3. Using an Active Switch with TeleMini v1.0</h2></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="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="_easymini"></a>Chapter 6. EasyMini</h1></div></div></div><div class="figure"><a id="idm45058131130096"></a><p class="title"><strong>Figure 6.1. EasyMini Board</strong></p><div class="figure-contents"><div class="mediaobject"><img src="easymini-top.jpg" width="495" alt="easymini-top.jpg" /></div></div></div><br class="figure-break" /><p>EasyMini is built on a 0.8 inch by 1½ inch circuit board. It’s +designed to fit in a 24mm coupler tube.</p><p>You usually don’t need to configure EasyMini at all; it’s set +up to do dual-deployment with an event at apogee to separate +the airframe and deploy a drogue and another event at 250m +(820ft) to deploy the main. Install EasyMini in your airframe, +hook up a battery, igniters and a power switch and you’re +ready to fly.</p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_easymini_screw_terminals"></a>6.1. EasyMini Screw Terminals</h2></div></div></div><p>EasyMini has two sets of four screw terminals near one end of the +board. 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 id="idm45058131124080"></a><p class="title"><strong>Table 6.1. EasyMini Screw Terminals</strong></p><div class="table-contents"><table summary="EasyMini Screw Terminals" cellpadding="4px" style="border-collapse: collapse;border-top: 1px solid #78079a; border-bottom: 1px solid #78079a; border-left: 1px solid #78079a; border-right: 1px solid #78079a; "><colgroup><col class="col_1" /><col class="col_2" /><col class="col_3" /></colgroup><thead><tr><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Terminal #</th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Terminal Name</th><th style="border-bottom: 1px solid #78079a; " align="left" valign="top">Description</th></tr></thead><tbody><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 1</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main -</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main pyro channel connection to pyro circuit</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 2</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main pyro channel common connection to battery</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 3</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Battery</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Positive external battery terminal</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 4</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Battery -</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Negative external battery terminal</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Bottom 1</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee -</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee pyro channel connection to pyro circuit</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Bottom 2</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee pyro channel common connection to battery</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Bottom 3</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Switch Output</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Switch connection to flight computer</p></td></tr><tr><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>Bottom 4</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>Switch Input</p></td><td style="" align="left" valign="top"><p>Switch connection to positive battery terminal</p></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 id="_connecting_a_battery_to_easymini"></a>6.2. Connecting A Battery To EasyMini</h2></div></div></div><p>There are two possible battery connections on +EasyMini. You can use either method; both feed +through the power switch terminals.</p><p>One battery connection is the standard Altus Metrum +white JST plug. This mates with single-cell Lithium +Polymer batteries sold by Altus Metrum.</p><p>The other is a pair of screw terminals marked <span class="emphasis"><em>Battery ++</em></span> and <span class="emphasis"><em>Battery -</em></span>. Connect a battery from 4 to 12 +volts to these terminals, being careful to match polarity.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_charging_lithium_batteries"></a>6.3. Charging Lithium Batteries</h2></div></div></div><p>Because EasyMini allows for batteries other than the +standard Altus Metrum Lithium Polymer cells, it cannot +incorporate a battery charger circuit. Therefore, when +using a Litium Polymer cell, you’ll need an external +charger. These are available from Altus Metrum, or +from Spark Fun.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_using_a_separate_pyro_battery_with_easymini"></a>6.4. Using a Separate Pyro Battery with EasyMini</h2></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 EasyMini +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><h2 class="title" style="clear: both"><a id="_using_an_active_switch_with_easymini"></a>6.5. Using an Active Switch with EasyMini</h2></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="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="_telemega"></a>Chapter 7. TeleMega</h1></div></div></div><div class="figure"><a id="idm45058131075552"></a><p class="title"><strong>Figure 7.1. TeleMega Board</strong></p><div class="figure-contents"><div class="mediaobject"><img src="telemega-v1.0-top.jpg" width="495" alt="telemega-v1.0-top.jpg" /></div></div></div><br class="figure-break" /><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><p>TeleMega v2.0 has a few minor changes from v1.0:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Companion connector matches EasyMega functions +</li><li class="listitem"> +Serial port connector replaced with servo connector with +support for up to 4 PWM channels. +</li><li class="listitem"> +Radio switched from cc1120 to cc1200. +</li></ul></div><p>None of these affect operation using the stock firmware, but +they do mean that the device needs different firmware to +operate correctly, so make sure you load the right firmware +when reflashing the device.</p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_telemega_screw_terminals"></a>7.1. TeleMega Screw Terminals</h2></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 id="idm45058131066192"></a><p class="title"><strong>Table 7.1. TeleMega Screw Terminals</strong></p><div class="table-contents"><table summary="TeleMega Screw Terminals" cellpadding="4px" style="border-collapse: collapse;border-top: 1px solid #78079a; border-bottom: 1px solid #78079a; border-left: 1px solid #78079a; border-right: 1px solid #78079a; "><colgroup><col class="col_1" /><col class="col_2" /><col class="col_3" /></colgroup><thead><tr><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Terminal #</th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Terminal Name</th><th style="border-bottom: 1px solid #78079a; " align="left" valign="top">Description</th></tr></thead><tbody><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 1</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Switch Input</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Switch connection to positive battery terminal</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 2</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Switch Output</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Switch connection to flight computer</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 3</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>GND</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Ground connection for use with external active switch</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 4</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main -</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main pyro channel connection to pyro circuit</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 5</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main pyro channel common connection to battery</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 6</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee -</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee pyro channel connection to pyro circuit</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 7</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee pyro channel common connection to battery</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 8</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>D -</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>D pyro channel connection to pyro circuit</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 9</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>D</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>D pyro channel common connection to battery</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Bottom 1</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>GND</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Ground connection for negative pyro battery terminal</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Bottom 2</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Pyro</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Positive pyro battery terminal</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Bottom 3</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Lipo</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Power switch output. Use to connect main battery to pyro battery input</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Bottom 4</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>A -</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>A pyro channel connection to pyro circuit</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Bottom 5</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>A</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>A pyro channel common connection to battery</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Bottom 6</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>B -</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>B pyro channel connection to pyro circuit</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Bottom 7</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>B</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>B pyro channel common connection to battery</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Bottom 8</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>C -</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>C pyro channel connection to pyro circuit</p></td></tr><tr><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>Bottom 9</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>C</p></td><td style="" align="left" valign="top"><p>C pyro channel common connection to battery</p></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 id="_using_a_separate_pyro_battery_with_telemega"></a>7.2. Using a Separate Pyro Battery with TeleMega</h2></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><h2 class="title" style="clear: both"><a id="_using_only_one_battery_with_telemega"></a>7.3. Using Only One Battery With TeleMega</h2></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><h2 class="title" style="clear: both"><a id="_using_an_active_switch_with_telemega"></a>7.4. Using an Active Switch with TeleMega</h2></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="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="_easymega"></a>Chapter 8. EasyMega</h1></div></div></div><div class="figure"><a id="idm45058130988752"></a><p class="title"><strong>Figure 8.1. EasyMega Board</strong></p><div class="figure-contents"><div class="mediaobject"><img src="easymega-v1.0-top.jpg" width="405" alt="easymega-v1.0-top.jpg" /></div></div></div><br class="figure-break" /><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><h2 class="title" style="clear: both"><a id="_easymega_screw_terminals"></a>8.1. EasyMega Screw Terminals</h2></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 id="idm45058130983408"></a><p class="title"><strong>Table 8.1. EasyMega Screw Terminals</strong></p><div class="table-contents"><table summary="EasyMega Screw Terminals" cellpadding="4px" style="border-collapse: collapse;border-top: 1px solid #78079a; border-bottom: 1px solid #78079a; border-left: 1px solid #78079a; border-right: 1px solid #78079a; "><colgroup><col class="col_1" /><col class="col_2" /><col class="col_3" /></colgroup><thead><tr><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Terminal #</th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Terminal Name</th><th style="border-bottom: 1px solid #78079a; " align="left" valign="top">Description</th></tr></thead><tbody><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 1</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Switch Input</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Switch connection to positive battery terminal</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 2</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Switch Output</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Switch connection to flight computer</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 3</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>GND</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Ground connection for use with external active switch</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 4</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main -</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main pyro channel connection to pyro circuit</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 5</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main pyro channel common connection to battery</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 6</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee -</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee pyro channel connection to pyro circuit</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 7</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee pyro channel common connection to battery</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 8</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>D -</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>D pyro channel connection to pyro circuit</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 9</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>D</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>D pyro channel common connection to battery</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Bottom 1</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>GND</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Ground connection for negative pyro battery terminal</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Bottom 2</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Pyro</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Positive pyro battery terminal</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Bottom 3</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Lipo</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Power switch output. Use to connect main battery to pyro battery input</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Bottom 4</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>A -</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>A pyro channel connection to pyro circuit</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Bottom 5</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>A</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>A pyro channel common connection to battery</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Bottom 6</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>B -</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>B pyro channel connection to pyro circuit</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Bottom 7</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>B</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>B pyro channel common connection to battery</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Bottom 8</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>C -</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>C pyro channel connection to pyro circuit</p></td></tr><tr><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>Bottom 9</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>C</p></td><td style="" align="left" valign="top"><p>C pyro channel common connection to battery</p></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 id="_using_a_separate_pyro_battery_with_easymega"></a>8.2. Using a Separate Pyro Battery with EasyMega</h2></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><h2 class="title" style="clear: both"><a id="_using_only_one_battery_with_easymega"></a>8.3. Using Only One Battery With EasyMega</h2></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><h2 class="title" style="clear: both"><a id="_using_an_active_switch_with_easymega"></a>8.4. Using an Active Switch with EasyMega</h2></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="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="_installation"></a>Chapter 9. Installation</h1></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; you +can purchase suitable batteries from the any vendor selling +Altus Metrum products. 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.</p><div class="warning" style="margin-left: 0; margin-right: 10%;"><h3 class="title">Warning</h3><p>Check polarity and voltage before connecting any battery not +purchased from Altus Metrum.</p></div><div class="warning" style="margin-left: 0; margin-right: 10%;"><h3 class="title">Warning</h3><p>Spark Fun sells batteries that have a matching connector with +the correct polarity. However, these batteries include an +integrated current limiting circuit. That circuit will cause +the battery to shut down when firing the igniter circuit. Do +not use these batteries unless you remove the current limiting +circuit.</p></div><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 +<a class="xref" href="#_using_a_separate_pyro_battery" title="3.8. Using a Separate Pyro Battery">Section 3.8, “Using a Separate Pyro Battery”</a> 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 class="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="_using_altus_metrum_products"></a>Chapter 10. Using Altus Metrum Products</h1></div></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_being_legal"></a>10.1. Being Legal</h2></div></div></div><p>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 id="_in_the_rocket"></a>10.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 id="_on_the_ground"></a>10.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 +USB cable to plug into the flight computer board directly. +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"> +an antenna and feed-line or adapter +</li><li class="listitem"> +a TeleDongle +</li><li class="listitem"> +a notebook computer +</li><li class="listitem"> +optionally, a hand-held GPS receiver +</li><li class="listitem"> +optionally, an HT or receiver covering 435 MHz +</li></ol></div><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>.</p><p>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 id="_data_analysis"></a>10.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 flight log in a format 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 id="_future_plans"></a>10.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 id="_altosui"></a>Chapter 11. AltosUI</h1></div></div></div><div class="figure"><a id="idm45058130868928"></a><p class="title"><strong>Figure 11.1. AltosUI Main Window</strong></p><div class="figure-contents"><div class="mediaobject"><img src="altosui.png" width="414" alt="altosui.png" /></div></div></div><br class="figure-break" /><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 id="_monitor_flight"></a>11.1. Monitor Flight</h2></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="figure"><a id="idm45058130863296"></a><p class="title"><strong>Figure 11.2. Device Selection Dialog</strong></p><div class="figure-contents"><div class="mediaobject"><img src="device-selection.png" width="279" alt="device-selection.png" /></div></div></div><br class="figure-break" /><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"> +The configured call-sign +</li><li class="listitem"> +The device serial number +</li><li class="listitem"> +The flight number. Each altimeter remembers how +many times it has flown. +</li><li class="listitem"> +The rocket flight state. Each flight passes through +several states including Pad, Boost, Fast, Coast, +Drogue, Main and Landed. +</li><li class="listitem"> +The Received Signal Strength Indicator value. This +lets you know how strong a signal TeleDongle is +receiving. At the default data rate, 38400 bps, in +bench testing, the radio inside TeleDongle v0.2 +operates down to about -106dBm, while the v3 radio +works down to about -111dBm. Weaker signals, or an +environment with radio noise may cause the data to +not be received. The packet link uses error +detection and correction techniques which prevent +incorrect data from being reported. +</li><li class="listitem"> +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. +</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 <span class="emphasis"><em>flight order</em></span> +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 <span class="emphasis"><em>table</em></span> 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 id="_launch_pad"></a>11.1.1. Launch Pad</h3></div></div></div><div class="figure"><a id="idm45058130849200"></a><p class="title"><strong>Figure 11.3. Monitor Flight Launch Pad View</strong></p><div class="figure-contents"><div class="mediaobject"><img src="launch-pad.png" width="495" alt="launch-pad.png" /></div></div></div><br class="figure-break" /><p>The <span class="emphasis"><em>Launch Pad</em></span> 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> +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 <span class="emphasis"><em>GO</em></span> status. +</dd><dt><span class="term"> +Apogee Igniter Voltage +</span></dt><dd> +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 <span class="emphasis"><em>GO</em></span> status. +</dd><dt><span class="term"> +Main Igniter Voltage +</span></dt><dd> +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 <span class="emphasis"><em>GO</em></span> status. +</dd><dt><span class="term"> +On-board Data Logging +</span></dt><dd> +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. +</dd><dt><span class="term"> +GPS Locked +</span></dt><dd> +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. +</dd><dt><span class="term"> +GPS Ready +</span></dt><dd> +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. +</dd></dl></div><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 id="_ascent"></a>11.1.2. Ascent</h3></div></div></div><div class="figure"><a id="idm45058130830016"></a><p class="title"><strong>Figure 11.4. Monitor Flight Ascent View</strong></p><div class="figure-contents"><div class="mediaobject"><img src="ascent.png" width="495" alt="ascent.png" /></div></div></div><br class="figure-break" /><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 id="_descent"></a>11.1.3. Descent</h3></div></div></div><div class="figure"><a id="idm45058130823280"></a><p class="title"><strong>Figure 11.5. Monitor Flight Descent View</strong></p><div class="figure-contents"><div class="mediaobject"><img src="descent.png" width="495" alt="descent.png" /></div></div></div><br class="figure-break" /><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 id="_landed"></a>11.1.4. Landed</h3></div></div></div><div class="figure"><a id="idm45058130815168"></a><p class="title"><strong>Figure 11.6. Monitor Flight Landed View</strong></p><div class="figure-contents"><div class="mediaobject"><img src="landed.png" width="495" alt="landed.png" /></div></div></div><br class="figure-break" /><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 <span class="emphasis"><em>Graph Flight</em></span> 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 id="_table"></a>11.1.5. Table</h3></div></div></div><div class="figure"><a id="idm45058130806592"></a><p class="title"><strong>Figure 11.7. Monitor Flight Table View</strong></p><div class="figure-contents"><div class="mediaobject"><img src="table.png" width="495" alt="table.png" /></div></div></div><br class="figure-break" /><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 id="_site_map"></a>11.1.6. Site Map</h3></div></div></div><div class="figure"><a id="idm45058130801760"></a><p class="title"><strong>Figure 11.8. Monitor Flight Site Map View</strong></p><div class="figure-contents"><div class="mediaobject"><img src="site-map.png" width="495" alt="site-map.png" /></div></div></div><br class="figure-break" /><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 <a class="xref" href="#_load_maps" title="11.12. Load Maps">Section 11.12, “Load Maps”</a>.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_igniter"></a>11.1.7. Igniter</h3></div></div></div><div class="figure"><a id="idm45058130793680"></a><p class="title"><strong>Figure 11.9. Monitor Flight Additional Igniter View</strong></p><div class="figure-contents"><div class="mediaobject"><img src="ignitor.png" width="495" alt="ignitor.png" /></div></div></div><br class="figure-break" /><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 <span class="emphasis"><em>GO</em></span> +status.</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_save_flight_data"></a>11.2. Save Flight Data</h2></div></div></div><p>The altimeter records flight data to its internal +flash memory. +Data logged on board 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 <span class="emphasis"><em>Save Flight Data</em></span> button allows you to +read the flash memory and write it to disk.</p><p>Clicking on the <span class="emphasis"><em>Save Flight Data</em></span> 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 +<a class="xref" href="#_controlling_an_altimeter_over_the_radio_link" title="A.3. Controlling An Altimeter Over The Radio Link">Section A.3, “Controlling An Altimeter Over The Radio Link”</a> 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 id="_replay_flight"></a>11.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 +<a class="xref" href="#_monitor_flight" title="11.1. Monitor Flight">Section 11.1, “Monitor Flight”</a> to learn how this window operates.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_graph_data"></a>11.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 id="_flight_graph"></a>11.4.1. Flight Graph</h3></div></div></div><div class="figure"><a id="idm45058130777360"></a><p class="title"><strong>Figure 11.10. Flight Data Graph</strong></p><div class="figure-contents"><div class="mediaobject"><img src="graph.png" width="495" alt="graph.png" /></div></div></div><br class="figure-break" /><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 id="_configure_graph"></a>11.4.2. Configure Graph</h3></div></div></div><div class="figure"><a id="idm45058130771968"></a><p class="title"><strong>Figure 11.11. Flight Graph Configuration</strong></p><div class="figure-contents"><div class="mediaobject"><img src="graph-configure.png" width="495" alt="graph-configure.png" /></div></div></div><br class="figure-break" /><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 id="_flight_statistics"></a>11.4.3. Flight Statistics</h3></div></div></div><div class="figure"><a id="idm45058130767456"></a><p class="title"><strong>Figure 11.12. Flight Statistics</strong></p><div class="figure-contents"><div class="mediaobject"><img src="graph-stats.png" width="495" alt="graph-stats.png" /></div></div></div><br class="figure-break" /><p>Shows overall data computed from the flight.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_map"></a>11.4.4. Map</h3></div></div></div><div class="figure"><a id="idm45058130763168"></a><p class="title"><strong>Figure 11.13. Flight Map</strong></p><div class="figure-contents"><div class="mediaobject"><img src="graph-map.png" width="495" alt="graph-map.png" /></div></div></div><br class="figure-break" /><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 id="_export_data"></a>11.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 id="_comma_separated_value_format"></a>11.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 <span class="emphasis"><em>#</em></span> 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 id="_keyhole_markup_language_for_google_earth"></a>11.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 id="_configure_altimeter"></a>11.6. Configure Altimeter</h2></div></div></div><div class="figure"><a id="idm45058130751680"></a><p class="title"><strong>Figure 11.14. Altimeter Configuration</strong></p><div class="figure-contents"><div class="mediaobject"><img src="configure-altimeter.png" width="324" alt="configure-altimeter.png" /></div></div></div><br class="figure-break" /><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> +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. +</dd><dt><span class="term"> +Reset +</span></dt><dd> +This resets the dialog to the most recently saved +values, erasing any changes you have made. +</dd><dt><span class="term"> +Reboot +</span></dt><dd> +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. +</dd><dt><span class="term"> +Close +</span></dt><dd> +This closes the dialog. Any unsaved changes will be +lost. +</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 id="_main_deploy_altitude"></a>11.6.1. Main Deploy Altitude</h3></div></div></div><p>This sets the altitude (above the recorded pad +altitude) at which the <span class="emphasis"><em>main</em></span> 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 id="_apogee_delay"></a>11.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 id="_apogee_lockout"></a>11.6.3. 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 <span class="emphasis"><em>Mach Delay</em></span>, 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 id="_frequency"></a>11.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 id="_rf_calibration"></a>11.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 id="_telemetry_rdf_aprs_enable"></a>11.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 id="_telemetry_baud_rate"></a>11.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 id="_aprs_interval"></a>11.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 id="_aprs_ssid"></a>11.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 id="_aprs_format"></a>11.6.10. APRS Format</h3></div></div></div><p>Whether to send APRS data in Compressed or +Uncompressed format. Compressed format is +smaller and more precise. Uncompressed +format is older, but may work better with your +device. The Kenwood TH-D72 only displays +altitude information with Uncompressed +format, while the Yaesu FT1D only displays +altitude with Compressed format. Test before +you fly to see which to use.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_callsign"></a>11.6.11. 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 id="_maximum_flight_log_size"></a>11.6.12. 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 id="_ignitor_firing_mode"></a>11.6.13. 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> +This is the usual mode of operation; the +<span class="emphasis"><em>apogee</em></span> channel is fired at apogee and the +<span class="emphasis"><em>main</em></span> channel at the height above ground +specified by the <span class="emphasis"><em>Main Deploy Altitude</em></span> during +descent. +</dd><dt><span class="term"> +Redundant Apogee +</span></dt><dd> +This fires both channels at apogee, the +<span class="emphasis"><em>apogee</em></span> channel first followed after a two +second delay by the <span class="emphasis"><em>main</em></span> channel. +</dd><dt><span class="term"> +Redundant Main +</span></dt><dd> +This fires both channels at the height above +ground specified by the Main Deploy Altitude +setting during descent. The <span class="emphasis"><em>apogee</em></span> channel +is fired first, followed after a two second +delay by the <span class="emphasis"><em>main</em></span> channel. +</dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_pad_orientation"></a>11.6.14. 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> +In this mode, the antenna end of the flight +computer must point forward, in line with the +expected flight path. +</dd><dt><span class="term"> +Antenna Down +</span></dt><dd> +In this mode, the antenna end of the flight +computer must point aft, in line with the +expected flight path. +</dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_beeper_frequency"></a>11.6.15. 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 id="_logging_trigger_motion"></a>11.6.16. Logging Trigger Motion</h3></div></div></div><p>This sets the amount of motion that TeleGPS +needs to see before logging the new +position. Motions smaller than this are +skipped, which saves storage space.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_position_reporting_interval"></a>11.6.17. Position Reporting Interval</h3></div></div></div><p>The interval between TeleGPS position reports, +both over the air and in the log. Increase +this to reduce the frequency of radio +transmissions and the length of time available +in the log.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_configure_pyro_channels"></a>11.6.18. Configure Pyro Channels</h3></div></div></div><div class="figure"><a id="idm45058130694496"></a><p class="title"><strong>Figure 11.15. Additional Pyro Channel Configuration</strong></p><div class="figure-contents"><div class="mediaobject"><img src="configure-pyro.png" width="495" alt="configure-pyro.png" /></div></div></div><br class="figure-break" /><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.</p><p>Select conditions and set the related value; +the pyro channel will be activated when <span class="strong"><strong>all</strong></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 <span class="emphasis"><em>Pyro Firing +Time</em></span> 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 <span class="emphasis"><em>Save</em></span> button in +the main Configure Flight Computer window.</p><div class="variablelist"><dl class="variablelist"><dt><span class="term"> +Acceleration +</span></dt><dd> +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. +</dd><dt><span class="term"> +Vertical speed +</span></dt><dd> +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. +</dd><dt><span class="term"> +Height +</span></dt><dd> +Select a value, and then choose +whether the height above the launch pad should +be above or below that value. +</dd><dt><span class="term"> +Orientation +</span></dt><dd> +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. +</dd></dl></div><div class="note" style="margin-left: 0; margin-right: 10%;"><h3 class="title">Note</h3><p>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></div><div class="variablelist"><dl class="variablelist"><dt><span class="term"> +Flight Time +</span></dt><dd> +Time since boost was detected. Select a value and choose +whether to activate the pyro channel before or after that amount of +time. +</dd><dt><span class="term"> +Ascending +</span></dt><dd> +A simple test saying whether the rocket is going up or +not. This is exactly equivalent to testing whether the speed is > 0. +</dd><dt><span class="term"> +Descending +</span></dt><dd> +A simple test saying whether the rocket is going down or +not. This is exactly equivalent to testing whether the speed is < 0. +</dd><dt><span class="term"> +After Motor +</span></dt><dd> +The flight software counts each time the rocket starts +accelerating and then decelerating (presumably due to a motor or +motors burning). Use this value for multi-staged or multi-airstart +launches. +</dd><dt><span class="term"> +Delay +</span></dt><dd> +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. +</dd><dt><span class="term"> +Flight State +</span></dt><dd><p class="simpara"> +The flight software tracks the flight +through a sequence of states: +</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Boost. The motor has lit and the rocket is +accelerating upwards. +</li><li class="listitem"> +Fast. The motor has burned out and the +rocket is decelerating, but it is going +faster than 200m/s. +</li><li class="listitem"> +Coast. The rocket is still moving upwards +and decelerating, but the speed is less +than 200m/s. +</li><li class="listitem"> +Drogue. The rocket has reached apogee and +is heading back down, but is above the +configured Main altitude. +</li><li class="listitem"> +Main. The rocket is still descending, and +is below the Main altitude +</li><li class="listitem"> +Landed. The rocket is no longer moving. +</li></ul></div></dd></dl></div><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="strong"><strong>into</strong></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></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_configure_altosui"></a>11.7. Configure AltosUI</h2></div></div></div><div class="figure"><a id="idm45058130656608"></a><p class="title"><strong>Figure 11.16. Configure AltosUI Dialog</strong></p><div class="figure-contents"><div class="mediaobject"><img src="configure-altosui.png" width="216" alt="configure-altosui.png" /></div></div></div><br class="figure-break" /><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 id="_voice_settings"></a>11.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> +Turns all voice announcements on and off +</dd><dt><span class="term"> +Test Voice +</span></dt><dd> +Plays a short message allowing you to verify +that the audio system is working and the volume settings +are reasonable +</dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_log_directory"></a>11.7.2. Log Directory</h3></div></div></div><p>AltosUI logs all telemetry data and saves all +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 <span class="emphasis"><em>Select Directory</em></span> to +change where AltosUI reads and writes data +files.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_callsign_2"></a>11.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 id="_imperial_units"></a>11.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 id="_serial_debug"></a>11.7.5. 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 id="_font_size"></a>11.7.6. 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 id="_look_amp_feel"></a>11.7.7. Look & feel</h3></div></div></div><p>Switches between the available Java user +interface appearances. The default selection +is supposed to match the native window system +appearance for the target platform.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_menu_position"></a>11.7.8. Menu position</h3></div></div></div><p>Selects the initial position for the main +AltosUI window that includes all of the +command buttons.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_map_cache_size"></a>11.7.9. Map Cache Size</h3></div></div></div><p>Sets the number of map <span class="emphasis"><em>tiles</em></span> kept in memory +while the application is running. More tiles +consume more memory, but will make panning +around the map faster.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_manage_frequencies"></a>11.7.10. 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 id="_configure_groundstation"></a>11.8. Configure Groundstation</h2></div></div></div><div class="figure"><a id="idm45058130628688"></a><p class="title"><strong>Figure 11.17. Configure Groundstation Dialog</strong></p><div class="figure-contents"><div class="mediaobject"><img src="configure-groundstation.png" width="279" alt="configure-groundstation.png" /></div></div></div><br class="figure-break" /><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> +This writes any changes to the local Java +preferences file. If you don’t press this +button, any changes you make will be lost. +</dd><dt><span class="term"> +Reset +</span></dt><dd> +This resets the dialog to the most recently +saved values, erasing any changes you have +made. +</dd><dt><span class="term"> +Close +</span></dt><dd> +This closes the dialog. Any unsaved changes +will be lost. +</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 id="_frequency_2"></a>11.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 id="_rf_calibration_2"></a>11.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 id="_telemetry_rate"></a>11.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 id="_flash_image"></a>11.9. Flash Image</h2></div></div></div><p>This reprograms Altus Metrum devices with new +firmware. +TeleMetrum v1.x, TeleDongle v0.2, TeleMini +and TeleBT are all reprogrammed by using another +similar unit as a programming dongle (pair +programming). +TeleMega, EasyMega, TeleMetrum v2, +EasyMini and TeleDongle v3 are all +programmed directly +over USB (self programming). Please read +the directions for flashing devices in +<a class="xref" href="#_updating_device_firmware" title="Appendix C. Updating Device Firmware">Appendix C, <em>Updating Device Firmware</em></a>.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_fire_igniter"></a>11.10. Fire Igniter</h2></div></div></div><div class="figure"><a id="idm45058130608144"></a><p class="title"><strong>Figure 11.18. Fire Igniter Window</strong></p><div class="figure-contents"><div class="mediaobject"><img src="fire-igniter.png" width="108" alt="fire-igniter.png" /></div></div></div><br class="figure-break" /><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 <span class="emphasis"><em>Fire Igniter</em></span> 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 <span class="emphasis"><em>Arm</em></span> button.</p><p>Select the <span class="emphasis"><em>Arm</em></span> button. This enables the <span class="emphasis"><em>Fire</em></span> +button. The word <span class="emphasis"><em>Arm</em></span> is replaced by a countdown +timer indicating that you have 10 seconds to press the +<span class="emphasis"><em>Fire</em></span> 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 id="_scan_channels"></a>11.11. Scan Channels</h2></div></div></div><div class="figure"><a id="idm45058130598992"></a><p class="title"><strong>Figure 11.19. Scan Channels Window</strong></p><div class="figure-contents"><div class="mediaobject"><img src="scan-channels.png" width="288" alt="scan-channels.png" /></div></div></div><br class="figure-break" /><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 id="_load_maps"></a>11.12. Load Maps</h2></div></div></div><div class="figure"><a id="idm45058130594176"></a><p class="title"><strong>Figure 11.20. Load Maps Window</strong></p><div class="figure-contents"><div class="mediaobject"><img src="load-maps.png" width="468" alt="load-maps.png" /></div></div></div><br class="figure-break" /><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.</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> +A combination of satellite imagery and road data. This +is the default view. +</dd><dt><span class="term"> +Satellite +</span></dt><dd> +Just the satellite imagery without any annotation. +</dd><dt><span class="term"> +Roadmap +</span></dt><dd> +Roads, political boundaries and a few geographic +features. +</dd><dt><span class="term"> +Terrain +</span></dt><dd> +Contour intervals and shading that show hills and +valleys. +</dd></dl></div><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. Larger zoom levels show more detail, smaller +zoom levels less.</p><p>The Map Radius value sets how large an area around the +center point to download. Select a value large enough +to cover any plausible flight from that site. Be aware +that loading a large area with a high maximum zoom +level can attempt to download a lot of data. Loading +hybrid maps with a 10km radius at a minimum zoom of -2 +and a maximum zoom of 2 consumes about 120MB of +space. Terrain and road maps consume about 1/10 as +much space as satellite or hybrid maps.</p><p>Clicking the <span class="emphasis"><em>Load Map</em></span> 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 id="_monitor_idle"></a>11.13. Monitor Idle</h2></div></div></div><div class="figure"><a id="idm45058130577728"></a><p class="title"><strong>Figure 11.21. Monitor Idle Window</strong></p><div class="figure-contents"><div class="mediaobject"><img src="monitor-idle.png" width="468" alt="monitor-idle.png" /></div></div></div><br class="figure-break" /><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><p>You can change the frequency and callsign used to +communicate with the flight computer; they must both +match the configuration in the flight computer +exactly.</p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="_altosdroid"></a>Chapter 12. AltosDroid</h1></div></div></div><p>AltosDroid provides the same flight monitoring capabilities as +AltosUI, but runs on Android devices. AltosDroid is designed +to connect to a TeleBT receiver over Bluetooth™ and (on +Android devices supporting USB On-the-go) TeleDongle and +TeleBT devices over USB. AltosDroid monitors telemetry data, +logging it to internal storage in the Android device, and +presents that data in a UI similar to the <span class="emphasis"><em>Monitor Flight</em></span> +window in AltosUI.</p><p>This manual will explain how to configure AltosDroid, connect +to TeleBT or TeleDongle, 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 id="_installing_altosdroid"></a>12.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 id="_charging_telebt_battery"></a>12.2. Charging TeleBT Battery</h2></div></div></div><p>Before using TeleBT with AltosDroid, make sure the +internal TeleBT battery is charged. To do this, +attach a micro USB cable from a computer or other USB +power source to TeleBT. A dual LED on the circuit +board should illuminate, showing red while the battery +is charging, green when charging is completed, and +both red and green on at the same time if there is a +battery fault.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_connecting_to_telebt_over_bluetooth"></a>12.3. Connecting to TeleBT over Bluetooth™</h2></div></div></div><p>Press the Android <span class="emphasis"><em>Menu</em></span> button or soft-key to see the +configuration options available. Select the <span class="emphasis"><em>Connect a +device</em></span> option and then the <span class="emphasis"><em>Scan for devices</em></span> entry +at the bottom to look for your TeleBT device. Select +your device, and when it asks for the code, enter +<span class="emphasis"><em>1234</em></span>.</p><p>Subsequent connections will not require you to enter +that code, and your <span class="emphasis"><em>paired</em></span> 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 id="_connecting_to_teledongle_or_telebt_over_usb"></a>12.4. Connecting to TeleDongle or TeleBT over USB</h2></div></div></div><p>Get a special USB On-the-go adapter cable. These +cables have a USB micro-B male connector on one end +and a standard A female connector on the other +end. Plug in your TeleDongle or TeleBT device to the +adapter cable and the adapter cable into your phone +and AltosDroid should automatically start up. If it +doesn’t, the most likely reason is that your Android +device doesn’t support USB On-the-go.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_configuring_altosdroid"></a>12.5. Configuring AltosDroid</h2></div></div></div><p>There are several configuration and operation +parameters available in the AltosDroid menu.</p><div class="variablelist"><dl class="variablelist"><dt><span class="term"> +Select radio frequency +</span></dt><dd> +This selects which frequency to listen on by bringing +up a menu of pre-set radio frequencies. Pick the one +which matches your altimeter. +</dd><dt><span class="term"> +Select data rate +</span></dt><dd> +Altus Metrum transmitters can be configured to operate +at lower data rates to improve transmission range. If +you have configured your device to do this, this menu +item allows you to change the receiver to match. +</dd><dt><span class="term"> +Change units +</span></dt><dd> +This toggles between metric and imperial units. +</dd><dt><span class="term"> +Load maps +</span></dt><dd> +Brings up a dialog allowing you to download offline +map tiles so that you can have maps available even if +you have no network connectivity at the launch site. +</dd><dt><span class="term"> +Map type +</span></dt><dd> +Displays a menu of map types and lets you select +one. Hybrid maps include satellite images with a +roadmap overlaid. Satellite maps dispense with the +roadmap overlay. Roadmap shows just the roads. Terrain +includes roads along with shadows indicating changes +in elevation, and other geographical features. +</dd><dt><span class="term"> +Toggle Online/Offline maps +</span></dt><dd> +Switches between online and offline maps. Online maps +will show a <span class="emphasis"><em>move to current position</em></span> icon in the +upper right corner, while offline maps will have +copyright information all over the map. Otherwise, +they’re pretty similar. +</dd><dt><span class="term"> +Select Tracker +</span></dt><dd> +Switches the information displays to show data for a +different transmitting device. The map will always +show all of the devices in view. Trackers are shown +and selected by serial number, so make sure you note +the serial number of devices in each airframe. +</dd><dt><span class="term"> +Delete Track +</span></dt><dd> +Deletes all information about a transmitting device. +</dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_altosdroid_flight_monitoring"></a>12.6. 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><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_pad"></a>12.7. Pad</h2></div></div></div><p>The <span class="emphasis"><em>Pad</em></span> 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><p>When the pad tab is selected, the voice responses will +include status changes to the igniters and GPS +reception, letting you know if the rocket is still +ready for launch.</p><div class="variablelist"><dl class="variablelist"><dt><span class="term"> +Battery +</span></dt><dd> +This indicates whether the Li-Po battery powering the +transmitter has sufficient charge to last for the +duration of the flight. A value of more than 3.8V is +required for a <span class="emphasis"><em>GO</em></span> status. +</dd><dt><span class="term"> +Receiver Battery +</span></dt><dd> +This indicates whether the Li-Po battery powering the +TeleBT has sufficient charge to last for the duration +of the flight. A value of more than 3.8V is required +for a <span class="emphasis"><em>GO</em></span> status. +</dd><dt><span class="term"> +Data Logging +</span></dt><dd> +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 +and TeleMega can store multiple flights, depending on +the configured maximum flight log size. TeleGPS logs +data continuously. 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. +</dd><dt><span class="term"> +GPS Locked +</span></dt><dd> +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. +</dd><dt><span class="term"> +GPS Ready +</span></dt><dd> +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. +</dd><dt><span class="term"> +Apogee Igniter +</span></dt><dd> +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 <span class="emphasis"><em>GO</em></span> status. +</dd><dt><span class="term"> +Main Igniter +</span></dt><dd> +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 <span class="emphasis"><em>GO</em></span> status. +</dd><dt><span class="term"> +Igniter A-D +</span></dt><dd> +This indicates whether the indicated additional pyro +channel 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 <span class="emphasis"><em>GO</em></span> status. +</dd></dl></div><p>The Pad tab also shows the location of the Android +device.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_flight"></a>12.8. Flight</h2></div></div></div><p>The <span class="emphasis"><em>Flight</em></span> tab shows information used to evaluate +and spot a rocket while in flight. It displays speed +and height data to monitor the health of the rocket, +along with elevation, range and bearing to help locate +the rocket in the sky.</p><p>While the Flight tab is displayed, the voice +announcements will include current speed, height, +elevation and bearing information.</p><div class="variablelist"><dl class="variablelist"><dt><span class="term"> +Speed +</span></dt><dd> +Shows current vertical speed. During descent, the +speed values are averaged over a fairly long time to +try and make them steadier. +</dd><dt><span class="term"> +Height +</span></dt><dd> +Shows the current height above the launch pad. +</dd><dt><span class="term"> +Max Speed +</span></dt><dd> +Shows the maximum vertical speed seen during the +flight. +</dd><dt><span class="term"> +Max Height +</span></dt><dd> +Shows the maximum height above launch pad. +</dd><dt><span class="term"> +Elevation +</span></dt><dd> +This is the angle above the horizon from the android +devices current position. +</dd><dt><span class="term"> +Range +</span></dt><dd> +The total distance from the android device to the +rocket, including both ground distance and difference +in altitude. Use this to gauge how large the rocket is +likely to appear in the sky. +</dd><dt><span class="term"> +Bearing +</span></dt><dd> +This is the aziumuth from true north for the rocket +from the android device. Use this in combination with +the Elevation value to help locate the rocket in the +sky, or at least to help point the antenna in the +general direction. This is provided in both degrees +and a compass point (like West South West). You’ll +want to know which direction is true north before +launching your rocket. +</dd><dt><span class="term"> +Ground Distance +</span></dt><dd> +This shows the distance across the ground to the +lat/lon where the rocket is located. Use this to +estimate what is currently under the rocket. +</dd><dt><span class="term"> +Latitude/Longitude +</span></dt><dd> +Displays the last known location of the rocket. +</dd><dt><span class="term"> +Apogee Igniter +</span></dt><dd> +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 <span class="emphasis"><em>GO</em></span> status. +</dd><dt><span class="term"> +Main Igniter +</span></dt><dd> +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 <span class="emphasis"><em>GO</em></span> status. +</dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_recover"></a>12.9. Recover</h2></div></div></div><p>The <span class="emphasis"><em>Recover</em></span> tab shows information used while +recovering the rocket on the ground after flight.</p><p>While the Recover tab is displayed, the voice +announcements will include distance along with either +bearing or direction, depending on whether you are +moving.</p><div class="variablelist"><dl class="variablelist"><dt><span class="term"> +Bearing +</span></dt><dd> +This is the aziumuth from true north for the rocket +from the android device. Use this in combination with +the Elevation value to help locate the rocket in the +sky, or at least to help point the antenna in the +general direction. This is provided in both degrees +and a compass point (like West South West). You’ll +want to know which direction is true north before +launching your rocket. +</dd><dt><span class="term"> +Direction +</span></dt><dd> +When you are in motion, this provides the angle from +your current direction of motion towards the rocket. +</dd><dt><span class="term"> +Distance +</span></dt><dd> +Distance over the ground to the rocket. +</dd><dt><span class="term"> +Tar Lat/Tar Lon +</span></dt><dd> +Displays the last known location of the rocket. +</dd><dt><span class="term"> +My Lat/My Lon +</span></dt><dd> +Displays the location of the Android device. +</dd><dt><span class="term"> +Max Height +</span></dt><dd> +Shows the maximum height above launch pad. +</dd><dt><span class="term"> +Max Speed +</span></dt><dd> +Shows the maximum vertical speed seen during the +flight. +</dd><dt><span class="term"> +Max Accel +</span></dt><dd> +Shows the maximum vertical acceleration seen during +the flight. +</dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_map_2"></a>12.10. Map</h2></div></div></div><p>The <span class="emphasis"><em>Map</em></span> tab shows a map of the area around the +rocket being tracked along with information needed to +recover it.</p><p>On the map itself, icons showing the location of the +android device along with the last known location of +each tracker. A blue line is drawn from the android +device location to the currently selected tracker.</p><p>Below the map, the distance and either bearing or +direction along with the lat/lon of the target and the +android device are shown</p><p>The Map tab provides the same voice announcements as +the Recover tab.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_downloading_flight_logs"></a>12.11. 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, 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 +<span class="emphasis"><em>.telem</em></span> files in the TeleMetrum directory that will +work with AltosUI directly.</p></div></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a id="_system_operation"></a>Appendix A. System Operation</h1></div></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_firmware_modes"></a>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 +EasyMini doesn’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>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>See <a class="xref" href="#_understanding_beeps" title="3.5. Understanding Beeps">Section 3.5, “Understanding Beeps”</a> for a summary of all of +the audio signals used.</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 <span class="emphasis"><em>reset</em></span> 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 <span class="emphasis"><em>emergency recovery</em></span> mode. In this mode, TeleMini is +configured as follows:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Sets the radio frequency to 434.550MHz +</li><li class="listitem"> +Sets the radio calibration back to the factory value. +</li><li class="listitem"> +Sets the callsign to N0CALL +</li><li class="listitem"> +Does not go to <span class="emphasis"><em>pad</em></span> mode after five seconds. +</li></ul></div><p>To get into <span class="emphasis"><em>emergency recovery</em></span> 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 +<span class="emphasis"><em>idle</em></span> 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 id="_gps"></a>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 id="_controlling_an_altimeter_over_the_radio_link"></a>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"> +Save Flight Data—Recover flight data from the +rocket without opening it up. +</li><li class="listitem"> +Configure altimeter apogee delays, main deploy +heights and additional pyro event conditions to +respond to changing launch conditions. You can also +<span class="emphasis"><em>reboot</em></span> 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. +</li><li class="listitem"> +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. +</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 +<span class="emphasis"><em>idle</em></span> 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 <span class="emphasis"><em>pad</em></span> 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 <span class="emphasis"><em>pad</em></span> 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 id="_ground_testing"></a>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 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 id="_radio_link"></a>A.5. Radio Link</h2></div></div></div><p>TeleMetrum, TeleMini and TeleMega 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 <span class="emphasis"><em>normal packet radio</em></span> 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 id="_aprs"></a>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 +<a class="xref" href="#_configure_altimeter" title="11.6. Configure Altimeter">Section 11.6, “Configure Altimeter”</a>.</p><p>AltOS supports both compressed and uncompressed APRS +position report data formats. The compressed format +provides for higher position precision and shorter +packets than the uncompressed APRS format. We’ve found +some older APRS receivers that do not handle the +compressed format. The Kenwood TH-72A requires the use +of uncompressed format to display altitude information +correctly. The Yaesu FT1D requires the use of +compressed format to display altitude information.</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 as shown in the following table.</p><div class="table"><a id="idm45058130419360"></a><p class="title"><strong>Table A.1. Altus Metrum APRS Comments</strong></p><div class="table-contents"><table summary="Altus Metrum APRS Comments" cellpadding="4px" style="border-collapse: collapse;border-top: 1px solid #78079a; border-bottom: 1px solid #78079a; border-left: 1px solid #78079a; border-right: 1px solid #78079a; "><colgroup><col class="col_1" /><col class="col_2" /><col class="col_3" /></colgroup><thead><tr><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Field </th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Example </th><th style="border-bottom: 1px solid #78079a; " align="left" valign="top">Description</th></tr></thead><tbody><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>1</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>L</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>GPS Status U for unlocked, L for locked</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>2</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>6</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Number of Satellites in View</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>3</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>B4.0</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Altimeter Battery Voltage</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>4</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>A3.7</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee Igniter Voltage</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>5</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>M3.7</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main Igniter Voltage</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>6</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>1286</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Device Serial Number</p></td></tr><tr><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>4</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>1286</p></td><td style="" align="left" valign="top"><p>Device Serial Number</p></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="literallayout">L6 B4.0 A3.7 M3.7 1286</pre><p>Here’s an example of an APRS comment showing GPS lock with 6 +satellites in view and a primary battery at 4.0V from device 1876.</p><pre class="literallayout">L6 B4.0 1876</pre><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 <span class="emphasis"><em>L</em></span> to <span class="emphasis"><em>U</em></span>. 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 id="_configurable_parameters"></a>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”. All of the +configurable parameters can be set using AltosUI. Read +<a class="xref" href="#_configure_altimeter" title="11.6. Configure Altimeter">Section 11.6, “Configure Altimeter”</a> for more information.</p></div></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a id="_handling_precautions"></a>Appendix B. 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><div class="warning" style="margin-left: 0; margin-right: 10%;"><h3 class="title">Warning</h3><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></div><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="appendix"><div class="titlepage"><div><div><h1 class="title"><a id="_updating_device_firmware"></a>Appendix C. Updating Device Firmware</h1></div></div></div><p>TeleMega, TeleMetrum v2, EasyMega, EasyMini and TeleDongle v3 +are all +programmed directly over their USB connectors (self +programming). +TeleMetrum v1, TeleMini and TeleDongle v0.2 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><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_updating_telemega_telemetrum_v2_easymega_easymini_or_teledongle_v3_firmware"></a>C.1. Updating TeleMega, TeleMetrum v2, EasyMega, EasyMini or TeleDongle v3 Firmware</h2></div></div></div><p>Self-programmable devices are reprogrammed by +connecting them to your computer over USB.</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"> +Attach a battery if necessary and power switch to +the target device. Power up the device. +</li><li class="listitem"> +Using a Micro USB cable, connect the target device to your +computer’s USB socket. +</li><li class="listitem"> +Run AltosUI, and select <span class="emphasis"><em>Flash Image</em></span> from the File menu. +</li><li class="listitem"> +Select the target device in the Device Selection dialog. +</li><li class="listitem"> +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 EasyMini-v1.0-1.6.0.ihx. +</li><li class="listitem"> +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. +</li><li class="listitem"> +Hit the <span class="emphasis"><em>OK</em></span> button and the software should proceed +to flash the device with new firmware, showing a +progress bar. +</li><li class="listitem"> +Verify that the device is working by using the +<span class="emphasis"><em>Configure Altimeter</em></span> or <span class="emphasis"><em>Configure Groundstation</em></span> +item to check over the configuration. +</li></ol></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_recovering_from_self_flashing_failure"></a>C.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> +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="strong"><strong>not</strong></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. +</dd><dt><span class="term"> +EasyMega +</span></dt><dd> +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="strong"><strong>not</strong></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. +</dd><dt><span class="term"> +TeleMetrum v2 +</span></dt><dd> +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="strong"><strong>not</strong></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. +</dd><dt><span class="term"> +EasyMini +</span></dt><dd> +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. +</dd><dt><span class="term"> +TeleDongle v3 +</span></dt><dd> +Connect pin 32 on the CPU to ground. Pin 32 is closest +to the USB wires on the row of pins towards the center +of the board. Ground is available on the capacitor +next to it, on the end towards the USB wires. +</dd></dl></div><p>Once you’ve located the right pins:</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"> +Turn the altimeter power off. +</li><li class="listitem"> +Connect a battery. +</li><li class="listitem"> +Connect the indicated terminals together with a +short piece of wire. Take care not to accidentally +connect anything else. +</li><li class="listitem"> +Connect USB +</li><li class="listitem"> +Turn the board power on. +</li></ol></div><p>The board should now be visible over USB as +<span class="emphasis"><em>AltosFlash</em></span> and be ready to receive firmware. Once +the board has been powered up, you can remove the +piece of wire.</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_pair_programming"></a>C.2. Pair Programming</h2></div></div></div><p>The big concept to understand is that you have to use +a TeleMetrum v1.0, TeleBT v1.0 or TeleDongle v0.2 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><p>If you need to update the firmware on a TeleDongle +v0.2, 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><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_updating_telemetrum_v1_x_firmware"></a>C.2.1. Updating TeleMetrum v1.x Firmware</h3></div></div></div><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"> +Find the <span class="emphasis"><em>programming cable</em></span> 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. +</li><li class="listitem"> +Take the 2 screws out of the TeleDongle v0.2 +or TeleBT v1.0 case to get access to the +circuit board. +</li><li class="listitem"> +Plug the 8-pin end of the programming cable +to the matching connector on the TeleDongle +v0.2 or TeleBT v1.0, 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. +</li><li class="listitem"> +Attach a battery to the TeleMetrum board. +</li><li class="listitem"> +Plug the TeleDongle v0.2 or TeleBT v1.0 into +your computer’s USB port, and power up the +TeleMetrum. +</li><li class="listitem"> +Run AltosUI, and select <span class="emphasis"><em>Flash Image</em></span> from +the File menu. +</li><li class="listitem"> +Pick the TeleDongle v0.2 or TeleBT v1.0 +device from the list, identifying it as the +programming device. +</li><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li><li class="listitem"> +Hit the <span class="emphasis"><em>OK</em></span> button and the software should +proceed to flash the TeleMetrum with new +firmware, showing a progress bar. +</li><li class="listitem"> +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 <span class="emphasis"><em>v</em></span> command to check the version, +etc. +</li></ol></div><p>If something goes wrong, give it another try.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_updating_telemini_firmware"></a>C.2.2. Updating TeleMini Firmware</h3></div></div></div><p>You’ll need a special <span class="emphasis"><em>programming cable</em></span> 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><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"> +Take the 2 screws out of the TeleDongle v0.2 +or TeleBT v1.0 case to get access to the +circuit board. +</li><li class="listitem"> +Plug the 8-pin end of the programming cable +to the matching connector on the TeleDongle +v0.2 or TeleBT v1.0, 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. +</li><li class="listitem"> +Attach a battery to the TeleMini board. +</li><li class="listitem"> +Plug the TeleDongle v0.2 or TeleBT v1.0 into +your computer’s USB port, and power up the +TeleMini +</li><li class="listitem"> +Run AltosUI, and select <span class="emphasis"><em>Flash Image</em></span> from +the File menu. +</li><li class="listitem"> +Pick the TeleDongle v0.2 or TeleBT v1.0 +device from the list, identifying it as the +programming device. +</li><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li><li class="listitem"> +Hit the <span class="emphasis"><em>OK</em></span> button and the software should +proceed to flash the TeleMini with new +firmware, showing a progress bar. +</li><li class="listitem"> +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. +</li></ol></div><p>If something goes wrong, give it another try.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_updating_teledongle_v0_2_firmware"></a>C.2.3. Updating TeleDongle v0.2 Firmware</h3></div></div></div><p>Updating TeleDongle v0.2 firmware is just like +updating TeleMetrum v1.x or TeleMini firmware, but you +use either a TeleMetrum v1.x, TeleDongle v0.2 or +TeleBT v1.0 as the programmer.</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"> +Find the <span class="emphasis"><em>programming cable</em></span> 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. +</li><li class="listitem"> +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 v1.x, TeleDongle v0.2 +or TeleBT v1.0. +</li><li class="listitem"> +Take the 2 screws out of the TeleDongle v0.2 or +TeleBT v1.0 case to get access to the circuit board. +</li><li class="listitem"> +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 +v0.2. 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. +</li><li class="listitem"> +Attach a battery to the TeleMetrum v1.x board if +you’re using one. +</li><li class="listitem"> +Plug both the programmer and the TeleDongle into +your computer’s USB ports, and power up the +programmer. +</li><li class="listitem"> +Run AltosUI, and select <span class="emphasis"><em>Flash Image</em></span> from the File +menu. +</li><li class="listitem"> +Pick the programmer device from the list, +identifying it as the programming device. +</li><li class="listitem"> +Select the image you want put on the TeleDongle +v0.2, 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. +</li><li class="listitem"> +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 v0.2 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. +</li><li class="listitem"> +Hit the <span class="emphasis"><em>OK</em></span> button and the software should proceed +to flash the TeleDongle v0.2 with new firmware, +showing a progress bar. +</li><li class="listitem"> +Confirm that the TeleDongle v0.2 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 <span class="emphasis"><em>v</em></span> command to check the +version, etc. Once you’re happy, remove the +programming cable and put the cover back on the +TeleDongle v0.2. +</li></ol></div><p>If something goes wrong, give it another try.</p><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><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a id="_flight_data_recording"></a>Appendix D. Flight Data Recording</h1></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 id="idm45058130283472"></a><p class="title"><strong>Table D.1. Data Storage on Altus Metrum altimeters</strong></p><div class="table-contents"><table summary="Data Storage on Altus Metrum altimeters" cellpadding="4px" style="border-collapse: collapse;border-top: 1px solid #78079a; border-bottom: 1px solid #78079a; border-left: 1px solid #78079a; border-right: 1px solid #78079a; "><colgroup><col class="col_1" /><col class="col_2" /><col class="col_3" /><col class="col_4" /></colgroup><thead><tr><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Device </th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Bytes per Sample </th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Total Storage </th><th style="border-bottom: 1px solid #78079a; " align="left" valign="top">Minutes at Full Rate</th></tr></thead><tbody><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>TeleMetrum v1.0</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>8</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>1MB</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>20</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>TeleMetrum v1.1 v1.2</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>8</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>2MB</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>40</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>TeleMetrum v2.0</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>16</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>8MB</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>80</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>TeleMini v1.0</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>2</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>5kB</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>4</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>EasyMini</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>16</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>1MB</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>10</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>TeleMega</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>32</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>8MB</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>40</p></td></tr><tr><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>EasyMega</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>32</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>8MB</p></td><td style="" align="left" valign="top"><p>40</p></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.</p><p>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="appendix"><div class="titlepage"><div><div><h1 class="title"><a id="_altus_metrum_hardware_specifications"></a>Appendix E. Altus Metrum Hardware Specifications</h1></div></div></div><p>Here’s the full set of Altus Metrum products, both in +production and retired.</p><div class="table"><a id="idm45058130237152"></a><p class="title"><strong>Table E.1. Altus Metrum Flight Computer Electronics</strong></p><div class="table-contents"><table summary="Altus Metrum Flight Computer Electronics" cellpadding="4px" style="border-collapse: collapse;border-top: 1px solid #78079a; border-bottom: 1px solid #78079a; border-left: 1px solid #78079a; border-right: 1px solid #78079a; "><colgroup><col class="col_1" /><col class="col_2" /><col class="col_3" /><col class="col_4" /><col class="col_5" /><col class="col_6" /><col class="col_7" /><col class="col_8" /></colgroup><thead><tr><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Device </th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"> Barometer </th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"> Z-axis accel </th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"> GPS </th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"> 3D sensors </th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"> Storage </th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"> RF Output </th><th style="border-bottom: 1px solid #78079a; " align="left" valign="top"> Battery</th></tr></thead><tbody><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>TeleMetrum v1.0</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>MP3H6115 10km (33k')</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>MMA2202 50g</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>SkyTraq</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>-</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>1MB</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>10mW</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>3.7V</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>TeleMetrum v1.1</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>MP3H6115 10km (33k')</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>MMA2202 50g</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>SkyTraq</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>-</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>2MB</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>10mW</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>3.7V</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>TeleMetrum v1.2</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>MP3H6115 10km (33k')</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>ADXL78 70g</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>SkyTraq</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>-</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>2MB</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>10mW</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>3.7V</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>TeleMetrum v2.0</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>MS5607 30km (100k')</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>MMA6555 102g</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>uBlox Max-7Q</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>-</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>8MB</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>40mW</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>3.7V</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>TeleMini v1.0</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>MP3H6115 10km (33k')</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>-</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>-</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>-</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>5kB</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>10mW</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>3.7V</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>EasyMini v1.0</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>MS5607 30km (100k')</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>-</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>-</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>-</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>1MB</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>-</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>3.7-12V</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>TeleMega v1.0</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>MS5607 30km (100k')</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>MMA6555 102g</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>uBlox Max-7Q</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>MPU6000 HMC5883</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>8MB</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>40mW</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>3.7V</p></td></tr><tr><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>EasyMega v1.0</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>MS5607 30km (100k')</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>MMA6555 102g</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>-</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>MPU6000 HMC5883</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>8MB</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>-</p></td><td style="" align="left" valign="top"><p>3.7V</p></td></tr></tbody></table></div></div><br class="table-break" /><p></p><div class="table"><a id="idm45058130154144"></a><p class="title"><strong>Table E.2. Altus Metrum Flight Computer Mechanical Components</strong></p><div class="table-contents"><table summary="Altus Metrum Flight Computer Mechanical Components" cellpadding="4px" style="border-collapse: collapse;border-top: 1px solid #78079a; border-bottom: 1px solid #78079a; border-left: 1px solid #78079a; border-right: 1px solid #78079a; "><colgroup><col class="col_1" /><col class="col_2" /><col class="col_3" /><col class="col_4" /><col class="col_5" /><col class="col_6" /></colgroup><thead><tr><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Device</th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Connectors</th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Screw Terminals</th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Width</th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Length</th><th style="border-bottom: 1px solid #78079a; " align="left" valign="top">Tube Size</th></tr></thead><tbody><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>TeleMetrum</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Antenna Debug Companion USB Battery</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee pyro Main pyro Switch</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>1 inch (2.54cm)</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>2 ¾ inch (6.99cm)</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>29mm coupler</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>TeleMini v1.0</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Antenna Debug Battery</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee pyro Main pyro</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>½ inch (1.27cm)</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>1½ inch (3.81cm)</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>18mm coupler</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>TeleMini v2.0</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Antenna Debug USB Battery</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee pyro Main pyro Battery Switch</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>0.8 inch (2.03cm)</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>1½ inch (3.81cm)</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>24mm coupler</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>EasyMini</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Debug USB Battery</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee pyro Main pyro Battery</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>0.8 inch (2.03cm)</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>1½ inch (3.81cm)</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>24mm coupler</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>TeleMega</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Antenna Debug Companion USB Battery</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee pyro Main pyro Pyro A-D Switch Pyro battery</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>1¼ inch (3.18cm)</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>3¼ inch (8.26cm)</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>38mm coupler</p></td></tr><tr><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>EasyMega</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>Debug Companion USB Battery</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>Apogee pyro Main pyro Pyro A-D Switch Pyro battery</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>1¼ inch (3.18cm)</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>2¼ inch (5.62cm)</p></td><td style="" align="left" valign="top"><p>38mm coupler</p></td></tr></tbody></table></div></div><br class="table-break" /></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a id="_release_notes"></a>Appendix F. Release Notes</h1></div></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_6_2"></a>F.1. Release Notes for Version 1.6.2</h2></div></div></div><p>Version 1.6.2 includes support for our updated TeleMega v2.0 +product and bug fixes in in the flight software for all our boards +and ground station interfaces.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos"></a>F.1.1. AltOS</h3></div></div></div><p>AltOS New Features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Add support for TeleMega v2.0 boards. +</li><li class="listitem"> +Add PWM servo driver. There’s no higher level code using +this yet, but the driver allows testing of the TeleMega v2.0 +servo output connector. +</li></ul></div><p>AltOS Fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Slow down telemetry packets to allow receiver to keep +up. +</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_and_telegps_applications"></a>F.1.2. AltosUI and TeleGPS Applications</h3></div></div></div><p>AltosUI and TeleGPS Fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Fix post-flight orientation computation when processing +TeleMega and EasyMega eeprom data files. +</li><li class="listitem"> +Capture complete eeprom data even when there are invalid +entries in the data. This keeps reading eeprom contents and +writing the associated .eeprom file when an error is detected. +</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_documentation"></a>F.1.3. Documentation</h3></div></div></div><p>We spent a bunch of time trying to improve our documentation</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +HTML versions now have a table of contents on the left side. +</li><li class="listitem"> +EasyMini now has its own shorter manual. +</li><li class="listitem"> +Provide links between sections in each document. +</li><li class="listitem"> +Lots of minor rewriting and restructuring to avoid +duplication of information +</li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_6_1"></a>F.2. Release Notes for Version 1.6.1</h2></div></div></div><p>Version 1.6.1 includes support for our updated TeleBT v3.0 +product and bug fixes in in the flight software for all our boards +and ground station interfaces.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_2"></a>F.2.1. AltOS</h3></div></div></div><p>AltOS New Features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Add support for TeleBT v3.0 boards. +</li><li class="listitem"> +Add support for uncompressed APRS data, providing support +for older APRS receivers. Uncompressed APRS data is less +precise, takes more bandwidth and doesn’t have integrated +altitude data. +</li></ul></div><p>AltOS Fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Make TeleDongle and TeleBT more tolerant of data rate +variations from transmitting devices. +</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_and_telegps_applications_2"></a>F.2.2. AltosUI and TeleGPS Applications</h3></div></div></div><p>AltosUI and TeleGPS New Features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Add map to Monitor Idle display. It’s nice to be able to +verify that maps are working, instead of needing to use +Monitor Flight. +</li></ul></div><p>AltosUI and TeleGPS Fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Fix frequency configuration to round values instead of +truncate them, avoiding a common 1kHz error in the setting. +</li><li class="listitem"> +Turn the Windows stub into a more useful program that can +launch the application with parameters so that file manager +icons work more reliably. +</li><li class="listitem"> +Force KML export to use a C locale so that numbers are +formatted with <span class="emphasis"><em>.</em></span> instead of <span class="emphasis"><em>,</em></span> for a decimal separator in +non-US locales. +</li><li class="listitem"> +Preload map tiles based on distance rather than number of +tiles; this means you get the same resolution covering the +entire area, rather than having high resolution near the +center and low resolution further away. +</li><li class="listitem"> +Allow configuration of frequency and callsign in Monitor +Idle mode. +</li><li class="listitem"> +Fix layout weirdness when resizing windows on +Windows. Windows shouldn’t have giant blank spaces around +the useful content anymore. +</li><li class="listitem"> +Fix layout weirdness when resizing windows on +Windows. Windows shouldn’t have giant blank spaces around +the useful content anymore. +</li><li class="listitem"> +Use a longer filter for descent speed values. This should +provide something more useful on the display, although it +will take longer to respond to changes now. +</li><li class="listitem"> +Make Replay Flight run in realtime again. It had been set to +run at 10x speed by mistake. +</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosdroid_2"></a>F.2.3. AltosDroid</h3></div></div></div><p>AltosDroid New Features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Add offline map support using mapping code from AltosUI. +</li><li class="listitem"> +Support TeleDongle (and TeleBT via USB) on devices +supporting USB On-The-Go. +</li><li class="listitem"> +Display additional TeleMega pyro channel status in Pad tab. +</li><li class="listitem"> +Switch between metric and imperial units. +</li><li class="listitem"> +Monitor TeleBT battery voltage. +</li><li class="listitem"> +Track multiple devices at the same time, selecting between +them with a menu or using the map. +</li><li class="listitem"> +Add hybrid, satellite and terrain map types. +</li></ul></div><p>AltosDroid Fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Use standard Android display conventions so that a menu +button is available in the application title bar. +</li><li class="listitem"> +Adjust layout to work on large and small screens; shrinking +the go/no-go lights in smaller environments to try and make +everything visible. +</li><li class="listitem"> +Make voice announcements depend on current tab. +</li><li class="listitem"> +Compute adjustment to current travel direction while in +motion towards rocket. +</li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_6"></a>F.3. Release Notes for Version 1.6</h2></div></div></div><p>Version 1.6 includes support for our updated TeleDongle v3.0 +product and bug fixes in in the flight software for all our boards +and ground station interfaces.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_3"></a>F.3.1. AltOS</h3></div></div></div><p>AltOS New Features</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Add support for TeleDongle v3.0 boards. +</li></ul></div><p>AltOS Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Don’t beep out the continuity twice by accident in idle mode. +If the battery voltage report takes longer than the initialiation +sequence, the igniter continuity would get reported twice. +</li><li class="listitem"> +Record all 32 bits of gyro calibration data in TeleMega and +EasyMega log files. This fixes computation of the gyro rates +in AltosUI. +</li><li class="listitem"> +Change TeleDongle LED usage. Green LED flashes when valid +packet is received. Red LED flashes when invalid packet is +received. +</li><li class="listitem"> +Replace LPC11U14 SPI driver with non-interrupt version. The +interrupt code would occasionally wedge on long transfers +if interrupts were blocked for too long. This affects all +released TeleGPS products; if you have a TeleGPS device, +you’ll want to reflash the firmware. +</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_and_telegps_applications_3"></a>F.3.2. AltosUI and TeleGPS Applications</h3></div></div></div><p>AltosUI and TeleGPS New Features</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Compute tilt angle from TeleMega and EasyMega log +files. This duplicates the quaternion-based angle tracking +code from the flight firmware inside the ground station +software so that post-flight analysis can include evaluation +of the tilt angle. +</li><li class="listitem"> +Shows the tool button window when starting with a data file +specified. This means that opening a data file from the file +manager will now bring up the main window to let you operate +the whole application. +</li></ul></div><p>AltosUI Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Show the <span class="emphasis"><em>Connecting</em></span> dialog when using Monitor Idle. Lets +you cancel the Monitor Idle startup when connecting over the +radio link. +</li><li class="listitem"> +Make <span class="emphasis"><em>Monitor Idle</em></span> work for TeleGPS devices when connected +over USB. It’s nice for testing without needing to broadcast +over the radio. +</li><li class="listitem"> +Use different Windows API to discover USB devices. This +works better on my Windows 7 box, and will be used if the +older API fails to provide the necessary information. +</li><li class="listitem"> +Look in more places in the registry to try and identify the +installed Java version on Windows. If you install the +default 32-bit version of Windows on a 64-bit OS, the Java +registry information is hiding \SOFTWARE\Wow6432Node for +some reason. +</li><li class="listitem"> +Fix file association on Windows by searching for the +javaw.exe program instead of assuming it is in +%SYSTEMROOT%. This makes double-clicking on Altus Metrum +data files in the file manager work correctly. +</li><li class="listitem"> +When replaying a file, put <span class="emphasis"><em>done</em></span> in the Age field when we +reach the end of the file, instead of continuing to count forever. +</li><li class="listitem"> +In the Scan Channels code, wait for five seconds if we see +any packet. This is needed because AltOS now sends the +callsign, serial number and flight number only once every +five seconds these days. +</li><li class="listitem"> +In the Scan Channels code, reset pending flight state +information each time we change channels. This avoids having +flight computers appear on multiple frequencies by accident. +</li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_5"></a>F.4. Release Notes for 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><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_4"></a>F.4.1. AltOS</h3></div></div></div><p>AltOS New Features</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Add support for EasyMega boards. +</li><li class="listitem"> +Make the APRS SSID be configurable. This lets you track +different rockets on the same receiver without getting +things mixed up. +</li><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li></ul></div><p>AltOS Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Increase the maximum range for altitude values from +/-32767m +to +/-2147483647m, allowing the flight computers to function +correctly above the 32km level. +</li><li class="listitem"> +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. +</li><li class="listitem"> +Allow negative numbers in pyro configuration values. This +lets you specify things like descending speed or +deceleration. +</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_and_telegps_applications_4"></a>F.4.2. AltosUI and TeleGPS Applications</h3></div></div></div><p>AltosUI and TeleGPS New Features</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Support telemetry baud rate selection. Adds menus to +the flight monitoring and configuration for baud rate +selection. +</li><li class="listitem"> +Support APRS SSID configuration. +</li><li class="listitem"> +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. +</li></ul></div><p>AltosUI Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Make the <span class="emphasis"><em>Graph</em></span> button on the landed tab work again. +</li><li class="listitem"> +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. +</li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_4_2"></a>F.5. Release Notes for Version 1.4.2</h2></div></div></div><p>Version 1.4.2 is a minor release. It fixes Java-related install issues on +Windows</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_and_telegps_applications_5"></a>F.5.1. AltosUI and TeleGPS Applications</h3></div></div></div><p>Windows Install Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Checks for Java installation data in more registry locations. +</li><li class="listitem"> +Allows user to bypass Java installation in case the +detection fails. +</li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_4_1"></a>F.6. Release Notes for 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><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_and_telegps_applications_6"></a>F.6.1. AltosUI and TeleGPS Applications:</h3></div></div></div><p>Windows Install Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Provide signed Windows driver files. This should avoid any need to +disable driver signature checking on Windows 7 or 8. +</li><li class="listitem"> +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. +</li></ul></div><p>Other Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_4"></a>F.7. Release Notes for 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><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_5"></a>F.7.1. AltOS</h3></div></div></div><p>AltOS new features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Add support for TeleGPS boards. +</li><li class="listitem"> +Make the beeper tone configurable, making it +possible to distinguish between two Altus Metrum +products in the same ebay. +</li><li class="listitem"> +Make the firing time for extra pyro channels +configurable, allowing longer (or shorter) than the +default 50ms. Only relevant for TeleMega at this +time. +</li></ul></div><p>AltOS fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Replace the <span class="emphasis"><em>dit dit dit</em></span> 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. +</li><li class="listitem"> +Change state beeping to "Farnsworth spacing", which +means they’re quite a bit faster than before, and so +they take less time to send. +</li><li class="listitem"> +Fix bug preventing the selection of the <span class="emphasis"><em>Flight +State After</em></span> mode in pyro configuration. +</li><li class="listitem"> +Fix bug where erasing flights would reset the flight +number to 2 on TeleMega and TeleMetrum v2. +</li><li class="listitem"> +Fix u-Blox GPS driver to mark course and speed data +as being present. +</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_application"></a>F.7.2. AltosUI Application</h3></div></div></div><p>AltosUI new features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li><li class="listitem"> +Add new <span class="emphasis"><em>Ignitor</em></span> tab to the flight monitor display +for TeleMega’s extra ignitors. +</li><li class="listitem"> +Add additional ignitor firing marks and voltages to +the graph so you can see when the ignitors fired, +along with the ignitor voltages. +</li><li class="listitem"> +Add GPS course, ground speed and climb rate as +optional graph elements. +</li></ul></div><p>AltosUI fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +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. +</li><li class="listitem"> +Hide Tilt Angle in ascent tab for devices that don’t +have a gyro. +</li><li class="listitem"> +Increase the width of data lines in the graphs to +make them easier to read. +</li><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li><li class="listitem"> +Display error message when trying to configure +maximum flight log size while the flight computer +still has flight data stored. +</li><li class="listitem"> +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. +</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_telegps_application"></a>F.7.3. TeleGPS Application</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +New application designed for use with TeleGPS boards. +</li><li class="listitem"> +Shares code with AltosUI, mostly just trimmed down +to focus on TeleGPS-related functions. +</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_documentation_2"></a>F.7.4. Documentation</h3></div></div></div><p>Documentation changes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +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. +</li><li class="listitem"> +Add a description of the <span class="emphasis"><em>Apogee Lockout</em></span> setting, +which prevents the apogee charge from firing for a +configurable amount of time after boost. +</li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_3_2"></a>F.8. Release Notes for 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><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_6"></a>F.8.1. AltOS</h3></div></div></div><p>AltOS fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +On TeleMega, limit number of logged GPS status +information to 12 satellites. That’s all there is +room for in the log structure. +</li><li class="listitem"> +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. +</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_application_2"></a>F.8.2. AltosUI Application</h3></div></div></div><p>AltosUI fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +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. +</li><li class="listitem"> +Track the maximum height as computed from GPS +altitude data and report that in the flight summary +data. +</li><li class="listitem"> +Use letters (A, B, C, D) for alternate pyro channel +names instead of numbers (0, 1, 2, 3) in the Fire +Igniter dialog. +</li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_3_1"></a>F.9. Release Notes for 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><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_7"></a>F.9.1. AltOS</h3></div></div></div><p>AltOS new features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +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. +</li></ul></div><p>AltOS fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_application_3"></a>F.9.2. AltosUI Application</h3></div></div></div><p>AltosUI new features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li></ul></div><p>AltosUI fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +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. +</li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_3"></a>F.10. Release Notes for 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><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_8"></a>F.10.1. AltOS</h3></div></div></div><p>AltOS new features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Add STM32L processor support. This includes +enhancements to the scheduler to support products +with many threads. +</li><li class="listitem"> +Add NXP LPC11U14 processor support. +</li><li class="listitem"> +Support additional pyro channels. These are +configurable through the UI to handle air starts, +staging, additional recovery events and external +devices such as cameras. +</li><li class="listitem"> +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. +</li><li class="listitem"> +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 +</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_application_4"></a>F.10.2. AltosUI Application</h3></div></div></div><p>AltosUI new features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Support TeleMega, TeleMetrum v2.0, TeleMini v2.0 and +EasyMini telemetry and log formats. +</li></ul></div><p>AltosUI fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Use preferred units for main deployment height +configuration, instead of always doing configuration in +meters. +== MicroPeak Application +</li><li class="listitem"> +Add <span class="emphasis"><em>Download</em></span> button to menu bar. +</li><li class="listitem"> +Save the last log directory and offer that as the +default for new downloads +</li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_2_1"></a>F.11. Release Notes for 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><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_9"></a>F.11.1. AltOS</h3></div></div></div><p>AltOS new features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Add support for TeleBT +</li></ul></div><p>AltOS fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +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). +</li><li class="listitem"> +Correct Kalman filter model error covariance +matrix. The values used previously assumed +continuous measurements instead of discrete +measurements. +</li><li class="listitem"> +Fix some bugs in the USB driver for TeleMetrum and +TeleDongle that affected Windows users. +</li><li class="listitem"> +Adjusted the automatic gain control parameters that +affect receive performance for TeleDongle. Field +tests indicate that this may improve receive +performance somewhat. +</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_application_5"></a>F.11.2. AltosUI Application</h3></div></div></div><p>AltosUI application new features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Make the initial position of the AltosUI top level +window configurable. Along with this change, the +other windows will pop up at <span class="emphasis"><em>sensible</em></span> places now, +instead of on top of one another. +</li><li class="listitem"> +Add GPS data and a map to the graph window. This +lets you see a complete summary of the flight +without needing to <span class="emphasis"><em>replay</em></span> the whole thing. +</li></ul></div><p>AltosUI application fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Handle missing GPS lock in <span class="emphasis"><em>Descent</em></span> +tab. Previously, if the GPS position of the pad was +unknown, an exception would be raised, breaking the +Descent tab contents. +</li><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosdroid_3"></a>F.11.3. AltosDroid</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +First version of this application +</li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_2"></a>F.12. Release Notes for 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><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_10"></a>F.12.1. AltOS</h3></div></div></div><p>AltOS New Features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +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. +</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_and_micropeak_application"></a>F.12.2. AltosUI and MicroPeak Application</h3></div></div></div><p>New Features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Added MicroPeak application +</li></ul></div><p>AltosUI and MicroPeak fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Distribute Mac OS X packages in disk image (<span class="emphasis"><em>.dmg</em></span>) +format to greatly simplify installation. +</li><li class="listitem"> +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. +</li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_1"></a>F.13. Release Notes for Version 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><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_11"></a>F.13.1. AltOS</h3></div></div></div><p>AltOS fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +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. +</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_2"></a>F.13.2. AltosUI</h3></div></div></div><p>AltosUI new features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +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. +</li></ul></div><p>AltosUI fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_1_2"></a>F.14. Release Notes for 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><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_12"></a>F.14.1. AltOS</h3></div></div></div><p>AltOS Firmware New Features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Add apogee-lockout value. Overrides the apogee +detection logic to prevent incorrect apogee charge +firing. +</li><li class="listitem"> +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. +</li><li class="listitem"> +Provide RSSI values for Monitor Idle mode. This +makes it easy to check radio range without needing +to go to flight mode. +</li></ul></div><p>AltOS Fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Fix a bug where the data reported in telemetry +packets was from 320ms ago. +</li><li class="listitem"> +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. +</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_3"></a>F.14.2. AltosUI</h3></div></div></div><p>AltosUI New Features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Make the look-n-feel configurable, providing a choice from +the available options. +</li><li class="listitem"> +Add an <span class="emphasis"><em>Age</em></span> element to mark how long since a +telemetry packet has been received. Useful to +quickly gauge whether communications with the rocket +are still active. +</li><li class="listitem"> +Add <span class="emphasis"><em>Configure Ground Station</em></span> dialog to set the +radio frequency used by a particular TeleDongle +without having to go through the flight monitor UI. +</li><li class="listitem"> +Add configuration for the new apogee-lockout +value. A menu provides a list of reasonable values, +or the value can be set by hand. +</li><li class="listitem"> +Add Imperial units mode to present data in feet +instead of meters. +</li></ul></div><p>AltosUI Fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li><li class="listitem"> +Change how data are displayed in the <span class="emphasis"><em>table</em></span> 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 <span class="emphasis"><em>Monitor Idle</em></span> mode. +</li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_0_1"></a>F.15. Release Notes for 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><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_13"></a>F.15.1. AltOS</h3></div></div></div><p>AltOS New Features</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Add TeleMini v1.0 support. +</li><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li><li class="listitem"> +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 <span class="emphasis"><em>channels</em></span>, +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. +</li></ul></div><p>AltOS Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_application_6"></a>F.15.2. AltosUI Application</h3></div></div></div><p>AltosUI New Features</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Add main/apogee voltage graphs to the data +plot. This provides a visual indication if the +igniters fail before being fired. +</li><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li><li class="listitem"> +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 <span class="emphasis"><em>Landed</em></span> tab in the Monitor Flight +window so you can immediately see the results of a +flight. +</li></ul></div><p>AltosUI Changes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +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. +</li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_0_9_2"></a>F.16. Release Notes for 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="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_4"></a>F.16.1. AltosUI</h3></div></div></div><p>AltosUI fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Fix plotting problems due to missing file in the Mac +OS install image. +</li><li class="listitem"> +Always read whole eeprom blocks, mark empty records +invalid, display parsing errors to user. +</li><li class="listitem"> +Add software version to Configure AltosUI dialog +</li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_0_9"></a>F.17. Release Notes for 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="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_14"></a>F.17.1. AltOS</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_application_7"></a>F.17.2. AltosUI Application</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Support for telemetry format changes. +</li><li class="listitem"> +Support for multiple flight logs. +</li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_0_8"></a>F.18. Release Notes for Version 0.8</h2></div></div></div><p>Version 0.8 offers a major upgrade in the AltosUI +interface.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_application_8"></a>F.18.1. AltosUI Application:</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li><li class="listitem"> +Optimized flight status displays. Each flight state now has +it’s own custom <span class="emphasis"><em>tab</em></span> 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. +</li><li class="listitem"> +Monitor multiple flights simultaneously. If you have more +than one TeleDongle, you can monitor a flight with each one +on the same computer. +</li><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_0_7_1"></a>F.19. Release Notes for 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.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_application_9"></a>F.19.1. AltosUI Application</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +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. +</li><li class="listitem"> +Download logged data from TeleMetrum devices, either through +a direct USB connection or over the air through a TeleDongle +device. +</li><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li></ul></div></div></div></div></div></body></html>
\ No newline at end of file diff --git a/AltOS/doc/altusmetrum.pdf b/AltOS/doc/altusmetrum.pdf Binary files differindex a257787..72a2291 100644 --- a/AltOS/doc/altusmetrum.pdf +++ b/AltOS/doc/altusmetrum.pdf diff --git a/AltOS/doc/am.css b/AltOS/doc/am.css new file mode 100644 index 0000000..393ef81 --- /dev/null +++ b/AltOS/doc/am.css @@ -0,0 +1,476 @@ +/* + CSS stylesheet for XHTML produced by DocBook XSL stylesheets. +*/ + +@font-face { + font-family: 'Open Sans'; + src: url('fonts/OpenSans-Regular.ttf'); + font-weight: normal; + font-style: normal; +} + +@font-face { + font-family: 'Open Sans'; + src: url('fonts/OpenSans-Italic.ttf'); + font-weight: normal; + font-style: italic; +} + +@font-face { + font-family: 'Open Sans'; + src: url('fonts/OpenSans-Semibold.ttf'); + font-weight: bold; + font-style: normal; +} + +@font-face { + font-family: 'Open Sans'; + src: url('fonts/OpenSans-SemiboldItalic.ttf'); + font-weight: bold; + font-style: italic; +} + +@font-face { + font-family: 'DejaVu Sans Mono'; + src: url('fonts/DejaVuSansMono.ttf'); + font-weight: normal; + font-style: normal; +} + +@font-face { + font-family: 'DejaVu Sans Mono'; + src: url('fonts/DejaVuSansMono-Oblique.ttf'); + font-weight: normal; + font-style: oblique; +} + +@font-face { + font-family: 'DejaVu Sans Mono'; + src: url('fonts/DejaVuSansMono-Bold.ttf'); + font-weight: bold; + font-style: normal; +} + +@font-face { + font-family: 'DejaVu Sans Mono'; + src: url('fonts/DejaVuSansMono-BoldOblique.ttf'); + font-weight: bold; + font-style: oblique; +} + +body { + font-family: "Open Sans",sans-serif; + font-size: 12pt; +} + +code, pre { + font-family: "DejaVu Sans Mono", monospace; +} + +span.strong { + font-weight: bold; +} + +body blockquote { + margin-top: .75em; + line-height: 1.5; + margin-bottom: .75em; +} + +html body { + margin: 1em 5% 1em 5%; + line-height: 1.2; +} + +body div { + margin: 0; +} + +a:link { + color: #78079a; +} + +a:visited { + color: #78079a; +} + +h1, h2, h3, h4, h5, h6 +{ + color: #78079a; + font-family: "Open Sans",sans-serif; +} + +div.revhistory table { + width: 50%; + border-width: 1px; +} + +div titlepage { + margin-top: 100px; + border-top: 2px; +} + +div.warning h1, div.warning h2, div.warning h3, div.warning h4, div.warning h5, div.warning h6 { + color: #ff2020; +} + +div.warning p, div.note p, div.error p { + margin-left: 5%; + margin-left: 5%; +} + +h3.corpauthor img { + position: fixed; + left: 0px; + top: 0px; + width: 410px; + height: 90px; + border-right: 2px solid #808080; + border-bottom: 2px solid #808080; +} + +div.toc { + position: fixed; + left: 0px; + top: 92px; + bottom: 0; + width: 390px; + margin-right: 0; + margin-left: 0; + padding-left: 10px; + padding-right: 10px; + float: left; + border-right: 2px solid #808080; + border-collapse: collapse; + overflow: auto; +} + +div.toc p, +div.list-of-figures p, +div.list-of-tables p, +div.list-of-examples p, +div.toc a +{ + color: black; +} + +div.toc p { + color: black; +} + +div.toc a:link { + text-decoration: none; +} + +div.toc a:visited { + text-decoration: none; +} + +div.toc a:hover { + text-decoration: underline; +} + +div.toc a:active { + text-decoration: underline; +} + +div.book { + margin-left: 25em; +} + +div.list-of-figures { + display: none; +} + +div.list-of-tables { + display: none; +} + +div.figure p { + text-align: center; +} +div.figure img { + display: block; + margin: auto; +} + +div.table p.title { + text-align: center; +} + +div.table-contents table { + margin-left: auto; + margin-right: auto; +} + +div.example p.title, +div.sidebar p.title +{ + font-weight: normal; + color: #78079a; + font-family: "Open Sans",sans-serif; + margin-bottom: 0.2em; +} + +body h1 { + margin: .0em 0 0 -4%; + line-height: 1.3; + border-bottom: 2px solid #808080; +} + +body h2 { + margin: 0.5em 0 0 -4%; + line-height: 1.3; + border-bottom: 2px solid #808080; +} + +body h3 { + margin: .8em 0 0 -3%; + line-height: 1.3; +} + +body h4 { + margin: .8em 0 0 -3%; + line-height: 1.3; + border-top: 2px solid #808080; +} + +body h5 { + margin: .8em 0 0 -2%; + line-height: 1.3; +} + +body h6 { + margin: .8em 0 0 -1%; + line-height: 1.3; +} + +body hr { + border: none; /* Broken on IE6 */ +} +div.footnotes hr { + border: 1px solid #808080; +} + +div.navheader th, div.navheader td, div.navfooter td { + font-family: "Open Sans",sans-serif; + font-size: 12pt; + font-weight: normal; + color: #78079a; +} +div.navheader img, div.navfooter img { + border-style: none; +} +div.navheader a, div.navfooter a { + font-weight: normal; +} +div.navfooter hr { + border: 1px solid #808080; +} + +body td { + line-height: 1.2 +} + +body th { + line-height: 1.2; +} + +ol { + line-height: 1.2; +} + +ul, body dir, body menu { + line-height: 1.2; +} + +html { + margin: 0; + padding: 0; +} + +body h1, body h2, body h3, body h4, body h5, body h6 { + margin-left: 0 +} + +body pre { + margin: 0.5em 10% 0.5em 1em; + line-height: 1.0; +} + +tt.literal, code.literal { +} + +.programlisting, .screen { + border: 1px solid #808080; + background: #f4f4f4; + margin: 0.5em 10% 0.5em 0; + padding: 0.5em 1em; +} + +div.sidebar { + background: #ffffee; + margin: 1.0em 10% 0.5em 0; + padding: 0.5em 1em; + border: 1px solid #808080; +} +div.sidebar * { padding: 0; } +div.sidebar div { margin: 0; } +div.sidebar p.title { + margin-top: 0.5em; + margin-bottom: 0.2em; +} + +div.bibliomixed { + margin: 0.5em 5% 0.5em 1em; +} + +div.glossary dt { + font-weight: bold; +} +div.glossary dd p { + margin-top: 0.2em; +} + +dl { + margin: .8em 0; + line-height: 1.2; +} + +dt { + margin-top: 0.5em; +} + +dt span.term { + font-weight: bold; +} + +div.variablelist dd p { + margin-top: 0; +} + +div.itemizedlist li, div.orderedlist li { + margin-left: -0.8em; + margin-top: 0.5em; +} + +ul, ol { + list-style-position: outside; +} + +div.sidebar ul, div.sidebar ol { + margin-left: 2.8em; +} + +div.itemizedlist p.title, +div.orderedlist p.title, +div.variablelist p.title +{ + margin-bottom: -0.8em; +} + +div.revhistory { + border-style: none; +} + +div.revhistory table, div.revhistory th, div.revhistory td { + border-collapse: collapse; + border: 1px solid #808080; + padding: 0.25em; +} + +div.revhistory th { + color: black; +} + +/* Keep TOC and index lines close together. */ +div.toc dl, div.toc dt, +div.list-of-figures dl, div.list-of-figures dt, +div.list-of-tables dl, div.list-of-tables dt, +div.indexdiv dl, div.indexdiv dt +{ + line-height: normal; + margin-top: 0; + margin-bottom: 0; +} + +/* + Table styling does not work because of overriding attributes in + generated HTML. +*/ +div.table-contents p, +div.informaltable p +{ + margin: 0px; +} + +div.table thead, div.table tfoot, +div.informaltable thead, div.informaltable tfoot +{ + font-weight: bold; +} + +div.mediaobject img { + margin-bottom: 0.8em; +} +div.figure p.title, +div.table p.title +{ + margin-top: 1em; + margin-bottom: 0.4em; +} + +div.calloutlist p +{ + margin-top: 0em; + margin-bottom: 0.4em; +} + +a img { + border-style: none; +} + +@media print { + div.navheader, div.navfooter { display: none; } +} + +span.aqua { color: aqua; } +span.black { color: black; } +span.blue { color: blue; } +span.fuchsia { color: fuchsia; } +span.gray { color: gray; } +span.green { color: green; } +span.lime { color: lime; } +span.maroon { color: maroon; } +span.navy { color: navy; } +span.olive { color: olive; } +span.purple { color: purple; } +span.red { color: red; } +span.silver { color: silver; } +span.teal { color: teal; } +span.white { color: white; } +span.yellow { color: yellow; } + +span.aqua-background { background: aqua; } +span.black-background { background: black; } +span.blue-background { background: blue; } +span.fuchsia-background { background: fuchsia; } +span.gray-background { background: gray; } +span.green-background { background: green; } +span.lime-background { background: lime; } +span.maroon-background { background: maroon; } +span.navy-background { background: navy; } +span.olive-background { background: olive; } +span.purple-background { background: purple; } +span.red-background { background: red; } +span.silver-background { background: silver; } +span.teal-background { background: teal; } +span.white-background { background: white; } +span.yellow-background { background: yellow; } + +span.big { font-size: 2em; } +span.small { font-size: 0.6em; } + +span.underline { text-decoration: underline; } +span.overline { text-decoration: overline; } +span.line-through { text-decoration: line-through; } diff --git a/AltOS/doc/companion.pdf b/AltOS/doc/companion.pdf Binary files differindex 35fcf66..c8018f2 100644 --- a/AltOS/doc/companion.pdf +++ b/AltOS/doc/companion.pdf diff --git a/AltOS/doc/easymega-outline.pdf b/AltOS/doc/easymega-outline.pdf Binary files differindex 1a6be42..1d8ac85 100644 --- a/AltOS/doc/easymega-outline.pdf +++ b/AltOS/doc/easymega-outline.pdf diff --git a/AltOS/doc/easymega-v1.0-bottom.jpg b/AltOS/doc/easymega-v1.0-bottom.jpg Binary files differnew file mode 100644 index 0000000..be46f14 --- /dev/null +++ b/AltOS/doc/easymega-v1.0-bottom.jpg diff --git a/AltOS/doc/easymini-outline.pdf b/AltOS/doc/easymini-outline.pdf Binary files differindex 0e6ff9c..1610424 100644 --- a/AltOS/doc/easymini-outline.pdf +++ b/AltOS/doc/easymini-outline.pdf diff --git a/AltOS/doc/easymini-revhistory.html b/AltOS/doc/easymini-revhistory.html new file mode 100644 index 0000000..3588e49 --- /dev/null +++ b/AltOS/doc/easymini-revhistory.html @@ -0,0 +1,4 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Revision History</title><link rel="stylesheet" type="text/css" href="am.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.78.1" /></head><body><div class="revhistory"><table style="border-style:solid; width:100%;" summary="Revision History"><tr><th align="left" valign="top" colspan="2"><strong>Revision History</strong></th></tr><tr><td align="left">Revision 1.6.2</td><td align="left">10 January 2016</td></tr><tr><td align="left" colspan="2"> + First release of separate EasyMini doc + </td></tr></table></div></body></html> diff --git a/AltOS/doc/easymini.html b/AltOS/doc/easymini.html new file mode 100644 index 0000000..10cbdf2 --- /dev/null +++ b/AltOS/doc/easymini.html @@ -0,0 +1,670 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>EasyMini Owner’s Manual</title><link rel="stylesheet" type="text/css" href="am.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.78.1" /></head><body><div xml:lang="en" class="book" lang="en"><div class="titlepage"><div><div><h1 class="title"><a id="idm45510340386080"></a>EasyMini Owner’s Manual</h1></div><div><h2 class="subtitle">A Dual-Deploy Rocketry Flight Computer</h2></div><div><h3 class="corpauthor"> + <span class="inlinemediaobject"><img src="altusmetrum-oneline.svg" width="270" /></span> +</h3></div><div><div class="author"><h3 class="author"><span class="firstname">Bdale</span> <span class="surname">Garbee</span></h3><code class="email"><<a class="email" href="mailto:bdale@gag.com">bdale@gag.com</a>></code></div></div><div><div class="author"><h3 class="author"><span class="firstname">Keith</span> <span class="surname">Packard</span></h3><code class="email"><<a class="email" href="mailto:keithp@keithp.com">keithp@keithp.com</a>></code></div></div><div><p class="copyright">Copyright © 2016 Bdale Garbee and Keith Packard</p></div><div><div class="legalnotice"><a id="idm45510340537456"></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><a href="easymini-revhistory.html">Revision History</a></div></div><hr /></div><div class="dedication"><div class="titlepage"><div><div><h1 class="title"><a id="_acknowledgments"></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="blockquote"><blockquote class="blockquote"><div class="literallayout"><p>Bdale Garbee, KB0G<br /> +NAR #87103, TRA #12201</p></div></blockquote></div><div class="blockquote"><blockquote class="blockquote"><div class="literallayout"><p>Keith Packard, KD7SQG<br /> +NAR #88757, TRA #12200</p></div></blockquote></div></div><div class="toc"><p><strong>Table of Contents</strong></p><dl class="toc"><dt><span class="chapter"><a href="#_introduction_and_overview">1. Introduction and Overview</a></span></dt><dt><span class="chapter"><a href="#_getting_started">2. Getting Started</a></span></dt><dd><dl><dt><span class="section"><a href="#_batteries">2.1. Batteries</a></span></dt><dt><span class="section"><a href="#_linux_mac_windows_ground_station_software">2.2. Linux/Mac/Windows Ground Station Software</a></span></dt></dl></dd><dt><span class="chapter"><a href="#_using_altus_metrum_hardware">3. Using Altus Metrum Hardware</a></span></dt><dd><dl><dt><span class="section"><a href="#_wiring_and_electrical_interference">3.1. Wiring and Electrical Interference</a></span></dt><dt><span class="section"><a href="#_hooking_up_lithium_polymer_batteries">3.2. Hooking Up Lithium Polymer Batteries</a></span></dt><dt><span class="section"><a href="#_hooking_up_pyro_charges">3.3. Hooking Up Pyro Charges</a></span></dt><dt><span class="section"><a href="#_hooking_up_a_power_switch">3.4. Hooking Up a Power Switch</a></span></dt><dt><span class="section"><a href="#_understanding_beeps">3.5. Understanding Beeps</a></span></dt><dt><span class="section"><a href="#_turning_on_the_power">3.6. Turning On the Power</a></span></dt><dt><span class="section"><a href="#_using_an_external_active_switch_circuit">3.7. Using an External Active Switch Circuit</a></span></dt><dt><span class="section"><a href="#_using_a_separate_pyro_battery">3.8. Using a Separate Pyro Battery</a></span></dt><dt><span class="section"><a href="#_using_a_different_kind_of_battery">3.9. Using a Different Kind of Battery</a></span></dt></dl></dd><dt><span class="chapter"><a href="#_easymini">4. EasyMini</a></span></dt><dd><dl><dt><span class="section"><a href="#_easymini_screw_terminals">4.1. EasyMini Screw Terminals</a></span></dt><dt><span class="section"><a href="#_connecting_a_battery_to_easymini">4.2. Connecting A Battery To EasyMini</a></span></dt><dt><span class="section"><a href="#_charging_lithium_batteries">4.3. Charging Lithium Batteries</a></span></dt><dt><span class="section"><a href="#_using_a_separate_pyro_battery_with_easymini">4.4. Using a Separate Pyro Battery with EasyMini</a></span></dt><dt><span class="section"><a href="#_using_an_active_switch_with_easymini">4.5. Using an Active Switch with EasyMini</a></span></dt></dl></dd><dt><span class="chapter"><a href="#_installation">5. Installation</a></span></dt><dt><span class="chapter"><a href="#_using_altus_metrum_products">6. Using Altus Metrum Products</a></span></dt><dd><dl><dt><span class="section"><a href="#_in_the_rocket">6.1. In the Rocket</a></span></dt><dt><span class="section"><a href="#_on_the_ground">6.2. On the Ground</a></span></dt><dt><span class="section"><a href="#_data_analysis">6.3. Data Analysis</a></span></dt><dt><span class="section"><a href="#_future_plans">6.4. Future Plans</a></span></dt></dl></dd><dt><span class="chapter"><a href="#_altosui">7. AltosUI</a></span></dt><dd><dl><dt><span class="section"><a href="#_save_flight_data">7.1. Save Flight Data</a></span></dt><dt><span class="section"><a href="#_replay_flight">7.2. Replay Flight</a></span></dt><dt><span class="section"><a href="#_graph_data">7.3. Graph Data</a></span></dt><dd><dl><dt><span class="section"><a href="#_flight_graph">7.3.1. Flight Graph</a></span></dt><dt><span class="section"><a href="#_configure_graph">7.3.2. Configure Graph</a></span></dt><dt><span class="section"><a href="#_flight_statistics">7.3.3. Flight Statistics</a></span></dt></dl></dd><dt><span class="section"><a href="#_export_data">7.4. Export Data</a></span></dt><dd><dl><dt><span class="section"><a href="#_comma_separated_value_format">7.4.1. Comma Separated Value Format</a></span></dt></dl></dd><dt><span class="section"><a href="#_configure_altimeter">7.5. Configure Altimeter</a></span></dt><dd><dl><dt><span class="section"><a href="#_main_deploy_altitude">7.5.1. Main Deploy Altitude</a></span></dt><dt><span class="section"><a href="#_apogee_delay">7.5.2. Apogee Delay</a></span></dt><dt><span class="section"><a href="#_apogee_lockout">7.5.3. Apogee Lockout</a></span></dt><dt><span class="section"><a href="#_maximum_flight_log_size">7.5.4. Maximum Flight Log Size</a></span></dt><dt><span class="section"><a href="#_ignitor_firing_mode">7.5.5. Ignitor Firing Mode</a></span></dt><dt><span class="section"><a href="#_beeper_frequency">7.5.6. Beeper Frequency</a></span></dt></dl></dd><dt><span class="section"><a href="#_configure_altosui">7.6. Configure AltosUI</a></span></dt><dd><dl><dt><span class="section"><a href="#_log_directory">7.6.1. Log Directory</a></span></dt><dt><span class="section"><a href="#_imperial_units">7.6.2. Imperial Units</a></span></dt><dt><span class="section"><a href="#_serial_debug">7.6.3. Serial Debug</a></span></dt><dt><span class="section"><a href="#_font_size">7.6.4. Font size</a></span></dt><dt><span class="section"><a href="#_look_amp_feel">7.6.5. Look & feel</a></span></dt><dt><span class="section"><a href="#_menu_position">7.6.6. Menu position</a></span></dt></dl></dd><dt><span class="section"><a href="#_flash_image">7.7. Flash Image</a></span></dt><dt><span class="section"><a href="#_fire_igniter">7.8. Fire Igniter</a></span></dt></dl></dd><dt><span class="appendix"><a href="#_system_operation">A. System Operation</a></span></dt><dd><dl><dt><span class="section"><a href="#_firmware_modes">A.1. Firmware Modes</a></span></dt><dt><span class="section"><a href="#_ground_testing">A.2. Ground Testing</a></span></dt><dt><span class="section"><a href="#_configurable_parameters">A.3. Configurable Parameters</a></span></dt></dl></dd><dt><span class="appendix"><a href="#_handling_precautions">B. Handling Precautions</a></span></dt><dt><span class="appendix"><a href="#_updating_device_firmware">C. Updating Device Firmware</a></span></dt><dd><dl><dt><span class="section"><a href="#_updating_easymini_firmware">C.1. Updating EasyMini Firmware</a></span></dt><dd><dl><dt><span class="section"><a href="#_recovering_from_self_flashing_failure">C.1.1. Recovering From Self-Flashing Failure</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href="#_flight_data_recording">D. Flight Data Recording</a></span></dt><dt><span class="appendix"><a href="#_altus_metrum_hardware_specifications">E. Altus Metrum Hardware Specifications</a></span></dt><dt><span class="appendix"><a href="#_release_notes">F. Release Notes</a></span></dt><dd><dl><dt><span class="section"><a href="#_release_notes_for_version_1_6_2">F.1. Release Notes for Version 1.6.2</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos">F.1.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_and_telegps_applications">F.1.2. AltosUI and TeleGPS Applications</a></span></dt><dt><span class="section"><a href="#_documentation">F.1.3. Documentation</a></span></dt></dl></dd></dl></dd></dl></div><div class="list-of-figures"><p><strong>List of Figures</strong></p><dl><dt>4.1. <a href="#idm45510334965904">EasyMini Board</a></dt><dt>7.1. <a href="#idm45510334883664">AltosUI Main Window</a></dt><dt>7.2. <a href="#idm45510334869152">Flight Data Graph</a></dt><dt>7.3. <a href="#idm45510334863760">Flight Graph Configuration</a></dt><dt>7.4. <a href="#idm45510334859248">Flight Statistics</a></dt><dt>7.5. <a href="#idm45510334849584">Altimeter Configuration</a></dt><dt>7.6. <a href="#idm45510334815904">Configure AltosUI Dialog</a></dt><dt>7.7. <a href="#idm45510334797936">Fire Igniter Window</a></dt></dl></div><div class="list-of-tables"><p><strong>List of Tables</strong></p><dl><dt>3.1. <a href="#idm45510340510736">AltOS Modes</a></dt><dt>3.2. <a href="#idm45510335019088">Pad/Idle Indications</a></dt><dt>4.1. <a href="#idm45510334959888">EasyMini Screw Terminals</a></dt><dt>D.1. <a href="#idm45510334739984">Data Storage on Altus Metrum altimeters</a></dt><dt>E.1. <a href="#idm45510334720464">Altus Metrum Flight Computer Electronics</a></dt><dt>E.2. <a href="#idm45510334695696">Altus Metrum Flight Computer Mechanical Components</a></dt></dl></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="_introduction_and_overview"></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 v0.2 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. The latest version, TeleDongle +v3, has all new electronics with a higher performance radio +for improved range.</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 id="_getting_started"></a>Chapter 2. Getting Started</h1></div></div></div><p>The first thing to do after you open the box is to hook up a +battery and charge it if necessary.</p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_batteries"></a>2.1. Batteries</h2></div></div></div><p>The Lithium Polymer +EasyMini battery can be charged by disconnecting it +from the board and plugging it into a standalone +battery charger such as <a class="ulink" href="http://altusmetrum.org/LipoCharger" target="_top">LipoCharger</a>, 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 +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></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_linux_mac_windows_ground_station_software"></a>2.2. Linux/Mac/Windows Ground Station Software</h2></div></div></div><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, Mac OSX. 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></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="_using_altus_metrum_hardware"></a>Chapter 3. Using Altus Metrum Hardware</h1></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><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_wiring_and_electrical_interference"></a>3.1. Wiring and Electrical Interference</h2></div></div></div><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><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_hooking_up_lithium_polymer_batteries"></a>3.2. Hooking Up Lithium Polymer Batteries</h2></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><div class="warning" style="margin-left: 0; margin-right: 10%;"><h3 class="title">Warning</h3><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><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_hooking_up_pyro_charges"></a>3.3. Hooking Up Pyro Charges</h2></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><h2 class="title" style="clear: both"><a id="_hooking_up_a_power_switch"></a>3.4. Hooking Up a Power Switch</h2></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><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_understanding_beeps"></a>3.5. Understanding Beeps</h2></div></div></div><p>Altus Metrum flight computers include a beeper to +provide information about the state of the system.</p><p>Here’s a short summary of all of the modes and the +beeping +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 id="idm45510340510736"></a><p class="title"><strong>Table 3.1. AltOS Modes</strong></p><div class="table-contents"><table summary="AltOS Modes" cellpadding="4px" style="border-collapse: collapse;border-top: 1px solid #78079a; border-bottom: 1px solid #78079a; border-left: 1px solid #78079a; border-right: 1px solid #78079a; "><colgroup><col class="col_1" /><col class="col_2" /><col class="col_3" /><col class="col_4" /></colgroup><tbody><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Mode Name</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Abbreviation</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Beeps</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Description</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Startup</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>S</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>battery voltage in decivolts</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Calibrating sensors, detecting orientation.</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Idle</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>I</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>dit dit</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Ready to accept commands over USB</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Pad</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>P</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>dit dah dah dit</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Waiting for launch. Not listening for commands.</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Boost</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>B</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>dah dit dit dit</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Accelerating upwards.</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Fast</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>F</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>dit dit dah dit</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Decelerating, but moving faster than 200m/s.</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Coast</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>C</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>dah dit dah dit</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Decelerating, moving slower than 200m/s</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Drogue</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>D</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>dah dit dit</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Descending after apogee. Above main height.</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>M</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>dah dah</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Descending. Below main height.</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Landed</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>L</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>dit dah dit dit</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Stable altitude for at least ten seconds.</p></td></tr><tr><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>Sensor error</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>X</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>dah dit dit dah</p></td><td style="" align="left" valign="top"><p>Error detected during sensor calibration.</p></td></tr></tbody></table></div></div><br class="table-break" /><p>Here’s a summary of all of the Pad and Idle mode +indications. In Idle mode, you’ll hear one of these +just once after the two short dits indicating idle +mode. In Pad mode, after the dit dah dah dit +indicating Pad mode, you’ll hear these once every five +seconds.</p><div class="table"><a id="idm45510335019088"></a><p class="title"><strong>Table 3.2. Pad/Idle Indications</strong></p><div class="table-contents"><table summary="Pad/Idle Indications" cellpadding="4px" style="border-collapse: collapse;border-top: 1px solid #78079a; border-bottom: 1px solid #78079a; border-left: 1px solid #78079a; border-right: 1px solid #78079a; "><colgroup><col class="col_1" /><col class="col_2" /><col class="col_3" /></colgroup><thead><tr><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Name </th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Beeps </th><th style="border-bottom: 1px solid #78079a; " align="left" valign="top">Description</th></tr></thead><tbody><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Neither</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>brap</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>No continuity detected on either apogee or main igniters.</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>dit</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Continuity detected only on apogee igniter.</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>dit dit</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Continuity detected only on main igniter.</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Both</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>dit dit dit</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Continuity detected on both igniters.</p></td></tr><tr><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>Storage Full</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>warble</p></td><td style="" align="left" valign="top"><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><br class="table-break" /></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_turning_on_the_power"></a>3.6. Turning On the Power</h2></div></div></div><p>Connect a battery and power switch and turn the switch +to "on". The flight computer will signal power on by +reporting the battery voltage and then perform an internal self +test and sensor calibration.</p><p>Once the self test and calibration are complete, there +are two modes that an Altus Metrum flight computer can +operate in:</p><div class="variablelist"><dl class="variablelist"><dt><span class="term"> +Flight/Pad +</span></dt><dd> +The flight computer is waiting to detect +launch and then fly the rocket. In this mode, the USB +link is +disabled. +The only way to get out of this +mode is to power the flight computer down. +</dd><dt><span class="term"> +Idle +</span></dt><dd> +The flight computer is ready to communicate over USB +You can configure +the flight computer, download data or display +the current state. +</dd></dl></div><p>For EasyMini, if the USB cable is connected to a +computer, it will enter Idle mode. Otherwise, it will +enter Flight/Pad mode.</p><p>You can see in <a class="xref" href="#_understanding_beeps" title="3.5. Understanding Beeps">Section 3.5, “Understanding Beeps”</a> +how to tell which mode the flight computer is in.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_using_an_external_active_switch_circuit"></a>3.7. Using an External Active Switch Circuit</h2></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. Then follow +the instructions that come with your active switch to +connect it up.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_using_a_separate_pyro_battery"></a>3.8. Using a Separate Pyro Battery</h2></div></div></div><p>As mentioned above in <a class="xref" href="#_hooking_up_pyro_charges" title="3.3. Hooking Up Pyro Charges">Section 3.3, “Hooking Up Pyro Charges”</a>, 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 for each flight computer will be found +in the section below for that flight computer.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_using_a_different_kind_of_battery"></a>3.9. Using a Different Kind of Battery</h2></div></div></div><p>EasyMini +is +designed to use either a +lithium polymer battery or any other battery producing +between 4 and 12 volts, such as a rectangular 9V +battery.</p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="_easymini"></a>Chapter 4. EasyMini</h1></div></div></div><div class="figure"><a id="idm45510334965904"></a><p class="title"><strong>Figure 4.1. EasyMini Board</strong></p><div class="figure-contents"><div class="mediaobject"><img src="easymini-top.jpg" width="495" alt="easymini-top.jpg" /></div></div></div><br class="figure-break" /><p>EasyMini is built on a 0.8 inch by 1½ inch circuit board. It’s +designed to fit in a 24mm coupler tube.</p><p>You usually don’t need to configure EasyMini at all; it’s set +up to do dual-deployment with an event at apogee to separate +the airframe and deploy a drogue and another event at 250m +(820ft) to deploy the main. Install EasyMini in your airframe, +hook up a battery, igniters and a power switch and you’re +ready to fly.</p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_easymini_screw_terminals"></a>4.1. EasyMini Screw Terminals</h2></div></div></div><p>EasyMini has two sets of four screw terminals near one end of the +board. 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 id="idm45510334959888"></a><p class="title"><strong>Table 4.1. EasyMini Screw Terminals</strong></p><div class="table-contents"><table summary="EasyMini Screw Terminals" cellpadding="4px" style="border-collapse: collapse;border-top: 1px solid #78079a; border-bottom: 1px solid #78079a; border-left: 1px solid #78079a; border-right: 1px solid #78079a; "><colgroup><col class="col_1" /><col class="col_2" /><col class="col_3" /></colgroup><thead><tr><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Terminal #</th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Terminal Name</th><th style="border-bottom: 1px solid #78079a; " align="left" valign="top">Description</th></tr></thead><tbody><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 1</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main -</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main pyro channel connection to pyro circuit</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 2</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main pyro channel common connection to battery</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 3</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Battery</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Positive external battery terminal</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 4</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Battery -</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Negative external battery terminal</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Bottom 1</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee -</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee pyro channel connection to pyro circuit</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Bottom 2</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee pyro channel common connection to battery</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Bottom 3</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Switch Output</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Switch connection to flight computer</p></td></tr><tr><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>Bottom 4</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>Switch Input</p></td><td style="" align="left" valign="top"><p>Switch connection to positive battery terminal</p></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 id="_connecting_a_battery_to_easymini"></a>4.2. Connecting A Battery To EasyMini</h2></div></div></div><p>There are two possible battery connections on +EasyMini. You can use either method; both feed +through the power switch terminals.</p><p>One battery connection is the standard Altus Metrum +white JST plug. This mates with single-cell Lithium +Polymer batteries sold by Altus Metrum.</p><p>The other is a pair of screw terminals marked <span class="emphasis"><em>Battery ++</em></span> and <span class="emphasis"><em>Battery -</em></span>. Connect a battery from 4 to 12 +volts to these terminals, being careful to match polarity.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_charging_lithium_batteries"></a>4.3. Charging Lithium Batteries</h2></div></div></div><p>Because EasyMini allows for batteries other than the +standard Altus Metrum Lithium Polymer cells, it cannot +incorporate a battery charger circuit. Therefore, when +using a Litium Polymer cell, you’ll need an external +charger. These are available from Altus Metrum, or +from Spark Fun.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_using_a_separate_pyro_battery_with_easymini"></a>4.4. Using a Separate Pyro Battery with EasyMini</h2></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 EasyMini +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><h2 class="title" style="clear: both"><a id="_using_an_active_switch_with_easymini"></a>4.5. Using an Active Switch with EasyMini</h2></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="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="_installation"></a>Chapter 5. Installation</h1></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. +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; you +can purchase suitable batteries from the any vendor selling +Altus Metrum products. 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.</p><div class="warning" style="margin-left: 0; margin-right: 10%;"><h3 class="title">Warning</h3><p>Check polarity and voltage before connecting any battery not +purchased from Altus Metrum.</p></div><div class="warning" style="margin-left: 0; margin-right: 10%;"><h3 class="title">Warning</h3><p>Spark Fun sells batteries that have a matching connector with +the correct polarity. However, these batteries include an +integrated current limiting circuit. That circuit will cause +the battery to shut down when firing the igniter circuit. Do +not use these batteries unless you remove the current limiting +circuit.</p></div><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 +<a class="xref" href="#_using_a_separate_pyro_battery" title="3.8. Using a Separate Pyro Battery">Section 3.8, “Using a Separate Pyro Battery”</a> 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. +The screw terminal block is also used for the power switch leads.</p></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="_using_altus_metrum_products"></a>Chapter 6. Using Altus Metrum Products</h1></div></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_in_the_rocket"></a>6.1. 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. +A 110mAh battery weighs less +than a triple A battery and is a good choice for use +with +EasyMini.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_on_the_ground"></a>6.2. On the Ground</h2></div></div></div><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>After the flight, +you can use a +USB cable to plug into the flight computer board directly. +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></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_data_analysis"></a>6.3. 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 flight log in a format 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 id="_future_plans"></a>6.4. Future Plans</h2></div></div></div><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 id="_altosui"></a>Chapter 7. AltosUI</h1></div></div></div><div class="figure"><a id="idm45510334883664"></a><p class="title"><strong>Figure 7.1. AltosUI Main Window</strong></p><div class="figure-contents"><div class="mediaobject"><img src="altosui.png" width="414" alt="altosui.png" /></div></div></div><br class="figure-break" /><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 id="_save_flight_data"></a>7.1. Save Flight Data</h2></div></div></div><p>The altimeter records flight data to its internal +flash memory. +The <span class="emphasis"><em>Save Flight Data</em></span> button allows you to +read the flash memory and write it to disk.</p><p>Clicking on the <span class="emphasis"><em>Save Flight Data</em></span> 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.</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 id="_replay_flight"></a>7.2. 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.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_graph_data"></a>7.3. 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 id="_flight_graph"></a>7.3.1. Flight Graph</h3></div></div></div><div class="figure"><a id="idm45510334869152"></a><p class="title"><strong>Figure 7.2. Flight Data Graph</strong></p><div class="figure-contents"><div class="mediaobject"><img src="graph.png" width="495" alt="graph.png" /></div></div></div><br class="figure-break" /><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 id="_configure_graph"></a>7.3.2. Configure Graph</h3></div></div></div><div class="figure"><a id="idm45510334863760"></a><p class="title"><strong>Figure 7.3. Flight Graph Configuration</strong></p><div class="figure-contents"><div class="mediaobject"><img src="graph-configure.png" width="495" alt="graph-configure.png" /></div></div></div><br class="figure-break" /><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 id="_flight_statistics"></a>7.3.3. Flight Statistics</h3></div></div></div><div class="figure"><a id="idm45510334859248"></a><p class="title"><strong>Figure 7.4. Flight Statistics</strong></p><div class="figure-contents"><div class="mediaobject"><img src="graph-stats.png" width="495" alt="graph-stats.png" /></div></div></div><br class="figure-break" /><p>Shows overall data computed from the flight.</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_export_data"></a>7.4. 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.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_comma_separated_value_format"></a>7.4.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 <span class="emphasis"><em>#</em></span> 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><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_configure_altimeter"></a>7.5. Configure Altimeter</h2></div></div></div><div class="figure"><a id="idm45510334849584"></a><p class="title"><strong>Figure 7.5. Altimeter Configuration</strong></p><div class="figure-contents"><div class="mediaobject"><img src="configure-altimeter.png" width="324" alt="configure-altimeter.png" /></div></div></div><br class="figure-break" /><p>Select this button and then select an 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> +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. +</dd><dt><span class="term"> +Reset +</span></dt><dd> +This resets the dialog to the most recently saved +values, erasing any changes you have made. +</dd><dt><span class="term"> +Reboot +</span></dt><dd> +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. +</dd><dt><span class="term"> +Close +</span></dt><dd> +This closes the dialog. Any unsaved changes will be +lost. +</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 id="_main_deploy_altitude"></a>7.5.1. Main Deploy Altitude</h3></div></div></div><p>This sets the altitude (above the recorded pad +altitude) at which the <span class="emphasis"><em>main</em></span> 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 id="_apogee_delay"></a>7.5.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 id="_apogee_lockout"></a>7.5.3. 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 <span class="emphasis"><em>Mach Delay</em></span>, 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 id="_maximum_flight_log_size"></a>7.5.4. 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 id="_ignitor_firing_mode"></a>7.5.5. 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> +This is the usual mode of operation; the +<span class="emphasis"><em>apogee</em></span> channel is fired at apogee and the +<span class="emphasis"><em>main</em></span> channel at the height above ground +specified by the <span class="emphasis"><em>Main Deploy Altitude</em></span> during +descent. +</dd><dt><span class="term"> +Redundant Apogee +</span></dt><dd> +This fires both channels at apogee, the +<span class="emphasis"><em>apogee</em></span> channel first followed after a two +second delay by the <span class="emphasis"><em>main</em></span> channel. +</dd><dt><span class="term"> +Redundant Main +</span></dt><dd> +This fires both channels at the height above +ground specified by the Main Deploy Altitude +setting during descent. The <span class="emphasis"><em>apogee</em></span> channel +is fired first, followed after a two second +delay by the <span class="emphasis"><em>main</em></span> channel. +</dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_beeper_frequency"></a>7.5.6. 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><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_configure_altosui"></a>7.6. Configure AltosUI</h2></div></div></div><div class="figure"><a id="idm45510334815904"></a><p class="title"><strong>Figure 7.6. Configure AltosUI Dialog</strong></p><div class="figure-contents"><div class="mediaobject"><img src="configure-altosui.png" width="216" alt="configure-altosui.png" /></div></div></div><br class="figure-break" /><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 id="_log_directory"></a>7.6.1. Log Directory</h3></div></div></div><p>AltosUI logs all telemetry data and saves all +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 <span class="emphasis"><em>Select Directory</em></span> to +change where AltosUI reads and writes data +files.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_imperial_units"></a>7.6.2. 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 id="_serial_debug"></a>7.6.3. 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 id="_font_size"></a>7.6.4. 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 id="_look_amp_feel"></a>7.6.5. Look & feel</h3></div></div></div><p>Switches between the available Java user +interface appearances. The default selection +is supposed to match the native window system +appearance for the target platform.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_menu_position"></a>7.6.6. Menu position</h3></div></div></div><p>Selects the initial position for the main +AltosUI window that includes all of the +command buttons.</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_flash_image"></a>7.7. Flash Image</h2></div></div></div><p>This reprograms Altus Metrum devices with new +firmware. +EasyMini is +programmed directly +over USB (self programming). Please read +the directions for flashing devices in +<a class="xref" href="#_updating_device_firmware" title="Appendix C. Updating Device Firmware">Appendix C, <em>Updating Device Firmware</em></a>.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_fire_igniter"></a>7.8. Fire Igniter</h2></div></div></div><div class="figure"><a id="idm45510334797936"></a><p class="title"><strong>Figure 7.7. Fire Igniter Window</strong></p><div class="figure-contents"><div class="mediaobject"><img src="fire-igniter.png" width="108" alt="fire-igniter.png" /></div></div></div><br class="figure-break" /><p>This activates the igniter circuits in the flight +computer to help test recovery systems +deployment.</p><p>Selecting the <span class="emphasis"><em>Fire Igniter</em></span> 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 <span class="emphasis"><em>Arm</em></span> button.</p><p>Select the <span class="emphasis"><em>Arm</em></span> button. This enables the <span class="emphasis"><em>Fire</em></span> +button. The word <span class="emphasis"><em>Arm</em></span> is replaced by a countdown +timer indicating that you have 10 seconds to press the +<span class="emphasis"><em>Fire</em></span> button or the system will deactivate, at which +point you start over again at selecting the desired +igniter.</p></div></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a id="_system_operation"></a>Appendix A. System Operation</h1></div></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_firmware_modes"></a>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. +Since +EasyMini doesn’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.</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>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. +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>See <a class="xref" href="#_understanding_beeps" title="3.5. Understanding Beeps">Section 3.5, “Understanding Beeps”</a> for a summary of all of +the audio signals used.</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></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_ground_testing"></a>A.2. 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.</p><p>Just prep the rocket for flight, then power up the altimeter +in “idle” +mode. +You can now command the altimeter to fire the apogee +or main charges from a safe distance using your +computer 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 id="_configurable_parameters"></a>A.3. 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”. All of the +configurable parameters can be set using AltosUI. Read +<a class="xref" href="#_configure_altimeter" title="7.5. Configure Altimeter">Section 7.5, “Configure Altimeter”</a> for more information.</p></div></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a id="_handling_precautions"></a>Appendix B. 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><div class="warning" style="margin-left: 0; margin-right: 10%;"><h3 class="title">Warning</h3><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></div><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="appendix"><div class="titlepage"><div><div><h1 class="title"><a id="_updating_device_firmware"></a>Appendix C. Updating Device Firmware</h1></div></div></div><p>EasyMini is +programmed directly over their USB connectors (self +programming).</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><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_updating_easymini_firmware"></a>C.1. Updating EasyMini Firmware</h2></div></div></div><p>Self-programmable devices are reprogrammed by +connecting them to your computer over USB.</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"> +Attach a battery if necessary and power switch to +the target device. Power up the device. +</li><li class="listitem"> +Using a Micro USB cable, connect the target device to your +computer’s USB socket. +</li><li class="listitem"> +Run AltosUI, and select <span class="emphasis"><em>Flash Image</em></span> from the File menu. +</li><li class="listitem"> +Select the target device in the Device Selection dialog. +</li><li class="listitem"> +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 EasyMini-v1.0-1.6.0.ihx. +</li><li class="listitem"> +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. +</li><li class="listitem"> +Hit the <span class="emphasis"><em>OK</em></span> button and the software should proceed +to flash the device with new firmware, showing a +progress bar. +</li><li class="listitem"> +Verify that the device is working by using the +<span class="emphasis"><em>Configure Altimeter</em></span> or <span class="emphasis"><em>Configure Groundstation</em></span> +item to check over the configuration. +</li></ol></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_recovering_from_self_flashing_failure"></a>C.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"> +EasyMini +</span></dt><dd> +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. +</dd></dl></div><p>Once you’ve located the right pins:</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"> +Turn the altimeter power off. +</li><li class="listitem"> +Connect a battery. +</li><li class="listitem"> +Connect the indicated terminals together with a +short piece of wire. Take care not to accidentally +connect anything else. +</li><li class="listitem"> +Connect USB +</li><li class="listitem"> +Turn the board power on. +</li></ol></div><p>The board should now be visible over USB as +<span class="emphasis"><em>AltosFlash</em></span> and be ready to receive firmware. Once +the board has been powered up, you can remove the +piece of wire.</p></div></div></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a id="_flight_data_recording"></a>Appendix D. Flight Data Recording</h1></div></div></div><p>Each flight computer logs data at 100 samples per second +during ascent and 10 samples per second during +descent. +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 id="idm45510334739984"></a><p class="title"><strong>Table D.1. Data Storage on Altus Metrum altimeters</strong></p><div class="table-contents"><table summary="Data Storage on Altus Metrum altimeters" cellpadding="4px" style="border-collapse: collapse;border-top: 1px solid #78079a; border-bottom: 1px solid #78079a; border-left: 1px solid #78079a; border-right: 1px solid #78079a; "><colgroup><col class="col_1" /><col class="col_2" /><col class="col_3" /><col class="col_4" /></colgroup><thead><tr><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Device </th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Bytes per Sample </th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Total Storage </th><th style="border-bottom: 1px solid #78079a; " align="left" valign="top">Minutes at Full Rate</th></tr></thead><tbody><tr><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>EasyMini</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>16</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>1MB</p></td><td style="" align="left" valign="top"><p>10</p></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 +EasyMini. +This consumes 64kB +of flash space. This configuration space is not available +for storing flight log 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.</p><p>The default size allows for several flights on each flight +computer. +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="appendix"><div class="titlepage"><div><div><h1 class="title"><a id="_altus_metrum_hardware_specifications"></a>Appendix E. Altus Metrum Hardware Specifications</h1></div></div></div><p>Here’s the full set of Altus Metrum products, both in +production and retired.</p><div class="table"><a id="idm45510334720464"></a><p class="title"><strong>Table E.1. Altus Metrum Flight Computer Electronics</strong></p><div class="table-contents"><table summary="Altus Metrum Flight Computer Electronics" cellpadding="4px" style="border-collapse: collapse;border-top: 1px solid #78079a; border-bottom: 1px solid #78079a; border-left: 1px solid #78079a; border-right: 1px solid #78079a; "><colgroup><col class="col_1" /><col class="col_2" /><col class="col_3" /><col class="col_4" /><col class="col_5" /><col class="col_6" /><col class="col_7" /><col class="col_8" /></colgroup><thead><tr><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Device </th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"> Barometer </th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"> Z-axis accel </th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"> GPS </th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"> 3D sensors </th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"> Storage </th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"> RF Output </th><th style="border-bottom: 1px solid #78079a; " align="left" valign="top"> Battery</th></tr></thead><tbody><tr><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>EasyMini v1.0</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>MS5607 30km (100k')</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>-</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>-</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>-</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>1MB</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>-</p></td><td style="" align="left" valign="top"><p>3.7-12V</p></td></tr></tbody></table></div></div><br class="table-break" /><p></p><div class="table"><a id="idm45510334695696"></a><p class="title"><strong>Table E.2. Altus Metrum Flight Computer Mechanical Components</strong></p><div class="table-contents"><table summary="Altus Metrum Flight Computer Mechanical Components" cellpadding="4px" style="border-collapse: collapse;border-top: 1px solid #78079a; border-bottom: 1px solid #78079a; border-left: 1px solid #78079a; border-right: 1px solid #78079a; "><colgroup><col class="col_1" /><col class="col_2" /><col class="col_3" /><col class="col_4" /><col class="col_5" /><col class="col_6" /></colgroup><thead><tr><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Device</th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Connectors</th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Screw Terminals</th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Width</th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Length</th><th style="border-bottom: 1px solid #78079a; " align="left" valign="top">Tube Size</th></tr></thead><tbody><tr><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>EasyMini</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>Debug USB Battery</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>Apogee pyro Main pyro Battery</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>0.8 inch (2.03cm)</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>1½ inch (3.81cm)</p></td><td style="" align="left" valign="top"><p>24mm coupler</p></td></tr></tbody></table></div></div><br class="table-break" /></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a id="_release_notes"></a>Appendix F. Release Notes</h1></div></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_6_2"></a>F.1. Release Notes for Version 1.6.2</h2></div></div></div><p>Version 1.6.2 includes support for our updated TeleMega v2.0 +product and bug fixes in in the flight software for all our boards +and ground station interfaces.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos"></a>F.1.1. AltOS</h3></div></div></div><p>AltOS New Features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Add support for TeleMega v2.0 boards. +</li><li class="listitem"> +Add PWM servo driver. There’s no higher level code using +this yet, but the driver allows testing of the TeleMega v2.0 +servo output connector. +</li></ul></div><p>AltOS Fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Slow down telemetry packets to allow receiver to keep +up. +</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_and_telegps_applications"></a>F.1.2. AltosUI and TeleGPS Applications</h3></div></div></div><p>AltosUI and TeleGPS Fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Fix post-flight orientation computation when processing +TeleMega and EasyMega eeprom data files. +</li><li class="listitem"> +Capture complete eeprom data even when there are invalid +entries in the data. This keeps reading eeprom contents and +writing the associated .eeprom file when an error is detected. +</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_documentation"></a>F.1.3. Documentation</h3></div></div></div><p>We spent a bunch of time trying to improve our documentation</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +HTML versions now have a table of contents on the left side. +</li><li class="listitem"> +EasyMini now has its own shorter manual. +</li><li class="listitem"> +Provide links between sections in each document. +</li><li class="listitem"> +Lots of minor rewriting and restructuring to avoid +duplication of information +</li></ul></div></div></div></div></div></body></html>
\ No newline at end of file diff --git a/AltOS/doc/easymini.pdf b/AltOS/doc/easymini.pdf Binary files differnew file mode 100644 index 0000000..fec1330 --- /dev/null +++ b/AltOS/doc/easymini.pdf diff --git a/AltOS/doc/fonts/DejaVuSansMono-Bold.ttf b/AltOS/doc/fonts/DejaVuSansMono-Bold.ttf Binary files differnew file mode 100644 index 0000000..1085a73 --- /dev/null +++ b/AltOS/doc/fonts/DejaVuSansMono-Bold.ttf diff --git a/AltOS/doc/fonts/DejaVuSansMono-BoldOblique.ttf b/AltOS/doc/fonts/DejaVuSansMono-BoldOblique.ttf Binary files differnew file mode 100644 index 0000000..3175ebf --- /dev/null +++ b/AltOS/doc/fonts/DejaVuSansMono-BoldOblique.ttf diff --git a/AltOS/doc/fonts/DejaVuSansMono-Oblique.ttf b/AltOS/doc/fonts/DejaVuSansMono-Oblique.ttf Binary files differnew file mode 100644 index 0000000..d5d6f92 --- /dev/null +++ b/AltOS/doc/fonts/DejaVuSansMono-Oblique.ttf diff --git a/AltOS/doc/fonts/DejaVuSansMono.ttf b/AltOS/doc/fonts/DejaVuSansMono.ttf Binary files differnew file mode 100644 index 0000000..05e2345 --- /dev/null +++ b/AltOS/doc/fonts/DejaVuSansMono.ttf diff --git a/AltOS/doc/fonts/OpenSans-Italic.ttf b/AltOS/doc/fonts/OpenSans-Italic.ttf Binary files differnew file mode 100644 index 0000000..c90da48 --- /dev/null +++ b/AltOS/doc/fonts/OpenSans-Italic.ttf diff --git a/AltOS/doc/fonts/OpenSans-Light.ttf b/AltOS/doc/fonts/OpenSans-Light.ttf Binary files differnew file mode 100644 index 0000000..0d38189 --- /dev/null +++ b/AltOS/doc/fonts/OpenSans-Light.ttf diff --git a/AltOS/doc/fonts/OpenSans-LightItalic.ttf b/AltOS/doc/fonts/OpenSans-LightItalic.ttf Binary files differnew file mode 100644 index 0000000..68299c4 --- /dev/null +++ b/AltOS/doc/fonts/OpenSans-LightItalic.ttf diff --git a/AltOS/doc/fonts/OpenSans-Regular.ttf b/AltOS/doc/fonts/OpenSans-Regular.ttf Binary files differnew file mode 100644 index 0000000..db43334 --- /dev/null +++ b/AltOS/doc/fonts/OpenSans-Regular.ttf diff --git a/AltOS/doc/fonts/OpenSans-Semibold.ttf b/AltOS/doc/fonts/OpenSans-Semibold.ttf Binary files differnew file mode 100644 index 0000000..1a7679e --- /dev/null +++ b/AltOS/doc/fonts/OpenSans-Semibold.ttf diff --git a/AltOS/doc/fonts/OpenSans-SemiboldItalic.ttf b/AltOS/doc/fonts/OpenSans-SemiboldItalic.ttf Binary files differnew file mode 100644 index 0000000..59b6d16 --- /dev/null +++ b/AltOS/doc/fonts/OpenSans-SemiboldItalic.ttf diff --git a/AltOS/doc/micropeak-nofont.svg b/AltOS/doc/micropeak-nofont.svg new file mode 100644 index 0000000..5e96b58 --- /dev/null +++ b/AltOS/doc/micropeak-nofont.svg @@ -0,0 +1,224 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<!-- Created with Inkscape (http://www.inkscape.org/) --> + +<svg + xmlns:dc="http://purl.org/dc/elements/1.1/" + xmlns:cc="http://creativecommons.org/ns#" + xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" + xmlns:svg="http://www.w3.org/2000/svg" + xmlns="http://www.w3.org/2000/svg" + xmlns:xlink="http://www.w3.org/1999/xlink" + xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd" + xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape" + width="45.75" + height="50.5" + id="svg2" + version="1.1" + inkscape:version="0.48.3.1 r9886" + sodipodi:docname="micropeak-nofont.svg"> + <defs + id="defs4"> + <linearGradient + id="linearGradient5343"> + <stop + style="stop-color:#7200a4;stop-opacity:1;" + offset="0" + id="stop5345" /> + <stop + style="stop-color:#da7000;stop-opacity:1;" + offset="1" + id="stop5347" /> + </linearGradient> + <marker + inkscape:stockid="Arrow2Send" + orient="auto" + refY="0" + refX="0" + id="Arrow2Send" + style="overflow:visible"> + <path + id="path3798" + style="fill-rule:evenodd;stroke-width:0.625;stroke-linejoin:round" + d="M 8.7185878,4.0337352 -2.2072895,0.01601326 8.7185884,-4.0017078 c -1.7454984,2.3720609 -1.7354408,5.6174519 -6e-7,8.035443 z" + transform="matrix(-0.3,0,0,-0.3,0.69,0)" + inkscape:connector-curvature="0" /> + </marker> + <marker + inkscape:stockid="Arrow1Send" + orient="auto" + refY="0" + refX="0" + id="Arrow1Send" + style="overflow:visible"> + <path + id="path3780" + d="M 0,0 5,-5 -12.5,0 5,5 0,0 z" + style="fill-rule:evenodd;stroke:#000000;stroke-width:1pt" + transform="matrix(-0.2,0,0,-0.2,-1.2,0)" + inkscape:connector-curvature="0" /> + </marker> + <marker + inkscape:stockid="Arrow2Mend" + orient="auto" + refY="0" + refX="0" + id="Arrow2Mend" + style="overflow:visible"> + <path + id="path3792" + style="fill-rule:evenodd;stroke-width:0.625;stroke-linejoin:round" + d="M 8.7185878,4.0337352 -2.2072895,0.01601326 8.7185884,-4.0017078 c -1.7454984,2.3720609 -1.7354408,5.6174519 -6e-7,8.035443 z" + transform="scale(-0.6,-0.6)" + inkscape:connector-curvature="0" /> + </marker> + <marker + inkscape:stockid="Arrow1Lend" + orient="auto" + refY="0" + refX="0" + id="Arrow1Lend" + style="overflow:visible"> + <path + id="path3768" + d="M 0,0 5,-5 -12.5,0 5,5 0,0 z" + style="fill-rule:evenodd;stroke:#000000;stroke-width:1pt" + transform="matrix(-0.8,0,0,-0.8,-10,0)" + inkscape:connector-curvature="0" /> + </marker> + <marker + inkscape:stockid="Arrow2Lend" + orient="auto" + refY="0" + refX="0" + id="Arrow2Lend" + style="overflow:visible"> + <path + id="path3786" + style="fill-rule:evenodd;stroke-width:0.625;stroke-linejoin:round" + d="M 8.7185878,4.0337352 -2.2072895,0.01601326 8.7185884,-4.0017078 c -1.7454984,2.3720609 -1.7354408,5.6174519 -6e-7,8.035443 z" + transform="matrix(-1.1,0,0,-1.1,-1.1,0)" + inkscape:connector-curvature="0" /> + </marker> + <linearGradient + inkscape:collect="always" + xlink:href="#linearGradient5343" + id="linearGradient5349" + x1="255.48561" + y1="275.90405" + x2="280.61411" + y2="275.90405" + gradientUnits="userSpaceOnUse" /> + </defs> + <sodipodi:namedview + id="base" + pagecolor="#ffffff" + bordercolor="#666666" + borderopacity="1.0" + inkscape:pageopacity="0.0" + inkscape:pageshadow="2" + inkscape:zoom="16.321712" + inkscape:cx="39.182144" + inkscape:cy="19.678463" + inkscape:document-units="px" + inkscape:current-layer="layer1" + showgrid="false" + inkscape:window-width="1871" + inkscape:window-height="1383" + inkscape:window-x="653" + inkscape:window-y="147" + inkscape:window-maximized="0" + fit-margin-top="0" + fit-margin-left="0" + fit-margin-right="0" + fit-margin-bottom="0" /> + <metadata + id="metadata7"> + <rdf:RDF> + <cc:Work + rdf:about=""> + <dc:format>image/svg+xml</dc:format> + <dc:type + rdf:resource="http://purl.org/dc/dcmitype/StillImage" /> + <dc:title /> + </cc:Work> + </rdf:RDF> + </metadata> + <g + inkscape:label="Layer 1" + inkscape:groupmode="layer" + id="layer1" + transform="translate(-241.93841,-252.5196)"> + <g + style="font-size:16px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;line-height:125%;letter-spacing:0px;word-spacing:0px;fill:#7200a4;fill-opacity:1;stroke:none;font-family:Minion Pro;-inkscape-font-specification:Minion Pro" + id="text2985"> + <path + d="m 257.20241,268.30647 c 0,-1.07999 -0.396,-1.872 -1.584,-1.872 -1.188,0 -1.584,0.79201 -1.584,1.872 l 0,8.676 c 0,2.88 -2.052,5.112 -4.824,5.112 -3.06,0 -4.104,-1.872 -4.104,-5.076 l 0,-8.712 c 0,-1.07999 -0.396,-1.872 -1.584,-1.872 -1.188,0 -1.584,0.79201 -1.584,1.872 l 0,21.924 c 0,1.08 0.396,1.872 1.584,1.872 1.188,0 1.584,-0.792 1.584,-1.872 l 0,-6.156 c 0.792,0.612 2.088,0.972 3.564,0.972 2.304,0 4.428,-0.792 5.652,-2.988 l 0.072,0.072 0,1.26 c 0,0.864 0.54,1.44 1.404,1.44 0.864,0 1.404,-0.576 1.404,-1.44 l 0,-15.084" + style="font-size:36px;font-weight:500;text-align:start;line-height:125%;writing-mode:lr-tb;text-anchor:start;fill:#7200a4;font-family:ITC Benguiat Gothic Std;-inkscape-font-specification:ITC Benguiat Gothic Std Medium" + id="path3003" + inkscape:connector-curvature="0" /> + </g> + <path + style="fill:none;stroke:url(#linearGradient5349);stroke-width:2.9000001;stroke-linecap:round;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;marker-end:none" + d="m 256.93561,290.70327 c 3.04022,-0.24413 4.30317,-2.66932 5.38268,-5.56604 1.68059,-4.50963 3.67214,-15.86904 8.62227,-20.55527 4.0668,-3.85 8.22354,-3.46656 8.22354,-3.46656" + id="path2991" + inkscape:connector-curvature="0" + sodipodi:nodetypes="cssc" /> + <path + sodipodi:type="star" + style="fill:none;stroke:#da7000;stroke-width:1.10000002;stroke-linecap:round;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none" + id="path5341" + sodipodi:sides="5" + sodipodi:cx="279.29056" + sodipodi:cy="261.05426" + sodipodi:r1="7.2514729" + sodipodi:r2="3.6257365" + sodipodi:arg1="1.0731354" + sodipodi:arg2="1.7014539" + inkscape:flatsided="false" + inkscape:rounded="0" + inkscape:randomized="0" + d="m 282.7522,267.42614 -3.93403,-2.77705 -4.51792,1.66641 1.42544,-4.59964 -2.98096,-3.78185 4.815,-0.0657 2.67559,-4.00372 1.55039,4.55904 4.63457,1.30742 -3.85681,2.88333 z" + inkscape:transform-center-x="-0.29194889" + inkscape:transform-center-y="-0.40889198" /> + <g + style="font-size:10px;font-style:normal;font-variant:normal;font-weight:bold;font-stretch:normal;text-align:start;line-height:125%;letter-spacing:0px;word-spacing:0px;writing-mode:lr-tb;text-anchor:start;fill:#7200a4;fill-opacity:1;stroke:none;font-family:ITC Benguiat Gothic Std;-inkscape-font-specification:ITC Benguiat Gothic Std Bold" + id="text5351"> + <path + d="m 245.09283,298.56959 c -0.41,-0.49999 -0.65,-1.14 -0.99,-1.97 -0.16,-0.38999 -0.4,-0.55 -0.8,-0.55 -0.77,0 -0.8,0.59001 -0.96,1.55 -0.19,1.13 -0.36,3.09001 -0.36,4.23 0,0.7 0.05,1.16 0.62,1.16 0.56,0 0.64,-0.38 0.64,-0.85 l 0,-1.58 c 0,-0.86999 0.1,-1.77 0.24,-2.69 l 0.02,0 c 0.16,0.51 0.89,2.18 1.59,2.18 0.7,0 1.43,-1.67 1.59,-2.18 l 0.02,0 c 0.14,0.92 0.24,1.82001 0.24,2.69 l 0,1.58 c 0,0.47 0.08,0.85 0.64,0.85 0.57,0 0.62,-0.46 0.62,-1.16 0,-1.13999 -0.17,-3.1 -0.36,-4.23 -0.16,-0.95999 -0.19,-1.55 -0.96,-1.55 -0.4,0 -0.64,0.16001 -0.8,0.55 -0.34,0.83 -0.58,1.47001 -0.99,1.97" + id="path3006" + inkscape:connector-curvature="0" /> + <path + d="m 250.6994,298.46959 c 0,-0.35999 -0.19,-0.65 -0.6,-0.65 -0.41,0 -0.6,0.29001 -0.6,0.65 l 0,3.87 c 0,0.36 0.19,0.65 0.6,0.65 0.41,0 0.6,-0.29 0.6,-0.65 l 0,-3.87 m -0.6,-2.65 c -0.37,0 -0.66,0.26001 -0.66,0.74 0,0.48 0.29,0.74 0.66,0.74 0.37,0 0.66,-0.26 0.66,-0.74 0,-0.47999 -0.29,-0.74 -0.66,-0.74" + id="path3008" + inkscape:connector-curvature="0" /> + <path + d="m 253.96283,297.87959 c -1.31999,0 -2.16,1.00001 -2.16,2.19 0,1.35 1.04001,2.89 3.46,2.89 0.94,0 1.2,-0.17 1.2,-0.56 0,-0.44999 -0.2,-0.58 -1.03,-0.58 -1.33999,0 -2.31,-0.58 -2.31,-1.78 0,-0.51999 0.38,-1.02 1.08,-1.02 l 1.51,0 c 0.34,0 0.61,-0.18 0.61,-0.57 0,-0.38999 -0.27,-0.57 -0.61,-0.57 l -1.75,0" + id="path3010" + inkscape:connector-curvature="0" /> + <path + d="m 257.17283,302.30959 c 0,0.39 0.22,0.68 0.6,0.68 0.38,0 0.6,-0.29 0.6,-0.68 l 0,-2.19 c 0,-0.91999 0.29,-1.16 0.88,-1.16 0.43,0 0.69,-0.18 0.69,-0.56 0,-0.33999 -0.18,-0.58 -0.62,-0.58 -0.56,0 -0.94,0.24001 -1.02,0.79 l -0.02,0 -0.02,-0.31 c -0.04,-0.44999 -0.32,-0.48 -0.54,-0.48 -0.35,0 -0.55,0.20001 -0.55,0.61 l 0,3.88" + id="path3012" + inkscape:connector-curvature="0" /> + <path + d="m 265.06268,300.41959 c 0,-1.45999 -0.9,-2.6 -2.46,-2.6 -1.56,0 -2.46,1.14001 -2.46,2.6 0,1.46 0.9,2.6 2.46,2.6 1.56,0 2.46,-1.14 2.46,-2.6 m -1.26,0 c 0,0.8 -0.38,1.52 -1.2,1.52 -0.82,0 -1.2,-0.72 -1.2,-1.52 0,-0.79999 0.38,-1.52 1.2,-1.52 0.82,0 1.2,0.72001 1.2,1.52" + id="path3014" + inkscape:connector-curvature="0" /> + <path + d="m 266.07908,302.30959 c 0,0.38 0.2,0.68 0.63,0.68 0.43,0 0.63,-0.3 0.63,-0.68 l 0,-2.07 c 2.5,-0.67999 3.6,-1.44 3.6,-2.74 0,-0.83999 -0.54,-1.42 -1.58,-1.42 l -2.65,0 c -0.43,0 -0.63,0.22001 -0.63,0.54 l 0,5.69 m 1.26,-5.15 1.46,0 c 0.74,0 0.88,0.16 0.88,0.43 0,0.61 -1.68,1.31 -2.34,1.45 l 0,-1.88" + id="path3016" + inkscape:connector-curvature="0" /> + <path + d="m 275.53549,302.95959 c 0.32,0 0.58,-0.17 0.58,-0.54 0,-0.36999 -0.26,-0.54 -0.58,-0.54 l -1.29,0 c -0.84,0 -1.55,-0.25 -1.63,-1.19 l 3.06,0 c 0.42,0 0.49,-0.25 0.49,-0.59 0,-1.16999 -0.69,-2.28 -2.36,-2.28 -1.53,0 -2.51,1.17001 -2.51,2.67 0,1.49 1,2.47 2.78,2.47 l 1.46,0 m -2.84,-3.17 c 0.14,-0.59999 0.64,-0.97 1.11,-0.97 0.47,0 0.97,0.37001 1.1,0.97 l -2.21,0" + id="path3018" + inkscape:connector-curvature="0" /> + <path + d="m 281.2219,299.57959 c 0,-1.22999 -0.62,-1.7 -1.68,-1.7 l -1.75,0 c -0.33,0 -0.59,0.17001 -0.59,0.54 0,0.37 0.26,0.54 0.59,0.54 l 1.83,0 c 0.27,0 0.4,0.14001 0.4,0.65 l -0.42,0 c -1.17,0 -2.78,0.39001 -2.78,1.83 0,0.96 0.74,1.58 1.75,1.58 0.69,0 1.23,-0.18 1.55,-0.58 0.03,0.38 0.18,0.58 0.51,0.58 0.44,0 0.59,-0.25 0.59,-0.66 l 0,-2.78 m -1.14,1.57 c 0,0.57 -0.58,0.91 -1.14,0.91 -0.6,0 -0.92,-0.27 -0.92,-0.68 0,-0.46999 0.67,-0.87 2.06,-0.87 l 0,0.64" + id="path3020" + inkscape:connector-curvature="0" /> + <path + d="m 283.9183,300.21959 c 1.34,0.08 1.87,1.30001 1.85,1.87 -0.02,0.63 0.19,0.9 0.6,0.9 0.47,0 0.6,-0.33 0.6,-0.66 0,-0.75999 -0.24,-2.1 -1.66,-2.61 l 0,-0.02 c 0.68,-0.2 1.32,-0.79 1.32,-1.39 0,-0.28999 -0.2,-0.49 -0.54,-0.49 -0.21,0 -0.43,0.12 -0.58,0.39 -0.3,0.56 -0.82,0.94 -1.59,1.01 l 0,-2.72 c 0,-0.35999 -0.19,-0.65 -0.6,-0.65 -0.41,0 -0.6,0.29001 -0.6,0.65 l 0,5.84 c 0,0.36 0.19,0.65 0.6,0.65 0.41,0 0.6,-0.29 0.6,-0.65 l 0,-2.12" + id="path3022" + inkscape:connector-curvature="0" /> + </g> + </g> +</svg> diff --git a/AltOS/doc/micropeak-oneline.svg b/AltOS/doc/micropeak-oneline.svg new file mode 100644 index 0000000..4b69582 --- /dev/null +++ b/AltOS/doc/micropeak-oneline.svg @@ -0,0 +1,239 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<!-- Created with Inkscape (http://www.inkscape.org/) --> + +<svg + xmlns:dc="http://purl.org/dc/elements/1.1/" + xmlns:cc="http://creativecommons.org/ns#" + xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" + xmlns:svg="http://www.w3.org/2000/svg" + xmlns="http://www.w3.org/2000/svg" + xmlns:xlink="http://www.w3.org/1999/xlink" + xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd" + xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape" + width="444" + height="98" + id="svg2" + version="1.1" + inkscape:version="0.91 r13725" + sodipodi:docname="micropeak-oneline.svg"> + <defs + id="defs4"> + <linearGradient + id="linearGradient5343"> + <stop + style="stop-color:#7200a4;stop-opacity:1;" + offset="0" + id="stop5345" /> + <stop + style="stop-color:#da7000;stop-opacity:1;" + offset="1" + id="stop5347" /> + </linearGradient> + <marker + inkscape:stockid="Arrow2Send" + orient="auto" + refY="0" + refX="0" + id="Arrow2Send" + style="overflow:visible"> + <path + id="path3798" + style="fill-rule:evenodd;stroke-width:0.625;stroke-linejoin:round" + d="M 8.7185878,4.0337352 -2.2072895,0.01601326 8.7185884,-4.0017078 c -1.7454984,2.3720609 -1.7354408,5.6174519 -6e-7,8.035443 z" + transform="matrix(-0.3,0,0,-0.3,0.69,0)" + inkscape:connector-curvature="0" /> + </marker> + <marker + inkscape:stockid="Arrow1Send" + orient="auto" + refY="0" + refX="0" + id="Arrow1Send" + style="overflow:visible"> + <path + id="path3780" + d="M 0,0 5,-5 -12.5,0 5,5 0,0 Z" + style="fill-rule:evenodd;stroke:#000000;stroke-width:1pt" + transform="matrix(-0.2,0,0,-0.2,-1.2,0)" + inkscape:connector-curvature="0" /> + </marker> + <marker + inkscape:stockid="Arrow2Mend" + orient="auto" + refY="0" + refX="0" + id="Arrow2Mend" + style="overflow:visible"> + <path + id="path3792" + style="fill-rule:evenodd;stroke-width:0.625;stroke-linejoin:round" + d="M 8.7185878,4.0337352 -2.2072895,0.01601326 8.7185884,-4.0017078 c -1.7454984,2.3720609 -1.7354408,5.6174519 -6e-7,8.035443 z" + transform="scale(-0.6,-0.6)" + inkscape:connector-curvature="0" /> + </marker> + <marker + inkscape:stockid="Arrow1Lend" + orient="auto" + refY="0" + refX="0" + id="Arrow1Lend" + style="overflow:visible"> + <path + id="path3768" + d="M 0,0 5,-5 -12.5,0 5,5 0,0 Z" + style="fill-rule:evenodd;stroke:#000000;stroke-width:1pt" + transform="matrix(-0.8,0,0,-0.8,-10,0)" + inkscape:connector-curvature="0" /> + </marker> + <marker + inkscape:stockid="Arrow2Lend" + orient="auto" + refY="0" + refX="0" + id="Arrow2Lend" + style="overflow:visible"> + <path + id="path3786" + style="fill-rule:evenodd;stroke-width:0.625;stroke-linejoin:round" + d="M 8.7185878,4.0337352 -2.2072895,0.01601326 8.7185884,-4.0017078 c -1.7454984,2.3720609 -1.7354408,5.6174519 -6e-7,8.035443 z" + transform="matrix(-1.1,0,0,-1.1,-1.1,0)" + inkscape:connector-curvature="0" /> + </marker> + <linearGradient + inkscape:collect="always" + xlink:href="#linearGradient5343" + id="linearGradient5349" + x1="255.48561" + y1="275.90405" + x2="280.61411" + y2="275.90405" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.9246394,0,0,1.9246394,-200.29778,-270.16721)" /> + </defs> + <sodipodi:namedview + id="base" + pagecolor="#ffffff" + bordercolor="#666666" + borderopacity="1.0" + inkscape:pageopacity="0.0" + inkscape:pageshadow="2" + inkscape:zoom="2.8852983" + inkscape:cx="243.9235" + inkscape:cy="27.872251" + inkscape:document-units="px" + inkscape:current-layer="layer1" + showgrid="false" + inkscape:window-width="1871" + inkscape:window-height="1383" + inkscape:window-x="119" + inkscape:window-y="125" + inkscape:window-maximized="0" + fit-margin-top="0" + fit-margin-left="0" + fit-margin-right="0" + fit-margin-bottom="0" /> + <metadata + id="metadata7"> + <rdf:RDF> + <cc:Work + rdf:about=""> + <dc:format>image/svg+xml</dc:format> + <dc:type + rdf:resource="http://purl.org/dc/dcmitype/StillImage" /> + <dc:title></dc:title> + </cc:Work> + </rdf:RDF> + </metadata> + <g + inkscape:label="Layer 1" + inkscape:groupmode="layer" + id="layer1" + transform="translate(-241.93841,-205.0196)"> + <g + style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:30.79423141px;line-height:125%;font-family:'Minion Pro';-inkscape-font-specification:'Minion Pro';letter-spacing:0px;word-spacing:0px;fill:#7200a4;fill-opacity:1;stroke:none" + id="text2985" + transform="translate(23.408014,-22.546654)" /> + <path + style="fill:none;stroke:url(#linearGradient5349);stroke-width:5.58145428;stroke-linecap:round;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1;marker-end:none" + d="m 294.21061,289.33175 c 5.85134,-0.46986 8.28205,-5.13748 10.35972,-10.71262 3.23453,-8.67942 7.06755,-30.54218 16.59477,-39.56149 7.82712,-7.40985 15.82735,-6.67187 15.82735,-6.67187" + id="path2991" + inkscape:connector-curvature="0" + sodipodi:nodetypes="cssc" /> + <path + sodipodi:type="star" + style="fill:none;stroke:#da7000;stroke-width:2.11710358;stroke-linecap:round;stroke-linejoin:miter;stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1" + id="path5341" + sodipodi:sides="5" + sodipodi:cx="337.23586" + sodipodi:cy="232.26813" + sodipodi:r1="13.956471" + sodipodi:r2="6.9782352" + sodipodi:arg1="1.0731354" + sodipodi:arg2="1.7014539" + inkscape:flatsided="false" + inkscape:rounded="0" + inkscape:randomized="0" + d="m 343.89829,244.5317 -7.57159,-5.34482 -8.69538,3.20724 2.74347,-8.85265 -5.73728,-7.27871 9.26715,-0.12642 5.14955,-7.70573 2.98393,8.77452 8.91988,2.51631 -7.42297,5.54937 z" + inkscape:transform-center-x="-0.56191834" + inkscape:transform-center-y="-0.78695059" /> + <g + id="g4212" + style="fill:#78079a;fill-opacity:1"> + <path + inkscape:connector-curvature="0" + id="path4233" + style="font-style:normal;font-variant:normal;font-weight:500;font-stretch:normal;font-size:69.28701782px;line-height:125%;font-family:'ITC Benguiat Gothic Std';-inkscape-font-specification:'ITC Benguiat Gothic Std Medium';letter-spacing:0px;word-spacing:0px;fill:#78079a;fill-opacity:1;stroke:none;text-align:start;writing-mode:lr-tb;text-anchor:start" + d="m 271.3161,268.77261 c 0,-2.07861 -0.76216,-3.60293 -3.04863,-3.60293 -2.28647,0 -3.04863,1.52432 -3.04863,3.60293 l 0,16.69817 c 0,5.54296 -3.94936,9.83875 -9.28446,9.83875 -5.88939,0 -7.89872,-3.60292 -7.89872,-9.76946 l 0,-16.76746 c 0,-2.07861 -0.76215,-3.60293 -3.04862,-3.60293 -2.28648,0 -3.04863,1.52432 -3.04863,3.60293 l 0,42.19579 c 0,2.07861 0.76215,3.60293 3.04863,3.60293 2.28647,0 3.04862,-1.52432 3.04862,-3.60293 l 0,-11.84808 c 1.52432,1.17788 4.01865,1.87075 6.85942,1.87075 4.43437,0 8.5223,-1.52431 10.87806,-5.75082 l 0.13857,0.13857 0,2.42505 c 0,1.66289 1.03931,2.77148 2.7022,2.77148 1.66289,0 2.70219,-1.10859 2.70219,-2.77148 l 0,-29.03126 z" + transform="translate(23.40801,-22.54665)" /> + <g + style="fill:#78079a;fill-opacity:1" + id="g4200"> + <path + style="font-style:normal;font-variant:normal;font-weight:500;font-stretch:normal;font-size:medium;line-height:125%;font-family:'ITC Benguiat Gothic Std';-inkscape-font-specification:'ITC Benguiat Gothic Std Medium';text-align:start;letter-spacing:0px;word-spacing:0px;writing-mode:lr-tb;text-anchor:start;fill:#78079a;fill-opacity:1;stroke:none" + inkscape:connector-curvature="0" + id="path4236" + d="m 380.37736,256.92285 c 4.28006,0 10.5949,-13.68217 12.13853,-17.05008 l 0.14033,0 c 2.10495,11.50705 2.38561,23.15443 2.38561,34.02999 0,2.73644 0.77182,4.28007 3.08726,4.28007 2.10495,0 3.08726,-1.68396 3.08726,-4.28007 0,-9.54243 -1.82429,-30.31125 -3.71875,-38.94154 -0.49115,-2.38561 -1.75412,-5.47287 -4.06956,-5.47287 -3.92924,0 -5.54303,9.19161 -13.05068,19.71635 -7.50765,-10.52474 -9.12145,-19.71635 -13.05068,-19.71635 -2.31545,0 -3.57842,3.08726 -4.06957,5.47287 -1.89445,8.63029 -3.71874,29.39911 -3.71874,38.94154 0,2.59611 0.98231,4.28007 3.08726,4.28007 2.31544,0 3.08725,-1.54363 3.08725,-4.28007 0,-10.87556 0.28066,-22.52294 2.31545,-34.02999 l 0.14033,0 c 1.61379,3.36791 7.92864,17.05008 12.2087,17.05008 z" /> + <path + style="font-style:normal;font-variant:normal;font-weight:500;font-stretch:normal;font-size:medium;line-height:125%;font-family:'ITC Benguiat Gothic Std';-inkscape-font-specification:'ITC Benguiat Gothic Std Medium';text-align:start;letter-spacing:0px;word-spacing:0px;writing-mode:lr-tb;text-anchor:start;fill:#78079a;fill-opacity:1;stroke:none" + inkscape:connector-curvature="0" + id="path4238" + d="m 416.62852,245.76662 c 0,-2.10495 -0.77182,-3.64858 -3.08726,-3.64858 -2.31544,0 -3.08726,1.54363 -3.08726,3.64858 l 0,28.76763 c 0,2.10495 0.77182,3.64858 3.08726,3.64858 2.31544,0 3.08726,-1.54363 3.08726,-3.64858 l 0,-28.76763 z m -3.08726,-15.64678 c -2.24528,0 -3.29775,1.96462 -3.29775,4.06956 0,2.10495 1.05247,4.06957 3.29775,4.06957 2.24528,0 3.29775,-1.96462 3.29775,-4.06957 0,-2.10494 -1.05247,-4.06956 -3.29775,-4.06956 z" /> + <path + style="font-style:normal;font-variant:normal;font-weight:500;font-stretch:normal;font-size:medium;line-height:125%;font-family:'ITC Benguiat Gothic Std';-inkscape-font-specification:'ITC Benguiat Gothic Std Medium';text-align:start;letter-spacing:0px;word-spacing:0px;writing-mode:lr-tb;text-anchor:start;fill:#78079a;fill-opacity:1;stroke:none" + inkscape:connector-curvature="0" + id="path4240" + d="m 446.07368,272.21881 c -8.56013,0 -15.36613,-5.33254 -15.36613,-14.73464 0,-6.52534 3.57842,-9.8231 12.27887,-9.8231 l 7.9988,0 c 1.89446,0 3.15743,-0.84197 3.15743,-2.66626 0,-1.82429 -1.26297,-2.66627 -3.15743,-2.66627 l -11.92804,0 c -9.19161,0 -14.94513,6.45517 -14.94513,14.94513 0,12.77002 10.59491,20.69866 20.13734,20.69866 l 8.34963,0 c 1.96462,0 3.36791,-0.91214 3.36791,-2.87676 0,-1.96462 -1.40329,-2.87676 -3.36791,-2.87676 l -6.52534,0 z" /> + <path + style="font-style:normal;font-variant:normal;font-weight:500;font-stretch:normal;font-size:medium;line-height:125%;font-family:'ITC Benguiat Gothic Std';-inkscape-font-specification:'ITC Benguiat Gothic Std Medium';text-align:start;letter-spacing:0px;word-spacing:0px;writing-mode:lr-tb;text-anchor:start;fill:#78079a;fill-opacity:1;stroke:none" + inkscape:connector-curvature="0" + id="path4242" + d="m 461.22931,274.53425 c 0,2.10495 0.77181,3.64858 3.08725,3.64858 2.31545,0 3.08726,-1.54363 3.08726,-3.64858 l 0,-18.59371 c 0,-5.47287 4.35023,-8.27947 9.47227,-8.27947 2.24528,0 3.15742,-1.05247 3.15742,-3.01709 0,-2.03478 -1.33313,-2.73643 -3.64858,-2.73643 -4.49055,0 -7.50764,1.68396 -8.84078,6.10435 l -0.14033,0 0,-2.03478 c 0,-2.10495 -0.77181,-3.64858 -3.08726,-3.64858 -2.31544,0 -3.08725,1.54363 -3.08725,3.64858 l 0,28.55713 z" /> + <path + style="font-style:normal;font-variant:normal;font-weight:500;font-stretch:normal;font-size:medium;line-height:125%;font-family:'ITC Benguiat Gothic Std';-inkscape-font-specification:'ITC Benguiat Gothic Std Medium';text-align:start;letter-spacing:0px;word-spacing:0px;writing-mode:lr-tb;text-anchor:start;fill:#78079a;fill-opacity:1;stroke:none" + inkscape:connector-curvature="0" + id="path4244" + d="m 498.09441,273.06079 c -6.38501,0 -10.66507,-6.10435 -10.66507,-12.91035 0,-6.806 4.28006,-12.91036 10.66507,-12.91036 6.45518,0 10.73524,6.10436 10.73524,12.91036 0,6.806 -4.28006,12.91035 -10.73524,12.91035 z m 0,5.33253 c 9.54243,0 16.90975,-7.92864 16.90975,-18.31305 0,-9.68276 -7.36732,-18.17272 -16.90975,-18.17272 -9.54243,0 -16.83959,8.48996 -16.83959,18.17272 0,10.38441 7.29716,18.31305 16.83959,18.31305 z" /> + <path + style="font-style:normal;font-variant:normal;font-weight:500;font-stretch:normal;font-size:medium;line-height:125%;font-family:'ITC Benguiat Gothic Std';-inkscape-font-specification:'ITC Benguiat Gothic Std Medium';text-align:start;letter-spacing:0px;word-spacing:0px;writing-mode:lr-tb;text-anchor:start;fill:#78079a;fill-opacity:1;stroke:none" + inkscape:connector-curvature="0" + id="path4246" + d="m 529.43293,256.78252 c 8.63029,-3.08726 27.15383,-6.45518 27.15383,-18.73404 0,-5.6132 -4.49055,-8.34963 -10.03358,-8.34963 l -20.418,0 c -2.17512,0 -2.87677,1.4033 -2.87677,3.36792 l 0,41.46748 c 0,2.17511 0.98231,3.64858 3.08726,3.64858 2.10495,0 3.08726,-1.47347 3.08726,-3.64858 l 0,-17.75173 z m 15.99761,-21.33015 c 2.45577,0 4.28006,0.84198 4.28006,3.57842 0,6.31484 -13.19101,8.48995 -20.27767,11.43688 l 0,-15.0153 15.99761,0 z" /> + <path + style="font-style:normal;font-variant:normal;font-weight:500;font-stretch:normal;font-size:medium;line-height:125%;font-family:'ITC Benguiat Gothic Std';-inkscape-font-specification:'ITC Benguiat Gothic Std Medium';text-align:start;letter-spacing:0px;word-spacing:0px;writing-mode:lr-tb;text-anchor:start;fill:#78079a;fill-opacity:1;stroke:none" + inkscape:connector-curvature="0" + id="path4248" + d="m 566.52497,255.80021 c 0.91214,-4.49056 4.13973,-8.56013 10.87556,-8.56013 5.68336,0 9.26178,3.64858 9.54244,8.56013 l -20.418,0 z m 23.15443,4.77121 c 3.36792,0 3.43808,-0.77181 3.43808,-3.71874 0,-8.84078 -6.94633,-14.94513 -15.64678,-14.94513 -10.45458,0 -17.8219,7.15682 -17.8219,17.68157 0,12.34903 7.78831,18.38321 17.05008,18.38321 l 13.47167,0 c 1.89446,0 3.15743,-0.84198 3.15743,-2.66627 0,-1.82428 -1.26297,-2.66626 -3.15743,-2.66626 l -13.33134,0 c -5.75352,0 -11.08606,-3.92924 -10.5949,-12.06838 l 23.43509,0 z" /> + <path + style="font-style:normal;font-variant:normal;font-weight:500;font-stretch:normal;font-size:medium;line-height:125%;font-family:'ITC Benguiat Gothic Std';-inkscape-font-specification:'ITC Benguiat Gothic Std Medium';text-align:start;letter-spacing:0px;word-spacing:0px;writing-mode:lr-tb;text-anchor:start;fill:#78079a;fill-opacity:1;stroke:none" + inkscape:connector-curvature="0" + id="path4250" + d="m 620.52676,265.34264 c 0,6.10435 -3.43809,8.27947 -9.26178,8.27947 -5.26237,0 -8.27946,-1.89446 -8.27946,-6.10436 0,-6.5955 9.47227,-8.56012 17.54124,-8.56012 l 0,6.38501 z m -5.68336,-17.26058 c 4.28006,0 5.68336,0.98231 5.68336,3.99941 l 0,2.10494 c -9.05128,0.56132 -23.71576,1.4033 -23.71576,13.612 0,6.66567 5.68336,10.59491 13.47167,10.59491 4.77122,0 7.0165,-1.26297 10.66508,-3.9994 0,2.24528 0.91214,3.57841 2.87676,3.57841 1.96462,0 2.87676,-1.33313 2.87676,-3.57841 l 0,-19.43569 c 0,-6.24468 -1.68396,-12.62969 -10.94573,-12.62969 l -12.98052,0 c -2.03478,0 -3.36791,0.91214 -3.36791,2.87676 0,1.96462 1.33313,2.87676 3.36791,2.87676 l 12.06838,0 z" /> + <path + style="font-style:normal;font-variant:normal;font-weight:500;font-stretch:normal;font-size:medium;line-height:125%;font-family:'ITC Benguiat Gothic Std';-inkscape-font-specification:'ITC Benguiat Gothic Std Medium';text-align:start;letter-spacing:0px;word-spacing:0px;writing-mode:lr-tb;text-anchor:start;fill:#78079a;fill-opacity:1;stroke:none" + inkscape:connector-curvature="0" + id="path4252" + d="m 635.47191,274.53425 c 0,2.10495 0.77181,3.64858 3.08725,3.64858 2.31545,0 3.08726,-1.54363 3.08726,-3.64858 l 0,-17.19041 c 11.71755,1.61379 15.50645,5.33253 17.19041,17.26057 0.28066,1.96462 0.56132,3.57842 3.0171,3.57842 2.03478,0 3.15742,-1.05248 3.15742,-3.29776 0,-7.9988 -4.13973,-17.19041 -12.27887,-19.64618 l 0,-0.14033 c 3.92924,-1.33313 9.6126,-5.89386 9.6126,-10.45458 0,-1.54363 -1.05247,-2.8066 -2.24528,-2.8066 -2.31544,0 -2.8066,1.6138 -5.05187,4.77122 -2.52594,3.71874 -7.29716,6.24468 -11.92805,6.24468 l -1.47346,0 0,-19.71635 c 0,-2.10495 -0.77181,-3.64858 -3.08726,-3.64858 -2.31544,0 -3.08725,1.54363 -3.08725,3.64858 l 0,41.39732 z" /> + </g> + </g> + </g> +</svg> diff --git a/AltOS/doc/micropeak-revhistory.html b/AltOS/doc/micropeak-revhistory.html new file mode 100644 index 0000000..11cd280 --- /dev/null +++ b/AltOS/doc/micropeak-revhistory.html @@ -0,0 +1,19 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Revision History</title><link rel="stylesheet" type="text/css" href="am.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.78.1" /></head><body><div class="revhistory"><table style="border-style:solid; width:100%;" summary="Revision History"><tr><th align="left" valign="top" colspan="2"><strong>Revision History</strong></th></tr><tr><td align="left">Revision 1.3.2</td><td align="left">12 February 2014</td></tr><tr><td align="left" colspan="2"> + Add a "Download" button to the main window, which makes it + quicker to access the download function. Update the data + download documentation to reflect the new MicroPeak USB + adapter design. Monitor data during download to let you see + if the USB connection is working at all by showing the + characters received from the MicroPeak USB adapter. + </td></tr><tr><td align="left">Revision 1.2</td><td align="left">20 January 2013</td></tr><tr><td align="left" colspan="2"> + Add documentation for the MicroPeak USB adapter board. Note + the switch to a Kalman filter for peak altitude + determination. + </td></tr><tr><td align="left">Revision 1.1</td><td align="left">12 December 2012</td></tr><tr><td align="left" colspan="2"> + Add comments about EEPROM storage format and programming jig. + </td></tr><tr><td align="left">Revision 1.0</td><td align="left">18 November 2012</td></tr><tr><td align="left" colspan="2"> + Updates for version 1.0 release. + </td></tr><tr><td align="left">Revision 0.1</td><td align="left">29 October 2012</td></tr><tr><td align="left" colspan="2"> + Initial release with preliminary hardware. + </td></tr></table></div></body></html> diff --git a/AltOS/doc/micropeak.html b/AltOS/doc/micropeak.html index 627266d..7347af3 100644 --- a/AltOS/doc/micropeak.html +++ b/AltOS/doc/micropeak.html @@ -1,386 +1,326 @@ -<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>MicroPeak Owner's Manual</title><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="book"><div class="titlepage"><div><div><h1 class="title"><a name="idm45460940730432"></a>MicroPeak Owner's Manual</h1></div><div><h2 class="subtitle">A recording altimeter for hobby rocketry</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Keith</span> <span class="surname">Packard</span></h3></div></div><div><p class="copyright">Copyright 2014 Bdale Garbee and Keith Packard</p></div><div><div class="legalnotice"><a name="idm45460913524128"></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 0.1</td><td align="left">29 October 2012</td></tr><tr><td align="left" colspan="2"> - Initial release with preliminary hardware. - </td></tr><tr><td align="left">Revision 1.0</td><td align="left">18 November 2012</td></tr><tr><td align="left" colspan="2"> - Updates for version 1.0 release. - </td></tr><tr><td align="left">Revision 1.1</td><td align="left">12 December 2012</td></tr><tr><td align="left" colspan="2"> - Add comments about EEPROM storage format and programming jig. - </td></tr><tr><td align="left">Revision 1.2</td><td align="left">20 January 2013</td></tr><tr><td align="left" colspan="2"> - Add documentation for the MicroPeak USB adapter board. Note - the switch to a Kalman filter for peak altitude - determination. - </td></tr><tr><td align="left">Revision 1.3.2</td><td align="left">12 February 2014</td></tr><tr><td align="left" colspan="2"> - Add a "Download" button to the main window, which makes it - quicker to access the download function. Update the data - download documentation to reflect the new MicroPeak USB - adapter design. Monitor data during download to let you see - if the USB connection is working at all by showing the - characters received from the MicroPeak USB adapter. - </td></tr></table></div></div></div><hr></div><div class="dedication"><div class="titlepage"><div><div><h1 class="title"><a name="idm45460913513696"></a>Acknowledgements</h1></div></div></div><p> - Thanks to John Lyngdal for suggesting that we build something like this. - </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> -BdaleGarbee,KB0G<br> -NAR#87103,TRA#12201<br> -<br> -KeithPackard,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="#idm45460913510944">1. Quick Start Guide</a></span></dt><dt><span class="chapter"><a href="#idm45460910009728">2. Handling Precautions</a></span></dt><dt><span class="chapter"><a href="#idm45460910005344">3. The MicroPeak USB adapter</a></span></dt><dd><dl><dt><span class="section"><a href="#idm45460914399696">1. Installing the MicroPeak software</a></span></dt><dt><span class="section"><a href="#idm45460914396608">2. Downloading Micro Peak data</a></span></dt><dt><span class="section"><a href="#idm45460914373472">3. Analyzing MicroPeak Data</a></span></dt><dd><dl><dt><span class="section"><a href="#idm45460914369984">3.1. MicroPeak Graphs</a></span></dt><dt><span class="section"><a href="#idm45460914366384">3.2. MicroPeak Flight Statistics</a></span></dt><dt><span class="section"><a href="#idm45460914362512">3.3. Raw Data</a></span></dt><dt><span class="section"><a href="#idm45460908884080">3.4. Configuring the Graph</a></span></dt></dl></dd><dt><span class="section"><a href="#idm45460908880544">4. Setting MicroPeak Preferences</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idm45460908870560">4. Technical Information</a></span></dt><dd><dl><dt><span class="section"><a href="#idm45460908869888">1. Barometric Sensor</a></span></dt><dt><span class="section"><a href="#idm45460908867136">2. Micro-controller</a></span></dt><dt><span class="section"><a href="#idm45460908864784">3. Lithium Battery</a></span></dt><dt><span class="section"><a href="#idm45460908862000">4. Atmospheric Model</a></span></dt><dt><span class="section"><a href="#idm45460908859024">5. Mechanical Considerations</a></span></dt><dt><span class="section"><a href="#idm45460908856272">6. On-board data storage</a></span></dt><dt><span class="section"><a href="#idm45460908835936">7. MicroPeak Programming Interface</a></span></dt></dl></dd></dl></div><div class="list-of-tables"><p><b>List of Tables</b></p><dl><dt>4.1. <a href="#idm45460908854160">MicroPeak EEPROM Data Storage</a></dt></dl></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idm45460913510944"></a>Chapter1.Quick Start Guide</h1></div></div></div><p> - MicroPeak is designed to be easy to use. Requiring no external - components, flying takes just a few steps - </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p> - Install the battery. Fit a CR1025 battery into the plastic - carrier. The positive (+) terminal should be towards the more - open side of the carrier. Slip the carrier into the battery - holder with the positive (+) terminal facing away from the - circuit board. - </p><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="micropeak-back.jpg" width="405"></td></tr></table></div></div></li><li class="listitem"><p> - Install MicroPeak in your rocket. This can be as simple as - preparing a soft cushion of wadding inside a vented model payload - bay. Wherever you mount it, make sure you protect the - barometric sensor from corrosive ejection gasses as those - will damage the sensor, and shield it from light as that can - cause incorrect sensor readings. - </p></li><li class="listitem"><p> - Turn MicroPeak on. Slide the switch so that the actuator - covers the '1' printed on the board. MicroPeak will report - the maximum height of the last flight in decimeters using a - sequence of flashes on the LED. A sequence of short flashes - indicates one digit. A single long flash indicates zero. The - height is reported in decimeters, so the last digit will be - tenths of a meter. For example, if MicroPeak reports 5 4 4 - 3, then the maximum height of the last flight was 544.3m, or - 1786 feet. - </p></li><li class="listitem"><p> - Finish preparing the rocket for flight. After the - previous flight data have been reported, MicroPeak waits for - one minute before starting to check for launch. This gives - you time to finish assembling the rocket. As those - activities might cause pressure changes inside the airframe, - MicroPeak might accidentally detect boost. If you need to do - anything to the airframe after the one minute window passes, - make sure to be careful not to disturb the altimeter. The - LED will remain dark during the one minute delay, but after - that, it will start blinking once every 3 seconds. - </p></li><li class="listitem"><p> - Fly the rocket. Once the rocket passes about 30m in height - (100 feet), the micro-controller will record the ground - pressure and track the pressure seen during the flight. In - this mode, the LED flickers rapidly. When the rocket lands, - and the pressure stabilizes, the micro-controller will record - the minimum pressure pressure experienced during the flight, - compute the height represented by the difference in air - pressure and blink that value out on the LED. After that, - MicroPeak powers down to conserve battery power. - </p></li><li class="listitem"><p> - Recover the data. Turn MicroPeak off and then back on. MicroPeak - will blink out the maximum height for the last flight. Turn - MicroPeak back off to conserve battery power. - </p></li></ul></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idm45460910009728"></a>Chapter2.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 CR1025 Lithium batteries have an - extraordinary power density. This is great because we can fly with - much less battery mass... but if they are punctured - or their contacts are allowed to short, they can and will release their - energy very rapidly! - Thus we recommend that you take some care when handling MicroPeak - to keep conductive material from coming in contact with the exposed metal elements. - </p><p> - The barometric sensor used in MicroPeak is sensitive to - sunlight. Please consider this when designing an - installation. 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 ports 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="idm45460910005344"></a>Chapter3.The MicroPeak USB adapter</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idm45460914399696">1. Installing the MicroPeak software</a></span></dt><dt><span class="section"><a href="#idm45460914396608">2. Downloading Micro Peak data</a></span></dt><dt><span class="section"><a href="#idm45460914373472">3. Analyzing MicroPeak Data</a></span></dt><dd><dl><dt><span class="section"><a href="#idm45460914369984">3.1. MicroPeak Graphs</a></span></dt><dt><span class="section"><a href="#idm45460914366384">3.2. MicroPeak Flight Statistics</a></span></dt><dt><span class="section"><a href="#idm45460914362512">3.3. Raw Data</a></span></dt><dt><span class="section"><a href="#idm45460908884080">3.4. Configuring the Graph</a></span></dt></dl></dd><dt><span class="section"><a href="#idm45460908880544">4. Setting MicroPeak Preferences</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="405"><tr><td><img src="MicroPeakUSB-2.0.jpg" width="405"></td></tr></table></div></div><p> - MicroPeak stores barometric pressure information for the first - 48 seconds of the flight in on-board non-volatile memory. The - contents of this memory can be downloaded to a computer using - the MicroPeak USB adapter. - </p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idm45460914399696"></a>1.Installing the MicroPeak software</h2></div></div></div><p> - The MicroPeak application runs on Linux, Mac OS X and - Windows. You can download the latest version from - <a class="ulink" href="http://altusmetrum.org/AltOS" target="_top">http://altusmetrum.org/AltOS</a>. - </p><p> - On Mac OS X and Windows, the FTDI USB device driver needs to - be installed. A compatible version of this driver is included - with the MicroPeak application, but you may want to download a - newer version from <a class="ulink" href="http://www.ftdichip.com/FTDrivers.htm" target="_top">http://www.ftdichip.com/FTDrivers.htm</a>. - </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idm45460914396608"></a>2.Downloading Micro Peak data</h2></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p> - Plug the MicroPeak USB adapter in to your computer. - </p></li><li class="listitem"><p> - Start the MicroPeak application. - </p><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="45"><tr><td><img src="micropeak-nofont.svg" width="45"></td></tr></table></div></div></li><li class="listitem"><p> - Click on the Download button at the top of the window. - </p><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="micropeak-app.png" width="405"></td></tr></table></div></div></li><li class="listitem"><p> - Select from the listed devices. There will probably be - only one. - </p><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="207"><tr><td><img src="micropeak-device-dialog.png" width="207"></td></tr></table></div></div></li><li class="listitem"><p> - The application will now wait until it receives valid data - from the MicroPeak USB adapter. - </p><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="180"><tr><td><img src="micropeak-download.png" width="180"></td></tr></table></div></div><p> - The MicroPeak USB adapter has a small phototransistor - under the hole in the center of the box. - Locate this, turn on the MicroPeak and place the orange LED on the MicroPeak - directly inside the hole, resting the MicroPeak itself on - the box. You should see the blue LED on the MicroPeak USB - adapter blinking in time with the orange LED on the - MicroPeak board itself. - </p><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="MicroPeakUSB-2.0-inuse.jpg" width="405"></td></tr></table></div></div></li><li class="listitem"><p> - After the maximum flight height is reported, MicroPeak will - pause for a few seconds, blink the LED four times rapidly - and then send the data in one long blur on the LED. The - MicroPeak application should receive the data. When it does, - it will present the data in a graph and offer to save the - data to a file. If not, you can power cycle the MicroPeak - board and try again. - </p><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="207"><tr><td><img src="micropeak-save-dialog.png" width="207"></td></tr></table></div></div></li><li class="listitem"><p> - Once the data are saved, a graph will be displayed with - height, speed and acceleration values computed from the - recorded barometric pressure data. See the next section - for more details on that. - </p></li></ul></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idm45460914373472"></a>3.Analyzing MicroPeak Data</h2></div></div></div><p> - The MicroPeak application can present flight data in the form - of a graph, a collection of computed statistics or in tabular - form. - </p><p> - MicroPeak collects raw barometric pressure data which is - then used to compute the remaining data. Altitude is computed - through a standard atmospheric model. Absolute error in this - data will be affected by local atmospheric - conditions. Fortunately, these errors tend to mostly cancel - out, so the error in the height computation is much smaller - than the error in altitude would be. - </p><p> - Speed and acceleration are computed by first smoothing the - height data with a Gaussian window averaging filter. For speed - data, this average uses seven samples. For acceleration data, - eleven samples are used. These were chosen to provide - reasonably smooth speed and acceleration data, which would - otherwise be swamped with noise. - </p><p> - The File menu has operations to open existing flight logs, - Download new data from MicroPeak, Save a copy of the flight - log to a new file, Export the tabular data (as seen in the Raw - Data tab) to a file, change the application Preferences, Close - the current window or close all windows and Exit the - application. - </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm45460914369984"></a>3.1.MicroPeak Graphs</h3></div></div></div><p> - Under the Graph tab, the height, speed and acceleration values - are displayed together. You can zoom in on the graph by - clicking and dragging to sweep out an area of - interest. Right-click on the plot to bring up a menu that will - let you save, copy or print the graph. - </p><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="micropeak-graph.png" width="405"></td></tr></table></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm45460914366384"></a>3.2.MicroPeak Flight Statistics</h3></div></div></div><p> - The Statistics tab presents overall data from the flight. Note - that the Maximum height value is taken from the minumum - pressure captured in flight, and may be different from the - apparant apogee value as the on-board data are sampled twice - as fast as the recorded values, or because the true apogee - occurred after the on-board memory was full. Each value is - presented in several units as appropriate. - </p><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="micropeak-statistics.png" width="405"></td></tr></table></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm45460914362512"></a>3.3.Raw Data</h3></div></div></div><p> - A table consisting of the both the raw barometric pressure - data and values computed from that for each recorded time. - </p><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="micropeak-raw-data.png" width="405"></td></tr></table></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm45460908884080"></a>3.4.Configuring the Graph</h3></div></div></div><p> - This selects which graph elements to show, and lets you - switch between metric and imperial units - </p><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="micropeak-graph-configure.png" width="405"></td></tr></table></div></div></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idm45460908880544"></a>4.Setting MicroPeak Preferences</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="162"><tr><td><img src="micropeak-preferences.png" width="162"></td></tr></table></div></div><p> - The MicroPeak application has a few user settings which are - configured through the Preferences dialog, which can be - accessed from the File menu. - </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p> - The Log Directory is where flight data will be saved to - and loaded from by default. Of course, you can always - navigate to other directories in the file chooser windows, - this setting is just the starting point. - </p></li><li class="listitem"><p> - If you prefer to see your graph data in feet and - miles per hour instead of meters and meters per second, - you can select Imperial Units. - </p></li><li class="listitem"><p> - To see what data is actually arriving over the serial - port, start the MicroPeak application from a command - prompt and select the Serial Debug option. This can be - useful in debugging serial communication problems, but - most people need never choose this. - </p></li><li class="listitem"><p> - You can adjust the size of the text in the Statistics tab - by changing the Font size preference. There are three - settings, with luck one will both fit on your screen and - provide readable values. - </p></li><li class="listitem"><p> - The Look & feel menu shows a list of available - application appearance choices. By default, the MicroPeak - application tries to blend in with other applications, but - you may choose some other appearance if you like. - </p></li></ul></div><p> - </p><p> - Note that MicroPeak shares a subset of the AltosUI - preferences, so if you use both of these applications, change - in one application will affect the other. - </p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idm45460908870560"></a>Chapter4.Technical Information</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idm45460908869888">1. Barometric Sensor</a></span></dt><dt><span class="section"><a href="#idm45460908867136">2. Micro-controller</a></span></dt><dt><span class="section"><a href="#idm45460908864784">3. Lithium Battery</a></span></dt><dt><span class="section"><a href="#idm45460908862000">4. Atmospheric Model</a></span></dt><dt><span class="section"><a href="#idm45460908859024">5. Mechanical Considerations</a></span></dt><dt><span class="section"><a href="#idm45460908856272">6. On-board data storage</a></span></dt><dt><span class="section"><a href="#idm45460908835936">7. MicroPeak Programming Interface</a></span></dt></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idm45460908869888"></a>1.Barometric Sensor</h2></div></div></div><p> - MicroPeak uses the Measurement Specialties MS5607 sensor. This - has a range of 120kPa to 1kPa with an absolute accuracy of - 150Pa and a resolution of 2.4Pa. - </p><p> - The pressure range corresponds roughly to an altitude range of - -1500m (-4900 feet) to 31000m (102000 feet), while the - resolution is approximately 20cm (8 inches) near sea level and - 60cm (24in) at 10000m (33000 feet). - </p><p> - Ground pressure is computed from an average of 16 samples, - taken while the altimeter is at rest. The flight pressure used to - report maximum height is computed from a Kalman filter - designed to smooth out any minor noise in the sensor - values. The flight pressure recorded to non-volatile storage - is unfiltered, coming directly from the pressure sensor. - </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idm45460908867136"></a>2.Micro-controller</h2></div></div></div><p> - MicroPeak uses an Atmel ATtiny85 micro-controller. This tiny - CPU contains 8kB of flash for the application, 512B of RAM for - temporary data storage and 512B of EEPROM for non-volatile - storage of previous flight data. - </p><p> - The ATtiny85 has a low-power mode which turns off all of the - clocks and powers down most of the internal components. In - this mode, the chip consumes only .1μA of power. MicroPeak - uses this mode once the flight has ended to preserve battery - power. - </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idm45460908864784"></a>3.Lithium Battery</h2></div></div></div><p> - The CR1025 battery used by MicroPeak holds 30mAh of power, - which is sufficient to run for over 40 hours. Because - MicroPeak powers down on landing, run time includes only time - sitting on the launch pad or during flight. - </p><p> - The large positive terminal (+) is usually marked, while the - smaller negative terminal is not. Make sure you install the - battery with the positive terminal facing away from the - circuit board where it will be in contact with the metal - battery holder. A small pad on the circuit board makes contact - with the negative battery terminal. - </p><p> - Shipping restrictions may prevent us from including a CR1025 - battery with MicroPeak. If so, many stores carry CR1025 - batteries as they are commonly used in small electronic - devices such as flash lights. - </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idm45460908862000"></a>4.Atmospheric Model</h2></div></div></div><p> - MicroPeak contains a fixed atmospheric model which is used to - convert barometric pressure into altitude. The model was - converted into a 469-element piece-wise linear approximation - which is then used to compute the altitude of the ground and - apogee. The difference between these represents the maximum - height of the flight. - </p><p> - The model assumes a particular set of atmospheric conditions, - which, while a reasonable average, cannot represent the changing - nature of the real atmosphere. Fortunately, for flights - reasonably close to the ground, the effect of this global - inaccuracy are largely canceled out when the computed ground - altitude is subtracted from the computed apogee altitude, so - the resulting height is more accurate than either the ground - or apogee altitudes. - </p><p> - Because the raw pressure data is recorded to non-volatile - storage, you can use that, along with a more sophisticated - atmospheric model, to compute your own altitude values. - </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idm45460908859024"></a>5.Mechanical Considerations</h2></div></div></div><p> - MicroPeak is designed to be rugged enough for typical rocketry - applications. It contains two moving parts, the battery holder - and the power switch, which were selected for their - ruggedness. - </p><p> - The MicroPeak battery holder is designed to withstand impact - up to 150g without breaking contact (or, worse yet, causing - the battery to fall out). That means it should stand up to - almost any launch you care to try, and should withstand fairly - rough landings. - </p><p> - The power switch is designed to withstand up to 50g forces in - any direction. Because it is a sliding switch, orienting the - switch perpendicular to the direction of rocket travel will - serve to further protect the switch from launch forces. - </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idm45460908856272"></a>6.On-board data storage</h2></div></div></div><p> - The ATtiny85 has 512 bytes of non-volatile storage, separate - from the code storage memory. The MicroPeak firmware uses this - to store information about the last completed - flight. Barometric measurements from the ground before launch - and at apogee are stored, and used at power-on to compute the - height of the last flight. - </p><p> - In addition to the data used to present the height of the last - flight, MicroPeak also stores barometric information sampled - at regular intervals during the flight. This is the - information captured with the MicroPeak USB adapter. It can - also be read from MicroPeak through any AVR programming - tool. - </p><div class="table"><a name="idm45460908854160"></a><p class="title"><b>Table4.1.MicroPeak EEPROM Data Storage</b></p><div class="table-contents"><table summary="MicroPeak EEPROM Data Storage" border="1"><colgroup><col align="center" class="Address"><col align="center" class="Size (bytes)"><col align="left" class="Description"></colgroup><thead><tr><th align="center">Address</th><th align="center">Size (bytes)</th><th align="center">Description</th></tr></thead><tbody><tr><td align="center">0x000</td><td align="center">4</td><td align="left">Average ground pressure (Pa)</td></tr><tr><td align="center">0x004</td><td align="center">4</td><td align="left">Minimum flight pressure (Pa)</td></tr><tr><td align="center">0x008</td><td align="center">2</td><td align="left">Number of in-flight samples</td></tr><tr><td align="center">0x00a … 0x1fe</td><td align="center">2</td><td align="left">Instantaneous flight pressure (Pa) low 16 bits</td></tr></tbody></table></div></div><br class="table-break"><p> - All EEPROM data are stored least-significant byte first. The - instantaneous flight pressure data are stored without the - upper 16 bits of data. The upper bits can be reconstructed - from the previous sample, assuming that pressure doesn't - change by more more than 32kPa in a single sample - interval. Note that this pressure data is <span class="emphasis"><em>not</em></span> - filtered in any way, while both the recorded ground and apogee - pressure values are, so you shouldn't expect the minimum - instantaneous pressure value to match the recorded minimum - pressure value exactly. - </p><p> - MicroPeak samples pressure every 96ms, but stores only every - other sample in the EEPROM. This provides for 251 pressure - samples at 192ms intervals, or 48.192s of storage. The clock - used for these samples is a factory calibrated RC circuit - built into the ATtiny85 and is accurate only to within 10% at - 25C. So, you can count on the pressure data being accurate, - but speed or acceleration data computed from this will be - limited by the accuracy of this clock. - </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idm45460908835936"></a>7.MicroPeak Programming Interface</h2></div></div></div><p> - MicroPeak exposes a standard 6-pin AVR programming interface, - but not using the usual 2x3 array of pins on 0.1" - centers. Instead, there is a single row of tiny 0.60mm - 0.85mm pads on 1.20mm centers exposed near the edge of the - circuit board. We couldn't find any connector that was - small enough to include on the circuit board. - </p><p> - In lieu of an actual connector, the easiest way to connect to - the bare pads is through a set of Pogo pins. These - spring-loaded contacts are designed to connect in precisely - this way. We've designed a programming jig, the MicroPeak - Pogo Pin board which provides a standard AVR interface on one - end and a recessed slot for MicroPeak to align the board with - the Pogo Pins. - </p><p> - The MicroPeak Pogo Pin board is not a complete AVR programmer, - it is an interface board that provides a 3.3V regulated power - supply to run the MicroPeak via USB and a standard 6-pin AVR - programming interface with the usual 2x3 grid of pins on 0.1" - centers. This can be connected to any AVR programming - dongle. - </p><p> - The AVR programming interface cannot run faster than of the - AVR CPU clock frequency. Because MicroPeak runs at 250kHz to - save power, you must configure your AVR programming system to - clock the AVR programming interface at no faster than - 62.5kHz, or a clock period of 32S. - </p></div></div></div></body></html> +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>MicroPeak Owner’s Manual</title><link rel="stylesheet" type="text/css" href="am.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.78.1" /></head><body><div xml:lang="en" class="book" lang="en"><div class="titlepage"><div><div><h1 class="title"><a id="idm46222414925680"></a>MicroPeak Owner’s Manual</h1></div><div><h2 class="subtitle">A recording altimeter for hobby rocketry</h2></div><div><h3 class="corpauthor"> + <span class="inlinemediaobject"><img src="micropeak-oneline.svg" width="270" /></span> +</h3></div><div><div class="author"><h3 class="author"><span class="firstname">Keith</span> <span class="surname">Packard</span></h3><code class="email"><<a class="email" href="mailto:keithp@keithp.com">keithp@keithp.com</a>></code></div></div><div><p class="copyright">Copyright © 2014 Keith Packard</p></div><div><div class="legalnotice"><a id="idm46222415052400"></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><a href="micropeak-revhistory.html">Revision History</a></div></div><hr /></div><div class="dedication"><div class="titlepage"><div><div><h1 class="title"><a id="_acknowledgements"></a>Acknowledgements</h1></div></div></div><p>Thanks to John Lyngdal for suggesting that we build something +like this.</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="blockquote"><blockquote class="blockquote"><div class="literallayout"><p>Bdale Garbee, KB0G<br /> +NAR #87103, TRA #12201</p></div></blockquote></div><div class="blockquote"><blockquote class="blockquote"><div class="literallayout"><p>Keith Packard, KD7SQG<br /> +NAR #88757, TRA #12200</p></div></blockquote></div></div><div class="toc"><p><strong>Table of Contents</strong></p><dl class="toc"><dt><span class="chapter"><a href="#_using_micropeak">1. Using MicroPeak</a></span></dt><dt><span class="chapter"><a href="#_the_micropeak_usb_adapter">2. The MicroPeak USB adapter</a></span></dt><dd><dl><dt><span class="section"><a href="#_installing_the_micropeak_software">2.1. Installing the MicroPeak software</a></span></dt><dt><span class="section"><a href="#_downloading_micro_peak_data">2.2. Downloading Micro Peak data</a></span></dt><dt><span class="section"><a href="#_analyzing_micropeak_data">2.3. Analyzing MicroPeak Data</a></span></dt><dd><dl><dt><span class="section"><a href="#_micropeak_graphs">2.3.1. MicroPeak Graphs</a></span></dt><dt><span class="section"><a href="#_micropeak_flight_statistics">2.3.2. MicroPeak Flight Statistics</a></span></dt><dt><span class="section"><a href="#_raw_flight_data">2.3.3. Raw Flight Data</a></span></dt><dt><span class="section"><a href="#_configuring_the_graph">2.3.4. Configuring the Graph</a></span></dt></dl></dd><dt><span class="section"><a href="#_setting_micropeak_preferences">2.4. Setting MicroPeak Preferences</a></span></dt></dl></dd><dt><span class="appendix"><a href="#_handling_precautions">A. Handling Precautions</a></span></dt><dt><span class="appendix"><a href="#_technical_information">B. Technical Information</a></span></dt><dd><dl><dt><span class="section"><a href="#_barometric_sensor">B.1. Barometric Sensor</a></span></dt><dt><span class="section"><a href="#_micro_controller">B.2. Micro-controller</a></span></dt><dt><span class="section"><a href="#_lithium_battery">B.3. Lithium Battery</a></span></dt><dt><span class="section"><a href="#_atmospheric_model">B.4. Atmospheric Model</a></span></dt><dt><span class="section"><a href="#_mechanical_considerations">B.5. Mechanical Considerations</a></span></dt><dt><span class="section"><a href="#_micropeak_programming_interface">B.6. MicroPeak Programming Interface</a></span></dt></dl></dd><dt><span class="appendix"><a href="#_on_board_data_storage">C. On-board data storage</a></span></dt></dl></div><div class="list-of-figures"><p><strong>List of Figures</strong></p><dl><dt>1.1. <a href="#idm46222411271328">MicroPeak and Battery</a></dt><dt>2.1. <a href="#idm46222414185232">MicroPeak USB Adapter</a></dt><dt>2.2. <a href="#idm46222415015888">MicroPeak Application</a></dt><dt>2.3. <a href="#idm46222415011264">MicroPeak Device Dialog</a></dt><dt>2.4. <a href="#idm46222415074064">MicroPeak Download Dialog</a></dt><dt>2.5. <a href="#idm46222415069120">MicroPeak Downloading</a></dt><dt>2.6. <a href="#idm46222415064112">MicroPeak Save Dialog</a></dt><dt>2.7. <a href="#idm46222409546800">MicroPeak Graph</a></dt><dt>2.8. <a href="#idm46222409541696">MicroPeak Flight Statistics</a></dt><dt>2.9. <a href="#idm46222409536688">MicroPeak Raw Flight Data</a></dt><dt>2.10. <a href="#idm46222409531904">MicroPeak Graph Configuration</a></dt><dt>2.11. <a href="#idm46222409527040">MicroPeak Preferences</a></dt></dl></div><div class="list-of-tables"><p><strong>List of Tables</strong></p><dl><dt>C.1. <a href="#idm46222409481536">MicroPeak EEPROM Data Storage</a></dt></dl></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="_using_micropeak"></a>Chapter 1. Using MicroPeak</h1></div></div></div><p>MicroPeak is designed to be easy to use. Requiring no external +components, flying takes just a few steps</p><div class="variablelist"><dl class="variablelist"><dt><span class="term"> +Install the battery +</span></dt><dd> +Fit a CR1025 battery into the plastic carrier. The positive +(+) terminal should be towards the more open side of the +carrier. Slip the carrier into the battery holder with the +positive (+) terminal facing away from the circuit board. +</dd></dl></div><div class="figure"><a id="idm46222411271328"></a><p class="title"><strong>Figure 1.1. MicroPeak and Battery</strong></p><div class="figure-contents"><div class="mediaobject"><img src="micropeak-back.jpg" width="405" alt="micropeak-back.jpg" /></div></div></div><br class="figure-break" /><div class="variablelist"><dl class="variablelist"><dt><span class="term"> +Install MicroPeak in your rocket +</span></dt><dd> +This can be as simple as preparing a soft cushion of wadding +inside a vented model payload bay. Wherever you mount it, +make sure you protect the barometric sensor from corrosive +ejection gasses as those will damage the sensor, and shield +it from light as that can cause incorrect sensor readings. +</dd><dt><span class="term"> +Turn MicroPeak on +</span></dt><dd> +Slide the switch so that the actuator covers the <span class="emphasis"><em>1</em></span> printed +on the board. MicroPeak will report the maximum height of +the last flight in decimeters using a sequence of flashes on +the LED. A sequence of short flashes indicates one digit. A +single long flash indicates zero. The height is reported in +decimeters, so the last digit will be tenths of a meter. For +example, if MicroPeak reports 5 4 4 3, then the maximum +height of the last flight was 544.3m, or 1786 feet. +</dd><dt><span class="term"> +Finish preparing the rocket for flight +</span></dt><dd> +After the previous flight data have been reported, MicroPeak +waits for one minute before starting to check for +launch. This gives you time to finish assembling the +rocket. As those activities might cause pressure changes +inside the airframe, MicroPeak might accidentally detect +boost. If you need to do anything to the airframe after the +one minute window passes, make sure to be careful not to +disturb the altimeter. The LED will remain dark during the +one minute delay, but after that, it will start blinking +once every 3 seconds. +</dd><dt><span class="term"> +Fly the rocket +</span></dt><dd> +Once the rocket passes about 30m in height (100 feet), the +micro-controller will record the ground pressure and track +the pressure seen during the flight. In this mode, the LED +flickers rapidly. When the rocket lands, and the pressure +stabilizes, the micro-controller will record the minimum +pressure pressure experienced during the flight, compute the +height represented by the difference in air pressure and +blink that value out on the LED. After that, MicroPeak +powers down to conserve battery power. +</dd><dt><span class="term"> +Recover the data +</span></dt><dd> +Turn MicroPeak off and then back on. MicroPeak will blink +out the maximum height for the last flight. Turn MicroPeak +back off to conserve battery power. +</dd></dl></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="_the_micropeak_usb_adapter"></a>Chapter 2. The MicroPeak USB adapter</h1></div></div></div><div class="figure"><a id="idm46222414185232"></a><p class="title"><strong>Figure 2.1. MicroPeak USB Adapter</strong></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="MicroPeakUSB-2.0.jpg" align="middle" width="405" alt="MicroPeakUSB-2.0.jpg" /></div></div></div><br class="figure-break" /><p>MicroPeak stores barometric pressure information for the first +48 seconds of the flight in on-board non-volatile memory. The +contents of this memory can be downloaded to a computer using +the MicroPeak USB adapter.</p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_installing_the_micropeak_software"></a>2.1. Installing the MicroPeak software</h2></div></div></div><p>The MicroPeak application runs on Linux, Mac OS X and +Windows. You can download the latest version from +<a class="ulink" href="http://altusmetrum.org/MicroPeak" target="_top">http://altusmetrum.org/MicroPeak</a></p><p>On Mac OS X and Windows, the FTDI USB device driver +needs to be installed. A compatible version of this +driver is included with the MicroPeak application, but +you may want to download a newer version from +<a class="ulink" href="http://www.ftdichip.com/FTDrivers.htm" target="_top">http://www.ftdichip.com/FTDrivers.htm</a></p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_downloading_micro_peak_data"></a>2.2. Downloading Micro Peak data</h2></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Plug the MicroPeak USB adapter in to your computer. +</li><li class="listitem"> +Start the MicroPeak application. +</li></ul></div><div class="informalfigure"><div class="mediaobject" align="center"><img src="micropeak-nofont.svg" align="middle" width="45" alt="micropeak-nofont.svg" /></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Click on the Download button at the top of the +window. +</li></ul></div><div class="figure"><a id="idm46222415015888"></a><p class="title"><strong>Figure 2.2. MicroPeak Application</strong></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="micropeak-app.png" align="middle" width="405" alt="micropeak-app.png" /></div></div></div><br class="figure-break" /><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Select from the listed devices. There will probably +be only one. +</li></ul></div><div class="figure"><a id="idm46222415011264"></a><p class="title"><strong>Figure 2.3. MicroPeak Device Dialog</strong></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="micropeak-device-dialog.png" align="middle" width="207" alt="micropeak-device-dialog.png" /></div></div></div><br class="figure-break" /><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +The application will now wait until it receives +valid data from the MicroPeak USB adapter. +</li></ul></div><div class="figure"><a id="idm46222415074064"></a><p class="title"><strong>Figure 2.4. MicroPeak Download Dialog</strong></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="micropeak-download.png" align="middle" width="180" alt="micropeak-download.png" /></div></div></div><br class="figure-break" /><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +The MicroPeak USB adapter has a small +phototransistor under the hole in the center of the +box. Locate this, turn on the MicroPeak and place +the orange LED on the MicroPeak directly inside the +hole, resting the MicroPeak itself on the box. You +should see the blue LED on the MicroPeak USB adapter +blinking in time with the orange LED on the +MicroPeak board itself. +</li></ul></div><div class="figure"><a id="idm46222415069120"></a><p class="title"><strong>Figure 2.5. MicroPeak Downloading</strong></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="MicroPeakUSB-2.0-inuse.jpg" align="middle" width="405" alt="MicroPeakUSB-2.0-inuse.jpg" /></div></div></div><br class="figure-break" /><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +After the maximum flight height is reported, +MicroPeak will pause for a few seconds, blink the +LED four times rapidly and then send the data in one +long blur on the LED. The MicroPeak application +should receive the data. When it does, it will +present the data in a graph and offer to save the +data to a file. If not, you can power cycle the +MicroPeak board and try again. +</li></ul></div><div class="figure"><a id="idm46222415064112"></a><p class="title"><strong>Figure 2.6. MicroPeak Save Dialog</strong></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="micropeak-save-dialog.png" align="middle" width="207" alt="micropeak-save-dialog.png" /></div></div></div><br class="figure-break" /><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Once the data are saved, a graph will be displayed +with height, speed and acceleration values computed +from the recorded barometric pressure data. See +<<_analyzing_micropeak_data> for more details on that. +</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_analyzing_micropeak_data"></a>2.3. Analyzing MicroPeak Data</h2></div></div></div><p>The MicroPeak application can present flight data in +the form of a graph, a collection of computed +statistics or in tabular form.</p><p>MicroPeak collects raw barometric pressure data which +is then used to compute the remaining data. Altitude +is computed through a standard atmospheric +model. Absolute error in this data will be affected by +local atmospheric conditions. Fortunately, these +errors tend to mostly cancel out, so the error in the +height computation is much smaller than the error in +altitude would be.</p><p>Speed and acceleration are computed by first smoothing +the height data with a Gaussian window averaging +filter. For speed data, this average uses seven +samples. For acceleration data, eleven samples are +used. These were chosen to provide reasonably smooth +speed and acceleration data, which would otherwise be +swamped with noise.</p><p>The File menu has operations to open existing flight +logs, Download new data from MicroPeak, Save a copy of +the flight log to a new file, Export the tabular data +(as seen in the Raw Data tab) to a file, change the +application Preferences, Close the current window or +close all windows and Exit the application.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_micropeak_graphs"></a>2.3.1. MicroPeak Graphs</h3></div></div></div><div class="figure"><a id="idm46222409546800"></a><p class="title"><strong>Figure 2.7. MicroPeak Graph</strong></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="micropeak-graph.png" align="middle" width="405" alt="micropeak-graph.png" /></div></div></div><br class="figure-break" /><p>Under the Graph tab, the height, speed and acceleration values +are displayed together. You can zoom in on the graph by +clicking and dragging to sweep out an area of +interest. Right-click on the plot to bring up a menu that will +let you save, copy or print the graph.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_micropeak_flight_statistics"></a>2.3.2. MicroPeak Flight Statistics</h3></div></div></div><div class="figure"><a id="idm46222409541696"></a><p class="title"><strong>Figure 2.8. MicroPeak Flight Statistics</strong></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="micropeak-statistics.png" align="middle" width="405" alt="micropeak-statistics.png" /></div></div></div><br class="figure-break" /><p>The Statistics tab presents overall data from +the flight. Note that the Maximum height value +is taken from the minumum pressure captured in +flight, and may be different from the apparant +apogee value as the on-board data are sampled +twice as fast as the recorded values, or +because the true apogee occurred after the +on-board memory was full. Each value is +presented in several units as appropriate.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_raw_flight_data"></a>2.3.3. Raw Flight Data</h3></div></div></div><div class="figure"><a id="idm46222409536688"></a><p class="title"><strong>Figure 2.9. MicroPeak Raw Flight Data</strong></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="micropeak-raw-data.png" align="middle" width="405" alt="micropeak-raw-data.png" /></div></div></div><br class="figure-break" /><p>A table consisting of the both the raw barometric pressure +data and values computed from that for each recorded time.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_configuring_the_graph"></a>2.3.4. Configuring the Graph</h3></div></div></div><div class="figure"><a id="idm46222409531904"></a><p class="title"><strong>Figure 2.10. MicroPeak Graph Configuration</strong></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="micropeak-graph-configure.png" align="middle" width="405" alt="micropeak-graph-configure.png" /></div></div></div><br class="figure-break" /><p>This selects which graph elements to show, and lets you +switch between metric and imperial units</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_setting_micropeak_preferences"></a>2.4. Setting MicroPeak Preferences</h2></div></div></div><div class="figure"><a id="idm46222409527040"></a><p class="title"><strong>Figure 2.11. MicroPeak Preferences</strong></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="micropeak-preferences.png" align="middle" width="162" alt="micropeak-preferences.png" /></div></div></div><br class="figure-break" /><p>The MicroPeak application has a few user settings which are +configured through the Preferences dialog, which can be +accessed from the File menu.</p><div class="variablelist"><dl class="variablelist"><dt><span class="term"> +Log Directory +</span></dt><dd> +The Log Directory is where flight data will be +saved to and loaded from by default. Of +course, you can always navigate to other +directories in the file chooser windows, this +setting is just the starting point. +</dd><dt><span class="term"> +Imperial Units +</span></dt><dd> +If you prefer to see your graph data in feet +and miles per hour instead of meters and +meters per second, you can select Imperial +Units. +</dd><dt><span class="term"> +Serial Debug +</span></dt><dd> +To see what data is actually arriving over the +serial port, start the MicroPeak application +from a command prompt and select the Serial +Debug option. This can be useful in debugging +serial communication problems, but most people +need never choose this. +</dd><dt><span class="term"> +Font Size +</span></dt><dd> +You can adjust the size of the text in the +Statistics tab by changing the Font size +preference. There are three settings, with +luck one will both fit on your screen and +provide readable values. +</dd><dt><span class="term"> +Look & Feel +</span></dt><dd> +The Look & feel menu shows a list of available +application appearance choices. By default, +the MicroPeak application tries to blend in +with other applications, but you may choose +some other appearance if you like. +</dd></dl></div><p>Note that MicroPeak shares a subset of the +AltosUI preferences, so if you use both of +these applications, change in one application +will affect the other.</p></div></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a id="_handling_precautions"></a>Appendix A. 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><div class="warning" style="margin-left: 0; margin-right: 10%;"><h3 class="title">Warning</h3><p>The CR1025 Lithium batteries have an extraordinary power +density. This is great because we can fly with much less +battery mass… but if they are punctured or their contacts +are allowed to short, they can and will release their energy +very rapidly! Thus we recommend that you take some care when +handling MicroPeak to keep conductive material from coming in +contact with the exposed metal elements.</p></div><p>The barometric sensor used in MicroPeak is sensitive to +sunlight. Please consider this when designing an +installation. 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 ports 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="appendix"><div class="titlepage"><div><div><h1 class="title"><a id="_technical_information"></a>Appendix B. Technical Information</h1></div></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_barometric_sensor"></a>B.1. Barometric Sensor</h2></div></div></div><p>MicroPeak uses the Measurement Specialties MS5607 +sensor. This has a range of 120kPa to 1kPa with an +absolute accuracy of 150Pa and a resolution of 2.4Pa.</p><p>The pressure range corresponds roughly to an altitude +range of -1500m (-4900 feet) to 31000m (102000 feet), +while the resolution is approximately 20cm (8 inches) +near sea level and 60cm (24in) at 10000m (33000 feet).</p><p>Ground pressure is computed from an average of 16 +samples, taken while the altimeter is at rest. The +flight pressure used to report maximum height is +computed from a Kalman filter designed to smooth out +any minor noise in the sensor values. The flight +pressure recorded to non-volatile storage is +unfiltered, coming directly from the pressure sensor.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_micro_controller"></a>B.2. Micro-controller</h2></div></div></div><p>MicroPeak uses an Atmel ATtiny85 +micro-controller. This tiny CPU contains 8kB of flash +for the application, 512B of RAM for temporary data +storage and 512B of EEPROM for non-volatile storage of +previous flight data.</p><p>The ATtiny85 has a low-power mode which turns off all +of the clocks and powers down most of the internal +components. In this mode, the chip consumes only .1μA +of power. MicroPeak uses this mode once the flight has +ended to preserve battery power.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_lithium_battery"></a>B.3. Lithium Battery</h2></div></div></div><p>The CR1025 battery used by MicroPeak holds 30mAh of +power, which is sufficient to run for over 40 +hours. Because MicroPeak powers down on landing, run +time includes only time sitting on the launch pad or +during flight.</p><p>The large positive terminal (+) is usually marked, +while the smaller negative terminal is not. Make sure +you install the battery with the positive terminal +facing away from the circuit board where it will be in +contact with the metal battery holder. A small pad on +the circuit board makes contact with the negative +battery terminal.</p><p>Shipping restrictions may prevent us from including a +CR1025 battery with MicroPeak. If so, many stores +carry CR1025 batteries as they are commonly used in +small electronic devices such as flash lights.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_atmospheric_model"></a>B.4. Atmospheric Model</h2></div></div></div><p>MicroPeak contains a fixed atmospheric model which is +used to convert barometric pressure into altitude. The +model was converted into a 469-element piece-wise +linear approximation which is then used to compute the +altitude of the ground and apogee. The difference +between these represents the maximum height of the +flight.</p><p>The model assumes a particular set of atmospheric +conditions, which, while a reasonable average, cannot +represent the changing nature of the real +atmosphere. Fortunately, for flights reasonably close +to the ground, the effect of this global inaccuracy +are largely canceled out when the computed ground +altitude is subtracted from the computed apogee +altitude, so the resulting height is more accurate +than either the ground or apogee altitudes.</p><p>Because the raw pressure data is recorded to +non-volatile storage, you can use that, along with a +more sophisticated atmospheric model, to compute your +own altitude values.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_mechanical_considerations"></a>B.5. Mechanical Considerations</h2></div></div></div><p>MicroPeak is designed to be rugged enough for typical +rocketry applications. It contains two moving parts, +the battery holder and the power switch, which were +selected for their ruggedness.</p><p>The MicroPeak battery holder is designed to withstand +impact up to 150g without breaking contact (or, worse +yet, causing the battery to fall out). That means it +should stand up to almost any launch you care to try, +and should withstand fairly rough landings.</p><p>The power switch is designed to withstand up to 50g +forces in any direction. Because it is a sliding +switch, orienting the switch perpendicular to the +direction of rocket travel will serve to further +protect the switch from launch forces.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_micropeak_programming_interface"></a>B.6. MicroPeak Programming Interface</h2></div></div></div><p>MicroPeak exposes a standard 6-pin AVR programming +interface, but not using the usual 2x3 array of pins +on 0.1" centers. Instead, there is a single row of +tiny 0.60mm × 0.85mm pads on 1.20mm centers exposed +near the edge of the circuit board. We couldn’t find +any connector that was small enough to include on the +circuit board.</p><p>In lieu of an actual connector, the easiest way to +connect to the bare pads is through a set of Pogo +pins. These spring-loaded contacts are designed to +connect in precisely this way. We’ve designed a +programming jig, the MicroPeak Pogo Pin board which +provides a standard AVR interface on one end and a +recessed slot for MicroPeak to align the board with +the Pogo Pins.</p><p>The MicroPeak Pogo Pin board is not a complete AVR +programmer, it is an interface board that provides a +3.3V regulated power supply to run the MicroPeak via +USB and a standard 6-pin AVR programming interface +with the usual 2x3 grid of pins on 0.1" centers. This +can be connected to any AVR programming dongle.</p><p>The AVR programming interface cannot run faster than ¼ +of the AVR CPU clock frequency. Because MicroPeak runs +at 250kHz to save power, you must configure your AVR +programming system to clock the AVR programming +interface at no faster than 62.5kHz, or a clock period +of 32µS.</p></div></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a id="_on_board_data_storage"></a>Appendix C. On-board data storage</h1></div></div></div><p>The ATtiny85 has 512 bytes of non-volatile storage, separate +from the code storage memory. The MicroPeak firmware uses this +to store information about the last completed +flight. Barometric measurements from the ground before launch +and at apogee are stored, and used at power-on to compute the +height of the last flight.</p><p>In addition to the data used to present the height of the last +flight, MicroPeak also stores barometric information sampled +at regular intervals during the flight. This is the +information captured with the MicroPeak USB adapter. It can +also be read from MicroPeak through any AVR programming tool.</p><div class="table"><a id="idm46222409481536"></a><p class="title"><strong>Table C.1. MicroPeak EEPROM Data Storage</strong></p><div class="table-contents"><table summary="MicroPeak EEPROM Data Storage" cellpadding="4px" style="border-collapse: collapse;border-top: 1px solid #78079a; border-bottom: 1px solid #78079a; border-left: 1px solid #78079a; border-right: 1px solid #78079a; "><colgroup><col class="col_1" /><col class="col_2" /><col class="col_3" /></colgroup><tbody><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Address</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Size (bytes)</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Description</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>0x000</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>4</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Average ground pressure (Pa)</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>0x004</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>4</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Minimum flight pressure (Pa)</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>0x008</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>2</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Number of in-flight samples</p></td></tr><tr><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>0x00a … 0x1fe</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>2</p></td><td style="" align="left" valign="top"><p>Instantaneous flight pressure (Pa) low 16 bits</p></td></tr></tbody></table></div></div><br class="table-break" /><p>All EEPROM data are stored least-significant byte first. The +instantaneous flight pressure data are stored without the +upper 16 bits of data. The upper bits can be reconstructed +from the previous sample, assuming that pressure doesn’t +change by more more than 32kPa in a single sample +interval. Note that this pressure data is <span class="strong"><strong>not</strong></span> filtered in +any way, while both the recorded ground and apogee pressure +values are, so you shouldn’t expect the minimum instantaneous +pressure value to match the recorded minimum pressure value +exactly.</p><p>MicroPeak samples pressure every 96ms, but stores only every +other sample in the EEPROM. This provides for 251 pressure +samples at 192ms intervals, or 48.192s of storage. The clock +used for these samples is a factory calibrated RC circuit +built into the ATtiny85 and is accurate only to within ±10% at +25°C. So, you can count on the pressure data being accurate, +but speed or acceleration data computed from this will be +limited by the accuracy of this clock.</p></div></div></body></html>
\ No newline at end of file diff --git a/AltOS/doc/micropeak.pdf b/AltOS/doc/micropeak.pdf Binary files differindex 9d21e31..32adf76 100644 --- a/AltOS/doc/micropeak.pdf +++ b/AltOS/doc/micropeak.pdf diff --git a/AltOS/doc/release-notes-0.7.1.html b/AltOS/doc/release-notes-0.7.1.html index 7a1f22b..4aba5b1 100644 --- a/AltOS/doc/release-notes-0.7.1.html +++ b/AltOS/doc/release-notes-0.7.1.html @@ -1,42 +1,48 @@ -<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title></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="article"><div class="titlepage"><hr></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></body></html> +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Release Notes for Version 0.7.1</title><link rel="stylesheet" type="text/css" href="am.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.78.1" /></head><body><div xml:lang="en" class="article" lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="idm44963605602096"></a>Release Notes for Version 0.7.1</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Bdale</span> <span class="surname">Garbee</span></h3><code class="email"><<a class="email" href="mailto:bdale@gag.com">bdale@gag.com</a>></code></div></div><div><div class="author"><h3 class="author"><span class="firstname">Keith</span> <span class="surname">Packard</span></h3><code class="email"><<a class="email" href="mailto:keithp@keithp.com">keithp@keithp.com</a>></code></div></div><div><p class="copyright">Copyright © 2010 Bdale Garbee and Keith Packard</p></div><div><div class="legalnotice"><a id="idm44963604916640"></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><hr /></div><p>Version 0.7.1 is the first release containing our new +cross-platform Java-based user interface.</p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_altosui_application"></a>1. AltosUI Application</h2></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +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. +</li><li class="listitem"> +Download logged data from TeleMetrum devices, either through +a direct USB connection or over the air through a TeleDongle +device. +</li><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li></ul></div></div></div></body></html>
\ No newline at end of file diff --git a/AltOS/doc/release-notes-0.7.1.pdf b/AltOS/doc/release-notes-0.7.1.pdf Binary files differnew file mode 100644 index 0000000..83f740c --- /dev/null +++ b/AltOS/doc/release-notes-0.7.1.pdf diff --git a/AltOS/doc/release-notes-0.8.html b/AltOS/doc/release-notes-0.8.html index 8ace7a9..bd1359b 100644 --- a/AltOS/doc/release-notes-0.8.html +++ b/AltOS/doc/release-notes-0.8.html @@ -1,41 +1,48 @@ -<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title></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="article"><div class="titlepage"><hr></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></body></html> +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Release Notes for Version 0.8</title><link rel="stylesheet" type="text/css" href="am.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.78.1" /></head><body><div xml:lang="en" class="article" lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="idm45383193986496"></a>Release Notes for Version 0.8</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Bdale</span> <span class="surname">Garbee</span></h3><code class="email"><<a class="email" href="mailto:bdale@gag.com">bdale@gag.com</a>></code></div></div><div><div class="author"><h3 class="author"><span class="firstname">Keith</span> <span class="surname">Packard</span></h3><code class="email"><<a class="email" href="mailto:keithp@keithp.com">keithp@keithp.com</a>></code></div></div><div><p class="copyright">Copyright © 2010 Bdale Garbee and Keith Packard</p></div><div><div class="legalnotice"><a id="idm45383195396112"></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><hr /></div><p>Version 0.8 offers a major upgrade in the AltosUI +interface.</p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_altosui_application"></a>1. AltosUI Application:</h2></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li><li class="listitem"> +Optimized flight status displays. Each flight state now has +it’s own custom <span class="emphasis"><em>tab</em></span> 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. +</li><li class="listitem"> +Monitor multiple flights simultaneously. If you have more +than one TeleDongle, you can monitor a flight with each one +on the same computer. +</li><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li></ul></div></div></div></body></html>
\ No newline at end of file diff --git a/AltOS/doc/release-notes-0.8.pdf b/AltOS/doc/release-notes-0.8.pdf Binary files differnew file mode 100644 index 0000000..1fa3b40 --- /dev/null +++ b/AltOS/doc/release-notes-0.8.pdf diff --git a/AltOS/doc/release-notes-0.9.2.html b/AltOS/doc/release-notes-0.9.2.html index 9e16524..a75a62d 100644 --- a/AltOS/doc/release-notes-0.9.2.html +++ b/AltOS/doc/release-notes-0.9.2.html @@ -1,9 +1,17 @@ -<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title></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="article"><div class="titlepage"><hr></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></body></html> +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Release Notes for Version 0.9.2</title><link rel="stylesheet" type="text/css" href="am.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.78.1" /></head><body><div xml:lang="en" class="article" lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="idm45823547640848"></a>Release Notes for Version 0.9.2</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Bdale</span> <span class="surname">Garbee</span></h3><code class="email"><<a class="email" href="mailto:bdale@gag.com">bdale@gag.com</a>></code></div></div><div><div class="author"><h3 class="author"><span class="firstname">Keith</span> <span class="surname">Packard</span></h3><code class="email"><<a class="email" href="mailto:keithp@keithp.com">keithp@keithp.com</a>></code></div></div><div><p class="copyright">Copyright © 2011 Bdale Garbee and Keith Packard</p></div><div><div class="legalnotice"><a id="idm45823547805616"></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><hr /></div><p>Version 0.9.2 is an AltosUI bug-fix release, with no firmware +changes.</p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_altosui"></a>1. AltosUI</h2></div></div></div><p>AltosUI fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Fix plotting problems due to missing file in the Mac +OS install image. +</li><li class="listitem"> +Always read whole eeprom blocks, mark empty records +invalid, display parsing errors to user. +</li><li class="listitem"> +Add software version to Configure AltosUI dialog +</li></ul></div></div></div></body></html>
\ No newline at end of file diff --git a/AltOS/doc/release-notes-0.9.2.pdf b/AltOS/doc/release-notes-0.9.2.pdf Binary files differnew file mode 100644 index 0000000..d70aa3b --- /dev/null +++ b/AltOS/doc/release-notes-0.9.2.pdf diff --git a/AltOS/doc/release-notes-0.9.html b/AltOS/doc/release-notes-0.9.html index f5ed9a7..d534e4a 100644 --- a/AltOS/doc/release-notes-0.9.html +++ b/AltOS/doc/release-notes-0.9.html @@ -1,20 +1,30 @@ -<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title></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="article"><div class="titlepage"><hr></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></body></html> +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Release Notes for Version 0.9</title><link rel="stylesheet" type="text/css" href="am.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.78.1" /></head><body><div xml:lang="en" class="article" lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="idm45727429924624"></a>Release Notes for Version 0.9</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Bdale</span> <span class="surname">Garbee</span></h3><code class="email"><<a class="email" href="mailto:bdale@gag.com">bdale@gag.com</a>></code></div></div><div><div class="author"><h3 class="author"><span class="firstname">Keith</span> <span class="surname">Packard</span></h3><code class="email"><<a class="email" href="mailto:keithp@keithp.com">keithp@keithp.com</a>></code></div></div><div><p class="copyright">Copyright © 2011 Bdale Garbee and Keith Packard</p></div><div><div class="legalnotice"><a id="idm45727429178448"></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><hr /></div><p>Version 0.9 adds a few new firmware features and accompanying +AltosUI changes, along with new hardware support.</p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_altos"></a>1. AltOS</h2></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_altosui_application"></a>2. AltosUI Application</h2></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Support for telemetry format changes. +</li><li class="listitem"> +Support for multiple flight logs. +</li></ul></div></div></div></body></html>
\ No newline at end of file diff --git a/AltOS/doc/release-notes-0.9.pdf b/AltOS/doc/release-notes-0.9.pdf Binary files differnew file mode 100644 index 0000000..f5c9671 --- /dev/null +++ b/AltOS/doc/release-notes-0.9.pdf diff --git a/AltOS/doc/release-notes-1.0.1.html b/AltOS/doc/release-notes-1.0.1.html index a58fed6..c01939e 100644 --- a/AltOS/doc/release-notes-1.0.1.html +++ b/AltOS/doc/release-notes-1.0.1.html @@ -1,81 +1,88 @@ -<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title></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="article"><div class="titlepage"><hr></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></body></html> +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Release Notes for Version 1.0.1</title><link rel="stylesheet" type="text/css" href="am.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.78.1" /></head><body><div xml:lang="en" class="article" lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="idm45643182896304"></a>Release Notes for Version 1.0.1</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Bdale</span> <span class="surname">Garbee</span></h3><code class="email"><<a class="email" href="mailto:bdale@gag.com">bdale@gag.com</a>></code></div></div><div><div class="author"><h3 class="author"><span class="firstname">Keith</span> <span class="surname">Packard</span></h3><code class="email"><<a class="email" href="mailto:keithp@keithp.com">keithp@keithp.com</a>></code></div></div><div><p class="copyright">Copyright © 2011 Bdale Garbee and Keith Packard</p></div><div><div class="legalnotice"><a id="idm45643183043184"></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><hr /></div><p>Version 1.0.1 is a major release, adding support for the +TeleMini device and lots of new AltosUI features</p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_altos"></a>1. AltOS</h2></div></div></div><p>AltOS New Features</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Add TeleMini v1.0 support. +</li><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li><li class="listitem"> +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 <span class="emphasis"><em>channels</em></span>, +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. +</li></ul></div><p>AltOS Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_altosui_application"></a>2. AltosUI Application</h2></div></div></div><p>AltosUI New Features</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Add main/apogee voltage graphs to the data +plot. This provides a visual indication if the +igniters fail before being fired. +</li><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li><li class="listitem"> +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 <span class="emphasis"><em>Landed</em></span> tab in the Monitor Flight +window so you can immediately see the results of a +flight. +</li></ul></div><p>AltosUI Changes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +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. +</li></ul></div></div></div></body></html>
\ No newline at end of file diff --git a/AltOS/doc/release-notes-1.0.1.pdf b/AltOS/doc/release-notes-1.0.1.pdf Binary files differnew file mode 100644 index 0000000..d0cf32b --- /dev/null +++ b/AltOS/doc/release-notes-1.0.1.pdf diff --git a/AltOS/doc/release-notes-1.1.1.html b/AltOS/doc/release-notes-1.1.1.html index 2281d94..a800c40 100644 --- a/AltOS/doc/release-notes-1.1.1.html +++ b/AltOS/doc/release-notes-1.1.1.html @@ -1,46 +1,50 @@ -<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title></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="article"><div class="titlepage"><hr></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></body></html> +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Release Notes for Version 1.1</title><link rel="stylesheet" type="text/css" href="am.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.78.1" /></head><body><div xml:lang="en" class="article" lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="idm45495557658240"></a>Release Notes for Version 1.1</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Bdale</span> <span class="surname">Garbee</span></h3><code class="email"><<a class="email" href="mailto:bdale@gag.com">bdale@gag.com</a>></code></div></div><div><div class="author"><h3 class="author"><span class="firstname">Keith</span> <span class="surname">Packard</span></h3><code class="email"><<a class="email" href="mailto:keithp@keithp.com">keithp@keithp.com</a>></code></div></div><div><p class="copyright">Copyright © 2012 Bdale Garbee and Keith Packard</p></div><div><div class="legalnotice"><a id="idm45495557772624"></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><hr /></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><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_altos"></a>1. AltOS</h2></div></div></div><p>AltOS fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +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. +</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_altosui"></a>2. AltosUI</h2></div></div></div><p>AltosUI new features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +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. +</li></ul></div><p>AltosUI fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li></ul></div></div></div></body></html>
\ No newline at end of file diff --git a/AltOS/doc/release-notes-1.1.1.pdf b/AltOS/doc/release-notes-1.1.1.pdf Binary files differnew file mode 100644 index 0000000..4a7ad5f --- /dev/null +++ b/AltOS/doc/release-notes-1.1.1.pdf diff --git a/AltOS/doc/release-notes-1.1.html b/AltOS/doc/release-notes-1.1.html index c1be788..0ef54c3 100644 --- a/AltOS/doc/release-notes-1.1.html +++ b/AltOS/doc/release-notes-1.1.html @@ -1,73 +1,83 @@ -<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title></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="article"><div class="titlepage"><hr></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></body></html> +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Release Notes for Version 1.1</title><link rel="stylesheet" type="text/css" href="am.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.78.1" /></head><body><div xml:lang="en" class="article" lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="idm45793842102736"></a>Release Notes for Version 1.1</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Bdale</span> <span class="surname">Garbee</span></h3><code class="email"><<a class="email" href="mailto:bdale@gag.com">bdale@gag.com</a>></code></div></div><div><div class="author"><h3 class="author"><span class="firstname">Keith</span> <span class="surname">Packard</span></h3><code class="email"><<a class="email" href="mailto:keithp@keithp.com">keithp@keithp.com</a>></code></div></div><div><p class="copyright">Copyright © 2013 Bdale Garbee and Keith Packard</p></div><div><div class="legalnotice"><a id="idm45793841365680"></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><hr /></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><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_altos"></a>1. AltOS</h2></div></div></div><p>AltOS Firmware New Features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Add apogee-lockout value. Overrides the apogee +detection logic to prevent incorrect apogee charge +firing. +</li><li class="listitem"> +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. +</li><li class="listitem"> +Provide RSSI values for Monitor Idle mode. This +makes it easy to check radio range without needing +to go to flight mode. +</li></ul></div><p>AltOS Fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Fix a bug where the data reported in telemetry +packets was from 320ms ago. +</li><li class="listitem"> +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. +</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_altosui"></a>2. AltosUI</h2></div></div></div><p>AltosUI New Features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Make the look-n-feel configurable, providing a choice from +the available options. +</li><li class="listitem"> +Add an <span class="emphasis"><em>Age</em></span> element to mark how long since a +telemetry packet has been received. Useful to +quickly gauge whether communications with the rocket +are still active. +</li><li class="listitem"> +Add <span class="emphasis"><em>Configure Ground Station</em></span> dialog to set the +radio frequency used by a particular TeleDongle +without having to go through the flight monitor UI. +</li><li class="listitem"> +Add configuration for the new apogee-lockout +value. A menu provides a list of reasonable values, +or the value can be set by hand. +</li><li class="listitem"> +Add Imperial units mode to present data in feet +instead of meters. +</li></ul></div><p>AltosUI Fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li><li class="listitem"> +Change how data are displayed in the <span class="emphasis"><em>table</em></span> 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 <span class="emphasis"><em>Monitor Idle</em></span> mode. +</li></ul></div></div></div></body></html>
\ No newline at end of file diff --git a/AltOS/doc/release-notes-1.1.pdf b/AltOS/doc/release-notes-1.1.pdf Binary files differnew file mode 100644 index 0000000..56cde60 --- /dev/null +++ b/AltOS/doc/release-notes-1.1.pdf diff --git a/AltOS/doc/release-notes-1.2.1.html b/AltOS/doc/release-notes-1.2.1.html index b2943dc..c437704 100644 --- a/AltOS/doc/release-notes-1.2.1.html +++ b/AltOS/doc/release-notes-1.2.1.html @@ -1,61 +1,66 @@ -<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title></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="article"><div class="titlepage"><hr></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></body></html> +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Release Notes for Version 1.2.1</title><link rel="stylesheet" type="text/css" href="am.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.78.1" /></head><body><div xml:lang="en" class="article" lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="idm45575208742624"></a>Release Notes for Version 1.2.1</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Bdale</span> <span class="surname">Garbee</span></h3><code class="email"><<a class="email" href="mailto:bdale@gag.com">bdale@gag.com</a>></code></div></div><div><div class="author"><h3 class="author"><span class="firstname">Keith</span> <span class="surname">Packard</span></h3><code class="email"><<a class="email" href="mailto:keithp@keithp.com">keithp@keithp.com</a>></code></div></div><div><p class="copyright">Copyright © 2013 Bdale Garbee and Keith Packard</p></div><div><div class="legalnotice"><a id="idm45575207980576"></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><hr /></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><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_altos"></a>1. AltOS</h2></div></div></div><p>AltOS new features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Add support for TeleBT +</li></ul></div><p>AltOS fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +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). +</li><li class="listitem"> +Correct Kalman filter model error covariance +matrix. The values used previously assumed +continuous measurements instead of discrete +measurements. +</li><li class="listitem"> +Fix some bugs in the USB driver for TeleMetrum and +TeleDongle that affected Windows users. +</li><li class="listitem"> +Adjusted the automatic gain control parameters that +affect receive performance for TeleDongle. Field +tests indicate that this may improve receive +performance somewhat. +</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_altosui_application"></a>2. AltosUI Application</h2></div></div></div><p>AltosUI application new features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Make the initial position of the AltosUI top level +window configurable. Along with this change, the +other windows will pop up at <span class="emphasis"><em>sensible</em></span> places now, +instead of on top of one another. +</li><li class="listitem"> +Add GPS data and a map to the graph window. This +lets you see a complete summary of the flight +without needing to <span class="emphasis"><em>replay</em></span> the whole thing. +</li></ul></div><p>AltosUI application fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Handle missing GPS lock in <span class="emphasis"><em>Descent</em></span> +tab. Previously, if the GPS position of the pad was +unknown, an exception would be raised, breaking the +Descent tab contents. +</li><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_altosdroid"></a>3. AltosDroid</h2></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +First version of this application +</li></ul></div></div></div></body></html>
\ No newline at end of file diff --git a/AltOS/doc/release-notes-1.2.1.pdf b/AltOS/doc/release-notes-1.2.1.pdf Binary files differnew file mode 100644 index 0000000..b05ffef --- /dev/null +++ b/AltOS/doc/release-notes-1.2.1.pdf diff --git a/AltOS/doc/release-notes-1.2.html b/AltOS/doc/release-notes-1.2.html index e9a4eb7..4c62ae0 100644 --- a/AltOS/doc/release-notes-1.2.html +++ b/AltOS/doc/release-notes-1.2.html @@ -1,27 +1,25 @@ -<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title></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="article"><div class="titlepage"><hr></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></body></html> +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Release Notes for Version 1.2</title><link rel="stylesheet" type="text/css" href="am.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.78.1" /></head><body><div xml:lang="en" class="article" lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="idm45800497156992"></a>Release Notes for Version 1.2</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Bdale</span> <span class="surname">Garbee</span></h3><code class="email"><<a class="email" href="mailto:bdale@gag.com">bdale@gag.com</a>></code></div></div><div><div class="author"><h3 class="author"><span class="firstname">Keith</span> <span class="surname">Packard</span></h3><code class="email"><<a class="email" href="mailto:keithp@keithp.com">keithp@keithp.com</a>></code></div></div><div><p class="copyright">Copyright © 2013 Bdale Garbee and Keith Packard</p></div><div><div class="legalnotice"><a id="idm45800497219696"></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><hr /></div><p>Version 1.2 is a major release. It adds support for MicroPeak +and the MicroPeak USB adapter.</p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_altos"></a>1. AltOS</h2></div></div></div><p>AltOS New Features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +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. +</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_altosui_and_micropeak_application"></a>2. AltosUI and MicroPeak Application</h2></div></div></div><p>New Features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Added MicroPeak application +</li></ul></div><p>AltosUI and MicroPeak fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Distribute Mac OS X packages in disk image (<span class="emphasis"><em>.dmg</em></span>) +format to greatly simplify installation. +</li><li class="listitem"> +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. +</li></ul></div></div></div></body></html>
\ No newline at end of file diff --git a/AltOS/doc/release-notes-1.2.pdf b/AltOS/doc/release-notes-1.2.pdf Binary files differnew file mode 100644 index 0000000..59c61cf --- /dev/null +++ b/AltOS/doc/release-notes-1.2.pdf diff --git a/AltOS/doc/release-notes-1.3.1.html b/AltOS/doc/release-notes-1.3.1.html index 8f82e36..7f49827 100644 --- a/AltOS/doc/release-notes-1.3.1.html +++ b/AltOS/doc/release-notes-1.3.1.html @@ -1,43 +1,45 @@ -<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title></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="article"><div class="titlepage"><hr></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></body></html> +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Release Notes for Version 1.3.1</title><link rel="stylesheet" type="text/css" href="am.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.78.1" /></head><body><div xml:lang="en" class="article" lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="idm46116135990864"></a>Release Notes for Version 1.3.1</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Bdale</span> <span class="surname">Garbee</span></h3><code class="email"><<a class="email" href="mailto:bdale@gag.com">bdale@gag.com</a>></code></div></div><div><div class="author"><h3 class="author"><span class="firstname">Keith</span> <span class="surname">Packard</span></h3><code class="email"><<a class="email" href="mailto:keithp@keithp.com">keithp@keithp.com</a>></code></div></div><div><p class="copyright">Copyright © 2014 Bdale Garbee and Keith Packard</p></div><div><div class="legalnotice"><a id="idm46116136143216"></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><hr /></div><p>Version 1.3.1 is a minor release. It improves support for +TeleMega, TeleMetrum v2.0, TeleMini v2.0 and EasyMini.</p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_altos"></a>1. AltOS</h2></div></div></div><p>AltOS new features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +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. +</li></ul></div><p>AltOS fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_altosui_application"></a>2. AltosUI Application</h2></div></div></div><p>AltosUI new features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li></ul></div><p>AltosUI fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +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. +</li></ul></div></div></div></body></html>
\ No newline at end of file diff --git a/AltOS/doc/release-notes-1.3.1.pdf b/AltOS/doc/release-notes-1.3.1.pdf Binary files differnew file mode 100644 index 0000000..9a12a39 --- /dev/null +++ b/AltOS/doc/release-notes-1.3.1.pdf diff --git a/AltOS/doc/release-notes-1.3.2.html b/AltOS/doc/release-notes-1.3.2.html index aa5ad51..29853ff 100644 --- a/AltOS/doc/release-notes-1.3.2.html +++ b/AltOS/doc/release-notes-1.3.2.html @@ -1,29 +1,32 @@ -<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title></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="article"><div class="titlepage"><hr></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></body></html> +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Release Notes for Version 1.3.2</title><link rel="stylesheet" type="text/css" href="am.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.78.1" /></head><body><div xml:lang="en" class="article" lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="idm45777924924144"></a>Release Notes for Version 1.3.2</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Bdale</span> <span class="surname">Garbee</span></h3><code class="email"><<a class="email" href="mailto:bdale@gag.com">bdale@gag.com</a>></code></div></div><div><div class="author"><h3 class="author"><span class="firstname">Keith</span> <span class="surname">Packard</span></h3><code class="email"><<a class="email" href="mailto:keithp@keithp.com">keithp@keithp.com</a>></code></div></div><div><p class="copyright">Copyright © 2014 Bdale Garbee and Keith Packard</p></div><div><div class="legalnotice"><a id="idm45777924987680"></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><hr /></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><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_altos"></a>1. AltOS</h2></div></div></div><p>AltOS fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +On TeleMega, limit number of logged GPS status +information to 12 satellites. That’s all there is +room for in the log structure. +</li><li class="listitem"> +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. +</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_altosui_application"></a>2. AltosUI Application</h2></div></div></div><p>AltosUI fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +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. +</li><li class="listitem"> +Track the maximum height as computed from GPS +altitude data and report that in the flight summary +data. +</li><li class="listitem"> +Use letters (A, B, C, D) for alternate pyro channel +names instead of numbers (0, 1, 2, 3) in the Fire +Igniter dialog. +</li></ul></div></div></div></body></html>
\ No newline at end of file diff --git a/AltOS/doc/release-notes-1.3.2.pdf b/AltOS/doc/release-notes-1.3.2.pdf Binary files differnew file mode 100644 index 0000000..0445f11 --- /dev/null +++ b/AltOS/doc/release-notes-1.3.2.pdf diff --git a/AltOS/doc/release-notes-1.3.html b/AltOS/doc/release-notes-1.3.html index 7000d2b..038563a 100644 --- a/AltOS/doc/release-notes-1.3.html +++ b/AltOS/doc/release-notes-1.3.html @@ -1,42 +1,46 @@ -<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title></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="article"><div class="titlepage"><hr></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></body></html> +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Release Notes for Version 1.3</title><link rel="stylesheet" type="text/css" href="am.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.78.1" /></head><body><div xml:lang="en" class="article" lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="idm45594197557488"></a>Release Notes for Version 1.3</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Bdale</span> <span class="surname">Garbee</span></h3><code class="email"><<a class="email" href="mailto:bdale@gag.com">bdale@gag.com</a>></code></div></div><div><div class="author"><h3 class="author"><span class="firstname">Keith</span> <span class="surname">Packard</span></h3><code class="email"><<a class="email" href="mailto:keithp@keithp.com">keithp@keithp.com</a>></code></div></div><div><p class="copyright">Copyright © 2013 Bdale Garbee and Keith Packard</p></div><div><div class="legalnotice"><a id="idm45594196824624"></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><hr /></div><p>Version 1.3 is a major release. It adds support for TeleMega, +TeleMetrum v2.0, TeleMini v2.0 and EasyMini.</p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_altos"></a>1. AltOS</h2></div></div></div><p>AltOS new features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Add STM32L processor support. This includes +enhancements to the scheduler to support products +with many threads. +</li><li class="listitem"> +Add NXP LPC11U14 processor support. +</li><li class="listitem"> +Support additional pyro channels. These are +configurable through the UI to handle air starts, +staging, additional recovery events and external +devices such as cameras. +</li><li class="listitem"> +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. +</li><li class="listitem"> +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 +</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_altosui_application"></a>2. AltosUI Application</h2></div></div></div><p>AltosUI new features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Support TeleMega, TeleMetrum v2.0, TeleMini v2.0 and +EasyMini telemetry and log formats. +</li></ul></div><p>AltosUI fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Use preferred units for main deployment height +configuration, instead of always doing configuration in +meters. +== MicroPeak Application +</li><li class="listitem"> +Add <span class="emphasis"><em>Download</em></span> button to menu bar. +</li><li class="listitem"> +Save the last log directory and offer that as the +default for new downloads +</li></ul></div></div></div></body></html>
\ No newline at end of file diff --git a/AltOS/doc/release-notes-1.3.pdf b/AltOS/doc/release-notes-1.3.pdf Binary files differnew file mode 100644 index 0000000..ef94834 --- /dev/null +++ b/AltOS/doc/release-notes-1.3.pdf diff --git a/AltOS/doc/release-notes-1.4.1.html b/AltOS/doc/release-notes-1.4.1.html index a6da4cf..f34250a 100644 --- a/AltOS/doc/release-notes-1.4.1.html +++ b/AltOS/doc/release-notes-1.4.1.html @@ -1,32 +1,31 @@ -<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title></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="article"><div class="titlepage"><hr></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></body></html> +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Release Notes for Version 1.4.1</title><link rel="stylesheet" type="text/css" href="am.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.78.1" /></head><body><div xml:lang="en" class="article" lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="idm46108124935024"></a>Release Notes for Version 1.4.1</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Bdale</span> <span class="surname">Garbee</span></h3><code class="email"><<a class="email" href="mailto:bdale@gag.com">bdale@gag.com</a>></code></div></div><div><div class="author"><h3 class="author"><span class="firstname">Keith</span> <span class="surname">Packard</span></h3><code class="email"><<a class="email" href="mailto:keithp@keithp.com">keithp@keithp.com</a>></code></div></div><div><p class="copyright">Copyright © 2014 Bdale Garbee and Keith Packard</p></div><div><div class="legalnotice"><a id="idm46108124122208"></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><hr /></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><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_altosui_and_telegps_applications"></a>1. AltosUI and TeleGPS Applications:</h2></div></div></div><p>Windows Install Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Provide signed Windows driver files. This should avoid any need to +disable driver signature checking on Windows 7 or 8. +</li><li class="listitem"> +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. +</li></ul></div><p>Other Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li></ul></div></div></div></body></html>
\ No newline at end of file diff --git a/AltOS/doc/release-notes-1.4.1.pdf b/AltOS/doc/release-notes-1.4.1.pdf Binary files differnew file mode 100644 index 0000000..3b5ee3e --- /dev/null +++ b/AltOS/doc/release-notes-1.4.1.pdf diff --git a/AltOS/doc/release-notes-1.4.2.html b/AltOS/doc/release-notes-1.4.2.html new file mode 100644 index 0000000..5dbc76f --- /dev/null +++ b/AltOS/doc/release-notes-1.4.2.html @@ -0,0 +1,14 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Release Notes for Version 1.4.2</title><link rel="stylesheet" type="text/css" href="am.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.78.1" /></head><body><div xml:lang="en" class="article" lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="idm46117876744784"></a>Release Notes for Version 1.4.2</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Bdale</span> <span class="surname">Garbee</span></h3><code class="email"><<a class="email" href="mailto:bdale@gag.com">bdale@gag.com</a>></code></div></div><div><div class="author"><h3 class="author"><span class="firstname">Keith</span> <span class="surname">Packard</span></h3><code class="email"><<a class="email" href="mailto:keithp@keithp.com">keithp@keithp.com</a>></code></div></div><div><p class="copyright">Copyright © 2014 Bdale Garbee and Keith Packard</p></div><div><div class="legalnotice"><a id="idm46117876892272"></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><hr /></div><p>Version 1.4.2 is a minor release. It fixes Java-related install issues on +Windows</p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_altosui_and_telegps_applications"></a>1. AltosUI and TeleGPS Applications</h2></div></div></div><p>Windows Install Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Checks for Java installation data in more registry locations. +</li><li class="listitem"> +Allows user to bypass Java installation in case the +detection fails. +</li></ul></div></div></div></body></html>
\ No newline at end of file diff --git a/AltOS/doc/release-notes-1.4.2.pdf b/AltOS/doc/release-notes-1.4.2.pdf Binary files differnew file mode 100644 index 0000000..2791554 --- /dev/null +++ b/AltOS/doc/release-notes-1.4.2.pdf diff --git a/AltOS/doc/release-notes-1.4.html b/AltOS/doc/release-notes-1.4.html index 01df042..5b20ecd 100644 --- a/AltOS/doc/release-notes-1.4.html +++ b/AltOS/doc/release-notes-1.4.html @@ -1,114 +1,110 @@ -<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title></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="article"><div class="titlepage"><hr></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></body></html> +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Release Notes for Version 1.4</title><link rel="stylesheet" type="text/css" href="am.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.78.1" /></head><body><div xml:lang="en" class="article" lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="idm45858957362192"></a>Release Notes for Version 1.4</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Bdale</span> <span class="surname">Garbee</span></h3><code class="email"><<a class="email" href="mailto:bdale@gag.com">bdale@gag.com</a>></code></div></div><div><div class="author"><h3 class="author"><span class="firstname">Keith</span> <span class="surname">Packard</span></h3><code class="email"><<a class="email" href="mailto:keithp@keithp.com">keithp@keithp.com</a>></code></div></div><div><p class="copyright">Copyright © 2014 Bdale Garbee and Keith Packard</p></div><div><div class="legalnotice"><a id="idm45858956544608"></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><hr /></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><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_altos"></a>1. AltOS</h2></div></div></div><p>AltOS new features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Add support for TeleGPS boards. +</li><li class="listitem"> +Make the beeper tone configurable, making it +possible to distinguish between two Altus Metrum +products in the same ebay. +</li><li class="listitem"> +Make the firing time for extra pyro channels +configurable, allowing longer (or shorter) than the +default 50ms. Only relevant for TeleMega at this +time. +</li></ul></div><p>AltOS fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Replace the <span class="emphasis"><em>dit dit dit</em></span> 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. +</li><li class="listitem"> +Change state beeping to "Farnsworth spacing", which +means they’re quite a bit faster than before, and so +they take less time to send. +</li><li class="listitem"> +Fix bug preventing the selection of the <span class="emphasis"><em>Flight +State After</em></span> mode in pyro configuration. +</li><li class="listitem"> +Fix bug where erasing flights would reset the flight +number to 2 on TeleMega and TeleMetrum v2. +</li><li class="listitem"> +Fix u-Blox GPS driver to mark course and speed data +as being present. +</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_altosui_application"></a>2. AltosUI Application</h2></div></div></div><p>AltosUI new features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li><li class="listitem"> +Add new <span class="emphasis"><em>Ignitor</em></span> tab to the flight monitor display +for TeleMega’s extra ignitors. +</li><li class="listitem"> +Add additional ignitor firing marks and voltages to +the graph so you can see when the ignitors fired, +along with the ignitor voltages. +</li><li class="listitem"> +Add GPS course, ground speed and climb rate as +optional graph elements. +</li></ul></div><p>AltosUI fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +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. +</li><li class="listitem"> +Hide Tilt Angle in ascent tab for devices that don’t +have a gyro. +</li><li class="listitem"> +Increase the width of data lines in the graphs to +make them easier to read. +</li><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li><li class="listitem"> +Display error message when trying to configure +maximum flight log size while the flight computer +still has flight data stored. +</li><li class="listitem"> +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. +</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_telegps_application"></a>3. TeleGPS Application</h2></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +New application designed for use with TeleGPS boards. +</li><li class="listitem"> +Shares code with AltosUI, mostly just trimmed down +to focus on TeleGPS-related functions. +</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_documentation"></a>4. Documentation</h2></div></div></div><p>Documentation changes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +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. +</li><li class="listitem"> +Add a description of the <span class="emphasis"><em>Apogee Lockout</em></span> setting, +which prevents the apogee charge from firing for a +configurable amount of time after boost. +</li></ul></div></div></div></body></html>
\ No newline at end of file diff --git a/AltOS/doc/release-notes-1.4.pdf b/AltOS/doc/release-notes-1.4.pdf Binary files differnew file mode 100644 index 0000000..3dc1a90 --- /dev/null +++ b/AltOS/doc/release-notes-1.4.pdf diff --git a/AltOS/doc/release-notes-1.5.html b/AltOS/doc/release-notes-1.5.html index b1ed4a9..210e36f 100644 --- a/AltOS/doc/release-notes-1.5.html +++ b/AltOS/doc/release-notes-1.5.html @@ -1,68 +1,61 @@ -<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title></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="article"><div class="titlepage"><hr></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></body></html> +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Release Notes for Version 1.5</title><link rel="stylesheet" type="text/css" href="am.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.78.1" /></head><body><div xml:lang="en" class="article" lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="idm45039062682368"></a>Release Notes for Version 1.5</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Bdale</span> <span class="surname">Garbee</span></h3><code class="email"><<a class="email" href="mailto:bdale@gag.com">bdale@gag.com</a>></code></div></div><div><div class="author"><h3 class="author"><span class="firstname">Keith</span> <span class="surname">Packard</span></h3><code class="email"><<a class="email" href="mailto:keithp@keithp.com">keithp@keithp.com</a>></code></div></div><div><p class="copyright">Copyright © 2014 Bdale Garbee and Keith Packard</p></div><div><div class="legalnotice"><a id="idm45039062850176"></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><hr /></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><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_altos"></a>1. AltOS</h2></div></div></div><p>AltOS New Features</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Add support for EasyMega boards. +</li><li class="listitem"> +Make the APRS SSID be configurable. This lets you track +different rockets on the same receiver without getting +things mixed up. +</li><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li></ul></div><p>AltOS Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Increase the maximum range for altitude values from +/-32767m +to +/-2147483647m, allowing the flight computers to function +correctly above the 32km level. +</li><li class="listitem"> +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. +</li><li class="listitem"> +Allow negative numbers in pyro configuration values. This +lets you specify things like descending speed or +deceleration. +</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_altosui_and_telegps_applications"></a>2. AltosUI and TeleGPS Applications</h2></div></div></div><p>AltosUI and TeleGPS New Features</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Support telemetry baud rate selection. Adds menus to +the flight monitoring and configuration for baud rate +selection. +</li><li class="listitem"> +Support APRS SSID configuration. +</li><li class="listitem"> +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. +</li></ul></div><p>AltosUI Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Make the <span class="emphasis"><em>Graph</em></span> button on the landed tab work again. +</li><li class="listitem"> +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. +</li></ul></div></div></div></body></html>
\ No newline at end of file diff --git a/AltOS/doc/release-notes-1.5.pdf b/AltOS/doc/release-notes-1.5.pdf Binary files differnew file mode 100644 index 0000000..52e7baf --- /dev/null +++ b/AltOS/doc/release-notes-1.5.pdf diff --git a/AltOS/doc/release-notes-1.6.1.html b/AltOS/doc/release-notes-1.6.1.html index 26e6c26..5229202 100644 --- a/AltOS/doc/release-notes-1.6.1.html +++ b/AltOS/doc/release-notes-1.6.1.html @@ -1,99 +1,86 @@ -<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title></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="article"><div class="titlepage"><hr></div><p> - Version 1.6.1 includes support for our updated TeleBT v3.0 - product and bug fixes in in the flight software for all our boards - and ground station interfaces. - </p><p> - AltOS New Features - </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p> - Add support for TeleBT v3.0 boards. - </p></li><li class="listitem"><p> - Add support for uncompressed APRS data, providing support - for older APRS receivers. Uncompressed APRS data is less - precise, takes more bandwidth and doesn't have integrated - altitude data. - </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> - Make TeleDongle and TeleBT more tolerant of data rate - variations from transmitting devices. - </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> - Add map to Monitor Idle display. It's nice to be able to - verify that maps are working, instead of needing to use - Monitor Flight. - </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> - Fix frequency configuration to round values instead of - truncate them, avoiding a common 1kHz error in the setting. - </p></li><li class="listitem"><p> - Turn the Windows stub into a more useful program that can - launch the application with parameters so that file manager - icons work more reliably. - </p></li><li class="listitem"><p> - Force KML export to use a C locale so that numbers are - formatted with '.' instead of ',' for a decimal separator in - non-US locales. - </p></li><li class="listitem"><p> - Preload map tiles based on distance rather than number of - tiles; this means you get the same resolution covering the - entire area, rather than having high resolution near the - center and low resolution further away. - </p></li><li class="listitem"><p> - Allow configuration of frequency and callsign in Monitor - Idle mode. - </p></li><li class="listitem"><p> - Fix layout weirdness when resizing windows on - Windows. Windows shouldn't have giant blank spaces around - the useful content anymore. - </p></li><li class="listitem"><p> - Fix layout weirdness when resizing windows on - Windows. Windows shouldn't have giant blank spaces around - the useful content anymore. - </p></li><li class="listitem"><p> - Use a longer filter for descent speed values. This should - provide something more useful on the display, although it - will take longer to respond to changes now. - </p></li><li class="listitem"><p> - Make Replay Flight run in realtime again. It had been set to - run at 10x speed by mistake. - </p></li></ul></div><p> - </p><p> - AltosDroid New Features - </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p> - Add offline map support using mapping code from AltosUI. - </p></li><li class="listitem"><p> - Support TeleDongle (and TeleBT via USB) on devices - supporting USB On-The-Go. - </p></li><li class="listitem"><p> - Display additional TeleMega pyro channel status in Pad tab. - </p></li><li class="listitem"><p> - Switch between metric and imperial units. - </p></li><li class="listitem"><p> - Monitor TeleBT battery voltage. - </p></li><li class="listitem"><p> - Track multiple devices at the same time, selecting between - them with a menu or using the map. - </p></li><li class="listitem"><p> - Add hybrid, satellite and terrain map types. - </p></li></ul></div><p> - </p><p> - AltosDroid Fixes - </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p> - Use standard Android display conventions so that a menu - button is available in the application title bar. - </p></li><li class="listitem"><p> - Adjust layout to work on large and small screens; shrinking - the go/no-go lights in smaller environments to try and make - everything visible. - </p></li><li class="listitem"><p> - Make voice announcements depend on current tab. - </p></li><li class="listitem"><p> - Compute adjustment to current travel direction while in - motion towards rocket. - </p></li></ul></div><p> - </p></div></body></html> +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Release Notes for Version 1.6.1</title><link rel="stylesheet" type="text/css" href="am.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.78.1" /></head><body><div xml:lang="en" class="article" lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="idm45281923841024"></a>Release Notes for Version 1.6.1</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Bdale</span> <span class="surname">Garbee</span></h3><code class="email"><<a class="email" href="mailto:bdale@gag.com">bdale@gag.com</a>></code></div></div><div><div class="author"><h3 class="author"><span class="firstname">Keith</span> <span class="surname">Packard</span></h3><code class="email"><<a class="email" href="mailto:keithp@keithp.com">keithp@keithp.com</a>></code></div></div><div><p class="copyright">Copyright © 2015 Bdale Garbee and Keith Packard</p></div><div><div class="legalnotice"><a id="idm45281923968816"></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><hr /></div><p>Version 1.6.1 includes support for our updated TeleBT v3.0 +product and bug fixes in in the flight software for all our boards +and ground station interfaces.</p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_altos"></a>1. AltOS</h2></div></div></div><p>AltOS New Features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Add support for TeleBT v3.0 boards. +</li><li class="listitem"> +Add support for uncompressed APRS data, providing support +for older APRS receivers. Uncompressed APRS data is less +precise, takes more bandwidth and doesn’t have integrated +altitude data. +</li></ul></div><p>AltOS Fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Make TeleDongle and TeleBT more tolerant of data rate +variations from transmitting devices. +</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_altosui_and_telegps_applications"></a>2. AltosUI and TeleGPS Applications</h2></div></div></div><p>AltosUI and TeleGPS New Features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Add map to Monitor Idle display. It’s nice to be able to +verify that maps are working, instead of needing to use +Monitor Flight. +</li></ul></div><p>AltosUI and TeleGPS Fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Fix frequency configuration to round values instead of +truncate them, avoiding a common 1kHz error in the setting. +</li><li class="listitem"> +Turn the Windows stub into a more useful program that can +launch the application with parameters so that file manager +icons work more reliably. +</li><li class="listitem"> +Force KML export to use a C locale so that numbers are +formatted with <span class="emphasis"><em>.</em></span> instead of <span class="emphasis"><em>,</em></span> for a decimal separator in +non-US locales. +</li><li class="listitem"> +Preload map tiles based on distance rather than number of +tiles; this means you get the same resolution covering the +entire area, rather than having high resolution near the +center and low resolution further away. +</li><li class="listitem"> +Allow configuration of frequency and callsign in Monitor +Idle mode. +</li><li class="listitem"> +Fix layout weirdness when resizing windows on +Windows. Windows shouldn’t have giant blank spaces around +the useful content anymore. +</li><li class="listitem"> +Fix layout weirdness when resizing windows on +Windows. Windows shouldn’t have giant blank spaces around +the useful content anymore. +</li><li class="listitem"> +Use a longer filter for descent speed values. This should +provide something more useful on the display, although it +will take longer to respond to changes now. +</li><li class="listitem"> +Make Replay Flight run in realtime again. It had been set to +run at 10x speed by mistake. +</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_altosdroid"></a>3. AltosDroid</h2></div></div></div><p>AltosDroid New Features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Add offline map support using mapping code from AltosUI. +</li><li class="listitem"> +Support TeleDongle (and TeleBT via USB) on devices +supporting USB On-The-Go. +</li><li class="listitem"> +Display additional TeleMega pyro channel status in Pad tab. +</li><li class="listitem"> +Switch between metric and imperial units. +</li><li class="listitem"> +Monitor TeleBT battery voltage. +</li><li class="listitem"> +Track multiple devices at the same time, selecting between +them with a menu or using the map. +</li><li class="listitem"> +Add hybrid, satellite and terrain map types. +</li></ul></div><p>AltosDroid Fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Use standard Android display conventions so that a menu +button is available in the application title bar. +</li><li class="listitem"> +Adjust layout to work on large and small screens; shrinking +the go/no-go lights in smaller environments to try and make +everything visible. +</li><li class="listitem"> +Make voice announcements depend on current tab. +</li><li class="listitem"> +Compute adjustment to current travel direction while in +motion towards rocket. +</li></ul></div></div></div></body></html>
\ No newline at end of file diff --git a/AltOS/doc/release-notes-1.6.1.pdf b/AltOS/doc/release-notes-1.6.1.pdf Binary files differnew file mode 100644 index 0000000..185a7c4 --- /dev/null +++ b/AltOS/doc/release-notes-1.6.1.pdf diff --git a/AltOS/doc/release-notes-1.6.2.html b/AltOS/doc/release-notes-1.6.2.html new file mode 100644 index 0000000..097b741 --- /dev/null +++ b/AltOS/doc/release-notes-1.6.2.html @@ -0,0 +1,35 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Release Notes for Version 1.6.2</title><link rel="stylesheet" type="text/css" href="am.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.78.1" /></head><body><div xml:lang="en" class="article" lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="idm45438886235792"></a>Release Notes for Version 1.6.2</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Bdale</span> <span class="surname">Garbee</span></h3><code class="email"><<a class="email" href="mailto:bdale@gag.com">bdale@gag.com</a>></code></div></div><div><div class="author"><h3 class="author"><span class="firstname">Keith</span> <span class="surname">Packard</span></h3><code class="email"><<a class="email" href="mailto:keithp@keithp.com">keithp@keithp.com</a>></code></div></div><div><p class="copyright">Copyright © 2016 Bdale Garbee and Keith Packard</p></div><div><div class="legalnotice"><a id="idm45438885472624"></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><hr /></div><p>Version 1.6.2 includes support for our updated TeleMega v2.0 +product and bug fixes in in the flight software for all our boards +and ground station interfaces.</p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_altos"></a>1. AltOS</h2></div></div></div><p>AltOS New Features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Add support for TeleMega v2.0 boards. +</li><li class="listitem"> +Add PWM servo driver. There’s no higher level code using +this yet, but the driver allows testing of the TeleMega v2.0 +servo output connector. +</li></ul></div><p>AltOS Fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Slow down telemetry packets to allow receiver to keep +up. +</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_altosui_and_telegps_applications"></a>2. AltosUI and TeleGPS Applications</h2></div></div></div><p>AltosUI and TeleGPS Fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Fix post-flight orientation computation when processing +TeleMega and EasyMega eeprom data files. +</li><li class="listitem"> +Capture complete eeprom data even when there are invalid +entries in the data. This keeps reading eeprom contents and +writing the associated .eeprom file when an error is detected. +</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_documentation"></a>3. Documentation</h2></div></div></div><p>We spent a bunch of time trying to improve our documentation</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +HTML versions now have a table of contents on the left side. +</li><li class="listitem"> +EasyMini now has its own shorter manual. +</li><li class="listitem"> +Provide links between sections in each document. +</li><li class="listitem"> +Lots of minor rewriting and restructuring to avoid +duplication of information +</li></ul></div></div></div></body></html>
\ No newline at end of file diff --git a/AltOS/doc/release-notes-1.6.2.pdf b/AltOS/doc/release-notes-1.6.2.pdf Binary files differnew file mode 100644 index 0000000..e472eb3 --- /dev/null +++ b/AltOS/doc/release-notes-1.6.2.pdf diff --git a/AltOS/doc/release-notes-1.6.html b/AltOS/doc/release-notes-1.6.html index ca58446..e93cde9 100644 --- a/AltOS/doc/release-notes-1.6.html +++ b/AltOS/doc/release-notes-1.6.html @@ -1,83 +1,76 @@ -<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title></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="article"><div class="titlepage"><hr></div><p> - Version 1.6 includes support for our updated TeleDongle v3.0 - product and bug fixes in in the flight software for all our boards - and ground station interfaces. - </p><p> - AltOS New Features - </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p> - Add support for TeleDongle v3.0 boards. - </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> - Don't beep out the continuity twice by accident in idle mode. - If the battery voltage report takes longer than the initialiation - sequence, the igniter continuity would get reported twice. - </p></li><li class="listitem"><p> - Record all 32 bits of gyro calibration data in TeleMega and - EasyMega log files. This fixes computation of the gyro rates - in AltosUI. - </p></li><li class="listitem"><p> - Change TeleDongle LED usage. Green LED flashes when valid - packet is received. Red LED flashes when invalid packet is - received. - </p></li><li class="listitem"><p> - Replace LPC11U14 SPI driver with non-interrupt version. The - interrupt code would occasionally wedge on long transfers - if interrupts were blocked for too long. This affects all - released TeleGPS products; if you have a TeleGPS device, - you'll want to reflash the firmware. - </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> - Compute tilt angle from TeleMega and EasyMega log - files. This duplicates the quaternion-based angle tracking - code from the flight firmware inside the ground station - software so that post-flight analysis can include evaluation - of the tilt angle. - </p></li><li class="listitem"><p> - Shows the tool button window when starting with a data file - specified. This means that opening a data file from the file - manager will now bring up the main window to let you operate - the whole 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> - Show the 'Connecting' dialog when using Monitor Idle. Lets - you cancel the Monitor Idle startup when connecting over the - radio link. - </p></li><li class="listitem"><p> - Make 'Monitor Idle' work for TeleGPS devices when connected - over USB. It's nice for testing without needing to broadcast - over the radio. - </p></li><li class="listitem"><p> - Use different Windows API to discover USB devices. This - works better on my Windows 7 box, and will be used if the - older API fails to provide the necessary information. - </p></li><li class="listitem"><p> - Look in more places in the registry to try and identify the - installed Java version on Windows. If you install the - default 32-bit version of Windows on a 64-bit OS, the Java - registry information is hiding \SOFTWARE\Wow6432Node for - some reason. - </p></li><li class="listitem"><p> - Fix file association on Windows by searching for the - javaw.exe program instead of assuming it is in - %SYSTEMROOT%. This makes double-clicking on Altus Metrum - data files in the file manager work correctly. - </p></li><li class="listitem"><p> - When replaying a file, put 'done' in the Age field when we - reach the end of the file, instead of continuing to count forever. - </p></li><li class="listitem"><p> - In the Scan Channels code, wait for five seconds if we see - any packet. This is needed because AltOS now sends the - callsign, serial number and flight number only once every - five seconds these days. - </p></li><li class="listitem"><p> - In the Scan Channels code, reset pending flight state - information each time we change channels. This avoids having - flight computers appear on multiple frequencies by accident. - </p></li></ul></div><p> - </p></div></body></html> +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Release Notes for Version 1.6</title><link rel="stylesheet" type="text/css" href="am.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.78.1" /></head><body><div xml:lang="en" class="article" lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="idm45110209480096"></a>Release Notes for Version 1.6</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Bdale</span> <span class="surname">Garbee</span></h3><code class="email"><<a class="email" href="mailto:bdale@gag.com">bdale@gag.com</a>></code></div></div><div><div class="author"><h3 class="author"><span class="firstname">Keith</span> <span class="surname">Packard</span></h3><code class="email"><<a class="email" href="mailto:keithp@keithp.com">keithp@keithp.com</a>></code></div></div><div><p class="copyright">Copyright © 2015 Bdale Garbee and Keith Packard</p></div><div><div class="legalnotice"><a id="idm45110208745040"></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><hr /></div><p>Version 1.6 includes support for our updated TeleDongle v3.0 +product and bug fixes in in the flight software for all our boards +and ground station interfaces.</p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_altos"></a>1. AltOS</h2></div></div></div><p>AltOS New Features</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Add support for TeleDongle v3.0 boards. +</li></ul></div><p>AltOS Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Don’t beep out the continuity twice by accident in idle mode. +If the battery voltage report takes longer than the initialiation +sequence, the igniter continuity would get reported twice. +</li><li class="listitem"> +Record all 32 bits of gyro calibration data in TeleMega and +EasyMega log files. This fixes computation of the gyro rates +in AltosUI. +</li><li class="listitem"> +Change TeleDongle LED usage. Green LED flashes when valid +packet is received. Red LED flashes when invalid packet is +received. +</li><li class="listitem"> +Replace LPC11U14 SPI driver with non-interrupt version. The +interrupt code would occasionally wedge on long transfers +if interrupts were blocked for too long. This affects all +released TeleGPS products; if you have a TeleGPS device, +you’ll want to reflash the firmware. +</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_altosui_and_telegps_applications"></a>2. AltosUI and TeleGPS Applications</h2></div></div></div><p>AltosUI and TeleGPS New Features</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Compute tilt angle from TeleMega and EasyMega log +files. This duplicates the quaternion-based angle tracking +code from the flight firmware inside the ground station +software so that post-flight analysis can include evaluation +of the tilt angle. +</li><li class="listitem"> +Shows the tool button window when starting with a data file +specified. This means that opening a data file from the file +manager will now bring up the main window to let you operate +the whole application. +</li></ul></div><p>AltosUI Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Show the <span class="emphasis"><em>Connecting</em></span> dialog when using Monitor Idle. Lets +you cancel the Monitor Idle startup when connecting over the +radio link. +</li><li class="listitem"> +Make <span class="emphasis"><em>Monitor Idle</em></span> work for TeleGPS devices when connected +over USB. It’s nice for testing without needing to broadcast +over the radio. +</li><li class="listitem"> +Use different Windows API to discover USB devices. This +works better on my Windows 7 box, and will be used if the +older API fails to provide the necessary information. +</li><li class="listitem"> +Look in more places in the registry to try and identify the +installed Java version on Windows. If you install the +default 32-bit version of Windows on a 64-bit OS, the Java +registry information is hiding \SOFTWARE\Wow6432Node for +some reason. +</li><li class="listitem"> +Fix file association on Windows by searching for the +javaw.exe program instead of assuming it is in +%SYSTEMROOT%. This makes double-clicking on Altus Metrum +data files in the file manager work correctly. +</li><li class="listitem"> +When replaying a file, put <span class="emphasis"><em>done</em></span> in the Age field when we +reach the end of the file, instead of continuing to count forever. +</li><li class="listitem"> +In the Scan Channels code, wait for five seconds if we see +any packet. This is needed because AltOS now sends the +callsign, serial number and flight number only once every +five seconds these days. +</li><li class="listitem"> +In the Scan Channels code, reset pending flight state +information each time we change channels. This avoids having +flight computers appear on multiple frequencies by accident. +</li></ul></div></div></div></body></html>
\ No newline at end of file diff --git a/AltOS/doc/release-notes-1.6.pdf b/AltOS/doc/release-notes-1.6.pdf Binary files differnew file mode 100644 index 0000000..e4c0aee --- /dev/null +++ b/AltOS/doc/release-notes-1.6.pdf diff --git a/AltOS/doc/telegps-configure.png b/AltOS/doc/telegps-configure.png Binary files differnew file mode 100644 index 0000000..56cb203 --- /dev/null +++ b/AltOS/doc/telegps-configure.png diff --git a/AltOS/doc/telegps-graph-configure.png b/AltOS/doc/telegps-graph-configure.png Binary files differnew file mode 100644 index 0000000..67eb5d9 --- /dev/null +++ b/AltOS/doc/telegps-graph-configure.png diff --git a/AltOS/doc/telegps-graph-graph.png b/AltOS/doc/telegps-graph-graph.png Binary files differnew file mode 100644 index 0000000..443ada0 --- /dev/null +++ b/AltOS/doc/telegps-graph-graph.png diff --git a/AltOS/doc/telegps-graph-map.png b/AltOS/doc/telegps-graph-map.png Binary files differnew file mode 100644 index 0000000..dddea22 --- /dev/null +++ b/AltOS/doc/telegps-graph-map.png diff --git a/AltOS/doc/telegps-graph-stats.png b/AltOS/doc/telegps-graph-stats.png Binary files differnew file mode 100644 index 0000000..d181ce5 --- /dev/null +++ b/AltOS/doc/telegps-graph-stats.png diff --git a/AltOS/doc/telegps-info.png b/AltOS/doc/telegps-info.png Binary files differnew file mode 100644 index 0000000..cc279b8 --- /dev/null +++ b/AltOS/doc/telegps-info.png diff --git a/AltOS/doc/telegps-location.png b/AltOS/doc/telegps-location.png Binary files differnew file mode 100644 index 0000000..e32b14c --- /dev/null +++ b/AltOS/doc/telegps-location.png diff --git a/AltOS/doc/telegps-map.png b/AltOS/doc/telegps-map.png Binary files differnew file mode 100644 index 0000000..f5557de --- /dev/null +++ b/AltOS/doc/telegps-map.png diff --git a/AltOS/doc/telegps-oneline.svg b/AltOS/doc/telegps-oneline.svg new file mode 100644 index 0000000..2149789 --- /dev/null +++ b/AltOS/doc/telegps-oneline.svg @@ -0,0 +1,332 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<!-- Created with Inkscape (http://www.inkscape.org/) --> + +<svg + xmlns:dc="http://purl.org/dc/elements/1.1/" + xmlns:cc="http://creativecommons.org/ns#" + xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" + xmlns:svg="http://www.w3.org/2000/svg" + xmlns="http://www.w3.org/2000/svg" + xmlns:xlink="http://www.w3.org/1999/xlink" + xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd" + xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape" + width="444" + height="98" + id="svg2" + version="1.1" + inkscape:version="0.91 r13725" + sodipodi:docname="telegps-oneline.svg"> + <defs + id="defs4"> + <radialGradient + inkscape:collect="always" + xlink:href="#linearGradient3169" + id="radialGradient3175" + cx="951.68713" + cy="2305.2668" + fx="951.68713" + fy="2305.2668" + r="951.68701" + gradientTransform="matrix(1,0,0,1.2664529,0,-321.14689)" + gradientUnits="userSpaceOnUse" /> + <linearGradient + id="linearGradient3169"> + <stop + style="stop-color:#ff8a00;stop-opacity:1;" + offset="0" + id="stop3171" /> + <stop + id="stop3445" + offset="0.71698111" + style="stop-color:#c24573;stop-opacity:0.98039216;" /> + <stop + style="stop-color:#8500e7;stop-opacity:0.96078432;" + offset="1" + id="stop3173" /> + </linearGradient> + <radialGradient + inkscape:collect="always" + xlink:href="#linearGradient3165" + id="radialGradient3171" + cx="951.68713" + cy="1205.2668" + fx="951.68713" + fy="1205.2668" + r="951.68701" + gradientTransform="matrix(1,0,0,1.2664529,0,-321.14689)" + gradientUnits="userSpaceOnUse" /> + <linearGradient + id="linearGradient3165"> + <stop + style="stop-color:#000000;stop-opacity:1;" + offset="0" + id="stop3167" /> + <stop + style="stop-color:#000000;stop-opacity:0;" + offset="1" + id="stop3169" /> + </linearGradient> + <radialGradient + inkscape:collect="always" + xlink:href="#linearGradient3169" + id="radialGradient2838" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1,0,0,1.2664529,0,-321.14689)" + cx="951.68713" + cy="2305.2668" + fx="951.68713" + fy="2305.2668" + r="951.68701" /> + <linearGradient + id="linearGradient3181"> + <stop + style="stop-color:#ff8a00;stop-opacity:1;" + offset="0" + id="stop3183" /> + <stop + id="stop3185" + offset="0.71698111" + style="stop-color:#c24573;stop-opacity:0.98039216;" /> + <stop + style="stop-color:#8500e7;stop-opacity:0.96078432;" + offset="1" + id="stop3187" /> + </linearGradient> + <radialGradient + inkscape:collect="always" + xlink:href="#linearGradient3165" + id="radialGradient2840" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1,0,0,1.2664529,0,-321.14689)" + cx="951.68713" + cy="1205.2668" + fx="951.68713" + fy="1205.2668" + r="951.68701" /> + <linearGradient + id="linearGradient3190"> + <stop + style="stop-color:#000000;stop-opacity:1;" + offset="0" + id="stop3192" /> + <stop + style="stop-color:#000000;stop-opacity:0;" + offset="1" + id="stop3194" /> + </linearGradient> + <radialGradient + inkscape:collect="always" + xlink:href="#linearGradient3169" + id="radialGradient2830" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1,0,0,1.2664529,0,-321.14689)" + cx="951.68713" + cy="2305.2668" + fx="951.68713" + fy="2305.2668" + r="951.68701" /> + <linearGradient + id="linearGradient3197"> + <stop + style="stop-color:#ff8a00;stop-opacity:1;" + offset="0" + id="stop3199" /> + <stop + id="stop3201" + offset="0.71698111" + style="stop-color:#c24573;stop-opacity:0.98039216;" /> + <stop + style="stop-color:#8500e7;stop-opacity:0.96078432;" + offset="1" + id="stop3203" /> + </linearGradient> + <radialGradient + inkscape:collect="always" + xlink:href="#linearGradient3165" + id="radialGradient2832" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1,0,0,1.2664529,0,-321.14689)" + cx="951.68713" + cy="1205.2668" + fx="951.68713" + fy="1205.2668" + r="951.68701" /> + <linearGradient + id="linearGradient3206"> + <stop + style="stop-color:#000000;stop-opacity:1;" + offset="0" + id="stop3208" /> + <stop + style="stop-color:#000000;stop-opacity:0;" + offset="1" + id="stop3210" /> + </linearGradient> + <radialGradient + inkscape:collect="always" + xlink:href="#linearGradient3169" + id="radialGradient2834" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1,0,0,1.2664529,0,-321.14689)" + cx="951.68713" + cy="2305.2668" + fx="951.68713" + fy="2305.2668" + r="951.68701" /> + <linearGradient + id="linearGradient3213"> + <stop + style="stop-color:#ff8a00;stop-opacity:1;" + offset="0" + id="stop3215" /> + <stop + id="stop3217" + offset="0.71698111" + style="stop-color:#c24573;stop-opacity:0.98039216;" /> + <stop + style="stop-color:#8500e7;stop-opacity:0.96078432;" + offset="1" + id="stop3219" /> + </linearGradient> + <radialGradient + inkscape:collect="always" + xlink:href="#linearGradient3165" + id="radialGradient2836" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1,0,0,1.2664529,0,-321.14689)" + cx="951.68713" + cy="1205.2668" + fx="951.68713" + fy="1205.2668" + r="951.68701" /> + <linearGradient + id="linearGradient3222"> + <stop + style="stop-color:#000000;stop-opacity:1;" + offset="0" + id="stop3224" /> + <stop + style="stop-color:#000000;stop-opacity:0;" + offset="1" + id="stop3226" /> + </linearGradient> + <radialGradient + r="951.68701" + fy="2305.2668" + fx="951.68713" + cy="2305.2668" + cx="951.68713" + gradientTransform="matrix(1,0,0,1.2664529,0,-321.14689)" + gradientUnits="userSpaceOnUse" + id="radialGradient3232" + xlink:href="#linearGradient3169" + inkscape:collect="always" /> + <radialGradient + r="951.68701" + fy="1205.2668" + fx="951.68713" + cy="1205.2668" + cx="951.68713" + gradientTransform="matrix(1,0,0,1.2664529,0,-321.14689)" + gradientUnits="userSpaceOnUse" + id="radialGradient3234" + xlink:href="#linearGradient3165" + inkscape:collect="always" /> + <radialGradient + inkscape:collect="always" + xlink:href="#linearGradient3169" + id="radialGradient4101" + cx="194.54575" + cy="361.16367" + fx="194.54575" + fy="361.16367" + r="70.597672" + gradientTransform="matrix(0.39116682,0,0,0.37516256,264.74942,305.15926)" + gradientUnits="userSpaceOnUse" /> + </defs> + <sodipodi:namedview + id="base" + pagecolor="#ffffff" + bordercolor="#666666" + borderopacity="1.0" + inkscape:pageopacity="0.0" + inkscape:pageshadow="2" + inkscape:zoom="2.8" + inkscape:cx="199.46382" + inkscape:cy="-0.91832278" + inkscape:document-units="px" + inkscape:current-layer="layer1" + showgrid="false" + fit-margin-top="0" + fit-margin-left="0" + fit-margin-right="0" + fit-margin-bottom="0" + inkscape:window-width="2060" + inkscape:window-height="1038" + inkscape:window-x="128" + inkscape:window-y="382" + inkscape:window-maximized="0" /> + <metadata + id="metadata7"> + <rdf:RDF> + <cc:Work + rdf:about=""> + <dc:format>image/svg+xml</dc:format> + <dc:type + rdf:resource="http://purl.org/dc/dcmitype/StillImage" /> + <dc:title></dc:title> + </cc:Work> + </rdf:RDF> + </metadata> + <g + inkscape:label="Layer 1" + inkscape:groupmode="layer" + id="layer1" + transform="translate(-261.09094,-391.54617)"> + <path + style="fill:url(#radialGradient4101);fill-opacity:1" + d="m 313.2338,458.43158 0.74799,-0.66263 15.28371,-14.26539 8.11342,8.62622 -15.92828,15.01016 z m 14.17973,0.52672 -5.51012,-6.01784 -6.00005,5.63616 5.67488,5.96037 z m 7.4271,-6.87951 -5.66258,-6.0785 -5.84869,5.64101 5.55447,6.01448 z m 16.92051,1.26751 -2.22702,-2.35058 -1.08325,0.7265 c -1.96176,1.31568 -4.1533,1.8588 -5.30166,1.31387 -0.35512,-0.16852 -4.38371,-4.24634 -6.4391,-6.49926 -2.47128,-2.70877 -6.95192,-7.30832 -7.0731,-8.42455 l -0.0997,-0.91841 -2.61387,-1.17418 -2.61387,-1.17418 -0.0486,-0.99688 c -0.0951,-1.95235 1.02366,-4.56153 2.77984,-6.48307 2.5501,-2.79022 5.56698,-4.22936 8.37374,-3.99451 l 0.97627,0.0817 0.91575,2.85892 0.91576,2.85892 0.80353,0.0846 c 0.44195,0.0465 0.89673,0.14357 1.01064,0.21564 0.1139,0.0721 4.37229,4.5213 6.5073,6.82994 2.21944,2.39996 6.39675,6.92997 6.55055,7.29806 0.53391,1.27783 -0.22109,3.65537 -1.74006,5.47948 -0.36354,0.43658 -0.66009,0.84091 -0.659,0.89852 10e-4,0.0576 0.9568,1.12825 2.12378,2.37921 1.16697,1.25095 2.12177,2.358 2.12177,2.46012 0,0.26127 -0.35803,0.67512 -0.68056,0.78665 -0.19689,0.0681 -0.88798,-0.55589 -2.49916,-2.25648 z m -5.43503,-2.55191 c 0.37628,-0.19196 0.96494,-0.53484 1.30813,-0.76195 l 0.62398,-0.41293 -0.66117,-0.67369 c -0.67097,-0.68367 -0.81984,-1.17245 -0.46513,-1.52716 0.38493,-0.38494 0.9136,-0.20884 1.54209,0.51365 l 0.61736,0.7097 0.56187,-0.66886 c 0.66948,-0.79697 1.32734,-2.14185 1.32608,-2.71094 -0.004,-1.83194 -2.74447,-1.05143 -5.2295,1.48943 -1.66747,1.70495 -2.47525,3.74553 -1.66865,4.21533 0.46647,0.2717 1.31435,0.20014 2.04494,-0.17258 z m -14.68075,-17.36398 c 0.87596,-1.05862 2.85317,-2.73572 3.96513,-3.36327 0.66454,-0.37504 0.86538,-0.57179 0.79857,-0.78228 -0.0491,-0.15467 -0.4136,-1.19935 -0.81002,-2.32152 l -0.72076,-2.04031 -0.6284,0.0502 c -1.61556,0.12898 -3.54486,1.11891 -5.2022,2.66926 -1.57748,1.47566 -3.04496,3.99315 -3.08636,5.29473 l -0.0181,0.56872 2.11562,0.96695 2.11563,0.96695 0.40259,-0.60243 c 0.22142,-0.33133 0.70215,-0.96447 1.06829,-1.40696 z m 12.87345,-4.09635 15.86492,-15.16531 c 2.77649,3.01655 5.68624,6.11689 8.08087,8.70358 l -15.85433,14.95877 z m 13.97892,0.39936 -5.57785,-6.0158 -5.98287,5.61632 5.73242,5.92485 z m 7.30703,-6.86817 -5.51608,-6.02447 -5.99586,5.63174 5.68363,5.96272 z" + id="path3063" + inkscape:connector-curvature="0" + sodipodi:nodetypes="ccccccccccccccccscssascccssscccscasscsssssccssscssssscssscssccccsccccccccccccccccc" /> + <g + id="g4484" + style="fill:#78079a;fill-opacity:1"> + <path + d="m 397.31307,420.68962 11.6021,0 c 2.13722,0 3.66381,-0.99229 3.66381,-3.12952 0,-2.13723 -1.52659,-3.12951 -3.66381,-3.12951 l -29.92119,0 c -2.13723,0 -3.66382,0.99228 -3.66382,3.12951 0,2.13723 1.52659,3.12952 3.66382,3.12952 l 11.60209,0 0,42.51556 c 0,2.36622 1.06862,3.96914 3.3585,3.96914 2.28989,0 3.3585,-1.60292 3.3585,-3.96914 l 0,-42.51556 z" + id="path4214" + inkscape:connector-curvature="0" + style="font-style:normal;font-variant:normal;font-weight:500;font-stretch:normal;font-size:medium;line-height:125%;font-family:'ITC Benguiat Gothic Std';-inkscape-font-specification:'ITC Benguiat Gothic Std Medium';text-align:start;letter-spacing:0px;word-spacing:0px;writing-mode:lr-tb;text-anchor:start;fill:#78079a;fill-opacity:1;stroke:none" /> + <path + d="m 416.63996,442.82519 c 0.99228,-4.88509 4.50344,-9.31221 11.83108,-9.31221 6.18269,0 10.0755,3.96914 10.38082,9.31221 l -22.2119,0 z m 25.18875,5.19041 c 3.66382,0 3.74015,-0.83963 3.74015,-4.04547 0,-9.61752 -7.55662,-16.25819 -17.02149,-16.25819 -11.37311,0 -19.38771,7.78561 -19.38771,19.23505 0,13.434 8.47258,19.99834 18.54808,19.99834 l 14.65528,0 c 2.0609,0 3.43483,-0.91596 3.43483,-2.90052 0,-1.98457 -1.37393,-2.90053 -3.43483,-2.90053 l -14.50262,0 c -6.25902,0 -12.06007,-4.27445 -11.52576,-13.12868 l 25.49407,0 z" + id="path4216" + inkscape:connector-curvature="0" + style="font-style:normal;font-variant:normal;font-weight:500;font-stretch:normal;font-size:medium;line-height:125%;font-family:'ITC Benguiat Gothic Std';-inkscape-font-specification:'ITC Benguiat Gothic Std Medium';text-align:start;letter-spacing:0px;word-spacing:0px;writing-mode:lr-tb;text-anchor:start;fill:#78079a;fill-opacity:1;stroke:none" /> + <path + d="m 460.34936,418.17074 c 0,-2.28989 -0.83962,-3.96913 -3.3585,-3.96913 -2.51888,0 -3.3585,1.67924 -3.3585,3.96913 l 0,45.03444 c 0,2.36622 1.06861,3.96914 3.3585,3.96914 2.28989,0 3.3585,-1.60292 3.3585,-3.96914 l 0,-45.03444 z" + id="path4218" + inkscape:connector-curvature="0" + style="font-style:normal;font-variant:normal;font-weight:500;font-stretch:normal;font-size:medium;line-height:125%;font-family:'ITC Benguiat Gothic Std';-inkscape-font-specification:'ITC Benguiat Gothic Std Medium';text-align:start;letter-spacing:0px;word-spacing:0px;writing-mode:lr-tb;text-anchor:start;fill:#78079a;fill-opacity:1;stroke:none" /> + <path + d="m 476.12335,442.82519 c 0.99228,-4.88509 4.50344,-9.31221 11.83108,-9.31221 6.18269,0 10.0755,3.96914 10.38082,9.31221 l -22.2119,0 z m 25.18875,5.19041 c 3.66382,0 3.74015,-0.83963 3.74015,-4.04547 0,-9.61752 -7.55663,-16.25819 -17.02149,-16.25819 -11.37311,0 -19.38771,7.78561 -19.38771,19.23505 0,13.434 8.47258,19.99834 18.54808,19.99834 l 14.65528,0 c 2.0609,0 3.43483,-0.91596 3.43483,-2.90052 0,-1.98457 -1.37393,-2.90053 -3.43483,-2.90053 l -14.50262,0 c -6.25902,0 -12.06007,-4.27445 -11.52576,-13.12868 l 25.49407,0 z" + id="path4220" + inkscape:connector-curvature="0" + style="font-style:normal;font-variant:normal;font-weight:500;font-stretch:normal;font-size:medium;line-height:125%;font-family:'ITC Benguiat Gothic Std';-inkscape-font-specification:'ITC Benguiat Gothic Std Medium';text-align:start;letter-spacing:0px;word-spacing:0px;writing-mode:lr-tb;text-anchor:start;fill:#78079a;fill-opacity:1;stroke:none" /> + <path + d="m 547.99836,461.14428 c -15.11326,0 -29.84486,-8.09093 -29.84486,-25.11242 0,-10.53348 5.87738,-15.34224 13.89198,-15.34224 l 17.40314,0 c 2.13723,0 3.66382,-0.99229 3.66382,-3.12952 0,-2.13723 -1.52659,-3.12951 -3.66382,-3.12951 l -18.70074,0 c -12.44172,0 -20.07467,8.93056 -20.07467,21.21962 0,20.9143 17.09781,31.75309 35.95122,31.75309 5.19041,0 8.09093,-0.45797 8.09093,-4.88509 l 0,-29.84485 c 0,-4.42712 -1.83191,-4.96142 -5.64839,-4.96142 l -12.89969,0 c -2.13723,0 -3.66382,0.99228 -3.66382,3.12951 0,2.13723 1.52659,3.12951 3.66382,3.12951 l 11.83108,0 0,27.17332 z" + id="path4222" + inkscape:connector-curvature="0" + style="font-style:normal;font-variant:normal;font-weight:500;font-stretch:normal;font-size:medium;line-height:125%;font-family:'ITC Benguiat Gothic Std';-inkscape-font-specification:'ITC Benguiat Gothic Std Medium';text-align:start;letter-spacing:0px;word-spacing:0px;writing-mode:lr-tb;text-anchor:start;fill:#78079a;fill-opacity:1;stroke:none" /> + <path + d="m 571.73446,443.8938 c 9.38854,-3.3585 29.53954,-7.02232 29.53954,-20.37999 0,-6.10637 -4.88509,-9.08322 -10.91513,-9.08322 l -22.2119,0 c -2.36621,0 -3.12951,1.52659 -3.12951,3.66382 l 0,45.11077 c 0,2.36622 1.06862,3.96914 3.3585,3.96914 2.28989,0 3.3585,-1.60292 3.3585,-3.96914 l 0,-19.31138 z m 17.40314,-23.20418 c 2.67154,0 4.65611,0.91595 4.65611,3.89281 0,6.86966 -14.34996,9.23587 -22.05925,12.44171 l 0,-16.33452 17.40314,0 z" + id="path4224" + inkscape:connector-curvature="0" + style="font-style:normal;font-variant:normal;font-weight:500;font-stretch:normal;font-size:medium;line-height:125%;font-family:'ITC Benguiat Gothic Std';-inkscape-font-specification:'ITC Benguiat Gothic Std Medium';text-align:start;letter-spacing:0px;word-spacing:0px;writing-mode:lr-tb;text-anchor:start;fill:#78079a;fill-opacity:1;stroke:none" /> + <path + d="m 615.90185,414.43059 c -6.1827,0 -11.60208,3.51116 -11.60208,10.45715 0,18.70074 34.04297,4.04547 34.04297,22.59355 0,8.16726 -4.80877,13.20502 -15.80021,13.20502 l -14.80793,0 c -2.13722,0 -3.66382,0.99228 -3.66382,3.12951 0,2.13723 1.5266,3.12951 3.66382,3.12951 l 16.79248,0 c 12.97606,0 20.99064,-8.54891 20.99064,-19.6167 0,-24.65445 -34.04298,-12.89969 -34.04298,-22.51722 0,-3.96913 4.12181,-4.12179 6.56433,-4.12179 l 17.09782,0 c 2.13726,0 3.66383,-0.99229 3.66383,-3.12952 0,-2.13723 -1.52657,-3.12951 -3.66383,-3.12951 l -19.23504,0 z" + id="path4226" + inkscape:connector-curvature="0" + style="font-style:normal;font-variant:normal;font-weight:500;font-stretch:normal;font-size:medium;line-height:125%;font-family:'ITC Benguiat Gothic Std';-inkscape-font-specification:'ITC Benguiat Gothic Std Medium';text-align:start;letter-spacing:0px;word-spacing:0px;writing-mode:lr-tb;text-anchor:start;fill:#78079a;fill-opacity:1;stroke:none" /> + </g> + </g> +</svg> diff --git a/AltOS/doc/telegps-preferences.png b/AltOS/doc/telegps-preferences.png Binary files differnew file mode 100644 index 0000000..ad14fd8 --- /dev/null +++ b/AltOS/doc/telegps-preferences.png diff --git a/AltOS/doc/telegps-revhistory.html b/AltOS/doc/telegps-revhistory.html new file mode 100644 index 0000000..d76e517 --- /dev/null +++ b/AltOS/doc/telegps-revhistory.html @@ -0,0 +1,14 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Revision History</title><link rel="stylesheet" type="text/css" href="am.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.78.1" /></head><body><div class="revhistory"><table style="border-style:solid; width:100%;" summary="Revision History"><tr><th align="left" valign="top" colspan="2"><strong>Revision History</strong></th></tr><tr><td align="left">Revision 1.6.1</td><td align="left">15 July 2015</td></tr><tr><td align="left" colspan="2"> + Minor release adding TeleBT v3.0 support. + </td></tr><tr><td align="left">Revision 1.6</td><td align="left">8 January 2015</td></tr><tr><td align="left" colspan="2"> + Major release adding TeleDongle v3.0 support. + </td></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.2</td><td align="left">17 August 2014</td></tr><tr><td align="left" colspan="2"> + Minor release fixing some Windows installation bugs. + </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"> + Initial version + </td></tr></table></div></body></html> diff --git a/AltOS/doc/telegps-scan.png b/AltOS/doc/telegps-scan.png Binary files differnew file mode 100644 index 0000000..9b19e68 --- /dev/null +++ b/AltOS/doc/telegps-scan.png diff --git a/AltOS/doc/telegps-status.png b/AltOS/doc/telegps-status.png Binary files differnew file mode 100644 index 0000000..dc338f0 --- /dev/null +++ b/AltOS/doc/telegps-status.png diff --git a/AltOS/doc/telegps-table.png b/AltOS/doc/telegps-table.png Binary files differnew file mode 100644 index 0000000..b3c82e8 --- /dev/null +++ b/AltOS/doc/telegps-table.png diff --git a/AltOS/doc/telegps-v1.0-top.jpg b/AltOS/doc/telegps-v1.0-top.jpg Binary files differnew file mode 100644 index 0000000..ac122f2 --- /dev/null +++ b/AltOS/doc/telegps-v1.0-top.jpg diff --git a/AltOS/doc/telegps.html b/AltOS/doc/telegps.html index 50f74c0..6a2b6a1 100644 --- a/AltOS/doc/telegps.html +++ b/AltOS/doc/telegps.html @@ -1,866 +1,913 @@ -<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>TeleGPS Owner's Manual</title><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="book"><div class="titlepage"><div><div><h1 class="title"><a name="idm45869268938816"></a>TeleGPS Owner's Manual</h1></div><div><h2 class="subtitle">A recording GPS tracker</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Keith</span> <span class="surname">Packard</span></h3></div></div><div><p class="copyright">Copyright 2015 Bdale Garbee and Keith Packard</p></div><div><div class="legalnotice"><a name="idm45869241732464"></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.6</td><td align="left">8 January 2015</td></tr><tr><td align="left" colspan="2"> - Major release adding TeleDongle v3.0 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">13 June 2014</td></tr><tr><td align="left" colspan="2"> - Initial release - </td></tr></table></div></div></div><hr></div><div class="dedication"><div class="titlepage"><div><div><h1 class="title"><a name="idm45869241725744"></a>Acknowledgements</h1></div></div></div><p> - Have fun using these products, and we hope to meet all of you - out on the rocket flight line somewhere. - </p><div class="literallayout"><p><br> -BdaleGarbee,KB0G<br> -NAR#87103,TRA#12201<br> -<br> -KeithPackard,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="#idm45869241723376">1. Quick Start Guide</a></span></dt><dt><span class="chapter"><a href="#idm45869241718752">2. Handling Precautions</a></span></dt><dt><span class="chapter"><a href="#idm45869238226240">3. TeleGPS Hardware</a></span></dt><dd><dl><dt><span class="section"><a href="#idm45869238225600">1. Hooking Up Lithium Polymer Batteries</a></span></dt><dt><span class="section"><a href="#idm45869238222784">2. On-board Data Recording</a></span></dt><dt><span class="section"><a href="#idm45869238218576">3. Installation</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idm45869238215456">4. System Operation</a></span></dt><dd><dl><dt><span class="section"><a href="#idm45869238214784">1. GFSK Telemetry</a></span></dt><dt><span class="section"><a href="#idm45869240867456">2. APRS</a></span></dt><dt><span class="section"><a href="#idm45869242600368">3. Configurable Parameters</a></span></dt><dd><dl><dt><span class="section"><a href="#idm45869242599040">3.1. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idm45869242596912">3.2. Callsign</a></span></dt><dt><span class="section"><a href="#idm45869242595728">3.3. Telemetry/RDF/APRS Enable</a></span></dt><dt><span class="section"><a href="#idm45869242594400">3.4. APRS Interval</a></span></dt><dt><span class="section"><a href="#idm45869242592896">3.5. Maximum Flight Log</a></span></dt><dt><span class="section"><a href="#idm45869242591296">3.6. Logging Trigger Motion</a></span></dt><dt><span class="section"><a href="#idm45869242589968">3.7. Position Reporting Interval</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#idm45869242588320">5. TeleGPS Application</a></span></dt><dd><dl><dt><span class="section"><a href="#idm45869242586736">1. Telemetry Monitoring</a></span></dt><dd><dl><dt><span class="section"><a href="#idm45869242577744">1.1. Map</a></span></dt><dt><span class="section"><a href="#idm45869242571616">1.2. Location</a></span></dt><dt><span class="section"><a href="#idm45869237093232">1.3. Status</a></span></dt><dt><span class="section"><a href="#idm45869237089808">1.4. Table</a></span></dt></dl></dd><dt><span class="section"><a href="#idm45869237085920">2. TeleGPS Menus</a></span></dt><dd><dl><dt><span class="section"><a href="#idm45869237077952">2.1. New Window</a></span></dt><dt><span class="section"><a href="#idm45869237076656">2.2. Graph Data</a></span></dt><dt><span class="section"><a href="#idm45869237060384">2.3. Export Data</a></span></dt><dt><span class="section"><a href="#idm45869237054400">2.4. Load Maps</a></span></dt><dt><span class="section"><a href="#idm45869237040656">2.5. Preferences</a></span></dt><dt><span class="section"><a href="#idm45869237021056">2.6. Close</a></span></dt><dt><span class="section"><a href="#idm45869237019792">2.7. Exit</a></span></dt><dt><span class="section"><a href="#idm45869237018640">2.8. Connect Device</a></span></dt><dt><span class="section"><a href="#idm45869237015104">2.9. Disconnect</a></span></dt><dt><span class="section"><a href="#idm45869237013952">2.10. Scan Channels</a></span></dt><dt><span class="section"><a href="#idm45869237010400">2.11. Download Data</a></span></dt><dt><span class="section"><a href="#idm45869237007264">2.12. Configure Device</a></span></dt><dt><span class="section"><a href="#idm45869236983600">2.13. Flash Device</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#idm45869236982000">6. Updating Device Firmware</a></span></dt><dd><dl><dt><span class="section"><a href="#idm45869236979632">1. - Updating TeleGPS Firmware - </a></span></dt></dl></dd><dt><span class="chapter"><a href="#idm45869236970352">7. Technical Information</a></span></dt><dd><dl><dt><span class="section"><a href="#idm45869236969680">1. GPS Receiver</a></span></dt><dt><span class="section"><a href="#idm45869236966368">2. Micro-controller</a></span></dt><dt><span class="section"><a href="#idm45869236965040">3. Lithium Polymer Battery</a></span></dt><dt><span class="section"><a href="#idm45869236963776">4. Mechanical Considerations</a></span></dt><dt><span class="section"><a href="#idm45869236962448">5. On-board data storage</a></span></dt></dl></dd><dt><span class="appendix"><a href="#idm45869236960992">A. Release Notes</a></span></dt></dl></div><div class="list-of-tables"><p><b>List of Tables</b></p><dl><dt>4.1. <a href="#idm45869238928544">Altus Metrum APRS Comments</a></dt></dl></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idm45869241723376"></a>Chapter1.Quick Start Guide</h1></div></div></div><p> - TeleGPS is designed to be easy to use. Requiring no external - components, flying takes just a few steps. - </p><p> - First, download and install the software from <a class="ulink" href="http://altusmetrum.org/AltOS" target="_top">http://altusmetrum.org/AltOS</a>. This will make sure that - you have the right device drivers installed. - </p><p> - Next, plug in the battery and USB cable and connect TeleGPS to - your computer. This will charge the battery and allow you to - configure the device. - </p><p> - Start the TeleGPS application and set the callsign and frequency - on your TeleGPS device; refer to the Configure TeleGPS section - in the TeleGPS Application chapter for instructions. - </p><p> - Unplug TeleGPS when the battery charger light goes green. This - will enable the radio and logging portions of the TeleGPS - firmware. - </p><p> - Connect TeleDongle to your computer and start TeleGPS or start - AltosDroid on your android device and connect to TeleBT. Set the - frequency to match the TeleGPS and you should be receiving telemetry. - </p></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idm45869241718752"></a>Chapter2.Handling Precautions</h1></div></div></div><p> - All Altus Metrum products are sophisticated electronic devices. - When handled gently and properly installed in an air-frame, they - will deliver impressive results. However, as with all electronic - devices, there are some precautions you must take. - </p><p> - The Lithium polymer batteries have an - extraordinary power density. This is great because we can fly with - much less battery mass... but if they are punctured - or their contacts are allowed to short, they can and will release their - energy very rapidly! - Thus we recommend that you take some care when handling TeleGPS - to keep conductive material from coming in contact with the exposed metal elements. - </p><p> - As with all other rocketry electronics, Altus Metrum devices must - be protected from exposure to corrosive motor exhaust and ejection - charge gasses. - </p></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idm45869238226240"></a>Chapter3.TeleGPS Hardware</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idm45869238225600">1. Hooking Up Lithium Polymer Batteries</a></span></dt><dt><span class="section"><a href="#idm45869238222784">2. On-board Data Recording</a></span></dt><dt><span class="section"><a href="#idm45869238218576">3. Installation</a></span></dt></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idm45869238225600"></a>1.Hooking Up Lithium Polymer Batteries</h2></div></div></div><p> - TeleGPS has a two pin JST PH series connector to connect up - a single-cell Lithium Polymer cell (3.7V nominal). You can - purchase matching batteries from the Altus Metrum store, or - other vendors, or you can make your own. Pin 1 of the - connector is positive, pin 2 is negative. Spark Fun sells a - cable with the connector attached, which they call a <a class="ulink" href="https://www.sparkfun.com/products/9914" target="_top">JST Jumper 2 - Wire Assembly</a>. - </p><p> - Many RC vendors also sell lithium polymer batteries with - this same connector. All that we have found use the opposite - polarity, and if you use them that way, you will damage or - destroy TeleGPS. - </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idm45869238222784"></a>2.On-board Data Recording</h2></div></div></div><p> - TeleGPS logs GPS data at a user-configurable rate. Data are - logged to a 2MB on-board flash memory part, which can be - partitioned into several equal-sized blocks, one for each - flight. 64kB of this storage are reserved to hold - configuration data, leaving 1984kB for flight data. - </p><p> - The on-board flash is partitioned into separate flight logs, - each of a fixed maximum size. Increase the maximum size of - each log and you reduce the number of flights that can be - stored. Decrease the size and you can store more flights. - </p><p> - To compute the amount of space needed for a single log, you - can divide the expected time (in seconds) by the sample period - (by default, 1 second per sample) and then multiply the result - by 32 bytes per sample. For instance, a sample period of 1 - second and a flight lasting one hour will take 32 * 3600 = - 115200 bytes. TeleGPS does try to reduce log space used by not - recording position information when it isn't moving, so actual - space consumed may be less than this. - </p><p> - The default size allows for four flights of 496kB each, which - provides over four hours of logging at 1 sample per second. - </p><p> - TeleGPS will not overwrite existing flight data, so be sure to - download flight data and erase it from the onboard flash - before it fills up. TeleGPS will still report telemetry even - if memory is full, so the only thing you will lose is the - on-board data log. - </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idm45869238218576"></a>3.Installation</h2></div></div></div><p> - The battery connectors are a standard 2-pin JST connector and - match batteries sold by Spark Fun. These batteries are - single-cell Lithium Polymer batteries that nominally provide 3.7 - volts. Other vendors sell similar batteries for RC aircraft - using mating connectors, however the polarity for those is - generally reversed from the batteries used by Altus Metrum - products. In particular, the Tenergy batteries supplied for use - in Featherweight flight computers are not compatible with Altus - Metrum flight computers or battery chargers. <span class="emphasis"><em>Check - polarity and voltage before connecting any battery not purchased - from Altus Metrum or Spark Fun.</em></span> - </p><p> - TeleGPS uses an integrate GPS patch antenna and won't - receive GPS signals if installed inside a metal or carbon - fiber compartment. Test GPS reception and telemetry - transmission with the system installed and all other - electronics powered up to verify signal reception and make - sure there isn't any interference from other systems. - </p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idm45869238215456"></a>Chapter4.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="#idm45869238214784">1. GFSK Telemetry</a></span></dt><dt><span class="section"><a href="#idm45869240867456">2. APRS</a></span></dt><dt><span class="section"><a href="#idm45869242600368">3. Configurable Parameters</a></span></dt><dd><dl><dt><span class="section"><a href="#idm45869242599040">3.1. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idm45869242596912">3.2. Callsign</a></span></dt><dt><span class="section"><a href="#idm45869242595728">3.3. Telemetry/RDF/APRS Enable</a></span></dt><dt><span class="section"><a href="#idm45869242594400">3.4. APRS Interval</a></span></dt><dt><span class="section"><a href="#idm45869242592896">3.5. Maximum Flight Log</a></span></dt><dt><span class="section"><a href="#idm45869242591296">3.6. Logging Trigger Motion</a></span></dt><dt><span class="section"><a href="#idm45869242589968">3.7. Position Reporting Interval</a></span></dt></dl></dd></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idm45869238214784"></a>1.GFSK Telemetry</h2></div></div></div><p> - TeleGPS's native telemetry system doesn't use a 'normal packet - radio' mode like APRS because it's not very efficient. The - GFSK modulation we use is FSK with the base-band pulses passed - through a Gaussian filter before they go into the modulator to - limit the transmitted bandwidth. When combined with forward - error correction and interleaving, this allows us to have a - very robust 19.2 kilobit data link with only 10-40 milliwatts - of transmit power, a whip antenna in the rocket, and a - hand-held Yagi on the ground. We've had flights to above 21k - feet AGL with great reception, and calculations suggest we - should be good to well over 40k feet AGL with a 5-element yagi - on the ground with our 10mW units and over 100k feet AGL with - the 40mW devices. - </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idm45869240867456"></a>2.APRS</h2></div></div></div><p> - TeleGPS can send APRS if desired, and the - interval between APRS packets can be configured. As each APRS - packet takes a full second to transmit, we recommend an - interval of at least 5 seconds to avoid consuming too much - battery power or radio channel bandwidth. You can configure - the APRS interval using AltosUI; that process is described in - the Configure Altimeter section of the AltosUI chapter. - </p><p> - AltOS uses the APRS compressed position report data format, - which provides for higher position precision and shorter - packets than the original APRS format. It also includes - altitude data, which is invaluable when tracking rockets. We - haven't found a receiver which doesn't handle compressed - positions, but it's just possible that you have one, so if you - have an older device that can receive the raw packets but - isn't displaying position information, it's possible that this - is the cause. - </p><p> - The APRS packet format includes a comment field that can have - arbitrary text in it. AltOS uses this to send status - information about the flight computer. It sends four fields as - shown in the following table. - </p><div class="table"><a name="idm45869238928544"></a><p class="title"><b>Table4.1.Altus Metrum APRS Comments</b></p><div class="table-contents"><table summary="Altus Metrum APRS Comments" border="1"><colgroup><col align="center" class="Field"><col align="center" class="Example"><col align="center" class="Description"></colgroup><thead><tr><th align="center">Field</th><th align="center">Example</th><th align="center">Description</th></tr></thead><tbody><tr><td align="center">1</td><td align="center">L</td><td align="center">GPS Status U for unlocked, L for locked</td></tr><tr><td align="center">2</td><td align="center">6</td><td align="center">Number of Satellites in View</td></tr><tr><td align="center">3</td><td align="center">B4.0</td><td align="center">Battery Voltage</td></tr></tbody></table></div></div><br class="table-break"><p> - Here's an example of an APRS comment showing GPS lock with 6 - satellites in view and a battery at 4.0V. - </p><pre class="screen"> - L6 B4.0 - </pre><p> - </p><p> - Make sure your primary battery is above 3.8V and GPS is locked - with at least 5 or 6 satellites in view before starting. If GPS - is switching between L and U regularly, then it doesn't have a - good lock and you should wait until it becomes stable. - </p><p> - If the GPS receiver loses lock, the APRS data transmitted will - contain the last position for which GPS lock was - available. You can tell that this has happened by noticing - that the GPS status character switches from 'L' to 'U'. Before - GPS has locked, APRS will transmit zero for latitude, - longitude and altitude. - </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idm45869242600368"></a>3.Configurable Parameters</h2></div></div></div><p> - Configuring TeleGPS is very - simple; the few configurable parameters can all be set - using the TeleGPS application over USB. Read - the Configure TeleGPS section in the TeleGPS Software chapter below - for more information. - </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm45869242599040"></a>3.1.Radio Frequency</h3></div></div></div><p> - Altus Metrum boards support radio frequencies in the 70cm - band. By default, the configuration interface provides a - list of 10 “standard” frequencies in 100kHz channels starting at - 434.550MHz. However, the firmware supports use of - any 50kHz multiple within the 70cm band. At any given - launch, we highly recommend coordinating when and by whom each - frequency will be used to avoid interference. And of course, both - TeleGPS and the receiver must be configured to the same - frequency to successfully communicate with each other. - </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm45869242596912"></a>3.2.Callsign</h3></div></div></div><p> - This sets the callsign used for telemetry and APRS to - identify the device. - </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm45869242595728"></a>3.3.Telemetry/RDF/APRS Enable</h3></div></div></div><p> - You can completely disable the radio, if necessary, leaving - TeleGPS only logging data to internal memory. - </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm45869242594400"></a>3.4.APRS Interval</h3></div></div></div><p> - This selects how often APRS packets are transmitted. Set - this to zero to disable APRS without also disabling the - regular telemetry and RDF transmissions. As APRS takes a - full second to transmit a single position report, we - recommend sending packets no more than once every 5 seconds. - </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm45869242592896"></a>3.5.Maximum Flight Log</h3></div></div></div><p> - Changing this value will set the maximum amount of flight - log storage that an individual flight will use. The - available storage is divided into as many flights of the - specified size as can fit in the available space. You can - download and erase individual flight logs. If you fill up - the available storage, future flights will not get logged - until you erase some of the stored ones. - </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm45869242591296"></a>3.6.Logging Trigger Motion</h3></div></div></div><p> - If TeleGPS moves less than this distance over a long period - of time, it will not log that location, saving storage space. - </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm45869242589968"></a>3.7.Position Reporting Interval</h3></div></div></div><p> - This sets how often TeleGPS reports position information via - telemetry and to the on-board log. Reducing this value will - save power and logging memory consumption. - </p></div></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idm45869242588320"></a>Chapter5.TeleGPS Application</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idm45869242586736">1. Telemetry Monitoring</a></span></dt><dd><dl><dt><span class="section"><a href="#idm45869242577744">1.1. Map</a></span></dt><dt><span class="section"><a href="#idm45869242571616">1.2. Location</a></span></dt><dt><span class="section"><a href="#idm45869237093232">1.3. Status</a></span></dt><dt><span class="section"><a href="#idm45869237089808">1.4. Table</a></span></dt></dl></dd><dt><span class="section"><a href="#idm45869237085920">2. TeleGPS Menus</a></span></dt><dd><dl><dt><span class="section"><a href="#idm45869237077952">2.1. New Window</a></span></dt><dt><span class="section"><a href="#idm45869237076656">2.2. Graph Data</a></span></dt><dt><span class="section"><a href="#idm45869237060384">2.3. Export Data</a></span></dt><dt><span class="section"><a href="#idm45869237054400">2.4. Load Maps</a></span></dt><dt><span class="section"><a href="#idm45869237040656">2.5. Preferences</a></span></dt><dt><span class="section"><a href="#idm45869237021056">2.6. Close</a></span></dt><dt><span class="section"><a href="#idm45869237019792">2.7. Exit</a></span></dt><dt><span class="section"><a href="#idm45869237018640">2.8. Connect Device</a></span></dt><dt><span class="section"><a href="#idm45869237015104">2.9. Disconnect</a></span></dt><dt><span class="section"><a href="#idm45869237013952">2.10. Scan Channels</a></span></dt><dt><span class="section"><a href="#idm45869237010400">2.11. Download Data</a></span></dt><dt><span class="section"><a href="#idm45869237007264">2.12. Configure Device</a></span></dt><dt><span class="section"><a href="#idm45869236983600">2.13. Flash Device</a></span></dt></dl></dd></dl></div><p> - The TeleGPS application provides a graphical user interface for - interacting with the Altus Metrum product family. TeleGPS can - monitor telemetry data, configure devices and many other - tasks. The primary interface window is for displaying data - received over the telemetry link. There are additional - tasks available from the main window menu bar. This chapter - is split into sections, each of which documents one of the tasks - provided from the top-level toolbar. - </p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idm45869242586736"></a>1.Telemetry Monitoring</h2></div></div></div><p> - This is the window brought up when you start the - application. If you have a TeleDongle device connected to the - computer, it will automatically be selected for telemetry monitoring - </p><p> - All telemetry data received are automatically recorded in - suitable log files. The name of the files includes the current - date and TeleGPS serial and flight numbers. - </p><p> - The radio frequency being monitored by the TeleDongle device - is displayed at the top of the window. You can configure the - frequency by clicking on the frequency box and selecting the - desired frequency. The TeleGPS application remembers the last - frequency selected for each TeleDongle and selects that - automatically the next time you use that device. - </p><p> - Below the TeleDongle frequency selector, the window contains a few - significant pieces of information about the altimeter providing - the telemetry data stream: - </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>The configured call-sign</p></li><li class="listitem"><p>The device serial number</p></li><li class="listitem"><p>The flight number. TeleGPS remembers how many - times it has flown. - </p></li><li class="listitem"><p> - The Received Signal Strength Indicator value. This lets - you know how strong a signal TeleDongle is receiving. The - radio inside TeleDongle operates down to about -100dBm; - weaker signals may not be receivable. The packet link uses - error detection and correction techniques which prevent - incorrect data from being reported. - </p></li><li class="listitem"><p> - The age of the displayed data, in seconds since the last - successfully received telemetry packet. In normal operation - this will stay in the low single digits. If the number starts - counting up, then you are no longer receiving data over the radio - link from the flight computer. - </p></li></ul></div><p> - Finally, the largest portion of the window contains a set of - tabs, each of which contain some information about the TeleGPS - board. The final 'table' tab displays many of the raw telemetry - values in one place in a spreadsheet-like format. - </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm45869242577744"></a>1.1.Map</h3></div></div></div><p> - The Map tab shows the TeleGPS track over time on top of map - data making it easy to locate the device. - </p><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="495"><tr><td><img src="telegps-map.png" width="495"></td></tr></table></div></div><p> - The map's default scale is approximately 3m (10ft) per pixel. The map - can be dragged using the left mouse button. The map will attempt - to keep the rocket roughly centered while data is being received. - </p><p> - You can adjust the style of map and the zoom level with - buttons on the right side of the map window. You can draw a - line on the map by moving the mouse over the map with a - button other than the left one pressed, or by pressing the - left button while also holding down the shift key. The - length of the line in real-world units will be shown at the - start of the line. - </p><p> - Images are fetched automatically via the Google Maps Static API, - and cached on disk for reuse. If map images cannot be downloaded, - the rocket's path will be traced on a dark gray background - instead. - </p><p> - You can pre-load images for your favorite launch sites - before you leave home; check out the 'Preload Maps' section below. - </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm45869242571616"></a>1.2.Location</h3></div></div></div><p> - The Location tab shows the raw GPS data received from TeleGPS. - </p><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="495"><tr><td><img src="telegps-location.png" width="495"></td></tr></table></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm45869237093232"></a>1.3.Status</h3></div></div></div><p> - The Status tab shows data relative to the location of - TeleGPS when the application first received telemetry from - it. - </p><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="495"><tr><td><img src="telegps-status.png" width="495"></td></tr></table></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm45869237089808"></a>1.4.Table</h3></div></div></div><p> - The Table tab shows detailed information about the GPS - receiver - </p><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="495"><tr><td><img src="telegps-table.png" width="495"></td></tr></table></div></div></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idm45869237085920"></a>2.TeleGPS Menus</h2></div></div></div><p> - TeleGPS has three or four menus at the top of the window: - </p><div class="variablelist"><dl class="variablelist"><dt><span class="term">File</span></dt><dd><p> - New Window, Graph Data, Export Data, Load Maps, Preferences, Close and Exit - </p></dd><dt><span class="term">Monitor</span></dt><dd><p> - Connect Device, Disconnect and Scan Channels - </p></dd><dt><span class="term">Device</span></dt><dd><p> - Download Data, Configure Device and Flash Device - </p></dd><dt><span class="term">Frequency</span></dt><dd><p> - This shows the current monitoring frequency with a - drop-down menu listing other configured - frequencies. You can change the set of frequencies - shown here from the Preferences dialog. This menu is - only shown when the TeleGPS application is connected - to a TeleDongle or TeleBT device. - </p></dd></dl></div><p> - </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm45869237077952"></a>2.1.New Window</h3></div></div></div><p> - This creates another telemetry monitoring window, in case - you have multiple TeleDongle devices connected to the - computer. - </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm45869237076656"></a>2.2.Graph Data</h3></div></div></div><p> - This brings up a file dialog to load a saved log, either - a .telem file of recorded telemetry or .eeprom of saved - data from on-board memory. It looks a bit like the flight - monitoring window, using a selection of tabs to show - different views of the saved data. - </p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idm45869237075344"></a>2.2.1.Graph</h4></div></div></div><p> - The Graph tab shows a plot of the the GPS data - collected. The X axis is time in seconds; there are a - variety of Y axes available for different kinds of data. - </p><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="540"><tr><td><img src="telegps-graph-graph.png" width="540"></td></tr></table></div></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idm45869237071632"></a>2.2.2.Configure Graph</h4></div></div></div><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="540"><tr><td><img src="telegps-graph-configure.png" width="540"></td></tr></table></div></div><p> - This selects which graph elements to show, and, at the - bottom, lets you switch between metric and imperial units - </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idm45869237067968"></a>2.2.3.Statistics</h4></div></div></div><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="540"><tr><td><img src="telegps-graph-stats.png" width="540"></td></tr></table></div></div><p> - Shows overall data computed from the flight. - </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idm45869237064448"></a>2.2.4.Map</h4></div></div></div><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="540"><tr><td><img src="telegps-graph-map.png" width="540"></td></tr></table></div></div><p> - Shows a map of the area overlaid with the GPS track. As with - the telemetry monitoring window, you can select the style - of map and zoom level using buttons along the side; - you can scroll the map by dragging within the map pressing - the left button and you can draw a line to measure - distances using either the left button with the shift key, - or any other button. - </p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm45869237060384"></a>2.3.Export Data</h3></div></div></div><p> - This tool takes the raw data files and makes them available for - external analysis. When you select this button, you are prompted to - select a data file, which can be either a .eeprom or .telem. - The .eeprom files contain higher resolution and more continuous data, - while .telem files contain receiver signal strength information. - Next, a second dialog appears which is used to select - where to write the resulting file. It has a selector to choose - between CSV and KML file formats. - </p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idm45869237058272"></a>2.3.1.Comma Separated Value Format</h4></div></div></div><p> - This is a text file containing the data in a form suitable for - import into a spreadsheet or other external data analysis - tool. The first few lines of the file contain the version and - configuration information from TeleGPS, then - there is a single header line which labels all of the - fields. All of these lines start with a '#' character which - many tools can be configured to skip over. - </p><p> - The remaining lines of the file contain the data, with each - field separated by a comma and at least one space. All of - the sensor values are converted to standard units, with the - barometric data reported in both pressure, altitude and - height above pad units. - </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idm45869237055888"></a>2.3.2.Keyhole Markup Language (for Google Earth)</h4></div></div></div><p> - This is the format used by Google Earth to provide an overlay - within that application. With this, you can use Google Earth to - see the whole flight path in 3D. - </p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm45869237054400"></a>2.4.Load Maps</h3></div></div></div><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="468"><tr><td><img src="load-maps.png" width="468"></td></tr></table></div></div><p> - Before using TeleGPS, you can use Load Maps to load map data - in case you don't have access to the internet while - receiving telemetry. - </p><p> - There's a drop-down menu of rocket launch sites we know - about; if your favorites aren't there, please let us know - the lat/lon and name of the site. The contents of this list - are actually downloaded from our server at run-time, so as - new sites are sent in, they'll get automatically added to - this list. If the launch site isn't in the list, you can - manually enter the lat/lon values - </p><p> - There are four different kinds of maps you can view; you can - select which to download by selecting as many as you like from - the available types: - </p><div class="variablelist"><dl class="variablelist"><dt><span class="term">Hybrid</span></dt><dd><p> - A combination of satellite imagery and road data. This - is the default view. - </p></dd><dt><span class="term">Satellite</span></dt><dd><p> - Just the satellite imagery without any annotation. - </p></dd><dt><span class="term">Roadmap</span></dt><dd><p> - Roads, political boundaries and a few geographic features. - </p></dd><dt><span class="term">Terrain</span></dt><dd><p> - Contour intervals and shading that show hills and - valleys. - </p></dd></dl></div><p> - </p><p> - You can specify the range of zoom levels to download; smaller - numbers show more area with less resolution. The default - level, 0, shows about 3m/pixel. One zoom level change - doubles or halves that number. - </p><p> - The Tile Radius value sets how large an area around the center - point to download. Each tile is 512x512 pixels, and the - 'radius' value specifies how many tiles away from the center - will be downloaded. Specify a radius of 0 and you get only the - center tile. A radius of 1 loads a 3x3 grid, centered on the - specified location. - </p><p> - Clicking the 'Load Map' button will fetch images from Google - Maps; note that Google limits how many images you can fetch at - once, so if you load more than one launch site, you may get - some gray areas in the map which indicate that Google is tired - of sending data to you. Try again later. - </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm45869237040656"></a>2.5.Preferences</h3></div></div></div><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="216"><tr><td><img src="telegps-preferences.png" width="216"></td></tr></table></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idm45869237037648"></a>2.5.1.Voice Settings</h4></div></div></div><p> - AltosUI provides voice announcements during flight so that you - can keep your eyes on the sky and still get information about - the current flight status. However, sometimes you don't want - to hear them. - </p><div class="variablelist"><dl class="variablelist"><dt><span class="term">Enable</span></dt><dd><p>Turns all voice announcements on and off</p></dd><dt><span class="term">Test Voice</span></dt><dd><p> - Plays a short message allowing you to verify - that the audio system is working and the volume settings - are reasonable - </p></dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idm45869237032624"></a>2.5.2.Log Directory</h4></div></div></div><p> - AltosUI logs all telemetry data and saves all TeleMetrum flash - data to this directory. This directory is also used as the - staring point when selecting data files for display or export. - </p><p> - Click on the directory name to bring up a directory choosing - dialog, select a new directory and click 'Select Directory' to - change where AltosUI reads and writes data files. - </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idm45869237030592"></a>2.5.3.Callsign</h4></div></div></div><p> - This value is transmitted in each command packet sent from - TeleDongle and received from an altimeter. It is not used in - telemetry mode, as the callsign configured in the altimeter board - is included in all telemetry packets. Configure this - with the AltosUI operators call sign as needed to comply with - your local radio regulations. - </p><p> - Note that to successfully command a flight computer over the radio - (to configure the altimeter, monitor idle, or fire pyro charges), - the callsign configured here must exactly match the callsign - configured in the flight computer. This matching is case - sensitive. - </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idm45869237028320"></a>2.5.4.Imperial Units</h4></div></div></div><p> - This switches between metric units (meters) and imperial - units (feet and miles). This affects the display of values - use during flight monitoring, configuration, data graphing - and all of the voice announcements. It does not change the - units used when exporting to CSV files, those are always - produced in metric units. - </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idm45869237026800"></a>2.5.5.Serial Debug</h4></div></div></div><p> - This causes all communication with a connected device to be - dumped to the console from which AltosUI was started. If - you've started it from an icon or menu entry, the output - will simply be discarded. This mode can be useful to debug - various serial communication issues. - </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idm45869237025296"></a>2.5.6.Font Size</h4></div></div></div><p> - Selects the set of fonts used in the flight monitor - window. Choose between the small, medium and large sets. - </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idm45869237024000"></a>2.5.7.Look & Feel</h4></div></div></div><p> - Adjust the style of the windows. By default, the TeleGPS - application attempts to blend in with the native style. - </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idm45869237022704"></a>2.5.8.Manage Frequencies</h4></div></div></div><p> - This brings up a dialog where you can configure the set of - frequencies shown in the various frequency menus. You can - add as many as you like, or even reconfigure the default - set. Changing this list does not affect the frequency - settings of any devices, it only changes the set of - frequencies shown in the menus. - </p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm45869237021056"></a>2.6.Close</h3></div></div></div><p> - This closes the current window, leaving any other windows - open and the application running. - </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm45869237019792"></a>2.7.Exit</h3></div></div></div><p> - This closes all TeleGPS windows and terminates the application. - </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm45869237018640"></a>2.8.Connect Device</h3></div></div></div><p> - Selecting this item brings up a dialog box listing all of - the connected TeleDongle devices. When you choose one of - these, AltosUI will display telemetry data as received by - the selected TeleDongle device. - </p><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="279"><tr><td><img src="device-selection.png" width="279"></td></tr></table></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm45869237015104"></a>2.9.Disconnect</h3></div></div></div><p> - Disconnects the currently connected TeleDongle or TeleBT - </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm45869237013952"></a>2.10.Scan Channels</h3></div></div></div><p> - Scans the configured set of frequencies looking for - telemetry signals. A list of all of the discovered signals - is show; selecting one of those and clicking on 'Monitor' - will select that frequency in the associated TeleGPS - application window. - </p><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="279"><tr><td><img src="telegps-scan.png" width="279"></td></tr></table></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm45869237010400"></a>2.11.Download Data</h3></div></div></div><p> - TeleGPS records data to its internal flash memory. - On-board data is recorded at the same rate as telemetry - but is not subject to radio drop-outs. As - such, it generally provides a more complete and precise record. - The 'Download Data' menu entry allows you to read the - flash memory and write it to disk. - </p><p> - Select the 'Download Data' menu entry to bring up a list of - connected TeleGPS devices. After the device has been - selected, a dialog showing the data stored in the - device will be shown allowing you to select which entries to - download and which to delete. You must erase flights in order for the space they - consume to be reused by another track. This prevents - accidentally losing data if you neglect to download - data before starting TeleGPS again. Note that if there is no more - space available in the device, then no data will be recorded. - </p><p> - The file name for each data log is computed automatically - from the recorded date, altimeter serial number and flight - number information. - </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm45869237007264"></a>2.12.Configure Device</h3></div></div></div><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="324"><tr><td><img src="telegps-configure.png" width="324"></td></tr></table></div></div><p> - Select this button and then select any connected TeleGPS - device from the list provided. - </p><p> - The first few lines of the dialog provide information about the - connected device, including the product name, - software version and hardware serial number. Below that are the - individual configuration entries. - </p><p> - At the bottom of the dialog, there are four buttons: - </p><div class="variablelist"><dl class="variablelist"><dt><span class="term">Save</span></dt><dd><p> - This writes any changes to the - configuration parameter block in flash memory. If you don't - press this button, any changes you make will be lost. - </p></dd><dt><span class="term">Reset</span></dt><dd><p> - This resets the dialog to the most recently saved values, - erasing any changes you have made. - </p></dd><dt><span class="term">Reboot</span></dt><dd><p> - This reboots the device. This will restart logging for - a new flight number, if any log information has been - saved for the current flight. - </p></dd><dt><span class="term">Close</span></dt><dd><p> - This closes the dialog. Any unsaved changes will be - lost. - </p></dd></dl></div><p> - The rest of the dialog contains the parameters to be configured. - </p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idm45869236995216"></a>2.12.1.Frequency</h4></div></div></div><p> - This configures which of the frequencies to use for both - telemetry and packet command mode. Note that if you set this - value via packet command mode, the TeleDongle frequency will - also be automatically reconfigured to match so that - communication will continue afterwards. - </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idm45869236993712"></a>2.12.2.RF Calibration</h4></div></div></div><p> - The radios in every Altus Metrum device are calibrated at the - factory to ensure that they transmit and receive on the - specified frequency. If you need to you can adjust the calibration - by changing this value. Do not do this without understanding what - the value means, read the appendix on calibration and/or the source - code for more information. To change a TeleDongle's calibration, - you must reprogram the unit completely. - </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idm45869236992048"></a>2.12.3.Telemetry/RDF/APRS Enable</h4></div></div></div><p> - Enables the radio for transmission during flight. When - disabled, the radio will not transmit anything during flight - at all. - </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idm45869236990736"></a>2.12.4.APRS Interval</h4></div></div></div><p> - How often to transmit GPS information via APRS (in - seconds). When set to zero, APRS transmission is - disabled. This option is available on TeleMetrum v2 and - TeleMega boards. TeleMetrum v1 boards cannot transmit APRS - packets. Note that a single APRS packet takes nearly a full - second to transmit, so enabling this option will prevent - sending any other telemetry during that time. - </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idm45869236989152"></a>2.12.5.Callsign</h4></div></div></div><p> - This sets the call sign included in each telemetry packet. Set this - as needed to conform to your local radio regulations. - </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idm45869236987824"></a>2.12.6.Maximum Log Size</h4></div></div></div><p> - This sets the space (in kilobytes) allocated for each data - log. The available space will be divided into chunks of this - size. A smaller value will allow more logs to be stored, - a larger value will record data for longer times. - </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idm45869236986384"></a>2.12.7.Logging Trigger Motion</h4></div></div></div><p> - If TeleGPS moves less than this distance over a long period - of time, it will not log that location, saving storage space. - </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idm45869236985072"></a>2.12.8.Position Reporting Interval</h4></div></div></div><p> - This sets how often TeleGPS reports position information via - telemetry and to the on-board log. Reducing this value will - save power and logging memory consumption. - </p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idm45869236983600"></a>2.13.Flash Device</h3></div></div></div><p> - This reprograms TeleGPS devices with new firmware. Please - read the directions for flashing devices in the Updating - Device Firmware chapter below. - </p></div></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idm45869236982000"></a>Chapter6.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="#idm45869236979632">1. - Updating TeleGPS Firmware - </a></span></dt></dl></div><p> - TeleGPS is programmed directly over its USB connectors. - </p><p> - You may wish to begin by ensuring you have current firmware images. - These are distributed as part of the TeleGPS software bundle that - also includes the TeleGPS ground station program. Newer ground - station versions typically work fine with older firmware versions, - so you don't need to update your devices just to try out new - software features. You can always download the most recent - version from <a class="ulink" href="http://www.altusmetrum.org/AltOS/" target="_top">http://www.altusmetrum.org/AltOS/</a>. - </p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idm45869236979632"></a>1. - Updating TeleGPS Firmware - </h2></div></div></div><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p> - Attach a battery and power switch to the target - device. Power up the device. - </p></li><li class="listitem"><p> - Using a Micro USB cable, connect the target device to your - computer's USB socket. - </p></li><li class="listitem"><p> - Run TeleGPS, and select 'Flash Device' from the Device menu. - </p></li><li class="listitem"><p> - Select the target device in the Device Selection dialog. - </p></li><li class="listitem"><p> - Select the image you want to flash to the device, which - should have a name in the form - <product>-v<product-version>-<software-version>.ihx, such - as TeleGPS-v1.0-1.4.0.ihx. - </p></li><li class="listitem"><p> - Make sure the configuration parameters are reasonable - looking. If the serial number and/or RF configuration - values aren't right, you'll need to change them. - </p></li><li class="listitem"><p> - Hit the 'OK' button and the software should proceed to flash - the device with new firmware, showing a progress bar. - </p></li><li class="listitem"><p> - Verify that the device is working by using the 'Configure - Altimeter' item to check over the configuration. - </p></li></ol></div></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idm45869236970352"></a>Chapter7.Technical Information</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idm45869236969680">1. GPS Receiver</a></span></dt><dt><span class="section"><a href="#idm45869236966368">2. Micro-controller</a></span></dt><dt><span class="section"><a href="#idm45869236965040">3. Lithium Polymer Battery</a></span></dt><dt><span class="section"><a href="#idm45869236963776">4. Mechanical Considerations</a></span></dt><dt><span class="section"><a href="#idm45869236962448">5. On-board data storage</a></span></dt></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idm45869236969680"></a>1.GPS Receiver</h2></div></div></div><p> - TeleGPS uses the u-Blox Max-7Q GPS receiver. - </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idm45869236966368"></a>2.Micro-controller</h2></div></div></div><p> - TeleGPS uses an NXP LPC11U14 micro-controller. This tiny - CPU contains 32kB of flash for the application and 4kB of RAM for - temporary data storage. - </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idm45869236965040"></a>3.Lithium Polymer Battery</h2></div></div></div><p> - Shipping restrictions may prevent us from including a battery - battery with TeleGPS. - </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idm45869236963776"></a>4.Mechanical Considerations</h2></div></div></div><p> - TeleGPS is designed to be rugged enough for typical rocketry - applications. The 4 mounting holes on the board are sized for - use with 4-40 or M3 screws. - </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idm45869236962448"></a>5.On-board data storage</h2></div></div></div><p> - TeleGPS has 2MB of non-volatile storage, separate from the - code storage memory. The TeleGPS firmware uses this to log - information during flight. - </p></div></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a name="idm45869236960992"></a>AppendixA.Release Notes</h1></div></div></div><div class="simplesect"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idm45869236960352"></a>Version 1.6</h2></div></div></div><p> - Version 1.6 includes support for our updated TeleDongle v3.0 - product and bug fixes in in the flight software for all our boards - and ground station interfaces. - </p><p> - AltOS New Features - </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p> - Add support for TeleDongle v3.0 boards. - </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> - Don't beep out the continuity twice by accident in idle mode. - If the battery voltage report takes longer than the initialiation - sequence, the igniter continuity would get reported twice. - </p></li><li class="listitem"><p> - Record all 32 bits of gyro calibration data in TeleMega and - EasyMega log files. This fixes computation of the gyro rates - in AltosUI. - </p></li><li class="listitem"><p> - Change TeleDongle LED usage. Green LED flashes when valid - packet is received. Red LED flashes when invalid packet is - received. - </p></li><li class="listitem"><p> - Replace LPC11U14 SPI driver with non-interrupt version. The - interrupt code would occasionally wedge on long transfers - if interrupts were blocked for too long. This affects all - released TeleGPS products; if you have a TeleGPS device, - you'll want to reflash the firmware. - </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> - Compute tilt angle from TeleMega and EasyMega log - files. This duplicates the quaternion-based angle tracking - code from the flight firmware inside the ground station - software so that post-flight analysis can include evaluation - of the tilt angle. - </p></li><li class="listitem"><p> - Shows the tool button window when starting with a data file - specified. This means that opening a data file from the file - manager will now bring up the main window to let you operate - the whole 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> - Show the 'Connecting' dialog when using Monitor Idle. Lets - you cancel the Monitor Idle startup when connecting over the - radio link. - </p></li><li class="listitem"><p> - Make 'Monitor Idle' work for TeleGPS devices when connected - over USB. It's nice for testing without needing to broadcast - over the radio. - </p></li><li class="listitem"><p> - Use different Windows API to discover USB devices. This - works better on my Windows 7 box, and will be used if the - older API fails to provide the necessary information. - </p></li><li class="listitem"><p> - Look in more places in the registry to try and identify the - installed Java version on Windows. If you install the - default 32-bit version of Windows on a 64-bit OS, the Java - registry information is hiding \SOFTWARE\Wow6432Node for - some reason. - </p></li><li class="listitem"><p> - Fix file association on Windows by searching for the - javaw.exe program instead of assuming it is in - %SYSTEMROOT%. This makes double-clicking on Altus Metrum - data files in the file manager work correctly. - </p></li><li class="listitem"><p> - When replaying a file, put 'done' in the Age field when we - reach the end of the file, instead of continuing to count forever. - </p></li><li class="listitem"><p> - In the Scan Channels code, wait for five seconds if we see - any packet. This is needed because AltOS now sends the - callsign, serial number and flight number only once every - five seconds these days. - </p></li><li class="listitem"><p> - In the Scan Channels code, reset pending flight state - information each time we change channels. This avoids having - flight computers appear on multiple frequencies by accident. - </p></li></ul></div><p> - </p></div><div class="simplesect"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idm45869236958752"></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="idm45869236957152"></a>Version 1.4</h2></div></div></div><p> - Version 1.4 is a major release. It includes support for our new - TeleGPS product, new features and bug fixes in in the flight - software for all our boards and the AltosUI ground station - </p><p> - AltOS New Features - </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p> - Add support for TeleGPS boards. - </p></li><li class="listitem"><p> - Replace the 'dit dit dit' tones at startup with the current - battery voltage, measured in tenths of a volt. This lets you - check the battery voltage without needing telemetry, which - is especially useful on EasyMini. - </p></li><li class="listitem"><p> - Change state beeping to "Farnsworth spacing", which means - they're quite a bit faster than before, and so they take - less time to send. - </p></li><li class="listitem"><p> - Make the beeper tone configurable, making it possible to - distinguish between two Altus Metrum products in the same ebay. - </p></li><li class="listitem"><p> - Make the firing time for extra pyro channels configurable, - allowing longer (or shorter) than the default 50ms. Only relevant - for TeleMega at this time. - </p></li></ul></div><p> - </p><p> - AltOS Fixes - </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p> - Fix bug preventing the selection of the 'Flight State After' - mode in pyro configuration. - </p></li><li class="listitem"><p> - Fix bug where erasing flights would reset the flight number - to 2 on TeleMega and TeleMetrum v2. - </p></li><li class="listitem"><p> - Fix u-Blox GPS driver to mark course and speed data as being - present. - </p></li></ul></div><p> - </p><p> - AltosUI New Features - </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p> - Add zooming and new content types (terrain and road maps) to - map view. Change map storage format from PNG to Jpeg, which - saves a huge amount of disk space. You will need to - re-download all of your pre-loaded map images. - </p></li><li class="listitem"><p> - Add a distance measuring device to the maps view. Select - this by using any button other than the left one, or by - pressing shift or control on the keyboard while using the - left button. - </p></li><li class="listitem"><p> - Add new 'Ignitor' tab to the flight monitor display for - TeleMega's extra ignitors. - </p></li><li class="listitem"><p> - Increase the width of data lines in the graphs to make them - easier to read. - </p></li><li class="listitem"><p> - Add additional ignitor firing marks and voltages to the - graph so you can see when the ignitors fired, along with - the ignitor voltages. - </p></li><li class="listitem"><p> - Add GPS course, ground speed and climb rate as optional - graph elements. - </p></li></ul></div><p> - </p><p> - AltosUI Fixes - </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p> - When flashing new firmware, re-try opening the device as - sometimes it takes a while for the underlying operating - system to recognize that the device has rebooted in - preparation for the flashing operation. - </p></li><li class="listitem"><p> - Hide Tilt Angle in ascent tab for devices that don't have a gyro. - </p></li><li class="listitem"><p> - Filter out speed and acceleration spikes caused by ejection - charge firing when computing the maximum values. This - provides a more accurate reading of those maximums. - </p></li><li class="listitem"><p> - Fix EasyMini voltage displays. Early EasyMini prototypes - used a 3.0V regulator, and AltosUI still used that value as - the basis of the computation. Production EasyMini boards - have always shipped with a 3.3V regulator. Also, purple - EasyMini boards sensed the battery voltage past the blocking - diode, resulting in a drop of about 150mV from the true - battery voltage. Compensate for that when displaying the - value. - </p></li><li class="listitem"><p> - Display error message when trying to configure maximum - flight log size while the flight computer still has flight - data stored. - </p></li><li class="listitem"><p> - Handle TeleMetrum and TeleMini eeprom files generated with - pre-1.0 firmware. Those ancient versions didn't report the - log format, so just use the product name instead. - </p></li></ul></div><p> - </p><p> - TeleGPS Application - </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p> - New application designed for use with TeleGPS boards. - </p></li><li class="listitem"><p> - Shares code with AltosUI, mostly just trimmed down to focus - on TeleGPS-related functions. - </p></li></ul></div><p> - </p><p> - Documentation changes - </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p> - Re-create the drill template images; they should print - correctly from Firefox at least. Ship these as individual - PDF files so they're easy to print. - </p></li><li class="listitem"><p> - Add a description of the 'Apogee Lockout' setting, which - prevents the apogee charge from firing for a configurable - amount of time after boost. - </p></li></ul></div><p> - </p></div></div></div></body></html> +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>TeleGPS Owner’s Manual</title><link rel="stylesheet" type="text/css" href="am.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.78.1" /></head><body><div xml:lang="en" class="book" lang="en"><div class="titlepage"><div><div><h1 class="title"><a id="idm46008582029136"></a>TeleGPS Owner’s Manual</h1></div><div><h2 class="subtitle">An Owner's Manual for the TeleGPS recording GPS tracker</h2></div><div><h3 class="corpauthor"> + <span class="inlinemediaobject"><img src="telegps-oneline.svg" width="270" /></span> +</h3></div><div><div class="author"><h3 class="author"><span class="firstname">Bdale</span> <span class="surname">Garbee</span></h3><code class="email"><<a class="email" href="mailto:bdale@gag.com">bdale@gag.com</a>></code></div></div><div><div class="author"><h3 class="author"><span class="firstname">Keith</span> <span class="surname">Packard</span></h3><code class="email"><<a class="email" href="mailto:keithp@keithp.com">keithp@keithp.com</a>></code></div></div><div><p class="copyright">Copyright © 2015 Bdale Garbee and Keith Packard</p></div><div><div class="legalnotice"><a id="idm46008582174432"></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><a href="telegps-revhistory.html">Revision History</a></div></div><hr /></div><div class="dedication"><div class="titlepage"><div><div><h1 class="title"><a id="_acknowledgments"></a>Acknowledgments</h1></div></div></div><p>Thanks to Anthony (AJ) Towns for major contributions including +the TeleGPS 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="blockquote"><blockquote class="blockquote"><div class="literallayout"><p>Bdale Garbee, KB0G<br /> +NAR #87103, TRA #12201</p></div></blockquote></div><div class="blockquote"><blockquote class="blockquote"><div class="literallayout"><p>Keith Packard, KD7SQG<br /> +NAR #88757, TRA #12200</p></div></blockquote></div></div><div class="toc"><p><strong>Table of Contents</strong></p><dl class="toc"><dt><span class="chapter"><a href="#_telegps_quick_start_guide">1. TeleGPS Quick Start Guide</a></span></dt><dt><span class="chapter"><a href="#_using_telegps_hardware">2. Using TeleGPS Hardware</a></span></dt><dd><dl><dt><span class="section"><a href="#_hooking_up_lithium_polymer_batteries">2.1. Hooking Up Lithium Polymer Batteries</a></span></dt><dt><span class="section"><a href="#_on_board_data_recording">2.2. On-board Data Recording</a></span></dt><dt><span class="section"><a href="#_installation">2.3. Installation</a></span></dt></dl></dd><dt><span class="chapter"><a href="#_telegps_application">3. TeleGPS Application</a></span></dt><dd><dl><dt><span class="section"><a href="#_telemetry_monitoring">3.1. Telemetry Monitoring</a></span></dt><dd><dl><dt><span class="section"><a href="#_map">3.1.1. Map</a></span></dt><dt><span class="section"><a href="#_location">3.1.2. Location</a></span></dt><dt><span class="section"><a href="#_status">3.1.3. Status</a></span></dt><dt><span class="section"><a href="#_table">3.1.4. Table</a></span></dt></dl></dd><dt><span class="section"><a href="#_telegps_menus">3.2. TeleGPS Menus</a></span></dt><dd><dl><dt><span class="section"><a href="#_new_window">3.2.1. New Window</a></span></dt></dl></dd><dt><span class="section"><a href="#_graph_data">3.3. Graph Data</a></span></dt><dd><dl><dt><span class="section"><a href="#_data_graph">3.3.1. Data Graph</a></span></dt><dt><span class="section"><a href="#_graph_configuration">3.3.2. Graph Configuration</a></span></dt><dt><span class="section"><a href="#_statistics">3.3.3. Statistics</a></span></dt><dt><span class="section"><a href="#_map_2">3.3.4. Map</a></span></dt></dl></dd><dt><span class="section"><a href="#_export_data">3.4. Export Data</a></span></dt><dd><dl><dt><span class="section"><a href="#_comma_separated_value_format">3.4.1. Comma Separated Value Format</a></span></dt><dt><span class="section"><a href="#_keyhole_markup_language_for_google_earth">3.4.2. Keyhole Markup Language (for Google Earth)</a></span></dt></dl></dd><dt><span class="section"><a href="#_load_maps">3.5. Load Maps</a></span></dt><dt><span class="section"><a href="#_preferences">3.6. Preferences</a></span></dt><dd><dl><dt><span class="section"><a href="#_voice_settings">3.6.1. Voice Settings</a></span></dt><dt><span class="section"><a href="#_log_directory">3.6.2. Log Directory</a></span></dt><dt><span class="section"><a href="#_callsign">3.6.3. Callsign</a></span></dt><dt><span class="section"><a href="#_imperial_units">3.6.4. Imperial Units</a></span></dt><dt><span class="section"><a href="#_serial_debug">3.6.5. Serial Debug</a></span></dt><dt><span class="section"><a href="#_font_size">3.6.6. Font size</a></span></dt><dt><span class="section"><a href="#_look_amp_feel">3.6.7. Look & feel</a></span></dt><dt><span class="section"><a href="#_menu_position">3.6.8. Menu position</a></span></dt><dt><span class="section"><a href="#_map_cache_size">3.6.9. Map Cache Size</a></span></dt><dt><span class="section"><a href="#_manage_frequencies">3.6.10. Manage Frequencies</a></span></dt></dl></dd><dt><span class="section"><a href="#_close">3.7. Close</a></span></dt><dt><span class="section"><a href="#_exit">3.8. Exit</a></span></dt><dt><span class="section"><a href="#_connect_device">3.9. Connect Device</a></span></dt><dt><span class="section"><a href="#_disconnect">3.10. Disconnect</a></span></dt><dt><span class="section"><a href="#_scan_channels">3.11. Scan Channels</a></span></dt><dt><span class="section"><a href="#_download_data">3.12. Download Data</a></span></dt><dt><span class="section"><a href="#_configure_device">3.13. Configure Device</a></span></dt><dd><dl><dt><span class="section"><a href="#_frequency">3.13.1. Frequency</a></span></dt><dt><span class="section"><a href="#_rf_calibration">3.13.2. RF Calibration</a></span></dt><dt><span class="section"><a href="#_telemetry_rdf_aprs_enable">3.13.3. Telemetry/RDF/APRS Enable</a></span></dt><dt><span class="section"><a href="#_telemetry_baud_rate">3.13.4. Telemetry baud rate</a></span></dt><dt><span class="section"><a href="#_aprs_interval">3.13.5. APRS Interval</a></span></dt><dt><span class="section"><a href="#_aprs_ssid">3.13.6. APRS SSID</a></span></dt><dt><span class="section"><a href="#_aprs_format">3.13.7. APRS Format</a></span></dt><dt><span class="section"><a href="#_callsign_2">3.13.8. Callsign</a></span></dt><dt><span class="section"><a href="#_logging_trigger_motion">3.13.9. Logging Trigger Motion</a></span></dt><dt><span class="section"><a href="#_position_reporting_interval">3.13.10. Position Reporting Interval</a></span></dt></dl></dd><dt><span class="section"><a href="#_flash_device">3.14. Flash Device</a></span></dt></dl></dd><dt><span class="appendix"><a href="#_telegps_system_operation">A. TeleGPS System Operation</a></span></dt><dd><dl><dt><span class="section"><a href="#_gfsk_telemetry">A.1. GFSK Telemetry</a></span></dt><dt><span class="section"><a href="#_aprs">A.2. APRS</a></span></dt><dt><span class="section"><a href="#_configurable_parameters">A.3. Configurable Parameters</a></span></dt></dl></dd><dt><span class="appendix"><a href="#_handling_precautions">B. Handling Precautions</a></span></dt><dt><span class="appendix"><a href="#_technical_information">C. Technical Information</a></span></dt><dd><dl><dt><span class="section"><a href="#_gps_receiver">C.1. GPS Receiver</a></span></dt><dt><span class="section"><a href="#_micro_controller">C.2. Micro-controller</a></span></dt><dt><span class="section"><a href="#_lithium_polymer_battery">C.3. Lithium Polymer Battery</a></span></dt><dt><span class="section"><a href="#_mechanical_considerations">C.4. Mechanical Considerations</a></span></dt><dt><span class="section"><a href="#_on_board_data_storage">C.5. On-board data storage</a></span></dt></dl></dd><dt><span class="appendix"><a href="#_updating_device_firmware">D. Updating Device Firmware</a></span></dt><dd><dl><dt><span class="section"><a href="#_updating_telegps_firmware">D.1. Updating TeleGPS Firmware</a></span></dt></dl></dd><dt><span class="appendix"><a href="#_release_notes">E. Release Notes</a></span></dt><dd><dl><dt><span class="section"><a href="#_release_notes_for_version_1_6_2">E.1. Release Notes for Version 1.6.2</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos">E.1.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_and_telegps_applications">E.1.2. AltosUI and TeleGPS Applications</a></span></dt><dt><span class="section"><a href="#_documentation">E.1.3. Documentation</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_6_1">E.2. Release Notes for Version 1.6.1</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_2">E.2.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_and_telegps_applications_2">E.2.2. AltosUI and TeleGPS Applications</a></span></dt><dt><span class="section"><a href="#_altosdroid">E.2.3. AltosDroid</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_6">E.3. Release Notes for Version 1.6</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_3">E.3.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_and_telegps_applications_3">E.3.2. AltosUI and TeleGPS Applications</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_5">E.4. Release Notes for Version 1.5</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_4">E.4.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_and_telegps_applications_4">E.4.2. AltosUI and TeleGPS Applications</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_4_2">E.5. Release Notes for Version 1.4.2</a></span></dt><dd><dl><dt><span class="section"><a href="#_altosui_and_telegps_applications_5">E.5.1. AltosUI and TeleGPS Applications</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_4_1">E.6. Release Notes for Version 1.4.1</a></span></dt><dd><dl><dt><span class="section"><a href="#_altosui_and_telegps_applications_6">E.6.1. AltosUI and TeleGPS Applications:</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_4">E.7. Release Notes for Version 1.4</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_5">E.7.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_application">E.7.2. AltosUI Application</a></span></dt><dt><span class="section"><a href="#_telegps_application_2">E.7.3. TeleGPS Application</a></span></dt><dt><span class="section"><a href="#_documentation_2">E.7.4. Documentation</a></span></dt></dl></dd></dl></dd></dl></div><div class="list-of-figures"><p><strong>List of Figures</strong></p><dl><dt>3.1. <a href="#idm46008576256672">TeleGPS Map View</a></dt><dt>3.2. <a href="#idm46008582263920">TeleGPS Location View</a></dt><dt>3.3. <a href="#idm46008576235360">TeleGPS Status View</a></dt><dt>3.4. <a href="#idm46008576230928">TeleGPS Information Table</a></dt><dt>3.5. <a href="#idm46008576214528">TeleGPS Graph</a></dt><dt>3.6. <a href="#idm46008576210624">TeleGPS Graph Configuration</a></dt><dt>3.7. <a href="#idm46008576206112">TeleGPS Statistics</a></dt><dt>3.8. <a href="#idm46008576201824">TeleGPS Map</a></dt><dt>3.9. <a href="#idm46008576189984">Load Maps Window</a></dt><dt>3.10. <a href="#idm46008576173536">TeleGPS Preferences Window</a></dt><dt>3.11. <a href="#idm46008576142560">Device Selection Dialog</a></dt><dt>3.12. <a href="#idm46008576137136">Radio Scanning Dialog</a></dt><dt>3.13. <a href="#idm46008576127328">TeleGPS Configuration Dialog</a></dt></dl></div><div class="list-of-tables"><p><strong>List of Tables</strong></p><dl><dt>A.1. <a href="#idm46008576086176">Altus Metrum APRS Comments</a></dt></dl></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="_telegps_quick_start_guide"></a>Chapter 1. TeleGPS Quick Start Guide</h1></div></div></div><p>TeleGPS is designed to be easy to use. Requiring no external +components, flying takes just a few steps.</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"> +First, download and install the software from +<a class="ulink" href="http://altusmetrum.org/AltOS" target="_top">http://altusmetrum.org/AltOS</a>. This will make sure that +you have the right device drivers installed. +</li><li class="listitem"> +Next, plug in the battery and USB cable and connect TeleGPS to +your computer. This will charge the battery and allow you to +configure the device. +</li><li class="listitem"> +Start the TeleGPS application and set the callsign and frequency +on your TeleGPS device; refer to <a class="xref" href="#_configure_device" title="3.13. Configure Device">Section 3.13, “Configure Device”</a> for instructions. +</li><li class="listitem"> +Unplug TeleGPS when the battery charger light goes green. This +will enable the radio and logging portions of the TeleGPS +firmware. +</li><li class="listitem"> +Connect TeleDongle to your computer and start TeleGPS or start +AltosDroid on your android device and connect to TeleBT. Set the +frequency to match the TeleGPS and you should be receiving telemetry. +</li></ol></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="_using_telegps_hardware"></a>Chapter 2. Using TeleGPS Hardware</h1></div></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_hooking_up_lithium_polymer_batteries"></a>2.1. Hooking Up Lithium Polymer Batteries</h2></div></div></div><p>TeleGPS has a two pin JST PH series connector to connect up +a single-cell Lithium Polymer cell (3.7V nominal). You can +purchase matching batteries from the Altus Metrum store, or +other vendors, or you can make your own. Pin 1 of the +connector is positive, pin 2 is negative. Spark Fun sells a +cable with the connector attached, which they call a +<a class="ulink" href="https://www.sparkfun.com/products/9914" target="_top">JST Jumper 2 Wire Assembly</a></p><div class="warning" style="margin-left: 0; margin-right: 10%;"><h3 class="title">Warning</h3><p>Many RC vendors also sell lithium polymer batteries with +this same connector. All that we have found use the opposite +polarity, and if you use them that way, you will damage or +destroy TeleGPS.</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_on_board_data_recording"></a>2.2. On-board Data Recording</h2></div></div></div><p>TeleGPS logs GPS data at a user-configurable +rate. Data are logged to a 2MB on-board flash memory +part, which can be partitioned into several +equal-sized blocks, one for each flight. 64kB of this +storage are reserved to hold configuration data, +leaving 1984kB for flight data.</p><p>The on-board flash is partitioned into separate flight +logs, each of a fixed maximum size. Increase the +maximum size of each log and you reduce the number of +flights that can be stored. Decrease the size and you +can store more flights.</p><p>To compute the amount of space needed for a single +log, you can divide the expected time (in seconds) by +the sample period (by default, 1 second per sample) +and then multiply the result by 32 bytes per +sample. For instance, a sample period of 1 second and +a flight lasting one hour will take 32 * 3600 = 115200 +bytes. TeleGPS does try to reduce log space used by +not recording position information when it isn’t +moving, so actual space consumed may be less than +this.</p><p>The default size allows for four flights of 496kB +each, which provides over four hours of logging at 1 +sample per second.</p><p>TeleGPS will not overwrite existing flight data, so be +sure to download flight data and erase it from the +onboard flash before it fills up. TeleGPS will still +report telemetry even if memory is full, so the only +thing you will lose is the on-board data log.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_installation"></a>2.3. Installation</h2></div></div></div><p>The battery connectors are a standard 2-pin JST +connector and match batteries sold by Spark Fun. These +batteries are single-cell Lithium Polymer batteries +that nominally provide 3.7 volts. Other vendors sell +similar batteries for RC aircraft using mating +connectors, however the polarity for those is +generally reversed from the batteries used by Altus +Metrum products. In particular, the Tenergy batteries +supplied for use in Featherweight flight computers are +not compatible with Altus Metrum flight computers or +battery chargers.</p><div class="warning" style="margin-left: 0; margin-right: 10%;"><h3 class="title">Warning</h3><p>Check polarity and voltage before connecting any +battery not purchased from Altus Metrum or Spark +Fun.</p></div><p>TeleGPS uses an integrate GPS patch antenna and won’t +receive GPS signals if installed inside a metal or +carbon fiber compartment. Test GPS reception and +telemetry transmission with the system installed and +all other electronics powered up to verify signal +reception and make sure there isn’t any interference +from other systems.</p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="_telegps_application"></a>Chapter 3. TeleGPS Application</h1></div></div></div><p>The TeleGPS application provides a graphical user interface for +interacting with the Altus Metrum product family. TeleGPS can +monitor telemetry data, configure devices and many other +tasks. The primary interface window is for displaying data +received over the telemetry link. There are additional +tasks available from the main window menu bar.</p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_telemetry_monitoring"></a>3.1. Telemetry Monitoring</h2></div></div></div><p>This is the window brought up when you start the +application. If you have a TeleDongle device connected +to the computer, it will automatically be selected for +telemetry monitoring</p><p>All telemetry data received are automatically recorded +in suitable log files. The name of the files includes +the current date and TeleGPS serial and flight +numbers.</p><p>The radio frequency being monitored by the TeleDongle +device is displayed at the top of the window. You can +configure the frequency by clicking on the frequency +box and selecting the desired frequency. The TeleGPS +application remembers the last frequency selected for +each TeleDongle and selects that automatically the +next time you use that device.</p><p>Below the TeleDongle frequency selector, the window +contains a few significant pieces of information about +the altimeter providing the telemetry data stream:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +The configured call-sign +</li><li class="listitem"> +The device serial number +</li><li class="listitem"> +The flight number. TeleGPS remembers how many times +it has flown. +</li><li class="listitem"> +The Received Signal Strength Indicator value. This +lets you know how strong a signal TeleDongle is +receiving. The radio inside TeleDongle operates down +to about -100dBm; weaker signals may not be +receivable. The packet link uses error detection and +correction techniques which prevent incorrect data +from being reported. +</li><li class="listitem"> +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. +</li></ul></div><p>Finally, the largest portion of the window contains a set of +tabs, each of which contain some information about the TeleGPS +board. The final <span class="emphasis"><em>table</em></span> tab displays many of the raw telemetry +values in one place in a spreadsheet-like format.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_map"></a>3.1.1. Map</h3></div></div></div><p>The Map tab shows the TeleGPS track over time +on top of map data making it easy to locate +the device.</p><div class="figure"><a id="idm46008576256672"></a><p class="title"><strong>Figure 3.1. TeleGPS Map View</strong></p><div class="figure-contents"><div class="mediaobject"><img src="telegps-map.png" width="495" alt="telegps-map.png" /></div></div></div><br class="figure-break" /><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 +<a class="xref" href="#_load_maps" title="3.5. Load Maps">Section 3.5, “Load Maps”</a>.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_location"></a>3.1.2. Location</h3></div></div></div><p>The Location tab shows the raw GPS data +received from TeleGPS.</p><div class="figure"><a id="idm46008582263920"></a><p class="title"><strong>Figure 3.2. TeleGPS Location View</strong></p><div class="figure-contents"><div class="mediaobject"><img src="telegps-location.png" width="495" alt="telegps-location.png" /></div></div></div><br class="figure-break" /></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_status"></a>3.1.3. Status</h3></div></div></div><p>The Status tab shows data relative to the +location of TeleGPS when the application first +received telemetry from it.</p><div class="figure"><a id="idm46008576235360"></a><p class="title"><strong>Figure 3.3. TeleGPS Status View</strong></p><div class="figure-contents"><div class="mediaobject"><img src="telegps-status.png" width="495" alt="telegps-status.png" /></div></div></div><br class="figure-break" /></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_table"></a>3.1.4. Table</h3></div></div></div><p>The Table tab shows detailed information about +the GPS receiver</p><div class="figure"><a id="idm46008576230928"></a><p class="title"><strong>Figure 3.4. TeleGPS Information Table</strong></p><div class="figure-contents"><div class="mediaobject"><img src="telegps-table.png" width="495" alt="telegps-table.png" /></div></div></div><br class="figure-break" /></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_telegps_menus"></a>3.2. TeleGPS Menus</h2></div></div></div><p>TeleGPS has three or four menus at the top of +the window:</p><div class="variablelist"><dl class="variablelist"><dt><span class="term"> +File +</span></dt><dd> +New Window, Graph Data, Export Data, Load Maps, +Preferences, Close and Exit +</dd><dt><span class="term"> +Monitor +</span></dt><dd> +Connect Device, Disconnect and Scan Channels +</dd><dt><span class="term"> +Device +</span></dt><dd> +Download Data, Configure Device and Flash Device +</dd><dt><span class="term"> +Frequency +</span></dt><dd> +This shows the current monitoring frequency with a +drop-down menu listing other configured +frequencies. You can change the set of frequencies +shown here from the Preferences dialog. This menu is +only shown when the TeleGPS application is connected +to a TeleDongle or TeleBT device. +</dd></dl></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_new_window"></a>3.2.1. New Window</h3></div></div></div><p>This creates another telemetry monitoring window, in case +you have multiple TeleDongle devices connected to the +computer.</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_graph_data"></a>3.3. Graph Data</h2></div></div></div><p>The Graph tab shows a plot of the the GPS data +collected. The X axis is time in seconds; there are a +variety of Y axes available for different kinds of +data. This window also allows you to see some +statistics computed from the data, and an overall map +of the entire data record.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_data_graph"></a>3.3.1. Data Graph</h3></div></div></div><div class="figure"><a id="idm46008576214528"></a><p class="title"><strong>Figure 3.5. TeleGPS Graph</strong></p><div class="figure-contents"><div class="mediaobject"><img src="telegps-graph-graph.png" width="495" alt="telegps-graph-graph.png" /></div></div></div><br class="figure-break" /></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_graph_configuration"></a>3.3.2. Graph Configuration</h3></div></div></div><div class="figure"><a id="idm46008576210624"></a><p class="title"><strong>Figure 3.6. TeleGPS Graph Configuration</strong></p><div class="figure-contents"><div class="mediaobject"><img src="telegps-graph-configure.png" width="495" alt="telegps-graph-configure.png" /></div></div></div><br class="figure-break" /><p>This selects which graph elements to show, and, at the +bottom, lets you switch between metric and imperial +units</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_statistics"></a>3.3.3. Statistics</h3></div></div></div><div class="figure"><a id="idm46008576206112"></a><p class="title"><strong>Figure 3.7. TeleGPS Statistics</strong></p><div class="figure-contents"><div class="mediaobject"><img src="telegps-graph-stats.png" width="495" alt="telegps-graph-stats.png" /></div></div></div><br class="figure-break" /><p>Shows overall data computed from the flight.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_map_2"></a>3.3.4. Map</h3></div></div></div><div class="figure"><a id="idm46008576201824"></a><p class="title"><strong>Figure 3.8. TeleGPS Map</strong></p><div class="figure-contents"><div class="mediaobject"><img src="telegps-graph-map.png" width="540" alt="telegps-graph-map.png" /></div></div></div><br class="figure-break" /><p>Shows a map of the area overlaid with the GPS track. As with +the telemetry monitoring window, you can select the style +of map and zoom level using buttons along the side; +you can scroll the map by dragging within the map pressing +the left button and you can draw a line to measure +distances using either the left button with the shift key, +or any other button.</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_export_data"></a>3.4. 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 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 id="_comma_separated_value_format"></a>3.4.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 TeleGPS, then +there is a single header line which labels all +of the fields. All of these lines start with a +<span class="emphasis"><em>#</em></span> 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 id="_keyhole_markup_language_for_google_earth"></a>3.4.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 path in 3D.</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_load_maps"></a>3.5. Load Maps</h2></div></div></div><div class="figure"><a id="idm46008576189984"></a><p class="title"><strong>Figure 3.9. Load Maps Window</strong></p><div class="figure-contents"><div class="mediaobject"><img src="load-maps.png" width="468" alt="load-maps.png" /></div></div></div><br class="figure-break" /><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.</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> +A combination of satellite imagery and road data. This +is the default view. +</dd><dt><span class="term"> +Satellite +</span></dt><dd> +Just the satellite imagery without any annotation. +</dd><dt><span class="term"> +Roadmap +</span></dt><dd> +Roads, political boundaries and a few geographic +features. +</dd><dt><span class="term"> +Terrain +</span></dt><dd> +Contour intervals and shading that show hills and +valleys. +</dd></dl></div><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. Larger zoom levels show more detail, smaller +zoom levels less.</p><p>The Map Radius value sets how large an area around the +center point to download. Select a value large enough +to cover any plausible flight from that site. Be aware +that loading a large area with a high maximum zoom +level can attempt to download a lot of data. Loading +hybrid maps with a 10km radius at a minimum zoom of -2 +and a maximum zoom of 2 consumes about 120MB of +space. Terrain and road maps consume about 1/10 as +much space as satellite or hybrid maps.</p><p>Clicking the <span class="emphasis"><em>Load Map</em></span> 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 id="_preferences"></a>3.6. Preferences</h2></div></div></div><div class="figure"><a id="idm46008576173536"></a><p class="title"><strong>Figure 3.10. TeleGPS Preferences Window</strong></p><div class="figure-contents"><div class="mediaobject"><img src="telegps-preferences.png" width="216" alt="telegps-preferences.png" /></div></div></div><br class="figure-break" /><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_voice_settings"></a>3.6.1. Voice Settings</h3></div></div></div><p>TeleGPS 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> +Turns all voice announcements on and off +</dd><dt><span class="term"> +Test Voice +</span></dt><dd> +Plays a short message allowing you to verify +that the audio system is working and the volume settings +are reasonable +</dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_log_directory"></a>3.6.2. Log Directory</h3></div></div></div><p>TeleGPS logs all telemetry data and saves all +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 <span class="emphasis"><em>Select Directory</em></span> to +change where TeleGPS reads and writes data +files.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_callsign"></a>3.6.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 TeleGPS +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 id="_imperial_units"></a>3.6.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 id="_serial_debug"></a>3.6.5. Serial Debug</h3></div></div></div><p>This causes all communication with a connected +device to be dumped to the console from which +TeleGPS 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 id="_font_size"></a>3.6.6. 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 id="_look_amp_feel"></a>3.6.7. Look & feel</h3></div></div></div><p>Switches between the available Java user +interface appearances. The default selection +is supposed to match the native window system +appearance for the target platform.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_menu_position"></a>3.6.8. Menu position</h3></div></div></div><p>Selects the initial position for the main +TeleGPS window that includes all of the +command buttons.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_map_cache_size"></a>3.6.9. Map Cache Size</h3></div></div></div><p>Sets the number of map <span class="emphasis"><em>tiles</em></span> kept in memory +while the application is running. More tiles +consume more memory, but will make panning +around the map faster.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_manage_frequencies"></a>3.6.10. 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 id="_close"></a>3.7. Close</h2></div></div></div><p>This closes the current window, leaving any other windows +open and the application running.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_exit"></a>3.8. Exit</h2></div></div></div><p>This closes all TeleGPS windows and terminates the +application.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_connect_device"></a>3.9. Connect Device</h2></div></div></div><p>Selecting this item brings up a dialog box listing all +of the connected TeleDongle devices. When you choose +one of these, AltosUI will display telemetry data as +received by the selected TeleDongle device.</p><div class="figure"><a id="idm46008576142560"></a><p class="title"><strong>Figure 3.11. Device Selection Dialog</strong></p><div class="figure-contents"><div class="mediaobject"><img src="device-selection.png" width="279" alt="device-selection.png" /></div></div></div><br class="figure-break" /></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_disconnect"></a>3.10. Disconnect</h2></div></div></div><p>Disconnects the currently connected TeleDongle or +TeleBT</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_scan_channels"></a>3.11. Scan Channels</h2></div></div></div><div class="figure"><a id="idm46008576137136"></a><p class="title"><strong>Figure 3.12. Radio Scanning Dialog</strong></p><div class="figure-contents"><div class="mediaobject"><img src="telegps-scan.png" width="279" alt="telegps-scan.png" /></div></div></div><br class="figure-break" /><p>Scans the configured set of frequencies looking for +telemetry signals. A list of all of the discovered +signals is show; selecting one of those and clicking +on <span class="emphasis"><em>Monitor</em></span> will select that frequency in the +associated TeleGPS application window.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_download_data"></a>3.12. Download Data</h2></div></div></div><p>TeleGPS records data to its internal flash memory. +On-board data is recorded at the same rate as +telemetry but is not subject to radio drop-outs. As +such, it generally provides a more complete and +precise record. The <span class="emphasis"><em>Download Data</em></span> menu entry allows +you to read the flash memory and write it to disk.</p><p>Select the <span class="emphasis"><em>Download Data</em></span> menu entry to bring up a +list of connected TeleGPS devices. After the device +has been selected, a dialog showing the data stored in +the device will be shown allowing you to select which +entries to download and which to delete. You must +erase flights in order for the space they consume to +be reused by another track. This prevents accidentally +losing data if you neglect to download data before +starting TeleGPS again. Note that if there is no more +space available in the device, then no data will be +recorded.</p><p>The file name for each data log is computed +automatically from the recorded date, altimeter serial +number and flight number information.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_configure_device"></a>3.13. Configure Device</h2></div></div></div><div class="figure"><a id="idm46008576127328"></a><p class="title"><strong>Figure 3.13. TeleGPS Configuration Dialog</strong></p><div class="figure-contents"><div class="mediaobject"><img src="telegps-configure.png" width="324" alt="telegps-configure.png" /></div></div></div><br class="figure-break" /><p>Select this button and then select any connected TeleGPS +device from the list provided.</p><p>The first few lines of the dialog provide information +about the connected device, including the product +name, software version and hardware serial +number. Below that are the individual configuration +entries.</p><p>At the bottom of the dialog, there are four buttons:</p><div class="variablelist"><dl class="variablelist"><dt><span class="term"> +Save +</span></dt><dd> +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. +</dd><dt><span class="term"> +Reset +</span></dt><dd> +This resets the dialog to the most recently saved +values, erasing any changes you have made. +</dd><dt><span class="term"> +Reboot +</span></dt><dd> +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. +</dd><dt><span class="term"> +Close +</span></dt><dd> +This closes the dialog. Any unsaved changes will be +lost. +</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 id="_frequency"></a>3.13.1. 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 id="_rf_calibration"></a>3.13.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. 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 id="_telemetry_rdf_aprs_enable"></a>3.13.3. 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 id="_telemetry_baud_rate"></a>3.13.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 id="_aprs_interval"></a>3.13.5. 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. +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 id="_aprs_ssid"></a>3.13.6. 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 id="_aprs_format"></a>3.13.7. APRS Format</h3></div></div></div><p>Whether to send APRS data in Compressed or +Uncompressed format. Compressed format is +smaller and more precise. Uncompressed +format is older, but may work better with your +device. The Kenwood TH-D72 only displays +altitude information with Uncompressed +format, while the Yaesu FT1D only displays +altitude with Compressed format. Test before +you fly to see which to use.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_callsign_2"></a>3.13.8. 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 id="_logging_trigger_motion"></a>3.13.9. Logging Trigger Motion</h3></div></div></div><p>This sets the amount of motion that TeleGPS +needs to see before logging the new +position. Motions smaller than this are +skipped, which saves storage space.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_position_reporting_interval"></a>3.13.10. Position Reporting Interval</h3></div></div></div><p>The interval between TeleGPS position reports, +both over the air and in the log. Increase +this to reduce the frequency of radio +transmissions and the length of time available +in the log.</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_flash_device"></a>3.14. Flash Device</h2></div></div></div><p>This reprograms TeleGPS devices with new +firmware. Please read the directions for flashing +devices in <a class="xref" href="#_updating_device_firmware" title="Appendix D. Updating Device Firmware">Appendix D, <em>Updating Device Firmware</em></a>.</p></div></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a id="_telegps_system_operation"></a>Appendix A. TeleGPS System Operation</h1></div></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_gfsk_telemetry"></a>A.1. GFSK Telemetry</h2></div></div></div><p>TeleGPS’s native telemetry system doesn’t use a +<span class="emphasis"><em>normal packet radio</em></span> mode like APRS because it’s not +very efficient. The GFSK modulation we use is FSK +with the base-band pulses passed through a Gaussian +filter before they go into the modulator to limit the +transmitted bandwidth. When combined with forward +error correction and interleaving, this allows us to +have a very robust 19.2 kilobit data link with only +10-40 milliwatts of transmit power, a whip antenna in +the rocket, and a hand-held Yagi on the ground. We’ve +had flights to above 21k feet AGL with great +reception, and calculations suggest we should be good +to well over 40k feet AGL with a 5-element yagi on the +ground with our 10mW units and over 100k feet AGL with +the 40mW devices.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_aprs"></a>A.2. APRS</h2></div></div></div><p>TeleGPS can send APRS if desired, and the +interval between APRS packets can be configured. As each APRS +packet takes a full second to transmit, we recommend an +interval of at least 5 seconds to avoid consuming too much +battery power or radio channel bandwidth. You can configure +the APRS interval using TeleGPS; that process is described in +<a class="xref" href="#_configure_device" title="3.13. Configure Device">Section 3.13, “Configure Device”</a>.</p><p>AltOS supports both compressed and uncompressed APRS +position report data formats. The compressed format +provides for higher position precision and shorter +packets than the uncompressed APRS format. We’ve found +some older APRS receivers that do not handle the +compressed format. The Kenwood TH-72A requires the use +of uncompressed format to display altitude information +correctly. The Yaesu FT1D requires the use of +compressed format to display altitude information.</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 as shown in the following table.</p><div class="table"><a id="idm46008576086176"></a><p class="title"><strong>Table A.1. Altus Metrum APRS Comments</strong></p><div class="table-contents"><table summary="Altus Metrum APRS Comments" cellpadding="4px" style="border-collapse: collapse;border-top: 1px solid #78079a; border-bottom: 1px solid #78079a; border-left: 1px solid #78079a; border-right: 1px solid #78079a; "><colgroup><col class="col_1" /><col class="col_2" /><col class="col_3" /></colgroup><thead><tr><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Field </th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Example </th><th style="border-bottom: 1px solid #78079a; " align="left" valign="top">Description</th></tr></thead><tbody><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>1</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>L</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>GPS Status U for unlocked, L for locked</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>2</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>6</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Number of Satellites in View</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>3</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>B4.0</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Altimeter Battery Voltage</p></td></tr><tr><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>4</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>1286</p></td><td style="" align="left" valign="top"><p>Device Serial Number</p></td></tr></tbody></table></div></div><br class="table-break" /><p>Here’s an example of an APRS comment showing GPS lock with 6 +satellites in view and a primary battery at 4.0V from device 1876.</p><pre class="literallayout">L6 B4.0 1876</pre><p>Make sure your primary battery is above 3.8V +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 <span class="emphasis"><em>L</em></span> to <span class="emphasis"><em>U</em></span>. 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 id="_configurable_parameters"></a>A.3. Configurable Parameters</h2></div></div></div><p>Configuring TeleGPS is very simple; the few configurable +parameters can all be set using the TeleGPS application over +USB. Check out <a class="xref" href="#_configure_device" title="3.13. Configure Device">Section 3.13, “Configure Device”</a>.</p></div></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a id="_handling_precautions"></a>Appendix B. 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><div class="warning" style="margin-left: 0; margin-right: 10%;"><h3 class="title">Warning</h3><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></div><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="appendix"><div class="titlepage"><div><div><h1 class="title"><a id="_technical_information"></a>Appendix C. Technical Information</h1></div></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_gps_receiver"></a>C.1. GPS Receiver</h2></div></div></div><p>TeleGPS uses the u-Blox Max-7Q GPS receiver.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_micro_controller"></a>C.2. Micro-controller</h2></div></div></div><p>TeleGPS uses an NXP LPC11U14 micro-controller. This +tiny CPU contains 32kB of flash for the application +and 4kB of RAM for temporary data storage.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_lithium_polymer_battery"></a>C.3. Lithium Polymer Battery</h2></div></div></div><p>Shipping restrictions may prevent us from including a +battery battery with TeleGPS.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_mechanical_considerations"></a>C.4. Mechanical Considerations</h2></div></div></div><p>TeleGPS is designed to be rugged enough for typical +rocketry applications. The 4 mounting holes on the +board are sized for use with 4-40 or M3 screws.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_on_board_data_storage"></a>C.5. On-board data storage</h2></div></div></div><p>TeleGPS has 2MB of non-volatile storage, separate from +the code storage memory. The TeleGPS firmware uses +this to log information during flight.</p></div></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a id="_updating_device_firmware"></a>Appendix D. Updating Device Firmware</h1></div></div></div><p>TeleGPS is programmed directly over its USB connectors.</p><p>You may wish to begin by ensuring you have current firmware images. +These are distributed as part of the TeleGPS software bundle that +also includes the TeleGPS ground station program. Newer ground +station versions typically work fine with older firmware versions, +so you don’t need to update your devices just to try out new +software features. You can always download the most recent +version from <a class="ulink" href="http://www.altusmetrum.org/AltOS/" target="_top">http://www.altusmetrum.org/AltOS/</a></p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_updating_telegps_firmware"></a>D.1. Updating TeleGPS Firmware</h2></div></div></div><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"> +Attach a battery and power switch to the target +device. Power up the device. +</li><li class="listitem"> +Using a Micro USB cable, connect the target device to +your computer’s USB socket. +</li><li class="listitem"> +Run TeleGPS, and select <span class="emphasis"><em>Flash Device</em></span> from the +Device menu. +</li><li class="listitem"> +Select the target device in the Device Selection +dialog. +</li><li class="listitem"> +Select the image you want to flash to the device, +which should have a name in the form +<product>-v<product-version>-<software-version>.ihx, +such as TeleGPS-v1.0-1.4.0.ihx. +</li><li class="listitem"> +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. +</li><li class="listitem"> +Hit the <span class="emphasis"><em>OK</em></span> button and the software should proceed +to flash the device with new firmware, showing a +progress bar. +</li><li class="listitem"> +Verify that the device is working by using the +'Configure Device item to check over the +configuration. +</li></ol></div></div></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a id="_release_notes"></a>Appendix E. Release Notes</h1></div></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_6_2"></a>E.1. Release Notes for Version 1.6.2</h2></div></div></div><p>Version 1.6.2 includes support for our updated TeleMega v2.0 +product and bug fixes in in the flight software for all our boards +and ground station interfaces.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos"></a>E.1.1. AltOS</h3></div></div></div><p>AltOS New Features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Add support for TeleMega v2.0 boards. +</li><li class="listitem"> +Add PWM servo driver. There’s no higher level code using +this yet, but the driver allows testing of the TeleMega v2.0 +servo output connector. +</li></ul></div><p>AltOS Fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Slow down telemetry packets to allow receiver to keep +up. +</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_and_telegps_applications"></a>E.1.2. AltosUI and TeleGPS Applications</h3></div></div></div><p>AltosUI and TeleGPS Fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Fix post-flight orientation computation when processing +TeleMega and EasyMega eeprom data files. +</li><li class="listitem"> +Capture complete eeprom data even when there are invalid +entries in the data. This keeps reading eeprom contents and +writing the associated .eeprom file when an error is detected. +</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_documentation"></a>E.1.3. Documentation</h3></div></div></div><p>We spent a bunch of time trying to improve our documentation</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +HTML versions now have a table of contents on the left side. +</li><li class="listitem"> +EasyMini now has its own shorter manual. +</li><li class="listitem"> +Provide links between sections in each document. +</li><li class="listitem"> +Lots of minor rewriting and restructuring to avoid +duplication of information +</li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_6_1"></a>E.2. Release Notes for Version 1.6.1</h2></div></div></div><p>Version 1.6.1 includes support for our updated TeleBT v3.0 +product and bug fixes in in the flight software for all our boards +and ground station interfaces.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_2"></a>E.2.1. AltOS</h3></div></div></div><p>AltOS New Features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Add support for TeleBT v3.0 boards. +</li><li class="listitem"> +Add support for uncompressed APRS data, providing support +for older APRS receivers. Uncompressed APRS data is less +precise, takes more bandwidth and doesn’t have integrated +altitude data. +</li></ul></div><p>AltOS Fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Make TeleDongle and TeleBT more tolerant of data rate +variations from transmitting devices. +</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_and_telegps_applications_2"></a>E.2.2. AltosUI and TeleGPS Applications</h3></div></div></div><p>AltosUI and TeleGPS New Features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Add map to Monitor Idle display. It’s nice to be able to +verify that maps are working, instead of needing to use +Monitor Flight. +</li></ul></div><p>AltosUI and TeleGPS Fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Fix frequency configuration to round values instead of +truncate them, avoiding a common 1kHz error in the setting. +</li><li class="listitem"> +Turn the Windows stub into a more useful program that can +launch the application with parameters so that file manager +icons work more reliably. +</li><li class="listitem"> +Force KML export to use a C locale so that numbers are +formatted with <span class="emphasis"><em>.</em></span> instead of <span class="emphasis"><em>,</em></span> for a decimal separator in +non-US locales. +</li><li class="listitem"> +Preload map tiles based on distance rather than number of +tiles; this means you get the same resolution covering the +entire area, rather than having high resolution near the +center and low resolution further away. +</li><li class="listitem"> +Allow configuration of frequency and callsign in Monitor +Idle mode. +</li><li class="listitem"> +Fix layout weirdness when resizing windows on +Windows. Windows shouldn’t have giant blank spaces around +the useful content anymore. +</li><li class="listitem"> +Fix layout weirdness when resizing windows on +Windows. Windows shouldn’t have giant blank spaces around +the useful content anymore. +</li><li class="listitem"> +Use a longer filter for descent speed values. This should +provide something more useful on the display, although it +will take longer to respond to changes now. +</li><li class="listitem"> +Make Replay Flight run in realtime again. It had been set to +run at 10x speed by mistake. +</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosdroid"></a>E.2.3. AltosDroid</h3></div></div></div><p>AltosDroid New Features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Add offline map support using mapping code from AltosUI. +</li><li class="listitem"> +Support TeleDongle (and TeleBT via USB) on devices +supporting USB On-The-Go. +</li><li class="listitem"> +Display additional TeleMega pyro channel status in Pad tab. +</li><li class="listitem"> +Switch between metric and imperial units. +</li><li class="listitem"> +Monitor TeleBT battery voltage. +</li><li class="listitem"> +Track multiple devices at the same time, selecting between +them with a menu or using the map. +</li><li class="listitem"> +Add hybrid, satellite and terrain map types. +</li></ul></div><p>AltosDroid Fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Use standard Android display conventions so that a menu +button is available in the application title bar. +</li><li class="listitem"> +Adjust layout to work on large and small screens; shrinking +the go/no-go lights in smaller environments to try and make +everything visible. +</li><li class="listitem"> +Make voice announcements depend on current tab. +</li><li class="listitem"> +Compute adjustment to current travel direction while in +motion towards rocket. +</li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_6"></a>E.3. Release Notes for Version 1.6</h2></div></div></div><p>Version 1.6 includes support for our updated TeleDongle v3.0 +product and bug fixes in in the flight software for all our boards +and ground station interfaces.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_3"></a>E.3.1. AltOS</h3></div></div></div><p>AltOS New Features</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Add support for TeleDongle v3.0 boards. +</li></ul></div><p>AltOS Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Don’t beep out the continuity twice by accident in idle mode. +If the battery voltage report takes longer than the initialiation +sequence, the igniter continuity would get reported twice. +</li><li class="listitem"> +Record all 32 bits of gyro calibration data in TeleMega and +EasyMega log files. This fixes computation of the gyro rates +in AltosUI. +</li><li class="listitem"> +Change TeleDongle LED usage. Green LED flashes when valid +packet is received. Red LED flashes when invalid packet is +received. +</li><li class="listitem"> +Replace LPC11U14 SPI driver with non-interrupt version. The +interrupt code would occasionally wedge on long transfers +if interrupts were blocked for too long. This affects all +released TeleGPS products; if you have a TeleGPS device, +you’ll want to reflash the firmware. +</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_and_telegps_applications_3"></a>E.3.2. AltosUI and TeleGPS Applications</h3></div></div></div><p>AltosUI and TeleGPS New Features</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Compute tilt angle from TeleMega and EasyMega log +files. This duplicates the quaternion-based angle tracking +code from the flight firmware inside the ground station +software so that post-flight analysis can include evaluation +of the tilt angle. +</li><li class="listitem"> +Shows the tool button window when starting with a data file +specified. This means that opening a data file from the file +manager will now bring up the main window to let you operate +the whole application. +</li></ul></div><p>AltosUI Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Show the <span class="emphasis"><em>Connecting</em></span> dialog when using Monitor Idle. Lets +you cancel the Monitor Idle startup when connecting over the +radio link. +</li><li class="listitem"> +Make <span class="emphasis"><em>Monitor Idle</em></span> work for TeleGPS devices when connected +over USB. It’s nice for testing without needing to broadcast +over the radio. +</li><li class="listitem"> +Use different Windows API to discover USB devices. This +works better on my Windows 7 box, and will be used if the +older API fails to provide the necessary information. +</li><li class="listitem"> +Look in more places in the registry to try and identify the +installed Java version on Windows. If you install the +default 32-bit version of Windows on a 64-bit OS, the Java +registry information is hiding \SOFTWARE\Wow6432Node for +some reason. +</li><li class="listitem"> +Fix file association on Windows by searching for the +javaw.exe program instead of assuming it is in +%SYSTEMROOT%. This makes double-clicking on Altus Metrum +data files in the file manager work correctly. +</li><li class="listitem"> +When replaying a file, put <span class="emphasis"><em>done</em></span> in the Age field when we +reach the end of the file, instead of continuing to count forever. +</li><li class="listitem"> +In the Scan Channels code, wait for five seconds if we see +any packet. This is needed because AltOS now sends the +callsign, serial number and flight number only once every +five seconds these days. +</li><li class="listitem"> +In the Scan Channels code, reset pending flight state +information each time we change channels. This avoids having +flight computers appear on multiple frequencies by accident. +</li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_5"></a>E.4. Release Notes for 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><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_4"></a>E.4.1. AltOS</h3></div></div></div><p>AltOS New Features</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Add support for EasyMega boards. +</li><li class="listitem"> +Make the APRS SSID be configurable. This lets you track +different rockets on the same receiver without getting +things mixed up. +</li><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li></ul></div><p>AltOS Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Increase the maximum range for altitude values from +/-32767m +to +/-2147483647m, allowing the flight computers to function +correctly above the 32km level. +</li><li class="listitem"> +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. +</li><li class="listitem"> +Allow negative numbers in pyro configuration values. This +lets you specify things like descending speed or +deceleration. +</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_and_telegps_applications_4"></a>E.4.2. AltosUI and TeleGPS Applications</h3></div></div></div><p>AltosUI and TeleGPS New Features</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Support telemetry baud rate selection. Adds menus to +the flight monitoring and configuration for baud rate +selection. +</li><li class="listitem"> +Support APRS SSID configuration. +</li><li class="listitem"> +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. +</li></ul></div><p>AltosUI Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Make the <span class="emphasis"><em>Graph</em></span> button on the landed tab work again. +</li><li class="listitem"> +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. +</li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_4_2"></a>E.5. Release Notes for Version 1.4.2</h2></div></div></div><p>Version 1.4.2 is a minor release. It fixes Java-related install issues on +Windows</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_and_telegps_applications_5"></a>E.5.1. AltosUI and TeleGPS Applications</h3></div></div></div><p>Windows Install Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Checks for Java installation data in more registry locations. +</li><li class="listitem"> +Allows user to bypass Java installation in case the +detection fails. +</li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_4_1"></a>E.6. Release Notes for 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><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_and_telegps_applications_6"></a>E.6.1. AltosUI and TeleGPS Applications:</h3></div></div></div><p>Windows Install Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Provide signed Windows driver files. This should avoid any need to +disable driver signature checking on Windows 7 or 8. +</li><li class="listitem"> +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. +</li></ul></div><p>Other Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_4"></a>E.7. Release Notes for 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><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_5"></a>E.7.1. AltOS</h3></div></div></div><p>AltOS new features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Add support for TeleGPS boards. +</li><li class="listitem"> +Make the beeper tone configurable, making it +possible to distinguish between two Altus Metrum +products in the same ebay. +</li><li class="listitem"> +Make the firing time for extra pyro channels +configurable, allowing longer (or shorter) than the +default 50ms. Only relevant for TeleMega at this +time. +</li></ul></div><p>AltOS fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +Replace the <span class="emphasis"><em>dit dit dit</em></span> 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. +</li><li class="listitem"> +Change state beeping to "Farnsworth spacing", which +means they’re quite a bit faster than before, and so +they take less time to send. +</li><li class="listitem"> +Fix bug preventing the selection of the <span class="emphasis"><em>Flight +State After</em></span> mode in pyro configuration. +</li><li class="listitem"> +Fix bug where erasing flights would reset the flight +number to 2 on TeleMega and TeleMetrum v2. +</li><li class="listitem"> +Fix u-Blox GPS driver to mark course and speed data +as being present. +</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_application"></a>E.7.2. AltosUI Application</h3></div></div></div><p>AltosUI new features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li><li class="listitem"> +Add new <span class="emphasis"><em>Ignitor</em></span> tab to the flight monitor display +for TeleMega’s extra ignitors. +</li><li class="listitem"> +Add additional ignitor firing marks and voltages to +the graph so you can see when the ignitors fired, +along with the ignitor voltages. +</li><li class="listitem"> +Add GPS course, ground speed and climb rate as +optional graph elements. +</li></ul></div><p>AltosUI fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +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. +</li><li class="listitem"> +Hide Tilt Angle in ascent tab for devices that don’t +have a gyro. +</li><li class="listitem"> +Increase the width of data lines in the graphs to +make them easier to read. +</li><li class="listitem"> +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. +</li><li class="listitem"> +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. +</li><li class="listitem"> +Display error message when trying to configure +maximum flight log size while the flight computer +still has flight data stored. +</li><li class="listitem"> +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. +</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_telegps_application_2"></a>E.7.3. TeleGPS Application</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +New application designed for use with TeleGPS boards. +</li><li class="listitem"> +Shares code with AltosUI, mostly just trimmed down +to focus on TeleGPS-related functions. +</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_documentation_2"></a>E.7.4. Documentation</h3></div></div></div><p>Documentation changes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"> +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. +</li><li class="listitem"> +Add a description of the <span class="emphasis"><em>Apogee Lockout</em></span> setting, +which prevents the apogee charge from firing for a +configurable amount of time after boost. +</li></ul></div></div></div></div></div></body></html>
\ No newline at end of file diff --git a/AltOS/doc/telegps.pdf b/AltOS/doc/telegps.pdf Binary files differindex fba94e5..031c36b 100644 --- a/AltOS/doc/telegps.pdf +++ b/AltOS/doc/telegps.pdf diff --git a/AltOS/doc/telemega-outline.pdf b/AltOS/doc/telemega-outline.pdf Binary files differindex 6b4fe19..5cf8b60 100644 --- a/AltOS/doc/telemega-outline.pdf +++ b/AltOS/doc/telemega-outline.pdf diff --git a/AltOS/doc/telemetrum-outline.pdf b/AltOS/doc/telemetrum-outline.pdf Binary files differindex f3862d0..c81c5a4 100644 --- a/AltOS/doc/telemetrum-outline.pdf +++ b/AltOS/doc/telemetrum-outline.pdf diff --git a/AltOS/doc/telemetrum-v2.0-th.jpg b/AltOS/doc/telemetrum-v2.0-th.jpg Binary files differnew file mode 100644 index 0000000..ceec699 --- /dev/null +++ b/AltOS/doc/telemetrum-v2.0-th.jpg diff --git a/AltOS/doc/telemetry.pdf b/AltOS/doc/telemetry.pdf Binary files differindex c035641..9109512 100644 --- a/AltOS/doc/telemetry.pdf +++ b/AltOS/doc/telemetry.pdf diff --git a/AltOS/doc/telemini-outline.pdf b/AltOS/doc/telemini-outline.pdf Binary files differnew file mode 100644 index 0000000..d27c697 --- /dev/null +++ b/AltOS/doc/telemini-outline.pdf |
