summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBdale Garbee <bdale@gag.com>2014-09-13 12:28:41 -0600
committerBdale Garbee <bdale@gag.com>2014-09-13 12:28:41 -0600
commitc871dd92a548e6af1e14d8866e01dda37d129747 (patch)
tree0a22e3645841e464db1c1c937c73965c88e2b1e8
parentd97214a95c2f49e41e70a57519034b4e3c3c693a (diff)
update docs
Diffstat
-rw-r--r--AltOS/doc/altos.html214
-rw-r--r--AltOS/doc/altos.pdfbin162027 -> 162027 bytes
-rw-r--r--AltOS/doc/altusmetrum.html657
-rw-r--r--AltOS/doc/altusmetrum.pdfbin14009623 -> 14603787 bytes
-rw-r--r--AltOS/doc/companion.html16
-rw-r--r--AltOS/doc/companion.pdfbin24524 -> 24524 bytes
-rw-r--r--AltOS/doc/configure-altimeter.pngbin44924 -> 47224 bytes
-rw-r--r--AltOS/doc/configure-groundstation.pngbin17329 -> 16306 bytes
-rw-r--r--AltOS/doc/easymega-outline.pdfbin0 -> 7022 bytes
-rw-r--r--AltOS/doc/easymega.svg33
-rw-r--r--AltOS/doc/easymini-outline.pdfbin7047 -> 7047 bytes
-rw-r--r--AltOS/doc/micropeak.html42
-rw-r--r--AltOS/doc/micropeak.pdfbin3675043 -> 3675043 bytes
-rw-r--r--AltOS/doc/release-notes-1.5.html68
-rw-r--r--AltOS/doc/scan-channels.pngbin18787 -> 18400 bytes
-rw-r--r--AltOS/doc/telegps.html138
-rw-r--r--AltOS/doc/telegps.pdfbin2886583 -> 2886587 bytes
-rw-r--r--AltOS/doc/telemega-outline.pdfbin7025 -> 7025 bytes
-rw-r--r--AltOS/doc/telemetrum-outline.pdfbin7097 -> 7097 bytes
-rw-r--r--AltOS/doc/telemetry.html36
-rw-r--r--AltOS/doc/telemetry.pdfbin40587 -> 40587 bytes
21 files changed, 760 insertions, 444 deletions
diff --git a/AltOS/doc/altos.html b/AltOS/doc/altos.html
index 6e5da2b..bae58c0 100644
--- a/AltOS/doc/altos.html
+++ b/AltOS/doc/altos.html
@@ -1,11 +1,11 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>AltOS</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="idp4816880"></a>AltOS</h1></div><div><h2 class="subtitle">Altos Metrum Operating System</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 © 2010 Keith Packard</p></div><div><div class="legalnotice"><a name="idp31226096"></a><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>AltOS</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="idp21800576"></a>AltOS</h1></div><div><h2 class="subtitle">Altos Metrum Operating System</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 © 2010 Keith Packard</p></div><div><div class="legalnotice"><a name="idp48221904"></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.1</td><td align="left">05 November 2012</td></tr><tr><td align="left" colspan="2">Portable version</td></tr><tr><td align="left">Revision 0.1</td><td align="left">22 November 2010</td></tr><tr><td align="left" colspan="2">Initial content</td></tr></table></div></div></div><hr></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="chapter"><a href="#idp31164064">1. Overview</a></span></dt><dt><span class="chapter"><a href="#idp32100176">2. AltOS Porting Layer</a></span></dt><dd><dl><dt><span class="section"><a href="#idp32101680">1. Low-level CPU operations</a></span></dt><dd><dl><dt><span class="section"><a href="#idp32102912">1.1. ao_arch_block_interrupts/ao_arch_release_interrupts</a></span></dt><dt><span class="section"><a href="#idp32104960">1.2. ao_arch_save_regs, ao_arch_save_stack,
- ao_arch_restore_stack</a></span></dt><dt><span class="section"><a href="#idp35902816">1.3. ao_arch_wait_interupt</a></span></dt></dl></dd><dt><span class="section"><a href="#idp35905360">2. GPIO operations</a></span></dt><dd><dl><dt><span class="section"><a href="#idp35906528">2.1. GPIO setup</a></span></dt><dt><span class="section"><a href="#idp35915792">2.2. Reading and writing GPIO pins</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#idp31170336">3. Programming the 8051 with SDCC</a></span></dt><dd><dl><dt><span class="section"><a href="#idp31172432">1. 8051 memory spaces</a></span></dt><dd><dl><dt><span class="section"><a href="#idp31174368">1.1. __data</a></span></dt><dt><span class="section"><a href="#idp31176544">1.2. __idata</a></span></dt><dt><span class="section"><a href="#idp31177984">1.3. __xdata</a></span></dt><dt><span class="section"><a href="#idp31179392">1.4. __pdata</a></span></dt><dt><span class="section"><a href="#idp31180896">1.5. __code</a></span></dt><dt><span class="section"><a href="#idp31182336">1.6. __bit</a></span></dt><dt><span class="section"><a href="#idp31183840">1.7. __sfr, __sfr16, __sfr32, __sbit</a></span></dt></dl></dd><dt><span class="section"><a href="#idp31185376">2. Function calls on the 8051</a></span></dt><dd><dl><dt><span class="section"><a href="#idp31186848">2.1. __reentrant functions</a></span></dt><dt><span class="section"><a href="#idp31189040">2.2. Non __reentrant functions</a></span></dt><dt><span class="section"><a href="#idp31191184">2.3. __interrupt functions</a></span></dt><dt><span class="section"><a href="#idp31192752">2.4. __critical functions and statements</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#idp31194816">4. Task functions</a></span></dt><dd><dl><dt><span class="section"><a href="#idp31195872">1. ao_add_task</a></span></dt><dt><span class="section"><a href="#idp31198128">2. ao_exit</a></span></dt><dt><span class="section"><a href="#idp36730320">3. ao_sleep</a></span></dt><dt><span class="section"><a href="#idp36733920">4. ao_wakeup</a></span></dt><dt><span class="section"><a href="#idp36736912">5. ao_alarm</a></span></dt><dt><span class="section"><a href="#idp36740096">6. ao_start_scheduler</a></span></dt><dt><span class="section"><a href="#idp36742000">7. ao_clock_init</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp36743936">5. Timer Functions</a></span></dt><dd><dl><dt><span class="section"><a href="#idp36745440">1. ao_time</a></span></dt><dt><span class="section"><a href="#idp36747424">2. ao_delay</a></span></dt><dt><span class="section"><a href="#idp36749344">3. ao_timer_set_adc_interval</a></span></dt><dt><span class="section"><a href="#idp36751472">4. ao_timer_init</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp36753664">6. AltOS Mutexes</a></span></dt><dd><dl><dt><span class="section"><a href="#idp36755536">1. ao_mutex_get</a></span></dt><dt><span class="section"><a href="#idp36757376">2. ao_mutex_put</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp36759344">7. DMA engine</a></span></dt><dd><dl><dt><span class="section"><a href="#idp36762784">1. CC1111 DMA Engine</a></span></dt><dd><dl><dt><span class="section"><a href="#idp36763456">1.1. ao_dma_alloc</a></span></dt><dt><span class="section"><a href="#idp36765632">1.2. ao_dma_set_transfer</a></span></dt><dt><span class="section"><a href="#idp36767904">1.3. ao_dma_start</a></span></dt><dt><span class="section"><a href="#idp36769920">1.4. ao_dma_trigger</a></span></dt><dt><span class="section"><a href="#idp36771840">1.5. ao_dma_abort</a></span></dt></dl></dd><dt><span class="section"><a href="#idp36773984">2. STM32L DMA Engine</a></span></dt><dd><dl><dt><span class="section"><a href="#idp36774656">2.1. ao_dma_alloc</a></span></dt><dt><span class="section"><a href="#idp36776656">2.2. ao_dma_set_transfer</a></span></dt><dt><span class="section"><a href="#idp36778912">2.3. ao_dma_set_isr</a></span></dt><dt><span class="section"><a href="#idp36781072">2.4. ao_dma_start</a></span></dt><dt><span class="section"><a href="#idp36783376">2.5. ao_dma_done_transfer</a></span></dt><dt><span class="section"><a href="#idp36785360">2.6. ao_dma_abort</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#idp36787632">8. Stdio interface</a></span></dt><dd><dl><dt><span class="section"><a href="#idp36789136">1. putchar</a></span></dt><dt><span class="section"><a href="#idp36791104">2. getchar</a></span></dt><dt><span class="section"><a href="#idp36793200">3. flush</a></span></dt><dt><span class="section"><a href="#idp36795232">4. ao_add_stdio</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp36799264">9. Command line interface</a></span></dt><dd><dl><dt><span class="section"><a href="#idp36800672">1. ao_cmd_register</a></span></dt><dt><span class="section"><a href="#idp35138512">2. ao_cmd_lex</a></span></dt><dt><span class="section"><a href="#idp34367392">3. ao_cmd_put16</a></span></dt><dt><span class="section"><a href="#idp35043824">4. ao_cmd_put8</a></span></dt><dt><span class="section"><a href="#idp35136016">5. ao_cmd_white</a></span></dt><dt><span class="section"><a href="#idp34188208">6. ao_cmd_hex</a></span></dt><dt><span class="section"><a href="#idp36380096">7. ao_cmd_decimal</a></span></dt><dt><span class="section"><a href="#idp36807664">8. ao_match_word</a></span></dt><dt><span class="section"><a href="#idp36809680">9. ao_cmd_init</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp36811792">10. USB target device</a></span></dt><dd><dl><dt><span class="section"><a href="#idp36813984">1. ao_usb_flush</a></span></dt><dt><span class="section"><a href="#idp36816016">2. ao_usb_putchar</a></span></dt><dt><span class="section"><a href="#idp36818080">3. ao_usb_pollchar</a></span></dt><dt><span class="section"><a href="#idp36820112">4. ao_usb_getchar</a></span></dt><dt><span class="section"><a href="#idp36822016">5. ao_usb_disable</a></span></dt><dt><span class="section"><a href="#idp36824736">6. ao_usb_enable</a></span></dt><dt><span class="section"><a href="#idp36826736">7. ao_usb_init</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp36828848">11. Serial peripherals</a></span></dt><dd><dl><dt><span class="section"><a href="#idp36830832">1. ao_serial_getchar</a></span></dt><dt><span class="section"><a href="#idp36832752">2. ao_serial_putchar</a></span></dt><dt><span class="section"><a href="#idp36834656">3. ao_serial_drain</a></span></dt><dt><span class="section"><a href="#idp36836544">4. ao_serial_set_speed</a></span></dt><dt><span class="section"><a href="#idp36838512">5. ao_serial_init</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp36840592">12. CC1111 Radio peripheral</a></span></dt><dd><dl><dt><span class="section"><a href="#idp36841232">1. Radio Introduction</a></span></dt><dt><span class="section"><a href="#idp36848256">2. ao_radio_set_telemetry</a></span></dt><dt><span class="section"><a href="#idp36850352">3. ao_radio_set_packet</a></span></dt><dt><span class="section"><a href="#idp36852448">4. ao_radio_set_rdf</a></span></dt><dt><span class="section"><a href="#idp36854576">5. ao_radio_idle</a></span></dt><dt><span class="section"><a href="#idp36856512">6. ao_radio_get</a></span></dt><dt><span class="section"><a href="#idp36858432">7. ao_radio_put</a></span></dt><dt><span class="section"><a href="#idp36860208">8. ao_radio_abort</a></span></dt><dt><span class="section"><a href="#idp36862160">9. Radio Telemetry</a></span></dt><dd><dl><dt><span class="section"><a href="#idp36863424">9.1. ao_radio_send</a></span></dt><dt><span class="section"><a href="#idp36865584">9.2. ao_radio_recv</a></span></dt></dl></dd><dt><span class="section"><a href="#idp36867984">10. Radio Direction Finding</a></span></dt><dd><dl><dt><span class="section"><a href="#idp36869104">10.1. ao_radio_rdf</a></span></dt></dl></dd><dt><span class="section"><a href="#idp36871136">11. Radio Packet Mode</a></span></dt><dd><dl><dt><span class="section"><a href="#idp36872416">11.1. ao_packet_putchar</a></span></dt><dt><span class="section"><a href="#idp36874528">11.2. ao_packet_pollchar</a></span></dt><dt><span class="section"><a href="#idp36876496">11.3. ao_packet_slave_start</a></span></dt><dt><span class="section"><a href="#idp36878384">11.4. ao_packet_slave_stop</a></span></dt><dt><span class="section"><a href="#idp36880240">11.5. ao_packet_slave_init</a></span></dt><dt><span class="section"><a href="#idp36882208">11.6. ao_packet_master_init</a></span></dt></dl></dd></dl></dd></dl></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp31164064"></a>Chapter 1. Overview</h1></div></div></div><p>
+ </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.1</td><td align="left">05 November 2012</td></tr><tr><td align="left" colspan="2">Portable version</td></tr><tr><td align="left">Revision 0.1</td><td align="left">22 November 2010</td></tr><tr><td align="left" colspan="2">Initial content</td></tr></table></div></div></div><hr></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="chapter"><a href="#idp48146816">1. Overview</a></span></dt><dt><span class="chapter"><a href="#idp49084928">2. AltOS Porting Layer</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49086432">1. Low-level CPU operations</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49087664">1.1. ao_arch_block_interrupts/ao_arch_release_interrupts</a></span></dt><dt><span class="section"><a href="#idp49089712">1.2. ao_arch_save_regs, ao_arch_save_stack,
+ ao_arch_restore_stack</a></span></dt><dt><span class="section"><a href="#idp48316496">1.3. ao_arch_wait_interupt</a></span></dt></dl></dd><dt><span class="section"><a href="#idp48319040">2. GPIO operations</a></span></dt><dd><dl><dt><span class="section"><a href="#idp48320208">2.1. GPIO setup</a></span></dt><dt><span class="section"><a href="#idp48329248">2.2. Reading and writing GPIO pins</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#idp48153376">3. Programming the 8051 with SDCC</a></span></dt><dd><dl><dt><span class="section"><a href="#idp48155472">1. 8051 memory spaces</a></span></dt><dd><dl><dt><span class="section"><a href="#idp48157408">1.1. __data</a></span></dt><dt><span class="section"><a href="#idp48159584">1.2. __idata</a></span></dt><dt><span class="section"><a href="#idp48161024">1.3. __xdata</a></span></dt><dt><span class="section"><a href="#idp48162432">1.4. __pdata</a></span></dt><dt><span class="section"><a href="#idp48163936">1.5. __code</a></span></dt><dt><span class="section"><a href="#idp48165376">1.6. __bit</a></span></dt><dt><span class="section"><a href="#idp48166880">1.7. __sfr, __sfr16, __sfr32, __sbit</a></span></dt></dl></dd><dt><span class="section"><a href="#idp48168416">2. Function calls on the 8051</a></span></dt><dd><dl><dt><span class="section"><a href="#idp48169888">2.1. __reentrant functions</a></span></dt><dt><span class="section"><a href="#idp48172080">2.2. Non __reentrant functions</a></span></dt><dt><span class="section"><a href="#idp48174224">2.3. __interrupt functions</a></span></dt><dt><span class="section"><a href="#idp48175792">2.4. __critical functions and statements</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#idp48177856">4. Task functions</a></span></dt><dd><dl><dt><span class="section"><a href="#idp48178912">1. ao_add_task</a></span></dt><dt><span class="section"><a href="#idp48181168">2. ao_exit</a></span></dt><dt><span class="section"><a href="#idp53712512">3. ao_sleep</a></span></dt><dt><span class="section"><a href="#idp53716112">4. ao_wakeup</a></span></dt><dt><span class="section"><a href="#idp53719104">5. ao_alarm</a></span></dt><dt><span class="section"><a href="#idp53722288">6. ao_start_scheduler</a></span></dt><dt><span class="section"><a href="#idp53724224">7. ao_clock_init</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp53726192">5. Timer Functions</a></span></dt><dd><dl><dt><span class="section"><a href="#idp53727696">1. ao_time</a></span></dt><dt><span class="section"><a href="#idp53729728">2. ao_delay</a></span></dt><dt><span class="section"><a href="#idp53731568">3. ao_timer_set_adc_interval</a></span></dt><dt><span class="section"><a href="#idp53733616">4. ao_timer_init</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp53735808">6. AltOS Mutexes</a></span></dt><dd><dl><dt><span class="section"><a href="#idp53737680">1. ao_mutex_get</a></span></dt><dt><span class="section"><a href="#idp53739520">2. ao_mutex_put</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp53741488">7. DMA engine</a></span></dt><dd><dl><dt><span class="section"><a href="#idp53744928">1. CC1111 DMA Engine</a></span></dt><dd><dl><dt><span class="section"><a href="#idp53745600">1.1. ao_dma_alloc</a></span></dt><dt><span class="section"><a href="#idp53747776">1.2. ao_dma_set_transfer</a></span></dt><dt><span class="section"><a href="#idp53750048">1.3. ao_dma_start</a></span></dt><dt><span class="section"><a href="#idp53752064">1.4. ao_dma_trigger</a></span></dt><dt><span class="section"><a href="#idp53753904">1.5. ao_dma_abort</a></span></dt></dl></dd><dt><span class="section"><a href="#idp53756048">2. STM32L DMA Engine</a></span></dt><dd><dl><dt><span class="section"><a href="#idp53756720">2.1. ao_dma_alloc</a></span></dt><dt><span class="section"><a href="#idp53758640">2.2. ao_dma_set_transfer</a></span></dt><dt><span class="section"><a href="#idp53760896">2.3. ao_dma_set_isr</a></span></dt><dt><span class="section"><a href="#idp53763056">2.4. ao_dma_start</a></span></dt><dt><span class="section"><a href="#idp53765360">2.5. ao_dma_done_transfer</a></span></dt><dt><span class="section"><a href="#idp53767344">2.6. ao_dma_abort</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#idp53769616">8. Stdio interface</a></span></dt><dd><dl><dt><span class="section"><a href="#idp53771120">1. putchar</a></span></dt><dt><span class="section"><a href="#idp53773088">2. getchar</a></span></dt><dt><span class="section"><a href="#idp53775184">3. flush</a></span></dt><dt><span class="section"><a href="#idp53777216">4. ao_add_stdio</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp53781248">9. Command line interface</a></span></dt><dd><dl><dt><span class="section"><a href="#idp53782656">1. ao_cmd_register</a></span></dt><dt><span class="section"><a href="#idp53791296">2. ao_cmd_lex</a></span></dt><dt><span class="section"><a href="#idp53793376">3. ao_cmd_put16</a></span></dt><dt><span class="section"><a href="#idp53795216">4. ao_cmd_put8</a></span></dt><dt><span class="section"><a href="#idp53797104">5. ao_cmd_white</a></span></dt><dt><span class="section"><a href="#idp53799168">6. ao_cmd_hex</a></span></dt><dt><span class="section"><a href="#idp53801216">7. ao_cmd_decimal</a></span></dt><dt><span class="section"><a href="#idp53803312">8. ao_match_word</a></span></dt><dt><span class="section"><a href="#idp53805392">9. ao_cmd_init</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp53807616">10. USB target device</a></span></dt><dd><dl><dt><span class="section"><a href="#idp53809840">1. ao_usb_flush</a></span></dt><dt><span class="section"><a href="#idp53811984">2. ao_usb_putchar</a></span></dt><dt><span class="section"><a href="#idp53814160">3. ao_usb_pollchar</a></span></dt><dt><span class="section"><a href="#idp53816304">4. ao_usb_getchar</a></span></dt><dt><span class="section"><a href="#idp53818320">5. ao_usb_disable</a></span></dt><dt><span class="section"><a href="#idp53821152">6. ao_usb_enable</a></span></dt><dt><span class="section"><a href="#idp53823264">7. ao_usb_init</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp53825488">11. Serial peripherals</a></span></dt><dd><dl><dt><span class="section"><a href="#idp53827504">1. ao_serial_getchar</a></span></dt><dt><span class="section"><a href="#idp53829536">2. ao_serial_putchar</a></span></dt><dt><span class="section"><a href="#idp53831504">3. ao_serial_drain</a></span></dt><dt><span class="section"><a href="#idp50449072">4. ao_serial_set_speed</a></span></dt><dt><span class="section"><a href="#idp51183888">5. ao_serial_init</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp51578544">12. CC1111 Radio peripheral</a></span></dt><dd><dl><dt><span class="section"><a href="#idp50893296">1. Radio Introduction</a></span></dt><dt><span class="section"><a href="#idp51568800">2. ao_radio_set_telemetry</a></span></dt><dt><span class="section"><a href="#idp51487072">3. ao_radio_set_packet</a></span></dt><dt><span class="section"><a href="#idp53835632">4. ao_radio_set_rdf</a></span></dt><dt><span class="section"><a href="#idp53837760">5. ao_radio_idle</a></span></dt><dt><span class="section"><a href="#idp53839696">6. ao_radio_get</a></span></dt><dt><span class="section"><a href="#idp53841616">7. ao_radio_put</a></span></dt><dt><span class="section"><a href="#idp53843392">8. ao_radio_abort</a></span></dt><dt><span class="section"><a href="#idp53845344">9. Radio Telemetry</a></span></dt><dd><dl><dt><span class="section"><a href="#idp53846608">9.1. ao_radio_send</a></span></dt><dt><span class="section"><a href="#idp53848768">9.2. ao_radio_recv</a></span></dt></dl></dd><dt><span class="section"><a href="#idp53851168">10. Radio Direction Finding</a></span></dt><dd><dl><dt><span class="section"><a href="#idp53852288">10.1. ao_radio_rdf</a></span></dt></dl></dd><dt><span class="section"><a href="#idp53854320">11. Radio Packet Mode</a></span></dt><dd><dl><dt><span class="section"><a href="#idp53855600">11.1. ao_packet_putchar</a></span></dt><dt><span class="section"><a href="#idp53857712">11.2. ao_packet_pollchar</a></span></dt><dt><span class="section"><a href="#idp53859680">11.3. ao_packet_slave_start</a></span></dt><dt><span class="section"><a href="#idp53861568">11.4. ao_packet_slave_stop</a></span></dt><dt><span class="section"><a href="#idp53863424">11.5. ao_packet_slave_init</a></span></dt><dt><span class="section"><a href="#idp53865392">11.6. ao_packet_master_init</a></span></dt></dl></dd></dl></dd></dl></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp48146816"></a>Chapter 1. Overview</h1></div></div></div><p>
AltOS is a operating system built for a variety of
microcontrollers used in Altus Metrum devices. It has a simple
porting layer for each CPU while providing a convenient
@@ -85,8 +85,8 @@
</pre><p>
As you can see, a long sequence of subsystems are initialized
and then the scheduler is started.
- </p></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp32100176"></a>Chapter 2. AltOS Porting Layer</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp32101680">1. Low-level CPU operations</a></span></dt><dd><dl><dt><span class="section"><a href="#idp32102912">1.1. ao_arch_block_interrupts/ao_arch_release_interrupts</a></span></dt><dt><span class="section"><a href="#idp32104960">1.2. ao_arch_save_regs, ao_arch_save_stack,
- ao_arch_restore_stack</a></span></dt><dt><span class="section"><a href="#idp35902816">1.3. ao_arch_wait_interupt</a></span></dt></dl></dd><dt><span class="section"><a href="#idp35905360">2. GPIO operations</a></span></dt><dd><dl><dt><span class="section"><a href="#idp35906528">2.1. GPIO setup</a></span></dt><dt><span class="section"><a href="#idp35915792">2.2. Reading and writing GPIO pins</a></span></dt></dl></dd></dl></div><p>
+ </p></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp49084928"></a>Chapter 2. AltOS Porting Layer</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp49086432">1. Low-level CPU operations</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49087664">1.1. ao_arch_block_interrupts/ao_arch_release_interrupts</a></span></dt><dt><span class="section"><a href="#idp49089712">1.2. ao_arch_save_regs, ao_arch_save_stack,
+ ao_arch_restore_stack</a></span></dt><dt><span class="section"><a href="#idp48316496">1.3. ao_arch_wait_interupt</a></span></dt></dl></dd><dt><span class="section"><a href="#idp48319040">2. GPIO operations</a></span></dt><dd><dl><dt><span class="section"><a href="#idp48320208">2.1. GPIO setup</a></span></dt><dt><span class="section"><a href="#idp48329248">2.2. Reading and writing GPIO pins</a></span></dt></dl></dd></dl></div><p>
AltOS provides a CPU-independent interface to various common
microcontroller subsystems, including GPIO pins, interrupts,
SPI, I2C, USB and asynchronous serial interfaces. By making
@@ -94,11 +94,11 @@
application code can all be written that work on any supported
CPU. Many of the architecture abstraction interfaces are
prefixed with ao_arch.
- </p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp32101680"></a>1. Low-level CPU operations</h2></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49086432"></a>1. Low-level CPU operations</h2></div></div></div><p>
These primitive operations provide the abstraction needed to
run the multi-tasking framework while providing reliable
interrupt delivery.
- </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp32102912"></a>1.1. ao_arch_block_interrupts/ao_arch_release_interrupts</h3></div></div></div><pre class="programlisting">
+ </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49087664"></a>1.1. ao_arch_block_interrupts/ao_arch_release_interrupts</h3></div></div></div><pre class="programlisting">
static inline void
ao_arch_block_interrupts(void);
@@ -109,7 +109,7 @@
discard any interrupts. Use these for sections of code that
must be atomic with respect to any code run from an
interrupt handler.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp32104960"></a>1.2. ao_arch_save_regs, ao_arch_save_stack,
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49089712"></a>1.2. ao_arch_save_regs, ao_arch_save_stack,
ao_arch_restore_stack</h3></div></div></div><pre class="programlisting">
static inline void
ao_arch_save_regs(void);
@@ -127,7 +127,7 @@
in the current ao_task structure. ao_arch_restore_stack
switches back to the saved stack, restores all registers and
branches to the saved return address.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp35902816"></a>1.3. ao_arch_wait_interupt</h3></div></div></div><pre class="programlisting">
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp48316496"></a>1.3. ao_arch_wait_interupt</h3></div></div></div><pre class="programlisting">
#define ao_arch_wait_interrupt()
</pre><p>
This stops the CPU, leaving clocks and interrupts
@@ -139,10 +139,10 @@
disable interrupts again. If the CPU doesn't have any
reduced power mode, this must at the least allow pending
interrupts to be processed.
- </p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp35905360"></a>2. GPIO operations</h2></div></div></div><p>
+ </p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp48319040"></a>2. GPIO operations</h2></div></div></div><p>
These functions provide an abstract interface to configure and
manipulate GPIO pins.
- </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp35906528"></a>2.1. GPIO setup</h3></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp48320208"></a>2.1. GPIO setup</h3></div></div></div><p>
These macros may be invoked at system initialization time to
configure pins as needed for system operation. One tricky
aspect is that some chips provide direct access to specific
@@ -151,14 +151,14 @@
provide both port+bit and pin arguments. Simply define the
arguments needed for the target platform and leave the
others undefined.
- </p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp35908368"></a>2.1.1. ao_enable_output</h4></div></div></div><pre class="programlisting">
+ </p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp49091568"></a>2.1.1. ao_enable_output</h4></div></div></div><pre class="programlisting">
#define ao_enable_output(port, bit, pin, value)
</pre><p>
Set the specified port+bit (also called 'pin') for output,
initializing to the specified value. The macro must avoid
driving the pin with the opposite value if at all
possible.
- </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp35910400"></a>2.1.2. ao_enable_input</h4></div></div></div><pre class="programlisting">
+ </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp48323856"></a>2.1.2. ao_enable_input</h4></div></div></div><pre class="programlisting">
#define ao_enable_input(port, bit, mode)
</pre><p>
Sets the specified port/bit to be an input pin. 'mode' is
@@ -176,18 +176,18 @@
0. Don't apply either a pull-up or pull-down. A
disconnected pin will read an undetermined value.
</p></li></ul></div><p>
- </p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp35915792"></a>2.2. Reading and writing GPIO pins</h3></div></div></div><p>
+ </p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp48329248"></a>2.2. Reading and writing GPIO pins</h3></div></div></div><p>
These macros read and write individual GPIO pins.
- </p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp35916864"></a>2.2.1. ao_gpio_set</h4></div></div></div><pre class="programlisting">
+ </p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp48330320"></a>2.2.1. ao_gpio_set</h4></div></div></div><pre class="programlisting">
#define ao_gpio_set(port, bit, pin, value)
</pre><p>
Sets the specified port/bit or pin to the indicated value
- </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp31168000"></a>2.2.2. ao_gpio_get</h4></div></div></div><pre class="programlisting">
+ </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp48151040"></a>2.2.2. ao_gpio_get</h4></div></div></div><pre class="programlisting">
#define ao_gpio_get(port, bit, pin)
</pre><p>
Returns either 1 or 0 depending on whether the input to
the pin is high or low.
- </p></div></div></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp31170336"></a>Chapter 3. Programming the 8051 with SDCC</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp31172432">1. 8051 memory spaces</a></span></dt><dd><dl><dt><span class="section"><a href="#idp31174368">1.1. __data</a></span></dt><dt><span class="section"><a href="#idp31176544">1.2. __idata</a></span></dt><dt><span class="section"><a href="#idp31177984">1.3. __xdata</a></span></dt><dt><span class="section"><a href="#idp31179392">1.4. __pdata</a></span></dt><dt><span class="section"><a href="#idp31180896">1.5. __code</a></span></dt><dt><span class="section"><a href="#idp31182336">1.6. __bit</a></span></dt><dt><span class="section"><a href="#idp31183840">1.7. __sfr, __sfr16, __sfr32, __sbit</a></span></dt></dl></dd><dt><span class="section"><a href="#idp31185376">2. Function calls on the 8051</a></span></dt><dd><dl><dt><span class="section"><a href="#idp31186848">2.1. __reentrant functions</a></span></dt><dt><span class="section"><a href="#idp31189040">2.2. Non __reentrant functions</a></span></dt><dt><span class="section"><a href="#idp31191184">2.3. __interrupt functions</a></span></dt><dt><span class="section"><a href="#idp31192752">2.4. __critical functions and statements</a></span></dt></dl></dd></dl></div><p>
+ </p></div></div></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp48153376"></a>Chapter 3. Programming the 8051 with SDCC</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp48155472">1. 8051 memory spaces</a></span></dt><dd><dl><dt><span class="section"><a href="#idp48157408">1.1. __data</a></span></dt><dt><span class="section"><a href="#idp48159584">1.2. __idata</a></span></dt><dt><span class="section"><a href="#idp48161024">1.3. __xdata</a></span></dt><dt><span class="section"><a href="#idp48162432">1.4. __pdata</a></span></dt><dt><span class="section"><a href="#idp48163936">1.5. __code</a></span></dt><dt><span class="section"><a href="#idp48165376">1.6. __bit</a></span></dt><dt><span class="section"><a href="#idp48166880">1.7. __sfr, __sfr16, __sfr32, __sbit</a></span></dt></dl></dd><dt><span class="section"><a href="#idp48168416">2. Function calls on the 8051</a></span></dt><dd><dl><dt><span class="section"><a href="#idp48169888">2.1. __reentrant functions</a></span></dt><dt><span class="section"><a href="#idp48172080">2.2. Non __reentrant functions</a></span></dt><dt><span class="section"><a href="#idp48174224">2.3. __interrupt functions</a></span></dt><dt><span class="section"><a href="#idp48175792">2.4. __critical functions and statements</a></span></dt></dl></dd></dl></div><p>
The 8051 is a primitive 8-bit processor, designed in the mists
of time in as few transistors as possible. The architecture is
highly irregular and includes several separate memory
@@ -198,7 +198,7 @@
</p><p>
When built on other architectures, the various SDCC-specific
symbols are #defined as empty strings so they don't affect the compiler.
- </p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp31172432"></a>1. 8051 memory spaces</h2></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp48155472"></a>1. 8051 memory spaces</h2></div></div></div><p>
The __data/__xdata/__code memory spaces below were completely
separate in the original 8051 design. In the cc1111, this
isn't true&#8212;they all live in a single unified 64kB address
@@ -212,7 +212,7 @@
is decorated with a memory space identifier which clutters the
code but makes the resulting code far smaller and more
efficient.
- </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp31174368"></a>1.1. __data</h3></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp48157408"></a>1.1. __data</h3></div></div></div><p>
The 8051 can directly address these 128 bytes of
memory. This makes them precious so they should be
reserved for frequently addressed values. Oh, just to
@@ -222,42 +222,42 @@
these registers located at 0x00 - 0x1F. AltOS uses only
the first bank at 0x00 - 0x07, leaving the other 24
bytes available for other data.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp31176544"></a>1.2. __idata</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp48159584"></a>1.2. __idata</h3></div></div></div><p>
There are an additional 128 bytes of internal memory
that share the same address space as __data but which
cannot be directly addressed. The stack normally
occupies this space and so AltOS doesn't place any
static storage here.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp31177984"></a>1.3. __xdata</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp48161024"></a>1.3. __xdata</h3></div></div></div><p>
This is additional general memory accessed through a
single 16-bit address register. The CC1111F32 has 32kB
of memory available here. Most program data should live
in this memory space.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp31179392"></a>1.4. __pdata</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp48162432"></a>1.4. __pdata</h3></div></div></div><p>
This is an alias for the first 256 bytes of __xdata
memory, but uses a shorter addressing mode with
single global 8-bit value for the high 8 bits of the
address and any of several 8-bit registers for the low 8
bits. AltOS uses a few bits of this memory, it should
probably use more.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp31180896"></a>1.5. __code</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp48163936"></a>1.5. __code</h3></div></div></div><p>
All executable code must live in this address space, but
you can stick read-only data here too. It is addressed
using the 16-bit address register and special 'code'
access opcodes. Anything read-only should live in this space.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp31182336"></a>1.6. __bit</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp48165376"></a>1.6. __bit</h3></div></div></div><p>
The 8051 has 128 bits of bit-addressible memory that
lives in the __data segment from 0x20 through
0x2f. Special instructions access these bits
in a single atomic operation. This isn't so much a
separate address space as a special addressing mode for
a few bytes in the __data segment.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp31183840"></a>1.7. __sfr, __sfr16, __sfr32, __sbit</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp48166880"></a>1.7. __sfr, __sfr16, __sfr32, __sbit</h3></div></div></div><p>
Access to physical registers in the device use this mode
which declares the variable name, its type and the
address it lives at. No memory is allocated for these
variables.
- </p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp31185376"></a>2. Function calls on the 8051</h2></div></div></div><p>
+ </p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp48168416"></a>2. Function calls on the 8051</h2></div></div></div><p>
Because stack addressing is expensive, and stack space
limited, the default function call declaration in SDCC
allocates all parameters and local variables in static global
@@ -265,7 +265,7 @@
non-reentrant, and also consume space for parameters and
locals even when they are not running. The benefit is smaller
code and faster execution.
- </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp31186848"></a>2.1. __reentrant functions</h3></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp48169888"></a>2.1. __reentrant functions</h3></div></div></div><p>
All functions which are re-entrant, either due to recursion
or due to a potential context switch while executing, should
be marked as __reentrant so that their parameters and local
@@ -278,7 +278,7 @@
invoked can also be marked as __reentrant. The resulting
code will be larger, but the savings in memory are
frequently worthwhile.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp31189040"></a>2.2. Non __reentrant functions</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp48172080"></a>2.2. Non __reentrant functions</h3></div></div></div><p>
All parameters and locals in non-reentrant functions can
have data space decoration so that they are allocated in
__xdata, __pdata or __data space as desired. This can avoid
@@ -290,14 +290,14 @@
non-reentrant. Because of this, interrupt handlers must not
invoke any library functions, including the multiply and
divide code.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp31191184"></a>2.3. __interrupt functions</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp48174224"></a>2.3. __interrupt functions</h3></div></div></div><p>
Interrupt functions are declared with with an __interrupt
decoration that includes the interrupt number. SDCC saves
and restores all of the registers in these functions and
uses the 'reti' instruction at the end so that they operate
as stand-alone interrupt handlers. Interrupt functions may
call the ao_wakeup function to wake AltOS tasks.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp31192752"></a>2.4. __critical functions and statements</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp48175792"></a>2.4. __critical functions and statements</h3></div></div></div><p>
SDCC has built-in support for suspending interrupts during
critical code. Functions marked as __critical will have
interrupts suspended for the whole period of
@@ -308,9 +308,9 @@
quickly as possible. AltOS doesn't use this form in shared
code as other compilers wouldn't know what to do. Use
ao_arch_block_interrupts and ao_arch_release_interrupts instead.
- </p></div></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp31194816"></a>Chapter 4. Task functions</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp31195872">1. ao_add_task</a></span></dt><dt><span class="section"><a href="#idp31198128">2. ao_exit</a></span></dt><dt><span class="section"><a href="#idp36730320">3. ao_sleep</a></span></dt><dt><span class="section"><a href="#idp36733920">4. ao_wakeup</a></span></dt><dt><span class="section"><a href="#idp36736912">5. ao_alarm</a></span></dt><dt><span class="section"><a href="#idp36740096">6. ao_start_scheduler</a></span></dt><dt><span class="section"><a href="#idp36742000">7. ao_clock_init</a></span></dt></dl></div><p>
+ </p></div></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp48177856"></a>Chapter 4. Task functions</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp48178912">1. ao_add_task</a></span></dt><dt><span class="section"><a href="#idp48181168">2. ao_exit</a></span></dt><dt><span class="section"><a href="#idp53712512">3. ao_sleep</a></span></dt><dt><span class="section"><a href="#idp53716112">4. ao_wakeup</a></span></dt><dt><span class="section"><a href="#idp53719104">5. ao_alarm</a></span></dt><dt><span class="section"><a href="#idp53722288">6. ao_start_scheduler</a></span></dt><dt><span class="section"><a href="#idp53724224">7. ao_clock_init</a></span></dt></dl></div><p>
This chapter documents how to create, destroy and schedule AltOS tasks.
- </p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp31195872"></a>1. ao_add_task</h2></div></div></div><pre class="programlisting">
+ </p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp48178912"></a>1. ao_add_task</h2></div></div></div><pre class="programlisting">
void
ao_add_task(__xdata struct ao_task * task,
void (*start)(void),
@@ -321,12 +321,12 @@
display), and the start address. It does not switch to the
new task. 'start' must not ever return; there is no place
to return to.
- </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp31198128"></a>2. ao_exit</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp48181168"></a>2. ao_exit</h2></div></div></div><pre class="programlisting">
void
ao_exit(void)
</pre><p>
This terminates the current task.
- </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp36730320"></a>3. ao_sleep</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp53712512"></a>3. ao_sleep</h2></div></div></div><pre class="programlisting">
void
ao_sleep(__xdata void *wchan)
</pre><p>
@@ -348,7 +348,7 @@
ao_sleep(&amp;ao_radio_done);
ao_arch_release_interrupts();
</pre><p>
- </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp36733920"></a>4. ao_wakeup</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp53716112"></a>4. ao_wakeup</h2></div></div></div><pre class="programlisting">
void
ao_wakeup(__xdata void *wchan)
</pre><p>
@@ -365,7 +365,7 @@
Note that this need not block interrupts as the ao_sleep block
can only be run from normal mode, and so this sequence can
never be interrupted with execution of the other sequence.
- </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp36736912"></a>5. ao_alarm</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp53719104"></a>5. ao_alarm</h2></div></div></div><pre class="programlisting">
void
ao_alarm(uint16_t delay);
@@ -390,18 +390,18 @@
incoming radio data. If no data is received before the
timeout fires, ao_sleep will return 1 and then this code
will abort the radio receive operation.
- </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp36740096"></a>6. ao_start_scheduler</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp53722288"></a>6. ao_start_scheduler</h2></div></div></div><pre class="programlisting">
void
ao_start_scheduler(void);
</pre><p>
This is called from 'main' when the system is all
initialized and ready to run. It will not return.
- </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp36742000"></a>7. ao_clock_init</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp53724224"></a>7. ao_clock_init</h2></div></div></div><pre class="programlisting">
void
ao_clock_init(void);
</pre><p>
This initializes the main CPU clock and switches to it.
- </p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp36743936"></a>Chapter 5. Timer Functions</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp36745440">1. ao_time</a></span></dt><dt><span class="section"><a href="#idp36747424">2. ao_delay</a></span></dt><dt><span class="section"><a href="#idp36749344">3. ao_timer_set_adc_interval</a></span></dt><dt><span class="section"><a href="#idp36751472">4. ao_timer_init</a></span></dt></dl></div><p>
+ </p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp53726192"></a>Chapter 5. Timer Functions</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp53727696">1. ao_time</a></span></dt><dt><span class="section"><a href="#idp53729728">2. ao_delay</a></span></dt><dt><span class="section"><a href="#idp53731568">3. ao_timer_set_adc_interval</a></span></dt><dt><span class="section"><a href="#idp53733616">4. ao_timer_init</a></span></dt></dl></div><p>
AltOS sets up one of the CPU timers to run at 100Hz and
exposes this tick as the fundemental unit of time. At each
interrupt, AltOS increments the counter, and schedules any tasks
@@ -409,51 +409,51 @@
collect current data readings. Doing this from the ISR ensures
that the values are sampled at a regular rate, independent
of any scheduling jitter.
- </p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp36745440"></a>1. ao_time</h2></div></div></div><pre class="programlisting">
+ </p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp53727696"></a>1. ao_time</h2></div></div></div><pre class="programlisting">
uint16_t
ao_time(void)
</pre><p>
Returns the current system tick count. Note that this is
only a 16 bit value, and so it wraps every 655.36 seconds.
- </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp36747424"></a>2. ao_delay</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp53729728"></a>2. ao_delay</h2></div></div></div><pre class="programlisting">
void
ao_delay(uint16_t ticks);
</pre><p>
Suspend the current task for at least 'ticks' clock units.
- </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp36749344"></a>3. ao_timer_set_adc_interval</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp53731568"></a>3. ao_timer_set_adc_interval</h2></div></div></div><pre class="programlisting">
void
ao_timer_set_adc_interval(uint8_t interval);
</pre><p>
This sets the number of ticks between ADC samples. If set
to 0, no ADC samples are generated. AltOS uses this to
slow down the ADC sampling rate to save power.
- </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp36751472"></a>4. ao_timer_init</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp53733616"></a>4. ao_timer_init</h2></div></div></div><pre class="programlisting">
void
ao_timer_init(void)
</pre><p>
This turns on the 100Hz tick. It is required for any of the
time-based functions to work. It should be called by 'main'
before ao_start_scheduler.
- </p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp36753664"></a>Chapter 6. AltOS Mutexes</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp36755536">1. ao_mutex_get</a></span></dt><dt><span class="section"><a href="#idp36757376">2. ao_mutex_put</a></span></dt></dl></div><p>
+ </p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp53735808"></a>Chapter 6. AltOS Mutexes</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp53737680">1. ao_mutex_get</a></span></dt><dt><span class="section"><a href="#idp53739520">2. ao_mutex_put</a></span></dt></dl></div><p>
AltOS provides mutexes as a basic synchronization primitive. Each
mutexes is simply a byte of memory which holds 0 when the mutex
is free or the task id of the owning task when the mutex is
owned. Mutex calls are checked&#8212;attempting to acquire a mutex
already held by the current task or releasing a mutex not held
by the current task will both cause a panic.
- </p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp36755536"></a>1. ao_mutex_get</h2></div></div></div><pre class="programlisting">
+ </p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp53737680"></a>1. ao_mutex_get</h2></div></div></div><pre class="programlisting">
void
ao_mutex_get(__xdata uint8_t *mutex);
</pre><p>
Acquires the specified mutex, blocking if the mutex is
owned by another task.
- </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp36757376"></a>2. ao_mutex_put</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp53739520"></a>2. ao_mutex_put</h2></div></div></div><pre class="programlisting">
void
ao_mutex_put(__xdata uint8_t *mutex);
</pre><p>
Releases the specified mutex, waking up all tasks waiting
for it.
- </p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp36759344"></a>Chapter 7. DMA engine</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp36762784">1. CC1111 DMA Engine</a></span></dt><dd><dl><dt><span class="section"><a href="#idp36763456">1.1. ao_dma_alloc</a></span></dt><dt><span class="section"><a href="#idp36765632">1.2. ao_dma_set_transfer</a></span></dt><dt><span class="section"><a href="#idp36767904">1.3. ao_dma_start</a></span></dt><dt><span class="section"><a href="#idp36769920">1.4. ao_dma_trigger</a></span></dt><dt><span class="section"><a href="#idp36771840">1.5. ao_dma_abort</a></span></dt></dl></dd><dt><span class="section"><a href="#idp36773984">2. STM32L DMA Engine</a></span></dt><dd><dl><dt><span class="section"><a href="#idp36774656">2.1. ao_dma_alloc</a></span></dt><dt><span class="section"><a href="#idp36776656">2.2. ao_dma_set_transfer</a></span></dt><dt><span class="section"><a href="#idp36778912">2.3. ao_dma_set_isr</a></span></dt><dt><span class="section"><a href="#idp36781072">2.4. ao_dma_start</a></span></dt><dt><span class="section"><a href="#idp36783376">2.5. ao_dma_done_transfer</a></span></dt><dt><span class="section"><a href="#idp36785360">2.6. ao_dma_abort</a></span></dt></dl></dd></dl></div><p>
+ </p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp53741488"></a>Chapter 7. DMA engine</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp53744928">1. CC1111 DMA Engine</a></span></dt><dd><dl><dt><span class="section"><a href="#idp53745600">1.1. ao_dma_alloc</a></span></dt><dt><span class="section"><a href="#idp53747776">1.2. ao_dma_set_transfer</a></span></dt><dt><span class="section"><a href="#idp53750048">1.3. ao_dma_start</a></span></dt><dt><span class="section"><a href="#idp53752064">1.4. ao_dma_trigger</a></span></dt><dt><span class="section"><a href="#idp53753904">1.5. ao_dma_abort</a></span></dt></dl></dd><dt><span class="section"><a href="#idp53756048">2. STM32L DMA Engine</a></span></dt><dd><dl><dt><span class="section"><a href="#idp53756720">2.1. ao_dma_alloc</a></span></dt><dt><span class="section"><a href="#idp53758640">2.2. ao_dma_set_transfer</a></span></dt><dt><span class="section"><a href="#idp53760896">2.3. ao_dma_set_isr</a></span></dt><dt><span class="section"><a href="#idp53763056">2.4. ao_dma_start</a></span></dt><dt><span class="section"><a href="#idp53765360">2.5. ao_dma_done_transfer</a></span></dt><dt><span class="section"><a href="#idp53767344">2.6. ao_dma_abort</a></span></dt></dl></dd></dl></div><p>
The CC1111 and STM32L both contain a useful bit of extra
hardware in the form of a number of programmable DMA
engines. They can be configured to copy data in memory, or
@@ -476,7 +476,7 @@
from hardware to memory, that trigger event is supplied by the
hardware device. When copying data from memory to hardware, the
transfer is usually initiated by software.
- </p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp36762784"></a>1. CC1111 DMA Engine</h2></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp36763456"></a>1.1. ao_dma_alloc</h3></div></div></div><pre class="programlisting">
+ </p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp53744928"></a>1. CC1111 DMA Engine</h2></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp53745600"></a>1.1. ao_dma_alloc</h3></div></div></div><pre class="programlisting">
uint8_t
ao_dma_alloc(__xdata uint8_t *done)
</pre><p>
@@ -486,7 +486,7 @@
AO_DMA_ABORTED bit if ao_dma_abort was called. Note that it
is possible to get both bits if the transfer was aborted
after it had finished.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp36765632"></a>1.2. ao_dma_set_transfer</h3></div></div></div><pre class="programlisting">
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp53747776"></a>1.2. ao_dma_set_transfer</h3></div></div></div><pre class="programlisting">
void
ao_dma_set_transfer(uint8_t id,
void __xdata *srcaddr,
@@ -500,24 +500,24 @@
cfg1 are values directly out of the CC1111 documentation
and tell the DMA engine what the transfer unit size,
direction and step are.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp36767904"></a>1.3. ao_dma_start</h3></div></div></div><pre class="programlisting">
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp53750048"></a>1.3. ao_dma_start</h3></div></div></div><pre class="programlisting">
void
ao_dma_start(uint8_t id);
</pre><p>
Arm the specified DMA engine and await a signal from
either hardware or software to start transferring data.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp36769920"></a>1.4. ao_dma_trigger</h3></div></div></div><pre class="programlisting">
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp53752064"></a>1.4. ao_dma_trigger</h3></div></div></div><pre class="programlisting">
void
ao_dma_trigger(uint8_t id)
</pre><p>
Trigger the specified DMA engine to start copying data.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp36771840"></a>1.5. ao_dma_abort</h3></div></div></div><pre class="programlisting">
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp53753904"></a>1.5. ao_dma_abort</h3></div></div></div><pre class="programlisting">
void
ao_dma_abort(uint8_t id)
</pre><p>
Terminate any in-progress DMA transaction, marking its
'done' variable with the AO_DMA_ABORTED bit.
- </p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp36773984"></a>2. STM32L DMA Engine</h2></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp36774656"></a>2.1. ao_dma_alloc</h3></div></div></div><pre class="programlisting">
+ </p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp53756048"></a>2. STM32L DMA Engine</h2></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp53756720"></a>2.1. ao_dma_alloc</h3></div></div></div><pre class="programlisting">
uint8_t ao_dma_done[];
void
@@ -525,7 +525,7 @@
</pre><p>
Reserve a DMA engine for exclusive use by one
driver.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp36776656"></a>2.2. ao_dma_set_transfer</h3></div></div></div><pre class="programlisting">
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp53758640"></a>2.2. ao_dma_set_transfer</h3></div></div></div><pre class="programlisting">
void
ao_dma_set_transfer(uint8_t id,
void *peripheral,
@@ -538,7 +538,7 @@
value directly out of the STM32L documentation and tells the
DMA engine what the transfer unit size, direction and step
are.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp36778912"></a>2.3. ao_dma_set_isr</h3></div></div></div><pre class="programlisting">
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp53760896"></a>2.3. ao_dma_set_isr</h3></div></div></div><pre class="programlisting">
void
ao_dma_set_isr(uint8_t index, void (*isr)(int))
</pre><p>
@@ -546,7 +546,7 @@
completes in lieu of setting the ao_dma_done bits. Use this
when some work needs to be done when the DMA finishes that
cannot wait until user space resumes.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp36781072"></a>2.4. ao_dma_start</h3></div></div></div><pre class="programlisting">
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp53763056"></a>2.4. ao_dma_start</h3></div></div></div><pre class="programlisting">
void
ao_dma_start(uint8_t id);
</pre><p>
@@ -557,19 +557,19 @@
or the AO_DMA_ABORTED bit if ao_dma_abort was called. Note
that it is possible to get both bits if the transfer was
aborted after it had finished.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp36783376"></a>2.5. ao_dma_done_transfer</h3></div></div></div><pre class="programlisting">
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp53765360"></a>2.5. ao_dma_done_transfer</h3></div></div></div><pre class="programlisting">
void
ao_dma_done_transfer(uint8_t id);
</pre><p>
Signals that a specific DMA engine is done being used. This
allows multiple drivers to use the same DMA engine safely.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp36785360"></a>2.6. ao_dma_abort</h3></div></div></div><pre class="programlisting">
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp53767344"></a>2.6. ao_dma_abort</h3></div></div></div><pre class="programlisting">
void
ao_dma_abort(uint8_t id)
</pre><p>
Terminate any in-progress DMA transaction, marking its
'done' variable with the AO_DMA_ABORTED bit.
- </p></div></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp36787632"></a>Chapter 8. Stdio interface</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp36789136">1. putchar</a></span></dt><dt><span class="section"><a href="#idp36791104">2. getchar</a></span></dt><dt><span class="section"><a href="#idp36793200">3. flush</a></span></dt><dt><span class="section"><a href="#idp36795232">4. ao_add_stdio</a></span></dt></dl></div><p>
+ </p></div></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp53769616"></a>Chapter 8. Stdio interface</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp53771120">1. putchar</a></span></dt><dt><span class="section"><a href="#idp53773088">2. getchar</a></span></dt><dt><span class="section"><a href="#idp53775184">3. flush</a></span></dt><dt><span class="section"><a href="#idp53777216">4. ao_add_stdio</a></span></dt></dl></div><p>
AltOS offers a stdio interface over USB, serial and the RF
packet link. This provides for control of the device locally or
remotely. This is hooked up to the stdio functions by providing
@@ -577,13 +577,13 @@
automatically multiplex the available communication channels;
output is always delivered to the channel which provided the
most recent input.
- </p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp36789136"></a>1. putchar</h2></div></div></div><pre class="programlisting">
+ </p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp53771120"></a>1. putchar</h2></div></div></div><pre class="programlisting">
void
putchar(char c)
</pre><p>
Delivers a single character to the current console
device.
- </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp36791104"></a>2. getchar</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp53773088"></a>2. getchar</h2></div></div></div><pre class="programlisting">
char
getchar(void)
</pre><p>
@@ -591,13 +591,13 @@
console devices. The current console device is set to
that which delivered this character. This blocks until
a character is available.
- </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp36793200"></a>3. flush</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp53775184"></a>3. flush</h2></div></div></div><pre class="programlisting">
void
flush(void)
</pre><p>
Flushes the current console device output buffer. Any
pending characters will be delivered to the target device.
- </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp36795232"></a>4. ao_add_stdio</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp53777216"></a>4. ao_add_stdio</h2></div></div></div><pre class="programlisting">
void
ao_add_stdio(char (*pollchar)(void),
void (*putchar)(char),
@@ -619,13 +619,13 @@
'flush' forces the output buffer to be flushed. It may
block until the buffer is delivered, but it is not
required to do so.
- </p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp36799264"></a>Chapter 9. Command line interface</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp36800672">1. ao_cmd_register</a></span></dt><dt><span class="section"><a href="#idp35138512">2. ao_cmd_lex</a></span></dt><dt><span class="section"><a href="#idp34367392">3. ao_cmd_put16</a></span></dt><dt><span class="section"><a href="#idp35043824">4. ao_cmd_put8</a></span></dt><dt><span class="section"><a href="#idp35136016">5. ao_cmd_white</a></span></dt><dt><span class="section"><a href="#idp34188208">6. ao_cmd_hex</a></span></dt><dt><span class="section"><a href="#idp36380096">7. ao_cmd_decimal</a></span></dt><dt><span class="section"><a href="#idp36807664">8. ao_match_word</a></span></dt><dt><span class="section"><a href="#idp36809680">9. ao_cmd_init</a></span></dt></dl></div><p>
+ </p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp53781248"></a>Chapter 9. Command line interface</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp53782656">1. ao_cmd_register</a></span></dt><dt><span class="section"><a href="#idp53791296">2. ao_cmd_lex</a></span></dt><dt><span class="section"><a href="#idp53793376">3. ao_cmd_put16</a></span></dt><dt><span class="section"><a href="#idp53795216">4. ao_cmd_put8</a></span></dt><dt><span class="section"><a href="#idp53797104">5. ao_cmd_white</a></span></dt><dt><span class="section"><a href="#idp53799168">6. ao_cmd_hex</a></span></dt><dt><span class="section"><a href="#idp53801216">7. ao_cmd_decimal</a></span></dt><dt><span class="section"><a href="#idp53803312">8. ao_match_word</a></span></dt><dt><span class="section"><a href="#idp53805392">9. ao_cmd_init</a></span></dt></dl></div><p>
AltOS includes a simple command line parser which is hooked up
to the stdio interfaces permitting remote control of the device
over USB, serial or the RF link as desired. Each command uses a
single character to invoke it, the remaining characters on the
line are available as parameters to the command.
- </p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp36800672"></a>1. ao_cmd_register</h2></div></div></div><pre class="programlisting">
+ </p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp53782656"></a>1. ao_cmd_register</h2></div></div></div><pre class="programlisting">
void
ao_cmd_register(__code struct ao_cmds *cmds)
</pre><p>
@@ -656,38 +656,38 @@
The command line is invalid for some reason other
than invalid tokens.
</p></dd></dl></div><p>
- </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp35138512"></a>2. ao_cmd_lex</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp53791296"></a>2. ao_cmd_lex</h2></div></div></div><pre class="programlisting">
void
ao_cmd_lex(void);
</pre><p>
This gets the next character out of the command line
buffer and sticks it into ao_cmd_lex_c. At the end of the
line, ao_cmd_lex_c will get a newline ('\n') character.
- </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp34367392"></a>3. ao_cmd_put16</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp53793376"></a>3. ao_cmd_put16</h2></div></div></div><pre class="programlisting">
void
ao_cmd_put16(uint16_t v);
</pre><p>
Writes 'v' as four hexadecimal characters.
- </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp35043824"></a>4. ao_cmd_put8</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp53795216"></a>4. ao_cmd_put8</h2></div></div></div><pre class="programlisting">
void
ao_cmd_put8(uint8_t v);
</pre><p>
Writes 'v' as two hexadecimal characters.
- </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp35136016"></a>5. ao_cmd_white</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp53797104"></a>5. ao_cmd_white</h2></div></div></div><pre class="programlisting">
void
ao_cmd_white(void)
</pre><p>
This skips whitespace by calling ao_cmd_lex while
ao_cmd_lex_c is either a space or tab. It does not skip
any characters if ao_cmd_lex_c already non-white.
- </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp34188208"></a>6. ao_cmd_hex</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp53799168"></a>6. ao_cmd_hex</h2></div></div></div><pre class="programlisting">
void
ao_cmd_hex(void)
</pre><p>
This reads a 16-bit hexadecimal value from the command
line with optional leading whitespace. The resulting value
is stored in ao_cmd_lex_i;
- </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp36380096"></a>7. ao_cmd_decimal</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp53801216"></a>7. ao_cmd_decimal</h2></div></div></div><pre class="programlisting">
void
ao_cmd_decimal(void)
</pre><p>
@@ -695,7 +695,7 @@
line with optional leading whitespace. The resulting value
is stored in ao_cmd_lex_u32 and the low 16 bits are stored
in ao_cmd_lex_i;
- </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp36807664"></a>8. ao_match_word</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp53803312"></a>8. ao_match_word</h2></div></div></div><pre class="programlisting">
uint8_t
ao_match_word(__code char *word)
</pre><p>
@@ -703,14 +703,14 @@
line. It does not skip leading white space. If 'word' is
found, then 1 is returned. Otherwise, ao_cmd_status is set to
ao_cmd_syntax_error and 0 is returned.
- </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp36809680"></a>9. ao_cmd_init</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp53805392"></a>9. ao_cmd_init</h2></div></div></div><pre class="programlisting">
void
ao_cmd_init(void
</pre><p>
Initializes the command system, setting up the built-in
commands and adding a task to run the command processing
loop. It should be called by 'main' before ao_start_scheduler.
- </p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp36811792"></a>Chapter 10. USB target device</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp36813984">1. ao_usb_flush</a></span></dt><dt><span class="section"><a href="#idp36816016">2. ao_usb_putchar</a></span></dt><dt><span class="section"><a href="#idp36818080">3. ao_usb_pollchar</a></span></dt><dt><span class="section"><a href="#idp36820112">4. ao_usb_getchar</a></span></dt><dt><span class="section"><a href="#idp36822016">5. ao_usb_disable</a></span></dt><dt><span class="section"><a href="#idp36824736">6. ao_usb_enable</a></span></dt><dt><span class="section"><a href="#idp36826736">7. ao_usb_init</a></span></dt></dl></div><p>
+ </p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp53807616"></a>Chapter 10. USB target device</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp53809840">1. ao_usb_flush</a></span></dt><dt><span class="section"><a href="#idp53811984">2. ao_usb_putchar</a></span></dt><dt><span class="section"><a href="#idp53814160">3. ao_usb_pollchar</a></span></dt><dt><span class="section"><a href="#idp53816304">4. ao_usb_getchar</a></span></dt><dt><span class="section"><a href="#idp53818320">5. ao_usb_disable</a></span></dt><dt><span class="section"><a href="#idp53821152">6. ao_usb_enable</a></span></dt><dt><span class="section"><a href="#idp53823264">7. ao_usb_init</a></span></dt></dl></div><p>
AltOS contains a full-speed USB target device driver. It can be
programmed to offer any kind of USB target, but to simplify
interactions with a variety of operating systems, AltOS provides
@@ -724,7 +724,7 @@
interface if desired, offering control of the device over the
USB link. Alternatively, the functions can be accessed directly
to provide for USB-specific I/O.
- </p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp36813984"></a>1. ao_usb_flush</h2></div></div></div><pre class="programlisting">
+ </p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp53809840"></a>1. ao_usb_flush</h2></div></div></div><pre class="programlisting">
void
ao_usb_flush(void);
</pre><p>
@@ -732,7 +732,7 @@
to be delivered to the USB host if there is pending data,
or if the last IN packet was full to indicate to the host
that there isn't any more pending data available.
- </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp36816016"></a>2. ao_usb_putchar</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp53811984"></a>2. ao_usb_putchar</h2></div></div></div><pre class="programlisting">
void
ao_usb_putchar(char c);
</pre><p>
@@ -741,7 +741,7 @@
adds a byte to the pending IN packet for delivery to the
USB host. If the USB packet is full, this queues the 'IN'
packet for delivery.
- </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp36818080"></a>3. ao_usb_pollchar</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp53814160"></a>3. ao_usb_pollchar</h2></div></div></div><pre class="programlisting">
char
ao_usb_pollchar(void);
</pre><p>
@@ -749,13 +749,13 @@
packet received, this returns AO_READ_AGAIN. Otherwise, it
returns the next character, reporting to the host that it
is ready for more data when the last character is gone.
- </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp36820112"></a>4. ao_usb_getchar</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp53816304"></a>4. ao_usb_getchar</h2></div></div></div><pre class="programlisting">
char
ao_usb_getchar(void);
</pre><p>
This uses ao_pollchar to receive the next character,
blocking while ao_pollchar returns AO_READ_AGAIN.
- </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp36822016"></a>5. ao_usb_disable</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp53818320"></a>5. ao_usb_disable</h2></div></div></div><pre class="programlisting">
void
ao_usb_disable(void);
</pre><p>
@@ -770,7 +770,7 @@
after disabling the USB device, it's likely that the cable
will need to be disconnected and reconnected before it
will work again.
- </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp36824736"></a>6. ao_usb_enable</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp53821152"></a>6. ao_usb_enable</h2></div></div></div><pre class="programlisting">
void
ao_usb_enable(void);
</pre><p>
@@ -778,7 +778,7 @@
disabled. See the note above about needing to physically
remove and re-insert the cable to get the host to
re-initialize the USB link.
- </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp36826736"></a>7. ao_usb_init</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp53823264"></a>7. ao_usb_init</h2></div></div></div><pre class="programlisting">
void
ao_usb_init(void);
</pre><p>
@@ -786,7 +786,7 @@
the control end point and adds the usb I/O functions to
the stdio system. Call this from main before
ao_start_scheduler.
- </p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp36828848"></a>Chapter 11. Serial peripherals</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp36830832">1. ao_serial_getchar</a></span></dt><dt><span class="section"><a href="#idp36832752">2. ao_serial_putchar</a></span></dt><dt><span class="section"><a href="#idp36834656">3. ao_serial_drain</a></span></dt><dt><span class="section"><a href="#idp36836544">4. ao_serial_set_speed</a></span></dt><dt><span class="section"><a href="#idp36838512">5. ao_serial_init</a></span></dt></dl></div><p>
+ </p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp53825488"></a>Chapter 11. Serial peripherals</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp53827504">1. ao_serial_getchar</a></span></dt><dt><span class="section"><a href="#idp53829536">2. ao_serial_putchar</a></span></dt><dt><span class="section"><a href="#idp53831504">3. ao_serial_drain</a></span></dt><dt><span class="section"><a href="#idp50449072">4. ao_serial_set_speed</a></span></dt><dt><span class="section"><a href="#idp51183888">5. ao_serial_init</a></span></dt></dl></div><p>
The CC1111 provides two USART peripherals. AltOS uses one for
asynch serial data, generally to communicate with a GPS device,
and the other for a SPI bus. The UART is configured to operate
@@ -797,25 +797,25 @@
</p><p>
To prevent loss of data, AltOS provides receive and transmit
fifos of 32 characters each.
- </p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp36830832"></a>1. ao_serial_getchar</h2></div></div></div><pre class="programlisting">
+ </p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp53827504"></a>1. ao_serial_getchar</h2></div></div></div><pre class="programlisting">
char
ao_serial_getchar(void);
</pre><p>
Returns the next character from the receive fifo, blocking
until a character is received if the fifo is empty.
- </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp36832752"></a>2. ao_serial_putchar</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp53829536"></a>2. ao_serial_putchar</h2></div></div></div><pre class="programlisting">
void
ao_serial_putchar(char c);
</pre><p>
Adds a character to the transmit fifo, blocking if the
fifo is full. Starts transmitting characters.
- </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp36834656"></a>3. ao_serial_drain</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp53831504"></a>3. ao_serial_drain</h2></div></div></div><pre class="programlisting">
void
ao_serial_drain(void);
</pre><p>
Blocks until the transmit fifo is empty. Used internally
when changing serial speeds.
- </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp36836544"></a>4. ao_serial_set_speed</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp50449072"></a>4. ao_serial_set_speed</h2></div></div></div><pre class="programlisting">
void
ao_serial_set_speed(uint8_t speed);
</pre><p>
@@ -823,14 +823,14 @@
AO_SERIAL_SPEED_4800, AO_SERIAL_SPEED_9600 or
AO_SERIAL_SPEED_57600. This first flushes the transmit
fifo using ao_serial_drain.
- </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp36838512"></a>5. ao_serial_init</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp51183888"></a>5. ao_serial_init</h2></div></div></div><pre class="programlisting">
void
ao_serial_init(void)
</pre><p>
Initializes the serial peripheral. Call this from 'main'
before jumping to ao_start_scheduler. The default speed
setting is AO_SERIAL_SPEED_4800.
- </p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp36840592"></a>Chapter 12. CC1111 Radio peripheral</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp36841232">1. Radio Introduction</a></span></dt><dt><span class="section"><a href="#idp36848256">2. ao_radio_set_telemetry</a></span></dt><dt><span class="section"><a href="#idp36850352">3. ao_radio_set_packet</a></span></dt><dt><span class="section"><a href="#idp36852448">4. ao_radio_set_rdf</a></span></dt><dt><span class="section"><a href="#idp36854576">5. ao_radio_idle</a></span></dt><dt><span class="section"><a href="#idp36856512">6. ao_radio_get</a></span></dt><dt><span class="section"><a href="#idp36858432">7. ao_radio_put</a></span></dt><dt><span class="section"><a href="#idp36860208">8. ao_radio_abort</a></span></dt><dt><span class="section"><a href="#idp36862160">9. Radio Telemetry</a></span></dt><dd><dl><dt><span class="section"><a href="#idp36863424">9.1. ao_radio_send</a></span></dt><dt><span class="section"><a href="#idp36865584">9.2. ao_radio_recv</a></span></dt></dl></dd><dt><span class="section"><a href="#idp36867984">10. Radio Direction Finding</a></span></dt><dd><dl><dt><span class="section"><a href="#idp36869104">10.1. ao_radio_rdf</a></span></dt></dl></dd><dt><span class="section"><a href="#idp36871136">11. Radio Packet Mode</a></span></dt><dd><dl><dt><span class="section"><a href="#idp36872416">11.1. ao_packet_putchar</a></span></dt><dt><span class="section"><a href="#idp36874528">11.2. ao_packet_pollchar</a></span></dt><dt><span class="section"><a href="#idp36876496">11.3. ao_packet_slave_start</a></span></dt><dt><span class="section"><a href="#idp36878384">11.4. ao_packet_slave_stop</a></span></dt><dt><span class="section"><a href="#idp36880240">11.5. ao_packet_slave_init</a></span></dt><dt><span class="section"><a href="#idp36882208">11.6. ao_packet_master_init</a></span></dt></dl></dd></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp36841232"></a>1. Radio Introduction</h2></div></div></div><p>
+ </p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp51578544"></a>Chapter 12. CC1111 Radio peripheral</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp50893296">1. Radio Introduction</a></span></dt><dt><span class="section"><a href="#idp51568800">2. ao_radio_set_telemetry</a></span></dt><dt><span class="section"><a href="#idp51487072">3. ao_radio_set_packet</a></span></dt><dt><span class="section"><a href="#idp53835632">4. ao_radio_set_rdf</a></span></dt><dt><span class="section"><a href="#idp53837760">5. ao_radio_idle</a></span></dt><dt><span class="section"><a href="#idp53839696">6. ao_radio_get</a></span></dt><dt><span class="section"><a href="#idp53841616">7. ao_radio_put</a></span></dt><dt><span class="section"><a href="#idp53843392">8. ao_radio_abort</a></span></dt><dt><span class="section"><a href="#idp53845344">9. Radio Telemetry</a></span></dt><dd><dl><dt><span class="section"><a href="#idp53846608">9.1. ao_radio_send</a></span></dt><dt><span class="section"><a href="#idp53848768">9.2. ao_radio_recv</a></span></dt></dl></dd><dt><span class="section"><a href="#idp53851168">10. Radio Direction Finding</a></span></dt><dd><dl><dt><span class="section"><a href="#idp53852288">10.1. ao_radio_rdf</a></span></dt></dl></dd><dt><span class="section"><a href="#idp53854320">11. Radio Packet Mode</a></span></dt><dd><dl><dt><span class="section"><a href="#idp53855600">11.1. ao_packet_putchar</a></span></dt><dt><span class="section"><a href="#idp53857712">11.2. ao_packet_pollchar</a></span></dt><dt><span class="section"><a href="#idp53859680">11.3. ao_packet_slave_start</a></span></dt><dt><span class="section"><a href="#idp53861568">11.4. ao_packet_slave_stop</a></span></dt><dt><span class="section"><a href="#idp53863424">11.5. ao_packet_slave_init</a></span></dt><dt><span class="section"><a href="#idp53865392">11.6. ao_packet_master_init</a></span></dt></dl></dd></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp50893296"></a>1. Radio Introduction</h2></div></div></div><p>
The CC1111 radio transceiver sends and receives digital packets
with forward error correction and detection. The AltOS driver is
fairly specific to the needs of the TeleMetrum and TeleDongle
@@ -868,7 +868,7 @@
receiver. This is designed to provide a beacon to track
the device when other location mechanisms fail.
</p></li></ol></div><p>
- </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp36848256"></a>2. ao_radio_set_telemetry</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp51568800"></a>2. ao_radio_set_telemetry</h2></div></div></div><pre class="programlisting">
void
ao_radio_set_telemetry(void);
</pre><p>
@@ -877,7 +877,7 @@
other RF parameters. It does not include the base frequency
or channel though. Those are set at the time of transmission
or reception, in case the values are changed by the user.
- </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp36850352"></a>3. ao_radio_set_packet</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp51487072"></a>3. ao_radio_set_packet</h2></div></div></div><pre class="programlisting">
void
ao_radio_set_packet(void);
</pre><p>
@@ -886,7 +886,7 @@
parameters. It does not include the base frequency or
channel though. Those are set at the time of transmission or
reception, in case the values are changed by the user.
- </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp36852448"></a>4. ao_radio_set_rdf</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp53835632"></a>4. ao_radio_set_rdf</h2></div></div></div><pre class="programlisting">
void
ao_radio_set_rdf(void);
</pre><p>
@@ -896,38 +896,38 @@
and data whitening logic is turned off so that the resulting
modulation is received as a 1kHz tone by a conventional 70cm
FM audio receiver.
- </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp36854576"></a>5. ao_radio_idle</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp53837760"></a>5. ao_radio_idle</h2></div></div></div><pre class="programlisting">
void
ao_radio_idle(void);
</pre><p>
Sets the radio device to idle mode, waiting until it reaches
that state. This will terminate any in-progress transmit or
receive operation.
- </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp36856512"></a>6. ao_radio_get</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp53839696"></a>6. ao_radio_get</h2></div></div></div><pre class="programlisting">
void
ao_radio_get(void);
</pre><p>
Acquires the radio mutex and then configures the radio
frequency using the global radio calibration and channel
values.
- </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp36858432"></a>7. ao_radio_put</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp53841616"></a>7. ao_radio_put</h2></div></div></div><pre class="programlisting">
void
ao_radio_put(void);
</pre><p>
Releases the radio mutex.
- </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp36860208"></a>8. ao_radio_abort</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp53843392"></a>8. ao_radio_abort</h2></div></div></div><pre class="programlisting">
void
ao_radio_abort(void);
</pre><p>
Aborts any transmission or reception process by aborting the
associated DMA object and calling ao_radio_idle to terminate
the radio operation.
- </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp36862160"></a>9. Radio Telemetry</h2></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp53845344"></a>9. Radio Telemetry</h2></div></div></div><p>
In telemetry mode, you can send or receive a telemetry
packet. The data from receiving a packet also includes the RSSI
and status values supplied by the receiver. These are added
after the telemetry data.
- </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp36863424"></a>9.1. ao_radio_send</h3></div></div></div><pre class="programlisting">
+ </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp53846608"></a>9.1. ao_radio_send</h3></div></div></div><pre class="programlisting">
void
ao_radio_send(__xdata struct ao_telemetry *telemetry);
</pre><p>
@@ -936,7 +936,7 @@
telemetry mode. This function calls ao_radio_get() before
sending, and ao_radio_put() afterwards, to correctly
serialize access to the radio device.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp36865584"></a>9.2. ao_radio_recv</h3></div></div></div><pre class="programlisting">
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp53848768"></a>9.2. ao_radio_recv</h3></div></div></div><pre class="programlisting">
void
ao_radio_recv(__xdata struct ao_radio_recv *radio);
</pre><p>
@@ -947,21 +947,21 @@
to the radio device. This returns non-zero if a packet was
received, or zero if the operation was aborted (from some
other task calling ao_radio_abort()).
- </p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp36867984"></a>10. Radio Direction Finding</h2></div></div></div><p>
+ </p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp53851168"></a>10. Radio Direction Finding</h2></div></div></div><p>
In radio direction finding mode, there's just one function to
use
- </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp36869104"></a>10.1. ao_radio_rdf</h3></div></div></div><pre class="programlisting">
+ </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp53852288"></a>10.1. ao_radio_rdf</h3></div></div></div><pre class="programlisting">
void
ao_radio_rdf(int ms);
</pre><p>
This sends an RDF packet lasting for the specified amount
of time. The maximum length is 1020 ms.
- </p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp36871136"></a>11. Radio Packet Mode</h2></div></div></div><p>
+ </p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp53854320"></a>11. Radio Packet Mode</h2></div></div></div><p>
Packet mode is asymmetrical and is configured at compile time
for either master or slave mode (but not both). The basic I/O
functions look the same at both ends, but the internals are
different, along with the initialization steps.
- </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp36872416"></a>11.1. ao_packet_putchar</h3></div></div></div><pre class="programlisting">
+ </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp53855600"></a>11.1. ao_packet_putchar</h3></div></div></div><pre class="programlisting">
void
ao_packet_putchar(char c);
</pre><p>
@@ -971,32 +971,32 @@
transmit a packet if the output buffer is full. On the
slave side, any pending data will be sent the next time
the master polls for data.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp36874528"></a>11.2. ao_packet_pollchar</h3></div></div></div><pre class="programlisting">
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp53857712"></a>11.2. ao_packet_pollchar</h3></div></div></div><pre class="programlisting">
char
ao_packet_pollchar(void);
</pre><p>
This returns a pending input character if available,
otherwise returns AO_READ_AGAIN. On the master side, if
this empties the buffer, it triggers a poll for more data.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp36876496"></a>11.3. ao_packet_slave_start</h3></div></div></div><pre class="programlisting">
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp53859680"></a>11.3. ao_packet_slave_start</h3></div></div></div><pre class="programlisting">
void
ao_packet_slave_start(void);
</pre><p>
This is available only on the slave side and starts a task
to listen for packet data.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp36878384"></a>11.4. ao_packet_slave_stop</h3></div></div></div><pre class="programlisting">
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp53861568"></a>11.4. ao_packet_slave_stop</h3></div></div></div><pre class="programlisting">
void
ao_packet_slave_stop(void);
</pre><p>
Disables the packet slave task, stopping the radio receiver.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp36880240"></a>11.5. ao_packet_slave_init</h3></div></div></div><pre class="programlisting">
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp53863424"></a>11.5. ao_packet_slave_init</h3></div></div></div><pre class="programlisting">
void
ao_packet_slave_init(void);
</pre><p>
Adds the packet stdio functions to the stdio package so
that when packet slave mode is enabled, characters will
get send and received through the stdio functions.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp36882208"></a>11.6. ao_packet_master_init</h3></div></div></div><pre class="programlisting">
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp53865392"></a>11.6. ao_packet_master_init</h3></div></div></div><pre class="programlisting">
void
ao_packet_master_init(void);
</pre><p>
diff --git a/AltOS/doc/altos.pdf b/AltOS/doc/altos.pdf
index 08c5344..e2d4aed 100644
--- a/AltOS/doc/altos.pdf
+++ b/AltOS/doc/altos.pdf
Binary files differ
diff --git a/AltOS/doc/altusmetrum.html b/AltOS/doc/altusmetrum.html
index 47b4882..f104894 100644
--- a/AltOS/doc/altusmetrum.html
+++ b/AltOS/doc/altusmetrum.html
@@ -1,10 +1,12 @@
-<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="idp12496880"></a>The Altus Metrum System</h1></div><div><h2 class="subtitle">An Owner's Manual for Altus Metrum Rocketry Electronics</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Bdale</span> <span class="surname">Garbee</span></h3></div></div><div><div class="author"><h3 class="author"><span class="firstname">Keith</span> <span class="surname">Packard</span></h3></div></div><div><div class="author"><h3 class="author"><span class="firstname">Bob</span> <span class="surname">Finch</span></h3></div></div><div><div class="author"><h3 class="author"><span class="firstname">Anthony</span> <span class="surname">Towns</span></h3></div></div><div><p class="copyright">Copyright © 2014 Bdale Garbee and Keith Packard</p></div><div><div class="legalnotice"><a name="idp38841440"></a><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>The Altus Metrum System</title><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="book"><div class="titlepage"><div><div><h1 class="title"><a name="idp16901520"></a>The Altus Metrum System</h1></div><div><h2 class="subtitle">An Owner's Manual for Altus Metrum Rocketry Electronics</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Bdale</span> <span class="surname">Garbee</span></h3></div></div><div><div class="author"><h3 class="author"><span class="firstname">Keith</span> <span class="surname">Packard</span></h3></div></div><div><div class="author"><h3 class="author"><span class="firstname">Bob</span> <span class="surname">Finch</span></h3></div></div><div><div class="author"><h3 class="author"><span class="firstname">Anthony</span> <span class="surname">Towns</span></h3></div></div><div><p class="copyright">Copyright © 2014 Bdale Garbee and Keith Packard</p></div><div><div class="legalnotice"><a name="idp43234368"></a><p>
This document is released under the terms of the
<a class="ulink" href="http://creativecommons.org/licenses/by-sa/3.0/" target="_top">
Creative Commons ShareAlike 3.0
</a>
license.
- </p></div></div><div><div class="revhistory"><table style="border-style:solid; width:100%;" summary="Revision History"><tr><th align="left" valign="top" colspan="2"><b>Revision History</b></th></tr><tr><td align="left">Revision 1.4.1</td><td align="left">24 June 2014</td></tr><tr><td align="left" colspan="2">
+ </p></div></div><div><div class="revhistory"><table style="border-style:solid; width:100%;" summary="Revision History"><tr><th align="left" valign="top" colspan="2"><b>Revision History</b></th></tr><tr><td align="left">Revision 1.5</td><td align="left">6 September 2014</td></tr><tr><td align="left" colspan="2">
+ Major release adding EasyMega support.
+ </td></tr><tr><td align="left">Revision 1.4.1</td><td align="left">20 June 2014</td></tr><tr><td align="left" colspan="2">
Minor release fixing some installation bugs.
</td></tr><tr><td align="left">Revision 1.4</td><td align="left">15 June 2014</td></tr><tr><td align="left" colspan="2">
Major release adding TeleGPS support.
@@ -39,7 +41,7 @@
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="idp43519856"></a>Acknowledgments</h1></div></div></div><p>
+ </td></tr><tr><td align="left">Revision 0.8</td><td align="left">24 November 2010</td></tr><tr><td align="left" colspan="2">Updated for software version 0.8 </td></tr></table></div></div></div><hr></div><div class="dedication"><div class="titlepage"><div><div><h1 class="title"><a name="idp43407920"></a>Acknowledgments</h1></div></div></div><p>
Thanks to Bob Finch, W9YA, NAR 12965, TRA 12350 for writing &#8220;The
Mere-Mortals Quick Start/Usage Guide to the Altus Metrum Starter
Kit&#8221; which formed the basis of the original Getting Started chapter
@@ -62,19 +64,21 @@ NAR #87103, TRA #12201<br>
Keith Packard, KD7SQG<br>
NAR #88757, TRA #12200<br>
      </p></div><p>
- </p></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="chapter"><a href="#idp43524064">1. Introduction and Overview</a></span></dt><dt><span class="chapter"><a href="#idp43531824">2. Getting Started</a></span></dt><dt><span class="chapter"><a href="#idp38854464">3. Handling Precautions</a></span></dt><dt><span class="chapter"><a href="#idp38859952">4. Altus Metrum Hardware</a></span></dt><dd><dl><dt><span class="section"><a href="#idp38860624">1. General Usage Instructions</a></span></dt><dd><dl><dt><span class="section"><a href="#idp38862592">1.1. Hooking Up Lithium Polymer Batteries</a></span></dt><dt><span class="section"><a href="#idp42276480">1.2. Hooking Up Pyro Charges</a></span></dt><dt><span class="section"><a href="#idp42591936">1.3. Hooking Up a Power Switch</a></span></dt><dt><span class="section"><a href="#idp40956544">1.4. Using a Separate Pyro Battery</a></span></dt><dt><span class="section"><a href="#idp40258464">1.5. Using a Different Kind of Battery</a></span></dt></dl></dd><dt><span class="section"><a href="#idp43170688">2. Specifications</a></span></dt><dt><span class="section"><a href="#idp44431104">3. TeleMetrum</a></span></dt><dd><dl><dt><span class="section"><a href="#idp44436000">3.1. TeleMetrum Screw Terminals</a></span></dt><dt><span class="section"><a href="#idp44455216">3.2. Using a Separate Pyro Battery with TeleMetrum</a></span></dt><dt><span class="section"><a href="#idp44458464">3.3. Using an Active Switch with TeleMetrum</a></span></dt></dl></dd><dt><span class="section"><a href="#idp44460592">4. TeleMini v1.0</a></span></dt><dd><dl><dt><span class="section"><a href="#idp44465488">4.1. TeleMini v1.0 Screw Terminals</a></span></dt><dt><span class="section"><a href="#idp44484832">4.2. Using a Separate Pyro Battery with TeleMini v1.0</a></span></dt><dt><span class="section"><a href="#idp44488208">4.3. Using an Active Switch with TeleMini v1.0</a></span></dt></dl></dd><dt><span class="section"><a href="#idp44490416">5. TeleMini v2.0</a></span></dt><dd><dl><dt><span class="section"><a href="#idp44494432">5.1. TeleMini v2.0 Screw Terminals</a></span></dt><dt><span class="section"><a href="#idp44516816">5.2. Using a Separate Pyro Battery with TeleMini v2.0</a></span></dt><dt><span class="section"><a href="#idp44520016">5.3. Using an Active Switch with TeleMini v2.0</a></span></dt></dl></dd><dt><span class="section"><a href="#idp44522112">6. EasyMini</a></span></dt><dd><dl><dt><span class="section"><a href="#idp44525968">6.1. EasyMini Screw Terminals</a></span></dt><dt><span class="section"><a href="#idp44548352">6.2. Using a Separate Pyro Battery with EasyMini</a></span></dt><dt><span class="section"><a href="#idp44551536">6.3. Using an Active Switch with EasyMini</a></span></dt></dl></dd><dt><span class="section"><a href="#idp44553632">7. TeleMega</a></span></dt><dd><dl><dt><span class="section"><a href="#idp44557600">7.1. TeleMega Screw Terminals</a></span></dt><dt><span class="section"><a href="#idp44595104">7.2. Using a Separate Pyro Battery with TeleMega</a></span></dt><dt><span class="section"><a href="#idp44596704">7.3. Using Only One Battery With TeleMega</a></span></dt><dt><span class="section"><a href="#idp44598624">7.4. Using an Active Switch with TeleMega</a></span></dt></dl></dd><dt><span class="section"><a href="#idp44600672">8. Flight Data Recording</a></span></dt><dt><span class="section"><a href="#idp44629504">9. Installation</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp44636240">5. System Operation</a></span></dt><dd><dl><dt><span class="section"><a href="#idp44636880">1. Firmware Modes </a></span></dt><dt><span class="section"><a href="#idp44705168">2. GPS </a></span></dt><dt><span class="section"><a href="#idp44707952">3. Controlling An Altimeter Over The Radio Link</a></span></dt><dt><span class="section"><a href="#idp44719248">4. Ground Testing </a></span></dt><dt><span class="section"><a href="#idp44722000">5. Radio Link </a></span></dt><dt><span class="section"><a href="#idp44726000">6. APRS</a></span></dt><dt><span class="section"><a href="#idp44747968">7. Configurable Parameters</a></span></dt><dd><dl><dt><span class="section"><a href="#idp44749888">7.1. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp44751936">7.2. Callsign</a></span></dt><dt><span class="section"><a href="#idp44753472">7.3. Telemetry/RDF/APRS Enable</a></span></dt><dt><span class="section"><a href="#idp44754768">7.4. APRS Interval</a></span></dt><dt><span class="section"><a href="#idp44756240">7.5. Apogee Delay</a></span></dt><dt><span class="section"><a href="#idp44758832">7.6. Apogee Lockout</a></span></dt><dt><span class="section"><a href="#idp44760560">7.7. Main Deployment Altitude</a></span></dt><dt><span class="section"><a href="#idp44762256">7.8. Maximum Flight Log</a></span></dt><dt><span class="section"><a href="#idp44764400">7.9. Ignite Mode</a></span></dt><dt><span class="section"><a href="#idp44766512">7.10. Pad Orientation</a></span></dt><dt><span class="section"><a href="#idp44768208">7.11. Configurable Pyro Channels</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#idp44790592">6. AltosUI</a></span></dt><dd><dl><dt><span class="section"><a href="#idp44794208">1. Monitor Flight</a></span></dt><dd><dl><dt><span class="section"><a href="#idp44806928">1.1. Launch Pad</a></span></dt><dt><span class="section"><a href="#idp44823216">1.2. Ascent</a></span></dt><dt><span class="section"><a href="#idp44828672">1.3. Descent</a></span></dt><dt><span class="section"><a href="#idp44835536">1.4. Landed</a></span></dt><dt><span class="section"><a href="#idp44841968">1.5. Table</a></span></dt><dt><span class="section"><a href="#idp44845552">1.6. Site Map</a></span></dt><dt><span class="section"><a href="#idp44852272">1.7. Ignitor</a></span></dt></dl></dd><dt><span class="section"><a href="#idp44856048">2. Save Flight Data</a></span></dt><dt><span class="section"><a href="#idp44860000">3. Replay Flight</a></span></dt><dt><span class="section"><a href="#idp44862032">4. Graph Data</a></span></dt><dd><dl><dt><span class="section"><a href="#idp44864416">4.1. Flight Graph</a></span></dt><dt><span class="section"><a href="#idp44868864">4.2. Configure Graph</a></span></dt><dt><span class="section"><a href="#idp44872528">4.3. Flight Statistics</a></span></dt><dt><span class="section"><a href="#idp44876048">4.4. Map</a></span></dt></dl></dd><dt><span class="section"><a href="#idp44879904">5. Export Data</a></span></dt><dd><dl><dt><span class="section"><a href="#idp44881472">5.1. Comma Separated Value Format</a></span></dt><dt><span class="section"><a href="#idp44883824">5.2. Keyhole Markup Language (for Google Earth)</a></span></dt></dl></dd><dt><span class="section"><a href="#idp44885312">6. Configure Altimeter</a></span></dt><dd><dl><dt><span class="section"><a href="#idp44897616">6.1. Main Deploy Altitude</a></span></dt><dt><span class="section"><a href="#idp44899184">6.2. Apogee Delay</a></span></dt><dt><span class="section"><a href="#idp44900800">6.3. Apogee Lockoug</a></span></dt><dt><span class="section"><a href="#idp44902528">6.4. Frequency</a></span></dt><dt><span class="section"><a href="#idp44904032">6.5. RF Calibration</a></span></dt><dt><span class="section"><a href="#idp44905680">6.6. Telemetry/RDF/APRS Enable</a></span></dt><dt><span class="section"><a href="#idp44906976">6.7. APRS Interval</a></span></dt><dt><span class="section"><a href="#idp44908544">6.8. Callsign</a></span></dt><dt><span class="section"><a href="#idp44909856">6.9. Maximum Flight Log Size</a></span></dt><dt><span class="section"><a href="#idp44911296">6.10. Ignitor Firing Mode</a></span></dt><dt><span class="section"><a href="#idp44918208">6.11. Pad Orientation</a></span></dt><dt><span class="section"><a href="#idp44923424">6.12. Beeper Frequency</a></span></dt><dt><span class="section"><a href="#idp44924880">6.13. Configure Pyro Channels</a></span></dt></dl></dd><dt><span class="section"><a href="#idp44931248">7. Configure AltosUI</a></span></dt><dd><dl><dt><span class="section"><a href="#idp44934752">7.1. Voice Settings</a></span></dt><dt><span class="section"><a href="#idp44939776">7.2. Log Directory</a></span></dt><dt><span class="section"><a href="#idp44941776">7.3. Callsign</a></span></dt><dt><span class="section"><a href="#idp44944400">7.4. Imperial Units</a></span></dt><dt><span class="section"><a href="#idp44945904">7.5. Font Size</a></span></dt><dt><span class="section"><a href="#idp44947184">7.6. Serial Debug</a></span></dt><dt><span class="section"><a href="#idp44948688">7.7. Manage Frequencies</a></span></dt></dl></dd><dt><span class="section"><a href="#idp44950320">8. Configure Groundstation</a></span></dt><dd><dl><dt><span class="section"><a href="#idp44961440">8.1. Frequency</a></span></dt><dt><span class="section"><a href="#idp44963008">8.2. Radio Calibration</a></span></dt></dl></dd><dt><span class="section"><a href="#idp44964640">9. Flash Image</a></span></dt><dt><span class="section"><a href="#idp44966272">10. Fire Igniter</a></span></dt><dt><span class="section"><a href="#idp44971904">11. Scan Channels</a></span></dt><dt><span class="section"><a href="#idp44975760">12. Load Maps</a></span></dt><dt><span class="section"><a href="#idp44989568">13. Monitor Idle</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp44991664">7. AltosDroid</a></span></dt><dd><dl><dt><span class="section"><a href="#idp44994048">1. Installing AltosDroid</a></span></dt><dt><span class="section"><a href="#idp44995984">2. Connecting to TeleBT</a></span></dt><dt><span class="section"><a href="#idp44997984">3. Configuring AltosDroid</a></span></dt><dt><span class="section"><a href="#idp44999440">4. AltosDroid Flight Monitoring</a></span></dt><dd><dl><dt><span class="section"><a href="#idp45000752">4.1. Pad</a></span></dt></dl></dd><dt><span class="section"><a href="#idp45014304">5. Downloading Flight Logs</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp45015968">8. Using Altus Metrum Products</a></span></dt><dd><dl><dt><span class="section"><a href="#idp45016608">1. Being Legal</a></span></dt><dt><span class="section"><a href="#idp45018512">2. In the Rocket</a></span></dt><dt><span class="section"><a href="#idp45020976">3. On the Ground</a></span></dt><dt><span class="section"><a href="#idp45034288">4. Data Analysis</a></span></dt><dt><span class="section"><a href="#idp45036832">5. Future Plans</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp45041568">9. Altimeter Installation Recommendations</a></span></dt><dd><dl><dt><span class="section"><a href="#idp45043024">1. Mounting the Altimeter</a></span></dt><dt><span class="section"><a href="#idp45047856">2. Dealing with the Antenna</a></span></dt><dt><span class="section"><a href="#idp45053952">3. Preserving GPS Reception</a></span></dt><dt><span class="section"><a href="#idp45058736">4. Radio Frequency Interference</a></span></dt><dt><span class="section"><a href="#idp45066304">5. The Barometric Sensor</a></span></dt><dt><span class="section"><a href="#idp45069456">6. Ground Testing</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp45072624">10. Updating Device Firmware</a></span></dt><dd><dl><dt><span class="section"><a href="#idp45076640">1.
- Updating TeleMega, TeleMetrum v2 or EasyMini Firmware
- </a></span></dt><dd><dl><dt><span class="section"><a href="#idp45085696">1.1. Recovering From Self-Flashing Failure</a></span></dt></dl></dd><dt><span class="section"><a href="#idp45094672">2. Pair Programming</a></span></dt><dt><span class="section"><a href="#idp45096112">3. Updating TeleMetrum v1.x Firmware</a></span></dt><dt><span class="section"><a href="#idp45109648">4. Updating TeleMini Firmware</a></span></dt><dt><span class="section"><a href="#idp45123200">5. Updating TeleDongle Firmware</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp45139824">11. Hardware Specifications</a></span></dt><dd><dl><dt><span class="section"><a href="#idp45140464">1.
+ </p></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="chapter"><a href="#idp43412128">1. Introduction and Overview</a></span></dt><dt><span class="chapter"><a href="#idp43239632">2. Getting Started</a></span></dt><dt><span class="chapter"><a href="#idp43249600">3. Handling Precautions</a></span></dt><dt><span class="chapter"><a href="#idp43255088">4. Altus Metrum Hardware</a></span></dt><dd><dl><dt><span class="section"><a href="#idp43255760">1. General Usage Instructions</a></span></dt><dd><dl><dt><span class="section"><a href="#idp43257728">1.1. Hooking Up Lithium Polymer Batteries</a></span></dt><dt><span class="section"><a href="#idp43260736">1.2. Hooking Up Pyro Charges</a></span></dt><dt><span class="section"><a href="#idp43262816">1.3. Hooking Up a Power Switch</a></span></dt><dt><span class="section"><a href="#idp43266032">1.4. Using a Separate Pyro Battery</a></span></dt><dt><span class="section"><a href="#idp43268544">1.5. Using a Different Kind of Battery</a></span></dt></dl></dd><dt><span class="section"><a href="#idp43270288">2. Specifications</a></span></dt><dt><span class="section"><a href="#idp48828432">3. TeleMetrum</a></span></dt><dd><dl><dt><span class="section"><a href="#idp48831824">3.1. TeleMetrum Screw Terminals</a></span></dt><dt><span class="section"><a href="#idp48861136">3.2. Using a Separate Pyro Battery with TeleMetrum</a></span></dt><dt><span class="section"><a href="#idp48864384">3.3. Using an Active Switch with TeleMetrum</a></span></dt></dl></dd><dt><span class="section"><a href="#idp48866512">4. TeleMini v1.0</a></span></dt><dd><dl><dt><span class="section"><a href="#idp48871408">4.1. TeleMini v1.0 Screw Terminals</a></span></dt><dt><span class="section"><a href="#idp48890752">4.2. Using a Separate Pyro Battery with TeleMini v1.0</a></span></dt><dt><span class="section"><a href="#idp48894128">4.3. Using an Active Switch with TeleMini v1.0</a></span></dt></dl></dd><dt><span class="section"><a href="#idp48896336">5. TeleMini v2.0</a></span></dt><dd><dl><dt><span class="section"><a href="#idp48900352">5.1. TeleMini v2.0 Screw Terminals</a></span></dt><dt><span class="section"><a href="#idp48922736">5.2. Using a Separate Pyro Battery with TeleMini v2.0</a></span></dt><dt><span class="section"><a href="#idp48925936">5.3. Using an Active Switch with TeleMini v2.0</a></span></dt></dl></dd><dt><span class="section"><a href="#idp48928032">6. EasyMini</a></span></dt><dd><dl><dt><span class="section"><a href="#idp48931888">6.1. EasyMini Screw Terminals</a></span></dt><dt><span class="section"><a href="#idp48954272">6.2. Using a Separate Pyro Battery with EasyMini</a></span></dt><dt><span class="section"><a href="#idp48957456">6.3. Using an Active Switch with EasyMini</a></span></dt></dl></dd><dt><span class="section"><a href="#idp48959552">7. TeleMega</a></span></dt><dd><dl><dt><span class="section"><a href="#idp48963520">7.1. TeleMega Screw Terminals</a></span></dt><dt><span class="section"><a href="#idp49001024">7.2. Using a Separate Pyro Battery with TeleMega</a></span></dt><dt><span class="section"><a href="#idp49002624">7.3. Using Only One Battery With TeleMega</a></span></dt><dt><span class="section"><a href="#idp49004544">7.4. Using an Active Switch with TeleMega</a></span></dt></dl></dd><dt><span class="section"><a href="#idp49006592">8. EasyMega</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49010560">8.1. EasyMega Screw Terminals</a></span></dt><dt><span class="section"><a href="#idp49048064">8.2. Using a Separate Pyro Battery with EasyMega</a></span></dt><dt><span class="section"><a href="#idp49049664">8.3. Using Only One Battery With EasyMega</a></span></dt><dt><span class="section"><a href="#idp49051584">8.4. Using an Active Switch with EasyMega</a></span></dt></dl></dd><dt><span class="section"><a href="#idp49053632">9. Flight Data Recording</a></span></dt><dt><span class="section"><a href="#idp49084400">10. Installation</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp49091680">5. System Operation</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49092320">1. Firmware Modes </a></span></dt><dt><span class="section"><a href="#idp49160720">2. GPS </a></span></dt><dt><span class="section"><a href="#idp49163504">3. Controlling An Altimeter Over The Radio Link</a></span></dt><dt><span class="section"><a href="#idp49174800">4. Ground Testing </a></span></dt><dt><span class="section"><a href="#idp49177552">5. Radio Link </a></span></dt><dt><span class="section"><a href="#idp49181552">6. APRS</a></span></dt><dt><span class="section"><a href="#idp49205872">7. Configurable Parameters</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49207792">7.1. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp49209840">7.2. Callsign</a></span></dt><dt><span class="section"><a href="#idp49211376">7.3. Telemetry/RDF/APRS Enable</a></span></dt><dt><span class="section"><a href="#idp49212672">7.4. Telemetry baud rate</a></span></dt><dt><span class="section"><a href="#idp49214240">7.5. APRS Interval</a></span></dt><dt><span class="section"><a href="#idp49215712">7.6. APRS SSID</a></span></dt><dt><span class="section"><a href="#idp49217056">7.7. Apogee Delay</a></span></dt><dt><span class="section"><a href="#idp49219648">7.8. Apogee Lockout</a></span></dt><dt><span class="section"><a href="#idp49221376">7.9. Main Deployment Altitude</a></span></dt><dt><span class="section"><a href="#idp49223072">7.10. Maximum Flight Log</a></span></dt><dt><span class="section"><a href="#idp49225216">7.11. Ignite Mode</a></span></dt><dt><span class="section"><a href="#idp49227328">7.12. Pad Orientation</a></span></dt><dt><span class="section"><a href="#idp49229568">7.13. Configurable Pyro Channels</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#idp49252176">6. AltosUI</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49255792">1. Monitor Flight</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49268512">1.1. Launch Pad</a></span></dt><dt><span class="section"><a href="#idp49284800">1.2. Ascent</a></span></dt><dt><span class="section"><a href="#idp49290256">1.3. Descent</a></span></dt><dt><span class="section"><a href="#idp49297120">1.4. Landed</a></span></dt><dt><span class="section"><a href="#idp49303552">1.5. Table</a></span></dt><dt><span class="section"><a href="#idp49307136">1.6. Site Map</a></span></dt><dt><span class="section"><a href="#idp49313856">1.7. Ignitor</a></span></dt></dl></dd><dt><span class="section"><a href="#idp49317632">2. Save Flight Data</a></span></dt><dt><span class="section"><a href="#idp49321584">3. Replay Flight</a></span></dt><dt><span class="section"><a href="#idp49323616">4. Graph Data</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49326000">4.1. Flight Graph</a></span></dt><dt><span class="section"><a href="#idp49330448">4.2. Configure Graph</a></span></dt><dt><span class="section"><a href="#idp49334112">4.3. Flight Statistics</a></span></dt><dt><span class="section"><a href="#idp49337632">4.4. Map</a></span></dt></dl></dd><dt><span class="section"><a href="#idp49341488">5. Export Data</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49343056">5.1. Comma Separated Value Format</a></span></dt><dt><span class="section"><a href="#idp49345408">5.2. Keyhole Markup Language (for Google Earth)</a></span></dt></dl></dd><dt><span class="section"><a href="#idp49346896">6. Configure Altimeter</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49359200">6.1. Main Deploy Altitude</a></span></dt><dt><span class="section"><a href="#idp49360768">6.2. Apogee Delay</a></span></dt><dt><span class="section"><a href="#idp49362384">6.3. Apogee Lockoug</a></span></dt><dt><span class="section"><a href="#idp49364112">6.4. Frequency</a></span></dt><dt><span class="section"><a href="#idp49365616">6.5. RF Calibration</a></span></dt><dt><span class="section"><a href="#idp49367264">6.6. Telemetry/RDF/APRS Enable</a></span></dt><dt><span class="section"><a href="#idp49368560">6.7. Telemetry baud rate</a></span></dt><dt><span class="section"><a href="#idp49370128">6.8. APRS Interval</a></span></dt><dt><span class="section"><a href="#idp49371696">6.9. APRS SSID</a></span></dt><dt><span class="section"><a href="#idp49373024">6.10. Callsign</a></span></dt><dt><span class="section"><a href="#idp49374336">6.11. Maximum Flight Log Size</a></span></dt><dt><span class="section"><a href="#idp49375776">6.12. Ignitor Firing Mode</a></span></dt><dt><span class="section"><a href="#idp49382688">6.13. Pad Orientation</a></span></dt><dt><span class="section"><a href="#idp49387920">6.14. Beeper Frequency</a></span></dt><dt><span class="section"><a href="#idp49389376">6.15. Configure Pyro Channels</a></span></dt></dl></dd><dt><span class="section"><a href="#idp49395760">7. Configure AltosUI</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49399264">7.1. Voice Settings</a></span></dt><dt><span class="section"><a href="#idp49404288">7.2. Log Directory</a></span></dt><dt><span class="section"><a href="#idp49406288">7.3. Callsign</a></span></dt><dt><span class="section"><a href="#idp49408528">7.4. Imperial Units</a></span></dt><dt><span class="section"><a href="#idp49410032">7.5. Font Size</a></span></dt><dt><span class="section"><a href="#idp49411312">7.6. Serial Debug</a></span></dt><dt><span class="section"><a href="#idp49412816">7.7. Manage Frequencies</a></span></dt></dl></dd><dt><span class="section"><a href="#idp49414448">8. Configure Groundstation</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49425568">8.1. Frequency</a></span></dt><dt><span class="section"><a href="#idp49427136">8.2. RF Calibration</a></span></dt><dt><span class="section"><a href="#idp49428656">8.3. Telemetry Rate</a></span></dt></dl></dd><dt><span class="section"><a href="#idp49430128">9. Flash Image</a></span></dt><dt><span class="section"><a href="#idp49431776">10. Fire Igniter</a></span></dt><dt><span class="section"><a href="#idp49437408">11. Scan Channels</a></span></dt><dt><span class="section"><a href="#idp49441632">12. Load Maps</a></span></dt><dt><span class="section"><a href="#idp49455600">13. Monitor Idle</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp49457696">7. AltosDroid</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49460080">1. Installing AltosDroid</a></span></dt><dt><span class="section"><a href="#idp49462016">2. Connecting to TeleBT</a></span></dt><dt><span class="section"><a href="#idp49464016">3. Configuring AltosDroid</a></span></dt><dt><span class="section"><a href="#idp49465472">4. AltosDroid Flight Monitoring</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49466784">4.1. Pad</a></span></dt></dl></dd><dt><span class="section"><a href="#idp49480336">5. Downloading Flight Logs</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp49482000">8. Using Altus Metrum Products</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49482640">1. Being Legal</a></span></dt><dt><span class="section"><a href="#idp49484544">2. In the Rocket</a></span></dt><dt><span class="section"><a href="#idp49487072">3. On the Ground</a></span></dt><dt><span class="section"><a href="#idp49500464">4. Data Analysis</a></span></dt><dt><span class="section"><a href="#idp49503008">5. Future Plans</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp49506848">9. Altimeter Installation Recommendations</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49508304">1. Mounting the Altimeter</a></span></dt><dt><span class="section"><a href="#idp49513136">2. Dealing with the Antenna</a></span></dt><dt><span class="section"><a href="#idp49518704">3. Preserving GPS Reception</a></span></dt><dt><span class="section"><a href="#idp49523488">4. Radio Frequency Interference</a></span></dt><dt><span class="section"><a href="#idp49531056">5. The Barometric Sensor</a></span></dt><dt><span class="section"><a href="#idp49533856">6. Ground Testing</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp49537024">10. Updating Device Firmware</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49541072">1.
+ Updating TeleMega, TeleMetrum v2, EasyMega or EasyMini Firmware
+ </a></span></dt><dd><dl><dt><span class="section"><a href="#idp49550144">1.1. Recovering From Self-Flashing Failure</a></span></dt></dl></dd><dt><span class="section"><a href="#idp49568720">2. Pair Programming</a></span></dt><dt><span class="section"><a href="#idp49570160">3. Updating TeleMetrum v1.x Firmware</a></span></dt><dt><span class="section"><a href="#idp49583360">4. Updating TeleMini Firmware</a></span></dt><dt><span class="section"><a href="#idp49596912">5. Updating TeleDongle Firmware</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp49613536">11. Hardware Specifications</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49614176">1.
TeleMega Specifications
- </a></span></dt><dt><span class="section"><a href="#idp45151936">2.
+ </a></span></dt><dt><span class="section"><a href="#idp49625648">2.
+ EasyMega Specifications
+ </a></span></dt><dt><span class="section"><a href="#idp49635392">3.
TeleMetrum v2 Specifications
- </a></span></dt><dt><span class="section"><a href="#idp45162496">3. TeleMetrum v1 Specifications</a></span></dt><dt><span class="section"><a href="#idp45173056">4.
+ </a></span></dt><dt><span class="section"><a href="#idp49645952">4. TeleMetrum v1 Specifications</a></span></dt><dt><span class="section"><a href="#idp49656512">5.
TeleMini v2.0 Specifications
- </a></span></dt><dt><span class="section"><a href="#idp45181888">5.
+ </a></span></dt><dt><span class="section"><a href="#idp49665344">6.
TeleMini v1.0 Specifications
- </a></span></dt><dt><span class="section"><a href="#idp45190688">6.
+ </a></span></dt><dt><span class="section"><a href="#idp49674144">7.
EasyMini Specifications
- </a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp45198800">12. FAQ</a></span></dt><dt><span class="appendix"><a href="#idp45207648">A. Notes for Older Software</a></span></dt><dt><span class="appendix"><a href="#idp45230128">B. Drill Templates</a></span></dt><dd><dl><dt><span class="section"><a href="#idp45231296">1. TeleMega template</a></span></dt><dt><span class="section"><a href="#idp45247984">2. TeleMetrum template</a></span></dt><dt><span class="section"><a href="#idp45252368">3. TeleMini v2/EasyMini template</a></span></dt><dt><span class="section"><a href="#idp45256768">4. TeleMini v1 template</a></span></dt></dl></dd><dt><span class="appendix"><a href="#idp45261280">C. Calibration</a></span></dt><dd><dl><dt><span class="section"><a href="#idp45262832">1. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp45267376">2. TeleMetrum and TeleMega Accelerometers</a></span></dt></dl></dd><dt><span class="appendix"><a href="#idp45272480">D. Release Notes</a></span></dt></dl></div><div class="list-of-tables"><p><b>List of Tables</b></p><dl><dt>4.1. <a href="#idp42978752">Altus Metrum Electronics</a></dt><dt>4.2. <a href="#idp44395088">Altus Metrum Boards</a></dt><dt>4.3. <a href="#idp44437312">TeleMetrum Screw Terminals</a></dt><dt>4.4. <a href="#idp44466928">TeleMini v1.0 Connections</a></dt><dt>4.5. <a href="#idp44495840">TeleMini v2.0 Connections</a></dt><dt>4.6. <a href="#idp44527376">EasyMini Connections</a></dt><dt>4.7. <a href="#idp44558768">TeleMega Screw Terminals</a></dt><dt>4.8. <a href="#idp44602080">Data Storage on Altus Metrum altimeters</a></dt><dt>5.1. <a href="#idp44642240">AltOS Modes</a></dt><dt>5.2. <a href="#idp44679328">Pad/Idle Indications</a></dt><dt>5.3. <a href="#idp44729008">Altus Metrum APRS Comments</a></dt></dl></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp43524064"></a>Chapter 1. Introduction and Overview</h1></div></div></div><p>
+ </a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp49682256">12. FAQ</a></span></dt><dt><span class="appendix"><a href="#idp49691104">A. Notes for Older Software</a></span></dt><dt><span class="appendix"><a href="#idp49713504">B. Drill Templates</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49714672">1. TeleMega template</a></span></dt><dt><span class="section"><a href="#idp49731360">2. EasyMega template</a></span></dt><dt><span class="section"><a href="#idp49735744">3. TeleMetrum template</a></span></dt><dt><span class="section"><a href="#idp49740128">4. TeleMini v2/EasyMini template</a></span></dt><dt><span class="section"><a href="#idp49744528">5. TeleMini v1 template</a></span></dt></dl></dd><dt><span class="appendix"><a href="#idp49749040">C. Calibration</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49750592">1. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp49755136">2. TeleMetrum, TeleMega and EasyMega Accelerometers</a></span></dt></dl></dd><dt><span class="appendix"><a href="#idp49760816">D. Release Notes</a></span></dt></dl></div><div class="list-of-tables"><p><b>List of Tables</b></p><dl><dt>4.1. <a href="#idp48750064">Altus Metrum Electronics</a></dt><dt>4.2. <a href="#idp48804240">Altus Metrum Boards</a></dt><dt>4.3. <a href="#idp43191248">TeleMetrum Screw Terminals</a></dt><dt>4.4. <a href="#idp48872848">TeleMini v1.0 Connections</a></dt><dt>4.5. <a href="#idp48901760">TeleMini v2.0 Connections</a></dt><dt>4.6. <a href="#idp48933296">EasyMini Connections</a></dt><dt>4.7. <a href="#idp48964688">TeleMega Screw Terminals</a></dt><dt>4.8. <a href="#idp49011728">EasyMega Screw Terminals</a></dt><dt>4.9. <a href="#idp49055040">Data Storage on Altus Metrum altimeters</a></dt><dt>5.1. <a href="#idp49097680">AltOS Modes</a></dt><dt>5.2. <a href="#idp49134768">Pad/Idle Indications</a></dt><dt>5.3. <a href="#idp49185360">Altus Metrum APRS Comments</a></dt></dl></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp43412128"></a>Chapter 1. Introduction and Overview</h1></div></div></div><p>
Welcome to the Altus Metrum community! Our circuits and software reflect
our passion for both hobby rocketry and Free Software. We hope their
capabilities and performance will delight you in every way, but by
@@ -104,6 +108,10 @@ NAR #88757, TRA #12200<br>
EasyMini is a dual-deploy altimeter with logging and built-in
USB data download.
</p><p>
+ EasyMega is essentially a TeleMega board with the GPS receiver
+ and telemetry transmitter removed. It offers the same 6 pyro
+ channels and integrated gyroscopes for staging/air-start inhibit.
+ </p><p>
TeleDongle was our first ground station, providing a USB to RF
interfaces for communicating with the altimeters. Combined with
your choice of antenna and notebook computer, TeleDongle and our
@@ -121,11 +129,11 @@ NAR #88757, TRA #12200<br>
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="idp43531824"></a>Chapter 2. Getting Started</h1></div></div></div><p>
+ </p></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp43239632"></a>Chapter 2. Getting Started</h1></div></div></div><p>
The first thing to do after you check the inventory of parts in your
&#8220;starter kit&#8221; is to charge the battery.
</p><p>
- For TeleMetrum and TeleMega, the battery can be charged by plugging it into the
+ 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
@@ -144,7 +152,7 @@ NAR #88757, TRA #12200<br>
to trickle charge. It can take several hours to fully recharge a
deeply discharged battery.
</p><p>
- TeleMetrum v2.0 and TeleMega use a higher power battery charger,
+ 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
@@ -191,7 +199,7 @@ NAR #88757, TRA #12200<br>
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="idp38854464"></a>Chapter 3. Handling Precautions</h1></div></div></div><p>
+ </p></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp43249600"></a>Chapter 3. Handling Precautions</h1></div></div></div><p>
All Altus Metrum products are sophisticated electronic devices.
When handled gently and properly installed in an air-frame, they
will deliver impressive results. However, as with all electronic
@@ -230,7 +238,7 @@ NAR #88757, TRA #12200<br>
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="idp38859952"></a>Chapter 4. Altus Metrum Hardware</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp38860624">1. General Usage Instructions</a></span></dt><dd><dl><dt><span class="section"><a href="#idp38862592">1.1. Hooking Up Lithium Polymer Batteries</a></span></dt><dt><span class="section"><a href="#idp42276480">1.2. Hooking Up Pyro Charges</a></span></dt><dt><span class="section"><a href="#idp42591936">1.3. Hooking Up a Power Switch</a></span></dt><dt><span class="section"><a href="#idp40956544">1.4. Using a Separate Pyro Battery</a></span></dt><dt><span class="section"><a href="#idp40258464">1.5. Using a Different Kind of Battery</a></span></dt></dl></dd><dt><span class="section"><a href="#idp43170688">2. Specifications</a></span></dt><dt><span class="section"><a href="#idp44431104">3. TeleMetrum</a></span></dt><dd><dl><dt><span class="section"><a href="#idp44436000">3.1. TeleMetrum Screw Terminals</a></span></dt><dt><span class="section"><a href="#idp44455216">3.2. Using a Separate Pyro Battery with TeleMetrum</a></span></dt><dt><span class="section"><a href="#idp44458464">3.3. Using an Active Switch with TeleMetrum</a></span></dt></dl></dd><dt><span class="section"><a href="#idp44460592">4. TeleMini v1.0</a></span></dt><dd><dl><dt><span class="section"><a href="#idp44465488">4.1. TeleMini v1.0 Screw Terminals</a></span></dt><dt><span class="section"><a href="#idp44484832">4.2. Using a Separate Pyro Battery with TeleMini v1.0</a></span></dt><dt><span class="section"><a href="#idp44488208">4.3. Using an Active Switch with TeleMini v1.0</a></span></dt></dl></dd><dt><span class="section"><a href="#idp44490416">5. TeleMini v2.0</a></span></dt><dd><dl><dt><span class="section"><a href="#idp44494432">5.1. TeleMini v2.0 Screw Terminals</a></span></dt><dt><span class="section"><a href="#idp44516816">5.2. Using a Separate Pyro Battery with TeleMini v2.0</a></span></dt><dt><span class="section"><a href="#idp44520016">5.3. Using an Active Switch with TeleMini v2.0</a></span></dt></dl></dd><dt><span class="section"><a href="#idp44522112">6. EasyMini</a></span></dt><dd><dl><dt><span class="section"><a href="#idp44525968">6.1. EasyMini Screw Terminals</a></span></dt><dt><span class="section"><a href="#idp44548352">6.2. Using a Separate Pyro Battery with EasyMini</a></span></dt><dt><span class="section"><a href="#idp44551536">6.3. Using an Active Switch with EasyMini</a></span></dt></dl></dd><dt><span class="section"><a href="#idp44553632">7. TeleMega</a></span></dt><dd><dl><dt><span class="section"><a href="#idp44557600">7.1. TeleMega Screw Terminals</a></span></dt><dt><span class="section"><a href="#idp44595104">7.2. Using a Separate Pyro Battery with TeleMega</a></span></dt><dt><span class="section"><a href="#idp44596704">7.3. Using Only One Battery With TeleMega</a></span></dt><dt><span class="section"><a href="#idp44598624">7.4. Using an Active Switch with TeleMega</a></span></dt></dl></dd><dt><span class="section"><a href="#idp44600672">8. Flight Data Recording</a></span></dt><dt><span class="section"><a href="#idp44629504">9. Installation</a></span></dt></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp38860624"></a>1. General Usage Instructions</h2></div></div></div><p>
+ </p></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp43255088"></a>Chapter 4. Altus Metrum Hardware</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp43255760">1. General Usage Instructions</a></span></dt><dd><dl><dt><span class="section"><a href="#idp43257728">1.1. Hooking Up Lithium Polymer Batteries</a></span></dt><dt><span class="section"><a href="#idp43260736">1.2. Hooking Up Pyro Charges</a></span></dt><dt><span class="section"><a href="#idp43262816">1.3. Hooking Up a Power Switch</a></span></dt><dt><span class="section"><a href="#idp43266032">1.4. Using a Separate Pyro Battery</a></span></dt><dt><span class="section"><a href="#idp43268544">1.5. Using a Different Kind of Battery</a></span></dt></dl></dd><dt><span class="section"><a href="#idp43270288">2. Specifications</a></span></dt><dt><span class="section"><a href="#idp48828432">3. TeleMetrum</a></span></dt><dd><dl><dt><span class="section"><a href="#idp48831824">3.1. TeleMetrum Screw Terminals</a></span></dt><dt><span class="section"><a href="#idp48861136">3.2. Using a Separate Pyro Battery with TeleMetrum</a></span></dt><dt><span class="section"><a href="#idp48864384">3.3. Using an Active Switch with TeleMetrum</a></span></dt></dl></dd><dt><span class="section"><a href="#idp48866512">4. TeleMini v1.0</a></span></dt><dd><dl><dt><span class="section"><a href="#idp48871408">4.1. TeleMini v1.0 Screw Terminals</a></span></dt><dt><span class="section"><a href="#idp48890752">4.2. Using a Separate Pyro Battery with TeleMini v1.0</a></span></dt><dt><span class="section"><a href="#idp48894128">4.3. Using an Active Switch with TeleMini v1.0</a></span></dt></dl></dd><dt><span class="section"><a href="#idp48896336">5. TeleMini v2.0</a></span></dt><dd><dl><dt><span class="section"><a href="#idp48900352">5.1. TeleMini v2.0 Screw Terminals</a></span></dt><dt><span class="section"><a href="#idp48922736">5.2. Using a Separate Pyro Battery with TeleMini v2.0</a></span></dt><dt><span class="section"><a href="#idp48925936">5.3. Using an Active Switch with TeleMini v2.0</a></span></dt></dl></dd><dt><span class="section"><a href="#idp48928032">6. EasyMini</a></span></dt><dd><dl><dt><span class="section"><a href="#idp48931888">6.1. EasyMini Screw Terminals</a></span></dt><dt><span class="section"><a href="#idp48954272">6.2. Using a Separate Pyro Battery with EasyMini</a></span></dt><dt><span class="section"><a href="#idp48957456">6.3. Using an Active Switch with EasyMini</a></span></dt></dl></dd><dt><span class="section"><a href="#idp48959552">7. TeleMega</a></span></dt><dd><dl><dt><span class="section"><a href="#idp48963520">7.1. TeleMega Screw Terminals</a></span></dt><dt><span class="section"><a href="#idp49001024">7.2. Using a Separate Pyro Battery with TeleMega</a></span></dt><dt><span class="section"><a href="#idp49002624">7.3. Using Only One Battery With TeleMega</a></span></dt><dt><span class="section"><a href="#idp49004544">7.4. Using an Active Switch with TeleMega</a></span></dt></dl></dd><dt><span class="section"><a href="#idp49006592">8. EasyMega</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49010560">8.1. EasyMega Screw Terminals</a></span></dt><dt><span class="section"><a href="#idp49048064">8.2. Using a Separate Pyro Battery with EasyMega</a></span></dt><dt><span class="section"><a href="#idp49049664">8.3. Using Only One Battery With EasyMega</a></span></dt><dt><span class="section"><a href="#idp49051584">8.4. Using an Active Switch with EasyMega</a></span></dt></dl></dd><dt><span class="section"><a href="#idp49053632">9. Flight Data Recording</a></span></dt><dt><span class="section"><a href="#idp49084400">10. Installation</a></span></dt></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp43255760"></a>1. General Usage Instructions</h2></div></div></div><p>
Here are general instructions for hooking up an Altus Metrum
flight computer. Instructions specific to each model will be
found in the section devoted to that model below.
@@ -240,7 +248,7 @@ NAR #88757, TRA #12200<br>
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="idp38862592"></a>1.1. Hooking Up Lithium Polymer Batteries</h3></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp43257728"></a>1.1. Hooking Up Lithium Polymer Batteries</h3></div></div></div><p>
All Altus Metrum flight computers have a two pin JST PH
series connector to connect up a single-cell Lithium Polymer
cell (3.7V nominal). You can purchase matching batteries
@@ -254,7 +262,7 @@ NAR #88757, TRA #12200<br>
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="idp42276480"></a>1.2. Hooking Up Pyro Charges</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp43260736"></a>1.2. Hooking Up Pyro Charges</h3></div></div></div><p>
Altus Metrum flight computers always have two screws for
each pyro charge. This means you shouldn't need to put two
wires into a screw terminal or connect leads from pyro
@@ -265,13 +273,13 @@ NAR #88757, TRA #12200<br>
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="idp42591936"></a>1.3. Hooking Up a Power Switch</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp43262816"></a>1.3. Hooking Up a Power Switch</h3></div></div></div><p>
Altus Metrum flight computers need an external power switch
to turn them on. This disconnects both the computer and the
pyro charges from the battery, preventing the charges from
firing when in the Off position. The switch is in-line with
the positive battery terminal.
- </p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp42971904"></a>1.3.1. Using an External Active Switch Circuit</h4></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp43264192"></a>1.3.1. Using an External Active Switch Circuit</h4></div></div></div><p>
You can use an active switch circuit, such as the
Featherweight Magnetic Switch, with any Altus Metrum
flight computer. These require three connections, one to
@@ -280,7 +288,7 @@ NAR #88757, TRA #12200<br>
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="idp40956544"></a>1.4. Using a Separate Pyro Battery</h3></div></div></div><p>
+ </p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp43266032"></a>1.4. Using a Separate Pyro Battery</h3></div></div></div><p>
As mentioned above in the section on hooking up pyro
charges, one lead for each of the pyro charges is connected
through the power switch directly to the positive battery
@@ -297,18 +305,18 @@ NAR #88757, TRA #12200<br>
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="idp40258464"></a>1.5. Using a Different Kind of Battery</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp43268544"></a>1.5. Using a Different Kind of Battery</h3></div></div></div><p>
EasyMini and TeleMini v2 are designed to use either a
lithium polymer battery or any other battery producing
between 4 and 12 volts, such as a rectangular 9V
- battery. TeleMega and TeleMetrum are not designed for this,
+ 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="idp43170688"></a>2. Specifications</h2></div></div></div><p>
+ </p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp43270288"></a>2. Specifications</h2></div></div></div><p>
Here's the full set of Altus Metrum products, both in
production and retired.
- </p><div class="table"><a name="idp42978752"></a><p class="title"><b>Table 4.1. Altus Metrum Electronics</b></p><div class="table-contents"><table summary="Altus Metrum Electronics" border="1"><colgroup><col align="center" class="Device"><col align="center" class="Barometer"><col align="center" class="Z-axis accelerometer"><col align="center" class="GPS"><col align="center" class="3D sensors"><col align="center" class="Storage"><col align="center" class="RF"><col align="center" class="Battery"></colgroup><thead><tr><th align="center">Device</th><th align="center">Barometer</th><th align="center">Z-axis accelerometer</th><th align="center">GPS</th><th align="center">3D sensors</th><th align="center">Storage</th><th align="center">RF Output</th><th align="center">Battery</th></tr></thead><tbody><tr><td align="center">TeleMetrum v1.0</td><td align="center"><p>MP3H6115 10km (33k')</p></td><td align="center"><p>MMA2202 50g</p></td><td align="center">SkyTraq</td><td align="center">-</td><td align="center">1MB</td><td align="center">10mW</td><td align="center">3.7V</td></tr><tr><td align="center">TeleMetrum v1.1</td><td align="center"><p>MP3H6115 10km (33k')</p></td><td align="center"><p>MMA2202 50g</p></td><td align="center">SkyTraq</td><td align="center">-</td><td align="center">2MB</td><td align="center">10mW</td><td align="center">3.7V</td></tr><tr><td align="center">TeleMetrum v1.2</td><td align="center"><p>MP3H6115 10km (33k')</p></td><td align="center"><p>ADXL78 70g</p></td><td align="center">SkyTraq</td><td align="center">-</td><td align="center">2MB</td><td align="center">10mW</td><td align="center">3.7V</td></tr><tr><td align="center">TeleMetrum v2.0</td><td align="center"><p>MS5607 30km (100k')</p></td><td align="center"><p>MMA6555 102g</p></td><td align="center">uBlox Max-7Q</td><td align="center">-</td><td align="center">8MB</td><td align="center">40mW</td><td align="center">3.7V</td></tr><tr><td align="center"><p>TeleMini v1.0</p></td><td align="center"><p>MP3H6115 10km (33k')</p></td><td align="center">-</td><td align="center">-</td><td align="center">-</td><td align="center">5kB</td><td align="center">10mW</td><td align="center">3.7V</td></tr><tr><td align="center">TeleMini v2.0</td><td align="center"><p>MS5607 30km (100k')</p></td><td align="center">-</td><td align="center">-</td><td align="center">-</td><td align="center">1MB</td><td align="center">10mW</td><td align="center">3.7-12V</td></tr><tr><td align="center">EasyMini v1.0</td><td align="center"><p>MS5607 30km (100k')</p></td><td align="center">-</td><td align="center">-</td><td align="center">-</td><td align="center">1MB</td><td align="center">-</td><td align="center">3.7-12V</td></tr><tr><td align="center">TeleMega v1.0</td><td align="center"><p>MS5607 30km (100k')</p></td><td align="center"><p>MMA6555 102g</p></td><td align="center">uBlox Max-7Q</td><td align="center"><p>MPU6000 HMC5883</p></td><td align="center">8MB</td><td align="center">40mW</td><td align="center">3.7V</td></tr></tbody></table></div></div><br class="table-break"><div class="table"><a name="idp44395088"></a><p class="title"><b>Table 4.2. Altus Metrum Boards</b></p><div class="table-contents"><table summary="Altus Metrum Boards" border="1"><colgroup><col align="center" class="Device"><col align="center" class="Connectors"><col align="center" class="Screw Terminals"><col align="center" class="Width"><col align="center" class="Length"><col align="center" class="Tube Size"></colgroup><thead><tr><th align="center">Device</th><th align="center">Connectors</th><th align="center">Screw Terminals</th><th align="center">Width</th><th align="center">Length</th><th align="center">Tube Size</th></tr></thead><tbody><tr><td align="center">TeleMetrum</td><td align="center"><p>
+ </p><div class="table"><a name="idp48750064"></a><p class="title"><b>Table 4.1. Altus Metrum Electronics</b></p><div class="table-contents"><table summary="Altus Metrum Electronics" border="1"><colgroup><col align="center" class="Device"><col align="center" class="Barometer"><col align="center" class="Z-axis accelerometer"><col align="center" class="GPS"><col align="center" class="3D sensors"><col align="center" class="Storage"><col align="center" class="RF"><col align="center" class="Battery"></colgroup><thead><tr><th align="center">Device</th><th align="center">Barometer</th><th align="center">Z-axis accelerometer</th><th align="center">GPS</th><th align="center">3D sensors</th><th align="center">Storage</th><th align="center">RF Output</th><th align="center">Battery</th></tr></thead><tbody><tr><td align="center">TeleMetrum v1.0</td><td align="center"><p>MP3H6115 10km (33k')</p></td><td align="center"><p>MMA2202 50g</p></td><td align="center">SkyTraq</td><td align="center">-</td><td align="center">1MB</td><td align="center">10mW</td><td align="center">3.7V</td></tr><tr><td align="center">TeleMetrum v1.1</td><td align="center"><p>MP3H6115 10km (33k')</p></td><td align="center"><p>MMA2202 50g</p></td><td align="center">SkyTraq</td><td align="center">-</td><td align="center">2MB</td><td align="center">10mW</td><td align="center">3.7V</td></tr><tr><td align="center">TeleMetrum v1.2</td><td align="center"><p>MP3H6115 10km (33k')</p></td><td align="center"><p>ADXL78 70g</p></td><td align="center">SkyTraq</td><td align="center">-</td><td align="center">2MB</td><td align="center">10mW</td><td align="center">3.7V</td></tr><tr><td align="center">TeleMetrum v2.0</td><td align="center"><p>MS5607 30km (100k')</p></td><td align="center"><p>MMA6555 102g</p></td><td align="center">uBlox Max-7Q</td><td align="center">-</td><td align="center">8MB</td><td align="center">40mW</td><td align="center">3.7V</td></tr><tr><td align="center"><p>TeleMini v1.0</p></td><td align="center"><p>MP3H6115 10km (33k')</p></td><td align="center">-</td><td align="center">-</td><td align="center">-</td><td align="center">5kB</td><td align="center">10mW</td><td align="center">3.7V</td></tr><tr><td align="center">TeleMini v2.0</td><td align="center"><p>MS5607 30km (100k')</p></td><td align="center">-</td><td align="center">-</td><td align="center">-</td><td align="center">1MB</td><td align="center">10mW</td><td align="center">3.7-12V</td></tr><tr><td align="center">EasyMini v1.0</td><td align="center"><p>MS5607 30km (100k')</p></td><td align="center">-</td><td align="center">-</td><td align="center">-</td><td align="center">1MB</td><td align="center">-</td><td align="center">3.7-12V</td></tr><tr><td align="center">TeleMega v1.0</td><td align="center"><p>MS5607 30km (100k')</p></td><td align="center"><p>MMA6555 102g</p></td><td align="center">uBlox Max-7Q</td><td align="center"><p>MPU6000 HMC5883</p></td><td align="center">8MB</td><td align="center">40mW</td><td align="center">3.7V</td></tr><tr><td align="center">EasyMega v1.0</td><td align="center"><p>MS5607 30km (100k')</p></td><td align="center"><p>MMA6555 102g</p></td><td align="center">-</td><td align="center"><p>MPU6000 HMC5883</p></td><td align="center">8MB</td><td align="center">-</td><td align="center">3.7V</td></tr></tbody></table></div></div><br class="table-break"><div class="table"><a name="idp48804240"></a><p class="title"><b>Table 4.2. Altus Metrum Boards</b></p><div class="table-contents"><table summary="Altus Metrum Boards" border="1"><colgroup><col align="center" class="Device"><col align="center" class="Connectors"><col align="center" class="Screw Terminals"><col align="center" class="Width"><col align="center" class="Length"><col align="center" class="Tube Size"></colgroup><thead><tr><th align="center">Device</th><th align="center">Connectors</th><th align="center">Screw Terminals</th><th align="center">Width</th><th align="center">Length</th><th align="center">Tube Size</th></tr></thead><tbody><tr><td align="center">TeleMetrum</td><td align="center"><p>
Antenna
Debug
Companion
@@ -352,7 +360,18 @@ NAR #88757, TRA #12200<br>
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></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="idp44431104"></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>
+ </p></td><td align="center">1¼ inch (3.18cm)</td><td align="center">3¼ inch (8.26cm)</td><td align="center">38mm coupler</td></tr><tr><td align="center">EasyMega</td><td align="center"><p>
+ Debug
+ Companion
+ USB
+ Battery
+ </p></td><td align="center"><p>
+ Apogee pyro
+ Main pyro
+ Pyro A-D
+ Switch
+ Pyro battery
+ </p></td><td align="center">1¼ inch (3.18cm)</td><td align="center">2¼ inch (5.62cm)</td><td align="center">38mm coupler</td></tr></tbody></table></div></div><br class="table-break"></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp48828432"></a>3. TeleMetrum</h2></div></div></div><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="495"><tr><td><img src="telemetrum-v1.1-thside.jpg" width="495"></td></tr></table></div></div><p>
TeleMetrum is a 1 inch by 2¾ inch circuit board. It was designed to
fit inside coupler for 29mm air-frame tubing, but using it in a tube that
small in diameter may require some creativity in mounting and wiring
@@ -363,13 +382,13 @@ NAR #88757, TRA #12200<br>
the e-matches for apogee and main ejection charges depart from the
fin can end of the board, meaning an ideal &#8220;simple&#8221; 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="idp44436000"></a>3.1. TeleMetrum Screw Terminals</h3></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp48831824"></a>3.1. TeleMetrum Screw Terminals</h3></div></div></div><p>
TeleMetrum has six screw terminals on the end of the board
opposite the telemetry antenna. Two are for the power
switch, and two each for the apogee and main igniter
circuits. Using the picture above and starting from the top,
the terminals are as follows:
- </p><div class="table"><a name="idp44437312"></a><p class="title"><b>Table 4.3. TeleMetrum Screw Terminals</b></p><div class="table-contents"><table summary="TeleMetrum Screw Terminals" border="1"><colgroup><col align="center" class="Pin #"><col align="center" class="Pin Name"><col align="left" class="Description"></colgroup><thead><tr><th align="center">Terminal #</th><th align="center">Terminal Name</th><th align="center">Description</th></tr></thead><tbody><tr><td align="center">1</td><td align="center">Switch Output</td><td align="left">Switch connection to flight computer</td></tr><tr><td align="center">2</td><td align="center">Switch Input</td><td align="left">Switch connection to positive battery terminal</td></tr><tr><td align="center">3</td><td align="center">Main +</td><td align="left">Main pyro channel common connection to battery +</td></tr><tr><td align="center">4</td><td align="center">Main -</td><td align="left">Main pyro channel connection to pyro circuit</td></tr><tr><td align="center">5</td><td align="center">Apogee +</td><td align="left">Apogee pyro channel common connection to battery +</td></tr><tr><td align="center">6</td><td align="center">Apogee -</td><td align="left">Apogee pyro channel connection to pyro circuit</td></tr></tbody></table></div></div><br class="table-break"></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp44455216"></a>3.2. Using a Separate Pyro Battery with TeleMetrum</h3></div></div></div><p>
+ </p><div class="table"><a name="idp43191248"></a><p class="title"><b>Table 4.3. TeleMetrum Screw Terminals</b></p><div class="table-contents"><table summary="TeleMetrum Screw Terminals" border="1"><colgroup><col align="center" class="Pin #"><col align="center" class="Pin Name"><col align="left" class="Description"></colgroup><thead><tr><th align="center">Terminal #</th><th align="center">Terminal Name</th><th align="center">Description</th></tr></thead><tbody><tr><td align="center">1</td><td align="center">Switch Output</td><td align="left">Switch connection to flight computer</td></tr><tr><td align="center">2</td><td align="center">Switch Input</td><td align="left">Switch connection to positive battery terminal</td></tr><tr><td align="center">3</td><td align="center">Main +</td><td align="left">Main pyro channel common connection to battery +</td></tr><tr><td align="center">4</td><td align="center">Main -</td><td align="left">Main pyro channel connection to pyro circuit</td></tr><tr><td align="center">5</td><td align="center">Apogee +</td><td align="left">Apogee pyro channel common connection to battery +</td></tr><tr><td align="center">6</td><td align="center">Apogee -</td><td align="left">Apogee pyro channel connection to pyro circuit</td></tr></tbody></table></div></div><br class="table-break"></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp48861136"></a>3.2. Using a Separate Pyro Battery with TeleMetrum</h3></div></div></div><p>
As described above, using an external pyro battery involves
connecting the negative battery terminal to the flight
computer ground, connecting the positive battery terminal to
@@ -388,7 +407,7 @@ NAR #88757, TRA #12200<br>
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="idp44458464"></a>3.3. Using an Active Switch with TeleMetrum</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp48864384"></a>3.3. Using an Active Switch with TeleMetrum</h3></div></div></div><p>
As explained above, an external active switch requires three
connections, one to the positive battery terminal, one to
the flight computer positive input and one to ground.
@@ -397,7 +416,7 @@ NAR #88757, TRA #12200<br>
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="idp44460592"></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>
+ </p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp48866512"></a>4. TeleMini v1.0</h2></div></div></div><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="495"><tr><td><img src="telemini-v1-top.jpg" width="495"></td></tr></table></div></div><p>
TeleMini v1.0 is ½ inches by 1½ inches. It was
designed to fit inside an 18mm air-frame tube, but using it in
a tube that small in diameter may require some creativity in
@@ -410,7 +429,7 @@ NAR #88757, TRA #12200<br>
apogee and main ejection charges depart from the other end of
the board, meaning an ideal &#8220;simple&#8221; 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="idp44465488"></a>4.1. TeleMini v1.0 Screw Terminals</h3></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp48871408"></a>4.1. TeleMini v1.0 Screw Terminals</h3></div></div></div><p>
TeleMini v1.0 has four screw terminals on the end of the
board opposite the telemetry antenna. Two are for the apogee
and two are for main igniter circuits. There are also wires
@@ -418,7 +437,7 @@ NAR #88757, TRA #12200<br>
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="idp44466928"></a><p class="title"><b>Table 4.4. TeleMini v1.0 Connections</b></p><div class="table-contents"><table summary="TeleMini v1.0 Connections" border="1"><colgroup><col align="center" class="Pin #"><col align="center" class="Pin Name"><col align="left" class="Description"></colgroup><thead><tr><th align="center">Terminal #</th><th align="center">Terminal Name</th><th align="center">Description</th></tr></thead><tbody><tr><td align="center">1</td><td align="center">Apogee -</td><td align="left">Apogee pyro channel connection to pyro circuit</td></tr><tr><td align="center">2</td><td align="center">Apogee +</td><td align="left">Apogee pyro channel common connection to battery +</td></tr><tr><td align="center">3</td><td align="center">Main -</td><td align="left">Main pyro channel connection to pyro circuit</td></tr><tr><td align="center">4</td><td align="center">Main +</td><td align="left">Main pyro channel common connection to battery +</td></tr><tr><td align="center">Left</td><td align="center">Switch Output</td><td align="left">Switch connection to flight computer</td></tr><tr><td align="center">Right</td><td align="center">Switch Input</td><td align="left">Switch connection to positive battery terminal</td></tr></tbody></table></div></div><br class="table-break"></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp44484832"></a>4.2. Using a Separate Pyro Battery with TeleMini v1.0</h3></div></div></div><p>
+ </p><div class="table"><a name="idp48872848"></a><p class="title"><b>Table 4.4. TeleMini v1.0 Connections</b></p><div class="table-contents"><table summary="TeleMini v1.0 Connections" border="1"><colgroup><col align="center" class="Pin #"><col align="center" class="Pin Name"><col align="left" class="Description"></colgroup><thead><tr><th align="center">Terminal #</th><th align="center">Terminal Name</th><th align="center">Description</th></tr></thead><tbody><tr><td align="center">1</td><td align="center">Apogee -</td><td align="left">Apogee pyro channel connection to pyro circuit</td></tr><tr><td align="center">2</td><td align="center">Apogee +</td><td align="left">Apogee pyro channel common connection to battery +</td></tr><tr><td align="center">3</td><td align="center">Main -</td><td align="left">Main pyro channel connection to pyro circuit</td></tr><tr><td align="center">4</td><td align="center">Main +</td><td align="left">Main pyro channel common connection to battery +</td></tr><tr><td align="center">Left</td><td align="center">Switch Output</td><td align="left">Switch connection to flight computer</td></tr><tr><td align="center">Right</td><td align="center">Switch Input</td><td align="left">Switch connection to positive battery terminal</td></tr></tbody></table></div></div><br class="table-break"></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp48890752"></a>4.2. Using a Separate Pyro Battery with TeleMini v1.0</h3></div></div></div><p>
As described above, using an external pyro battery involves
connecting the negative battery terminal to the flight
computer ground, connecting the positive battery terminal to
@@ -439,7 +458,7 @@ NAR #88757, TRA #12200<br>
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="idp44488208"></a>4.3. Using an Active Switch with TeleMini v1.0</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp48894128"></a>4.3. Using an Active Switch with TeleMini v1.0</h3></div></div></div><p>
As explained above, an external active switch requires three
connections, one to the positive battery terminal, one to
the flight computer positive input and one to ground. Again,
@@ -450,21 +469,21 @@ NAR #88757, TRA #12200<br>
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="idp44490416"></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>
+ </p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp48896336"></a>5. TeleMini v2.0</h2></div></div></div><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="495"><tr><td><img src="telemini-v2-top.jpg" width="495"></td></tr></table></div></div><p>
TeleMini v2.0 is 0.8 inches by 1½ inches. It adds more
on-board data logging memory, a built-in USB connector and
screw terminals for the battery and power switch. The larger
board fits in a 24mm coupler. There's also a battery connector
for a LiPo battery if you want to use one of those.
- </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp44494432"></a>5.1. TeleMini v2.0 Screw Terminals</h3></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp48900352"></a>5.1. TeleMini v2.0 Screw Terminals</h3></div></div></div><p>
TeleMini v2.0 has two sets of four screw terminals on the end of the
board opposite the telemetry antenna. Using the picture
above, the top four have connections for the main pyro
circuit and an external battery and the bottom four have
connections for the apogee pyro circuit and the power
switch. Counting from the left, the connections are as follows:
- </p><div class="table"><a name="idp44495840"></a><p class="title"><b>Table 4.5. TeleMini v2.0 Connections</b></p><div class="table-contents"><table summary="TeleMini v2.0 Connections" border="1"><colgroup><col align="center" class="Pin #"><col align="center" class="Pin Name"><col align="left" class="Description"></colgroup><thead><tr><th align="center">Terminal #</th><th align="center">Terminal Name</th><th align="center">Description</th></tr></thead><tbody><tr><td align="center">Top 1</td><td align="center">Main -</td><td align="left">Main pyro channel connection to pyro circuit</td></tr><tr><td align="center">Top 2</td><td align="center">Main +</td><td align="left">Main pyro channel common connection to battery +</td></tr><tr><td align="center">Top 3</td><td align="center">Battery +</td><td align="left">Positive external battery terminal</td></tr><tr><td align="center">Top 4</td><td align="center">Battery -</td><td align="left">Negative external battery terminal</td></tr><tr><td align="center">Bottom 1</td><td align="center">Apogee -</td><td align="left">Apogee pyro channel connection to pyro circuit</td></tr><tr><td align="center">Bottom 2</td><td align="center">Apogee +</td><td align="left">Apogee pyro channel common connection to
- battery +</td></tr><tr><td align="center">Bottom 3</td><td align="center">Switch Output</td><td align="left">Switch connection to flight computer</td></tr><tr><td align="center">Bottom 4</td><td align="center">Switch Input</td><td align="left">Switch connection to positive battery terminal</td></tr></tbody></table></div></div><br class="table-break"></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp44516816"></a>5.2. Using a Separate Pyro Battery with TeleMini v2.0</h3></div></div></div><p>
+ </p><div class="table"><a name="idp48901760"></a><p class="title"><b>Table 4.5. TeleMini v2.0 Connections</b></p><div class="table-contents"><table summary="TeleMini v2.0 Connections" border="1"><colgroup><col align="center" class="Pin #"><col align="center" class="Pin Name"><col align="left" class="Description"></colgroup><thead><tr><th align="center">Terminal #</th><th align="center">Terminal Name</th><th align="center">Description</th></tr></thead><tbody><tr><td align="center">Top 1</td><td align="center">Main -</td><td align="left">Main pyro channel connection to pyro circuit</td></tr><tr><td align="center">Top 2</td><td align="center">Main +</td><td align="left">Main pyro channel common connection to battery +</td></tr><tr><td align="center">Top 3</td><td align="center">Battery +</td><td align="left">Positive external battery terminal</td></tr><tr><td align="center">Top 4</td><td align="center">Battery -</td><td align="left">Negative external battery terminal</td></tr><tr><td align="center">Bottom 1</td><td align="center">Apogee -</td><td align="left">Apogee pyro channel connection to pyro circuit</td></tr><tr><td align="center">Bottom 2</td><td align="center">Apogee +</td><td align="left">Apogee pyro channel common connection to
+ battery +</td></tr><tr><td align="center">Bottom 3</td><td align="center">Switch Output</td><td align="left">Switch connection to flight computer</td></tr><tr><td align="center">Bottom 4</td><td align="center">Switch Input</td><td align="left">Switch connection to positive battery terminal</td></tr></tbody></table></div></div><br class="table-break"></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp48922736"></a>5.2. Using a Separate Pyro Battery with TeleMini v2.0</h3></div></div></div><p>
As described above, using an external pyro battery involves
connecting the negative battery terminal to the flight
computer ground, connecting the positive battery terminal to
@@ -483,7 +502,7 @@ NAR #88757, TRA #12200<br>
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="idp44520016"></a>5.3. Using an Active Switch with TeleMini v2.0</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp48925936"></a>5.3. Using an Active Switch with TeleMini v2.0</h3></div></div></div><p>
As explained above, an external active switch requires three
connections, one to the positive battery terminal, one to
the flight computer positive input and one to ground. Use
@@ -493,20 +512,20 @@ NAR #88757, TRA #12200<br>
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="idp44522112"></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>
+ </p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp48928032"></a>6. EasyMini</h2></div></div></div><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="495"><tr><td><img src="easymini-top.jpg" width="495"></td></tr></table></div></div><p>
EasyMini is built on a 0.8 inch by 1½ inch circuit board. It's
designed to fit in a 24mm coupler tube. The connectors and
screw terminals match TeleMini v2.0, so you can easily swap between
EasyMini and TeleMini.
- </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp44525968"></a>6.1. EasyMini Screw Terminals</h3></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp48931888"></a>6.1. EasyMini Screw Terminals</h3></div></div></div><p>
EasyMini has two sets of four screw terminals on the end of the
board opposite the telemetry antenna. Using the picture
above, the top four have connections for the main pyro
circuit and an external battery and the bottom four have
connections for the apogee pyro circuit and the power
switch. Counting from the left, the connections are as follows:
- </p><div class="table"><a name="idp44527376"></a><p class="title"><b>Table 4.6. EasyMini Connections</b></p><div class="table-contents"><table summary="EasyMini Connections" border="1"><colgroup><col align="center" class="Pin #"><col align="center" class="Pin Name"><col align="left" class="Description"></colgroup><thead><tr><th align="center">Terminal #</th><th align="center">Terminal Name</th><th align="center">Description</th></tr></thead><tbody><tr><td align="center">Top 1</td><td align="center">Main -</td><td align="left">Main pyro channel connection to pyro circuit</td></tr><tr><td align="center">Top 2</td><td align="center">Main +</td><td align="left">Main pyro channel common connection to battery +</td></tr><tr><td align="center">Top 3</td><td align="center">Battery +</td><td align="left">Positive external battery terminal</td></tr><tr><td align="center">Top 4</td><td align="center">Battery -</td><td align="left">Negative external battery terminal</td></tr><tr><td align="center">Bottom 1</td><td align="center">Apogee -</td><td align="left">Apogee pyro channel connection to pyro circuit</td></tr><tr><td align="center">Bottom 2</td><td align="center">Apogee +</td><td align="left">Apogee pyro channel common connection to
- battery +</td></tr><tr><td align="center">Bottom 3</td><td align="center">Switch Output</td><td align="left">Switch connection to flight computer</td></tr><tr><td align="center">Bottom 4</td><td align="center">Switch Input</td><td align="left">Switch connection to positive battery terminal</td></tr></tbody></table></div></div><br class="table-break"></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp44548352"></a>6.2. Using a Separate Pyro Battery with EasyMini</h3></div></div></div><p>
+ </p><div class="table"><a name="idp48933296"></a><p class="title"><b>Table 4.6. EasyMini Connections</b></p><div class="table-contents"><table summary="EasyMini Connections" border="1"><colgroup><col align="center" class="Pin #"><col align="center" class="Pin Name"><col align="left" class="Description"></colgroup><thead><tr><th align="center">Terminal #</th><th align="center">Terminal Name</th><th align="center">Description</th></tr></thead><tbody><tr><td align="center">Top 1</td><td align="center">Main -</td><td align="left">Main pyro channel connection to pyro circuit</td></tr><tr><td align="center">Top 2</td><td align="center">Main +</td><td align="left">Main pyro channel common connection to battery +</td></tr><tr><td align="center">Top 3</td><td align="center">Battery +</td><td align="left">Positive external battery terminal</td></tr><tr><td align="center">Top 4</td><td align="center">Battery -</td><td align="left">Negative external battery terminal</td></tr><tr><td align="center">Bottom 1</td><td align="center">Apogee -</td><td align="left">Apogee pyro channel connection to pyro circuit</td></tr><tr><td align="center">Bottom 2</td><td align="center">Apogee +</td><td align="left">Apogee pyro channel common connection to
+ battery +</td></tr><tr><td align="center">Bottom 3</td><td align="center">Switch Output</td><td align="left">Switch connection to flight computer</td></tr><tr><td align="center">Bottom 4</td><td align="center">Switch Input</td><td align="left">Switch connection to positive battery terminal</td></tr></tbody></table></div></div><br class="table-break"></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp48954272"></a>6.2. Using a Separate Pyro Battery with EasyMini</h3></div></div></div><p>
As described above, using an external pyro battery involves
connecting the negative battery terminal to the flight
computer ground, connecting the positive battery terminal to
@@ -525,7 +544,7 @@ NAR #88757, TRA #12200<br>
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="idp44551536"></a>6.3. Using an Active Switch with EasyMini</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp48957456"></a>6.3. Using an Active Switch with EasyMini</h3></div></div></div><p>
As explained above, an external active switch requires three
connections, one to the positive battery terminal, one to
the flight computer positive input and one to ground. Use
@@ -535,19 +554,19 @@ NAR #88757, TRA #12200<br>
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="idp44553632"></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>
+ </p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp48959552"></a>7. TeleMega</h2></div></div></div><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="495"><tr><td><img src="telemega-v1.0-top.jpg" width="495"></td></tr></table></div></div><p>
TeleMega is a 1¼ inch by 3¼ inch circuit board. It was
designed to easily fit in a 38mm coupler. Like TeleMetrum,
TeleMega has an accelerometer and so it must be mounted so that
the board is aligned with the flight axis. It can be mounted
either antenna up or down.
- </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp44557600"></a>7.1. TeleMega Screw Terminals</h3></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp48963520"></a>7.1. TeleMega Screw Terminals</h3></div></div></div><p>
TeleMega has two sets of nine screw terminals on the end of
the board opposite the telemetry antenna. They are as follows:
- </p><div class="table"><a name="idp44558768"></a><p class="title"><b>Table 4.7. TeleMega Screw Terminals</b></p><div class="table-contents"><table summary="TeleMega Screw Terminals" border="1"><colgroup><col align="center" class="Pin #"><col align="center" class="Pin Name"><col align="left" class="Description"></colgroup><thead><tr><th align="center">Terminal #</th><th align="center">Terminal Name</th><th align="center">Description</th></tr></thead><tbody><tr><td align="center">Top 1</td><td align="center">Switch Input</td><td align="left">Switch connection to positive battery terminal</td></tr><tr><td align="center">Top 2</td><td align="center">Switch Output</td><td align="left">Switch connection to flight computer</td></tr><tr><td align="center">Top 3</td><td align="center">GND</td><td align="left">Ground connection for use with external active switch</td></tr><tr><td align="center">Top 4</td><td align="center">Main -</td><td align="left">Main pyro channel connection to pyro circuit</td></tr><tr><td align="center">Top 5</td><td align="center">Main +</td><td align="left">Main pyro channel common connection to battery +</td></tr><tr><td align="center">Top 6</td><td align="center">Apogee -</td><td align="left">Apogee pyro channel connection to pyro circuit</td></tr><tr><td align="center">Top 7</td><td align="center">Apogee +</td><td align="left">Apogee pyro channel common connection to battery +</td></tr><tr><td align="center">Top 8</td><td align="center">D -</td><td align="left">D pyro channel connection to pyro circuit</td></tr><tr><td align="center">Top 9</td><td align="center">D +</td><td align="left">D pyro channel common connection to battery +</td></tr><tr><td align="center">Bottom 1</td><td align="center">GND</td><td align="left">Ground connection for negative pyro battery terminal</td></tr><tr><td align="center">Bottom 2</td><td align="center">Pyro</td><td align="left">Positive pyro battery terminal</td></tr><tr><td align="center">Bottom 3</td><td align="center">Lipo</td><td align="left">
+ </p><div class="table"><a name="idp48964688"></a><p class="title"><b>Table 4.7. TeleMega Screw Terminals</b></p><div class="table-contents"><table summary="TeleMega Screw Terminals" border="1"><colgroup><col align="center" class="Pin #"><col align="center" class="Pin Name"><col align="left" class="Description"></colgroup><thead><tr><th align="center">Terminal #</th><th align="center">Terminal Name</th><th align="center">Description</th></tr></thead><tbody><tr><td align="center">Top 1</td><td align="center">Switch Input</td><td align="left">Switch connection to positive battery terminal</td></tr><tr><td align="center">Top 2</td><td align="center">Switch Output</td><td align="left">Switch connection to flight computer</td></tr><tr><td align="center">Top 3</td><td align="center">GND</td><td align="left">Ground connection for use with external active switch</td></tr><tr><td align="center">Top 4</td><td align="center">Main -</td><td align="left">Main pyro channel connection to pyro circuit</td></tr><tr><td align="center">Top 5</td><td align="center">Main +</td><td align="left">Main pyro channel common connection to battery +</td></tr><tr><td align="center">Top 6</td><td align="center">Apogee -</td><td align="left">Apogee pyro channel connection to pyro circuit</td></tr><tr><td align="center">Top 7</td><td align="center">Apogee +</td><td align="left">Apogee pyro channel common connection to battery +</td></tr><tr><td align="center">Top 8</td><td align="center">D -</td><td align="left">D pyro channel connection to pyro circuit</td></tr><tr><td align="center">Top 9</td><td align="center">D +</td><td align="left">D pyro channel common connection to battery +</td></tr><tr><td align="center">Bottom 1</td><td align="center">GND</td><td align="left">Ground connection for negative pyro battery terminal</td></tr><tr><td align="center">Bottom 2</td><td align="center">Pyro</td><td align="left">Positive pyro battery terminal</td></tr><tr><td align="center">Bottom 3</td><td align="center">Lipo</td><td align="left">
Power switch output. Use to connect main battery to
pyro battery input
- </td></tr><tr><td align="center">Bottom 4</td><td align="center">A -</td><td align="left">A pyro channel connection to pyro circuit</td></tr><tr><td align="center">Bottom 5</td><td align="center">A +</td><td align="left">A pyro channel common connection to battery +</td></tr><tr><td align="center">Bottom 6</td><td align="center">B -</td><td align="left">B pyro channel connection to pyro circuit</td></tr><tr><td align="center">Bottom 7</td><td align="center">B +</td><td align="left">B pyro channel common connection to battery +</td></tr><tr><td align="center">Bottom 8</td><td align="center">C -</td><td align="left">C pyro channel connection to pyro circuit</td></tr><tr><td align="center">Bottom 9</td><td align="center">C +</td><td align="left">C pyro channel common connection to battery +</td></tr></tbody></table></div></div><br class="table-break"></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp44595104"></a>7.2. Using a Separate Pyro Battery with TeleMega</h3></div></div></div><p>
+ </td></tr><tr><td align="center">Bottom 4</td><td align="center">A -</td><td align="left">A pyro channel connection to pyro circuit</td></tr><tr><td align="center">Bottom 5</td><td align="center">A +</td><td align="left">A pyro channel common connection to battery +</td></tr><tr><td align="center">Bottom 6</td><td align="center">B -</td><td align="left">B pyro channel connection to pyro circuit</td></tr><tr><td align="center">Bottom 7</td><td align="center">B +</td><td align="left">B pyro channel common connection to battery +</td></tr><tr><td align="center">Bottom 8</td><td align="center">C -</td><td align="left">C pyro channel connection to pyro circuit</td></tr><tr><td align="center">Bottom 9</td><td align="center">C +</td><td align="left">C pyro channel common connection to battery +</td></tr></tbody></table></div></div><br class="table-break"></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49001024"></a>7.2. Using a Separate Pyro Battery with TeleMega</h3></div></div></div><p>
TeleMega provides explicit support for an external pyro
battery. All that is required is to remove the jumper
between the lipo terminal (Bottom 3) and the pyro terminal
@@ -555,7 +574,7 @@ NAR #88757, TRA #12200<br>
(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="idp44596704"></a>7.3. Using Only One Battery With TeleMega</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49002624"></a>7.3. Using Only One Battery With TeleMega</h3></div></div></div><p>
Because TeleMega has built-in support for a separate pyro
battery, if you want to fly with just one battery running
both the computer and firing the charges, you need to
@@ -563,7 +582,7 @@ NAR #88757, TRA #12200<br>
circuit. TeleMega has two screw terminals for this&#8212;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="idp44598624"></a>7.4. Using an Active Switch with TeleMega</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49004544"></a>7.4. Using an Active Switch with TeleMega</h3></div></div></div><p>
As explained above, an external active switch requires three
connections, one to the positive battery terminal, one to
the flight computer positive input and one to ground.
@@ -571,14 +590,50 @@ NAR #88757, TRA #12200<br>
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="idp44600672"></a>8. Flight Data Recording</h2></div></div></div><p>
+ </p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49006592"></a>8. EasyMega</h2></div></div></div><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="405"><tr><td><img src="easymega-v1.0-top.jpg" width="405"></td></tr></table></div></div><p>
+ EasyMega is a 1¼ inch by 2¼ inch circuit board. It was
+ designed to easily fit in a 38mm coupler. Like TeleMetrum,
+ EasyMega has an accelerometer and so it must be mounted so that
+ the board is aligned with the flight axis. It can be mounted
+ either antenna up or down.
+ </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49010560"></a>8.1. EasyMega Screw Terminals</h3></div></div></div><p>
+ EasyMega has two sets of nine screw terminals on the end of
+ the board opposite the telemetry antenna. They are as follows:
+ </p><div class="table"><a name="idp49011728"></a><p class="title"><b>Table 4.8. EasyMega Screw Terminals</b></p><div class="table-contents"><table summary="EasyMega Screw Terminals" border="1"><colgroup><col align="center" class="Pin #"><col align="center" class="Pin Name"><col align="left" class="Description"></colgroup><thead><tr><th align="center">Terminal #</th><th align="center">Terminal Name</th><th align="center">Description</th></tr></thead><tbody><tr><td align="center">Top 1</td><td align="center">Switch Input</td><td align="left">Switch connection to positive battery terminal</td></tr><tr><td align="center">Top 2</td><td align="center">Switch Output</td><td align="left">Switch connection to flight computer</td></tr><tr><td align="center">Top 3</td><td align="center">GND</td><td align="left">Ground connection for use with external active switch</td></tr><tr><td align="center">Top 4</td><td align="center">Main -</td><td align="left">Main pyro channel connection to pyro circuit</td></tr><tr><td align="center">Top 5</td><td align="center">Main +</td><td align="left">Main pyro channel common connection to battery +</td></tr><tr><td align="center">Top 6</td><td align="center">Apogee -</td><td align="left">Apogee pyro channel connection to pyro circuit</td></tr><tr><td align="center">Top 7</td><td align="center">Apogee +</td><td align="left">Apogee pyro channel common connection to battery +</td></tr><tr><td align="center">Top 8</td><td align="center">D -</td><td align="left">D pyro channel connection to pyro circuit</td></tr><tr><td align="center">Top 9</td><td align="center">D +</td><td align="left">D pyro channel common connection to battery +</td></tr><tr><td align="center">Bottom 1</td><td align="center">GND</td><td align="left">Ground connection for negative pyro battery terminal</td></tr><tr><td align="center">Bottom 2</td><td align="center">Pyro</td><td align="left">Positive pyro battery terminal</td></tr><tr><td align="center">Bottom 3</td><td align="center">Lipo</td><td align="left">
+ Power switch output. Use to connect main battery to
+ pyro battery input
+ </td></tr><tr><td align="center">Bottom 4</td><td align="center">A -</td><td align="left">A pyro channel connection to pyro circuit</td></tr><tr><td align="center">Bottom 5</td><td align="center">A +</td><td align="left">A pyro channel common connection to battery +</td></tr><tr><td align="center">Bottom 6</td><td align="center">B -</td><td align="left">B pyro channel connection to pyro circuit</td></tr><tr><td align="center">Bottom 7</td><td align="center">B +</td><td align="left">B pyro channel common connection to battery +</td></tr><tr><td align="center">Bottom 8</td><td align="center">C -</td><td align="left">C pyro channel connection to pyro circuit</td></tr><tr><td align="center">Bottom 9</td><td align="center">C +</td><td align="left">C pyro channel common connection to battery +</td></tr></tbody></table></div></div><br class="table-break"></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49048064"></a>8.2. Using a Separate Pyro Battery with EasyMega</h3></div></div></div><p>
+ EasyMega provides explicit support for an external pyro
+ battery. All that is required is to remove the jumper
+ between the lipo terminal (Bottom 3) and the pyro terminal
+ (Bottom 2). Then hook the negative pyro battery terminal to ground
+ (Bottom 1) and the positive pyro battery to the pyro battery
+ input (Bottom 2). You can then use the existing pyro screw
+ terminals to hook up all of the pyro charges.
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49049664"></a>8.3. Using Only One Battery With EasyMega</h3></div></div></div><p>
+ Because EasyMega has built-in support for a separate pyro
+ battery, if you want to fly with just one battery running
+ both the computer and firing the charges, you need to
+ connect the flight computer battery to the pyro
+ circuit. EasyMega has two screw terminals for this&#8212;hook a
+ wire from the Lipo terminal (Bottom 3) to the Pyro terminal
+ (Bottom 2).
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49051584"></a>8.4. Using an Active Switch with EasyMega</h3></div></div></div><p>
+ As explained above, an external active switch requires three
+ connections, one to the positive battery terminal, one to
+ the flight computer positive input and one to ground.
+ </p><p>
+ The positive battery terminal is available on Top terminal
+ 1, the positive flight computer input is on Top terminal
+ 2. Ground is on Top terminal 3.
+ </p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49053632"></a>9. Flight Data Recording</h2></div></div></div><p>
Each flight computer logs data at 100 samples per second
during ascent and 10 samples per second during descent, except
for TeleMini v1.0, which records ascent at 10 samples per
second and descent at 1 sample per second. Data are logged to
an on-board flash memory part, which can be partitioned into
several equal-sized blocks, one for each flight.
- </p><div class="table"><a name="idp44602080"></a><p class="title"><b>Table 4.8. 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></tbody></table></div></div><br class="table-break"><p>
+ </p><div class="table"><a name="idp49055040"></a><p class="title"><b>Table 4.9. Data Storage on Altus Metrum altimeters</b></p><div class="table-contents"><table summary="Data Storage on Altus Metrum altimeters" border="1"><colgroup><col align="center" class="Device"><col align="center" class="Bytes per sample"><col align="center" class="Total storage"><col align="center" class="Minutes of full-rate"></colgroup><thead><tr><th align="center">Device</th><th align="center">Bytes per Sample</th><th align="center">Total Storage</th><th align="center">Minutes at Full Rate</th></tr></thead><tbody><tr><td align="center">TeleMetrum v1.0</td><td align="center">8</td><td align="center">1MB</td><td align="center">20</td></tr><tr><td align="center">TeleMetrum v1.1 v1.2</td><td align="center">8</td><td align="center">2MB</td><td align="center">40</td></tr><tr><td align="center">TeleMetrum v2.0</td><td align="center">16</td><td align="center">8MB</td><td align="center">80</td></tr><tr><td align="center">TeleMini v1.0</td><td align="center">2</td><td align="center">5kB</td><td align="center">4</td></tr><tr><td align="center">TeleMini v2.0</td><td align="center">16</td><td align="center">1MB</td><td align="center">10</td></tr><tr><td align="center">EasyMini</td><td align="center">16</td><td align="center">1MB</td><td align="center">10</td></tr><tr><td align="center">TeleMega</td><td align="center">32</td><td align="center">8MB</td><td align="center">40</td></tr><tr><td align="center">EasyMega</td><td align="center">32</td><td align="center">8MB</td><td align="center">40</td></tr></tbody></table></div></div><br class="table-break"><p>
The on-board flash is partitioned into separate flight logs,
each of a fixed maximum size. Increase the maximum size of
each log and you reduce the number of flights that can be
@@ -587,7 +642,7 @@ NAR #88757, TRA #12200<br>
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 and TeleMega
+ 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.
@@ -611,7 +666,7 @@ NAR #88757, TRA #12200<br>
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="idp44629504"></a>9. Installation</h2></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49084400"></a>10. Installation</h2></div></div></div><p>
A typical installation involves attaching
only a suitable battery, a single pole switch for
power on/off, and two pairs of wires connecting e-matches for the
@@ -658,11 +713,11 @@ NAR #88757, TRA #12200<br>
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="idp44636240"></a>Chapter 5. System Operation</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp44636880">1. Firmware Modes </a></span></dt><dt><span class="section"><a href="#idp44705168">2. GPS </a></span></dt><dt><span class="section"><a href="#idp44707952">3. Controlling An Altimeter Over The Radio Link</a></span></dt><dt><span class="section"><a href="#idp44719248">4. Ground Testing </a></span></dt><dt><span class="section"><a href="#idp44722000">5. Radio Link </a></span></dt><dt><span class="section"><a href="#idp44726000">6. APRS</a></span></dt><dt><span class="section"><a href="#idp44747968">7. Configurable Parameters</a></span></dt><dd><dl><dt><span class="section"><a href="#idp44749888">7.1. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp44751936">7.2. Callsign</a></span></dt><dt><span class="section"><a href="#idp44753472">7.3. Telemetry/RDF/APRS Enable</a></span></dt><dt><span class="section"><a href="#idp44754768">7.4. APRS Interval</a></span></dt><dt><span class="section"><a href="#idp44756240">7.5. Apogee Delay</a></span></dt><dt><span class="section"><a href="#idp44758832">7.6. Apogee Lockout</a></span></dt><dt><span class="section"><a href="#idp44760560">7.7. Main Deployment Altitude</a></span></dt><dt><span class="section"><a href="#idp44762256">7.8. Maximum Flight Log</a></span></dt><dt><span class="section"><a href="#idp44764400">7.9. Ignite Mode</a></span></dt><dt><span class="section"><a href="#idp44766512">7.10. Pad Orientation</a></span></dt><dt><span class="section"><a href="#idp44768208">7.11. 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="idp44636880"></a>1. Firmware Modes </h2></div></div></div><p>
+ </p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp49091680"></a>Chapter 5. System Operation</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp49092320">1. Firmware Modes </a></span></dt><dt><span class="section"><a href="#idp49160720">2. GPS </a></span></dt><dt><span class="section"><a href="#idp49163504">3. Controlling An Altimeter Over The Radio Link</a></span></dt><dt><span class="section"><a href="#idp49174800">4. Ground Testing </a></span></dt><dt><span class="section"><a href="#idp49177552">5. Radio Link </a></span></dt><dt><span class="section"><a href="#idp49181552">6. APRS</a></span></dt><dt><span class="section"><a href="#idp49205872">7. Configurable Parameters</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49207792">7.1. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp49209840">7.2. Callsign</a></span></dt><dt><span class="section"><a href="#idp49211376">7.3. Telemetry/RDF/APRS Enable</a></span></dt><dt><span class="section"><a href="#idp49212672">7.4. Telemetry baud rate</a></span></dt><dt><span class="section"><a href="#idp49214240">7.5. APRS Interval</a></span></dt><dt><span class="section"><a href="#idp49215712">7.6. APRS SSID</a></span></dt><dt><span class="section"><a href="#idp49217056">7.7. Apogee Delay</a></span></dt><dt><span class="section"><a href="#idp49219648">7.8. Apogee Lockout</a></span></dt><dt><span class="section"><a href="#idp49221376">7.9. Main Deployment Altitude</a></span></dt><dt><span class="section"><a href="#idp49223072">7.10. Maximum Flight Log</a></span></dt><dt><span class="section"><a href="#idp49225216">7.11. Ignite Mode</a></span></dt><dt><span class="section"><a href="#idp49227328">7.12. Pad Orientation</a></span></dt><dt><span class="section"><a href="#idp49229568">7.13. Configurable Pyro Channels</a></span></dt></dl></dd></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49092320"></a>1. Firmware Modes </h2></div></div></div><p>
The AltOS firmware build for the altimeters has two
fundamental modes, &#8220;idle&#8221; and &#8220;flight&#8221;. Which of these modes
the firmware operates in is determined at start up time. For
- TeleMetrum and TeleMega, which have accelerometers, the mode is
+ 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 &#8220;nose up&#8221;, then
@@ -689,7 +744,7 @@ NAR #88757, TRA #12200<br>
mode. In the description of the beeping pattern, &#8220;dit&#8221; means a
short beep while "dah" means a long beep (three times as
long). &#8220;Brap&#8221; means a long dissonant tone.
- </p><div class="table"><a name="idp44642240"></a><p class="title"><b>Table 5.1. AltOS Modes</b></p><div class="table-contents"><table summary="AltOS Modes" border="1"><colgroup><col align="center" class="Mode Name"><col align="center" class="Letter"><col align="center" class="Beeps"><col align="center" class="Description"></colgroup><thead><tr><th align="center">Mode Name</th><th align="center">Abbreviation</th><th align="center">Beeps</th><th align="center">Description</th></tr></thead><tbody><tr><td align="center">Startup</td><td align="center">S</td><td align="center">battery voltage in decivolts</td><td align="center">
+ </p><div class="table"><a name="idp49097680"></a><p class="title"><b>Table 5.1. AltOS Modes</b></p><div class="table-contents"><table summary="AltOS Modes" border="1"><colgroup><col align="center" class="Mode Name"><col align="center" class="Letter"><col align="center" class="Beeps"><col align="center" class="Description"></colgroup><thead><tr><th align="center">Mode Name</th><th align="center">Abbreviation</th><th align="center">Beeps</th><th align="center">Description</th></tr></thead><tbody><tr><td align="center">Startup</td><td align="center">S</td><td align="center">battery voltage in decivolts</td><td align="center">
<p>
Calibrating sensors, detecting orientation.
</p>
@@ -763,7 +818,7 @@ NAR #88757, TRA #12200<br>
slower than the &#8220;no continuity tone&#8221;)
</p><p>
Here's a summary of all of the &#8220;pad&#8221; and &#8220;idle&#8221; mode indications.
- </p><div class="table"><a name="idp44679328"></a><p class="title"><b>Table 5.2. Pad/Idle Indications</b></p><div class="table-contents"><table summary="Pad/Idle Indications" border="1"><colgroup><col align="center" class="Name"><col align="center" class="Beeps"><col align="center" class="Description"></colgroup><thead><tr><th align="center">Name</th><th align="center">Beeps</th><th align="center">Description</th></tr></thead><tbody><tr><td align="center">Neither</td><td align="center">brap</td><td align="center">
+ </p><div class="table"><a name="idp49134768"></a><p class="title"><b>Table 5.2. Pad/Idle Indications</b></p><div class="table-contents"><table summary="Pad/Idle Indications" border="1"><colgroup><col align="center" class="Name"><col align="center" class="Beeps"><col align="center" class="Description"></colgroup><thead><tr><th align="center">Name</th><th align="center">Beeps</th><th align="center">Description</th></tr></thead><tbody><tr><td align="center">Neither</td><td align="center">brap</td><td align="center">
<p>
No continuity detected on either apogee or main
igniters.
@@ -798,7 +853,8 @@ NAR #88757, TRA #12200<br>
beep. The flight computer will continue to report landed mode
and beep out the maximum height until turned off.
</p><p>
- One &#8220;neat trick&#8221; of particular value when TeleMetrum or TeleMega are used with
+ One &#8220;neat trick&#8221; 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
@@ -830,7 +886,7 @@ NAR #88757, TRA #12200<br>
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="idp44705168"></a>2. GPS </h2></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49160720"></a>2. GPS </h2></div></div></div><p>
TeleMetrum and TeleMega include a complete GPS receiver. A
complete explanation of how GPS works is beyond the scope of
this manual, but the bottom line is that the GPS receiver
@@ -848,7 +904,7 @@ NAR #88757, TRA #12200<br>
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="idp44707952"></a>3. Controlling An Altimeter Over The Radio Link</h2></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49163504"></a>3. Controlling An Altimeter Over The Radio Link</h2></div></div></div><p>
One of the unique features of the Altus Metrum system is the
ability to create a two way command link between TeleDongle
and an altimeter using the digital radio transceivers
@@ -919,7 +975,7 @@ NAR #88757, TRA #12200<br>
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="idp44719248"></a>4. Ground Testing </h2></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49174800"></a>4. Ground Testing </h2></div></div></div><p>
An important aspect of preparing a rocket using electronic deployment
for flight is ground testing the recovery system. Thanks
to the bi-directional radio link central to the Altus Metrum system,
@@ -935,7 +991,7 @@ NAR #88757, TRA #12200<br>
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="idp44722000"></a>5. Radio Link </h2></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49177552"></a>5. Radio Link </h2></div></div></div><p>
Our flight computers all incorporate an RF transceiver, but
it's not a full duplex system... each end can only be transmitting or
receiving at any given moment. So we had to decide how to manage the
@@ -968,7 +1024,7 @@ NAR #88757, TRA #12200<br>
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="idp44726000"></a>6. APRS</h2></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49181552"></a>6. APRS</h2></div></div></div><p>
TeleMetrum v2.0 and TeleMega can send APRS if desired, and the
interval between APRS packets can be configured. As each APRS
packet takes a full second to transmit, we recommend an
@@ -987,16 +1043,24 @@ NAR #88757, TRA #12200<br>
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="idp44729008"></a><p class="title"><b>Table 5.3. Altus Metrum APRS Comments</b></p><div class="table-contents"><table summary="Altus Metrum APRS Comments" border="1"><colgroup><col align="center" class="Field"><col align="center" class="Example"><col align="center" class="Description"></colgroup><thead><tr><th align="center">Field</th><th align="center">Example</th><th align="center">Description</th></tr></thead><tbody><tr><td align="center">1</td><td align="center">L</td><td align="center">GPS Status U for unlocked, L for locked</td></tr><tr><td align="center">2</td><td align="center">6</td><td align="center">Number of Satellites in View</td></tr><tr><td align="center">3</td><td align="center">B4.0</td><td align="center">Altimeter Battery Voltage</td></tr><tr><td align="center">4</td><td align="center">A3.7</td><td align="center">Apogee Igniter Voltage</td></tr><tr><td align="center">5</td><td align="center">M3.7</td><td align="center">Main Igniter Voltage</td></tr></tbody></table></div></div><br class="table-break"><p>
+ </p><div class="table"><a name="idp49185360"></a><p class="title"><b>Table 5.3. Altus Metrum APRS Comments</b></p><div class="table-contents"><table summary="Altus Metrum APRS Comments" border="1"><colgroup><col align="center" class="Field"><col align="center" class="Example"><col align="center" class="Description"></colgroup><thead><tr><th align="center">Field</th><th align="center">Example</th><th align="center">Description</th></tr></thead><tbody><tr><td align="center">1</td><td align="center">L</td><td align="center">GPS Status U for unlocked, L for locked</td></tr><tr><td align="center">2</td><td align="center">6</td><td align="center">Number of Satellites in View</td></tr><tr><td align="center">3</td><td align="center">B4.0</td><td align="center">Altimeter Battery Voltage</td></tr><tr><td align="center">4</td><td align="center">A3.7</td><td align="center">Apogee Igniter Voltage</td></tr><tr><td align="center">5</td><td align="center">M3.7</td><td align="center">Main Igniter Voltage</td></tr><tr><td align="center">6</td><td align="center">1286</td><td align="center">Device Serial Number</td></tr></tbody></table></div></div><br class="table-break"><p>
Here's an example of an APRS comment showing GPS lock with 6
satellites in view, a primary battery at 4.0V, and
- apogee and main igniters both at 3.7V.
+ apogee and main igniters both at 3.7V from device 1286.
</p><pre class="screen">
- L6 B4.0 A3.7 M3.7
+ L6 B4.0 A3.7 M3.7 1286
</pre><p>
</p><p>
Make sure your primary battery is above 3.8V, any connected
@@ -1011,7 +1075,7 @@ NAR #88757, TRA #12200<br>
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="idp44747968"></a>7. Configurable Parameters</h2></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49205872"></a>7. Configurable Parameters</h2></div></div></div><p>
Configuring an Altus Metrum altimeter for flight is very
simple. Even on our baro-only TeleMini and EasyMini boards,
the use of a Kalman filter means there is no need to set a
@@ -1019,7 +1083,7 @@ NAR #88757, TRA #12200<br>
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="idp44749888"></a>7.1. Radio Frequency</h3></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49207792"></a>7.1. Radio Frequency</h3></div></div></div><p>
Altus Metrum boards support radio frequencies in the 70cm
band. By default, the configuration interface provides a
list of 10 &#8220;standard&#8221; frequencies in 100kHz channels starting at
@@ -1029,24 +1093,36 @@ NAR #88757, TRA #12200<br>
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="idp44751936"></a>7.2. Callsign</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49209840"></a>7.2. Callsign</h3></div></div></div><p>
This sets the callsign used for telemetry, APRS and the
packet link. For telemetry and APRS, this is used to
identify the device. For the packet link, the callsign must
match that configured in AltosUI or the link will not
work. This is to prevent accidental configuration of another
Altus Metrum flight computer operating on the same frequency nearby.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp44753472"></a>7.3. Telemetry/RDF/APRS Enable</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49211376"></a>7.3. Telemetry/RDF/APRS Enable</h3></div></div></div><p>
You can completely disable the radio while in flight, if
necessary. This doesn't disable the packet link in idle
mode.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp44754768"></a>7.4. APRS Interval</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49212672"></a>7.4. Telemetry baud rate</h3></div></div></div><p>
+ This sets the modulation bit rate for data transmission for
+ both telemetry and packet link mode. Lower bit
+ rates will increase range while reducing the amount of data
+ that can be sent and increasing battery consumption. All
+ telemetry is done using a rate 1/2 constraint 4 convolution
+ code, so the actual data transmission rate is 1/2 of the
+ modulation bit rate specified here.
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49214240"></a>7.5. APRS Interval</h3></div></div></div><p>
This selects how often APRS packets are transmitted. Set
this to zero to disable APRS without also disabling the
regular telemetry and RDF transmissions. As APRS takes a
full second to transmit a single position report, we
recommend sending packets no more than once every 5 seconds.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp44756240"></a>7.5. Apogee Delay</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49215712"></a>7.6. APRS SSID</h3></div></div></div><p>
+ This selects the SSID reported in APRS packets. By default,
+ it is set to the last digit of the serial number, but you
+ can change this to any value from 0 to 9.
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49217056"></a>7.7. Apogee Delay</h3></div></div></div><p>
Apogee delay is the number of seconds after the altimeter detects flight
apogee that the drogue charge should be fired. In most cases, this
should be left at the default of 0. However, if you are flying
@@ -1062,7 +1138,7 @@ NAR #88757, TRA #12200<br>
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="idp44758832"></a>7.6. Apogee Lockout</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49219648"></a>7.8. Apogee Lockout</h3></div></div></div><p>
Apogee lockout is the number of seconds after boost where
the flight computer will not fire the apogee charge, even if
the rocket appears to be at apogee. This is often called
@@ -1072,7 +1148,7 @@ NAR #88757, TRA #12200<br>
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="idp44760560"></a>7.7. Main Deployment Altitude</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49221376"></a>7.9. Main Deployment Altitude</h3></div></div></div><p>
By default, the altimeter will fire the main deployment charge at an
elevation of 250 meters (about 820 feet) above ground. We think this
is a good elevation for most air-frames, but feel free to change this
@@ -1081,7 +1157,7 @@ NAR #88757, TRA #12200<br>
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="idp44762256"></a>7.8. Maximum Flight Log</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49223072"></a>7.10. Maximum Flight Log</h3></div></div></div><p>
Changing this value will set the maximum amount of flight
log storage that an individual flight will use. The
available storage is divided into as many flights of the
@@ -1093,7 +1169,7 @@ NAR #88757, TRA #12200<br>
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="idp44764400"></a>7.9. Ignite Mode</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49225216"></a>7.11. Ignite Mode</h3></div></div></div><p>
Instead of firing one charge at apogee and another charge at
a fixed height above the ground, you can configure the
altimeter to fire both at apogee or both during
@@ -1104,8 +1180,8 @@ NAR #88757, TRA #12200<br>
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="idp44766512"></a>7.10. Pad Orientation</h3></div></div></div><p>
- TeleMetrum and TeleMega measure acceleration along the axis
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49227328"></a>7.12. Pad Orientation</h3></div></div></div><p>
+ TeleMetrum, TeleMega and EasyMega measure acceleration along the axis
of the board. Which way the board is oriented affects the
sign of the acceleration value. Instead of trying to guess
which way the board is mounted in the air frame, the
@@ -1114,9 +1190,9 @@ NAR #88757, TRA #12200<br>
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="idp44768208"></a>7.11. Configurable Pyro Channels</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49229568"></a>7.13. Configurable Pyro Channels</h3></div></div></div><p>
In addition to the usual Apogee and Main pyro channels,
- TeleMega has four additional channels that can be configured
+ 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
@@ -1141,7 +1217,7 @@ NAR #88757, TRA #12200<br>
height above the launch pad should be above or below
that value.
</p></li><li class="listitem"><p>
- Orientation. TeleMega contains a 3-axis gyroscope and
+ 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
@@ -1214,7 +1290,7 @@ NAR #88757, TRA #12200<br>
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="idp44790592"></a>Chapter 6. AltosUI</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp44794208">1. Monitor Flight</a></span></dt><dd><dl><dt><span class="section"><a href="#idp44806928">1.1. Launch Pad</a></span></dt><dt><span class="section"><a href="#idp44823216">1.2. Ascent</a></span></dt><dt><span class="section"><a href="#idp44828672">1.3. Descent</a></span></dt><dt><span class="section"><a href="#idp44835536">1.4. Landed</a></span></dt><dt><span class="section"><a href="#idp44841968">1.5. Table</a></span></dt><dt><span class="section"><a href="#idp44845552">1.6. Site Map</a></span></dt><dt><span class="section"><a href="#idp44852272">1.7. Ignitor</a></span></dt></dl></dd><dt><span class="section"><a href="#idp44856048">2. Save Flight Data</a></span></dt><dt><span class="section"><a href="#idp44860000">3. Replay Flight</a></span></dt><dt><span class="section"><a href="#idp44862032">4. Graph Data</a></span></dt><dd><dl><dt><span class="section"><a href="#idp44864416">4.1. Flight Graph</a></span></dt><dt><span class="section"><a href="#idp44868864">4.2. Configure Graph</a></span></dt><dt><span class="section"><a href="#idp44872528">4.3. Flight Statistics</a></span></dt><dt><span class="section"><a href="#idp44876048">4.4. Map</a></span></dt></dl></dd><dt><span class="section"><a href="#idp44879904">5. Export Data</a></span></dt><dd><dl><dt><span class="section"><a href="#idp44881472">5.1. Comma Separated Value Format</a></span></dt><dt><span class="section"><a href="#idp44883824">5.2. Keyhole Markup Language (for Google Earth)</a></span></dt></dl></dd><dt><span class="section"><a href="#idp44885312">6. Configure Altimeter</a></span></dt><dd><dl><dt><span class="section"><a href="#idp44897616">6.1. Main Deploy Altitude</a></span></dt><dt><span class="section"><a href="#idp44899184">6.2. Apogee Delay</a></span></dt><dt><span class="section"><a href="#idp44900800">6.3. Apogee Lockoug</a></span></dt><dt><span class="section"><a href="#idp44902528">6.4. Frequency</a></span></dt><dt><span class="section"><a href="#idp44904032">6.5. RF Calibration</a></span></dt><dt><span class="section"><a href="#idp44905680">6.6. Telemetry/RDF/APRS Enable</a></span></dt><dt><span class="section"><a href="#idp44906976">6.7. APRS Interval</a></span></dt><dt><span class="section"><a href="#idp44908544">6.8. Callsign</a></span></dt><dt><span class="section"><a href="#idp44909856">6.9. Maximum Flight Log Size</a></span></dt><dt><span class="section"><a href="#idp44911296">6.10. Ignitor Firing Mode</a></span></dt><dt><span class="section"><a href="#idp44918208">6.11. Pad Orientation</a></span></dt><dt><span class="section"><a href="#idp44923424">6.12. Beeper Frequency</a></span></dt><dt><span class="section"><a href="#idp44924880">6.13. Configure Pyro Channels</a></span></dt></dl></dd><dt><span class="section"><a href="#idp44931248">7. Configure AltosUI</a></span></dt><dd><dl><dt><span class="section"><a href="#idp44934752">7.1. Voice Settings</a></span></dt><dt><span class="section"><a href="#idp44939776">7.2. Log Directory</a></span></dt><dt><span class="section"><a href="#idp44941776">7.3. Callsign</a></span></dt><dt><span class="section"><a href="#idp44944400">7.4. Imperial Units</a></span></dt><dt><span class="section"><a href="#idp44945904">7.5. Font Size</a></span></dt><dt><span class="section"><a href="#idp44947184">7.6. Serial Debug</a></span></dt><dt><span class="section"><a href="#idp44948688">7.7. Manage Frequencies</a></span></dt></dl></dd><dt><span class="section"><a href="#idp44950320">8. Configure Groundstation</a></span></dt><dd><dl><dt><span class="section"><a href="#idp44961440">8.1. Frequency</a></span></dt><dt><span class="section"><a href="#idp44963008">8.2. Radio Calibration</a></span></dt></dl></dd><dt><span class="section"><a href="#idp44964640">9. Flash Image</a></span></dt><dt><span class="section"><a href="#idp44966272">10. Fire Igniter</a></span></dt><dt><span class="section"><a href="#idp44971904">11. Scan Channels</a></span></dt><dt><span class="section"><a href="#idp44975760">12. Load Maps</a></span></dt><dt><span class="section"><a href="#idp44989568">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>
+ </p></li></ul></div></div></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp49252176"></a>Chapter 6. AltosUI</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp49255792">1. Monitor Flight</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49268512">1.1. Launch Pad</a></span></dt><dt><span class="section"><a href="#idp49284800">1.2. Ascent</a></span></dt><dt><span class="section"><a href="#idp49290256">1.3. Descent</a></span></dt><dt><span class="section"><a href="#idp49297120">1.4. Landed</a></span></dt><dt><span class="section"><a href="#idp49303552">1.5. Table</a></span></dt><dt><span class="section"><a href="#idp49307136">1.6. Site Map</a></span></dt><dt><span class="section"><a href="#idp49313856">1.7. Ignitor</a></span></dt></dl></dd><dt><span class="section"><a href="#idp49317632">2. Save Flight Data</a></span></dt><dt><span class="section"><a href="#idp49321584">3. Replay Flight</a></span></dt><dt><span class="section"><a href="#idp49323616">4. Graph Data</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49326000">4.1. Flight Graph</a></span></dt><dt><span class="section"><a href="#idp49330448">4.2. Configure Graph</a></span></dt><dt><span class="section"><a href="#idp49334112">4.3. Flight Statistics</a></span></dt><dt><span class="section"><a href="#idp49337632">4.4. Map</a></span></dt></dl></dd><dt><span class="section"><a href="#idp49341488">5. Export Data</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49343056">5.1. Comma Separated Value Format</a></span></dt><dt><span class="section"><a href="#idp49345408">5.2. Keyhole Markup Language (for Google Earth)</a></span></dt></dl></dd><dt><span class="section"><a href="#idp49346896">6. Configure Altimeter</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49359200">6.1. Main Deploy Altitude</a></span></dt><dt><span class="section"><a href="#idp49360768">6.2. Apogee Delay</a></span></dt><dt><span class="section"><a href="#idp49362384">6.3. Apogee Lockoug</a></span></dt><dt><span class="section"><a href="#idp49364112">6.4. Frequency</a></span></dt><dt><span class="section"><a href="#idp49365616">6.5. RF Calibration</a></span></dt><dt><span class="section"><a href="#idp49367264">6.6. Telemetry/RDF/APRS Enable</a></span></dt><dt><span class="section"><a href="#idp49368560">6.7. Telemetry baud rate</a></span></dt><dt><span class="section"><a href="#idp49370128">6.8. APRS Interval</a></span></dt><dt><span class="section"><a href="#idp49371696">6.9. APRS SSID</a></span></dt><dt><span class="section"><a href="#idp49373024">6.10. Callsign</a></span></dt><dt><span class="section"><a href="#idp49374336">6.11. Maximum Flight Log Size</a></span></dt><dt><span class="section"><a href="#idp49375776">6.12. Ignitor Firing Mode</a></span></dt><dt><span class="section"><a href="#idp49382688">6.13. Pad Orientation</a></span></dt><dt><span class="section"><a href="#idp49387920">6.14. Beeper Frequency</a></span></dt><dt><span class="section"><a href="#idp49389376">6.15. Configure Pyro Channels</a></span></dt></dl></dd><dt><span class="section"><a href="#idp49395760">7. Configure AltosUI</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49399264">7.1. Voice Settings</a></span></dt><dt><span class="section"><a href="#idp49404288">7.2. Log Directory</a></span></dt><dt><span class="section"><a href="#idp49406288">7.3. Callsign</a></span></dt><dt><span class="section"><a href="#idp49408528">7.4. Imperial Units</a></span></dt><dt><span class="section"><a href="#idp49410032">7.5. Font Size</a></span></dt><dt><span class="section"><a href="#idp49411312">7.6. Serial Debug</a></span></dt><dt><span class="section"><a href="#idp49412816">7.7. Manage Frequencies</a></span></dt></dl></dd><dt><span class="section"><a href="#idp49414448">8. Configure Groundstation</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49425568">8.1. Frequency</a></span></dt><dt><span class="section"><a href="#idp49427136">8.2. RF Calibration</a></span></dt><dt><span class="section"><a href="#idp49428656">8.3. Telemetry Rate</a></span></dt></dl></dd><dt><span class="section"><a href="#idp49430128">9. Flash Image</a></span></dt><dt><span class="section"><a href="#idp49431776">10. Fire Igniter</a></span></dt><dt><span class="section"><a href="#idp49437408">11. Scan Channels</a></span></dt><dt><span class="section"><a href="#idp49441632">12. Load Maps</a></span></dt><dt><span class="section"><a href="#idp49455600">13. Monitor Idle</a></span></dt></dl></div><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="414"><tr><td><img src="altosui.png" width="414"></td></tr></table></div></div><p>
The AltosUI program provides a graphical user interface for
interacting with the Altus Metrum product family. AltosUI can
monitor telemetry data, configure devices and many other
@@ -1222,7 +1298,7 @@ NAR #88757, TRA #12200<br>
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="idp44794208"></a>1. Monitor Flight</h2></div><div><h3 class="subtitle">Receive, Record and Display Telemetry Data</h3></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49255792"></a>1. Monitor Flight</h2></div><div><h3 class="subtitle">Receive, Record and Display Telemetry Data</h3></div></div></div><p>
Selecting this item brings up a dialog box listing all of the
connected TeleDongle devices. When you choose one of these,
AltosUI will create a window to display telemetry data as
@@ -1269,7 +1345,7 @@ NAR #88757, TRA #12200<br>
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="idp44806928"></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>
+ </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49268512"></a>1.1. Launch Pad</h3></div></div></div><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="495"><tr><td><img src="launch-pad.png" width="495"></td></tr></table></div></div><p>
The 'Launch Pad' tab shows information used to decide when the
rocket is ready for flight. The first elements include red/green
indicators, if any of these is red, you'll want to evaluate
@@ -1319,7 +1395,7 @@ NAR #88757, TRA #12200<br>
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="idp44823216"></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>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49284800"></a>1.2. Ascent</h3></div></div></div><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="495"><tr><td><img src="ascent.png" width="495"></td></tr></table></div></div><p>
This tab is shown during Boost, Fast and Coast
phases. The information displayed here helps monitor the
rocket as it heads towards apogee.
@@ -1338,7 +1414,7 @@ NAR #88757, TRA #12200<br>
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="idp44828672"></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>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49290256"></a>1.3. Descent</h3></div></div></div><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="495"><tr><td><img src="descent.png" width="495"></td></tr></table></div></div><p>
Once the rocket has reached apogee and (we hope) activated the
apogee charge, attention switches to tracking the rocket on
the way back to the ground, and for dual-deploy flights,
@@ -1367,7 +1443,7 @@ NAR #88757, TRA #12200<br>
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="idp44835536"></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>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49297120"></a>1.4. Landed</h3></div></div></div><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="495"><tr><td><img src="landed.png" width="495"></td></tr></table></div></div><p>
Once the rocket is on the ground, attention switches to
recovery. While the radio signal is often lost once the
rocket is on the ground, the last reported GPS position is
@@ -1396,13 +1472,13 @@ NAR #88757, TRA #12200<br>
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="idp44841968"></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>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49303552"></a>1.5. Table</h3></div></div></div><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="495"><tr><td><img src="table.png" width="495"></td></tr></table></div></div><p>
The table view shows all of the data available from the
flight computer. Probably the most useful data on
this tab is the detailed GPS information, which includes
horizontal dilution of precision information, and
information about the signal being received from the satellites.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp44845552"></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>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49307136"></a>1.6. Site Map</h3></div></div></div><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="495"><tr><td><img src="site-map.png" width="495"></td></tr></table></div></div><p>
When the TeleMetrum has a GPS fix, the Site Map tab will map
the rocket's position to make it easier for you to locate the
rocket, both while it is in the air, and when it has landed. The
@@ -1429,14 +1505,14 @@ NAR #88757, TRA #12200<br>
</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="idp44852272"></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>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49313856"></a>1.7. Ignitor</h3></div></div></div><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="495"><tr><td><img src="ignitor.png" width="495"></td></tr></table></div></div><p>
TeleMega includes four additional programmable pyro
channels. The Ignitor tab shows whether each of them has
continuity. If an ignitor has a low resistance, then the
voltage measured here will be close to the pyro battery
voltage. A value greater than 3.2V is required for a 'GO'
status.
- </p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp44856048"></a>2. Save Flight Data</h2></div></div></div><p>
+ </p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49317632"></a>2. Save Flight Data</h2></div></div></div><p>
The altimeter records flight data to its internal flash memory.
TeleMetrum data is recorded at a much higher rate than the telemetry
system can handle, and is not subject to radio drop-outs. As
@@ -1465,7 +1541,7 @@ NAR #88757, TRA #12200<br>
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="idp44860000"></a>3. Replay Flight</h2></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49321584"></a>3. Replay Flight</h2></div></div></div><p>
Select this button and you are prompted to select a flight
record file, either a .telem file recording telemetry data or a
.eeprom file containing flight data saved from the altimeter
@@ -1474,7 +1550,7 @@ NAR #88757, TRA #12200<br>
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="idp44862032"></a>4. Graph Data</h2></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49323616"></a>4. Graph Data</h2></div></div></div><p>
Select this button and you are prompted to select a flight
record file, either a .telem file recording telemetry data or a
.eeprom file containing flight data saved from
@@ -1486,7 +1562,7 @@ NAR #88757, TRA #12200<br>
</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="idp44864416"></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>
+ </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49326000"></a>4.1. Flight Graph</h3></div></div></div><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="540"><tr><td><img src="graph.png" width="540"></td></tr></table></div></div><p>
By default, the graph contains acceleration (blue),
velocity (green) and altitude (red).
</p><p>
@@ -1496,18 +1572,18 @@ NAR #88757, TRA #12200<br>
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="idp44868864"></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>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49330448"></a>4.2. Configure Graph</h3></div></div></div><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="540"><tr><td><img src="graph-configure.png" width="540"></td></tr></table></div></div><p>
This selects which graph elements to show, and, at the
very bottom, lets you switch between metric and
imperial units
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp44872528"></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>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49334112"></a>4.3. Flight Statistics</h3></div></div></div><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="540"><tr><td><img src="graph-stats.png" width="540"></td></tr></table></div></div><p>
Shows overall data computed from the flight.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp44876048"></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>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49337632"></a>4.4. Map</h3></div></div></div><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="540"><tr><td><img src="graph-map.png" width="540"></td></tr></table></div></div><p>
Shows a satellite image of the flight area overlaid
with the path of the flight. The red concentric
circles mark the launch pad, the black concentric
circles mark the landing location.
- </p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp44879904"></a>5. Export Data</h2></div></div></div><p>
+ </p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49341488"></a>5. Export Data</h2></div></div></div><p>
This tool takes the raw data files and makes them available for
external analysis. When you select this button, you are prompted to
select a flight data file, which can be either a .eeprom or .telem.
@@ -1516,7 +1592,7 @@ NAR #88757, TRA #12200<br>
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="idp44881472"></a>5.1. Comma Separated Value Format</h3></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49343056"></a>5.1. Comma Separated Value Format</h3></div></div></div><p>
This is a text file containing the data in a form suitable for
import into a spreadsheet or other external data analysis
tool. The first few lines of the file contain the version and
@@ -1530,11 +1606,11 @@ NAR #88757, TRA #12200<br>
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="idp44883824"></a>5.2. Keyhole Markup Language (for Google Earth)</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49345408"></a>5.2. Keyhole Markup Language (for Google Earth)</h3></div></div></div><p>
This is the format used by Google Earth to provide an overlay
within that application. With this, you can use Google Earth to
see the whole flight path in 3D.
- </p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp44885312"></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>
+ </p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49346896"></a>6. Configure Altimeter</h2></div></div></div><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="324"><tr><td><img src="configure-altimeter.png" width="324"></td></tr></table></div></div><p>
Select this button and then select either an altimeter or
TeleDongle Device from the list provided. Selecting a TeleDongle
device will use the radio link to configure a remote altimeter.
@@ -1562,14 +1638,14 @@ NAR #88757, TRA #12200<br>
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="idp44897616"></a>6.1. Main Deploy Altitude</h3></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49359200"></a>6.1. Main Deploy Altitude</h3></div></div></div><p>
This sets the altitude (above the recorded pad altitude) at
which the 'main' igniter will fire. The drop-down menu shows
some common values, but you can edit the text directly and
choose whatever you like. If the apogee charge fires below
this altitude, then the main charge will fire two seconds
after the apogee charge fires.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp44899184"></a>6.2. Apogee Delay</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49360768"></a>6.2. Apogee Delay</h3></div></div></div><p>
When flying redundant electronics, it's often important to
ensure that multiple apogee charges don't fire at precisely
the same time, as that can over pressurize the apogee deployment
@@ -1577,7 +1653,7 @@ NAR #88757, TRA #12200<br>
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="idp44900800"></a>6.3. Apogee Lockoug</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49362384"></a>6.3. Apogee Lockoug</h3></div></div></div><p>
Apogee lockout is the number of seconds after boost where
the flight computer will not fire the apogee charge, even if
the rocket appears to be at apogee. This is often called
@@ -1587,13 +1663,13 @@ NAR #88757, TRA #12200<br>
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="idp44902528"></a>6.4. Frequency</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49364112"></a>6.4. Frequency</h3></div></div></div><p>
This configures which of the frequencies to use for both
telemetry and packet command mode. Note that if you set this
value via packet command mode, the TeleDongle frequency will
also be automatically reconfigured to match so that
communication will continue afterwards.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp44904032"></a>6.5. RF Calibration</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49365616"></a>6.5. RF Calibration</h3></div></div></div><p>
The radios in every Altus Metrum device are calibrated at the
factory to ensure that they transmit and receive on the
specified frequency. If you need to you can adjust the calibration
@@ -1601,11 +1677,19 @@ NAR #88757, TRA #12200<br>
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="idp44905680"></a>6.6. Telemetry/RDF/APRS Enable</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49367264"></a>6.6. Telemetry/RDF/APRS Enable</h3></div></div></div><p>
Enables the radio for transmission during flight. When
disabled, the radio will not transmit anything during flight
at all.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp44906976"></a>6.7. APRS Interval</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49368560"></a>6.7. Telemetry baud rate</h3></div></div></div><p>
+ This sets the modulation bit rate for data transmission for
+ both telemetry and packet link mode. Lower bit
+ rates will increase range while reducing the amount of data
+ that can be sent and increasing battery consumption. All
+ telemetry is done using a rate 1/2 constraint 4 convolution
+ code, so the actual data transmission rate is 1/2 of the
+ modulation bit rate specified here.
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49370128"></a>6.8. APRS Interval</h3></div></div></div><p>
How often to transmit GPS information via APRS (in
seconds). When set to zero, APRS transmission is
disabled. This option is available on TeleMetrum v2 and
@@ -1613,15 +1697,19 @@ NAR #88757, TRA #12200<br>
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="idp44908544"></a>6.8. Callsign</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49371696"></a>6.9. APRS SSID</h3></div></div></div><p>
+ Which SSID to report in APRS packets. By default, this is
+ set to the last digit of the serial number, but can be
+ configured to any value from 0 to 9.
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49373024"></a>6.10. Callsign</h3></div></div></div><p>
This sets the call sign included in each telemetry packet. Set this
as needed to conform to your local radio regulations.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp44909856"></a>6.9. Maximum Flight Log Size</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49374336"></a>6.11. Maximum Flight Log Size</h3></div></div></div><p>
This sets the space (in kilobytes) allocated for each flight
log. The available space will be divided into chunks of this
size. A smaller value will allow more flights to be stored,
a larger value will record data from longer flights.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp44911296"></a>6.10. Ignitor Firing Mode</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49375776"></a>6.12. Ignitor Firing Mode</h3></div></div></div><p>
This configuration parameter allows the two standard ignitor
channels (Apogee and Main) to be used in different
configurations.
@@ -1640,9 +1728,9 @@ NAR #88757, TRA #12200<br>
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="idp44918208"></a>6.11. Pad Orientation</h3></div></div></div><p>
- Because they include accelerometers, TeleMetrum and
- TeleMega are sensitive to the orientation of the board. By
+ </p></dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49382688"></a>6.13. Pad Orientation</h3></div></div></div><p>
+ Because they include accelerometers, TeleMetrum,
+ TeleMega and EasyMega are sensitive to the orientation of the board. By
default, they expect the antenna end to point forward. This
parameter allows that default to be changed, permitting the
board to be mounted with the antenna pointing aft instead.
@@ -1654,15 +1742,15 @@ NAR #88757, TRA #12200<br>
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="idp44923424"></a>6.12. Beeper Frequency</h3></div></div></div><p>
+ </p></dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49387920"></a>6.14. Beeper Frequency</h3></div></div></div><p>
The beeper on all Altus Metrum flight computers works best
at 4000Hz, however if you have more than one flight computer
in a single airframe, having all of them sound at the same
frequency can be confusing. This parameter lets you adjust
the base beeper frequency value.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp44924880"></a>6.13. 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>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49389376"></a>6.15. Configure Pyro Channels</h3></div></div></div><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="540"><tr><td><img src="configure-pyro.png" width="540"></td></tr></table></div></div><p>
This opens a separate window to configure the additional
- pyro channels available on TeleMega. One column is
+ 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
@@ -1684,9 +1772,9 @@ NAR #88757, TRA #12200<br>
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="idp44931248"></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>
+ </p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49395760"></a>7. Configure AltosUI</h2></div></div></div><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="216"><tr><td><img src="configure-altosui.png" width="216"></td></tr></table></div></div><p>
This button presents a dialog so that you can configure the AltosUI global settings.
- </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp44934752"></a>7.1. Voice Settings</h3></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49399264"></a>7.1. Voice Settings</h3></div></div></div><p>
AltosUI provides voice announcements during flight so that you
can keep your eyes on the sky and still get information about
the current flight status. However, sometimes you don't want
@@ -1695,7 +1783,7 @@ NAR #88757, TRA #12200<br>
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="idp44939776"></a>7.2. Log Directory</h3></div></div></div><p>
+ </p></dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49404288"></a>7.2. Log Directory</h3></div></div></div><p>
AltosUI logs all telemetry data and saves all TeleMetrum flash
data to this directory. This directory is also used as the
staring point when selecting data files for display or export.
@@ -1703,7 +1791,7 @@ NAR #88757, TRA #12200<br>
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="idp44941776"></a>7.3. Callsign</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49406288"></a>7.3. Callsign</h3></div></div></div><p>
This value is transmitted in each command packet sent from
TeleDongle and received from an altimeter. It is not used in
telemetry mode, as the callsign configured in the altimeter board
@@ -1716,40 +1804,40 @@ NAR #88757, TRA #12200<br>
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="idp44944400"></a>7.4. Imperial Units</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49408528"></a>7.4. Imperial Units</h3></div></div></div><p>
This switches between metric units (meters) and imperial
units (feet and miles). This affects the display of values
use during flight monitoring, configuration, data graphing
and all of the voice announcements. It does not change the
units used when exporting to CSV files, those are always
produced in metric units.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp44945904"></a>7.5. Font Size</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49410032"></a>7.5. Font Size</h3></div></div></div><p>
Selects the set of fonts used in the flight monitor
window. Choose between the small, medium and large sets.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp44947184"></a>7.6. Serial Debug</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49411312"></a>7.6. Serial Debug</h3></div></div></div><p>
This causes all communication with a connected device to be
dumped to the console from which AltosUI was started. If
you've started it from an icon or menu entry, the output
will simply be discarded. This mode can be useful to debug
various serial communication issues.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp44948688"></a>7.7. Manage Frequencies</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49412816"></a>7.7. Manage Frequencies</h3></div></div></div><p>
This brings up a dialog where you can configure the set of
frequencies shown in the various frequency menus. You can
add as many as you like, or even reconfigure the default
set. Changing this list does not affect the frequency
settings of any devices, it only changes the set of
frequencies shown in the menus.
- </p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp44950320"></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 Device from the list provided.
+ </p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49414448"></a>8. Configure Groundstation</h2></div></div></div><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="279"><tr><td><img src="configure-groundstation.png" width="279"></td></tr></table></div></div><p>
+ Select this button and then select a TeleDongle or TeleBT Device from the list provided.
</p><p>
The first few lines of the dialog provide information about the
connected device, including the product name,
software version and hardware serial number. Below that are the
individual configuration entries.
</p><p>
- Note that the TeleDongle itself doesn't save any configuration
+ 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 TeleDongle to
+ 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>
@@ -1766,28 +1854,32 @@ NAR #88757, TRA #12200<br>
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="idp44961440"></a>8.1. Frequency</h3></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49425568"></a>8.1. Frequency</h3></div></div></div><p>
This configures the frequency to use for both telemetry and
packet command mode. Set this before starting any operation
involving packet command mode so that it will use the right
frequency. Telemetry monitoring mode also provides a menu to
change the frequency, and that menu also sets the same Java
preference value used here.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp44963008"></a>8.2. Radio Calibration</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49427136"></a>8.2. RF Calibration</h3></div></div></div><p>
The radios in every Altus Metrum device are calibrated at the
factory to ensure that they transmit and receive on the
- specified frequency. To change a TeleDongle's calibration,
+ 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><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp44964640"></a>9. Flash Image</h2></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49428656"></a>8.3. Telemetry Rate</h3></div></div></div><p>
+ This lets you match the telemetry and packet link rate from
+ the transmitter. If they don't match, the device won't
+ receive any data.
+ </p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49430128"></a>9. Flash Image</h2></div></div></div><p>
This reprograms Altus Metrum devices with new
firmware. TeleMetrum v1.x, TeleDongle, TeleMini and TeleBT are
all reprogrammed by using another similar unit as a
- programming dongle (pair programming). TeleMega, TeleMetrum v2
+ programming dongle (pair programming). TeleMega, EasyMega, TeleMetrum v2
and EasyMini are all programmed directly over their USB ports
(self programming). Please read the directions for flashing
devices in the Updating Device Firmware chapter below.
- </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp44966272"></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>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49431776"></a>10. Fire Igniter</h2></div></div></div><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="108"><tr><td><img src="fire-igniter.png" width="108"></td></tr></table></div></div><p>
This activates the igniter circuits in the flight computer to help
test recovery systems deployment. Because this command can operate
over the Packet Command Link, you can prepare the rocket as
@@ -1807,14 +1899,14 @@ NAR #88757, TRA #12200<br>
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="idp44971904"></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>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49437408"></a>11. Scan Channels</h2></div></div></div><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="288"><tr><td><img src="scan-channels.png" width="288"></td></tr></table></div></div><p>
This listens for telemetry packets on all of the configured
frequencies, displaying information about each device it
- receives a packet from. You can select which of the three
- telemetry formats should be tried; by default, it only listens
- for the standard telemetry packets used in v1.0 and later
+ 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="idp44975760"></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>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49441632"></a>12. Load Maps</h2></div></div></div><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="468"><tr><td><img src="load-maps.png" width="468"></td></tr></table></div></div><p>
Before heading out to a new launch site, you can use this to
load satellite images in case you don't have internet
connectivity at the site. This loads a fairly large area
@@ -1859,7 +1951,7 @@ NAR #88757, TRA #12200<br>
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="idp44989568"></a>13. Monitor Idle</h2></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49455600"></a>13. Monitor Idle</h2></div></div></div><p>
This brings up a dialog similar to the Monitor Flight UI,
except it works with the altimeter in &#8220;idle&#8221; mode by sending
query commands to discover the current state rather than
@@ -1868,7 +1960,7 @@ NAR #88757, TRA #12200<br>
callsigns match exactly. If you can receive telemetry, but
cannot manage to run Monitor Idle, then it's very likely that
your callsigns are different in some way.
- </p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp44991664"></a>Chapter 7. AltosDroid</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp44994048">1. Installing AltosDroid</a></span></dt><dt><span class="section"><a href="#idp44995984">2. Connecting to TeleBT</a></span></dt><dt><span class="section"><a href="#idp44997984">3. Configuring AltosDroid</a></span></dt><dt><span class="section"><a href="#idp44999440">4. AltosDroid Flight Monitoring</a></span></dt><dd><dl><dt><span class="section"><a href="#idp45000752">4.1. Pad</a></span></dt></dl></dd><dt><span class="section"><a href="#idp45014304">5. Downloading Flight Logs</a></span></dt></dl></div><p>
+ </p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp49457696"></a>Chapter 7. AltosDroid</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp49460080">1. Installing AltosDroid</a></span></dt><dt><span class="section"><a href="#idp49462016">2. Connecting to TeleBT</a></span></dt><dt><span class="section"><a href="#idp49464016">3. Configuring AltosDroid</a></span></dt><dt><span class="section"><a href="#idp49465472">4. AltosDroid Flight Monitoring</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49466784">4.1. Pad</a></span></dt></dl></dd><dt><span class="section"><a href="#idp49480336">5. Downloading Flight Logs</a></span></dt></dl></div><p>
AltosDroid provides the same flight monitoring capabilities as
AltosUI, but runs on Android devices and is designed to connect
to a TeleBT receiver over Bluetooth&#8482;. AltosDroid monitors
@@ -1879,14 +1971,14 @@ NAR #88757, TRA #12200<br>
This manual will explain how to configure AltosDroid, connect
to TeleBT, operate the flight monitoring interface and describe
what the displayed data means.
- </p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp44994048"></a>1. Installing AltosDroid</h2></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49460080"></a>1. Installing AltosDroid</h2></div></div></div><p>
AltosDroid is available from the Google Play store. To install
it on your Android device, open the Google Play Store
application and search for &#8220;altosdroid&#8221;. Make sure you don't
have a space between &#8220;altos&#8221; and &#8220;droid&#8221; 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="idp44995984"></a>2. Connecting to TeleBT</h2></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49462016"></a>2. Connecting to TeleBT</h2></div></div></div><p>
Press the Android 'Menu' button or soft-key to see the
configuration options available. Select the 'Connect a device'
option and then the 'Scan for devices' entry at the bottom to
@@ -1896,19 +1988,19 @@ NAR #88757, TRA #12200<br>
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="idp44997984"></a>3. Configuring AltosDroid</h2></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49464016"></a>3. Configuring AltosDroid</h2></div></div></div><p>
The only configuration option available for AltosDroid is
which frequency to listen on. Press the Android 'Menu' button
or soft-key and pick the 'Select radio frequency' entry. That
brings up a menu of pre-set radio frequencies; pick the one
which matches your altimeter.
- </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp44999440"></a>4. AltosDroid Flight Monitoring</h2></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49465472"></a>4. AltosDroid Flight Monitoring</h2></div></div></div><p>
AltosDroid is designed to mimic the AltosUI flight monitoring
display, providing separate tabs for each stage of your rocket
flight along with a tab containing a map of the local area
with icons marking the current location of the altimeter and
the Android device.
- </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp45000752"></a>4.1. Pad</h3></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49466784"></a>4.1. Pad</h3></div></div></div><p>
The 'Launch Pad' tab shows information used to decide when the
rocket is ready for flight. The first elements include red/green
indicators, if any of these is red, you'll want to evaluate
@@ -1956,26 +2048,26 @@ NAR #88757, TRA #12200<br>
The Launchpad tab also shows the computed launch pad position
and altitude, averaging many reported positions to improve the
accuracy of the fix.
- </p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp45014304"></a>5. Downloading Flight Logs</h2></div></div></div><p>
+ </p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49480336"></a>5. Downloading Flight Logs</h2></div></div></div><p>
AltosDroid always saves every bit of telemetry data it
receives. To download that to a computer for use with AltosUI,
simply remove the SD card from your Android device, or connect
your device to your computer's USB port and browse the files
on that device. You will find '.telem' files in the TeleMetrum
directory that will work with AltosUI directly.
- </p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp45015968"></a>Chapter 8. Using Altus Metrum Products</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp45016608">1. Being Legal</a></span></dt><dt><span class="section"><a href="#idp45018512">2. In the Rocket</a></span></dt><dt><span class="section"><a href="#idp45020976">3. On the Ground</a></span></dt><dt><span class="section"><a href="#idp45034288">4. Data Analysis</a></span></dt><dt><span class="section"><a href="#idp45036832">5. Future Plans</a></span></dt></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp45016608"></a>1. Being Legal</h2></div></div></div><p>
+ </p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp49482000"></a>Chapter 8. Using Altus Metrum Products</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp49482640">1. Being Legal</a></span></dt><dt><span class="section"><a href="#idp49484544">2. In the Rocket</a></span></dt><dt><span class="section"><a href="#idp49487072">3. On the Ground</a></span></dt><dt><span class="section"><a href="#idp49500464">4. Data Analysis</a></span></dt><dt><span class="section"><a href="#idp49503008">5. Future Plans</a></span></dt></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49482640"></a>1. Being Legal</h2></div></div></div><p>
First off, in the US, you need an <a class="ulink" href="http://www.altusmetrum.org/Radio/" target="_top">amateur radio license</a> or
other authorization to legally operate the radio transmitters that are part
of our products.
- </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp45018512"></a>2. In the Rocket</h2></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49484544"></a>2. In the Rocket</h2></div></div></div><p>
In the rocket itself, you just need a flight computer and
a single-cell, 3.7 volt nominal Li-Po rechargeable battery. An
850mAh battery weighs less than a 9V alkaline battery, and will
- run a TeleMetrum or TeleMega for hours.
+ 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.
+ choice for use with TeleMini or EasyMini.
</p><p>
- By default, we ship flight computers with a simple wire antenna.
+ 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
@@ -1983,7 +2075,7 @@ NAR #88757, TRA #12200<br>
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="idp45020976"></a>3. On the Ground</h2></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49487072"></a>3. On the Ground</h2></div></div></div><p>
To receive the data stream from the rocket, you need an antenna and short
feed-line connected to one of our <a class="ulink" href="http://www.altusmetrum.org/TeleDongle/" target="_top">TeleDongle</a> units. If possible, use an SMA to BNC
adapter instead of feedline between the antenna feedpoint and
@@ -2020,8 +2112,8 @@ NAR #88757, TRA #12200<br>
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 VX-7R, Bdale has a Baofung UV-5R
- which isn't as nice, but was a whole lot cheaper.
+ 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>
@@ -2045,7 +2137,7 @@ NAR #88757, TRA #12200<br>
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="idp45034288"></a>4. Data Analysis</h2></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49500464"></a>4. Data Analysis</h2></div></div></div><p>
Our software makes it easy to log the data from each flight, both the
telemetry received during the flight itself, and the more
complete data log recorded in the flash memory on the altimeter
@@ -2060,13 +2152,10 @@ NAR #88757, TRA #12200<br>
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="idp45036832"></a>5. Future Plans</h2></div></div></div><p>
- We've designed a simple GPS based radio tracker called TeleGPS.
- If all goes well, we hope to introduce this in the first
- half of 2014.
- </p><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49503008"></a>5. Future Plans</h2></div></div></div><p>
We have designed and prototyped several &#8220;companion boards&#8221; that
- can attach to the companion connector on TeleMetrum and TeleMega
+ 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
@@ -2083,14 +2172,14 @@ NAR #88757, TRA #12200<br>
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="idp45041568"></a>Chapter 9. Altimeter Installation Recommendations</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp45043024">1. Mounting the Altimeter</a></span></dt><dt><span class="section"><a href="#idp45047856">2. Dealing with the Antenna</a></span></dt><dt><span class="section"><a href="#idp45053952">3. Preserving GPS Reception</a></span></dt><dt><span class="section"><a href="#idp45058736">4. Radio Frequency Interference</a></span></dt><dt><span class="section"><a href="#idp45066304">5. The Barometric Sensor</a></span></dt><dt><span class="section"><a href="#idp45069456">6. Ground Testing</a></span></dt></dl></div><p>
+ </p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp49506848"></a>Chapter 9. Altimeter Installation Recommendations</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp49508304">1. Mounting the Altimeter</a></span></dt><dt><span class="section"><a href="#idp49513136">2. Dealing with the Antenna</a></span></dt><dt><span class="section"><a href="#idp49518704">3. Preserving GPS Reception</a></span></dt><dt><span class="section"><a href="#idp49523488">4. Radio Frequency Interference</a></span></dt><dt><span class="section"><a href="#idp49531056">5. The Barometric Sensor</a></span></dt><dt><span class="section"><a href="#idp49533856">6. Ground Testing</a></span></dt></dl></div><p>
Building high-power rockets that fly safely is hard enough. Mix
in some sophisticated electronics and a bunch of radio energy
and some creativity and/or compromise may be required. This chapter
contains some suggestions about how to install Altus Metrum
products into a rocket air-frame, including how to safely and
reliably mix a variety of electronics into the same air-frame.
- </p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp45043024"></a>1. Mounting the Altimeter</h2></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49508304"></a>1. Mounting the Altimeter</h2></div></div></div><p>
The first consideration is to ensure that the altimeter is
securely fastened to the air-frame. For most of our products, we
prefer nylon standoffs and nylon screws; they're good to at least 50G
@@ -2102,15 +2191,15 @@ NAR #88757, TRA #12200<br>
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 and
- TeleMega are aligned precisely along the axis of
+ 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="idp45047856"></a>2. Dealing with the Antenna</h2></div></div></div><p>
+ </p></li></ol></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49513136"></a>2. Dealing with the Antenna</h2></div></div></div><p>
The antenna supplied is just a piece of solid, insulated,
wire. If it gets damaged or broken, it can be easily
replaced. It should be kept straight and not cut; bending or
@@ -2153,7 +2242,7 @@ NAR #88757, TRA #12200<br>
SMA connector, and then run 50&#937; 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="idp45053952"></a>3. Preserving GPS Reception</h2></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49518704"></a>3. Preserving GPS Reception</h2></div></div></div><p>
The GPS antenna and receiver used in TeleMetrum and TeleMega is
highly sensitive and normally have no trouble tracking enough
satellites to provide accurate position information for
@@ -2172,7 +2261,7 @@ NAR #88757, TRA #12200<br>
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="idp45058736"></a>4. Radio Frequency Interference</h2></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49523488"></a>4. Radio Frequency Interference</h2></div></div></div><p>
Any altimeter will generate RFI; the digital circuits use
high-frequency clocks that spray radio interference across a
wide band. Altus Metrum altimeters generate intentional radio
@@ -2210,7 +2299,7 @@ NAR #88757, TRA #12200<br>
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="idp45066304"></a>5. The Barometric Sensor</h2></div></div></div><p>
+ </p></li></ul></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49531056"></a>5. The Barometric Sensor</h2></div></div></div><p>
Altusmetrum altimeters measure altitude with a barometric
sensor, essentially measuring the amount of air above the
rocket to figure out how high it is. A large number of
@@ -2228,7 +2317,7 @@ NAR #88757, TRA #12200<br>
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="idp45069456"></a>6. Ground Testing</h2></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49533856"></a>6. Ground Testing</h2></div></div></div><p>
The most important aspect of any installation is careful
ground testing. Bringing an air-frame up to the LCO table which
hasn't been ground tested can lead to delays or ejection
@@ -2250,10 +2339,10 @@ NAR #88757, TRA #12200<br>
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="idp45072624"></a>Chapter 10. Updating Device Firmware</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp45076640">1.
- Updating TeleMega, TeleMetrum v2 or EasyMini Firmware
- </a></span></dt><dd><dl><dt><span class="section"><a href="#idp45085696">1.1. Recovering From Self-Flashing Failure</a></span></dt></dl></dd><dt><span class="section"><a href="#idp45094672">2. Pair Programming</a></span></dt><dt><span class="section"><a href="#idp45096112">3. Updating TeleMetrum v1.x Firmware</a></span></dt><dt><span class="section"><a href="#idp45109648">4. Updating TeleMini Firmware</a></span></dt><dt><span class="section"><a href="#idp45123200">5. Updating TeleDongle Firmware</a></span></dt></dl></div><p>
- TeleMega, TeleMetrum v2 and EasyMini are all programmed directly
+ </p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp49537024"></a>Chapter 10. Updating Device Firmware</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp49541072">1.
+ Updating TeleMega, TeleMetrum v2, EasyMega or EasyMini Firmware
+ </a></span></dt><dd><dl><dt><span class="section"><a href="#idp49550144">1.1. Recovering From Self-Flashing Failure</a></span></dt></dl></dd><dt><span class="section"><a href="#idp49568720">2. Pair Programming</a></span></dt><dt><span class="section"><a href="#idp49570160">3. Updating TeleMetrum v1.x Firmware</a></span></dt><dt><span class="section"><a href="#idp49583360">4. Updating TeleMini Firmware</a></span></dt><dt><span class="section"><a href="#idp49596912">5. Updating TeleDongle Firmware</a></span></dt></dl></div><p>
+ TeleMega, TeleMetrum v2, EasyMega and EasyMini are all programmed directly
over their USB connectors (self programming). TeleMetrum v1, TeleMini and
TeleDongle are all programmed by using another device as a
programmer (pair programming). It's important to recognize which
@@ -2273,10 +2362,10 @@ NAR #88757, TRA #12200<br>
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 and EasyMini)
+ 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="idp45076640"></a>1. 
- Updating TeleMega, TeleMetrum v2 or EasyMini Firmware
+ </p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49541072"></a>1. 
+ Updating TeleMega, TeleMetrum v2, EasyMega or EasyMini Firmware
</h2></div></div></div><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>
Attach a battery and power switch to the target
device. Power up the device.
@@ -2302,7 +2391,7 @@ NAR #88757, TRA #12200<br>
</p></li><li class="listitem"><p>
Verify that the device is working by using the 'Configure
Altimeter' item to check over the configuration.
- </p></li></ol></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp45085696"></a>1.1. Recovering From Self-Flashing Failure</h3></div></div></div><p>
+ </p></li></ol></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49550144"></a>1.1. Recovering From Self-Flashing Failure</h3></div></div></div><p>
If the firmware loading fails, it can leave the device
unable to boot. Not to worry, you can force the device to
start the boot loader instead, which will let you try to
@@ -2319,6 +2408,14 @@ NAR #88757, TRA #12200<br>
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
@@ -2333,13 +2430,33 @@ NAR #88757, TRA #12200<br>
by the square pad around it, and then the pins could
sequentially across the board, making Pin 6 the one on the
other end of the row.
- </p></dd></dl></div></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp45094672"></a>2. Pair Programming</h2></div></div></div><p>
+ </p></dd></dl></div><p>
+ Once you've located the right pins:
+ </p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>
+ Turn the altimeter power off.
+ </p></li><li class="listitem"><p>
+ Connect a battery.
+ </p></li><li class="listitem"><p>
+ Connect the indicated terminals together with a short
+ piece of wire. Take care not to accidentally connect
+ anything else.
+ </p></li><li class="listitem"><p>
+ Connect USB
+ </p></li><li class="listitem"><p>
+ Turn the board power on.
+ </p></li><li class="listitem"><p>
+ The board should now be visible over USB as 'AltosFlash'
+ and be ready to receive firmware.
+ </p></li><li class="listitem"><p>
+ Once the board has been powered up, you can remove the
+ piece of wire.
+ </p></li></ol></div></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49568720"></a>2. Pair Programming</h2></div></div></div><p>
The big concept to understand is that you have to use a
TeleMega, TeleMetrum or TeleDongle as a programmer to update a
pair programmed device. Due to limited memory resources in the
cc1111, we don't support programming directly over USB for these
devices.
- </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp45096112"></a>3. Updating TeleMetrum v1.x Firmware</h2></div></div></div><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49570160"></a>3. Updating TeleMetrum v1.x Firmware</h2></div></div></div><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>
Find the 'programming cable' that you got as part of the starter
kit, that has a red 8-pin MicroMaTch connector on one end and a
red 4-pin MicroMaTch connector on the other end.
@@ -2382,7 +2499,7 @@ NAR #88757, TRA #12200<br>
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="idp45109648"></a>4. Updating TeleMini Firmware</h2></div></div></div><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>
+ </p></li></ol></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49583360"></a>4. Updating TeleMini Firmware</h2></div></div></div><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>
You'll need a special 'programming cable' to reprogram the
TeleMini. You can make your own using an 8-pin MicroMaTch
connector on one end and a set of four pins on the other.
@@ -2425,7 +2542,7 @@ NAR #88757, TRA #12200<br>
letting it come up in &#8220;flight&#8221; 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="idp45123200"></a>5. Updating TeleDongle Firmware</h2></div></div></div><p>
+ </p></li></ol></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49596912"></a>5. Updating TeleDongle Firmware</h2></div></div></div><p>
Updating TeleDongle's firmware is just like updating TeleMetrum or TeleMini
firmware, but you use either a TeleMetrum or another TeleDongle as the programmer.
</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>
@@ -2485,17 +2602,19 @@ NAR #88757, TRA #12200<br>
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="idp45139824"></a>Chapter 11. Hardware Specifications</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp45140464">1.
+ </p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp49613536"></a>Chapter 11. Hardware Specifications</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp49614176">1.
TeleMega Specifications
- </a></span></dt><dt><span class="section"><a href="#idp45151936">2.
+ </a></span></dt><dt><span class="section"><a href="#idp49625648">2.
+ EasyMega Specifications
+ </a></span></dt><dt><span class="section"><a href="#idp49635392">3.
TeleMetrum v2 Specifications
- </a></span></dt><dt><span class="section"><a href="#idp45162496">3. TeleMetrum v1 Specifications</a></span></dt><dt><span class="section"><a href="#idp45173056">4.
+ </a></span></dt><dt><span class="section"><a href="#idp49645952">4. TeleMetrum v1 Specifications</a></span></dt><dt><span class="section"><a href="#idp49656512">5.
TeleMini v2.0 Specifications
- </a></span></dt><dt><span class="section"><a href="#idp45181888">5.
+ </a></span></dt><dt><span class="section"><a href="#idp49665344">6.
TeleMini v1.0 Specifications
- </a></span></dt><dt><span class="section"><a href="#idp45190688">6.
+ </a></span></dt><dt><span class="section"><a href="#idp49674144">7.
EasyMini Specifications
- </a></span></dt></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp45140464"></a>1. 
+ </a></span></dt></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49614176"></a>1. 
TeleMega Specifications
</h2></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Recording altimeter for model rocketry.
@@ -2525,7 +2644,33 @@ NAR #88757, TRA #12200<br>
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="idp45151936"></a>2. 
+ </p></li></ul></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49625648"></a>2. 
+ EasyMega Specifications
+ </h2></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
+ Recording altimeter for model rocketry.
+ </p></li><li class="listitem"><p>
+ Supports dual deployment and four auxiliary pyro channels
+ (a total of 6 events).
+ </p></li><li class="listitem"><p>
+ Barometric pressure sensor good to 100k feet MSL.
+ </p></li><li class="listitem"><p>
+ 1-axis high-g accelerometer for motor characterization, capable of
+ +/- 102g.
+ </p></li><li class="listitem"><p>
+ 9-axis IMU including integrated 3-axis accelerometer,
+ 3-axis gyroscope and 3-axis magnetometer.
+ </p></li><li class="listitem"><p>
+ On-board 8 Megabyte non-volatile memory for flight data storage.
+ </p></li><li class="listitem"><p>
+ USB interface for battery charging, configuration, and data recovery.
+ </p></li><li class="listitem"><p>
+ Fully integrated support for Li-Po rechargeable batteries.
+ </p></li><li class="listitem"><p>
+ Can use either main system Li-Po or optional separate pyro battery
+ to fire e-matches.
+ </p></li><li class="listitem"><p>
+ 1.25 x 1.25 inch board designed to fit inside 38mm air-frame coupler tube.
+ </p></li></ul></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49635392"></a>3. 
TeleMetrum v2 Specifications
</h2></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Recording altimeter for model rocketry.
@@ -2551,7 +2696,7 @@ NAR #88757, TRA #12200<br>
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="idp45162496"></a>3. TeleMetrum v1 Specifications</h2></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
+ </p></li></ul></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49645952"></a>4. TeleMetrum v1 Specifications</h2></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Recording altimeter for model rocketry.
</p></li><li class="listitem"><p>
Supports dual deployment (can fire 2 ejection charges).
@@ -2575,7 +2720,7 @@ NAR #88757, TRA #12200<br>
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="idp45173056"></a>4. 
+ </p></li></ul></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49656512"></a>5. 
TeleMini v2.0 Specifications
</h2></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Recording altimeter for model rocketry.
@@ -2597,7 +2742,7 @@ NAR #88757, TRA #12200<br>
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="idp45181888"></a>5. 
+ </p></li></ul></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49665344"></a>6. 
TeleMini v1.0 Specifications
</h2></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Recording altimeter for model rocketry.
@@ -2618,7 +2763,7 @@ NAR #88757, TRA #12200<br>
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="idp45190688"></a>6. 
+ </p></li></ul></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49674144"></a>7. 
EasyMini Specifications
</h2></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Recording altimeter for model rocketry.
@@ -2638,7 +2783,7 @@ NAR #88757, TRA #12200<br>
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="idp45198800"></a>Chapter 12. FAQ</h1></div></div></div><p>
+ </p></li></ul></div></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp49682256"></a>Chapter 12. FAQ</h1></div></div></div><p>
<span class="emphasis"><em>TeleMetrum seems to shut off when disconnected from the
computer.</em></span>
Make sure the battery is adequately charged. Remember the
@@ -2683,7 +2828,7 @@ NAR #88757, TRA #12200<br>
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="idp45207648"></a>Appendix A. Notes for Older Software</h1></div></div></div><p>
+ </p></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a name="idp49691104"></a>Appendix A. Notes for Older Software</h1></div></div></div><p>
<span class="emphasis"><em>
Before AltosUI was written, using Altus Metrum devices required
some finesse with the Linux command line. There was a limited
@@ -2860,31 +3005,34 @@ NAR #88757, TRA #12200<br>
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="idp45230128"></a>Appendix B. Drill Templates</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp45231296">1. TeleMega template</a></span></dt><dt><span class="section"><a href="#idp45247984">2. TeleMetrum template</a></span></dt><dt><span class="section"><a href="#idp45252368">3. TeleMini v2/EasyMini template</a></span></dt><dt><span class="section"><a href="#idp45256768">4. TeleMini v1 template</a></span></dt></dl></div><p>
+ </p></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a name="idp49713504"></a>Appendix B. Drill Templates</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp49714672">1. TeleMega template</a></span></dt><dt><span class="section"><a href="#idp49731360">2. EasyMega template</a></span></dt><dt><span class="section"><a href="#idp49735744">3. TeleMetrum template</a></span></dt><dt><span class="section"><a href="#idp49740128">4. TeleMini v2/EasyMini template</a></span></dt><dt><span class="section"><a href="#idp49744528">5. TeleMini v1 template</a></span></dt></dl></div><p>
These images, when printed, provide precise templates for the
mounting holes in Altus Metrum flight computers
- </p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp45231296"></a>1. TeleMega template</h2></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49714672"></a>1. TeleMega template</h2></div></div></div><p>
TeleMega has overall dimensions of 1.250 x 3.250 inches, and
the mounting holes are sized for use with 4-40 or M3 screws.
- </p><div class="informalfigure"><div class="mediaobject" align="center"><a name="TeleMegaTemplate"></a><object type="image/svg+xml" data="telemega.svg" align="middle"></object></div></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp45247984"></a>2. TeleMetrum template</h2></div></div></div><p>
+ </p><div class="informalfigure"><div class="mediaobject" align="center"><a name="TeleMegaTemplate"></a><object type="image/svg+xml" data="telemega.svg" align="middle"></object></div></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49731360"></a>2. EasyMega template</h2></div></div></div><p>
+ EasyMega has overall dimensions of 1.250 x 2.250 inches, and
+ the mounting holes are sized for use with 4-40 or M3 screws.
+ </p><div class="informalfigure"><div class="mediaobject" align="center"><a name="EasyMegaTemplate"></a><object type="image/svg+xml" data="easymega.svg" align="middle"></object></div></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49735744"></a>3. TeleMetrum template</h2></div></div></div><p>
TeleMetrum has overall dimensions of 1.000 x 2.750 inches, and the
mounting holes are sized for use with 4-40 or M3 screws.
- </p><div class="informalfigure"><div class="mediaobject" align="center"><a name="TeleMetrumTemplate"></a><object type="image/svg+xml" data="telemetrum.svg" align="middle"></object></div></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp45252368"></a>3. TeleMini v2/EasyMini template</h2></div></div></div><p>
+ </p><div class="informalfigure"><div class="mediaobject" align="center"><a name="TeleMetrumTemplate"></a><object type="image/svg+xml" data="telemetrum.svg" align="middle"></object></div></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49740128"></a>4. TeleMini v2/EasyMini template</h2></div></div></div><p>
TeleMini v2 and EasyMini have overall dimensions of 0.800 x 1.500 inches, and the
mounting holes are sized for use with 4-40 or M3 screws.
- </p><div class="informalfigure"><div class="mediaobject" align="center"><a name="MiniTemplate"></a><object type="image/svg+xml" data="easymini.svg" align="middle"></object></div></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp45256768"></a>4. TeleMini v1 template</h2></div></div></div><p>
+ </p><div class="informalfigure"><div class="mediaobject" align="center"><a name="MiniTemplate"></a><object type="image/svg+xml" data="easymini.svg" align="middle"></object></div></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49744528"></a>5. TeleMini v1 template</h2></div></div></div><p>
TeleMini has overall dimensions of 0.500 x 1.500 inches, and the
mounting holes are sized for use with 2-56 or M2 screws.
- </p><div class="informalfigure"><div class="mediaobject" align="center"><a name="TeleMiniTemplate"></a><object type="image/svg+xml" data="telemini.svg" align="middle"></object></div></div></div></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a name="idp45261280"></a>Appendix C. Calibration</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp45262832">1. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp45267376">2. TeleMetrum and TeleMega Accelerometers</a></span></dt></dl></div><p>
+ </p><div class="informalfigure"><div class="mediaobject" align="center"><a name="TeleMiniTemplate"></a><object type="image/svg+xml" data="telemini.svg" align="middle"></object></div></div></div></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a name="idp49749040"></a>Appendix C. Calibration</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp49750592">1. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp49755136">2. TeleMetrum, TeleMega and EasyMega Accelerometers</a></span></dt></dl></div><p>
There are only two calibrations required for TeleMetrum and
- TeleMega, and only one for TeleDongle, TeleMini and EasyMini.
+ 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="idp45262832"></a>1. Radio Frequency</h2></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49750592"></a>1. Radio Frequency</h2></div></div></div><p>
The radio frequency is synthesized from a clock based on the
crystal on the board. The actual frequency of this oscillator
must be measured to generate a calibration constant. While our
@@ -2920,7 +3068,7 @@ NAR #88757, TRA #12200<br>
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="idp45267376"></a>2. TeleMetrum and TeleMega Accelerometers</h2></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49755136"></a>2. TeleMetrum, TeleMega and EasyMega Accelerometers</h2></div></div></div><p>
While barometric sensors are factory-calibrated,
accelerometers are not, and so each must be calibrated once
installed in a flight computer. Explicitly calibrating the
@@ -2943,7 +3091,7 @@ NAR #88757, TRA #12200<br>
&#8220;damaged&#8221; if the calibration is poor.
</p><p>
In the unlikely event an accel cal goes badly, it is possible
- that TeleMetrum or TeleMega may always come up in 'pad mode'
+ 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
@@ -2957,7 +3105,7 @@ NAR #88757, TRA #12200<br>
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="idp45272480"></a>Appendix D. Release Notes</h1></div></div></div><div class="simplesect"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp45273120"></a>Version 1.41</h2></div></div></div><p>
+ </p></div></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a name="idp49760816"></a>Appendix D. Release Notes</h1></div></div></div><div class="simplesect"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49761456"></a>Version 1.4.1</h2></div></div></div><p>
Version 1.4.1 is a minor release. It fixes install issues on
Windows and provides the missing TeleMetrum V2.0 firmware. There
aren't any changes to the firmware or host applications at
@@ -2988,7 +3136,74 @@ NAR #88757, TRA #12200<br>
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="idp45274720"></a>Version 1.4</h2></div></div></div><p>
+ </p></div><div class="simplesect"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49763056"></a>Version 1.5</h2></div></div></div><p>
+ Version 1.5 is a major release. It includes support for our new
+ EasyMega product, new features and bug fixes in in the flight
+ software for all our boards and the AltosUI ground station
+ </p><p>
+ AltOS New Features
+ </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
+ Add support for EasyMega boards.
+ </p></li><li class="listitem"><p>
+ Make the APRS SSID be configurable. This lets you track
+ different rockets on the same receiver without getting
+ things mixed up.
+ </p></li><li class="listitem"><p>
+ Report extra pyro channel continuity state on EasyMega and
+ TeleMega via the beeper. This lets you easily verify flight
+ readiness on these boards after powering up the electronics
+ on the rail.
+ </p></li><li class="listitem"><p>
+ Add lower telemetry data rates (2400 and 9600 bps) to
+ increase telemetry radio range. This reduces the amount of
+ data received as well as increasing battery consumption in
+ the transmitter.
+ </p></li><li class="listitem"><p>
+ Change TeleGPS to have only a single log, and append new
+ data to it rather than using seperate per-flight logs. This
+ avoids accidentally filling up log storage by turning
+ TeleGPS on/off several times.
+ </p></li></ul></div><p>
+ </p><p>
+ AltOS Fixes
+ </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
+ Increase the maximum range for altitude values from +/-32767m
+ to +/-2147483647m, allowing the flight computers to function
+ correctly above the 32km level.
+ </p></li><li class="listitem"><p>
+ Continuously test pyro firing conditions during delay stage,
+ inhibiting the pyro channel if the test fails. This prevents
+ firing pyro charges where the conditions were good before
+ the delay, but become bad before the delay expires.
+ </p></li><li class="listitem"><p>
+ Allow negative numbers in pyro configuration values. This
+ lets you specify things like descending speed or
+ deceleration.
+ </p></li></ul></div><p>
+ </p><p>
+ AltosUI and TeleGPS New Features
+ </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
+ Support telemetry baud rate selection. Adds menus to
+ the flight monitoring and configuration for baud rate
+ selection.
+ </p></li><li class="listitem"><p>
+ Support APRS SSID configuration.
+ </p></li><li class="listitem"><p>
+ Integrate with file managers. This provides icons for all of
+ our file types and associates our application with the files
+ so that using a file manager to open a AltOS data file
+ results in launching our application.
+ </p></li></ul></div><p>
+ </p><p>
+ AltosUI Fixes
+ </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
+ Make the 'Graph' button on the landed tab work again.
+ </p></li><li class="listitem"><p>
+ Make tests for Java on Windows a bit smarter, and also
+ provide the user with the option to skip installing Java for
+ cases where we just can't figure out what version is installed.
+ </p></li></ul></div><p>
+ </p></div><div class="simplesect"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49764656"></a>Version 1.4</h2></div></div></div><p>
Version 1.4 is a major release. It includes support for our new
TeleGPS product, new features and bug fixes in in the flight
software for all our boards and the AltosUI ground station
@@ -3101,7 +3316,7 @@ NAR #88757, TRA #12200<br>
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="idp45276320"></a>Version 1.3.2</h2></div></div></div><p>
+ </p></div><div class="simplesect"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49766160"></a>Version 1.3.2</h2></div></div></div><p>
Version 1.3.2 is a minor release. It includes small bug fixes for
the TeleMega flight software and AltosUI ground station
</p><p>
@@ -3129,7 +3344,7 @@ NAR #88757, TRA #12200<br>
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="idp45277824"></a>Version 1.3.1</h2></div></div></div><p>
+ </p></div><div class="simplesect"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49767664"></a>Version 1.3.1</h2></div></div></div><p>
Version 1.3.1 is a minor release. It improves support for TeleMega,
TeleMetrum v2.0, TeleMini v2.0 and EasyMini.
</p><p>
@@ -3171,7 +3386,7 @@ NAR #88757, TRA #12200<br>
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="idp45279328"></a>Version 1.3</h2></div></div></div><p>
+ </p></div><div class="simplesect"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49769168"></a>Version 1.3</h2></div></div></div><p>
Version 1.3 is a major release. It adds support for TeleMega,
TeleMetrum v2.0, TeleMini v2.0 and EasyMini.
</p><p>
@@ -3212,7 +3427,7 @@ NAR #88757, TRA #12200<br>
</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="idp45280832"></a>Version 1.2.1</h2></div></div></div><p>
+ </p></div><div class="simplesect"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49770672"></a>Version 1.2.1</h2></div></div></div><p>
Version 1.2.1 is a minor release. It adds support for TeleBT and
the AltosDroid application, provides several new features in
AltosUI and fixes some bugs in the AltOS firmware.
@@ -3272,7 +3487,7 @@ NAR #88757, TRA #12200<br>
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="idp45282336"></a>Version 1.2</h2></div></div></div><p>
+ </p></div><div class="simplesect"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49772176"></a>Version 1.2</h2></div></div></div><p>
Version 1.2 is a major release. It adds support for MicroPeak and
the MicroPeak USB adapter.
</p><p>
@@ -3298,7 +3513,7 @@ NAR #88757, TRA #12200<br>
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="idp45283840"></a>Version 1.1.1</h2></div></div></div><p>
+ </p></div><div class="simplesect"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49773680"></a>Version 1.1.1</h2></div></div></div><p>
Version 1.1.1 is a bug-fix release. It fixes a couple of bugs in
AltosUI and one firmware bug that affects TeleMetrum version 1.0
boards. Thanks to Bob Brown for help diagnosing the Google Earth
@@ -3343,7 +3558,7 @@ NAR #88757, TRA #12200<br>
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="idp45285344"></a>Version 1.1</h2></div></div></div><p>
+ </p></div><div class="simplesect"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49775184"></a>Version 1.1</h2></div></div></div><p>
Version 1.1 is a minor release. It provides a few new features in AltosUI
and the AltOS firmware and fixes bugs.
</p><p>
@@ -3415,7 +3630,7 @@ NAR #88757, TRA #12200<br>
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="idp45286848"></a>Version 1.0.1</h2></div></div></div><p>
+ </p></div><div class="simplesect"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49776688"></a>Version 1.0.1</h2></div></div></div><p>
Version 1.0.1 is a major release, adding support for the TeleMini
device and lots of new AltosUI features
</p><p>
@@ -3495,7 +3710,7 @@ NAR #88757, TRA #12200<br>
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="idp45288352"></a>Version 0.9.2</h2></div></div></div><p>
+ </p></div><div class="simplesect"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49778192"></a>Version 0.9.2</h2></div></div></div><p>
Version 0.9.2 is an AltosUI bug-fix release, with no firmware changes.
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Fix plotting problems due to missing file in the Mac OS install image.
@@ -3503,7 +3718,7 @@ NAR #88757, TRA #12200<br>
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="idp45289856"></a>Version 0.9</h2></div></div></div><p>
+</p></li></ul></div></div><div class="simplesect"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49779696"></a>Version 0.9</h2></div></div></div><p>
Version 0.9 adds a few new firmware features and accompanying
AltosUI changes, along with new hardware support.
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
@@ -3522,7 +3737,7 @@ NAR #88757, TRA #12200<br>
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="idp45291360"></a>Version 0.8</h2></div></div></div><p>
+</p></li></ul></div></div><div class="simplesect"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49781200"></a>Version 0.8</h2></div></div></div><p>
Version 0.8 offers a major upgrade in the AltosUI
interface. Significant new features include:
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
@@ -3562,7 +3777,7 @@ NAR #88757, TRA #12200<br>
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="idp45292864"></a>Version 0.7.1</h2></div></div></div><p>
+ </p></li></ul></div></div><div class="simplesect"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp49782704"></a>Version 0.7.1</h2></div></div></div><p>
Version 0.7.1 is the first release containing our new cross-platform Java-based user interface. AltosUI can:
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Receive and log telemetry from a connected TeleDongle
diff --git a/AltOS/doc/altusmetrum.pdf b/AltOS/doc/altusmetrum.pdf
index 53732c8..3dddf23 100644
--- a/AltOS/doc/altusmetrum.pdf
+++ b/AltOS/doc/altusmetrum.pdf
Binary files differ
diff --git a/AltOS/doc/companion.html b/AltOS/doc/companion.html
index c85b78e..cdbe2ac 100644
--- a/AltOS/doc/companion.html
+++ b/AltOS/doc/companion.html
@@ -1,10 +1,10 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>AltOS Companion Port</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"><div><div><h2 class="title"><a name="idp33805216"></a>AltOS Companion Port</h2></div><div><h3 class="subtitle"><i>Protocol Definitions</i></h3></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 © 2012 Keith Packard</p></div><div><div class="legalnotice"><a name="idp60299424"></a><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>AltOS Companion Port</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"><div><div><h2 class="title"><a name="idp30954880"></a>AltOS Companion Port</h2></div><div><h3 class="subtitle"><i>Protocol Definitions</i></h3></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 © 2012 Keith Packard</p></div><div><div class="legalnotice"><a name="idp57376448"></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">13 January 2012</td></tr><tr><td align="left" colspan="2">Initial content</td></tr></table></div></div></div><hr></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp60177952">1. Companion Port</a></span></dt><dt><span class="section"><a href="#idp60182400">2. Companion SPI Protocol</a></span></dt><dt><span class="section"><a href="#idp61057888">3. SPI Message Formats</a></span></dt><dd><dl><dt><span class="section"><a href="#idp61059168">3.1. Command Message</a></span></dt><dt><span class="section"><a href="#idp60192784">3.2. SETUP reply message</a></span></dt><dt><span class="section"><a href="#idp60214208">3.3. FETCH reply message</a></span></dt></dl></dd><dt><span class="section"><a href="#idp65708160">4. History and Motivation</a></span></dt></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp60177952"></a>1. Companion Port</h2></div></div></div><p>
+ </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">13 January 2012</td></tr><tr><td align="left" colspan="2">Initial content</td></tr></table></div></div></div><hr></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp57299792">1. Companion Port</a></span></dt><dt><span class="section"><a href="#idp57304288">2. Companion SPI Protocol</a></span></dt><dt><span class="section"><a href="#idp58182896">3. SPI Message Formats</a></span></dt><dd><dl><dt><span class="section"><a href="#idp58184144">3.1. Command Message</a></span></dt><dt><span class="section"><a href="#idp57314928">3.2. SETUP reply message</a></span></dt><dt><span class="section"><a href="#idp57336416">3.3. FETCH reply message</a></span></dt></dl></dd><dt><span class="section"><a href="#idp62825024">4. History and Motivation</a></span></dt></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp57299792"></a>1. Companion Port</h2></div></div></div><p>
Many Altus Metrum products come with an eight pin Micro MaTch
connector, called the Companion Port. This is often used to
program devices using a programming cable. However, it can also
@@ -25,7 +25,7 @@
provide a matching SPI slave implementation which supplies
telemetry information for the radio downlink during flight
</p></li></ul></div><p>
- </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp60182400"></a>2. Companion SPI Protocol</h2></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp57304288"></a>2. Companion SPI Protocol</h2></div></div></div><p>
The flight computer implements a SPI master communications
channel over the companion port, and uses this to get
information about a connected companion board and then to get
@@ -42,11 +42,11 @@
</p><p>
Because of the limits of the AVR processors used in the first
two companion boards, the SPI data rate is set to 187.5kbaud.
- </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp61057888"></a>3. SPI Message Formats</h2></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp58182896"></a>3. SPI Message Formats</h2></div></div></div><p>
This section first defines the command message format sent from
the flight computer to the companion board, and then the various
reply message formats for each type of command message.
- </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp61059168"></a>3.1. Command Message</h3></div></div></div><div class="table"><a name="idp61059840"></a><p class="title"><b>Table 1. Companion Command Message</b></p><div class="table-contents"><table summary="Companion Command Message" border="1"><colgroup><col align="center" class="Offset"><col align="center" class="Data Type"><col align="left" class="Name"><col align="left" class="Description"></colgroup><thead><tr><th align="center">Offset</th><th align="center">Data Type</th><th align="center">Name</th><th align="center">Description</th></tr></thead><tbody><tr><td align="center">0</td><td align="center">uint8_t</td><td align="left">command</td><td align="left">Command identifier</td></tr><tr><td align="center">1</td><td align="center">uint8_t</td><td align="left">flight_state</td><td align="left">Current flight computer state</td></tr><tr><td align="center">2</td><td align="center">uint16_t</td><td align="left">tick</td><td align="left">Flight computer clock (100 ticks/second)</td></tr><tr><td align="center">4</td><td align="center">uint16_t</td><td align="left">serial</td><td align="left">Flight computer serial number</td></tr><tr><td align="center">6</td><td align="center">uint16_t</td><td align="left">flight</td><td align="left">Flight number</td></tr><tr><td align="center">8</td><td class="auto-generated"> </td><td class="auto-generated"> </td><td class="auto-generated"> </td></tr></tbody></table></div></div><br class="table-break"><div class="table"><a name="idp64567568"></a><p class="title"><b>Table 2. Companion Command Identifiers</b></p><div class="table-contents"><table summary="Companion Command Identifiers" border="1"><colgroup><col align="center" class="Value"><col align="left" class="Name"><col align="left" class="Description"></colgroup><thead><tr><th align="center">Value</th><th align="left">Name</th><th align="left">Description</th></tr></thead><tbody><tr><td align="center">1</td><td align="left">SETUP</td><td align="left">Supply the flight computer with companion
+ </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp58184144"></a>3.1. Command Message</h3></div></div></div><div class="table"><a name="idp58184816"></a><p class="title"><b>Table 1. Companion Command Message</b></p><div class="table-contents"><table summary="Companion Command Message" border="1"><colgroup><col align="center" class="Offset"><col align="center" class="Data Type"><col align="left" class="Name"><col align="left" class="Description"></colgroup><thead><tr><th align="center">Offset</th><th align="center">Data Type</th><th align="center">Name</th><th align="center">Description</th></tr></thead><tbody><tr><td align="center">0</td><td align="center">uint8_t</td><td align="left">command</td><td align="left">Command identifier</td></tr><tr><td align="center">1</td><td align="center">uint8_t</td><td align="left">flight_state</td><td align="left">Current flight computer state</td></tr><tr><td align="center">2</td><td align="center">uint16_t</td><td align="left">tick</td><td align="left">Flight computer clock (100 ticks/second)</td></tr><tr><td align="center">4</td><td align="center">uint16_t</td><td align="left">serial</td><td align="left">Flight computer serial number</td></tr><tr><td align="center">6</td><td align="center">uint16_t</td><td align="left">flight</td><td align="left">Flight number</td></tr><tr><td align="center">8</td><td class="auto-generated"> </td><td class="auto-generated"> </td><td class="auto-generated"> </td></tr></tbody></table></div></div><br class="table-break"><div class="table"><a name="idp57480384"></a><p class="title"><b>Table 2. Companion Command Identifiers</b></p><div class="table-contents"><table summary="Companion Command Identifiers" border="1"><colgroup><col align="center" class="Value"><col align="left" class="Name"><col align="left" class="Description"></colgroup><thead><tr><th align="center">Value</th><th align="left">Name</th><th align="left">Description</th></tr></thead><tbody><tr><td align="center">1</td><td align="left">SETUP</td><td align="left">Supply the flight computer with companion
information</td></tr><tr><td align="center">2</td><td align="left">FETCH</td><td align="left">Return telemetry information</td></tr><tr><td align="center">3</td><td align="left">NOTIFY</td><td align="left">Tell companion board when flight state
changes</td></tr></tbody></table></div></div><br class="table-break"><p>
The flight computer will send a SETUP message shortly after
@@ -74,7 +74,7 @@
use this to change data collection parameters, disabling data
logging until the flight starts and terminating it when the
flight ends.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp60192784"></a>3.2. SETUP reply message</h3></div></div></div><div class="table"><a name="idp60193456"></a><p class="title"><b>Table 3. SETUP reply contents</b></p><div class="table-contents"><table summary="SETUP reply contents" border="1"><colgroup><col align="center" class="Offset"><col align="center" class="Data Type"><col align="left" class="Name"><col align="left" class="Description"></colgroup><thead><tr><th align="center">Offset</th><th align="center">Data Type</th><th align="center">Name</th><th align="center">Description</th></tr></thead><tbody><tr><td align="center">0</td><td align="center">uint16_t</td><td align="left">board_id</td><td align="left">Board identifier</td></tr><tr><td align="center">2</td><td align="center">uint16_t</td><td align="left">board_id_inverse</td><td align="left">~board_id&#8212;used to tell if a board is present</td></tr><tr><td align="center">4</td><td align="center">uint8_t</td><td align="left">update_period</td><td align="left">Minimum time (in 100Hz ticks) between FETCH commands</td></tr><tr><td align="center">5</td><td align="center">uint8_t</td><td align="left">channels</td><td align="left">Number of data channels to retrieve in FETCH command</td></tr><tr><td align="center">6</td><td class="auto-generated"> </td><td class="auto-generated"> </td><td class="auto-generated"> </td></tr></tbody></table></div></div><br class="table-break"><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp57314928"></a>3.2. SETUP reply message</h3></div></div></div><div class="table"><a name="idp57315600"></a><p class="title"><b>Table 3. SETUP reply contents</b></p><div class="table-contents"><table summary="SETUP reply contents" border="1"><colgroup><col align="center" class="Offset"><col align="center" class="Data Type"><col align="left" class="Name"><col align="left" class="Description"></colgroup><thead><tr><th align="center">Offset</th><th align="center">Data Type</th><th align="center">Name</th><th align="center">Description</th></tr></thead><tbody><tr><td align="center">0</td><td align="center">uint16_t</td><td align="left">board_id</td><td align="left">Board identifier</td></tr><tr><td align="center">2</td><td align="center">uint16_t</td><td align="left">board_id_inverse</td><td align="left">~board_id&#8212;used to tell if a board is present</td></tr><tr><td align="center">4</td><td align="center">uint8_t</td><td align="left">update_period</td><td align="left">Minimum time (in 100Hz ticks) between FETCH commands</td></tr><tr><td align="center">5</td><td align="center">uint8_t</td><td align="left">channels</td><td align="left">Number of data channels to retrieve in FETCH command</td></tr><tr><td align="center">6</td><td class="auto-generated"> </td><td class="auto-generated"> </td><td class="auto-generated"> </td></tr></tbody></table></div></div><br class="table-break"><p>
The SETUP reply contains enough information to uniquely
identify the companion board to the end user as well as for
the flight computer to know how many data values to expect in
@@ -85,12 +85,12 @@
bit-wise inverse of board_id. Current companion boards use
USB product ID as the board_id, but the flight computer does
not interpret this data and so it can be any value.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp60214208"></a>3.3. FETCH reply message</h3></div></div></div><div class="table"><a name="idp60214880"></a><p class="title"><b>Table 4. FETCH reply contents</b></p><div class="table-contents"><table summary="FETCH reply contents" border="1"><colgroup><col align="center" class="Offset"><col align="center" class="Data Type"><col align="left" class="Name"><col align="left" class="Description"></colgroup><thead><tr><th align="center">Offset</th><th align="center">Data Type</th><th align="center">Name</th><th align="center">Description</th></tr></thead><tbody><tr><td align="center">0</td><td align="center">uint16_t</td><td align="left">data0</td><td align="left">0th data item</td></tr><tr><td align="center">2</td><td align="center">uint16_t</td><td align="left">data1</td><td align="left">1st data item</td></tr><tr><td align="center">...</td><td class="auto-generated"> </td><td class="auto-generated"> </td><td class="auto-generated"> </td></tr></tbody></table></div></div><br class="table-break"><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp57336416"></a>3.3. FETCH reply message</h3></div></div></div><div class="table"><a name="idp57337088"></a><p class="title"><b>Table 4. FETCH reply contents</b></p><div class="table-contents"><table summary="FETCH reply contents" border="1"><colgroup><col align="center" class="Offset"><col align="center" class="Data Type"><col align="left" class="Name"><col align="left" class="Description"></colgroup><thead><tr><th align="center">Offset</th><th align="center">Data Type</th><th align="center">Name</th><th align="center">Description</th></tr></thead><tbody><tr><td align="center">0</td><td align="center">uint16_t</td><td align="left">data0</td><td align="left">0th data item</td></tr><tr><td align="center">2</td><td align="center">uint16_t</td><td align="left">data1</td><td align="left">1st data item</td></tr><tr><td align="center">...</td><td class="auto-generated"> </td><td class="auto-generated"> </td><td class="auto-generated"> </td></tr></tbody></table></div></div><br class="table-break"><p>
The FETCH reply contains arbitrary data to be reported over
the flight computer telemetry link. The number of 16-bit data items
must match the 'channels' value provided in the SETUP reply
message.
- </p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp65708160"></a>4. History and Motivation</h2></div></div></div><p>
+ </p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp62825024"></a>4. History and Motivation</h2></div></div></div><p>
To allow cross-programming, the original TeleMetrum and
TeleDongle designs needed to include some kind of
connector. With that in place, adding the ability to connect
diff --git a/AltOS/doc/companion.pdf b/AltOS/doc/companion.pdf
index cd7af1b..c19a0fd 100644
--- a/AltOS/doc/companion.pdf
+++ b/AltOS/doc/companion.pdf
Binary files differ
diff --git a/AltOS/doc/configure-altimeter.png b/AltOS/doc/configure-altimeter.png
index 514db3e..09a83d1 100644
--- a/AltOS/doc/configure-altimeter.png
+++ b/AltOS/doc/configure-altimeter.png
Binary files differ
diff --git a/AltOS/doc/configure-groundstation.png b/AltOS/doc/configure-groundstation.png
index 9f836e7..9e3c98a 100644
--- a/AltOS/doc/configure-groundstation.png
+++ b/AltOS/doc/configure-groundstation.png
Binary files differ
diff --git a/AltOS/doc/easymega-outline.pdf b/AltOS/doc/easymega-outline.pdf
new file mode 100644
index 0000000..8743d61
--- /dev/null
+++ b/AltOS/doc/easymega-outline.pdf
Binary files differ
diff --git a/AltOS/doc/easymega.svg b/AltOS/doc/easymega.svg
new file mode 100644
index 0000000..6d9d766
--- /dev/null
+++ b/AltOS/doc/easymega.svg
@@ -0,0 +1,33 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+
+<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"
+ width="2.5in"
+ height="1.5in"
+ viewBox="0 0 250 150"
+ preserveaspectratio="none"
+ id="svg2"
+ version="1.1">
+ <g transform="translate(12.5,12.5)"
+ style="fill:none;stroke:#000000;stroke-width:1;stroke-linejoin:miter;font-size:24">
+ <!-- outline -->
+ <rect width="225" height="125" x="0" y="0"/>
+ <!-- holes -->
+ <path d="M12.5,12.5 m-6.25,0 a6.25,6.25,0,1,0,12.5,0 a6.25,6.25,0,1,0,-12.5,0 l12.5,0 m-6.25,-6.25 l0,12.5"/>
+ <path d="M212.5,12.5 m-6.25,0 a6.25,6.25,0,1,0,12.5,0 a6.25,6.25,0,1,0,-12.5,0 l12.5,0 m-6.25,-6.25 l0,12.5"/>
+ <path d="M12.5,112.5 m-6.25,0 a6.25,6.25,0,1,0,12.5,0 a6.25,6.25,0,1,0,-12.5,0 l12.5,0 m-6.25,-6.25 l0,12.5"/>
+ <path d="M212.5,112.5 m-6.25,0 a6.25,6.25,0,1,0,12.5,0 a6.25,6.25,0,1,0,-12.5,0 l12.5,0 m-6.25,-6.25 l0,12.5"/>
+ <!-- arrow -->
+ <path d="M50,62.5 l125,0"/>
+ <path style="fill:#000000;stroke:none" d="M175,57.5 l10,5 l-10,5 z"/>
+ <!-- label -->
+ <text x="112.5" y="57.5" style="fill:#000000;stroke:none" text-anchor="middle">EasyMega</text>
+ <g transform="rotate(90)">
+ <text x="62.5" y="-190" style="fill:#000000;stroke:none" text-anchor="middle">UP</text>
+ </g>
+ </g>
+</svg>
diff --git a/AltOS/doc/easymini-outline.pdf b/AltOS/doc/easymini-outline.pdf
index 7a30878..670c822 100644
--- a/AltOS/doc/easymini-outline.pdf
+++ b/AltOS/doc/easymini-outline.pdf
Binary files differ
diff --git a/AltOS/doc/micropeak.html b/AltOS/doc/micropeak.html
index f443112..5fe70f9 100644
--- a/AltOS/doc/micropeak.html
+++ b/AltOS/doc/micropeak.html
@@ -1,4 +1,4 @@
-<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="idp23675904"></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="idp50893152"></a><p>
+<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="idp19019136"></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="idp45361792"></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
@@ -21,7 +21,7 @@
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="idp50903680"></a>Acknowledgements</h1></div></div></div><p>
+ </td></tr></table></div></div></div><hr></div><div class="dedication"><div class="titlepage"><div><div><h1 class="title"><a name="idp46247936"></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
@@ -33,7 +33,7 @@ NAR #87103, TRA #12201<br>
Keith Packard, KD7SQG<br>
NAR #88757, TRA #12200<br>
      </p></div><p>
- </p></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="chapter"><a href="#idp50906432">1. Quick Start Guide</a></span></dt><dt><span class="chapter"><a href="#idp50193728">2. Handling Precautions</a></span></dt><dt><span class="chapter"><a href="#idp50198112">3. The MicroPeak USB adapter</a></span></dt><dd><dl><dt><span class="section"><a href="#idp50011584">1. Installing the MicroPeak software</a></span></dt><dt><span class="section"><a href="#idp50014672">2. Downloading Micro Peak data</a></span></dt><dt><span class="section"><a href="#idp50037808">3. Analyzing MicroPeak Data</a></span></dt><dd><dl><dt><span class="section"><a href="#idp50041296">3.1. MicroPeak Graphs</a></span></dt><dt><span class="section"><a href="#idp50044896">3.2. MicroPeak Flight Statistics</a></span></dt><dt><span class="section"><a href="#idp50048768">3.3. Raw Data</a></span></dt><dt><span class="section"><a href="#idp55531984">3.4. Configuring the Graph</a></span></dt></dl></dd><dt><span class="section"><a href="#idp55535520">4. Setting MicroPeak Preferences</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp55545504">4. Technical Information</a></span></dt><dd><dl><dt><span class="section"><a href="#idp55546176">1. Barometric Sensor</a></span></dt><dt><span class="section"><a href="#idp55548928">2. Micro-controller</a></span></dt><dt><span class="section"><a href="#idp55551280">3. Lithium Battery</a></span></dt><dt><span class="section"><a href="#idp55554064">4. Atmospheric Model</a></span></dt><dt><span class="section"><a href="#idp55557040">5. Mechanical Considerations</a></span></dt><dt><span class="section"><a href="#idp55559792">6. On-board data storage</a></span></dt><dt><span class="section"><a href="#idp53369808">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="#idp55561904">MicroPeak EEPROM Data Storage</a></dt></dl></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp50906432"></a>Chapter 1. Quick Start Guide</h1></div></div></div><p>
+ </p></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="chapter"><a href="#idp46250688">1. Quick Start Guide</a></span></dt><dt><span class="chapter"><a href="#idp45537136">2. Handling Precautions</a></span></dt><dt><span class="chapter"><a href="#idp45541520">3. The MicroPeak USB adapter</a></span></dt><dd><dl><dt><span class="section"><a href="#idp45545072">1. Installing the MicroPeak software</a></span></dt><dt><span class="section"><a href="#idp45548160">2. Downloading Micro Peak data</a></span></dt><dt><span class="section"><a href="#idp45389376">3. Analyzing MicroPeak Data</a></span></dt><dd><dl><dt><span class="section"><a href="#idp45392864">3.1. MicroPeak Graphs</a></span></dt><dt><span class="section"><a href="#idp45396464">3.2. MicroPeak Flight Statistics</a></span></dt><dt><span class="section"><a href="#idp45400336">3.3. Raw Data</a></span></dt><dt><span class="section"><a href="#idp50875760">3.4. Configuring the Graph</a></span></dt></dl></dd><dt><span class="section"><a href="#idp50879376">4. Setting MicroPeak Preferences</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp50889408">4. Technical Information</a></span></dt><dd><dl><dt><span class="section"><a href="#idp50890080">1. Barometric Sensor</a></span></dt><dt><span class="section"><a href="#idp50892832">2. Micro-controller</a></span></dt><dt><span class="section"><a href="#idp50895184">3. Lithium Battery</a></span></dt><dt><span class="section"><a href="#idp50897968">4. Atmospheric Model</a></span></dt><dt><span class="section"><a href="#idp50900944">5. Mechanical Considerations</a></span></dt><dt><span class="section"><a href="#idp50903696">6. On-board data storage</a></span></dt><dt><span class="section"><a href="#idp50924032">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="#idp50905808">MicroPeak EEPROM Data Storage</a></dt></dl></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp46250688"></a>Chapter 1. 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>
@@ -84,7 +84,7 @@ NAR #88757, TRA #12200<br>
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="idp50193728"></a>Chapter 2. Handling Precautions</h1></div></div></div><p>
+ </p></li></ul></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp45537136"></a>Chapter 2. Handling Precautions</h1></div></div></div><p>
All Altus Metrum products are sophisticated electronic devices.
When handled gently and properly installed in an air-frame, they
will deliver impressive results. However, as with all electronic
@@ -114,12 +114,12 @@ NAR #88757, TRA #12200<br>
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="idp50198112"></a>Chapter 3. 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="#idp50011584">1. Installing the MicroPeak software</a></span></dt><dt><span class="section"><a href="#idp50014672">2. Downloading Micro Peak data</a></span></dt><dt><span class="section"><a href="#idp50037808">3. Analyzing MicroPeak Data</a></span></dt><dd><dl><dt><span class="section"><a href="#idp50041296">3.1. MicroPeak Graphs</a></span></dt><dt><span class="section"><a href="#idp50044896">3.2. MicroPeak Flight Statistics</a></span></dt><dt><span class="section"><a href="#idp50048768">3.3. Raw Data</a></span></dt><dt><span class="section"><a href="#idp55531984">3.4. Configuring the Graph</a></span></dt></dl></dd><dt><span class="section"><a href="#idp55535520">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>
+ </p></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp45541520"></a>Chapter 3. 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="#idp45545072">1. Installing the MicroPeak software</a></span></dt><dt><span class="section"><a href="#idp45548160">2. Downloading Micro Peak data</a></span></dt><dt><span class="section"><a href="#idp45389376">3. Analyzing MicroPeak Data</a></span></dt><dd><dl><dt><span class="section"><a href="#idp45392864">3.1. MicroPeak Graphs</a></span></dt><dt><span class="section"><a href="#idp45396464">3.2. MicroPeak Flight Statistics</a></span></dt><dt><span class="section"><a href="#idp45400336">3.3. Raw Data</a></span></dt><dt><span class="section"><a href="#idp50875760">3.4. Configuring the Graph</a></span></dt></dl></dd><dt><span class="section"><a href="#idp50879376">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="idp50011584"></a>1. Installing the MicroPeak software</h2></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp45545072"></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>.
@@ -128,7 +128,7 @@ NAR #88757, TRA #12200<br>
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="idp50014672"></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>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp45548160"></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.
@@ -161,7 +161,7 @@ NAR #88757, TRA #12200<br>
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="idp50037808"></a>3. Analyzing MicroPeak Data</h2></div></div></div><p>
+ </p></li></ul></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp45389376"></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.
@@ -187,13 +187,13 @@ NAR #88757, TRA #12200<br>
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="idp50041296"></a>3.1. MicroPeak Graphs</h3></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp45392864"></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="idp50044896"></a>3.2. MicroPeak Flight Statistics</h3></div></div></div><p>
+ </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="idp45396464"></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
@@ -201,13 +201,13 @@ NAR #88757, TRA #12200<br>
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="idp50048768"></a>3.3. Raw Data</h3></div></div></div><p>
+ </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="idp45400336"></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="idp55531984"></a>3.4. Configuring the Graph</h3></div></div></div><p>
+ </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="idp50875760"></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="idp55535520"></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>
+ </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="idp50879376"></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.
@@ -241,7 +241,7 @@ NAR #88757, TRA #12200<br>
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="idp55545504"></a>Chapter 4. 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="#idp55546176">1. Barometric Sensor</a></span></dt><dt><span class="section"><a href="#idp55548928">2. Micro-controller</a></span></dt><dt><span class="section"><a href="#idp55551280">3. Lithium Battery</a></span></dt><dt><span class="section"><a href="#idp55554064">4. Atmospheric Model</a></span></dt><dt><span class="section"><a href="#idp55557040">5. Mechanical Considerations</a></span></dt><dt><span class="section"><a href="#idp55559792">6. On-board data storage</a></span></dt><dt><span class="section"><a href="#idp53369808">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="idp55546176"></a>1. Barometric Sensor</h2></div></div></div><p>
+ </p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp50889408"></a>Chapter 4. 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="#idp50890080">1. Barometric Sensor</a></span></dt><dt><span class="section"><a href="#idp50892832">2. Micro-controller</a></span></dt><dt><span class="section"><a href="#idp50895184">3. Lithium Battery</a></span></dt><dt><span class="section"><a href="#idp50897968">4. Atmospheric Model</a></span></dt><dt><span class="section"><a href="#idp50900944">5. Mechanical Considerations</a></span></dt><dt><span class="section"><a href="#idp50903696">6. On-board data storage</a></span></dt><dt><span class="section"><a href="#idp50924032">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="idp50890080"></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.
@@ -257,7 +257,7 @@ NAR #88757, TRA #12200<br>
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="idp55548928"></a>2. Micro-controller</h2></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp50892832"></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
@@ -268,7 +268,7 @@ NAR #88757, TRA #12200<br>
this mode, the chip consumes only .1&#956;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="idp55551280"></a>3. Lithium Battery</h2></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp50895184"></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
@@ -285,7 +285,7 @@ NAR #88757, TRA #12200<br>
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="idp55554064"></a>4. Atmospheric Model</h2></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp50897968"></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
@@ -305,7 +305,7 @@ NAR #88757, TRA #12200<br>
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="idp55557040"></a>5. Mechanical Considerations</h2></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp50900944"></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
@@ -321,7 +321,7 @@ NAR #88757, TRA #12200<br>
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="idp55559792"></a>6. On-board data storage</h2></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp50903696"></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
@@ -335,7 +335,7 @@ NAR #88757, TRA #12200<br>
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="idp55561904"></a><p class="title"><b>Table 4.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 &#8230; 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>
+ </p><div class="table"><a name="idp50905808"></a><p class="title"><b>Table 4.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 &#8230; 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
@@ -355,7 +355,7 @@ NAR #88757, TRA #12200<br>
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 class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp53369808"></a>7. MicroPeak Programming Interface</h2></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp50924032"></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 ×
diff --git a/AltOS/doc/micropeak.pdf b/AltOS/doc/micropeak.pdf
index 14b6c10..a8cba38 100644
--- a/AltOS/doc/micropeak.pdf
+++ b/AltOS/doc/micropeak.pdf
Binary files differ
diff --git a/AltOS/doc/release-notes-1.5.html b/AltOS/doc/release-notes-1.5.html
new file mode 100644
index 0000000..b1ed4a9
--- /dev/null
+++ b/AltOS/doc/release-notes-1.5.html
@@ -0,0 +1,68 @@
+<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>
diff --git a/AltOS/doc/scan-channels.png b/AltOS/doc/scan-channels.png
index bf6b6e5..e45880c 100644
--- a/AltOS/doc/scan-channels.png
+++ b/AltOS/doc/scan-channels.png
Binary files differ
diff --git a/AltOS/doc/telegps.html b/AltOS/doc/telegps.html
index 0a04380..6595a57 100644
--- a/AltOS/doc/telegps.html
+++ b/AltOS/doc/telegps.html
@@ -1,4 +1,4 @@
-<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="idp27051008"></a>TeleGPS Owner's Manual</h1></div><div><h2 class="subtitle">A recording GPS tracker</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Keith</span> <span class="surname">Packard</span></h3></div></div><div><p class="copyright">Copyright © 2014 Bdale Garbee and Keith Packard</p></div><div><div class="legalnotice"><a name="idp54268208"></a><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>TeleGPS Owner's Manual</title><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="book"><div class="titlepage"><div><div><h1 class="title"><a name="idp34092416"></a>TeleGPS Owner's Manual</h1></div><div><h2 class="subtitle">A recording GPS tracker</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Keith</span> <span class="surname">Packard</span></h3></div></div><div><p class="copyright">Copyright © 2014 Bdale Garbee and Keith Packard</p></div><div><div class="legalnotice"><a name="idp60435168"></a><p>
This document is released under the terms of the
<a class="ulink" href="http://creativecommons.org/licenses/by-sa/3.0/" target="_top">
Creative Commons ShareAlike 3.0
@@ -8,7 +8,7 @@
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="idp54273408"></a>Acknowledgements</h1></div></div></div><p>
+ </td></tr></table></div></div></div><hr></div><div class="dedication"><div class="titlepage"><div><div><h1 class="title"><a name="idp60440208"></a>Acknowledgements</h1></div></div></div><p>
Have fun using these products, and we hope to meet all of you
out on the rocket flight line somewhere.
</p><div class="literallayout"><p><br>
@@ -18,9 +18,9 @@ NAR #87103, TRA #12201<br>
Keith Packard, KD7SQG<br>
NAR #88757, TRA #12200<br>
      </p></div><p>
- </p></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="chapter"><a href="#idp54275776">1. Quick Start Guide</a></span></dt><dt><span class="chapter"><a href="#idp54280400">2. Handling Precautions</a></span></dt><dt><span class="chapter"><a href="#idp53558976">3. TeleGPS Hardware</a></span></dt><dd><dl><dt><span class="section"><a href="#idp53559648">1. Hooking Up Lithium Polymer Batteries</a></span></dt><dt><span class="section"><a href="#idp53562576">2. On-board Data Recording</a></span></dt><dt><span class="section"><a href="#idp53566784">3. Installation</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp53569904">4. System Operation</a></span></dt><dd><dl><dt><span class="section"><a href="#idp53570576">1. GFSK Telemetry</a></span></dt><dt><span class="section"><a href="#idp53573504">2. APRS</a></span></dt><dt><span class="section"><a href="#idp53403232">3. Configurable Parameters</a></span></dt><dd><dl><dt><span class="section"><a href="#idp53404560">3.1. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp53406688">3.2. Callsign</a></span></dt><dt><span class="section"><a href="#idp53407872">3.3. Telemetry/RDF/APRS Enable</a></span></dt><dt><span class="section"><a href="#idp53409200">3.4. APRS Interval</a></span></dt><dt><span class="section"><a href="#idp53410704">3.5. Maximum Flight Log</a></span></dt><dt><span class="section"><a href="#idp53412304">3.6. Logging Trigger Motion</a></span></dt><dt><span class="section"><a href="#idp53413632">3.7. Position Reporting Interval</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#idp53415280">5. TeleGPS Application</a></span></dt><dd><dl><dt><span class="section"><a href="#idp53416864">1. Telemetry Monitoring</a></span></dt><dd><dl><dt><span class="section"><a href="#idp58905744">1.1. Map</a></span></dt><dt><span class="section"><a href="#idp58911776">1.2. Location</a></span></dt><dt><span class="section"><a href="#idp58915056">1.3. Status</a></span></dt><dt><span class="section"><a href="#idp58918480">1.4. Table</a></span></dt></dl></dd><dt><span class="section"><a href="#idp58922432">2. TeleGPS Menus</a></span></dt><dd><dl><dt><span class="section"><a href="#idp58930528">2.1. New Window</a></span></dt><dt><span class="section"><a href="#idp58931856">2.2. Graph Data</a></span></dt><dt><span class="section"><a href="#idp55925216">2.3. Export Data</a></span></dt><dt><span class="section"><a href="#idp56070224">2.4. Load Maps</a></span></dt><dt><span class="section"><a href="#idp58955008">2.5. Preferences</a></span></dt><dt><span class="section"><a href="#idp58974944">2.6. Close</a></span></dt><dt><span class="section"><a href="#idp58976208">2.7. Exit</a></span></dt><dt><span class="section"><a href="#idp58977360">2.8. Connect Device</a></span></dt><dt><span class="section"><a href="#idp58980896">2.9. Disconnect</a></span></dt><dt><span class="section"><a href="#idp58982048">2.10. Scan Channels</a></span></dt><dt><span class="section"><a href="#idp58985600">2.11. Download Data</a></span></dt><dt><span class="section"><a href="#idp58988736">2.12. Configure Device</a></span></dt><dt><span class="section"><a href="#idp59012480">2.13. Flash Device</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#idp59014080">6. Updating Device Firmware</a></span></dt><dd><dl><dt><span class="section"><a href="#idp59016528">1.
+ </p></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="chapter"><a href="#idp60442576">1. Quick Start Guide</a></span></dt><dt><span class="chapter"><a href="#idp61322976">2. Handling Precautions</a></span></dt><dt><span class="chapter"><a href="#idp61325872">3. TeleGPS Hardware</a></span></dt><dd><dl><dt><span class="section"><a href="#idp61326544">1. Hooking Up Lithium Polymer Batteries</a></span></dt><dt><span class="section"><a href="#idp61329472">2. On-board Data Recording</a></span></dt><dt><span class="section"><a href="#idp61333680">3. Installation</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp60611120">4. System Operation</a></span></dt><dd><dl><dt><span class="section"><a href="#idp60611792">1. GFSK Telemetry</a></span></dt><dt><span class="section"><a href="#idp60614720">2. APRS</a></span></dt><dt><span class="section"><a href="#idp60452976">3. Configurable Parameters</a></span></dt><dd><dl><dt><span class="section"><a href="#idp60454304">3.1. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp60456432">3.2. Callsign</a></span></dt><dt><span class="section"><a href="#idp60457616">3.3. Telemetry/RDF/APRS Enable</a></span></dt><dt><span class="section"><a href="#idp60458944">3.4. APRS Interval</a></span></dt><dt><span class="section"><a href="#idp60460448">3.5. Maximum Flight Log</a></span></dt><dt><span class="section"><a href="#idp60462048">3.6. Logging Trigger Motion</a></span></dt><dt><span class="section"><a href="#idp60463376">3.7. Position Reporting Interval</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#idp60465024">5. TeleGPS Application</a></span></dt><dd><dl><dt><span class="section"><a href="#idp60466608">1. Telemetry Monitoring</a></span></dt><dd><dl><dt><span class="section"><a href="#idp65947584">1.1. Map</a></span></dt><dt><span class="section"><a href="#idp65953616">1.2. Location</a></span></dt><dt><span class="section"><a href="#idp65956928">1.3. Status</a></span></dt><dt><span class="section"><a href="#idp65960480">1.4. Table</a></span></dt></dl></dd><dt><span class="section"><a href="#idp65964528">2. TeleGPS Menus</a></span></dt><dd><dl><dt><span class="section"><a href="#idp65972624">2.1. New Window</a></span></dt><dt><span class="section"><a href="#idp65973952">2.2. Graph Data</a></span></dt><dt><span class="section"><a href="#idp65990624">2.3. Export Data</a></span></dt><dt><span class="section"><a href="#idp65996688">2.4. Load Maps</a></span></dt><dt><span class="section"><a href="#idp66010688">2.5. Preferences</a></span></dt><dt><span class="section"><a href="#idp66031072">2.6. Close</a></span></dt><dt><span class="section"><a href="#idp66032368">2.7. Exit</a></span></dt><dt><span class="section"><a href="#idp66033632">2.8. Connect Device</a></span></dt><dt><span class="section"><a href="#idp66037296">2.9. Disconnect</a></span></dt><dt><span class="section"><a href="#idp66038560">2.10. Scan Channels</a></span></dt><dt><span class="section"><a href="#idp66042240">2.11. Download Data</a></span></dt><dt><span class="section"><a href="#idp66045408">2.12. Configure Device</a></span></dt><dt><span class="section"><a href="#idp64831824">2.13. Flash Device</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#idp63308272">6. Updating Device Firmware</a></span></dt><dd><dl><dt><span class="section"><a href="#idp66058400">1.
Updating TeleGPS Firmware
- </a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp59025888">7. Technical Information</a></span></dt><dd><dl><dt><span class="section"><a href="#idp59026560">1. GPS Receiver</a></span></dt><dt><span class="section"><a href="#idp59029872">2. Micro-controller</a></span></dt><dt><span class="section"><a href="#idp59031200">3. Lithium Polymer Battery</a></span></dt><dt><span class="section"><a href="#idp59032464">4. Mechanical Considerations</a></span></dt><dt><span class="section"><a href="#idp59033792">5. On-board data storage</a></span></dt></dl></dd><dt><span class="appendix"><a href="#idp59035248">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="#idp53386560">Altus Metrum APRS Comments</a></dt></dl></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp54275776"></a>Chapter 1. Quick Start Guide</h1></div></div></div><p>
+ </a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp66067760">7. Technical Information</a></span></dt><dd><dl><dt><span class="section"><a href="#idp66068432">1. GPS Receiver</a></span></dt><dt><span class="section"><a href="#idp66071744">2. Micro-controller</a></span></dt><dt><span class="section"><a href="#idp66073072">3. Lithium Polymer Battery</a></span></dt><dt><span class="section"><a href="#idp66074336">4. Mechanical Considerations</a></span></dt><dt><span class="section"><a href="#idp66075664">5. On-board data storage</a></span></dt></dl></dd><dt><span class="appendix"><a href="#idp66077120">A. Release Notes</a></span></dt></dl></div><div class="list-of-tables"><p><b>List of Tables</b></p><dl><dt>4.1. <a href="#idp60617744">Altus Metrum APRS Comments</a></dt></dl></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp60442576"></a>Chapter 1. Quick Start Guide</h1></div></div></div><p>
TeleGPS is designed to be easy to use. Requiring no external
components, flying takes just a few steps.
</p><p>
@@ -42,7 +42,7 @@ NAR #88757, TRA #12200<br>
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="idp54280400"></a>Chapter 2. Handling Precautions</h1></div></div></div><p>
+ </p></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp61322976"></a>Chapter 2. Handling Precautions</h1></div></div></div><p>
All Altus Metrum products are sophisticated electronic devices.
When handled gently and properly installed in an air-frame, they
will deliver impressive results. However, as with all electronic
@@ -59,7 +59,7 @@ NAR #88757, TRA #12200<br>
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="idp53558976"></a>Chapter 3. TeleGPS Hardware</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp53559648">1. Hooking Up Lithium Polymer Batteries</a></span></dt><dt><span class="section"><a href="#idp53562576">2. On-board Data Recording</a></span></dt><dt><span class="section"><a href="#idp53566784">3. Installation</a></span></dt></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp53559648"></a>1. Hooking Up Lithium Polymer Batteries</h2></div></div></div><p>
+ </p></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp61325872"></a>Chapter 3. TeleGPS Hardware</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp61326544">1. Hooking Up Lithium Polymer Batteries</a></span></dt><dt><span class="section"><a href="#idp61329472">2. On-board Data Recording</a></span></dt><dt><span class="section"><a href="#idp61333680">3. Installation</a></span></dt></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp61326544"></a>1. Hooking Up Lithium Polymer Batteries</h2></div></div></div><p>
TeleGPS has a two pin JST PH series connector to connect up
a single-cell Lithium Polymer cell (3.7V nominal). You can
purchase matching batteries from the Altus Metrum store, or
@@ -72,7 +72,7 @@ NAR #88757, TRA #12200<br>
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="idp53562576"></a>2. On-board Data Recording</h2></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp61329472"></a>2. On-board Data Recording</h2></div></div></div><p>
TeleGPS logs GPS data at a user-configurable rate. Data are
logged to a 2MB on-board flash memory part, which can be
partitioned into several equal-sized blocks, one for each
@@ -101,7 +101,7 @@ NAR #88757, TRA #12200<br>
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="idp53566784"></a>3. Installation</h2></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp61333680"></a>3. Installation</h2></div></div></div><p>
The battery connectors are a standard 2-pin JST connector and
match batteries sold by Spark Fun. These batteries are
single-cell Lithium Polymer batteries that nominally provide 3.7
@@ -120,7 +120,7 @@ NAR #88757, TRA #12200<br>
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="idp53569904"></a>Chapter 4. System Operation</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp53570576">1. GFSK Telemetry</a></span></dt><dt><span class="section"><a href="#idp53573504">2. APRS</a></span></dt><dt><span class="section"><a href="#idp53403232">3. Configurable Parameters</a></span></dt><dd><dl><dt><span class="section"><a href="#idp53404560">3.1. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp53406688">3.2. Callsign</a></span></dt><dt><span class="section"><a href="#idp53407872">3.3. Telemetry/RDF/APRS Enable</a></span></dt><dt><span class="section"><a href="#idp53409200">3.4. APRS Interval</a></span></dt><dt><span class="section"><a href="#idp53410704">3.5. Maximum Flight Log</a></span></dt><dt><span class="section"><a href="#idp53412304">3.6. Logging Trigger Motion</a></span></dt><dt><span class="section"><a href="#idp53413632">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="idp53570576"></a>1. GFSK Telemetry</h2></div></div></div><p>
+ </p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp60611120"></a>Chapter 4. System Operation</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp60611792">1. GFSK Telemetry</a></span></dt><dt><span class="section"><a href="#idp60614720">2. APRS</a></span></dt><dt><span class="section"><a href="#idp60452976">3. Configurable Parameters</a></span></dt><dd><dl><dt><span class="section"><a href="#idp60454304">3.1. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp60456432">3.2. Callsign</a></span></dt><dt><span class="section"><a href="#idp60457616">3.3. Telemetry/RDF/APRS Enable</a></span></dt><dt><span class="section"><a href="#idp60458944">3.4. APRS Interval</a></span></dt><dt><span class="section"><a href="#idp60460448">3.5. Maximum Flight Log</a></span></dt><dt><span class="section"><a href="#idp60462048">3.6. Logging Trigger Motion</a></span></dt><dt><span class="section"><a href="#idp60463376">3.7. Position Reporting Interval</a></span></dt></dl></dd></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp60611792"></a>1. GFSK Telemetry</h2></div></div></div><p>
TeleGPS's native telemetry system doesn't use a 'normal packet
radio' mode like APRS because it's not very efficient. The
GFSK modulation we use is FSK with the base-band pulses passed
@@ -134,7 +134,7 @@ NAR #88757, TRA #12200<br>
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="idp53573504"></a>2. APRS</h2></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp60614720"></a>2. APRS</h2></div></div></div><p>
TeleGPS can send APRS if desired, and the
interval between APRS packets can be configured. As each APRS
packet takes a full second to transmit, we recommend an
@@ -157,7 +157,7 @@ NAR #88757, TRA #12200<br>
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="idp53386560"></a><p class="title"><b>Table 4.1. Altus Metrum APRS Comments</b></p><div class="table-contents"><table summary="Altus Metrum APRS Comments" border="1"><colgroup><col align="center" class="Field"><col align="center" class="Example"><col align="center" class="Description"></colgroup><thead><tr><th align="center">Field</th><th align="center">Example</th><th align="center">Description</th></tr></thead><tbody><tr><td align="center">1</td><td align="center">L</td><td align="center">GPS Status U for unlocked, L for locked</td></tr><tr><td align="center">2</td><td align="center">6</td><td align="center">Number of Satellites in View</td></tr><tr><td align="center">3</td><td align="center">B4.0</td><td align="center">Battery Voltage</td></tr></tbody></table></div></div><br class="table-break"><p>
+ </p><div class="table"><a name="idp60617744"></a><p class="title"><b>Table 4.1. Altus Metrum APRS Comments</b></p><div class="table-contents"><table summary="Altus Metrum APRS Comments" border="1"><colgroup><col align="center" class="Field"><col align="center" class="Example"><col align="center" class="Description"></colgroup><thead><tr><th align="center">Field</th><th align="center">Example</th><th align="center">Description</th></tr></thead><tbody><tr><td align="center">1</td><td align="center">L</td><td align="center">GPS Status U for unlocked, L for locked</td></tr><tr><td align="center">2</td><td align="center">6</td><td align="center">Number of Satellites in View</td></tr><tr><td align="center">3</td><td align="center">B4.0</td><td align="center">Battery Voltage</td></tr></tbody></table></div></div><br class="table-break"><p>
Here's an example of an APRS comment showing GPS lock with 6
satellites in view and a battery at 4.0V.
</p><pre class="screen">
@@ -175,13 +175,13 @@ NAR #88757, TRA #12200<br>
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="idp53403232"></a>3. Configurable Parameters</h2></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp60452976"></a>3. Configurable Parameters</h2></div></div></div><p>
Configuring TeleGPS is very
simple; the few configurable parameters can all be set
using the TeleGPS application over USB. Read
the Configure TeleGPS section in the TeleGPS Software chapter below
for more information.
- </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp53404560"></a>3.1. Radio Frequency</h3></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp60454304"></a>3.1. Radio Frequency</h3></div></div></div><p>
Altus Metrum boards support radio frequencies in the 70cm
band. By default, the configuration interface provides a
list of 10 &#8220;standard&#8221; frequencies in 100kHz channels starting at
@@ -191,19 +191,19 @@ NAR #88757, TRA #12200<br>
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="idp53406688"></a>3.2. Callsign</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp60456432"></a>3.2. Callsign</h3></div></div></div><p>
This sets the callsign used for telemetry and APRS to
identify the device.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp53407872"></a>3.3. Telemetry/RDF/APRS Enable</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp60457616"></a>3.3. Telemetry/RDF/APRS Enable</h3></div></div></div><p>
You can completely disable the radio, if necessary, leaving
TeleGPS only logging data to internal memory.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp53409200"></a>3.4. APRS Interval</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp60458944"></a>3.4. APRS Interval</h3></div></div></div><p>
This selects how often APRS packets are transmitted. Set
this to zero to disable APRS without also disabling the
regular telemetry and RDF transmissions. As APRS takes a
full second to transmit a single position report, we
recommend sending packets no more than once every 5 seconds.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp53410704"></a>3.5. Maximum Flight Log</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp60460448"></a>3.5. Maximum Flight Log</h3></div></div></div><p>
Changing this value will set the maximum amount of flight
log storage that an individual flight will use. The
available storage is divided into as many flights of the
@@ -211,14 +211,14 @@ NAR #88757, TRA #12200<br>
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="idp53412304"></a>3.6. Logging Trigger Motion</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp60462048"></a>3.6. Logging Trigger Motion</h3></div></div></div><p>
If TeleGPS moves less than this distance over a long period
of time, it will not log that location, saving storage space.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp53413632"></a>3.7. Position Reporting Interval</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp60463376"></a>3.7. Position Reporting Interval</h3></div></div></div><p>
This sets how often TeleGPS reports position information via
telemetry and to the on-board log. Reducing this value will
save power and logging memory consumption.
- </p></div></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp53415280"></a>Chapter 5. TeleGPS Application</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp53416864">1. Telemetry Monitoring</a></span></dt><dd><dl><dt><span class="section"><a href="#idp58905744">1.1. Map</a></span></dt><dt><span class="section"><a href="#idp58911776">1.2. Location</a></span></dt><dt><span class="section"><a href="#idp58915056">1.3. Status</a></span></dt><dt><span class="section"><a href="#idp58918480">1.4. Table</a></span></dt></dl></dd><dt><span class="section"><a href="#idp58922432">2. TeleGPS Menus</a></span></dt><dd><dl><dt><span class="section"><a href="#idp58930528">2.1. New Window</a></span></dt><dt><span class="section"><a href="#idp58931856">2.2. Graph Data</a></span></dt><dt><span class="section"><a href="#idp55925216">2.3. Export Data</a></span></dt><dt><span class="section"><a href="#idp56070224">2.4. Load Maps</a></span></dt><dt><span class="section"><a href="#idp58955008">2.5. Preferences</a></span></dt><dt><span class="section"><a href="#idp58974944">2.6. Close</a></span></dt><dt><span class="section"><a href="#idp58976208">2.7. Exit</a></span></dt><dt><span class="section"><a href="#idp58977360">2.8. Connect Device</a></span></dt><dt><span class="section"><a href="#idp58980896">2.9. Disconnect</a></span></dt><dt><span class="section"><a href="#idp58982048">2.10. Scan Channels</a></span></dt><dt><span class="section"><a href="#idp58985600">2.11. Download Data</a></span></dt><dt><span class="section"><a href="#idp58988736">2.12. Configure Device</a></span></dt><dt><span class="section"><a href="#idp59012480">2.13. Flash Device</a></span></dt></dl></dd></dl></div><p>
+ </p></div></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp60465024"></a>Chapter 5. TeleGPS Application</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp60466608">1. Telemetry Monitoring</a></span></dt><dd><dl><dt><span class="section"><a href="#idp65947584">1.1. Map</a></span></dt><dt><span class="section"><a href="#idp65953616">1.2. Location</a></span></dt><dt><span class="section"><a href="#idp65956928">1.3. Status</a></span></dt><dt><span class="section"><a href="#idp65960480">1.4. Table</a></span></dt></dl></dd><dt><span class="section"><a href="#idp65964528">2. TeleGPS Menus</a></span></dt><dd><dl><dt><span class="section"><a href="#idp65972624">2.1. New Window</a></span></dt><dt><span class="section"><a href="#idp65973952">2.2. Graph Data</a></span></dt><dt><span class="section"><a href="#idp65990624">2.3. Export Data</a></span></dt><dt><span class="section"><a href="#idp65996688">2.4. Load Maps</a></span></dt><dt><span class="section"><a href="#idp66010688">2.5. Preferences</a></span></dt><dt><span class="section"><a href="#idp66031072">2.6. Close</a></span></dt><dt><span class="section"><a href="#idp66032368">2.7. Exit</a></span></dt><dt><span class="section"><a href="#idp66033632">2.8. Connect Device</a></span></dt><dt><span class="section"><a href="#idp66037296">2.9. Disconnect</a></span></dt><dt><span class="section"><a href="#idp66038560">2.10. Scan Channels</a></span></dt><dt><span class="section"><a href="#idp66042240">2.11. Download Data</a></span></dt><dt><span class="section"><a href="#idp66045408">2.12. Configure Device</a></span></dt><dt><span class="section"><a href="#idp64831824">2.13. Flash Device</a></span></dt></dl></dd></dl></div><p>
The TeleGPS application provides a graphical user interface for
interacting with the Altus Metrum product family. TeleGPS can
monitor telemetry data, configure devices and many other
@@ -227,7 +227,7 @@ NAR #88757, TRA #12200<br>
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="idp53416864"></a>1. Telemetry Monitoring</h2></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp60466608"></a>1. Telemetry Monitoring</h2></div></div></div><p>
This is the window brought up when you start the
application. If you have a TeleDongle device connected to the
computer, it will automatically be selected for telemetry monitoring
@@ -266,7 +266,7 @@ NAR #88757, TRA #12200<br>
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="idp58905744"></a>1.1. Map</h3></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp65947584"></a>1.1. Map</h3></div></div></div><p>
The Map tab shows the TeleGPS track over time on top of map
data making it easy to locate the device.
</p><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="495"><tr><td><img src="telegps-map.png" width="495"></td></tr></table></div></div><p>
@@ -289,16 +289,16 @@ NAR #88757, TRA #12200<br>
</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="idp58911776"></a>1.2. Location</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp65953616"></a>1.2. Location</h3></div></div></div><p>
The Location tab shows the raw GPS data received from TeleGPS.
- </p><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="495"><tr><td><img src="telegps-location.png" width="495"></td></tr></table></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp58915056"></a>1.3. Status</h3></div></div></div><p>
+ </p><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="495"><tr><td><img src="telegps-location.png" width="495"></td></tr></table></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp65956928"></a>1.3. Status</h3></div></div></div><p>
The Status tab shows data relative to the location of
TeleGPS when the application first received telemetry from
it.
- </p><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="495"><tr><td><img src="telegps-status.png" width="495"></td></tr></table></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp58918480"></a>1.4. Table</h3></div></div></div><p>
+ </p><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="495"><tr><td><img src="telegps-status.png" width="495"></td></tr></table></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp65960480"></a>1.4. Table</h3></div></div></div><p>
The Table tab shows detailed information about the GPS
receiver
- </p><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="495"><tr><td><img src="telegps-table.png" width="495"></td></tr></table></div></div></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp58922432"></a>2. TeleGPS Menus</h2></div></div></div><p>
+ </p><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="495"><tr><td><img src="telegps-table.png" width="495"></td></tr></table></div></div></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp65964528"></a>2. TeleGPS Menus</h2></div></div></div><p>
TeleGPS has three or four menus at the top of the window:
</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">File</span></dt><dd><p>
New Window, Graph Data, Export Data, Load Maps, Preferences, Close and Exit
@@ -314,26 +314,26 @@ NAR #88757, TRA #12200<br>
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="idp58930528"></a>2.1. New Window</h3></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp65972624"></a>2.1. New Window</h3></div></div></div><p>
This creates another telemetry monitoring window, in case
you have multiple TeleDongle devices connected to the
computer.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp58931856"></a>2.2. Graph Data</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp65973952"></a>2.2. Graph Data</h3></div></div></div><p>
This brings up a file dialog to load a saved log, either
a .telem file of recorded telemetry or .eeprom of saved
data from on-board memory. It looks a bit like the flight
monitoring window, using a selection of tabs to show
different views of the saved data.
- </p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp58933200"></a>2.2.1. Graph</h4></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp65975296"></a>2.2.1. Graph</h4></div></div></div><p>
The Graph tab shows a plot of the the GPS data
collected. The X axis is time in seconds; there are a
variety of Y axes available for different kinds of data.
- </p><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="540"><tr><td><img src="telegps-graph-graph.png" width="540"></td></tr></table></div></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp58937104"></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>
+ </p><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="540"><tr><td><img src="telegps-graph-graph.png" width="540"></td></tr></table></div></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp65979104"></a>2.2.2. Configure Graph</h4></div></div></div><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="540"><tr><td><img src="telegps-graph-configure.png" width="540"></td></tr></table></div></div><p>
This selects which graph elements to show, and, at the
bottom, lets you switch between metric and imperial units
- </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp58940880"></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>
+ </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp65982880"></a>2.2.3. Statistics</h4></div></div></div><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="540"><tr><td><img src="telegps-graph-stats.png" width="540"></td></tr></table></div></div><p>
Shows overall data computed from the flight.
- </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp58944496"></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>
+ </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp65986496"></a>2.2.4. Map</h4></div></div></div><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="540"><tr><td><img src="telegps-graph-map.png" width="540"></td></tr></table></div></div><p>
Shows a map of the area overlaid with the GPS track. As with
the telemetry monitoring window, you can select the style
of map and zoom level using buttons along the side;
@@ -341,7 +341,7 @@ NAR #88757, TRA #12200<br>
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="idp55925216"></a>2.3. Export Data</h3></div></div></div><p>
+ </p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp65990624"></a>2.3. Export Data</h3></div></div></div><p>
This tool takes the raw data files and makes them available for
external analysis. When you select this button, you are prompted to
select a data file, which can be either a .eeprom or .telem.
@@ -350,7 +350,7 @@ NAR #88757, TRA #12200<br>
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="idp56823520"></a>2.3.1. Comma Separated Value Format</h4></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp65992768"></a>2.3.1. Comma Separated Value Format</h4></div></div></div><p>
This is a text file containing the data in a form suitable for
import into a spreadsheet or other external data analysis
tool. The first few lines of the file contain the version and
@@ -364,11 +364,11 @@ NAR #88757, TRA #12200<br>
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="idp56832480"></a>2.3.2. Keyhole Markup Language (for Google Earth)</h4></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp65995200"></a>2.3.2. Keyhole Markup Language (for Google Earth)</h4></div></div></div><p>
This is the format used by Google Earth to provide an overlay
within that application. With this, you can use Google Earth to
see the whole flight path in 3D.
- </p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp56070224"></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>
+ </p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp65996688"></a>2.4. Load Maps</h3></div></div></div><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="468"><tr><td><img src="load-maps.png" width="468"></td></tr></table></div></div><p>
Before using TeleGPS, you can use Load Maps to load map data
in case you don't have access to the internet while
receiving telemetry.
@@ -413,7 +413,7 @@ NAR #88757, TRA #12200<br>
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="idp58955008"></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="idp58958016"></a>2.5.1. Voice Settings</h4></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp66010688"></a>2.5. Preferences</h3></div></div></div><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="216"><tr><td><img src="telegps-preferences.png" width="216"></td></tr></table></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp66013824"></a>2.5.1. Voice Settings</h4></div></div></div><p>
AltosUI provides voice announcements during flight so that you
can keep your eyes on the sky and still get information about
the current flight status. However, sometimes you don't want
@@ -422,7 +422,7 @@ NAR #88757, TRA #12200<br>
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="idp58963040"></a>2.5.2. Log Directory</h4></div></div></div><p>
+ </p></dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp66018944"></a>2.5.2. Log Directory</h4></div></div></div><p>
AltosUI logs all telemetry data and saves all TeleMetrum flash
data to this directory. This directory is also used as the
staring point when selecting data files for display or export.
@@ -430,7 +430,7 @@ NAR #88757, TRA #12200<br>
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="idp58965072"></a>2.5.3. Callsign</h4></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp66021008"></a>2.5.3. Callsign</h4></div></div></div><p>
This value is transmitted in each command packet sent from
TeleDongle and received from an altimeter. It is not used in
telemetry mode, as the callsign configured in the altimeter board
@@ -443,51 +443,51 @@ NAR #88757, TRA #12200<br>
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="idp58967344"></a>2.5.4. Imperial Units</h4></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp66023312"></a>2.5.4. Imperial Units</h4></div></div></div><p>
This switches between metric units (meters) and imperial
units (feet and miles). This affects the display of values
use during flight monitoring, configuration, data graphing
and all of the voice announcements. It does not change the
units used when exporting to CSV files, those are always
produced in metric units.
- </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp58968864"></a>2.5.5. Serial Debug</h4></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp66024864"></a>2.5.5. Serial Debug</h4></div></div></div><p>
This causes all communication with a connected device to be
dumped to the console from which AltosUI was started. If
you've started it from an icon or menu entry, the output
will simply be discarded. This mode can be useful to debug
various serial communication issues.
- </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp58970368"></a>2.5.6. Font Size</h4></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp66026400"></a>2.5.6. Font Size</h4></div></div></div><p>
Selects the set of fonts used in the flight monitor
window. Choose between the small, medium and large sets.
- </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp58971664"></a>2.5.7. Look &amp; Feel</h4></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp66027728"></a>2.5.7. Look &amp; 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="idp58972960"></a>2.5.8. Manage Frequencies</h4></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp66029056"></a>2.5.8. Manage Frequencies</h4></div></div></div><p>
This brings up a dialog where you can configure the set of
frequencies shown in the various frequency menus. You can
add as many as you like, or even reconfigure the default
set. Changing this list does not affect the frequency
settings of any devices, it only changes the set of
frequencies shown in the menus.
- </p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp58974944"></a>2.6. Close</h3></div></div></div><p>
+ </p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp66031072"></a>2.6. Close</h3></div></div></div><p>
This closes the current window, leaving any other windows
open and the application running.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp58976208"></a>2.7. Exit</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp66032368"></a>2.7. Exit</h3></div></div></div><p>
This closes all TeleGPS windows and terminates the application.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp58977360"></a>2.8. Connect Device</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp66033632"></a>2.8. Connect Device</h3></div></div></div><p>
Selecting this item brings up a dialog box listing all of
the connected TeleDongle devices. When you choose one of
these, AltosUI will display telemetry data as received by
the selected TeleDongle device.
- </p><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="279"><tr><td><img src="device-selection.png" width="279"></td></tr></table></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp58980896"></a>2.9. Disconnect</h3></div></div></div><p>
+ </p><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="279"><tr><td><img src="device-selection.png" width="279"></td></tr></table></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp66037296"></a>2.9. Disconnect</h3></div></div></div><p>
Disconnects the currently connected TeleDongle or TeleBT
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp58982048"></a>2.10. Scan Channels</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp66038560"></a>2.10. Scan Channels</h3></div></div></div><p>
Scans the configured set of frequencies looking for
telemetry signals. A list of all of the discovered signals
is show; selecting one of those and clicking on 'Monitor'
will select that frequency in the associated TeleGPS
application window.
- </p><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="279"><tr><td><img src="telegps-scan.png" width="279"></td></tr></table></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp58985600"></a>2.11. Download Data</h3></div></div></div><p>
+ </p><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="279"><tr><td><img src="telegps-scan.png" width="279"></td></tr></table></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp66042240"></a>2.11. Download Data</h3></div></div></div><p>
TeleGPS records data to its internal flash memory.
On-board data is recorded at the same rate as telemetry
but is not subject to radio drop-outs. As
@@ -508,7 +508,7 @@ NAR #88757, TRA #12200<br>
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="idp58988736"></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>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp66045408"></a>2.12. Configure Device</h3></div></div></div><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="324"><tr><td><img src="telegps-configure.png" width="324"></td></tr></table></div></div><p>
Select this button and then select any connected TeleGPS
device from the list provided.
</p><p>
@@ -534,13 +534,13 @@ NAR #88757, TRA #12200<br>
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="idp59000864"></a>2.12.1. Frequency</h4></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp63831792"></a>2.12.1. Frequency</h4></div></div></div><p>
This configures which of the frequencies to use for both
telemetry and packet command mode. Note that if you set this
value via packet command mode, the TeleDongle frequency will
also be automatically reconfigured to match so that
communication will continue afterwards.
- </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp59002368"></a>2.12.2. RF Calibration</h4></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp63587264"></a>2.12.2. RF Calibration</h4></div></div></div><p>
The radios in every Altus Metrum device are calibrated at the
factory to ensure that they transmit and receive on the
specified frequency. If you need to you can adjust the calibration
@@ -548,11 +548,11 @@ NAR #88757, TRA #12200<br>
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="idp59004032"></a>2.12.3. Telemetry/RDF/APRS Enable</h4></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp64336224"></a>2.12.3. Telemetry/RDF/APRS Enable</h4></div></div></div><p>
Enables the radio for transmission during flight. When
disabled, the radio will not transmit anything during flight
at all.
- </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp59005344"></a>2.12.4. APRS Interval</h4></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp62178976"></a>2.12.4. APRS Interval</h4></div></div></div><p>
How often to transmit GPS information via APRS (in
seconds). When set to zero, APRS transmission is
disabled. This option is available on TeleMetrum v2 and
@@ -560,26 +560,26 @@ NAR #88757, TRA #12200<br>
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="idp59006928"></a>2.12.5. Callsign</h4></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp63605184"></a>2.12.5. Callsign</h4></div></div></div><p>
This sets the call sign included in each telemetry packet. Set this
as needed to conform to your local radio regulations.
- </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp59008256"></a>2.12.6. Maximum Log Size</h4></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp64195792"></a>2.12.6. Maximum Log Size</h4></div></div></div><p>
This sets the space (in kilobytes) allocated for each data
log. The available space will be divided into chunks of this
size. A smaller value will allow more logs to be stored,
a larger value will record data for longer times.
- </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp59009696"></a>2.12.7. Logging Trigger Motion</h4></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp63537840"></a>2.12.7. Logging Trigger Motion</h4></div></div></div><p>
If TeleGPS moves less than this distance over a long period
of time, it will not log that location, saving storage space.
- </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp59011008"></a>2.12.8. Position Reporting Interval</h4></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp63009520"></a>2.12.8. Position Reporting Interval</h4></div></div></div><p>
This sets how often TeleGPS reports position information via
telemetry and to the on-board log. Reducing this value will
save power and logging memory consumption.
- </p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp59012480"></a>2.13. Flash Device</h3></div></div></div><p>
+ </p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp64831824"></a>2.13. Flash Device</h3></div></div></div><p>
This reprograms TeleGPS devices with new firmware. Please
read the directions for flashing devices in the Updating
Device Firmware chapter below.
- </p></div></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp59014080"></a>Chapter 6. Updating Device Firmware</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp59016528">1.
+ </p></div></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp63308272"></a>Chapter 6. Updating Device Firmware</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp66058400">1.
Updating TeleGPS Firmware
</a></span></dt></dl></div><p>
TeleGPS is programmed directly over its USB connectors.
@@ -591,7 +591,7 @@ NAR #88757, TRA #12200<br>
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="idp59016528"></a>1. 
+ </p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp66058400"></a>1. 
Updating TeleGPS Firmware
</h2></div></div></div><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>
Attach a battery and power switch to the target
@@ -618,24 +618,24 @@ NAR #88757, TRA #12200<br>
</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="idp59025888"></a>Chapter 7. Technical Information</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp59026560">1. GPS Receiver</a></span></dt><dt><span class="section"><a href="#idp59029872">2. Micro-controller</a></span></dt><dt><span class="section"><a href="#idp59031200">3. Lithium Polymer Battery</a></span></dt><dt><span class="section"><a href="#idp59032464">4. Mechanical Considerations</a></span></dt><dt><span class="section"><a href="#idp59033792">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="idp59026560"></a>1. GPS Receiver</h2></div></div></div><p>
+ </p></li></ol></div></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp66067760"></a>Chapter 7. Technical Information</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp66068432">1. GPS Receiver</a></span></dt><dt><span class="section"><a href="#idp66071744">2. Micro-controller</a></span></dt><dt><span class="section"><a href="#idp66073072">3. Lithium Polymer Battery</a></span></dt><dt><span class="section"><a href="#idp66074336">4. Mechanical Considerations</a></span></dt><dt><span class="section"><a href="#idp66075664">5. On-board data storage</a></span></dt></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp66068432"></a>1. GPS Receiver</h2></div></div></div><p>
TeleGPS uses the u-Blox Max-7Q GPS receiver.
- </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp59029872"></a>2. Micro-controller</h2></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp66071744"></a>2. Micro-controller</h2></div></div></div><p>
TeleGPS uses an NXP LPC11U14 micro-controller. This tiny
CPU contains 32kB of flash for the application and 4kB of RAM for
temporary data storage.
- </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp59031200"></a>3. Lithium Polymer Battery</h2></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp66073072"></a>3. Lithium Polymer Battery</h2></div></div></div><p>
Shipping restrictions may prevent us from including a battery
battery with TeleGPS.
- </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp59032464"></a>4. Mechanical Considerations</h2></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp66074336"></a>4. Mechanical Considerations</h2></div></div></div><p>
TeleGPS is designed to be rugged enough for typical rocketry
applications. The 4 mounting holes on the board are sized for
use with 4-40 or M3 screws.
- </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp59033792"></a>5. On-board data storage</h2></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp66075664"></a>5. On-board data storage</h2></div></div></div><p>
TeleGPS has 2MB of non-volatile storage, separate from the
code storage memory. The TeleGPS firmware uses this to log
information during flight.
- </p></div></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a name="idp59035248"></a>Appendix A. Release Notes</h1></div></div></div><div class="simplesect"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp59035888"></a>Version 1.41</h2></div></div></div><p>
+ </p></div></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a name="idp66077120"></a>Appendix A. Release Notes</h1></div></div></div><div class="simplesect"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp66077760"></a>Version 1.41</h2></div></div></div><p>
Version 1.4.1 is a minor release. It fixes install issues on
Windows and provides the missing TeleMetrum V2.0 firmware. There
aren't any changes to the firmware or host applications at
@@ -666,7 +666,7 @@ NAR #88757, TRA #12200<br>
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="idp59037488"></a>Version 1.4</h2></div></div></div><p>
+ </p></div><div class="simplesect"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp66079360"></a>Version 1.4</h2></div></div></div><p>
Version 1.4 is a major release. It includes support for our new
TeleGPS product, new features and bug fixes in in the flight
software for all our boards and the AltosUI ground station
diff --git a/AltOS/doc/telegps.pdf b/AltOS/doc/telegps.pdf
index fb5d50e..26703dc 100644
--- a/AltOS/doc/telegps.pdf
+++ b/AltOS/doc/telegps.pdf
Binary files differ
diff --git a/AltOS/doc/telemega-outline.pdf b/AltOS/doc/telemega-outline.pdf
index 11d5ba0..19d8be4 100644
--- a/AltOS/doc/telemega-outline.pdf
+++ b/AltOS/doc/telemega-outline.pdf
Binary files differ
diff --git a/AltOS/doc/telemetrum-outline.pdf b/AltOS/doc/telemetrum-outline.pdf
index 4656707..35b22a3 100644
--- a/AltOS/doc/telemetrum-outline.pdf
+++ b/AltOS/doc/telemetrum-outline.pdf
Binary files differ
diff --git a/AltOS/doc/telemetry.html b/AltOS/doc/telemetry.html
index 894ce92..7dc82f9 100644
--- a/AltOS/doc/telemetry.html
+++ b/AltOS/doc/telemetry.html
@@ -1,10 +1,10 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>AltOS Telemetry</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"><div><div><h2 class="title"><a name="idp10941344"></a>AltOS Telemetry</h2></div><div><h3 class="subtitle"><i>Packet Definitions</i></h3></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 © 2011 Keith Packard</p></div><div><div class="legalnotice"><a name="idp37435552"></a><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>AltOS Telemetry</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"><div><div><h2 class="title"><a name="idp23713408"></a>AltOS Telemetry</h2></div><div><h3 class="subtitle"><i>Packet Definitions</i></h3></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 © 2011 Keith Packard</p></div><div><div class="legalnotice"><a name="idp50134720"></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">01 July 2011</td></tr><tr><td align="left" colspan="2">Initial content</td></tr></table></div></div></div><hr></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp37314080">1. Packet Format Design</a></span></dt><dt><span class="section"><a href="#idp37316784">2. Packet Formats</a></span></dt><dd><dl><dt><span class="section"><a href="#idp37317984">2.1. Packet Header</a></span></dt><dt><span class="section"><a href="#idp41696096">2.2. Sensor Data</a></span></dt><dt><span class="section"><a href="#idp42829136">2.3. Configuration Data</a></span></dt><dt><span class="section"><a href="#idp42864656">2.4. GPS Location</a></span></dt><dt><span class="section"><a href="#idp42938656">2.5. GPS Satellite Data</a></span></dt></dl></dd><dt><span class="section"><a href="#idp42977376">3. Data Transmission</a></span></dt><dd><dl><dt><span class="section"><a href="#idp42978752">3.1. Modulation Scheme</a></span></dt><dt><span class="section"><a href="#idp42995184">3.2. Error Correction</a></span></dt></dl></dd><dt><span class="section"><a href="#idp43008656">4. TeleDongle packet format</a></span></dt><dt><span class="section"><a href="#idp43030240">5. History and Motivation</a></span></dt></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp37314080"></a>1. Packet Format Design</h2></div></div></div><p>
+ </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">01 July 2011</td></tr><tr><td align="left" colspan="2">Initial content</td></tr></table></div></div></div><hr></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp50058048">1. Packet Format Design</a></span></dt><dt><span class="section"><a href="#idp50061040">2. Packet Formats</a></span></dt><dd><dl><dt><span class="section"><a href="#idp50062240">2.1. Packet Header</a></span></dt><dt><span class="section"><a href="#idp50230704">2.2. Sensor Data</a></span></dt><dt><span class="section"><a href="#idp55625232">2.3. Configuration Data</a></span></dt><dt><span class="section"><a href="#idp55660688">2.4. GPS Location</a></span></dt><dt><span class="section"><a href="#idp52445616">2.5. GPS Satellite Data</a></span></dt></dl></dd><dt><span class="section"><a href="#idp55771872">3. Data Transmission</a></span></dt><dd><dl><dt><span class="section"><a href="#idp55773248">3.1. Modulation Scheme</a></span></dt><dt><span class="section"><a href="#idp55789680">3.2. Error Correction</a></span></dt></dl></dd><dt><span class="section"><a href="#idp55803152">4. TeleDongle packet format</a></span></dt><dt><span class="section"><a href="#idp55824736">5. History and Motivation</a></span></dt></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp50058048"></a>1. Packet Format Design</h2></div></div></div><p>
AltOS telemetry data is split into multiple different packets,
all the same size, but each includs an identifier so that the
ground station can distinguish among different types. A single
@@ -22,14 +22,14 @@
All packet types start with a five byte header which encodes the
device serial number, device clock value and the packet
type. The remaining 27 bytes encode type-specific data.
- </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp37316784"></a>2. Packet Formats</h2></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp50061040"></a>2. Packet Formats</h2></div></div></div><p>
This section first defines the packet header common to all packets
and then the per-packet data layout.
- </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp37317984"></a>2.1. Packet Header</h3></div></div></div><div class="table"><a name="idp37318656"></a><p class="title"><b>Table 1. Telemetry Packet Header</b></p><div class="table-contents"><table summary="Telemetry Packet Header" border="1"><colgroup><col align="center" class="Offset"><col align="center" class="Data Type"><col align="left" class="Name"><col align="left" class="Description"></colgroup><thead><tr><th align="center">Offset</th><th align="center">Data Type</th><th align="center">Name</th><th align="center">Description</th></tr></thead><tbody><tr><td align="center">0</td><td align="center">uint16_t</td><td align="left">serial</td><td align="left">Device serial Number</td></tr><tr><td align="center">2</td><td align="center">uint16_t</td><td align="left">tick</td><td align="left">Device time in 100ths of a second</td></tr><tr><td align="center">4</td><td align="center">uint8_t</td><td align="left">type</td><td align="left">Packet type</td></tr><tr><td align="center">5</td><td class="auto-generated"> </td><td class="auto-generated"> </td><td class="auto-generated"> </td></tr></tbody></table></div></div><br class="table-break"><p>
+ </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp50062240"></a>2.1. Packet Header</h3></div></div></div><div class="table"><a name="idp50062912"></a><p class="title"><b>Table 1. Telemetry Packet Header</b></p><div class="table-contents"><table summary="Telemetry Packet Header" border="1"><colgroup><col align="center" class="Offset"><col align="center" class="Data Type"><col align="left" class="Name"><col align="left" class="Description"></colgroup><thead><tr><th align="center">Offset</th><th align="center">Data Type</th><th align="center">Name</th><th align="center">Description</th></tr></thead><tbody><tr><td align="center">0</td><td align="center">uint16_t</td><td align="left">serial</td><td align="left">Device serial Number</td></tr><tr><td align="center">2</td><td align="center">uint16_t</td><td align="left">tick</td><td align="left">Device time in 100ths of a second</td></tr><tr><td align="center">4</td><td align="center">uint8_t</td><td align="left">type</td><td align="left">Packet type</td></tr><tr><td align="center">5</td><td class="auto-generated"> </td><td class="auto-generated"> </td><td class="auto-generated"> </td></tr></tbody></table></div></div><br class="table-break"><p>
Each packet starts with these five bytes which serve to identify
which device has transmitted the packet, when it was transmitted
and what the rest of the packet contains.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp41696096"></a>2.2. Sensor Data</h3></div></div></div><div class="informaltable"><table border="0"><colgroup><col align="center" class="Offset"><col align="left" class="Description"></colgroup><thead><tr><th align="center">Type</th><th align="left">Description</th></tr></thead><tbody><tr><td align="center">0x01</td><td align="left">TeleMetrum Sensor Data</td></tr><tr><td align="center">0x02</td><td align="left">TeleMini Sensor Data</td></tr><tr><td align="center">0x03</td><td align="left">TeleNano Sensor Data</td></tr></tbody></table></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp50230704"></a>2.2. Sensor Data</h3></div></div></div><div class="informaltable"><table border="0"><colgroup><col align="center" class="Offset"><col align="left" class="Description"></colgroup><thead><tr><th align="center">Type</th><th align="left">Description</th></tr></thead><tbody><tr><td align="center">0x01</td><td align="left">TeleMetrum Sensor Data</td></tr><tr><td align="center">0x02</td><td align="left">TeleMini Sensor Data</td></tr><tr><td align="center">0x03</td><td align="left">TeleNano Sensor Data</td></tr></tbody></table></div><p>
TeleMetrum, TeleMini and TeleNano share this same packet
format for sensor data. Each uses a distinct packet type so
that the receiver knows which data values are valid and which
@@ -38,63 +38,63 @@
Sensor Data packets are transmitted once per second on the
ground, 10 times per second during ascent and once per second
during descent and landing
- </p><div class="table"><a name="idp41708160"></a><p class="title"><b>Table 2. Sensor Packet Contents</b></p><div class="table-contents"><table summary="Sensor Packet Contents" border="1"><colgroup><col align="center" class="Offset"><col align="center" class="Data Type"><col align="left" class="Name"><col align="left" class="Description"></colgroup><thead><tr><th align="center">Offset</th><th align="center">Data Type</th><th align="center">Name</th><th align="center">Description</th></tr></thead><tbody><tr><td align="center">5</td><td align="center">uint8_t</td><td align="left">state</td><td align="left">Flight state</td></tr><tr><td align="center">6</td><td align="center">int16_t</td><td align="left">accel</td><td align="left">accelerometer (TM only)</td></tr><tr><td align="center">8</td><td align="center">int16_t</td><td align="left">pres</td><td align="left">pressure sensor</td></tr><tr><td align="center">10</td><td align="center">int16_t</td><td align="left">temp</td><td align="left">temperature sensor</td></tr><tr><td align="center">12</td><td align="center">int16_t</td><td align="left">v_batt</td><td align="left">battery voltage</td></tr><tr><td align="center">14</td><td align="center">int16_t</td><td align="left">sense_d</td><td align="left">drogue continuity sense (TM/Tm)</td></tr><tr><td align="center">16</td><td align="center">int16_t</td><td align="left">sense_m</td><td align="left">main continuity sense (TM/Tm)</td></tr><tr><td align="center">18</td><td align="center">int16_t</td><td align="left">acceleration</td><td align="left">m/s² * 16</td></tr><tr><td align="center">20</td><td align="center">int16_t</td><td align="left">speed</td><td align="left">m/s * 16</td></tr><tr><td align="center">22</td><td align="center">int16_t</td><td align="left">height</td><td align="left">m</td></tr><tr><td align="center">24</td><td align="center">int16_t</td><td align="left">ground_pres</td><td align="left">Average barometer reading on ground</td></tr><tr><td align="center">26</td><td align="center">int16_t</td><td align="left">ground_accel</td><td align="left">TM</td></tr><tr><td align="center">28</td><td align="center">int16_t</td><td align="left">accel_plus_g</td><td align="left">TM</td></tr><tr><td align="center">30</td><td align="center">int16_t</td><td align="left">accel_minus_g</td><td align="left">TM</td></tr><tr><td align="center">32</td><td class="auto-generated"> </td><td class="auto-generated"> </td><td class="auto-generated"> </td></tr></tbody></table></div></div><br class="table-break"></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp42829136"></a>2.3. Configuration Data</h3></div></div></div><div class="informaltable"><table border="0"><colgroup><col align="center" class="Offset"><col align="left" class="Description"></colgroup><thead><tr><th align="center">Type</th><th align="left">Description</th></tr></thead><tbody><tr><td align="center">0x04</td><td align="left">Configuration Data</td></tr></tbody></table></div><p>
+ </p><div class="table"><a name="idp50242768"></a><p class="title"><b>Table 2. Sensor Packet Contents</b></p><div class="table-contents"><table summary="Sensor Packet Contents" border="1"><colgroup><col align="center" class="Offset"><col align="center" class="Data Type"><col align="left" class="Name"><col align="left" class="Description"></colgroup><thead><tr><th align="center">Offset</th><th align="center">Data Type</th><th align="center">Name</th><th align="center">Description</th></tr></thead><tbody><tr><td align="center">5</td><td align="center">uint8_t</td><td align="left">state</td><td align="left">Flight state</td></tr><tr><td align="center">6</td><td align="center">int16_t</td><td align="left">accel</td><td align="left">accelerometer (TM only)</td></tr><tr><td align="center">8</td><td align="center">int16_t</td><td align="left">pres</td><td align="left">pressure sensor</td></tr><tr><td align="center">10</td><td align="center">int16_t</td><td align="left">temp</td><td align="left">temperature sensor</td></tr><tr><td align="center">12</td><td align="center">int16_t</td><td align="left">v_batt</td><td align="left">battery voltage</td></tr><tr><td align="center">14</td><td align="center">int16_t</td><td align="left">sense_d</td><td align="left">drogue continuity sense (TM/Tm)</td></tr><tr><td align="center">16</td><td align="center">int16_t</td><td align="left">sense_m</td><td align="left">main continuity sense (TM/Tm)</td></tr><tr><td align="center">18</td><td align="center">int16_t</td><td align="left">acceleration</td><td align="left">m/s² * 16</td></tr><tr><td align="center">20</td><td align="center">int16_t</td><td align="left">speed</td><td align="left">m/s * 16</td></tr><tr><td align="center">22</td><td align="center">int16_t</td><td align="left">height</td><td align="left">m</td></tr><tr><td align="center">24</td><td align="center">int16_t</td><td align="left">ground_pres</td><td align="left">Average barometer reading on ground</td></tr><tr><td align="center">26</td><td align="center">int16_t</td><td align="left">ground_accel</td><td align="left">TM</td></tr><tr><td align="center">28</td><td align="center">int16_t</td><td align="left">accel_plus_g</td><td align="left">TM</td></tr><tr><td align="center">30</td><td align="center">int16_t</td><td align="left">accel_minus_g</td><td align="left">TM</td></tr><tr><td align="center">32</td><td class="auto-generated"> </td><td class="auto-generated"> </td><td class="auto-generated"> </td></tr></tbody></table></div></div><br class="table-break"></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp55625232"></a>2.3. Configuration Data</h3></div></div></div><div class="informaltable"><table border="0"><colgroup><col align="center" class="Offset"><col align="left" class="Description"></colgroup><thead><tr><th align="center">Type</th><th align="left">Description</th></tr></thead><tbody><tr><td align="center">0x04</td><td align="left">Configuration Data</td></tr></tbody></table></div><p>
This provides a description of the software installed on the
flight computer as well as any user-specified configuration data.
</p><p>
Configuration data packets are transmitted once per second
during all phases of the flight
- </p><div class="table"><a name="idp42838288"></a><p class="title"><b>Table 3. Sensor Packet Contents</b></p><div class="table-contents"><table summary="Sensor Packet Contents" border="1"><colgroup><col align="center" class="Offset"><col align="center" class="Data Type"><col align="left" class="Name"><col align="left" class="Description"></colgroup><thead><tr><th align="center">Offset</th><th align="center">Data Type</th><th align="center">Name</th><th align="center">Description</th></tr></thead><tbody><tr><td align="center">5</td><td align="center">uint8_t</td><td align="left">type</td><td align="left">Device type</td></tr><tr><td align="center">6</td><td align="center">uint16_t</td><td align="left">flight</td><td align="left">Flight number</td></tr><tr><td align="center">8</td><td align="center">uint8_t</td><td align="left">config_major</td><td align="left">Config major version</td></tr><tr><td align="center">9</td><td align="center">uint8_t</td><td align="left">config_minor</td><td align="left">Config minor version</td></tr><tr><td align="center">10</td><td align="center">uint16_t</td><td align="left">apogee_delay</td><td align="left">Apogee deploy delay in seconds</td></tr><tr><td align="center">12</td><td align="center">uint16_t</td><td align="left">main_deploy</td><td align="left">Main deploy alt in meters</td></tr><tr><td align="center">14</td><td align="center">uint16_t</td><td align="left">flight_log_max</td><td align="left">Maximum flight log size (kB)</td></tr><tr><td align="center">16</td><td align="center">char</td><td align="left">callsign[8]</td><td align="left">Radio operator identifier</td></tr><tr><td align="center">24</td><td align="center">char</td><td align="left">version[8]</td><td align="left">Software version identifier</td></tr><tr><td align="center">32</td><td class="auto-generated"> </td><td class="auto-generated"> </td><td class="auto-generated"> </td></tr></tbody></table></div></div><br class="table-break"></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp42864656"></a>2.4. GPS Location</h3></div></div></div><div class="informaltable"><table border="0"><colgroup><col align="center" class="Offset"><col align="left" class="Description"></colgroup><thead><tr><th align="center">Type</th><th align="left">Description</th></tr></thead><tbody><tr><td align="center">0x05</td><td align="left">GPS Location</td></tr></tbody></table></div><p>
+ </p><div class="table"><a name="idp55634272"></a><p class="title"><b>Table 3. Sensor Packet Contents</b></p><div class="table-contents"><table summary="Sensor Packet Contents" border="1"><colgroup><col align="center" class="Offset"><col align="center" class="Data Type"><col align="left" class="Name"><col align="left" class="Description"></colgroup><thead><tr><th align="center">Offset</th><th align="center">Data Type</th><th align="center">Name</th><th align="center">Description</th></tr></thead><tbody><tr><td align="center">5</td><td align="center">uint8_t</td><td align="left">type</td><td align="left">Device type</td></tr><tr><td align="center">6</td><td align="center">uint16_t</td><td align="left">flight</td><td align="left">Flight number</td></tr><tr><td align="center">8</td><td align="center">uint8_t</td><td align="left">config_major</td><td align="left">Config major version</td></tr><tr><td align="center">9</td><td align="center">uint8_t</td><td align="left">config_minor</td><td align="left">Config minor version</td></tr><tr><td align="center">10</td><td align="center">uint16_t</td><td align="left">apogee_delay</td><td align="left">Apogee deploy delay in seconds</td></tr><tr><td align="center">12</td><td align="center">uint16_t</td><td align="left">main_deploy</td><td align="left">Main deploy alt in meters</td></tr><tr><td align="center">14</td><td align="center">uint16_t</td><td align="left">flight_log_max</td><td align="left">Maximum flight log size (kB)</td></tr><tr><td align="center">16</td><td align="center">char</td><td align="left">callsign[8]</td><td align="left">Radio operator identifier</td></tr><tr><td align="center">24</td><td align="center">char</td><td align="left">version[8]</td><td align="left">Software version identifier</td></tr><tr><td align="center">32</td><td class="auto-generated"> </td><td class="auto-generated"> </td><td class="auto-generated"> </td></tr></tbody></table></div></div><br class="table-break"></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp55660688"></a>2.4. GPS Location</h3></div></div></div><div class="informaltable"><table border="0"><colgroup><col align="center" class="Offset"><col align="left" class="Description"></colgroup><thead><tr><th align="center">Type</th><th align="left">Description</th></tr></thead><tbody><tr><td align="center">0x05</td><td align="left">GPS Location</td></tr></tbody></table></div><p>
This packet provides all of the information available from the
Venus SkyTraq GPS receiver&#8212;position, time, speed and precision
estimates.
</p><p>
GPS Location packets are transmitted once per second during
all phases of the flight
- </p><div class="table"><a name="idp40127408"></a><p class="title"><b>Table 4. GPS Location Packet Contents</b></p><div class="table-contents"><table summary="GPS Location Packet Contents" border="1"><colgroup><col align="center" class="Offset"><col align="center" class="Data Type"><col align="left" class="Name"><col align="left" class="Description"></colgroup><thead><tr><th align="center">Offset</th><th align="center">Data Type</th><th align="center">Name</th><th align="center">Description</th></tr></thead><tbody><tr><td align="center">5</td><td align="center">uint8_t</td><td align="left">flags</td><td align="left">See GPS Flags table below</td></tr><tr><td align="center">6</td><td align="center">int16_t</td><td align="left">altitude</td><td align="left">m</td></tr><tr><td align="center">8</td><td align="center">int32_t</td><td align="left">latitude</td><td align="left">degrees * 10<sup>7</sup></td></tr><tr><td align="center">12</td><td align="center">int32_t</td><td align="left">longitude</td><td align="left">degrees * 10<sup>7</sup></td></tr><tr><td align="center">16</td><td align="center">uint8_t</td><td align="left">year</td><td class="auto-generated"> </td></tr><tr><td align="center">17</td><td align="center">uint8_t</td><td align="left">month</td><td class="auto-generated"> </td></tr><tr><td align="center">18</td><td align="center">uint8_t</td><td align="left">day</td><td class="auto-generated"> </td></tr><tr><td align="center">19</td><td align="center">uint8_t</td><td align="left">hour</td><td class="auto-generated"> </td></tr><tr><td align="center">20</td><td align="center">uint8_t</td><td align="left">minute</td><td class="auto-generated"> </td></tr><tr><td align="center">21</td><td align="center">uint8_t</td><td align="left">second</td><td class="auto-generated"> </td></tr><tr><td align="center">22</td><td align="center">uint8_t</td><td align="left">pdop</td><td align="left">* 5</td></tr><tr><td align="center">23</td><td align="center">uint8_t</td><td align="left">hdop</td><td align="left">* 5</td></tr><tr><td align="center">24</td><td align="center">uint8_t</td><td align="left">vdop</td><td align="left">* 5</td></tr><tr><td align="center">25</td><td align="center">uint8_t</td><td align="left">mode</td><td align="left">See GPS Mode table below</td></tr><tr><td align="center">26</td><td align="center">uint16_t</td><td align="left">ground_speed</td><td align="left">cm/s</td></tr><tr><td align="center">28</td><td align="center">int16_t</td><td align="left">climb_rate</td><td align="left">cm/s</td></tr><tr><td align="center">30</td><td align="center">uint8_t</td><td align="left">course</td><td align="left">/ 2</td></tr><tr><td align="center">31</td><td align="center">uint8_t</td><td align="left">unused[1]</td><td class="auto-generated"> </td></tr><tr><td align="center">32</td><td class="auto-generated"> </td><td class="auto-generated"> </td><td class="auto-generated"> </td></tr></tbody></table></div></div><br class="table-break"><p>
+ </p><div class="table"><a name="idp55670352"></a><p class="title"><b>Table 4. GPS Location Packet Contents</b></p><div class="table-contents"><table summary="GPS Location Packet Contents" border="1"><colgroup><col align="center" class="Offset"><col align="center" class="Data Type"><col align="left" class="Name"><col align="left" class="Description"></colgroup><thead><tr><th align="center">Offset</th><th align="center">Data Type</th><th align="center">Name</th><th align="center">Description</th></tr></thead><tbody><tr><td align="center">5</td><td align="center">uint8_t</td><td align="left">flags</td><td align="left">See GPS Flags table below</td></tr><tr><td align="center">6</td><td align="center">int16_t</td><td align="left">altitude</td><td align="left">m</td></tr><tr><td align="center">8</td><td align="center">int32_t</td><td align="left">latitude</td><td align="left">degrees * 10<sup>7</sup></td></tr><tr><td align="center">12</td><td align="center">int32_t</td><td align="left">longitude</td><td align="left">degrees * 10<sup>7</sup></td></tr><tr><td align="center">16</td><td align="center">uint8_t</td><td align="left">year</td><td class="auto-generated"> </td></tr><tr><td align="center">17</td><td align="center">uint8_t</td><td align="left">month</td><td class="auto-generated"> </td></tr><tr><td align="center">18</td><td align="center">uint8_t</td><td align="left">day</td><td class="auto-generated"> </td></tr><tr><td align="center">19</td><td align="center">uint8_t</td><td align="left">hour</td><td class="auto-generated"> </td></tr><tr><td align="center">20</td><td align="center">uint8_t</td><td align="left">minute</td><td class="auto-generated"> </td></tr><tr><td align="center">21</td><td align="center">uint8_t</td><td align="left">second</td><td class="auto-generated"> </td></tr><tr><td align="center">22</td><td align="center">uint8_t</td><td align="left">pdop</td><td align="left">* 5</td></tr><tr><td align="center">23</td><td align="center">uint8_t</td><td align="left">hdop</td><td align="left">* 5</td></tr><tr><td align="center">24</td><td align="center">uint8_t</td><td align="left">vdop</td><td align="left">* 5</td></tr><tr><td align="center">25</td><td align="center">uint8_t</td><td align="left">mode</td><td align="left">See GPS Mode table below</td></tr><tr><td align="center">26</td><td align="center">uint16_t</td><td align="left">ground_speed</td><td align="left">cm/s</td></tr><tr><td align="center">28</td><td align="center">int16_t</td><td align="left">climb_rate</td><td align="left">cm/s</td></tr><tr><td align="center">30</td><td align="center">uint8_t</td><td align="left">course</td><td align="left">/ 2</td></tr><tr><td align="center">31</td><td align="center">uint8_t</td><td align="left">unused[1]</td><td class="auto-generated"> </td></tr><tr><td align="center">32</td><td class="auto-generated"> </td><td class="auto-generated"> </td><td class="auto-generated"> </td></tr></tbody></table></div></div><br class="table-break"><p>
Packed into a one byte field are status flags and the count of
satellites used to compute the position fix. Note that this
number may be lower than the number of satellites being
tracked; the receiver will not use information from satellites
with weak signals or which are close enough to the horizon to
have significantly degraded position accuracy.
- </p><div class="table"><a name="idp42904704"></a><p class="title"><b>Table 5. GPS Flags</b></p><div class="table-contents"><table summary="GPS Flags" border="1"><colgroup><col align="center" class="bits"><col align="left" class="name"><col align="left" class="description"></colgroup><thead><tr><th align="center">Bits</th><th align="center">Name</th><th align="center">Description</th></tr></thead><tbody><tr><td align="center">0-3</td><td align="left">nsats</td><td align="left">Number of satellites in solution</td></tr><tr><td align="center">4</td><td align="left">valid</td><td align="left">GPS solution is valid</td></tr><tr><td align="center">5</td><td align="left">running</td><td align="left">GPS receiver is operational</td></tr><tr><td align="center">6</td><td align="left">date_valid</td><td align="left">Reported date is valid</td></tr><tr><td align="center">7</td><td align="left">course_valid</td><td align="left">ground speed, course and climb rates are valid</td></tr></tbody></table></div></div><br class="table-break"><p>
+ </p><div class="table"><a name="idp55710640"></a><p class="title"><b>Table 5. GPS Flags</b></p><div class="table-contents"><table summary="GPS Flags" border="1"><colgroup><col align="center" class="bits"><col align="left" class="name"><col align="left" class="description"></colgroup><thead><tr><th align="center">Bits</th><th align="center">Name</th><th align="center">Description</th></tr></thead><tbody><tr><td align="center">0-3</td><td align="left">nsats</td><td align="left">Number of satellites in solution</td></tr><tr><td align="center">4</td><td align="left">valid</td><td align="left">GPS solution is valid</td></tr><tr><td align="center">5</td><td align="left">running</td><td align="left">GPS receiver is operational</td></tr><tr><td align="center">6</td><td align="left">date_valid</td><td align="left">Reported date is valid</td></tr><tr><td align="center">7</td><td align="left">course_valid</td><td align="left">ground speed, course and climb rates are valid</td></tr></tbody></table></div></div><br class="table-break"><p>
Here are all of the valid GPS operational modes. Altus Metrum
products will only ever report 'N' (not valid), 'A'
(Autonomous) modes or 'E' (Estimated). The remaining modes
are either testing modes or require additional data.
- </p><div class="table"><a name="idp42921088"></a><p class="title"><b>Table 6. GPS Mode</b></p><div class="table-contents"><table summary="GPS Mode" border="1"><colgroup><col align="center" class="value"><col align="center" class="name"><col align="left" class="description"></colgroup><thead><tr><th align="center">Mode</th><th align="center">Name</th><th align="center">Decsription</th></tr></thead><tbody><tr><td align="center">N</td><td align="center">Not Valid</td><td align="left">All data are invalid</td></tr><tr><td align="center">A</td><td align="center">Autonomous mode</td><td align="left">Data are derived from satellite data</td></tr><tr><td align="center">D</td><td align="center">Differential Mode</td><td align="left">
+ </p><div class="table"><a name="idp55727856"></a><p class="title"><b>Table 6. GPS Mode</b></p><div class="table-contents"><table summary="GPS Mode" border="1"><colgroup><col align="center" class="value"><col align="center" class="name"><col align="left" class="description"></colgroup><thead><tr><th align="center">Mode</th><th align="center">Name</th><th align="center">Decsription</th></tr></thead><tbody><tr><td align="center">N</td><td align="center">Not Valid</td><td align="left">All data are invalid</td></tr><tr><td align="center">A</td><td align="center">Autonomous mode</td><td align="left">Data are derived from satellite data</td></tr><tr><td align="center">D</td><td align="center">Differential Mode</td><td align="left">
Data are augmented with differential data from a
known ground station. The SkyTraq unit in TeleMetrum
does not support this mode
</td></tr><tr><td align="center">E</td><td align="center">Estimated</td><td align="left">
Data are estimated using dead reckoning from the
last known data
- </td></tr><tr><td align="center">M</td><td align="center">Manual</td><td align="left">Data were entered manually</td></tr><tr><td align="center">S</td><td align="center">Simulated</td><td align="left">GPS receiver testing mode</td></tr></tbody></table></div></div><br class="table-break"></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp42938656"></a>2.5. GPS Satellite Data</h3></div></div></div><div class="informaltable"><table border="0"><colgroup><col align="center" class="Offset"><col align="left" class="Description"></colgroup><thead><tr><th align="center">Type</th><th align="left">Description</th></tr></thead><tbody><tr><td align="center">0x06</td><td align="left">GPS Satellite Data</td></tr></tbody></table></div><p>
+ </td></tr><tr><td align="center">M</td><td align="center">Manual</td><td align="left">Data were entered manually</td></tr><tr><td align="center">S</td><td align="center">Simulated</td><td align="left">GPS receiver testing mode</td></tr></tbody></table></div></div><br class="table-break"></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp52445616"></a>2.5. GPS Satellite Data</h3></div></div></div><div class="informaltable"><table border="0"><colgroup><col align="center" class="Offset"><col align="left" class="Description"></colgroup><thead><tr><th align="center">Type</th><th align="left">Description</th></tr></thead><tbody><tr><td align="center">0x06</td><td align="left">GPS Satellite Data</td></tr></tbody></table></div><p>
This packet provides space vehicle identifiers and signal
quality information in the form of a C/N1 number for up to 12
satellites. The order of the svids is not specified.
</p><p>
GPS Satellite data are transmitted once per second during all
phases of the flight.
- </p><div class="table"><a name="idp42947840"></a><p class="title"><b>Table 7. GPS Satellite Data Contents</b></p><div class="table-contents"><table summary="GPS Satellite Data Contents" border="1"><colgroup><col align="right" class="Offset"><col align="center" class="Data Type"><col align="left" class="Name"><col align="left" class="Description"></colgroup><thead><tr><th align="center">Offset</th><th align="center">Data Type</th><th align="center">Name</th><th align="center">Description</th></tr></thead><tbody><tr><td align="right">5</td><td align="center">uint8_t</td><td align="left">channels</td><td align="left">Number of reported satellite information</td></tr><tr><td align="right">6</td><td align="center">sat_info_t</td><td align="left">sats[12]</td><td align="left">See Per-Satellite data table below</td></tr><tr><td align="right">30</td><td align="center">uint8_t</td><td align="left">unused[2]</td><td class="auto-generated"> </td></tr><tr><td align="right">32</td><td class="auto-generated"> </td><td class="auto-generated"> </td><td class="auto-generated"> </td></tr></tbody></table></div></div><br class="table-break"><div class="table"><a name="idp42963120"></a><p class="title"><b>Table 8. GPS Per-Satellite data (sat_info_t)</b></p><div class="table-contents"><table summary="GPS Per-Satellite data (sat_info_t)" border="1"><colgroup><col align="right" class="Offset"><col align="center" class="Data Type"><col align="left" class="Name"><col align="left" class="Description"></colgroup><thead><tr><th align="center">Offset</th><th align="center">Data Type</th><th align="center">Name</th><th align="center">Description</th></tr></thead><tbody><tr><td align="right">0</td><td align="center">uint8_t</td><td align="left">svid</td><td align="left">Space Vehicle Identifier</td></tr><tr><td align="right">1</td><td align="center">uint8_t</td><td align="left">c_n_1</td><td align="left">C/N1 signal quality indicator</td></tr><tr><td align="right">2</td><td class="auto-generated"> </td><td class="auto-generated"> </td><td class="auto-generated"> </td></tr></tbody></table></div></div><br class="table-break"></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp42977376"></a>3. Data Transmission</h2></div></div></div><p>
+ </p><div class="table"><a name="idp55742336"></a><p class="title"><b>Table 7. GPS Satellite Data Contents</b></p><div class="table-contents"><table summary="GPS Satellite Data Contents" border="1"><colgroup><col align="right" class="Offset"><col align="center" class="Data Type"><col align="left" class="Name"><col align="left" class="Description"></colgroup><thead><tr><th align="center">Offset</th><th align="center">Data Type</th><th align="center">Name</th><th align="center">Description</th></tr></thead><tbody><tr><td align="right">5</td><td align="center">uint8_t</td><td align="left">channels</td><td align="left">Number of reported satellite information</td></tr><tr><td align="right">6</td><td align="center">sat_info_t</td><td align="left">sats[12]</td><td align="left">See Per-Satellite data table below</td></tr><tr><td align="right">30</td><td align="center">uint8_t</td><td align="left">unused[2]</td><td class="auto-generated"> </td></tr><tr><td align="right">32</td><td class="auto-generated"> </td><td class="auto-generated"> </td><td class="auto-generated"> </td></tr></tbody></table></div></div><br class="table-break"><div class="table"><a name="idp55757616"></a><p class="title"><b>Table 8. GPS Per-Satellite data (sat_info_t)</b></p><div class="table-contents"><table summary="GPS Per-Satellite data (sat_info_t)" border="1"><colgroup><col align="right" class="Offset"><col align="center" class="Data Type"><col align="left" class="Name"><col align="left" class="Description"></colgroup><thead><tr><th align="center">Offset</th><th align="center">Data Type</th><th align="center">Name</th><th align="center">Description</th></tr></thead><tbody><tr><td align="right">0</td><td align="center">uint8_t</td><td align="left">svid</td><td align="left">Space Vehicle Identifier</td></tr><tr><td align="right">1</td><td align="center">uint8_t</td><td align="left">c_n_1</td><td align="left">C/N1 signal quality indicator</td></tr><tr><td align="right">2</td><td class="auto-generated"> </td><td class="auto-generated"> </td><td class="auto-generated"> </td></tr></tbody></table></div></div><br class="table-break"></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp55771872"></a>3. Data Transmission</h2></div></div></div><p>
Altus Metrum devices use the Texas Instruments CC1111
microcontroller which includes an integrated sub-GHz digital
transceiver. This transceiver is used to both transmit and
receive the telemetry packets. This section discusses what
modulation scheme is used and how this device is configured.
- </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp42978752"></a>3.1. Modulation Scheme</h3></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp55773248"></a>3.1. Modulation Scheme</h3></div></div></div><p>
Texas Instruments provides a tool for computing modulation
parameters given a desired modulation format and basic bit
rate. For AltOS, the basic bit rate was specified as 38 kBaud,
resulting in the following signal parmeters:
- </p><div class="table"><a name="idp42980032"></a><p class="title"><b>Table 9. Modulation Scheme</b></p><div class="table-contents"><table summary="Modulation Scheme" border="1"><colgroup><col align="center" class="parameter"><col align="center" class="value"><col align="center" class="description"></colgroup><thead><tr><th align="center">Parameter</th><th align="center">Value</th><th align="center">Description</th></tr></thead><tbody><tr><td align="center">Modulation</td><td align="center">GFSK</td><td align="center">Gaussian Frequency Shift Keying</td></tr><tr><td align="center">Deviation</td><td align="center">20.507812 kHz</td><td align="center">Frequency modulation</td></tr><tr><td align="center">Data rate</td><td align="center">38.360596 kBaud</td><td align="center">Raw bit rate</td></tr><tr><td align="center">RX Filter Bandwidth</td><td align="center">93.75 kHz</td><td align="center">Receiver Band pass filter bandwidth</td></tr><tr><td align="center">IF Frequency</td><td align="center">140.62 kHz</td><td align="center">Receiver intermediate frequency</td></tr></tbody></table></div></div><br class="table-break"></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp42995184"></a>3.2. Error Correction</h3></div></div></div><p>
+ </p><div class="table"><a name="idp55774528"></a><p class="title"><b>Table 9. Modulation Scheme</b></p><div class="table-contents"><table summary="Modulation Scheme" border="1"><colgroup><col align="center" class="parameter"><col align="center" class="value"><col align="center" class="description"></colgroup><thead><tr><th align="center">Parameter</th><th align="center">Value</th><th align="center">Description</th></tr></thead><tbody><tr><td align="center">Modulation</td><td align="center">GFSK</td><td align="center">Gaussian Frequency Shift Keying</td></tr><tr><td align="center">Deviation</td><td align="center">20.507812 kHz</td><td align="center">Frequency modulation</td></tr><tr><td align="center">Data rate</td><td align="center">38.360596 kBaud</td><td align="center">Raw bit rate</td></tr><tr><td align="center">RX Filter Bandwidth</td><td align="center">93.75 kHz</td><td align="center">Receiver Band pass filter bandwidth</td></tr><tr><td align="center">IF Frequency</td><td align="center">140.62 kHz</td><td align="center">Receiver intermediate frequency</td></tr></tbody></table></div></div><br class="table-break"></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp55789680"></a>3.2. Error Correction</h3></div></div></div><p>
The cc1111 provides forward error correction in hardware,
which AltOS uses to improve reception of weak signals. The
overall effect of this is to halve the available bandwidth for
data from 38 kBaud to 19 kBaud.
- </p><div class="table"><a name="idp42996448"></a><p class="title"><b>Table 10. Error Correction</b></p><div class="table-contents"><table summary="Error Correction" border="1"><colgroup><col align="center" class="parameter"><col align="center" class="value"><col align="center" class="description"></colgroup><thead><tr><th align="center">Parameter</th><th align="center">Value</th><th align="center">Description</th></tr></thead><tbody><tr><td align="center">Error Correction</td><td align="center">Convolutional coding</td><td align="center">1/2 rate, constraint length m=4</td></tr><tr><td align="center">Interleaving</td><td align="center">4 x 4</td><td align="center">Reduce effect of noise burst</td></tr><tr><td align="center">Data Whitening</td><td align="center">XOR with 9-bit PNR</td><td align="center">Rotate right with bit 8 = bit 0 xor bit 5, initial
- value 111111111</td></tr></tbody></table></div></div><br class="table-break"></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp43008656"></a>4. TeleDongle packet format</h2></div></div></div><p>
+ </p><div class="table"><a name="idp55790944"></a><p class="title"><b>Table 10. Error Correction</b></p><div class="table-contents"><table summary="Error Correction" border="1"><colgroup><col align="center" class="parameter"><col align="center" class="value"><col align="center" class="description"></colgroup><thead><tr><th align="center">Parameter</th><th align="center">Value</th><th align="center">Description</th></tr></thead><tbody><tr><td align="center">Error Correction</td><td align="center">Convolutional coding</td><td align="center">1/2 rate, constraint length m=4</td></tr><tr><td align="center">Interleaving</td><td align="center">4 x 4</td><td align="center">Reduce effect of noise burst</td></tr><tr><td align="center">Data Whitening</td><td align="center">XOR with 9-bit PNR</td><td align="center">Rotate right with bit 8 = bit 0 xor bit 5, initial
+ value 111111111</td></tr></tbody></table></div></div><br class="table-break"></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp55803152"></a>4. TeleDongle packet format</h2></div></div></div><p>
TeleDongle does not do any interpretation of the packet data,
instead it is configured to receive packets of a specified
length (32 bytes in this case). For each received packet,
@@ -106,9 +106,9 @@
the packet data, two bytes added by the cc1111 radio receiver
hardware and finally a checksum so that the host software can
validate that the line was transmitted without any errors.
- </p><div class="table"><a name="idp43011360"></a><p class="title"><b>Table 11. Packet Format</b></p><div class="table-contents"><table summary="Packet Format" border="1"><colgroup><col align="center" class="offset"><col align="center" class="name"><col align="center" class="value"><col align="center" class="description"></colgroup><thead><tr><th align="center">Offset</th><th align="center">Name</th><th align="center">Example</th><th align="center">Description</th></tr></thead><tbody><tr><td align="center">0</td><td align="center">length</td><td align="center">22</td><td align="center">Total length of data bytes in the line. Note that
+ </p><div class="table"><a name="idp55805856"></a><p class="title"><b>Table 11. Packet Format</b></p><div class="table-contents"><table summary="Packet Format" border="1"><colgroup><col align="center" class="offset"><col align="center" class="name"><col align="center" class="value"><col align="center" class="description"></colgroup><thead><tr><th align="center">Offset</th><th align="center">Name</th><th align="center">Example</th><th align="center">Description</th></tr></thead><tbody><tr><td align="center">0</td><td align="center">length</td><td align="center">22</td><td align="center">Total length of data bytes in the line. Note that
this includes the added RSSI and status bytes</td></tr><tr><td align="center">1 ·· length-3</td><td align="center">packet</td><td align="center">4f ·· 00</td><td align="center">Bytes of actual packet data</td></tr><tr><td align="center">length-2</td><td align="center">rssi</td><td align="center">3f</td><td align="center">Received signal strength. dBm = rssi / 2 - 74</td></tr><tr><td align="center">length-1</td><td align="center">lqi</td><td align="center">a9</td><td align="center">Link Quality Indicator and CRC status. Bit 7
- is set when the CRC is correct</td></tr><tr><td align="center">length</td><td align="center">checksum</td><td align="center">88</td><td align="center">(0x5a + sum(bytes 1 ·· length-1)) % 256</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="idp43030240"></a>5. History and Motivation</h2></div></div></div><p>
+ is set when the CRC is correct</td></tr><tr><td align="center">length</td><td align="center">checksum</td><td align="center">88</td><td align="center">(0x5a + sum(bytes 1 ·· length-1)) % 256</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="idp55824736"></a>5. History and Motivation</h2></div></div></div><p>
The original AltoOS telemetry mechanism encoded everything
available piece of information on the TeleMetrum hardware into a
single unified packet. Initially, the packets contained very
diff --git a/AltOS/doc/telemetry.pdf b/AltOS/doc/telemetry.pdf
index 9d95bc2..b7e0e7d 100644
--- a/AltOS/doc/telemetry.pdf
+++ b/AltOS/doc/telemetry.pdf
Binary files differ
generated by cgit v1.2.3 (git 2.39.1) at 2025-10-16 05:31:42 +0000