-<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="idm624
4192"></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="idp48059856"></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="idm624
1120"></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="idp47957712"></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="#idp47884288">1. Overview</a></span></dt><dt><span class="chapter"><a href="#idp48916512">2. AltOS Porting Layer</a></span></dt><dd><dl><dt><span class="section"><a href="#idp48918016">1. Low-level CPU operations</a></span></dt><dd><dl><dt><span class="section"><a href="#idp48919248">1.1. ao_arch_block_interrupts/ao_arch_release_interrupts</a></span></dt><dt><span class="section"><a href="#idp48921296">1.2. ao_arch_save_regs, ao_arch_save_stack,
- ao_arch_restore_stack</a></span></dt><dt><span class="section"><a href="#idp4
9830960">1.3. ao_arch_wait_interupt</a></span></dt></dl></dd><dt><span class="section"><a href="#idp49833504">2. GPIO operations</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49834672">2.1. GPIO setup</a></span></dt><dt><span class="section"><a href="#idp49843888">2.2. Reading and writing GPIO pins</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#idp47890928">3. Programming the 8051 with SDCC</a></span></dt><dd><dl><dt><span class="section"><a href="#idp47893024">1. 8051 memory spaces</a></span></dt><dd><dl><dt><span class="section"><a href="#idp47894960">1.1. __data</a></span></dt><dt><span class="section"><a href="#idp47897136">1.2. __idata</a></span></dt><dt><span class="section"><a href="#idp47898576">1.3. __xdata</a></span></dt><dt><span class="section"><a href="#idp47899984">1.4. __pdata</a></span></dt><dt><span class="section"><a href="#idp47901488">1.5. __code</a></span></dt><dt><span class="section"><a href="#idp47902928">1.6. __bit</a></span></dt><dt><span class="section"><a href="#idp47904432">1.7. __sfr, __sfr16, __sfr32, __sbit</a></span></dt></dl></dd><dt><span class="section"><a href="#idp47905968">2. Function calls on the 8051</a></span></dt><dd><dl><dt><span class="section"><a href="#idp47907440">2.1. __reentrant functions</a></span></dt><dt><span class="section"><a href="#idp47909632">2.2. Non __reentrant functions</a></span></dt><dt><span class="section"><a href="#idp47911776">2.3. __interrupt functions</a></span></dt><dt><span class="section"><a href="#idp47913344">2.4. __critical functions and statements</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#idp47915408">4. Task functions</a></span></dt><dd><dl><dt><span class="section"><a href="#idp47916464">1. ao_add_task</a></span></dt><dt><span class="section"><a href="#idp47918720">2. ao_exit</a></span></dt><dt><span class="section"><a href="#idp53787440">3. ao_sleep</a></span></dt><dt><span class="section"><a href="#idp53791040">4. ao_wakeup</a></span></dt><dt><span class="section"><a href="#idp53794032">5. ao_alarm</a></span></dt><dt><span class="section"><a href="#idp53797312">6. ao_start_scheduler</a></span></dt><dt><span class="section"><a href="#idp53799280">7. ao_clock_init</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp53801248">5. Timer Functions</a></span></dt><dd><dl><dt><span class="section"><a href="#idp53802752">1. ao_time</a></span></dt><dt><span class="section"><a href="#idp53804736">2. ao_delay</a></span></dt><dt><span class="section"><a href="#idp53806576">3. ao_timer_set_adc_interval</a></span></dt><dt><span class="section"><a href="#idp53808624">4. ao_timer_init</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp53810816">6. AltOS Mutexes</a></span></dt><dd><dl><dt><span class="section"><a href="#idp53812688">1. ao_mutex_get</a></span></dt><dt><span class="section"><a href="#idp53814528">2. ao_mutex_put</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp53816496">7. DMA engine</a></span></dt><dd><dl><dt><span class="section"><a href="#idp53819936">1. CC1111 DMA Engine</a></span></dt><dd><dl><dt><span class="section"><a href="#idp53820608">1.1. ao_dma_alloc</a></span></dt><dt><span class="section"><a href="#idp53822784">1.2. ao_dma_set_transfer</a></span></dt><dt><span class="section"><a href="#idp53825056">1.3. ao_dma_start</a></span></dt><dt><span class="section"><a href="#idp53827072">1.4. ao_dma_trigger</a></span></dt><dt><span class="section"><a href="#idp53828912">1.5. ao_dma_abort</a></span></dt></dl></dd><dt><span class="section"><a href="#idp53831056">2. STM32L DMA Engine</a></span></dt><dd><dl><dt><span class="section"><a href="#idp53831728">2.1. ao_dma_alloc</a></span></dt><dt><span class="section"><a href="#idp53833568">2.2. ao_dma_set_transfer</a></span></dt><dt><span class="section"><a href="#idp53835824">2.3. ao_dma_set_isr</a></span></dt><dt><span class="section"><a href="#idp53837904">2.4. ao_dma_start</a></span></dt><dt><span class="section"><a href="#idp53840208">2.5. ao_dma_done_transfer</a></span></dt><dt><span class="section"><a href="#idp53842192">2.6. ao_dma_abort</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#idp53844464">8. Stdio interface</a></span></dt><dd><dl><dt><span class="section"><a href="#idp53845968">1. putchar</a></span></dt><dt><span class="section"><a href="#idp53847856">2. getchar</a></span></dt><dt><span class="section"><a href="#idp53849952">3. flush</a></span></dt><dt><span class="section"><a href="#idp53851984">4. ao_add_stdio</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp53856016">9. Command line interface</a></span></dt><dd><dl><dt><span class="section"><a href="#idp53857424">1. ao_cmd_register</a></span></dt><dt><span class="section"><a href="#idp53866064">2. ao_cmd_lex</a></span></dt><dt><span class="section"><a href="#idp53868144">3. ao_cmd_put16</a></span></dt><dt><span class="section"><a href="#idp53869984">4. ao_cmd_put8</a></span></dt><dt><span class="section"><a href="#idp53871872">5. ao_cmd_white</a></span></dt><dt><span class="section"><a href="#idp53873936">6. ao_cmd_hex</a></span></dt><dt><span class="section"><a href="#idp53875984">7. ao_cmd_decimal</a></span></dt><dt><span class="section"><a href="#idp53878080">8. ao_match_word</a></span></dt><dt><span class="section"><a href="#idp53880160">9. ao_cmd_init</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp53882384">10. USB target device</a></span></dt><dd><dl><dt><span class="section"><a href="#idp53884608">1. ao_usb_flush</a></span></dt><dt><span class="section"><a href="#idp53886752">2. ao_usb_putchar</a></span></dt><dt><span class="section"><a href="#idp53888928">3. ao_usb_pollchar</a></span></dt><dt><span class="section"><a href="#idp53891072">4. ao_usb_getchar</a></span></dt><dt><span class="section"><a href="#idp53893088">5. ao_usb_disable</a></span></dt><dt><span class="section"><a href="#idp53895920">6. ao_usb_enable</a></span></dt><dt><span class="section"><a href="#idp53898032">7. ao_usb_init</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp53900256">11. Serial peripherals</a></span></dt><dd><dl><dt><span class="section"><a href="#idp53902272">1. ao_serial_getchar</a></span></dt><dt><span class="section"><a href="#idp53904304">2. ao_serial_putchar</a></span></dt><dt><span class="section"><a href="#idp53906272">3. ao_serial_drain</a></span></dt><dt><span class="section"><a href="#idp53908272">4. ao_serial_set_speed</a></span></dt><dt><span class="section"><a href="#idp53910304">5. ao_serial_init</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp53912496">12. CC1111 Radio peripheral</a></span></dt><dd><dl><dt><span class="section"><a href="#idp53913168">1. Radio Introduction</a></span></dt><dt><span class="section"><a href="#idp53920288">2. ao_radio_set_telemetry</a></span></dt><dt><span class="section"><a href="#idp53922448">3. ao_radio_set_packet</a></span></dt><dt><span class="section"><a href="#idp53924608">4. ao_radio_set_rdf</a></span></dt><dt><span class="section"><a href="#idp53926848">5. ao_radio_idle</a></span></dt><dt><span class="section"><a href="#idp53928896">6. ao_radio_get</a></span></dt><dt><span class="section"><a href="#idp53930928">7. ao_radio_put</a></span></dt><dt><span class="section"><a href="#idp53932864">8. ao_radio_abort</a></span></dt><dt><span class="section"><a href="#idp53934928">9. Radio Telemetry</a></span></dt><dd><dl><dt><span class="section"><a href="#idp53936224">9.1. ao_radio_send</a></span></dt><dt><span class="section"><a href="#idp53938448">9.2. ao_radio_recv</a></span></dt></dl></dd><dt><span class="section"><a href="#idp53940912">10. Radio Direction Finding</a></span></dt><dd><dl><dt><span class="section"><a href="#idp53942064">10.1. ao_radio_rdf</a></span></dt></dl></dd><dt><span class="section"><a href="#idp53944208">11. Radio Packet Mode</a></span></dt><dd><dl><dt><span class="section"><a href="#idp53945520">11.1. ao_packet_putchar</a></span></dt><dt><span class="section"><a href="#idp53947696">11.2. ao_packet_pollchar</a></span></dt><dt><span class="section"><a href="#idp53949776">11.3. ao_packet_slave_start</a></span></dt><dt><span class="section"><a href="#idp53951728">11.4. ao_packet_slave_stop</a></span></dt><dt><span class="section"><a href="#idp53953648">11.5. ao_packet_slave_init</a></span></dt><dt><span class="section"><a href="#idp53955680">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="idp47884288"></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="#idp47882736">1. Overview</a></span></dt><dt><span class="chapter"><a href="#idp48914816">2. AltOS Porting Layer</a></span></dt><dd><dl><dt><span class="section"><a href="#idp48916320">1. Low-level CPU operations</a></span></dt><dd><dl><dt><span class="section"><a href="#idp48917552">1.1. ao_arch_block_interrupts/ao_arch_release_interrupts</a></span></dt><dt><span class="section"><a href="#idp48919600">1.2. ao_arch_save_regs, ao_arch_save_stack,
+ ao_arch_restore_stack</a></span></dt><dt><span class="section"><a href="#idp4
8052384">1.3. ao_arch_wait_interupt</a></span></dt></dl></dd><dt><span class="section"><a href="#idp48054928">2. GPIO operations</a></span></dt><dd><dl><dt><span class="section"><a href="#idp48056096">2.1. GPIO setup</a></span></dt><dt><span class="section"><a href="#idp48065040">2.2. Reading and writing GPIO pins</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#idp47889248">3. Programming the 8051 with SDCC</a></span></dt><dd><dl><dt><span class="section"><a href="#idp47891344">1. 8051 memory spaces</a></span></dt><dd><dl><dt><span class="section"><a href="#idp47893280">1.1. __data</a></span></dt><dt><span class="section"><a href="#idp47895456">1.2. __idata</a></span></dt><dt><span class="section"><a href="#idp47896896">1.3. __xdata</a></span></dt><dt><span class="section"><a href="#idp47898304">1.4. __pdata</a></span></dt><dt><span class="section"><a href="#idp47899808">1.5. __code</a></span></dt><dt><span class="section"><a href="#idp47901248">1.6. __bit</a></span></dt><dt><span class="section"><a href="#idp47902752">1.7. __sfr, __sfr16, __sfr32, __sbit</a></span></dt></dl></dd><dt><span class="section"><a href="#idp47904288">2. Function calls on the 8051</a></span></dt><dd><dl><dt><span class="section"><a href="#idp47905760">2.1. __reentrant functions</a></span></dt><dt><span class="section"><a href="#idp47907952">2.2. Non __reentrant functions</a></span></dt><dt><span class="section"><a href="#idp47910096">2.3. __interrupt functions</a></span></dt><dt><span class="section"><a href="#idp47911664">2.4. __critical functions and statements</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#idp47913728">4. Task functions</a></span></dt><dd><dl><dt><span class="section"><a href="#idp47914784">1. ao_add_task</a></span></dt><dt><span class="section"><a href="#idp47917040">2. ao_exit</a></span></dt><dt><span class="section"><a href="#idp54330432">3. ao_sleep</a></span></dt><dt><span class="section"><a href="#idp54334032">4. ao_wakeup</a></span></dt><dt><span class="section"><a href="#idp54337024">5. ao_alarm</a></span></dt><dt><span class="section"><a href="#idp54340304">6. ao_start_scheduler</a></span></dt><dt><span class="section"><a href="#idp54342272">7. ao_clock_init</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp54344240">5. Timer Functions</a></span></dt><dd><dl><dt><span class="section"><a href="#idp54345744">1. ao_time</a></span></dt><dt><span class="section"><a href="#idp54347728">2. ao_delay</a></span></dt><dt><span class="section"><a href="#idp54349568">3. ao_timer_set_adc_interval</a></span></dt><dt><span class="section"><a href="#idp54351616">4. ao_timer_init</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp54353808">6. AltOS Mutexes</a></span></dt><dd><dl><dt><span class="section"><a href="#idp54355680">1. ao_mutex_get</a></span></dt><dt><span class="section"><a href="#idp54357520">2. ao_mutex_put</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp54359488">7. DMA engine</a></span></dt><dd><dl><dt><span class="section"><a href="#idp54362928">1. CC1111 DMA Engine</a></span></dt><dd><dl><dt><span class="section"><a href="#idp54363600">1.1. ao_dma_alloc</a></span></dt><dt><span class="section"><a href="#idp54365776">1.2. ao_dma_set_transfer</a></span></dt><dt><span class="section"><a href="#idp54368048">1.3. ao_dma_start</a></span></dt><dt><span class="section"><a href="#idp54370064">1.4. ao_dma_trigger</a></span></dt><dt><span class="section"><a href="#idp54371904">1.5. ao_dma_abort</a></span></dt></dl></dd><dt><span class="section"><a href="#idp54374048">2. STM32L DMA Engine</a></span></dt><dd><dl><dt><span class="section"><a href="#idp54374720">2.1. ao_dma_alloc</a></span></dt><dt><span class="section"><a href="#idp54376560">2.2. ao_dma_set_transfer</a></span></dt><dt><span class="section"><a href="#idp54378816">2.3. ao_dma_set_isr</a></span></dt><dt><span class="section"><a href="#idp54380896">2.4. ao_dma_start</a></span></dt><dt><span class="section"><a href="#idp54383200">2.5. ao_dma_done_transfer</a></span></dt><dt><span class="section"><a href="#idp54385184">2.6. ao_dma_abort</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#idp54387456">8. Stdio interface</a></span></dt><dd><dl><dt><span class="section"><a href="#idp54388960">1. putchar</a></span></dt><dt><span class="section"><a href="#idp54390848">2. getchar</a></span></dt><dt><span class="section"><a href="#idp54392944">3. flush</a></span></dt><dt><span class="section"><a href="#idp54394976">4. ao_add_stdio</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp54398928">9. Command line interface</a></span></dt><dd><dl><dt><span class="section"><a href="#idp54400336">1. ao_cmd_register</a></span></dt><dt><span class="section"><a href="#idp54408896">2. ao_cmd_lex</a></span></dt><dt><span class="section"><a href="#idp54410976">3. ao_cmd_put16</a></span></dt><dt><span class="section"><a href="#idp54412816">4. ao_cmd_put8</a></span></dt><dt><span class="section"><a href="#idp54414704">5. ao_cmd_white</a></span></dt><dt><span class="section"><a href="#idp54416768">6. ao_cmd_hex</a></span></dt><dt><span class="section"><a href="#idp54418816">7. ao_cmd_decimal</a></span></dt><dt><span class="section"><a href="#idp54420912">8. ao_match_word</a></span></dt><dt><span class="section"><a href="#idp54422992">9. ao_cmd_init</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp54425216">10. USB target device</a></span></dt><dd><dl><dt><span class="section"><a href="#idp54427440">1. ao_usb_flush</a></span></dt><dt><span class="section"><a href="#idp54429584">2. ao_usb_putchar</a></span></dt><dt><span class="section"><a href="#idp54431760">3. ao_usb_pollchar</a></span></dt><dt><span class="section"><a href="#idp54433904">4. ao_usb_getchar</a></span></dt><dt><span class="section"><a href="#idp54435920">5. ao_usb_disable</a></span></dt><dt><span class="section"><a href="#idp54438752">6. ao_usb_enable</a></span></dt><dt><span class="section"><a href="#idp54440864">7. ao_usb_init</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp54443088">11. Serial peripherals</a></span></dt><dd><dl><dt><span class="section"><a href="#idp54445104">1. ao_serial_getchar</a></span></dt><dt><span class="section"><a href="#idp54447136">2. ao_serial_putchar</a></span></dt><dt><span class="section"><a href="#idp54449104">3. ao_serial_drain</a></span></dt><dt><span class="section"><a href="#idp54451104">4. ao_serial_set_speed</a></span></dt><dt><span class="section"><a href="#idp54453136">5. ao_serial_init</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp54455328">12. CC1111 Radio peripheral</a></span></dt><dd><dl><dt><span class="section"><a href="#idp54456000">1. Radio Introduction</a></span></dt><dt><span class="section"><a href="#idp54463120">2. ao_radio_set_telemetry</a></span></dt><dt><span class="section"><a href="#idp54465280">3. ao_radio_set_packet</a></span></dt><dt><span class="section"><a href="#idp54467440">4. ao_radio_set_rdf</a></span></dt><dt><span class="section"><a href="#idp54469680">5. ao_radio_idle</a></span></dt><dt><span class="section"><a href="#idp54471728">6. ao_radio_get</a></span></dt><dt><span class="section"><a href="#idp54473760">7. ao_radio_put</a></span></dt><dt><span class="section"><a href="#idp54475696">8. ao_radio_abort</a></span></dt><dt><span class="section"><a href="#idp54477760">9. Radio Telemetry</a></span></dt><dd><dl><dt><span class="section"><a href="#idp54479056">9.1. ao_radio_send</a></span></dt><dt><span class="section"><a href="#idp54481280">9.2. ao_radio_recv</a></span></dt></dl></dd><dt><span class="section"><a href="#idp54483744">10. Radio Direction Finding</a></span></dt><dd><dl><dt><span class="section"><a href="#idp54484896">10.1. ao_radio_rdf</a></span></dt></dl></dd><dt><span class="section"><a href="#idp54487040">11. Radio Packet Mode</a></span></dt><dd><dl><dt><span class="section"><a href="#idp54488352">11.1. ao_packet_putchar</a></span></dt><dt><span class="section"><a href="#idp54490528">11.2. ao_packet_pollchar</a></span></dt><dt><span class="section"><a href="#idp54492608">11.3. ao_packet_slave_start</a></span></dt><dt><span class="section"><a href="#idp54494560">11.4. ao_packet_slave_stop</a></span></dt><dt><span class="section"><a href="#idp54496480">11.5. ao_packet_slave_init</a></span></dt><dt><span class="section"><a href="#idp54498512">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="idp47882736"></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
</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="idp48916512"></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="#idp48918016">1. Low-level CPU operations</a></span></dt><dd><dl><dt><span class="section"><a href="#idp48919248">1.1. ao_arch_block_interrupts/ao_arch_release_interrupts</a></span></dt><dt><span class="section"><a href="#idp48921296">1.2. ao_arch_save_regs, ao_arch_save_stack,
- ao_arch_restore_stack</a></span></dt><dt><span class="section"><a href="#idp4
9830960">1.3. ao_arch_wait_interupt</a></span></dt></dl></dd><dt><span class="section"><a href="#idp49833504">2. GPIO operations</a></span></dt><dd><dl><dt><span class="section"><a href="#idp49834672">2.1. GPIO setup</a></span></dt><dt><span class="section"><a href="#idp49843888">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="idp48914816"></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="#idp48916320">1. Low-level CPU operations</a></span></dt><dd><dl><dt><span class="section"><a href="#idp48917552">1.1. ao_arch_block_interrupts/ao_arch_release_interrupts</a></span></dt><dt><span class="section"><a href="#idp48919600">1.2. ao_arch_save_regs, ao_arch_save_stack,
+ ao_arch_restore_stack</a></span></dt><dt><span class="section"><a href="#idp4
8052384">1.3. ao_arch_wait_interupt</a></span></dt></dl></dd><dt><span class="section"><a href="#idp48054928">2. GPIO operations</a></span></dt><dd><dl><dt><span class="section"><a href="#idp48056096">2.1. GPIO setup</a></span></dt><dt><span class="section"><a href="#idp48065040">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
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="idp4891
8016"></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="idp4891
6320"></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="idp4891
9248"></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="idp4891
7552"></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);
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="idp48921296"></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="idp48919600"></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);
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="idp4
9830960"></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="idp4
8052384"></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
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="idp4
9833504"></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="idp4
8054928"></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="idp4
9834672"></a>2.1. GPIO setup</h3></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp4
8056096"></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
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="idp4892
3152"></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="idp4892
1456"></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="idp4
9838448"></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="idp4
8059744"></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
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="idp4
9843888"></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="idp4
8065040"></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="idp4
9844960"></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="idp4
8066112"></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="idp4
7888592"></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="idp4
8067952"></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="idp478
90928"></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="#idp47893024">1. 8051 memory spaces</a></span></dt><dd><dl><dt><span class="section"><a href="#idp47894960">1.1. __data</a></span></dt><dt><span class="section"><a href="#idp47897136">1.2. __idata</a></span></dt><dt><span class="section"><a href="#idp47898576">1.3. __xdata</a></span></dt><dt><span class="section"><a href="#idp47899984">1.4. __pdata</a></span></dt><dt><span class="section"><a href="#idp47901488">1.5. __code</a></span></dt><dt><span class="section"><a href="#idp47902928">1.6. __bit</a></span></dt><dt><span class="section"><a href="#idp47904432">1.7. __sfr, __sfr16, __sfr32, __sbit</a></span></dt></dl></dd><dt><span class="section"><a href="#idp47905968">2. Function calls on the 8051</a></span></dt><dd><dl><dt><span class="section"><a href="#idp47907440">2.1. __reentrant functions</a></span></dt><dt><span class="section"><a href="#idp47909632">2.2. Non __reentrant functions</a></span></dt><dt><span class="section"><a href="#idp47911776">2.3. __interrupt functions</a></span></dt><dt><span class="section"><a href="#idp47913344">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="idp478
89248"></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="#idp47891344">1. 8051 memory spaces</a></span></dt><dd><dl><dt><span class="section"><a href="#idp47893280">1.1. __data</a></span></dt><dt><span class="section"><a href="#idp47895456">1.2. __idata</a></span></dt><dt><span class="section"><a href="#idp47896896">1.3. __xdata</a></span></dt><dt><span class="section"><a href="#idp47898304">1.4. __pdata</a></span></dt><dt><span class="section"><a href="#idp47899808">1.5. __code</a></span></dt><dt><span class="section"><a href="#idp47901248">1.6. __bit</a></span></dt><dt><span class="section"><a href="#idp47902752">1.7. __sfr, __sfr16, __sfr32, __sbit</a></span></dt></dl></dd><dt><span class="section"><a href="#idp47904288">2. Function calls on the 8051</a></span></dt><dd><dl><dt><span class="section"><a href="#idp47905760">2.1. __reentrant functions</a></span></dt><dt><span class="section"><a href="#idp47907952">2.2. Non __reentrant functions</a></span></dt><dt><span class="section"><a href="#idp47910096">2.3. __interrupt functions</a></span></dt><dt><span class="section"><a href="#idp47911664">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
</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="idp4789
3024"></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="idp4789
1344"></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—they all live in a single unified 64kB address
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="idp4789
4960"></a>1.1. __data</h3></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp4789
3280"></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
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="idp4789
7136"></a>1.2. __idata</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp4789
5456"></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="idp4789
8576"></a>1.3. __xdata</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp4789
6896"></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="idp4789
9984"></a>1.4. __pdata</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp4789
8304"></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="idp47
901488"></a>1.5. __code</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp47
899808"></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="idp4790
2928"></a>1.6. __bit</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp4790
1248"></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="idp4790
4432"></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="idp4790
2752"></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, it's 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="idp4790
5968"></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="idp4790
4288"></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
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="idp4790
7440"></a>2.1. __reentrant functions</h3></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp4790
5760"></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
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="idp4790
9632"></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="idp4790
7952"></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
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="idp4791
1776"></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="idp4791
0096"></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="idp4791
3344"></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="idp4791
1664"></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
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="idp4791
5408"></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="#idp47916464">1. ao_add_task</a></span></dt><dt><span class="section"><a href="#idp47918720">2. ao_exit</a></span></dt><dt><span class="section"><a href="#idp53787440">3. ao_sleep</a></span></dt><dt><span class="section"><a href="#idp53791040">4. ao_wakeup</a></span></dt><dt><span class="section"><a href="#idp53794032">5. ao_alarm</a></span></dt><dt><span class="section"><a href="#idp53797312">6. ao_start_scheduler</a></span></dt><dt><span class="section"><a href="#idp53799280">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="idp4791
3728"></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="#idp47914784">1. ao_add_task</a></span></dt><dt><span class="section"><a href="#idp47917040">2. ao_exit</a></span></dt><dt><span class="section"><a href="#idp54330432">3. ao_sleep</a></span></dt><dt><span class="section"><a href="#idp54334032">4. ao_wakeup</a></span></dt><dt><span class="section"><a href="#idp54337024">5. ao_alarm</a></span></dt><dt><span class="section"><a href="#idp54340304">6. ao_start_scheduler</a></span></dt><dt><span class="section"><a href="#idp54342272">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="idp4791
6464"></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="idp4791
4784"></a>1. ao_add_task</h2></div></div></div><pre class="programlisting">
void
ao_add_task(__xdata struct ao_task * task,
void (*start)(void),
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="idp4791
8720"></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="idp4791
7040"></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="idp5
3787440"></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="idp5
4330432"></a>3. ao_sleep</h2></div></div></div><pre class="programlisting">
void
ao_sleep(__xdata void *wchan)
</pre><p>
ao_sleep(&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="idp5
3791040"></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="idp5
4334032"></a>4. ao_wakeup</h2></div></div></div><pre class="programlisting">
void
ao_wakeup(__xdata void *wchan)
</pre><p>
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="idp5
3794032"></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="idp5
4337024"></a>5. ao_alarm</h2></div></div></div><pre class="programlisting">
void
ao_alarm(uint16_t delay);
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="idp5
3797312"></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="idp5
4340304"></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="idp5
3799280"></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="idp5
4342272"></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="idp5
3801248"></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="#idp53802752">1. ao_time</a></span></dt><dt><span class="section"><a href="#idp53804736">2. ao_delay</a></span></dt><dt><span class="section"><a href="#idp53806576">3. ao_timer_set_adc_interval</a></span></dt><dt><span class="section"><a href="#idp53808624">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="idp5
4344240"></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="#idp54345744">1. ao_time</a></span></dt><dt><span class="section"><a href="#idp54347728">2. ao_delay</a></span></dt><dt><span class="section"><a href="#idp54349568">3. ao_timer_set_adc_interval</a></span></dt><dt><span class="section"><a href="#idp54351616">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
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="idp5
3802752"></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="idp5
4345744"></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="idp5
3804736"></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="idp5
4347728"></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="idp5
3806576"></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="idp5
4349568"></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="idp5
3808624"></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="idp5
4351616"></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="idp5
3810816"></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="#idp53812688">1. ao_mutex_get</a></span></dt><dt><span class="section"><a href="#idp53814528">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="idp5
4353808"></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="#idp54355680">1. ao_mutex_get</a></span></dt><dt><span class="section"><a href="#idp54357520">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—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="idp5
3812688"></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="idp5
4355680"></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="idp5
3814528"></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="idp5
4357520"></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="idp5
3816496"></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="#idp53819936">1. CC1111 DMA Engine</a></span></dt><dd><dl><dt><span class="section"><a href="#idp53820608">1.1. ao_dma_alloc</a></span></dt><dt><span class="section"><a href="#idp53822784">1.2. ao_dma_set_transfer</a></span></dt><dt><span class="section"><a href="#idp53825056">1.3. ao_dma_start</a></span></dt><dt><span class="section"><a href="#idp53827072">1.4. ao_dma_trigger</a></span></dt><dt><span class="section"><a href="#idp53828912">1.5. ao_dma_abort</a></span></dt></dl></dd><dt><span class="section"><a href="#idp53831056">2. STM32L DMA Engine</a></span></dt><dd><dl><dt><span class="section"><a href="#idp53831728">2.1. ao_dma_alloc</a></span></dt><dt><span class="section"><a href="#idp53833568">2.2. ao_dma_set_transfer</a></span></dt><dt><span class="section"><a href="#idp53835824">2.3. ao_dma_set_isr</a></span></dt><dt><span class="section"><a href="#idp53837904">2.4. ao_dma_start</a></span></dt><dt><span class="section"><a href="#idp53840208">2.5. ao_dma_done_transfer</a></span></dt><dt><span class="section"><a href="#idp53842192">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="idp5
4359488"></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="#idp54362928">1. CC1111 DMA Engine</a></span></dt><dd><dl><dt><span class="section"><a href="#idp54363600">1.1. ao_dma_alloc</a></span></dt><dt><span class="section"><a href="#idp54365776">1.2. ao_dma_set_transfer</a></span></dt><dt><span class="section"><a href="#idp54368048">1.3. ao_dma_start</a></span></dt><dt><span class="section"><a href="#idp54370064">1.4. ao_dma_trigger</a></span></dt><dt><span class="section"><a href="#idp54371904">1.5. ao_dma_abort</a></span></dt></dl></dd><dt><span class="section"><a href="#idp54374048">2. STM32L DMA Engine</a></span></dt><dd><dl><dt><span class="section"><a href="#idp54374720">2.1. ao_dma_alloc</a></span></dt><dt><span class="section"><a href="#idp54376560">2.2. ao_dma_set_transfer</a></span></dt><dt><span class="section"><a href="#idp54378816">2.3. ao_dma_set_isr</a></span></dt><dt><span class="section"><a href="#idp54380896">2.4. ao_dma_start</a></span></dt><dt><span class="section"><a href="#idp54383200">2.5. ao_dma_done_transfer</a></span></dt><dt><span class="section"><a href="#idp54385184">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
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="idp5
3819936"></a>1. CC1111 DMA Engine</h2></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp53820608"></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="idp5
4362928"></a>1. CC1111 DMA Engine</h2></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp54363600"></a>1.1. ao_dma_alloc</h3></div></div></div><pre class="programlisting">
uint8_t
ao_dma_alloc(__xdata uint8_t *done)
</pre><p>
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="idp5
3822784"></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="idp5
4365776"></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,
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="idp5
3825056"></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="idp5
4368048"></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="idp5
3827072"></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="idp5
4370064"></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="idp5
3828912"></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="idp5
4371904"></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 transation, 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="idp5
3831056"></a>2. STM32L DMA Engine</h2></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp53831728"></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="idp5
4374048"></a>2. STM32L DMA Engine</h2></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp54374720"></a>2.1. ao_dma_alloc</h3></div></div></div><pre class="programlisting">
uint8_t ao_dma_done[];
void
</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="idp5
3833568"></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="idp5
4376560"></a>2.2. ao_dma_set_transfer</h3></div></div></div><pre class="programlisting">
void
ao_dma_set_transfer(uint8_t id,
void *peripheral,
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="idp5
3835824"></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="idp5
4378816"></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>
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="idp5
3837904"></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="idp5
4380896"></a>2.4. ao_dma_start</h3></div></div></div><pre class="programlisting">
void
ao_dma_start(uint8_t id);
</pre><p>
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="idp5
3840208"></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="idp5
4383200"></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="idp5
3842192"></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="idp5
4385184"></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 transation, 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="idp5
3844464"></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="#idp53845968">1. putchar</a></span></dt><dt><span class="section"><a href="#idp53847856">2. getchar</a></span></dt><dt><span class="section"><a href="#idp53849952">3. flush</a></span></dt><dt><span class="section"><a href="#idp53851984">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="idp5
4387456"></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="#idp54388960">1. putchar</a></span></dt><dt><span class="section"><a href="#idp54390848">2. getchar</a></span></dt><dt><span class="section"><a href="#idp54392944">3. flush</a></span></dt><dt><span class="section"><a href="#idp54394976">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 localy or
remotely. This is hooked up to the stdio functions by providing
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="idp5
3845968"></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="idp5
4388960"></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="idp5
3847856"></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="idp5
4390848"></a>2. getchar</h2></div></div></div><pre class="programlisting">
char
getchar(void)
</pre><p>
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="idp5
3849952"></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="idp5
4392944"></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.
- xo </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp5
3851984"></a>4. ao_add_stdio</h2></div></div></div><pre class="programlisting">
+ xo </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp5
4394976"></a>4. ao_add_stdio</h2></div></div></div><pre class="programlisting">
void
ao_add_stdio(char (*pollchar)(void),
void (*putchar)(char),
'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="idp5
3856016"></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="#idp53857424">1. ao_cmd_register</a></span></dt><dt><span class="section"><a href="#idp53866064">2. ao_cmd_lex</a></span></dt><dt><span class="section"><a href="#idp53868144">3. ao_cmd_put16</a></span></dt><dt><span class="section"><a href="#idp53869984">4. ao_cmd_put8</a></span></dt><dt><span class="section"><a href="#idp53871872">5. ao_cmd_white</a></span></dt><dt><span class="section"><a href="#idp53873936">6. ao_cmd_hex</a></span></dt><dt><span class="section"><a href="#idp53875984">7. ao_cmd_decimal</a></span></dt><dt><span class="section"><a href="#idp53878080">8. ao_match_word</a></span></dt><dt><span class="section"><a href="#idp53880160">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="idp5
4398928"></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="#idp54400336">1. ao_cmd_register</a></span></dt><dt><span class="section"><a href="#idp54408896">2. ao_cmd_lex</a></span></dt><dt><span class="section"><a href="#idp54410976">3. ao_cmd_put16</a></span></dt><dt><span class="section"><a href="#idp54412816">4. ao_cmd_put8</a></span></dt><dt><span class="section"><a href="#idp54414704">5. ao_cmd_white</a></span></dt><dt><span class="section"><a href="#idp54416768">6. ao_cmd_hex</a></span></dt><dt><span class="section"><a href="#idp54418816">7. ao_cmd_decimal</a></span></dt><dt><span class="section"><a href="#idp54420912">8. ao_match_word</a></span></dt><dt><span class="section"><a href="#idp54422992">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="idp5
3857424"></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="idp5
4400336"></a>1. ao_cmd_register</h2></div></div></div><pre class="programlisting">
void
ao_cmd_register(__code struct ao_cmds *cmds)
</pre><p>
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="idp5
3866064"></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="idp5
4408896"></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="idp5
3868144"></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="idp5
4410976"></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="idp5
3869984"></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="idp5
4412816"></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="idp5
3871872"></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="idp5
4414704"></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="idp5
3873936"></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="idp5
4416768"></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="idp5
3875984"></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="idp5
4418816"></a>7. ao_cmd_decimal</h2></div></div></div><pre class="programlisting">
void
ao_cmd_decimal(void)
</pre><p>
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="idp5
3878080"></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="idp5
4420912"></a>8. ao_match_word</h2></div></div></div><pre class="programlisting">
uint8_t
ao_match_word(__code char *word)
</pre><p>
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="idp5
3880160"></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="idp5
4422992"></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="idp5
3882384"></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="#idp53884608">1. ao_usb_flush</a></span></dt><dt><span class="section"><a href="#idp53886752">2. ao_usb_putchar</a></span></dt><dt><span class="section"><a href="#idp53888928">3. ao_usb_pollchar</a></span></dt><dt><span class="section"><a href="#idp53891072">4. ao_usb_getchar</a></span></dt><dt><span class="section"><a href="#idp53893088">5. ao_usb_disable</a></span></dt><dt><span class="section"><a href="#idp53895920">6. ao_usb_enable</a></span></dt><dt><span class="section"><a href="#idp53898032">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="idp5
4425216"></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="#idp54427440">1. ao_usb_flush</a></span></dt><dt><span class="section"><a href="#idp54429584">2. ao_usb_putchar</a></span></dt><dt><span class="section"><a href="#idp54431760">3. ao_usb_pollchar</a></span></dt><dt><span class="section"><a href="#idp54433904">4. ao_usb_getchar</a></span></dt><dt><span class="section"><a href="#idp54435920">5. ao_usb_disable</a></span></dt><dt><span class="section"><a href="#idp54438752">6. ao_usb_enable</a></span></dt><dt><span class="section"><a href="#idp54440864">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
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="idp5
3884608"></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="idp5
4427440"></a>1. ao_usb_flush</h2></div></div></div><pre class="programlisting">
void
ao_usb_flush(void);
</pre><p>
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="idp5
3886752"></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="idp5
4429584"></a>2. ao_usb_putchar</h2></div></div></div><pre class="programlisting">
void
ao_usb_putchar(char c);
</pre><p>
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="idp5
3888928"></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="idp5
4431760"></a>3. ao_usb_pollchar</h2></div></div></div><pre class="programlisting">
char
ao_usb_pollchar(void);
</pre><p>
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="idp5
3891072"></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="idp5
4433904"></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="idp5
3893088"></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="idp5
4435920"></a>5. ao_usb_disable</h2></div></div></div><pre class="programlisting">
void
ao_usb_disable(void);
</pre><p>
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="idp5
3895920"></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="idp5
4438752"></a>6. ao_usb_enable</h2></div></div></div><pre class="programlisting">
void
ao_usb_enable(void);
</pre><p>
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="idp5
3898032"></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="idp5
4440864"></a>7. ao_usb_init</h2></div></div></div><pre class="programlisting">
void
ao_usb_init(void);
</pre><p>
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="idp5
3900256"></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="#idp53902272">1. ao_serial_getchar</a></span></dt><dt><span class="section"><a href="#idp53904304">2. ao_serial_putchar</a></span></dt><dt><span class="section"><a href="#idp53906272">3. ao_serial_drain</a></span></dt><dt><span class="section"><a href="#idp53908272">4. ao_serial_set_speed</a></span></dt><dt><span class="section"><a href="#idp53910304">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="idp5
4443088"></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="#idp54445104">1. ao_serial_getchar</a></span></dt><dt><span class="section"><a href="#idp54447136">2. ao_serial_putchar</a></span></dt><dt><span class="section"><a href="#idp54449104">3. ao_serial_drain</a></span></dt><dt><span class="section"><a href="#idp54451104">4. ao_serial_set_speed</a></span></dt><dt><span class="section"><a href="#idp54453136">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
</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="idp5
3902272"></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="idp5
4445104"></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="idp5
3904304"></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="idp5
4447136"></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="idp5
3906272"></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="idp5
4449104"></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="idp5
3908272"></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="idp5
4451104"></a>4. ao_serial_set_speed</h2></div></div></div><pre class="programlisting">
void
ao_serial_set_speed(uint8_t speed);
</pre><p>
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="idp5
3910304"></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="idp5
4453136"></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="idp5
3912496"></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="#idp53913168">1. Radio Introduction</a></span></dt><dt><span class="section"><a href="#idp53920288">2. ao_radio_set_telemetry</a></span></dt><dt><span class="section"><a href="#idp53922448">3. ao_radio_set_packet</a></span></dt><dt><span class="section"><a href="#idp53924608">4. ao_radio_set_rdf</a></span></dt><dt><span class="section"><a href="#idp53926848">5. ao_radio_idle</a></span></dt><dt><span class="section"><a href="#idp53928896">6. ao_radio_get</a></span></dt><dt><span class="section"><a href="#idp53930928">7. ao_radio_put</a></span></dt><dt><span class="section"><a href="#idp53932864">8. ao_radio_abort</a></span></dt><dt><span class="section"><a href="#idp53934928">9. Radio Telemetry</a></span></dt><dd><dl><dt><span class="section"><a href="#idp53936224">9.1. ao_radio_send</a></span></dt><dt><span class="section"><a href="#idp53938448">9.2. ao_radio_recv</a></span></dt></dl></dd><dt><span class="section"><a href="#idp53940912">10. Radio Direction Finding</a></span></dt><dd><dl><dt><span class="section"><a href="#idp53942064">10.1. ao_radio_rdf</a></span></dt></dl></dd><dt><span class="section"><a href="#idp53944208">11. Radio Packet Mode</a></span></dt><dd><dl><dt><span class="section"><a href="#idp53945520">11.1. ao_packet_putchar</a></span></dt><dt><span class="section"><a href="#idp53947696">11.2. ao_packet_pollchar</a></span></dt><dt><span class="section"><a href="#idp53949776">11.3. ao_packet_slave_start</a></span></dt><dt><span class="section"><a href="#idp53951728">11.4. ao_packet_slave_stop</a></span></dt><dt><span class="section"><a href="#idp53953648">11.5. ao_packet_slave_init</a></span></dt><dt><span class="section"><a href="#idp53955680">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="idp53913168"></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="idp5
4455328"></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="#idp54456000">1. Radio Introduction</a></span></dt><dt><span class="section"><a href="#idp54463120">2. ao_radio_set_telemetry</a></span></dt><dt><span class="section"><a href="#idp54465280">3. ao_radio_set_packet</a></span></dt><dt><span class="section"><a href="#idp54467440">4. ao_radio_set_rdf</a></span></dt><dt><span class="section"><a href="#idp54469680">5. ao_radio_idle</a></span></dt><dt><span class="section"><a href="#idp54471728">6. ao_radio_get</a></span></dt><dt><span class="section"><a href="#idp54473760">7. ao_radio_put</a></span></dt><dt><span class="section"><a href="#idp54475696">8. ao_radio_abort</a></span></dt><dt><span class="section"><a href="#idp54477760">9. Radio Telemetry</a></span></dt><dd><dl><dt><span class="section"><a href="#idp54479056">9.1. ao_radio_send</a></span></dt><dt><span class="section"><a href="#idp54481280">9.2. ao_radio_recv</a></span></dt></dl></dd><dt><span class="section"><a href="#idp54483744">10. Radio Direction Finding</a></span></dt><dd><dl><dt><span class="section"><a href="#idp54484896">10.1. ao_radio_rdf</a></span></dt></dl></dd><dt><span class="section"><a href="#idp54487040">11. Radio Packet Mode</a></span></dt><dd><dl><dt><span class="section"><a href="#idp54488352">11.1. ao_packet_putchar</a></span></dt><dt><span class="section"><a href="#idp54490528">11.2. ao_packet_pollchar</a></span></dt><dt><span class="section"><a href="#idp54492608">11.3. ao_packet_slave_start</a></span></dt><dt><span class="section"><a href="#idp54494560">11.4. ao_packet_slave_stop</a></span></dt><dt><span class="section"><a href="#idp54496480">11.5. ao_packet_slave_init</a></span></dt><dt><span class="section"><a href="#idp54498512">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="idp54456000"></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
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="idp5
3920288"></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="idp5
4463120"></a>2. ao_radio_set_telemetry</h2></div></div></div><pre class="programlisting">
void
ao_radio_set_telemetry(void);
</pre><p>
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="idp5
3922448"></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="idp5
4465280"></a>3. ao_radio_set_packet</h2></div></div></div><pre class="programlisting">
void
ao_radio_set_packet(void);
</pre><p>
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="idp5
3924608"></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="idp5
4467440"></a>4. ao_radio_set_rdf</h2></div></div></div><pre class="programlisting">
void
ao_radio_set_rdf(void);
</pre><p>
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="idp5
3926848"></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="idp5
4469680"></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="idp5
3928896"></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="idp5
4471728"></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="idp5
3930928"></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="idp5
4473760"></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="idp5
3932864"></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="idp5
4475696"></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="idp5
3934928"></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="idp5
4477760"></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="idp5
3936224"></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="idp5
4479056"></a>9.1. ao_radio_send</h3></div></div></div><pre class="programlisting">
void
ao_radio_send(__xdata struct ao_telemetry *telemetry);
</pre><p>
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="idp5
3938448"></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="idp5
4481280"></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>
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="idp5
3940912"></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="idp5
4483744"></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="idp5
3942064"></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="idp5
4484896"></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="idp5
3944208"></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="idp5
4487040"></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="idp5
3945520"></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="idp5
4488352"></a>11.1. ao_packet_putchar</h3></div></div></div><pre class="programlisting">
void
ao_packet_putchar(char c);
</pre><p>
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="idp5
3947696"></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="idp5
4490528"></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="idp5
3949776"></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="idp5
4492608"></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="idp5
3951728"></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="idp5
4494560"></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="idp5
3953648"></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="idp5
4496480"></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="idp5
3955680"></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="idp5
4498512"></a>11.6. ao_packet_master_init</h3></div></div></div><pre class="programlisting">
void
ao_packet_master_init(void);
</pre><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="id
p26428432"></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 © 2013 Bdale Garbee and Keith Packard</p></div><div><div class="legalnotice"><a name="idp53658176"></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="id
m6236096"></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="idp47882560"></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.3</td><td align="left">12 November 2013</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.3.1</td><td align="left">21 January 2014</td></tr><tr><td align="left" colspan="2">
+ Bug fixes for TeleMega and TeleMetrum v2.0 along with a few
+ small UI improvements.
+ </td></tr><tr><td align="left">Revision 1.3</td><td align="left">12 November 2013</td></tr><tr><td align="left" colspan="2">
Updated for software version 1.3. Version 1.3 adds support
for TeleMega, TeleMetrum v2.0, TeleMini v2.0 and EasyMini
and fixes bugs in AltosUI and the AltOS firmware.
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="idp
52772352"></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="idp
48972192"></a>Acknowledgments</h1></div></div></div><p>
Thanks to Bob Finch, W9YA, NAR 12965, TRA 12350 for writing “The
Mere-Mortals Quick Start/Usage Guide to the Altus Metrum Starter
Kit” which formed the basis of the original Getting Started chapter
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="#idp52776880">1. Introduction and Overview</a></span></dt><dt><span class="chapter"><a href="#idp57459264">2. Getting Started</a></span></dt><dt><span class="chapter"><a href="#idp52778544">3. Handling Precautions</a></span></dt><dt><span class="chapter"><a href="#idp52784032">4. Altus Metrum Hardware</a></span></dt><dd><dl><dt><span class="section"><a href="#idp52784704">1. Overview</a></span></dt><dt><span class="section"><a href="#idp58332736">2. TeleMetrum</a></span></dt><dt><span class="section"><a href="#idp58337760">3. TeleMini</a></span></dt><dt><span class="section"><a href="#idp58346160">4. EasyMini</a></span></dt><dt><span class="section"><a href="#idp58350144">5. TeleMega</a></span></dt><dt><span class="section"><a href="#idp58354240">6. Flight Data Recording</a></span></dt><dt><span class="section"><a href="#idp58383072">7. Installation</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp58389808">5. System Operation</a></span></dt><dd><dl><dt><span class="section"><a href="#idp58390448">1. Firmware Modes </a></span></dt><dt><span class="section"><a href="#idp58467152">2. GPS </a></span></dt><dt><span class="section"><a href="#idp58469936">3. Controlling An Altimeter Over The Radio Link</a></span></dt><dt><span class="section"><a href="#idp58481232">4. Ground Testing </a></span></dt><dt><span class="section"><a href="#idp58483984">5. Radio Link </a></span></dt><dt><span class="section"><a href="#idp58488672">6. Configurable Parameters</a></span></dt><dd><dl><dt><span class="section"><a href="#idp58490416">6.1. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp58492464">6.2. Apogee Delay</a></span></dt><dt><span class="section"><a href="#idp58495056">6.3. Main Deployment Altitude</a></span></dt><dt><span class="section"><a href="#idp58496752">6.4. Maximum Flight Log</a></span></dt><dt><span class="section"><a href="#idp58498896">6.5. Ignite Mode</a></span></dt><dt><span class="section"><a href="#idp58501008">6.6. Pad Orientation</a></span></dt><dt><span class="section"><a href="#idp58502704">6.7. Configurable Pyro Channels</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#idp58525184">6. AltosUI</a></span></dt><dd><dl><dt><span class="section"><a href="#idp58528800">1. Monitor Flight</a></span></dt><dd><dl><dt><span class="section"><a href="#idp58541520">1.1. Launch Pad</a></span></dt><dt><span class="section"><a href="#idp58557152">1.2. Ascent</a></span></dt><dt><span class="section"><a href="#idp58562608">1.3. Descent</a></span></dt><dt><span class="section"><a href="#idp58569472">1.4. Landed</a></span></dt><dt><span class="section"><a href="#idp58575904">1.5. Table</a></span></dt><dt><span class="section"><a href="#idp58579488">1.6. Site Map</a></span></dt></dl></dd><dt><span class="section"><a href="#idp58585152">2. Save Flight Data</a></span></dt><dt><span class="section"><a href="#idp58589632">3. Replay Flight</a></span></dt><dt><span class="section"><a href="#idp58591664">4. Graph Data</a></span></dt><dd><dl><dt><span class="section"><a href="#idp58594048">4.1. Flight Graph</a></span></dt><dt><span class="section"><a href="#idp58598496">4.2. Configure Graph</a></span></dt><dt><span class="section"><a href="#idp58602160">4.3. Flight Statistics</a></span></dt><dt><span class="section"><a href="#idp58605680">4.4. Map</a></span></dt></dl></dd><dt><span class="section"><a href="#idp58609536">5. Export Data</a></span></dt><dd><dl><dt><span class="section"><a href="#idp58611648">5.1. Comma Separated Value Format</a></span></dt><dt><span class="section"><a href="#idp58614000">5.2. Keyhole Markup Language (for Google Earth)</a></span></dt></dl></dd><dt><span class="section"><a href="#idp58615488">6. Configure Altimeter</a></span></dt><dd><dl><dt><span class="section"><a href="#idp58627792">6.1. Main Deploy Altitude</a></span></dt><dt><span class="section"><a href="#idp58629360">6.2. Apogee Delay</a></span></dt><dt><span class="section"><a href="#idp58630976">6.3. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp58632480">6.4. RF Calibration</a></span></dt><dt><span class="section"><a href="#idp58634128">6.5. Telemetry/RDF/APRS Enable</a></span></dt><dt><span class="section"><a href="#idp58635424">6.6. APRS Interval</a></span></dt><dt><span class="section"><a href="#idp58636928">6.7. Callsign</a></span></dt><dt><span class="section"><a href="#idp58638240">6.8. Maximum Flight Log Size</a></span></dt><dt><span class="section"><a href="#idp58639680">6.9. Ignite Mode</a></span></dt><dt><span class="section"><a href="#idp58646672">6.10. Pad Orientation</a></span></dt><dt><span class="section"><a href="#idp58651888">6.11. Configure Pyro Channels</a></span></dt></dl></dd><dt><span class="section"><a href="#idp58657696">7. Configure AltosUI</a></span></dt><dd><dl><dt><span class="section"><a href="#idp58661200">7.1. Voice Settings</a></span></dt><dt><span class="section"><a href="#idp58666224">7.2. Log Directory</a></span></dt><dt><span class="section"><a href="#idp58668224">7.3. Callsign</a></span></dt><dt><span class="section"><a href="#idp58670464">7.4. Imperial Units</a></span></dt><dt><span class="section"><a href="#idp58671968">7.5. Font Size</a></span></dt><dt><span class="section"><a href="#idp58673248">7.6. Serial Debug</a></span></dt><dt><span class="section"><a href="#idp58674752">7.7. Manage Frequencies</a></span></dt></dl></dd><dt><span class="section"><a href="#idp58676384">8. Configure Groundstation</a></span></dt><dd><dl><dt><span class="section"><a href="#idp58687504">8.1. Frequency</a></span></dt><dt><span class="section"><a href="#idp58689072">8.2. Radio Calibration</a></span></dt></dl></dd><dt><span class="section"><a href="#idp58690704">9. Flash Image</a></span></dt><dt><span class="section"><a href="#idp58692336">10. Fire Igniter</a></span></dt><dt><span class="section"><a href="#idp58697968">11. Scan Channels</a></span></dt><dt><span class="section"><a href="#idp58701824">12. Load Maps</a></span></dt><dt><span class="section"><a href="#idp58707520">13. Monitor Idle</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp58709616">7. AltosDroid</a></span></dt><dd><dl><dt><span class="section"><a href="#idp58712000">1. Installing AltosDroid</a></span></dt><dt><span class="section"><a href="#idp58713936">2. Connecting to TeleBT</a></span></dt><dt><span class="section"><a href="#idp58715936">3. Configuring AltosDroid</a></span></dt><dt><span class="section"><a href="#idp58717392">4. AltosDroid Flight Monitoring</a></span></dt><dd><dl><dt><span class="section"><a href="#idp58718704">4.1. Pad</a></span></dt></dl></dd><dt><span class="section"><a href="#idp58732256">5. Downloading Flight Logs</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp58733920">8. Using Altus Metrum Products</a></span></dt><dd><dl><dt><span class="section"><a href="#idp58734560">1. Being Legal</a></span></dt><dt><span class="section"><a href="#idp58736464">2. In the Rocket</a></span></dt><dt><span class="section"><a href="#idp58738928">3. On the Ground</a></span></dt><dt><span class="section"><a href="#idp58752240">4. Data Analysis</a></span></dt><dt><span class="section"><a href="#idp58754784">5. Future Plans</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp58759168">9. Altimeter Installation Recommendations</a></span></dt><dd><dl><dt><span class="section"><a href="#idp58760624">1. Mounting the Altimeter</a></span></dt><dt><span class="section"><a href="#idp58766032">2. Dealing with the Antenna</a></span></dt><dt><span class="section"><a href="#idp58771600">3. Preserving GPS Reception</a></span></dt><dt><span class="section"><a href="#idp58776384">4. Radio Frequency Interference</a></span></dt><dt><span class="section"><a href="#idp58783952">5. The Barometric Sensor</a></span></dt><dt><span class="section"><a href="#idp58786752">6. Ground Testing</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp58789920">10. Updating Device Firmware</a></span></dt><dd><dl><dt><span class="section"><a href="#idp58793936">1.
+ </p></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="chapter"><a href="#idp48053984">1. Introduction and Overview</a></span></dt><dt><span class="chapter"><a href="#idp48061744">2. Getting Started</a></span></dt><dt><span class="chapter"><a href="#idp47890336">3. Handling Precautions</a></span></dt><dt><span class="chapter"><a href="#idp47895824">4. Altus Metrum Hardware</a></span></dt><dd><dl><dt><span class="section"><a href="#idp47896496">1. Overview</a></span></dt><dt><span class="section"><a href="#idp53909808">2. TeleMetrum</a></span></dt><dt><span class="section"><a href="#idp53914976">3. TeleMini</a></span></dt><dt><span class="section"><a href="#idp53923600">4. EasyMini</a></span></dt><dt><span class="section"><a href="#idp53927712">5. TeleMega</a></span></dt><dt><span class="section"><a href="#idp53931936">6. Flight Data Recording</a></span></dt><dt><span class="section"><a href="#idp53961856">7. Installation</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp53968624">5. System Operation</a></span></dt><dd><dl><dt><span class="section"><a href="#idp53969296">1. Firmware Modes </a></span></dt><dt><span class="section"><a href="#idp53977296">2. GPS </a></span></dt><dt><span class="section"><a href="#idp53979824">3. Controlling An Altimeter Over The Radio Link</a></span></dt><dt><span class="section"><a href="#idp54060432">4. Ground Testing </a></span></dt><dt><span class="section"><a href="#idp54063184">5. Radio Link </a></span></dt><dt><span class="section"><a href="#idp54067872">6. Configurable Parameters</a></span></dt><dd><dl><dt><span class="section"><a href="#idp54069616">6.1. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp54071664">6.2. Apogee Delay</a></span></dt><dt><span class="section"><a href="#idp54074256">6.3. Main Deployment Altitude</a></span></dt><dt><span class="section"><a href="#idp54075952">6.4. Maximum Flight Log</a></span></dt><dt><span class="section"><a href="#idp54078096">6.5. Ignite Mode</a></span></dt><dt><span class="section"><a href="#idp54080208">6.6. Pad Orientation</a></span></dt><dt><span class="section"><a href="#idp54081904">6.7. Configurable Pyro Channels</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#idp54104384">6. AltosUI</a></span></dt><dd><dl><dt><span class="section"><a href="#idp54108000">1. Monitor Flight</a></span></dt><dd><dl><dt><span class="section"><a href="#idp54120720">1.1. Launch Pad</a></span></dt><dt><span class="section"><a href="#idp54136352">1.2. Ascent</a></span></dt><dt><span class="section"><a href="#idp54141808">1.3. Descent</a></span></dt><dt><span class="section"><a href="#idp54148672">1.4. Landed</a></span></dt><dt><span class="section"><a href="#idp54155520">1.5. Table</a></span></dt><dt><span class="section"><a href="#idp54159104">1.6. Site Map</a></span></dt></dl></dd><dt><span class="section"><a href="#idp54164768">2. Save Flight Data</a></span></dt><dt><span class="section"><a href="#idp54168720">3. Replay Flight</a></span></dt><dt><span class="section"><a href="#idp54170752">4. Graph Data</a></span></dt><dd><dl><dt><span class="section"><a href="#idp54173136">4.1. Flight Graph</a></span></dt><dt><span class="section"><a href="#idp54177584">4.2. Configure Graph</a></span></dt><dt><span class="section"><a href="#idp54181248">4.3. Flight Statistics</a></span></dt><dt><span class="section"><a href="#idp54184768">4.4. Map</a></span></dt></dl></dd><dt><span class="section"><a href="#idp54188624">5. Export Data</a></span></dt><dd><dl><dt><span class="section"><a href="#idp54190192">5.1. Comma Separated Value Format</a></span></dt><dt><span class="section"><a href="#idp54192544">5.2. Keyhole Markup Language (for Google Earth)</a></span></dt></dl></dd><dt><span class="section"><a href="#idp54194032">6. Configure Altimeter</a></span></dt><dd><dl><dt><span class="section"><a href="#idp54206336">6.1. Main Deploy Altitude</a></span></dt><dt><span class="section"><a href="#idp54208304">6.2. Apogee Delay</a></span></dt><dt><span class="section"><a href="#idp54209920">6.3. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp54211424">6.4. RF Calibration</a></span></dt><dt><span class="section"><a href="#idp54213072">6.5. Telemetry/RDF/APRS Enable</a></span></dt><dt><span class="section"><a href="#idp54214368">6.6. APRS Interval</a></span></dt><dt><span class="section"><a href="#idp54215872">6.7. Callsign</a></span></dt><dt><span class="section"><a href="#idp54217184">6.8. Maximum Flight Log Size</a></span></dt><dt><span class="section"><a href="#idp54218624">6.9. Ignite Mode</a></span></dt><dt><span class="section"><a href="#idp54225616">6.10. Pad Orientation</a></span></dt><dt><span class="section"><a href="#idp54230832">6.11. Configure Pyro Channels</a></span></dt></dl></dd><dt><span class="section"><a href="#idp54236640">7. Configure AltosUI</a></span></dt><dd><dl><dt><span class="section"><a href="#idp54240144">7.1. Voice Settings</a></span></dt><dt><span class="section"><a href="#idp54245168">7.2. Log Directory</a></span></dt><dt><span class="section"><a href="#idp54247168">7.3. Callsign</a></span></dt><dt><span class="section"><a href="#idp54249408">7.4. Imperial Units</a></span></dt><dt><span class="section"><a href="#idp54250912">7.5. Font Size</a></span></dt><dt><span class="section"><a href="#idp54252192">7.6. Serial Debug</a></span></dt><dt><span class="section"><a href="#idp54253696">7.7. Manage Frequencies</a></span></dt></dl></dd><dt><span class="section"><a href="#idp54255328">8. Configure Groundstation</a></span></dt><dd><dl><dt><span class="section"><a href="#idp54266448">8.1. Frequency</a></span></dt><dt><span class="section"><a href="#idp54268016">8.2. Radio Calibration</a></span></dt></dl></dd><dt><span class="section"><a href="#idp54269648">9. Flash Image</a></span></dt><dt><span class="section"><a href="#idp54271280">10. Fire Igniter</a></span></dt><dt><span class="section"><a href="#idp54276912">11. Scan Channels</a></span></dt><dt><span class="section"><a href="#idp54280768">12. Load Maps</a></span></dt><dt><span class="section"><a href="#idp54286464">13. Monitor Idle</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp54288560">7. AltosDroid</a></span></dt><dd><dl><dt><span class="section"><a href="#idp54290944">1. Installing AltosDroid</a></span></dt><dt><span class="section"><a href="#idp54292880">2. Connecting to TeleBT</a></span></dt><dt><span class="section"><a href="#idp54294880">3. Configuring AltosDroid</a></span></dt><dt><span class="section"><a href="#idp54296336">4. AltosDroid Flight Monitoring</a></span></dt><dd><dl><dt><span class="section"><a href="#idp54297648">4.1. Pad</a></span></dt></dl></dd><dt><span class="section"><a href="#idp54311200">5. Downloading Flight Logs</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp54312864">8. Using Altus Metrum Products</a></span></dt><dd><dl><dt><span class="section"><a href="#idp54313504">1. Being Legal</a></span></dt><dt><span class="section"><a href="#idp54315408">2. In the Rocket</a></span></dt><dt><span class="section"><a href="#idp54317872">3. On the Ground</a></span></dt><dt><span class="section"><a href="#idp54331184">4. Data Analysis</a></span></dt><dt><span class="section"><a href="#idp54333728">5. Future Plans</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp54338112">9. Altimeter Installation Recommendations</a></span></dt><dd><dl><dt><span class="section"><a href="#idp54339568">1. Mounting the Altimeter</a></span></dt><dt><span class="section"><a href="#idp54344400">2. Dealing with the Antenna</a></span></dt><dt><span class="section"><a href="#idp54349968">3. Preserving GPS Reception</a></span></dt><dt><span class="section"><a href="#idp54354752">4. Radio Frequency Interference</a></span></dt><dt><span class="section"><a href="#idp54362320">5. The Barometric Sensor</a></span></dt><dt><span class="section"><a href="#idp54365120">6. Ground Testing</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp54368288">10. Updating Device Firmware</a></span></dt><dd><dl><dt><span class="section"><a href="#idp54372304">1.
Updating TeleMega, TeleMetrum v2 or EasyMini Firmware
- </a></span></dt><dd><dl><dt><span class="section"><a href="#idp58802752">1.1. Recovering From Self-Flashing Failure</a></span></dt></dl></dd><dt><span class="section"><a href="#idp58811728">2. Pair Programming</a></span></dt><dt><span class="section"><a href="#idp58813168">3. Updating TeleMetrum v1.x Firmware</a></span></dt><dt><span class="section"><a href="#idp58826208">4. Updating TeleMini Firmware</a></span></dt><dt><span class="section"><a href="#idp58839600">5. Updating TeleDongle Firmware</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp58856144">11. Hardware Specifications</a></span></dt><dd><dl><dt><span class="section"><a href="#idp58856784">1.
+ </a></span></dt><dd><dl><dt><span class="section"><a href="#idp54381120">1.1. Recovering From Self-Flashing Failure</a></span></dt></dl></dd><dt><span class="section"><a href="#idp54390096">2. Pair Programming</a></span></dt><dt><span class="section"><a href="#idp54391536">3. Updating TeleMetrum v1.x Firmware</a></span></dt><dt><span class="section"><a href="#idp54404576">4. Updating TeleMini Firmware</a></span></dt><dt><span class="section"><a href="#idp54417968">5. Updating TeleDongle Firmware</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp54434512">11. Hardware Specifications</a></span></dt><dd><dl><dt><span class="section"><a href="#idp54435152">1.
TeleMega Specifications
- </a></span></dt><dt><span class="section"><a href="#idp58868016">2.
+ </a></span></dt><dt><span class="section"><a href="#idp54446496">2.
TeleMetrum v2 Specifications
- </a></span></dt><dt><span class="section"><a href="#idp58878256">3. TeleMetrum v1 Specifications</a></span></dt><dt><span class="section"><a href="#idp58888496">4.
+ </a></span></dt><dt><span class="section"><a href="#idp54457056">3. TeleMetrum v1 Specifications</a></span></dt><dt><span class="section"><a href="#idp54467616">4.
TeleMini v2.0 Specifications
- </a></span></dt><dt><span class="section"><a href="#idp58897328">5.
+ </a></span></dt><dt><span class="section"><a href="#idp54476448">5.
TeleMini v1.0 Specifications
- </a></span></dt><dt><span class="section"><a href="#idp58906128">6.
+ </a></span></dt><dt><span class="section"><a href="#idp54485248">6.
EasyMini Specifications
- </a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp5
8914240">12. FAQ</a></span></dt><dt><span class="appendix"><a href="#idp58923088">A. Notes for Older Software</a></span></dt><dt><span class="appendix"><a href="#idp58946464">B. Drill Templates</a></span></dt><dd><dl><dt><span class="section"><a href="#idp58947632">1. TeleMega template</a></span></dt><dt><span class="section"><a href="#idp58963600">2. TeleMetrum template</a></span></dt><dt><span class="section"><a href="#idp58967264">3. TeleMini v2/EasyMini template</a></span></dt><dt><span class="section"><a href="#idp58970944">4. TeleMini v1 template</a></span></dt></dl></dd><dt><span class="appendix"><a href="#idp58974736">C. Calibration</a></span></dt><dd><dl><dt><span class="section"><a href="#idp58976288">1. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp58980832">2. TeleMetrum and TeleMega Accelerometers</a></span></dt></dl></dd><dt><span class="appendix"><a href="#idp58985936">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="#idp52785760">Altus Metrum Electronics</a></dt><dt>4.2. <a href="#idp56763616">Altus Metrum Boards</a></dt><dt>4.3. <a href="#idp58355648">Data Storage on Altus Metrum altimeters</a></dt><dt>5.1. <a href="#idp58391728">AltOS Modes</a></dt><dt>5.2. <a href="#idp58440960">Pad/Idle Indications</a></dt></dl></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp52776880"></a>Chapter 1. Introduction and Overview</h1></div></div></div><p>
+ </a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp5
4493360">12. FAQ</a></span></dt><dt><span class="appendix"><a href="#idp54502208">A. Notes for Older Software</a></span></dt><dt><span class="appendix"><a href="#idp54526032">B. Drill Templates</a></span></dt><dd><dl><dt><span class="section"><a href="#idp54527200">1. TeleMega template</a></span></dt><dt><span class="section"><a href="#idp54543168">2. TeleMetrum template</a></span></dt><dt><span class="section"><a href="#idp54546832">3. TeleMini v2/EasyMini template</a></span></dt><dt><span class="section"><a href="#idp54550512">4. TeleMini v1 template</a></span></dt></dl></dd><dt><span class="appendix"><a href="#idp54554304">C. Calibration</a></span></dt><dd><dl><dt><span class="section"><a href="#idp54555856">1. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp54561136">2. TeleMetrum and TeleMega Accelerometers</a></span></dt></dl></dd><dt><span class="appendix"><a href="#idp54567264">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="#idp47897552">Altus Metrum Electronics</a></dt><dt>4.2. <a href="#idp53870912">Altus Metrum Boards</a></dt><dt>4.3. <a href="#idp53933376">Data Storage on Altus Metrum altimeters</a></dt><dt>5.1. <a href="#idp50990144">AltOS Modes</a></dt><dt>5.2. <a href="#idp54003920">Pad/Idle Indications</a></dt></dl></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp48053984"></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
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="idp
57459264"></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="idp
48061744"></a>Chapter 2. Getting Started</h1></div></div></div><p>
The first thing to do after you check the inventory of parts in your
“starter kit” is to charge the battery.
</p><p>
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="idp
52778544"></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="idp
47890336"></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
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="idp
52784032"></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="#idp52784704">1. Overview</a></span></dt><dt><span class="section"><a href="#idp58332736">2. TeleMetrum</a></span></dt><dt><span class="section"><a href="#idp58337760">3. TeleMini</a></span></dt><dt><span class="section"><a href="#idp58346160">4. EasyMini</a></span></dt><dt><span class="section"><a href="#idp58350144">5. TeleMega</a></span></dt><dt><span class="section"><a href="#idp58354240">6. Flight Data Recording</a></span></dt><dt><span class="section"><a href="#idp58383072">7. Installation</a></span></dt></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp52784704"></a>1. Overview</h2></div></div></div><p>
+ </p></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp
47895824"></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="#idp47896496">1. Overview</a></span></dt><dt><span class="section"><a href="#idp53909808">2. TeleMetrum</a></span></dt><dt><span class="section"><a href="#idp53914976">3. TeleMini</a></span></dt><dt><span class="section"><a href="#idp53923600">4. EasyMini</a></span></dt><dt><span class="section"><a href="#idp53927712">5. TeleMega</a></span></dt><dt><span class="section"><a href="#idp53931936">6. Flight Data Recording</a></span></dt><dt><span class="section"><a href="#idp53961856">7. Installation</a></span></dt></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp47896496"></a>1. Overview</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="idp
52785760"></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="idp56763616"></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="idp
47897552"></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="idp53870912"></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
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="idp5
8332736"></a>2. 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></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="idp5
3909808"></a>2. 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
the e-matches for apogee and main ejection charges depart from the
fin can end of the board, meaning an ideal “simple” avionics
bay for TeleMetrum should have at least 10 inches of interior length.
- </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp5
8337760"></a>3. TeleMini</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 class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp5
3914976"></a>3. TeleMini</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
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><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp5
8346160"></a>4. 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 class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp5
3923600"></a>4. 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><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp5
8350144"></a>5. 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 class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp5
3927712"></a>5. 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><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp5
8354240"></a>6. Flight 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="idp5
3931936"></a>6. 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="idp5
8355648"></a><p class="title"><b>Table 4.3. 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="idp5
3933376"></a><p class="title"><b>Table 4.3. 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>
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
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="idp5
8383072"></a>7. Installation</h2></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp5
3961856"></a>7. 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
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="idp5
8389808"></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="#idp58390448">1. Firmware Modes </a></span></dt><dt><span class="section"><a href="#idp58467152">2. GPS </a></span></dt><dt><span class="section"><a href="#idp58469936">3. Controlling An Altimeter Over The Radio Link</a></span></dt><dt><span class="section"><a href="#idp58481232">4. Ground Testing </a></span></dt><dt><span class="section"><a href="#idp58483984">5. Radio Link </a></span></dt><dt><span class="section"><a href="#idp58488672">6. Configurable Parameters</a></span></dt><dd><dl><dt><span class="section"><a href="#idp58490416">6.1. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp58492464">6.2. Apogee Delay</a></span></dt><dt><span class="section"><a href="#idp58495056">6.3. Main Deployment Altitude</a></span></dt><dt><span class="section"><a href="#idp58496752">6.4. Maximum Flight Log</a></span></dt><dt><span class="section"><a href="#idp58498896">6.5. Ignite Mode</a></span></dt><dt><span class="section"><a href="#idp58501008">6.6. Pad Orientation</a></span></dt><dt><span class="section"><a href="#idp58502704">6.7. 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="idp58390448"></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="idp5
3968624"></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="#idp53969296">1. Firmware Modes </a></span></dt><dt><span class="section"><a href="#idp53977296">2. GPS </a></span></dt><dt><span class="section"><a href="#idp53979824">3. Controlling An Altimeter Over The Radio Link</a></span></dt><dt><span class="section"><a href="#idp54060432">4. Ground Testing </a></span></dt><dt><span class="section"><a href="#idp54063184">5. Radio Link </a></span></dt><dt><span class="section"><a href="#idp54067872">6. Configurable Parameters</a></span></dt><dd><dl><dt><span class="section"><a href="#idp54069616">6.1. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp54071664">6.2. Apogee Delay</a></span></dt><dt><span class="section"><a href="#idp54074256">6.3. Main Deployment Altitude</a></span></dt><dt><span class="section"><a href="#idp54075952">6.4. Maximum Flight Log</a></span></dt><dt><span class="section"><a href="#idp54078096">6.5. Ignite Mode</a></span></dt><dt><span class="section"><a href="#idp54080208">6.6. Pad Orientation</a></span></dt><dt><span class="section"><a href="#idp54081904">6.7. 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="idp53969296"></a>1. Firmware Modes </h2></div></div></div><p>
The AltOS firmware build for the altimeters has two
fundamental modes, “idle” and “flight”. Which of these modes
the firmware operates in is determined at start up time. For
mode. In the description of the beeping pattern, “dit” means a
short beep while "dah" means a long beep (three times as
long). “Brap” means a long dissonant tone.
- </p><div class="table"><a name="idp5
8391728"></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">dit dit dit</td><td align="center">
+ </p><div class="table"><a name="idp5
0990144"></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">dit dit dit</td><td align="center">
<p>
Calibrating sensors, detecting orientation.
</p>
slower than the “no continuity tone”)
</p><p>
Here's a summary of all of the “pad” and “idle” mode indications.
- </p><div class="table"><a name="idp5
8440960"></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="idp5
4003920"></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.
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="idp5
8467152"></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="idp5
3977296"></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
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="idp5
8469936"></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="idp5
3979824"></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
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="idp5
8481232"></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="idp5
4060432"></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,
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="idp5
8483984"></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="idp5
4063184"></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
packet takes a full second to transmit, we recommend an
interval of at least 5 seconds to avoid consuming too much
battery power or radio channel bandwidth.
- </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp5
8488672"></a>6. 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="idp5
4067872"></a>6. Configurable Parameters</h2></div></div></div><p>
Configuring an Altus Metrum altimeter for flight is very
simple. Even on our baro-only TeleMini and EasyMini boards, the use of a Kalman
filter means there is no need to set a “mach delay”. The few
configurable parameters can all be set using AltosUI over USB or
or radio link via TeleDongle.
- </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp5
8490416"></a>6.1. Radio Frequency</h3></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp5
4069616"></a>6.1. Radio Frequency</h3></div></div></div><p>
Altus Metrum boards support radio frequencies in the 70cm
band. By default, the configuration interface provides a
list of 10 “standard” frequencies in 100kHz channels starting at
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="idp5
8492464"></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="idp5
4071664"></a>6.2. 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
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="idp5
8495056"></a>6.3. Main Deployment Altitude</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp5
4074256"></a>6.3. 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
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="idp5
8496752"></a>6.4. Maximum Flight Log</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp5
4075952"></a>6.4. 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
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="idp5
8498896"></a>6.5. Ignite Mode</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp5
4078096"></a>6.5. 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
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="idp5
8501008"></a>6.6. Pad Orientation</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp5
4080208"></a>6.6. Pad Orientation</h3></div></div></div><p>
TeleMetrum and TeleMega 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
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="idp5
8502704"></a>6.7. Configurable Pyro Channels</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp5
4081904"></a>6.7. 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
to activate when various flight conditions are
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="idp5
8525184"></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="#idp58528800">1. Monitor Flight</a></span></dt><dd><dl><dt><span class="section"><a href="#idp58541520">1.1. Launch Pad</a></span></dt><dt><span class="section"><a href="#idp58557152">1.2. Ascent</a></span></dt><dt><span class="section"><a href="#idp58562608">1.3. Descent</a></span></dt><dt><span class="section"><a href="#idp58569472">1.4. Landed</a></span></dt><dt><span class="section"><a href="#idp58575904">1.5. Table</a></span></dt><dt><span class="section"><a href="#idp58579488">1.6. Site Map</a></span></dt></dl></dd><dt><span class="section"><a href="#idp58585152">2. Save Flight Data</a></span></dt><dt><span class="section"><a href="#idp58589632">3. Replay Flight</a></span></dt><dt><span class="section"><a href="#idp58591664">4. Graph Data</a></span></dt><dd><dl><dt><span class="section"><a href="#idp58594048">4.1. Flight Graph</a></span></dt><dt><span class="section"><a href="#idp58598496">4.2. Configure Graph</a></span></dt><dt><span class="section"><a href="#idp58602160">4.3. Flight Statistics</a></span></dt><dt><span class="section"><a href="#idp58605680">4.4. Map</a></span></dt></dl></dd><dt><span class="section"><a href="#idp58609536">5. Export Data</a></span></dt><dd><dl><dt><span class="section"><a href="#idp58611648">5.1. Comma Separated Value Format</a></span></dt><dt><span class="section"><a href="#idp58614000">5.2. Keyhole Markup Language (for Google Earth)</a></span></dt></dl></dd><dt><span class="section"><a href="#idp58615488">6. Configure Altimeter</a></span></dt><dd><dl><dt><span class="section"><a href="#idp58627792">6.1. Main Deploy Altitude</a></span></dt><dt><span class="section"><a href="#idp58629360">6.2. Apogee Delay</a></span></dt><dt><span class="section"><a href="#idp58630976">6.3. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp58632480">6.4. RF Calibration</a></span></dt><dt><span class="section"><a href="#idp58634128">6.5. Telemetry/RDF/APRS Enable</a></span></dt><dt><span class="section"><a href="#idp58635424">6.6. APRS Interval</a></span></dt><dt><span class="section"><a href="#idp58636928">6.7. Callsign</a></span></dt><dt><span class="section"><a href="#idp58638240">6.8. Maximum Flight Log Size</a></span></dt><dt><span class="section"><a href="#idp58639680">6.9. Ignite Mode</a></span></dt><dt><span class="section"><a href="#idp58646672">6.10. Pad Orientation</a></span></dt><dt><span class="section"><a href="#idp58651888">6.11. Configure Pyro Channels</a></span></dt></dl></dd><dt><span class="section"><a href="#idp58657696">7. Configure AltosUI</a></span></dt><dd><dl><dt><span class="section"><a href="#idp58661200">7.1. Voice Settings</a></span></dt><dt><span class="section"><a href="#idp58666224">7.2. Log Directory</a></span></dt><dt><span class="section"><a href="#idp58668224">7.3. Callsign</a></span></dt><dt><span class="section"><a href="#idp58670464">7.4. Imperial Units</a></span></dt><dt><span class="section"><a href="#idp58671968">7.5. Font Size</a></span></dt><dt><span class="section"><a href="#idp58673248">7.6. Serial Debug</a></span></dt><dt><span class="section"><a href="#idp58674752">7.7. Manage Frequencies</a></span></dt></dl></dd><dt><span class="section"><a href="#idp58676384">8. Configure Groundstation</a></span></dt><dd><dl><dt><span class="section"><a href="#idp58687504">8.1. Frequency</a></span></dt><dt><span class="section"><a href="#idp58689072">8.2. Radio Calibration</a></span></dt></dl></dd><dt><span class="section"><a href="#idp58690704">9. Flash Image</a></span></dt><dt><span class="section"><a href="#idp58692336">10. Fire Igniter</a></span></dt><dt><span class="section"><a href="#idp58697968">11. Scan Channels</a></span></dt><dt><span class="section"><a href="#idp58701824">12. Load Maps</a></span></dt><dt><span class="section"><a href="#idp58707520">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="495"><tr><td><img src="altosui.png" width="495"></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="idp5
4104384"></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="#idp54108000">1. Monitor Flight</a></span></dt><dd><dl><dt><span class="section"><a href="#idp54120720">1.1. Launch Pad</a></span></dt><dt><span class="section"><a href="#idp54136352">1.2. Ascent</a></span></dt><dt><span class="section"><a href="#idp54141808">1.3. Descent</a></span></dt><dt><span class="section"><a href="#idp54148672">1.4. Landed</a></span></dt><dt><span class="section"><a href="#idp54155520">1.5. Table</a></span></dt><dt><span class="section"><a href="#idp54159104">1.6. Site Map</a></span></dt></dl></dd><dt><span class="section"><a href="#idp54164768">2. Save Flight Data</a></span></dt><dt><span class="section"><a href="#idp54168720">3. Replay Flight</a></span></dt><dt><span class="section"><a href="#idp54170752">4. Graph Data</a></span></dt><dd><dl><dt><span class="section"><a href="#idp54173136">4.1. Flight Graph</a></span></dt><dt><span class="section"><a href="#idp54177584">4.2. Configure Graph</a></span></dt><dt><span class="section"><a href="#idp54181248">4.3. Flight Statistics</a></span></dt><dt><span class="section"><a href="#idp54184768">4.4. Map</a></span></dt></dl></dd><dt><span class="section"><a href="#idp54188624">5. Export Data</a></span></dt><dd><dl><dt><span class="section"><a href="#idp54190192">5.1. Comma Separated Value Format</a></span></dt><dt><span class="section"><a href="#idp54192544">5.2. Keyhole Markup Language (for Google Earth)</a></span></dt></dl></dd><dt><span class="section"><a href="#idp54194032">6. Configure Altimeter</a></span></dt><dd><dl><dt><span class="section"><a href="#idp54206336">6.1. Main Deploy Altitude</a></span></dt><dt><span class="section"><a href="#idp54208304">6.2. Apogee Delay</a></span></dt><dt><span class="section"><a href="#idp54209920">6.3. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp54211424">6.4. RF Calibration</a></span></dt><dt><span class="section"><a href="#idp54213072">6.5. Telemetry/RDF/APRS Enable</a></span></dt><dt><span class="section"><a href="#idp54214368">6.6. APRS Interval</a></span></dt><dt><span class="section"><a href="#idp54215872">6.7. Callsign</a></span></dt><dt><span class="section"><a href="#idp54217184">6.8. Maximum Flight Log Size</a></span></dt><dt><span class="section"><a href="#idp54218624">6.9. Ignite Mode</a></span></dt><dt><span class="section"><a href="#idp54225616">6.10. Pad Orientation</a></span></dt><dt><span class="section"><a href="#idp54230832">6.11. Configure Pyro Channels</a></span></dt></dl></dd><dt><span class="section"><a href="#idp54236640">7. Configure AltosUI</a></span></dt><dd><dl><dt><span class="section"><a href="#idp54240144">7.1. Voice Settings</a></span></dt><dt><span class="section"><a href="#idp54245168">7.2. Log Directory</a></span></dt><dt><span class="section"><a href="#idp54247168">7.3. Callsign</a></span></dt><dt><span class="section"><a href="#idp54249408">7.4. Imperial Units</a></span></dt><dt><span class="section"><a href="#idp54250912">7.5. Font Size</a></span></dt><dt><span class="section"><a href="#idp54252192">7.6. Serial Debug</a></span></dt><dt><span class="section"><a href="#idp54253696">7.7. Manage Frequencies</a></span></dt></dl></dd><dt><span class="section"><a href="#idp54255328">8. Configure Groundstation</a></span></dt><dd><dl><dt><span class="section"><a href="#idp54266448">8.1. Frequency</a></span></dt><dt><span class="section"><a href="#idp54268016">8.2. Radio Calibration</a></span></dt></dl></dd><dt><span class="section"><a href="#idp54269648">9. Flash Image</a></span></dt><dt><span class="section"><a href="#idp54271280">10. Fire Igniter</a></span></dt><dt><span class="section"><a href="#idp54276912">11. Scan Channels</a></span></dt><dt><span class="section"><a href="#idp54280768">12. Load Maps</a></span></dt><dt><span class="section"><a href="#idp54286464">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
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="idp5
8528800"></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="idp5
4108000"></a>1. Monitor Flight</h2></div><div><h3 class="subtitle">Receive, Record and Display Telemetry Data</h3></div></div></div><p>
Selecting this item brings up a dialog box listing all of the
connected TeleDongle devices. When you choose one of these,
AltosUI will create a window to display telemetry data as
received by the selected TeleDongle device.
- </p><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="
315"><tr><td><img src="device-selection.png" width="315"></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="
279"><tr><td><img src="device-selection.png" width="279"></td></tr></table></div></div><p>
All telemetry data received are automatically recorded in
suitable log files. The name of the files includes the current
date and rocket serial and flight numbers.
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="idp5
8541520"></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="idp5
4120720"></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
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="idp5
8557152"></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="idp5
4136352"></a>1.2. Ascent</h3></div></div></div><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="495"><tr><td><img src="ascent.png" width="495"></td></tr></table></div></div><p>
This tab is shown during Boost, Fast and Coast
phases. The information displayed here helps monitor the
rocket as it heads towards apogee.
</p><p>
- The height, speed and acceleration are shown along with the
- maximum values for each of them. This allows you to quickly
- answer the most commonly asked questions you'll hear during
- flight.
+ The height, speed, acceleration and tilt are shown along
+ with the maximum values for each of them. This allows you to
+ quickly answer the most commonly asked questions you'll hear
+ during flight.
</p><p>
The current latitude and longitude reported by the GPS are
also shown. Note that under high acceleration, these values
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="idp5
8562608"></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="idp5
4141808"></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,
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="idp5
8569472"></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="idp5
4148672"></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
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="idp5
8575904"></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="idp5
4155520"></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="idp5
8579488"></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="idp5
4159104"></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
</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><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp5
8585152"></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="idp5
4164768"></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
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="idp5
8589632"></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="idp5
4168720"></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
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="idp5
8591664"></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="idp5
4170752"></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
</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="idp5
8594048"></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="495"><tr><td><img src="graph.png" width="495"></td></tr></table></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp5
4173136"></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>
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="idp5
8598496"></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="495"><tr><td><img src="graph-configure.png" width="495"></td></tr></table></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp5
4177584"></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="idp5
8602160"></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="495"><tr><td><img src="graph-stats.png" width="495"></td></tr></table></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp5
4181248"></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="idp5
8605680"></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="495"><tr><td><img src="graph-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="idp5
4184768"></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="idp5
8609536"></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="idp5
4188624"></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.
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="idp5
8611648"></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="idp5
4190192"></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
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="idp5
8614000"></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="idp5
4192544"></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="idp5
8615488"></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="270"><tr><td><img src="configure-altimeter.png" width="270"></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="idp5
4194032"></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.
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="idp5
8627792"></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="idp5
4206336"></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="idp5
8629360"></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="idp5
4208304"></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
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="idp5
8630976"></a>6.3. Radio Frequency</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp5
4209920"></a>6.3. Radio 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="idp5
8632480"></a>6.4. RF Calibration</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp5
4211424"></a>6.4. 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
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="idp5
8634128"></a>6.5. Telemetry/RDF/APRS Enable</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp5
4213072"></a>6.5. 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="idp5
8635424"></a>6.6. APRS Interval</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp5
4214368"></a>6.6. APRS Interval</h3></div></div></div><p>
How often to transmit GPS information via APRS. This option
is available on TeleMetrum v2 and TeleMega
boards. TeleMetrum v1 boards cannot transmit APRS
packets. Note that a single APRS packet takes nearly a full
second to transmit, so enabling this option will prevent
sending any other telemetry during that time.
- </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp5
8636928"></a>6.7. Callsign</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp5
4215872"></a>6.7. 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="idp5
8638240"></a>6.8. Maximum Flight Log Size</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp5
4217184"></a>6.8. 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="idp5
8639680"></a>6.9. Ignite Mode</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp5
4218624"></a>6.9. Ignite Mode</h3></div></div></div><p>
TeleMetrum and TeleMini provide two igniter channels as they
were originally designed as dual-deploy flight
computers. This configuration parameter allows the two
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="idp5
8646672"></a>6.10. Pad Orientation</h3></div></div></div><p>
+ </p></dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp5
4225616"></a>6.10. Pad Orientation</h3></div></div></div><p>
Because they include accelerometers, TeleMetrum and
TeleMega are sensitive to the orientation of the board. By
default, they expect the antenna end to point forward. This
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="idp5
8651888"></a>6.11. 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></dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp5
4230832"></a>6.11. 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
presented for each channel. Each row represents a single
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="idp5
8657696"></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="225"><tr><td><img src="configure-altosui.png" width="225"></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="idp5
4236640"></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="idp5
8661200"></a>7.1. Voice Settings</h3></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp5
4240144"></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
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="idp5
8666224"></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="idp5
4245168"></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.
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="idp5
8668224"></a>7.3. Callsign</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp5
4247168"></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
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="idp5
8670464"></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="idp5
4249408"></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="idp5
8671968"></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="idp5
4250912"></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="idp5
8673248"></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="idp5
4252192"></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="idp5
8674752"></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="idp5
4253696"></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="idp5
8676384"></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="270"><tr><td><img src="configure-groundstation.png" width="270"></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="idp5
4255328"></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><p>
The first few lines of the dialog provide information about the
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="idp5
8687504"></a>8.1. Frequency</h3></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp5
4266448"></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="idp5
8689072"></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="idp5
4268016"></a>8.2. Radio 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,
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="idp5
8690704"></a>9. Flash Image</h2></div></div></div><p>
+ </p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp5
4269648"></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
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="idp5
8692336"></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="90"><tr><td><img src="fire-igniter.png" width="90"></td></tr></table></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp5
4271280"></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
</p><p>
Selecting the 'Fire Igniter' button brings up the usual device
selection dialog. Pick the desired device. This brings up another
- window which shows the current continuity test status for both
- apogee and main charges.
+ window which shows the current continuity test status for all
+ of the pyro channels.
</p><p>
Next, select the desired igniter to fire. This will enable the
'Arm' button.
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="idp5
8697968"></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="248"><tr><td><img src="scan-channels.png" width="248"></td></tr></table></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp5
4276912"></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
firmware.
- </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp5
8701824"></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="495"><tr><td><img src="load-maps.png" width="495"></td></tr></table></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp5
4280768"></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
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="idp5
8707520"></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="idp5
4286464"></a>13. Monitor Idle</h2></div></div></div><p>
This brings up a dialog similar to the Monitor Flight UI,
except it works with the altimeter in “idle” mode by sending
query commands to discover the current state rather than
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="idp5
8709616"></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="#idp58712000">1. Installing AltosDroid</a></span></dt><dt><span class="section"><a href="#idp58713936">2. Connecting to TeleBT</a></span></dt><dt><span class="section"><a href="#idp58715936">3. Configuring AltosDroid</a></span></dt><dt><span class="section"><a href="#idp58717392">4. AltosDroid Flight Monitoring</a></span></dt><dd><dl><dt><span class="section"><a href="#idp58718704">4.1. Pad</a></span></dt></dl></dd><dt><span class="section"><a href="#idp58732256">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="idp5
4288560"></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="#idp54290944">1. Installing AltosDroid</a></span></dt><dt><span class="section"><a href="#idp54292880">2. Connecting to TeleBT</a></span></dt><dt><span class="section"><a href="#idp54294880">3. Configuring AltosDroid</a></span></dt><dt><span class="section"><a href="#idp54296336">4. AltosDroid Flight Monitoring</a></span></dt><dd><dl><dt><span class="section"><a href="#idp54297648">4.1. Pad</a></span></dt></dl></dd><dt><span class="section"><a href="#idp54311200">5. Downloading Flight Logs</a></span></dt></dl></div><p>
AltosDroid provides the same flight monitoring capabilities as
AltosUI, but runs on Android devices and is designed to connect
to a TeleBT receiver over Bluetooth™. AltosDroid monitors
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="idp5
8712000"></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="idp5
4290944"></a>1. Installing AltosDroid</h2></div></div></div><p>
AltosDroid is available from the Google Play store. To install
it on your Android device, open the Google Play Store
application and search for “altosdroid”. Make sure you don't
have a space between “altos” and “droid” or you probably won't
find what you want. That should bring you to the right page
from which you can download and install the application.
- </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp5
8713936"></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="idp5
4292880"></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
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="idp5
8715936"></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="idp5
4294880"></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="idp5
8717392"></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="idp5
4296336"></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="idp5
8718704"></a>4.1. Pad</h3></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp5
4297648"></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
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="idp5
8732256"></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="idp5
4311200"></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="idp5
8733920"></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="#idp58734560">1. Being Legal</a></span></dt><dt><span class="section"><a href="#idp58736464">2. In the Rocket</a></span></dt><dt><span class="section"><a href="#idp58738928">3. On the Ground</a></span></dt><dt><span class="section"><a href="#idp58752240">4. Data Analysis</a></span></dt><dt><span class="section"><a href="#idp58754784">5. Future Plans</a></span></dt></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp58734560"></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="idp5
4312864"></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="#idp54313504">1. Being Legal</a></span></dt><dt><span class="section"><a href="#idp54315408">2. In the Rocket</a></span></dt><dt><span class="section"><a href="#idp54317872">3. On the Ground</a></span></dt><dt><span class="section"><a href="#idp54331184">4. Data Analysis</a></span></dt><dt><span class="section"><a href="#idp54333728">5. Future Plans</a></span></dt></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp54313504"></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="idp5
8736464"></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="idp5
4315408"></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
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="idp5
8738928"></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="idp5
4317872"></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
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="idp5
8752240"></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="idp5
4331184"></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
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="idp5
8754784"></a>5. Future Plans</h2></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp5
4333728"></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.
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="idp5
8759168"></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="#idp58760624">1. Mounting the Altimeter</a></span></dt><dt><span class="section"><a href="#idp58766032">2. Dealing with the Antenna</a></span></dt><dt><span class="section"><a href="#idp58771600">3. Preserving GPS Reception</a></span></dt><dt><span class="section"><a href="#idp58776384">4. Radio Frequency Interference</a></span></dt><dt><span class="section"><a href="#idp58783952">5. The Barometric Sensor</a></span></dt><dt><span class="section"><a href="#idp58786752">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="idp5
4338112"></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="#idp54339568">1. Mounting the Altimeter</a></span></dt><dt><span class="section"><a href="#idp54344400">2. Dealing with the Antenna</a></span></dt><dt><span class="section"><a href="#idp54349968">3. Preserving GPS Reception</a></span></dt><dt><span class="section"><a href="#idp54354752">4. Radio Frequency Interference</a></span></dt><dt><span class="section"><a href="#idp54362320">5. The Barometric Sensor</a></span></dt><dt><span class="section"><a href="#idp54365120">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="idp5
8760624"></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="idp5
4339568"></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
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="idp5
8766032"></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="idp5
4344400"></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
SMA connector, and then run 50Ω coax from the board to the
antenna. Building a remote antenna is beyond the scope of this
manual.
- </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp5
8771600"></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="idp5
4349968"></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
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="idp5
8776384"></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="idp5
4354752"></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
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="idp5
8783952"></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="idp5
4362320"></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
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="idp5
8786752"></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="idp5
4365120"></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
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="idp58789920"></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="#idp58793936">1.
+ </p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp54368288"></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="#idp54372304">1.
Updating TeleMega, TeleMetrum v2 or EasyMini Firmware
- </a></span></dt><dd><dl><dt><span class="section"><a href="#idp5
8802752">1.1. Recovering From Self-Flashing Failure</a></span></dt></dl></dd><dt><span class="section"><a href="#idp58811728">2. Pair Programming</a></span></dt><dt><span class="section"><a href="#idp58813168">3. Updating TeleMetrum v1.x Firmware</a></span></dt><dt><span class="section"><a href="#idp58826208">4. Updating TeleMini Firmware</a></span></dt><dt><span class="section"><a href="#idp58839600">5. Updating TeleDongle Firmware</a></span></dt></dl></div><p>
+ </a></span></dt><dd><dl><dt><span class="section"><a href="#idp5
4381120">1.1. Recovering From Self-Flashing Failure</a></span></dt></dl></dd><dt><span class="section"><a href="#idp54390096">2. Pair Programming</a></span></dt><dt><span class="section"><a href="#idp54391536">3. Updating TeleMetrum v1.x Firmware</a></span></dt><dt><span class="section"><a href="#idp54404576">4. Updating TeleMini Firmware</a></span></dt><dt><span class="section"><a href="#idp54417968">5. Updating TeleDongle Firmware</a></span></dt></dl></div><p>
TeleMega, TeleMetrum v2 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
</p><p>
Self-programmable devices (TeleMega, TeleMetrum v2 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="idp58793936"></a>1.
+ </p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp54372304"></a>1.
Updating TeleMega, TeleMetrum v2 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
</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="idp5
8802752"></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="idp5
4381120"></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
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="idp5
8811728"></a>2. Pair Programming</h2></div></div></div><p>
+ </p></dd></dl></div></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp5
4390096"></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="idp5
8813168"></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="idp5
4391536"></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.
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="idp5
8826208"></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="idp5
4404576"></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.
letting it come up in “flight” mode and listening for telemetry.
</p></li><li class="listitem"><p>
If something goes wrong, give it another try.
- </p></li></ol></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp5
8839600"></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="idp5
4417968"></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>
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="idp58856144"></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="#idp58856784">1.
+ </p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp54434512"></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="#idp54435152">1.
TeleMega Specifications
- </a></span></dt><dt><span class="section"><a href="#idp58868016">2.
+ </a></span></dt><dt><span class="section"><a href="#idp54446496">2.
TeleMetrum v2 Specifications
- </a></span></dt><dt><span class="section"><a href="#idp58878256">3. TeleMetrum v1 Specifications</a></span></dt><dt><span class="section"><a href="#idp58888496">4.
+ </a></span></dt><dt><span class="section"><a href="#idp54457056">3. TeleMetrum v1 Specifications</a></span></dt><dt><span class="section"><a href="#idp54467616">4.
TeleMini v2.0 Specifications
- </a></span></dt><dt><span class="section"><a href="#idp58897328">5.
+ </a></span></dt><dt><span class="section"><a href="#idp54476448">5.
TeleMini v1.0 Specifications
- </a></span></dt><dt><span class="section"><a href="#idp58906128">6.
+ </a></span></dt><dt><span class="section"><a href="#idp54485248">6.
EasyMini Specifications
- </a></span></dt></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp58856784"></a>1.
+ </a></span></dt></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp54435152"></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.
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="idp58868016"></a>2.
+ </p></li></ul></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp54446496"></a>2.
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.
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="idp5
8878256"></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="idp5
4457056"></a>3. 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).
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="idp58888496"></a>4.
+ </p></li></ul></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp54467616"></a>4.
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.
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="idp58897328"></a>5.
+ </p></li></ul></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp54476448"></a>5.
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.
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="idp58906128"></a>6.
+ </p></li></ul></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp54485248"></a>6.
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.
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="idp5
8914240"></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="idp5
4493360"></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
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="idp5
8923088"></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="idp5
4502208"></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
Then, divide 434.550 MHz by the
measured frequency and multiply by the current radio cal value show
in the 'c s' command. For an unprogrammed board, the default value
- is 1186611. Take the resulting integer and program it using the 'c f'
+ is 1186611 for cc1111 based products and 7119667 for cc1120
+ based products. Take the resulting integer and program it using the 'c f'
command. Testing with the 'C' command again should show a carrier
within a few tens of Hertz of the intended frequency.
As with all 'c' sub-commands, follow this with a 'c w' to write the
- change to the parameter block in the on-board DataFlash chip.
+ change to the configuration memory.
</p><p>
Note that the 'reboot' command, which is very useful on the altimeters,
will likely just cause problems with the dongle. The *correct* way
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="idp5
8946464"></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="#idp58947632">1. TeleMega template</a></span></dt><dt><span class="section"><a href="#idp58963600">2. TeleMetrum template</a></span></dt><dt><span class="section"><a href="#idp58967264">3. TeleMini v2/EasyMini template</a></span></dt><dt><span class="section"><a href="#idp58970944">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="idp5
4526032"></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="#idp54527200">1. TeleMega template</a></span></dt><dt><span class="section"><a href="#idp54543168">2. TeleMetrum template</a></span></dt><dt><span class="section"><a href="#idp54546832">3. TeleMini v2/EasyMini template</a></span></dt><dt><span class="section"><a href="#idp54550512">4. 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="idp5
8947632"></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="idp5
4527200"></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"><a name="TeleMegaTemplate"></a><object type="image/svg+xml" data="telemega-outline.svg"></object></div></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp5
8963600"></a>2. TeleMetrum template</h2></div></div></div><p>
+ </p><div class="informalfigure"><div class="mediaobject"><a name="TeleMegaTemplate"></a><object type="image/svg+xml" data="telemega-outline.svg"></object></div></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp5
4543168"></a>2. 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"><a name="TeleMetrumTemplate"></a><object type="image/svg+xml" data="telemetrum.svg"></object></div></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp5
8967264"></a>3. TeleMini v2/EasyMini template</h2></div></div></div><p>
+ </p><div class="informalfigure"><div class="mediaobject"><a name="TeleMetrumTemplate"></a><object type="image/svg+xml" data="telemetrum.svg"></object></div></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp5
4546832"></a>3. 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"><a name="MiniTemplate"></a><object type="image/svg+xml" data="easymini-outline.svg"></object></div></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp5
8970944"></a>4. TeleMini v1 template</h2></div></div></div><p>
+ </p><div class="informalfigure"><div class="mediaobject"><a name="MiniTemplate"></a><object type="image/svg+xml" data="easymini-outline.svg"></object></div></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp5
4550512"></a>4. 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"><a name="TeleMiniTemplate"></a><object type="image/svg+xml" data="telemini.svg"></object></div></div></div></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a name="idp5
8974736"></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="#idp58976288">1. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp58980832">2. TeleMetrum and TeleMega Accelerometers</a></span></dt></dl></div><p>
+ </p><div class="informalfigure"><div class="mediaobject"><a name="TeleMiniTemplate"></a><object type="image/svg+xml" data="telemini.svg"></object></div></div></div></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a name="idp5
4554304"></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="#idp54555856">1. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp54561136">2. TeleMetrum and TeleMega 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.
All boards are shipped from the factory pre-calibrated, but
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="idp5
8976288"></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="idp5
4555856"></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
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="idp5
8980832"></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="idp5
4561136"></a>2. TeleMetrum and TeleMega 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
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="idp58985936"></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="idp58986576"></a>Version 1.3</h2></div></div></div><p>
+ </p></div></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a name="idp54567264"></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="idp54567904"></a>Version 1.3.1</h2></div></div></div><p>
+ Version 1.3.1 is a minor release. It improves support for TeleMega,
+ TeleMetrum v2.0, TeleMini v2.0 and EasyMini.
+ </p><p>
+ AltOS Firmware Changes
+ </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
+ Improve sensor boot code. If sensors fail to self-test, the
+ device will still boot up and check for pad/idle modes. If
+ in idle mode, the device will warn the user with a distinct
+ beep, if in Pad mode, the unit will operate as best it
+ can. Also, the Z-axis accelerometer now uses the factory
+ calibration values instead of re-calibrating on the pad each
+ time. This avoids accidental boost detect when moving the
+ device around while in Pad mode.
+ </p></li><li class="listitem"><p>
+ Fix antenna-down mode accelerometer configuration. Antenna
+ down mode wasn't working because the accelerometer
+ calibration values were getting re-computed incorrectly in
+ inverted mode.
+ </p></li><li class="listitem"><p>
+ Improved APRS mode. Now uses compressed position format for
+ smaller data size, improved precision and to include
+ altitude data as well as latitude and longitude. Also added
+ battery and pyro voltage reports in the APRS comment field
+ so you can confirm that the unit is ready for launch.
+ </p></li></ul></div><p>
+ </p><p>
+ AltosUI changes
+ </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
+ Display additional TeleMega sensor values in real
+ units. Make all of these values available for
+ plotting. Display TeleMega orientation value in the Ascent
+ and Table tabs.
+ </p></li><li class="listitem"><p>
+ Support additional TeleMega pyro channels in the Fire
+ Igniter dialog. This lets you do remote testing of all of
+ the channels, rather than just Apogee and Main.
+ </p></li><li class="listitem"><p>
+ Limit data rate when downloading satellite images from
+ Google to make sure we stay within their limits so that all
+ of the map tiles download successfully.
+ </p></li></ul></div><p>
+ </p></div><div class="simplesect"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp54569504"></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>
</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="idp5
8988176"></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="idp5
4571104"></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.
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="idp5
8989776"></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="idp5
4572608"></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>
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="idp5
8991280"></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="idp5
4574112"></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
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="idp5
8992784"></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="idp5
4575616"></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>
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="idp5
8994288"></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="idp5
4577120"></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>
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="idp5
8995792"></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="idp5
4578624"></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.
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="idp5
8997296"></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="idp5
4580128"></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>
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="idp5
8998800"></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="idp5
4581632"></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>
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="idp5
9000304"></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="idp5
4583136"></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
projects / web / altusmetrum / commitdiff
