-<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.76.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="book" title="AltOS"><div class="titlepage"><div><div><h1 class="title"><a name="idm148
30240"></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" title="Legal Notice"><a name="idp1786584"></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.76.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="book" title="AltOS"><div class="titlepage"><div><div><h1 class="title"><a name="idm148
45520"></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" title="Legal Notice"><a name="idp109448"></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 border="1" width="100%" summary="Revision history"><tr><th align="left" valign="top" colspan="2"><b>Revision History</b></th></tr><tr><td align="left">Revision 0.1</td><td align="left">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><dt><span class="chapter"><a href="#idp1
007408">1. Overview</a></span></dt><dt><span class="chapter"><a href="#idp2570488">2. Programming the 8051 with SDCC</a></span></dt><dd><dl><dt><span class="section"><a href="#idp3335368">1. 8051 memory spaces</a></span></dt><dd><dl><dt><span class="section"><a href="#idp2345416">1.1. __data</a></span></dt><dt><span class="section"><a href="#idp1747472">1.2. __idata</a></span></dt><dt><span class="section"><a href="#idp2268896">1.3. __xdata</a></span></dt><dt><span class="section"><a href="#idp2450056">1.4. __pdata</a></span></dt><dt><span class="section"><a href="#idp1759568">1.5. __code</a></span></dt><dt><span class="section"><a href="#idp2412672">1.6. __bit</a></span></dt><dt><span class="section"><a href="#idp3063120">1.7. __sfr, __sfr16, __sfr32, __sbit</a></span></dt></dl></dd><dt><span class="section"><a href="#idp3035016">2. Function calls on the 8051</a></span></dt><dd><dl><dt><span class="section"><a href="#idp3310384">2.1. __reentrant functions</a></span></dt><dt><span class="section"><a href="#idp2964320">2.2. Non __reentrant functions</a></span></dt><dt><span class="section"><a href="#idp1749176">2.3. __interrupt functions</a></span></dt><dt><span class="section"><a href="#idp2952984">2.4. __critical functions and statements</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#idp2996120">3. Task functions</a></span></dt><dd><dl><dt><span class="section"><a href="#idp2706040">1. ao_add_task</a></span></dt><dt><span class="section"><a href="#idp2783376">2. ao_exit</a></span></dt><dt><span class="section"><a href="#idp3175128">3. ao_sleep</a></span></dt><dt><span class="section"><a href="#idp2128856">4. ao_wakeup</a></span></dt><dt><span class="section"><a href="#idp2171264">5. ao_alarm</a></span></dt><dt><span class="section"><a href="#idp1183336">6. ao_start_scheduler</a></span></dt><dt><span class="section"><a href="#idp3499216">7. ao_clock_init</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp3096472">4. Timer Functions</a></span></dt><dd><dl><dt><span class="section"><a href="#idp3254408">1. ao_time</a></span></dt><dt><span class="section"><a href="#idp3394760">2. ao_delay</a></span></dt><dt><span class="section"><a href="#idp2275376">3. ao_timer_set_adc_interval</a></span></dt><dt><span class="section"><a href="#idp3123208">4. ao_timer_init</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp3220992">5. AltOS Mutexes</a></span></dt><dd><dl><dt><span class="section"><a href="#idp2768696">1. ao_mutex_get</a></span></dt><dt><span class="section"><a href="#idp2986320">2. ao_mutex_put</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp2941440">6. CC1111 DMA engine</a></span></dt><dd><dl><dt><span class="section"><a href="#idp3384272">1. ao_dma_alloc</a></span></dt><dt><span class="section"><a href="#idp2607448">2. ao_dma_set_transfer</a></span></dt><dt><span class="section"><a href="#idp2693856">3. ao_dma_start</a></span></dt><dt><span class="section"><a href="#idp3384000">4. ao_dma_trigger</a></span></dt><dt><span class="section"><a href="#idp1789224">5. ao_dma_abort</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp3413720">7. SDCC Stdio interface</a></span></dt><dd><dl><dt><span class="section"><a href="#idp2822792">1. putchar</a></span></dt><dt><span class="section"><a href="#idp2195872">2. getchar</a></span></dt><dt><span class="section"><a href="#idp3467784">3. flush</a></span></dt><dt><span class="section"><a href="#idp2635624">4. ao_add_stdio</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp1974208">8. Command line interface</a></span></dt><dd><dl><dt><span class="section"><a href="#idp2527728">1. ao_cmd_register</a></span></dt><dt><span class="section"><a href="#idp3042496">2. ao_cmd_lex</a></span></dt><dt><span class="section"><a href="#idp3394520">3. ao_cmd_put16</a></span></dt><dt><span class="section"><a href="#idp2319960">4. ao_cmd_put8</a></span></dt><dt><span class="section"><a href="#idp3139656">5. ao_cmd_white</a></span></dt><dt><span class="section"><a href="#idp3492136">6. ao_cmd_hex</a></span></dt><dt><span class="section"><a href="#idp2389576">7. ao_cmd_decimal</a></span></dt><dt><span class="section"><a href="#idp2185464">8. ao_match_word</a></span></dt><dt><span class="section"><a href="#idp2280648">9. ao_cmd_init</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp2495376">9. CC1111 USB target device</a></span></dt><dd><dl><dt><span class="section"><a href="#idp1747872">1. ao_usb_flush</a></span></dt><dt><span class="section"><a href="#idp2050352">2. ao_usb_putchar</a></span></dt><dt><span class="section"><a href="#idp2639304">3. ao_usb_pollchar</a></span></dt><dt><span class="section"><a href="#idp3533104">4. ao_usb_getchar</a></span></dt><dt><span class="section"><a href="#idp1750296">5. ao_usb_disable</a></span></dt><dt><span class="section"><a href="#idp2101016">6. ao_usb_enable</a></span></dt><dt><span class="section"><a href="#idp2678984">7. ao_usb_init</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp2249432">10. CC1111 Serial peripheral</a></span></dt><dd><dl><dt><span class="section"><a href="#idp2996672">1. ao_serial_getchar</a></span></dt><dt><span class="section"><a href="#idp3155952">2. ao_serial_putchar</a></span></dt><dt><span class="section"><a href="#idp3350064">3. ao_serial_drain</a></span></dt><dt><span class="section"><a href="#idp2065008">4. ao_serial_set_speed</a></span></dt><dt><span class="section"><a href="#idp2450936">5. ao_serial_init</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp1286080">11. CC1111 Radio peripheral</a></span></dt><dd><dl><dt><span class="section"><a href="#idp3302144">1. ao_radio_set_telemetry</a></span></dt><dt><span class="section"><a href="#idp988776">2. ao_radio_set_packet</a></span></dt><dt><span class="section"><a href="#idp3394248">3. ao_radio_set_rdf</a></span></dt><dt><span class="section"><a href="#idp3062848">4. ao_radio_idle</a></span></dt><dt><span class="section"><a href="#idp2490456">5. ao_radio_get</a></span></dt><dt><span class="section"><a href="#idp2147760">6. ao_radio_put</a></span></dt><dt><span class="section"><a href="#idp1214600">7. ao_radio_abort</a></span></dt><dt><span class="section"><a href="#idp1806960">8. ao_radio_send</a></span></dt><dt><span class="section"><a href="#idp3252216">9. ao_radio_recv</a></span></dt><dt><span class="section"><a href="#idp1259776">10. ao_radio_rdf</a></span></dt><dt><span class="section"><a href="#idp2069696">11. ao_packet_putchar</a></span></dt><dt><span class="section"><a href="#idp1536592">12. ao_packet_pollchar</a></span></dt><dt><span class="section"><a href="#idp3165392">13. ao_packet_slave_start</a></span></dt><dt><span class="section"><a href="#idp3384408">14. ao_packet_slave_stop</a></span></dt><dt><span class="section"><a href="#idp2784376">15. ao_packet_slave_init</a></span></dt><dt><span class="section"><a href="#idp2737784">16. ao_packet_master_init</a></span></dt></dl></dd></dl></div><div class="chapter" title="Chapter 1. Overview"><div class="titlepage"><div><div><h2 class="title"><a name="idp1007408"></a>Chapter 1. Overview</h2></div></div></div><p>
+ </p></div></div><div><div class="revhistory"><table border="1" width="100%" summary="Revision history"><tr><th align="left" valign="top" colspan="2"><b>Revision History</b></th></tr><tr><td align="left">Revision 0.1</td><td align="left">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><dt><span class="chapter"><a href="#idp1
11432">1. Overview</a></span></dt><dt><span class="chapter"><a href="#idp1427552">2. Programming the 8051 with SDCC</a></span></dt><dd><dl><dt><span class="section"><a href="#idp1932896">1. 8051 memory spaces</a></span></dt><dd><dl><dt><span class="section"><a href="#idp1539448">1.1. __data</a></span></dt><dt><span class="section"><a href="#idp3243048">1.2. __idata</a></span></dt><dt><span class="section"><a href="#idp905104">1.3. __xdata</a></span></dt><dt><span class="section"><a href="#idp2815944">1.4. __pdata</a></span></dt><dt><span class="section"><a href="#idp2085816">1.5. __code</a></span></dt><dt><span class="section"><a href="#idp1611720">1.6. __bit</a></span></dt><dt><span class="section"><a href="#idp2143464">1.7. __sfr, __sfr16, __sfr32, __sbit</a></span></dt></dl></dd><dt><span class="section"><a href="#idp2034368">2. Function calls on the 8051</a></span></dt><dd><dl><dt><span class="section"><a href="#idp2827648">2.1. __reentrant functions</a></span></dt><dt><span class="section"><a href="#idp3350176">2.2. Non __reentrant functions</a></span></dt><dt><span class="section"><a href="#idp1644208">2.3. __interrupt functions</a></span></dt><dt><span class="section"><a href="#idp1931128">2.4. __critical functions and statements</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#idp2235720">3. Task functions</a></span></dt><dd><dl><dt><span class="section"><a href="#idp2145232">1. ao_add_task</a></span></dt><dt><span class="section"><a href="#idp49456">2. ao_exit</a></span></dt><dt><span class="section"><a href="#idp50328">3. ao_sleep</a></span></dt><dt><span class="section"><a href="#idp52064">4. ao_wakeup</a></span></dt><dt><span class="section"><a href="#idp5464">5. ao_alarm</a></span></dt><dt><span class="section"><a href="#idp7304">6. ao_start_scheduler</a></span></dt><dt><span class="section"><a href="#idp8360">7. ao_clock_init</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp9632">4. Timer Functions</a></span></dt><dd><dl><dt><span class="section"><a href="#idp10624">1. ao_time</a></span></dt><dt><span class="section"><a href="#idp11688">2. ao_delay</a></span></dt><dt><span class="section"><a href="#idp12688">3. ao_timer_set_adc_interval</a></span></dt><dt><span class="section"><a href="#idp748296">4. ao_timer_init</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp749488">5. AltOS Mutexes</a></span></dt><dd><dl><dt><span class="section"><a href="#idp750840">1. ao_mutex_get</a></span></dt><dt><span class="section"><a href="#idp751936">2. ao_mutex_put</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp753080">6. CC1111 DMA engine</a></span></dt><dd><dl><dt><span class="section"><a href="#idp754920">1. ao_dma_alloc</a></span></dt><dt><span class="section"><a href="#idp756296">2. ao_dma_set_transfer</a></span></dt><dt><span class="section"><a href="#idp757744">3. ao_dma_start</a></span></dt><dt><span class="section"><a href="#idp758808">4. ao_dma_trigger</a></span></dt><dt><span class="section"><a href="#idp759864">5. ao_dma_abort</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp761032">7. SDCC Stdio interface</a></span></dt><dd><dl><dt><span class="section"><a href="#idp761992">1. putchar</a></span></dt><dt><span class="section"><a href="#idp763040">2. getchar</a></span></dt><dt><span class="section"><a href="#idp54808">3. flush</a></span></dt><dt><span class="section"><a href="#idp55872">4. ao_add_stdio</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp58336">8. Command line interface</a></span></dt><dd><dl><dt><span class="section"><a href="#idp59184">1. ao_cmd_register</a></span></dt><dt><span class="section"><a href="#idp64112">2. ao_cmd_lex</a></span></dt><dt><span class="section"><a href="#idp65264">3. ao_cmd_put16</a></span></dt><dt><span class="section"><a href="#idp66304">4. ao_cmd_put8</a></span></dt><dt><span class="section"><a href="#idp67336">5. ao_cmd_white</a></span></dt><dt><span class="section"><a href="#idp68488">6. ao_cmd_hex</a></span></dt><dt><span class="section"><a href="#idp69616">7. ao_cmd_decimal</a></span></dt><dt><span class="section"><a href="#idp70800">8. ao_match_word</a></span></dt><dt><span class="section"><a href="#idp72032">9. ao_cmd_init</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp73256">9. CC1111 USB target device</a></span></dt><dd><dl><dt><span class="section"><a href="#idp74736">1. ao_usb_flush</a></span></dt><dt><span class="section"><a href="#idp75960">2. ao_usb_putchar</a></span></dt><dt><span class="section"><a href="#idp77216">3. ao_usb_pollchar</a></span></dt><dt><span class="section"><a href="#idp3450240">4. ao_usb_getchar</a></span></dt><dt><span class="section"><a href="#idp3451248">5. ao_usb_disable</a></span></dt><dt><span class="section"><a href="#idp3452920">6. ao_usb_enable</a></span></dt><dt><span class="section"><a href="#idp3454056">7. ao_usb_init</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp3455248">10. CC1111 Serial peripheral</a></span></dt><dd><dl><dt><span class="section"><a href="#idp3456504">1. ao_serial_getchar</a></span></dt><dt><span class="section"><a href="#idp3457568">2. ao_serial_putchar</a></span></dt><dt><span class="section"><a href="#idp3458624">3. ao_serial_drain</a></span></dt><dt><span class="section"><a href="#idp3459664">4. ao_serial_set_speed</a></span></dt><dt><span class="section"><a href="#idp3460792">5. ao_serial_init</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp3461952">11. CC1111 Radio peripheral</a></span></dt><dd><dl><dt><span class="section"><a href="#idp3466304">1. ao_radio_set_telemetry</a></span></dt><dt><span class="section"><a href="#idp3467552">2. ao_radio_set_packet</a></span></dt><dt><span class="section"><a href="#idp3468800">3. ao_radio_set_rdf</a></span></dt><dt><span class="section"><a href="#idp3470080">4. ao_radio_idle</a></span></dt><dt><span class="section"><a href="#idp3471168">5. ao_radio_get</a></span></dt><dt><span class="section"><a href="#idp3472232">6. ao_radio_put</a></span></dt><dt><span class="section"><a href="#idp3473200">7. ao_radio_abort</a></span></dt><dt><span class="section"><a href="#idp3474720">8. ao_radio_send</a></span></dt><dt><span class="section"><a href="#idp3475976">9. ao_radio_recv</a></span></dt><dt><span class="section"><a href="#idp3477624">10. ao_radio_rdf</a></span></dt><dt><span class="section"><a href="#idp3479128">11. ao_packet_putchar</a></span></dt><dt><span class="section"><a href="#idp3480400">12. ao_packet_pollchar</a></span></dt><dt><span class="section"><a href="#idp3481520">13. ao_packet_slave_start</a></span></dt><dt><span class="section"><a href="#idp3482560">14. ao_packet_slave_stop</a></span></dt><dt><span class="section"><a href="#idp3483568">15. ao_packet_slave_init</a></span></dt><dt><span class="section"><a href="#idp3484688">16. ao_packet_master_init</a></span></dt></dl></dd></dl></div><div class="chapter" title="Chapter 1. Overview"><div class="titlepage"><div><div><h2 class="title"><a name="idp111432"></a>Chapter 1. Overview</h2></div></div></div><p>
AltOS is a operating system built for the 8051-compatible
processor found in the TI cc1111 microcontroller. It's designed
to be small and easy to program with. The main features are:
</pre><p>
As you can see, a long sequence of subsystems are initialized
and then the scheduler is started.
- </p></div><div class="chapter" title="Chapter 2. Programming the 8051 with SDCC"><div class="titlepage"><div><div><h2 class="title"><a name="idp
2570488"></a>Chapter 2. Programming the 8051 with SDCC</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#idp3335368">1. 8051 memory spaces</a></span></dt><dd><dl><dt><span class="section"><a href="#idp2345416">1.1. __data</a></span></dt><dt><span class="section"><a href="#idp1747472">1.2. __idata</a></span></dt><dt><span class="section"><a href="#idp2268896">1.3. __xdata</a></span></dt><dt><span class="section"><a href="#idp2450056">1.4. __pdata</a></span></dt><dt><span class="section"><a href="#idp1759568">1.5. __code</a></span></dt><dt><span class="section"><a href="#idp2412672">1.6. __bit</a></span></dt><dt><span class="section"><a href="#idp3063120">1.7. __sfr, __sfr16, __sfr32, __sbit</a></span></dt></dl></dd><dt><span class="section"><a href="#idp3035016">2. Function calls on the 8051</a></span></dt><dd><dl><dt><span class="section"><a href="#idp3310384">2.1. __reentrant functions</a></span></dt><dt><span class="section"><a href="#idp2964320">2.2. Non __reentrant functions</a></span></dt><dt><span class="section"><a href="#idp1749176">2.3. __interrupt functions</a></span></dt><dt><span class="section"><a href="#idp2952984">2.4. __critical functions and statements</a></span></dt></dl></dd></dl></div><p>
+ </p></div><div class="chapter" title="Chapter 2. Programming the 8051 with SDCC"><div class="titlepage"><div><div><h2 class="title"><a name="idp
1427552"></a>Chapter 2. Programming the 8051 with SDCC</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#idp1932896">1. 8051 memory spaces</a></span></dt><dd><dl><dt><span class="section"><a href="#idp1539448">1.1. __data</a></span></dt><dt><span class="section"><a href="#idp3243048">1.2. __idata</a></span></dt><dt><span class="section"><a href="#idp905104">1.3. __xdata</a></span></dt><dt><span class="section"><a href="#idp2815944">1.4. __pdata</a></span></dt><dt><span class="section"><a href="#idp2085816">1.5. __code</a></span></dt><dt><span class="section"><a href="#idp1611720">1.6. __bit</a></span></dt><dt><span class="section"><a href="#idp2143464">1.7. __sfr, __sfr16, __sfr32, __sbit</a></span></dt></dl></dd><dt><span class="section"><a href="#idp2034368">2. Function calls on the 8051</a></span></dt><dd><dl><dt><span class="section"><a href="#idp2827648">2.1. __reentrant functions</a></span></dt><dt><span class="section"><a href="#idp3350176">2.2. Non __reentrant functions</a></span></dt><dt><span class="section"><a href="#idp1644208">2.3. __interrupt functions</a></span></dt><dt><span class="section"><a href="#idp1931128">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
stack itself is of limited size. While SDCC papers over the
instruction set, it is not completely able to hide the memory
architecture from the application designer.
- </p><div class="section" title="1. 8051 memory spaces"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
3335368"></a>1. 8051 memory spaces</h2></div></div></div><p>
+ </p><div class="section" title="1. 8051 memory spaces"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
1932896"></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" title="1.1. __data"><div class="titlepage"><div><div><h3 class="title"><a name="idp
2345416"></a>1.1. __data</h3></div></div></div><p>
+ </p><div class="section" title="1.1. __data"><div class="titlepage"><div><div><h3 class="title"><a name="idp
1539448"></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" title="1.2. __idata"><div class="titlepage"><div><div><h3 class="title"><a name="idp
1747472"></a>1.2. __idata</h3></div></div></div><p>
+ </p></div><div class="section" title="1.2. __idata"><div class="titlepage"><div><div><h3 class="title"><a name="idp
3243048"></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" title="1.3. __xdata"><div class="titlepage"><div><div><h3 class="title"><a name="idp
2268896"></a>1.3. __xdata</h3></div></div></div><p>
+ </p></div><div class="section" title="1.3. __xdata"><div class="titlepage"><div><div><h3 class="title"><a name="idp
905104"></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" title="1.4. __pdata"><div class="titlepage"><div><div><h3 class="title"><a name="idp2
450056"></a>1.4. __pdata</h3></div></div></div><p>
+ </p></div><div class="section" title="1.4. __pdata"><div class="titlepage"><div><div><h3 class="title"><a name="idp2
815944"></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" title="1.5. __code"><div class="titlepage"><div><div><h3 class="title"><a name="idp
1759568"></a>1.5. __code</h3></div></div></div><p>
+ </p></div><div class="section" title="1.5. __code"><div class="titlepage"><div><div><h3 class="title"><a name="idp
2085816"></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" title="1.6. __bit"><div class="titlepage"><div><div><h3 class="title"><a name="idp
2412672"></a>1.6. __bit</h3></div></div></div><p>
+ </p></div><div class="section" title="1.6. __bit"><div class="titlepage"><div><div><h3 class="title"><a name="idp
1611720"></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" title="1.7. __sfr, __sfr16, __sfr32, __sbit"><div class="titlepage"><div><div><h3 class="title"><a name="idp
3063120"></a>1.7. __sfr, __sfr16, __sfr32, __sbit</h3></div></div></div><p>
+ </p></div><div class="section" title="1.7. __sfr, __sfr16, __sfr32, __sbit"><div class="titlepage"><div><div><h3 class="title"><a name="idp
2143464"></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" title="2. Function calls on the 8051"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
3035016"></a>2. Function calls on the 8051</h2></div></div></div><p>
+ </p></div></div><div class="section" title="2. Function calls on the 8051"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
2034368"></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" title="2.1. __reentrant functions"><div class="titlepage"><div><div><h3 class="title"><a name="idp
3310384"></a>2.1. __reentrant functions</h3></div></div></div><p>
+ </p><div class="section" title="2.1. __reentrant functions"><div class="titlepage"><div><div><h3 class="title"><a name="idp
2827648"></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" title="2.2. Non __reentrant functions"><div class="titlepage"><div><div><h3 class="title"><a name="idp
2964320"></a>2.2. Non __reentrant functions</h3></div></div></div><p>
+ </p></div><div class="section" title="2.2. Non __reentrant functions"><div class="titlepage"><div><div><h3 class="title"><a name="idp
3350176"></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" title="2.3. __interrupt functions"><div class="titlepage"><div><div><h3 class="title"><a name="idp1
749176"></a>2.3. __interrupt functions</h3></div></div></div><p>
+ </p></div><div class="section" title="2.3. __interrupt functions"><div class="titlepage"><div><div><h3 class="title"><a name="idp1
644208"></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" title="2.4. __critical functions and statements"><div class="titlepage"><div><div><h3 class="title"><a name="idp
2952984"></a>2.4. __critical functions and statements</h3></div></div></div><p>
+ </p></div><div class="section" title="2.4. __critical functions and statements"><div class="titlepage"><div><div><h3 class="title"><a name="idp
1931128"></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
that statement. Keeping critical sections as short as
possible is key to ensuring that interrupts are handled as
quickly as possible.
- </p></div></div></div><div class="chapter" title="Chapter 3. Task functions"><div class="titlepage"><div><div><h2 class="title"><a name="idp2
996120"></a>Chapter 3. Task functions</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#idp2706040">1. ao_add_task</a></span></dt><dt><span class="section"><a href="#idp2783376">2. ao_exit</a></span></dt><dt><span class="section"><a href="#idp3175128">3. ao_sleep</a></span></dt><dt><span class="section"><a href="#idp2128856">4. ao_wakeup</a></span></dt><dt><span class="section"><a href="#idp2171264">5. ao_alarm</a></span></dt><dt><span class="section"><a href="#idp1183336">6. ao_start_scheduler</a></span></dt><dt><span class="section"><a href="#idp3499216">7. ao_clock_init</a></span></dt></dl></div><p>
+ </p></div></div></div><div class="chapter" title="Chapter 3. Task functions"><div class="titlepage"><div><div><h2 class="title"><a name="idp2
235720"></a>Chapter 3. Task functions</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#idp2145232">1. ao_add_task</a></span></dt><dt><span class="section"><a href="#idp49456">2. ao_exit</a></span></dt><dt><span class="section"><a href="#idp50328">3. ao_sleep</a></span></dt><dt><span class="section"><a href="#idp52064">4. ao_wakeup</a></span></dt><dt><span class="section"><a href="#idp5464">5. ao_alarm</a></span></dt><dt><span class="section"><a href="#idp7304">6. ao_start_scheduler</a></span></dt><dt><span class="section"><a href="#idp8360">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" title="1. ao_add_task"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp2
706040"></a>1. ao_add_task</h2></div></div></div><pre class="programlisting">
+ </p><div class="section" title="1. ao_add_task"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp2
145232"></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" title="2. ao_exit"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
2783376"></a>2. ao_exit</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section" title="2. ao_exit"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
49456"></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" title="3. ao_sleep"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
3175128"></a>3. ao_sleep</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section" title="3. ao_sleep"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
50328"></a>3. ao_sleep</h2></div></div></div><pre class="programlisting">
void
ao_sleep(__xdata void *wchan)
</pre><p>
__critical while (!ao_radio_done)
ao_sleep(&ao_radio_done);
</pre><p>
- </p></div><div class="section" title="4. ao_wakeup"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
2128856"></a>4. ao_wakeup</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section" title="4. ao_wakeup"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
52064"></a>4. ao_wakeup</h2></div></div></div><pre class="programlisting">
void
ao_wakeup(__xdata void *wchan)
</pre><p>
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" title="5. ao_alarm"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
2171264"></a>5. ao_alarm</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section" title="5. ao_alarm"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
5464"></a>5. ao_alarm</h2></div></div></div><pre class="programlisting">
void
ao_alarm(uint16_t delay)
</pre><p>
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" title="6. ao_start_scheduler"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
1183336"></a>6. ao_start_scheduler</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section" title="6. ao_start_scheduler"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
7304"></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" title="7. ao_clock_init"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
3499216"></a>7. ao_clock_init</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section" title="7. ao_clock_init"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
8360"></a>7. ao_clock_init</h2></div></div></div><pre class="programlisting">
void
ao_clock_init(void)
</pre><p>
internal devices like USB. It should be called by the
'main' function first, before initializing any of the
other devices in the system.
- </p></div></div><div class="chapter" title="Chapter 4. Timer Functions"><div class="titlepage"><div><div><h2 class="title"><a name="idp
3096472"></a>Chapter 4. Timer Functions</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#idp3254408">1. ao_time</a></span></dt><dt><span class="section"><a href="#idp3394760">2. ao_delay</a></span></dt><dt><span class="section"><a href="#idp2275376">3. ao_timer_set_adc_interval</a></span></dt><dt><span class="section"><a href="#idp3123208">4. ao_timer_init</a></span></dt></dl></div><p>
+ </p></div></div><div class="chapter" title="Chapter 4. Timer Functions"><div class="titlepage"><div><div><h2 class="title"><a name="idp
9632"></a>Chapter 4. Timer Functions</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#idp10624">1. ao_time</a></span></dt><dt><span class="section"><a href="#idp11688">2. ao_delay</a></span></dt><dt><span class="section"><a href="#idp12688">3. ao_timer_set_adc_interval</a></span></dt><dt><span class="section"><a href="#idp748296">4. ao_timer_init</a></span></dt></dl></div><p>
AltOS sets up one of the cc1111 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 ADC values are sampled at a regular rate, independent
of any scheduling jitter.
- </p><div class="section" title="1. ao_time"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
3254408"></a>1. ao_time</h2></div></div></div><pre class="programlisting">
+ </p><div class="section" title="1. ao_time"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
10624"></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" title="2. ao_delay"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
3394760"></a>2. ao_delay</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section" title="2. ao_delay"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
11688"></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" title="3. ao_timer_set_adc_interval"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
2275376"></a>3. ao_timer_set_adc_interval</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section" title="3. ao_timer_set_adc_interval"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
12688"></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" title="4. ao_timer_init"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
3123208"></a>4. ao_timer_init</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section" title="4. ao_timer_init"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
748296"></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 using the CC1111 timer 1. 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" title="Chapter 5. AltOS Mutexes"><div class="titlepage"><div><div><h2 class="title"><a name="idp
3220992"></a>Chapter 5. AltOS Mutexes</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#idp2768696">1. ao_mutex_get</a></span></dt><dt><span class="section"><a href="#idp2986320">2. ao_mutex_put</a></span></dt></dl></div><p>
+ </p></div></div><div class="chapter" title="Chapter 5. AltOS Mutexes"><div class="titlepage"><div><div><h2 class="title"><a name="idp
749488"></a>Chapter 5. AltOS Mutexes</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#idp750840">1. ao_mutex_get</a></span></dt><dt><span class="section"><a href="#idp751936">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" title="1. ao_mutex_get"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
2768696"></a>1. ao_mutex_get</h2></div></div></div><pre class="programlisting">
+ </p><div class="section" title="1. ao_mutex_get"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
750840"></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" title="2. ao_mutex_put"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
2986320"></a>2. ao_mutex_put</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section" title="2. ao_mutex_put"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
751936"></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" title="Chapter 6. CC1111 DMA engine"><div class="titlepage"><div><div><h2 class="title"><a name="idp
2941440"></a>Chapter 6. CC1111 DMA engine</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#idp3384272">1. ao_dma_alloc</a></span></dt><dt><span class="section"><a href="#idp2607448">2. ao_dma_set_transfer</a></span></dt><dt><span class="section"><a href="#idp2693856">3. ao_dma_start</a></span></dt><dt><span class="section"><a href="#idp3384000">4. ao_dma_trigger</a></span></dt><dt><span class="section"><a href="#idp1789224">5. ao_dma_abort</a></span></dt></dl></div><p>
+ </p></div></div><div class="chapter" title="Chapter 6. CC1111 DMA engine"><div class="titlepage"><div><div><h2 class="title"><a name="idp
753080"></a>Chapter 6. CC1111 DMA engine</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#idp754920">1. ao_dma_alloc</a></span></dt><dt><span class="section"><a href="#idp756296">2. ao_dma_set_transfer</a></span></dt><dt><span class="section"><a href="#idp757744">3. ao_dma_start</a></span></dt><dt><span class="section"><a href="#idp758808">4. ao_dma_trigger</a></span></dt><dt><span class="section"><a href="#idp759864">5. ao_dma_abort</a></span></dt></dl></div><p>
The CC1111 contains a useful bit of extra hardware in the form
of five programmable DMA engines. They can be configured to copy
data in memory, or between memory and devices (or even between
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" title="1. ao_dma_alloc"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
3384272"></a>1. ao_dma_alloc</h2></div></div></div><pre class="programlisting">
+ </p><div class="section" title="1. ao_dma_alloc"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
754920"></a>1. ao_dma_alloc</h2></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" title="2. ao_dma_set_transfer"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
2607448"></a>2. ao_dma_set_transfer</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section" title="2. ao_dma_set_transfer"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
756296"></a>2. ao_dma_set_transfer</h2></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" title="3. ao_dma_start"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
2693856"></a>3. ao_dma_start</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section" title="3. ao_dma_start"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
757744"></a>3. ao_dma_start</h2></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" title="4. ao_dma_trigger"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
3384000"></a>4. ao_dma_trigger</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section" title="4. ao_dma_trigger"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
758808"></a>4. ao_dma_trigger</h2></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" title="5. ao_dma_abort"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
1789224"></a>5. ao_dma_abort</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section" title="5. ao_dma_abort"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
759864"></a>5. ao_dma_abort</h2></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="chapter" title="Chapter 7. SDCC Stdio interface"><div class="titlepage"><div><div><h2 class="title"><a name="idp
3413720"></a>Chapter 7. SDCC Stdio interface</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#idp2822792">1. putchar</a></span></dt><dt><span class="section"><a href="#idp2195872">2. getchar</a></span></dt><dt><span class="section"><a href="#idp3467784">3. flush</a></span></dt><dt><span class="section"><a href="#idp2635624">4. ao_add_stdio</a></span></dt></dl></div><p>
+ </p></div></div><div class="chapter" title="Chapter 7. SDCC Stdio interface"><div class="titlepage"><div><div><h2 class="title"><a name="idp
761032"></a>Chapter 7. SDCC Stdio interface</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#idp761992">1. putchar</a></span></dt><dt><span class="section"><a href="#idp763040">2. getchar</a></span></dt><dt><span class="section"><a href="#idp54808">3. flush</a></span></dt><dt><span class="section"><a href="#idp55872">4. ao_add_stdio</a></span></dt></dl></div><p>
AltOS offers a stdio interface over both USB and the RF packet
link. This provides for control of the device localy or
remotely. This is hooked up to the stdio functions in SDCC by
automatically multiplex the two available communication
channels; output is always delivered to the channel which
provided the most recent input.
- </p><div class="section" title="1. putchar"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
2822792"></a>1. putchar</h2></div></div></div><pre class="programlisting">
+ </p><div class="section" title="1. putchar"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
761992"></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" title="2. getchar"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
2195872"></a>2. getchar</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section" title="2. getchar"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
763040"></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" title="3. flush"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
3467784"></a>3. flush</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section" title="3. flush"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
54808"></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" title="4. ao_add_stdio"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
2635624"></a>4. ao_add_stdio</h2></div></div></div><pre class="programlisting">
+ xo </p></div><div class="section" title="4. ao_add_stdio"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
55872"></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" title="Chapter 8. Command line interface"><div class="titlepage"><div><div><h2 class="title"><a name="idp
1974208"></a>Chapter 8. Command line interface</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#idp2527728">1. ao_cmd_register</a></span></dt><dt><span class="section"><a href="#idp3042496">2. ao_cmd_lex</a></span></dt><dt><span class="section"><a href="#idp3394520">3. ao_cmd_put16</a></span></dt><dt><span class="section"><a href="#idp2319960">4. ao_cmd_put8</a></span></dt><dt><span class="section"><a href="#idp3139656">5. ao_cmd_white</a></span></dt><dt><span class="section"><a href="#idp3492136">6. ao_cmd_hex</a></span></dt><dt><span class="section"><a href="#idp2389576">7. ao_cmd_decimal</a></span></dt><dt><span class="section"><a href="#idp2185464">8. ao_match_word</a></span></dt><dt><span class="section"><a href="#idp2280648">9. ao_cmd_init</a></span></dt></dl></div><p>
+ </p></div></div><div class="chapter" title="Chapter 8. Command line interface"><div class="titlepage"><div><div><h2 class="title"><a name="idp
58336"></a>Chapter 8. Command line interface</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#idp59184">1. ao_cmd_register</a></span></dt><dt><span class="section"><a href="#idp64112">2. ao_cmd_lex</a></span></dt><dt><span class="section"><a href="#idp65264">3. ao_cmd_put16</a></span></dt><dt><span class="section"><a href="#idp66304">4. ao_cmd_put8</a></span></dt><dt><span class="section"><a href="#idp67336">5. ao_cmd_white</a></span></dt><dt><span class="section"><a href="#idp68488">6. ao_cmd_hex</a></span></dt><dt><span class="section"><a href="#idp69616">7. ao_cmd_decimal</a></span></dt><dt><span class="section"><a href="#idp70800">8. ao_match_word</a></span></dt><dt><span class="section"><a href="#idp72032">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 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" title="1. ao_cmd_register"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
2527728"></a>1. ao_cmd_register</h2></div></div></div><pre class="programlisting">
+ </p><div class="section" title="1. ao_cmd_register"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
59184"></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" title="2. ao_cmd_lex"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
3042496"></a>2. ao_cmd_lex</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section" title="2. ao_cmd_lex"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
64112"></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" title="3. ao_cmd_put16"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
3394520"></a>3. ao_cmd_put16</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section" title="3. ao_cmd_put16"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
65264"></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" title="4. ao_cmd_put8"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
2319960"></a>4. ao_cmd_put8</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section" title="4. ao_cmd_put8"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
66304"></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" title="5. ao_cmd_white"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
3139656"></a>5. ao_cmd_white</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section" title="5. ao_cmd_white"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
67336"></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" title="6. ao_cmd_hex"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
3492136"></a>6. ao_cmd_hex</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section" title="6. ao_cmd_hex"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
68488"></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" title="7. ao_cmd_decimal"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
2389576"></a>7. ao_cmd_decimal</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section" title="7. ao_cmd_decimal"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
69616"></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" title="8. ao_match_word"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
2185464"></a>8. ao_match_word</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section" title="8. ao_match_word"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
70800"></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" title="9. ao_cmd_init"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
2280648"></a>9. ao_cmd_init</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section" title="9. ao_cmd_init"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
72032"></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" title="Chapter 9. CC1111 USB target device"><div class="titlepage"><div><div><h2 class="title"><a name="idp
2495376"></a>Chapter 9. CC1111 USB target device</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#idp1747872">1. ao_usb_flush</a></span></dt><dt><span class="section"><a href="#idp2050352">2. ao_usb_putchar</a></span></dt><dt><span class="section"><a href="#idp2639304">3. ao_usb_pollchar</a></span></dt><dt><span class="section"><a href="#idp3533104">4. ao_usb_getchar</a></span></dt><dt><span class="section"><a href="#idp1750296">5. ao_usb_disable</a></span></dt><dt><span class="section"><a href="#idp2101016">6. ao_usb_enable</a></span></dt><dt><span class="section"><a href="#idp2678984">7. ao_usb_init</a></span></dt></dl></div><p>
+ </p></div></div><div class="chapter" title="Chapter 9. CC1111 USB target device"><div class="titlepage"><div><div><h2 class="title"><a name="idp
73256"></a>Chapter 9. CC1111 USB target device</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#idp74736">1. ao_usb_flush</a></span></dt><dt><span class="section"><a href="#idp75960">2. ao_usb_putchar</a></span></dt><dt><span class="section"><a href="#idp77216">3. ao_usb_pollchar</a></span></dt><dt><span class="section"><a href="#idp3450240">4. ao_usb_getchar</a></span></dt><dt><span class="section"><a href="#idp3451248">5. ao_usb_disable</a></span></dt><dt><span class="section"><a href="#idp3452920">6. ao_usb_enable</a></span></dt><dt><span class="section"><a href="#idp3454056">7. ao_usb_init</a></span></dt></dl></div><p>
The CC1111 contains a full-speed USB target device. 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" title="1. ao_usb_flush"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
1747872"></a>1. ao_usb_flush</h2></div></div></div><pre class="programlisting">
+ </p><div class="section" title="1. ao_usb_flush"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
74736"></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" title="2. ao_usb_putchar"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
2050352"></a>2. ao_usb_putchar</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section" title="2. ao_usb_putchar"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
75960"></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" title="3. ao_usb_pollchar"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
2639304"></a>3. ao_usb_pollchar</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section" title="3. ao_usb_pollchar"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
77216"></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" title="4. ao_usb_getchar"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
533104"></a>4. ao_usb_getchar</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section" title="4. ao_usb_getchar"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
450240"></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" title="5. ao_usb_disable"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
1750296"></a>5. ao_usb_disable</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section" title="5. ao_usb_disable"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
3451248"></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" title="6. ao_usb_enable"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
2101016"></a>6. ao_usb_enable</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section" title="6. ao_usb_enable"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
3452920"></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" title="7. ao_usb_init"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
2678984"></a>7. ao_usb_init</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section" title="7. ao_usb_init"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
3454056"></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" title="Chapter 10. CC1111 Serial peripheral"><div class="titlepage"><div><div><h2 class="title"><a name="idp
2249432"></a>Chapter 10. CC1111 Serial peripheral</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#idp2996672">1. ao_serial_getchar</a></span></dt><dt><span class="section"><a href="#idp3155952">2. ao_serial_putchar</a></span></dt><dt><span class="section"><a href="#idp3350064">3. ao_serial_drain</a></span></dt><dt><span class="section"><a href="#idp2065008">4. ao_serial_set_speed</a></span></dt><dt><span class="section"><a href="#idp2450936">5. ao_serial_init</a></span></dt></dl></div><p>
+ </p></div></div><div class="chapter" title="Chapter 10. CC1111 Serial peripheral"><div class="titlepage"><div><div><h2 class="title"><a name="idp
3455248"></a>Chapter 10. CC1111 Serial peripheral</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#idp3456504">1. ao_serial_getchar</a></span></dt><dt><span class="section"><a href="#idp3457568">2. ao_serial_putchar</a></span></dt><dt><span class="section"><a href="#idp3458624">3. ao_serial_drain</a></span></dt><dt><span class="section"><a href="#idp3459664">4. ao_serial_set_speed</a></span></dt><dt><span class="section"><a href="#idp3460792">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" title="1. ao_serial_getchar"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
2996672"></a>1. ao_serial_getchar</h2></div></div></div><pre class="programlisting">
+ </p><div class="section" title="1. ao_serial_getchar"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
3456504"></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" title="2. ao_serial_putchar"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
155952"></a>2. ao_serial_putchar</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section" title="2. ao_serial_putchar"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
457568"></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" title="3. ao_serial_drain"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
350064"></a>3. ao_serial_drain</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section" title="3. ao_serial_drain"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
458624"></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" title="4. ao_serial_set_speed"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
2065008"></a>4. ao_serial_set_speed</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section" title="4. ao_serial_set_speed"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
3459664"></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" title="5. ao_serial_init"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
2450936"></a>5. ao_serial_init</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section" title="5. ao_serial_init"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
3460792"></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" title="Chapter 11. CC1111 Radio peripheral"><div class="titlepage"><div><div><h2 class="title"><a name="idp
1286080"></a>Chapter 11. CC1111 Radio peripheral</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#idp3302144">1. ao_radio_set_telemetry</a></span></dt><dt><span class="section"><a href="#idp988776">2. ao_radio_set_packet</a></span></dt><dt><span class="section"><a href="#idp3394248">3. ao_radio_set_rdf</a></span></dt><dt><span class="section"><a href="#idp3062848">4. ao_radio_idle</a></span></dt><dt><span class="section"><a href="#idp2490456">5. ao_radio_get</a></span></dt><dt><span class="section"><a href="#idp2147760">6. ao_radio_put</a></span></dt><dt><span class="section"><a href="#idp1214600">7. ao_radio_abort</a></span></dt><dt><span class="section"><a href="#idp1806960">8. ao_radio_send</a></span></dt><dt><span class="section"><a href="#idp3252216">9. ao_radio_recv</a></span></dt><dt><span class="section"><a href="#idp1259776">10. ao_radio_rdf</a></span></dt><dt><span class="section"><a href="#idp2069696">11. ao_packet_putchar</a></span></dt><dt><span class="section"><a href="#idp1536592">12. ao_packet_pollchar</a></span></dt><dt><span class="section"><a href="#idp3165392">13. ao_packet_slave_start</a></span></dt><dt><span class="section"><a href="#idp3384408">14. ao_packet_slave_stop</a></span></dt><dt><span class="section"><a href="#idp2784376">15. ao_packet_slave_init</a></span></dt><dt><span class="section"><a href="#idp2737784">16. ao_packet_master_init</a></span></dt></dl></div><p>
+ </p></div></div><div class="chapter" title="Chapter 11. CC1111 Radio peripheral"><div class="titlepage"><div><div><h2 class="title"><a name="idp
3461952"></a>Chapter 11. CC1111 Radio peripheral</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#idp3466304">1. ao_radio_set_telemetry</a></span></dt><dt><span class="section"><a href="#idp3467552">2. ao_radio_set_packet</a></span></dt><dt><span class="section"><a href="#idp3468800">3. ao_radio_set_rdf</a></span></dt><dt><span class="section"><a href="#idp3470080">4. ao_radio_idle</a></span></dt><dt><span class="section"><a href="#idp3471168">5. ao_radio_get</a></span></dt><dt><span class="section"><a href="#idp3472232">6. ao_radio_put</a></span></dt><dt><span class="section"><a href="#idp3473200">7. ao_radio_abort</a></span></dt><dt><span class="section"><a href="#idp3474720">8. ao_radio_send</a></span></dt><dt><span class="section"><a href="#idp3475976">9. ao_radio_recv</a></span></dt><dt><span class="section"><a href="#idp3477624">10. ao_radio_rdf</a></span></dt><dt><span class="section"><a href="#idp3479128">11. ao_packet_putchar</a></span></dt><dt><span class="section"><a href="#idp3480400">12. ao_packet_pollchar</a></span></dt><dt><span class="section"><a href="#idp3481520">13. ao_packet_slave_start</a></span></dt><dt><span class="section"><a href="#idp3482560">14. ao_packet_slave_stop</a></span></dt><dt><span class="section"><a href="#idp3483568">15. ao_packet_slave_init</a></span></dt><dt><span class="section"><a href="#idp3484688">16. ao_packet_master_init</a></span></dt></dl></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 class="section" title="1. ao_radio_set_telemetry"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
302144"></a>1. ao_radio_set_telemetry</h2></div></div></div><pre class="programlisting">
+ </p><div class="section" title="1. ao_radio_set_telemetry"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
466304"></a>1. 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" title="2. ao_radio_set_packet"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
988776"></a>2. ao_radio_set_packet</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section" title="2. ao_radio_set_packet"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
3467552"></a>2. 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" title="3. ao_radio_set_rdf"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
394248"></a>3. ao_radio_set_rdf</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section" title="3. ao_radio_set_rdf"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
468800"></a>3. 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" title="4. ao_radio_idle"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
062848"></a>4. ao_radio_idle</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section" title="4. ao_radio_idle"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
470080"></a>4. 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" title="5. ao_radio_get"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
2490456"></a>5. ao_radio_get</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section" title="5. ao_radio_get"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
3471168"></a>5. 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" title="6. ao_radio_put"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
2147760"></a>6. ao_radio_put</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section" title="6. ao_radio_put"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
3472232"></a>6. 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" title="7. ao_radio_abort"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
1214600"></a>7. ao_radio_abort</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section" title="7. ao_radio_abort"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
3473200"></a>7. ao_radio_abort</h2></div></div></div><pre class="programlisting">
void
ao_radio_abort(void);
</pre><p>
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" title="8. ao_radio_send"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
1806960"></a>8. ao_radio_send</h2></div></div></div><pre class="programlisting">
+ </p><div class="section" title="8. ao_radio_send"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
3474720"></a>8. ao_radio_send</h2></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" title="9. ao_radio_recv"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
252216"></a>9. ao_radio_recv</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section" title="9. ao_radio_recv"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
475976"></a>9. ao_radio_recv</h2></div></div></div><pre class="programlisting">
void
ao_radio_recv(__xdata struct ao_radio_recv *radio);
</pre><p>
</p></div><p>
In radio direction finding mode, there's just one function to
use
- </p><div class="section" title="10. ao_radio_rdf"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
1259776"></a>10. ao_radio_rdf</h2></div></div></div><pre class="programlisting">
+ </p><div class="section" title="10. ao_radio_rdf"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
3477624"></a>10. ao_radio_rdf</h2></div></div></div><pre class="programlisting">
void
ao_radio_rdf(int ms);
</pre><p>
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" title="11. ao_packet_putchar"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
2069696"></a>11. ao_packet_putchar</h2></div></div></div><pre class="programlisting">
+ </p><div class="section" title="11. ao_packet_putchar"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
3479128"></a>11. ao_packet_putchar</h2></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" title="12. ao_packet_pollchar"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
1536592"></a>12. ao_packet_pollchar</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section" title="12. ao_packet_pollchar"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
3480400"></a>12. ao_packet_pollchar</h2></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" title="13. ao_packet_slave_start"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
165392"></a>13. ao_packet_slave_start</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section" title="13. ao_packet_slave_start"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
481520"></a>13. ao_packet_slave_start</h2></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" title="14. ao_packet_slave_stop"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
384408"></a>14. ao_packet_slave_stop</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section" title="14. ao_packet_slave_stop"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
482560"></a>14. ao_packet_slave_stop</h2></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" title="15. ao_packet_slave_init"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
2784376"></a>15. ao_packet_slave_init</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section" title="15. ao_packet_slave_init"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
3483568"></a>15. ao_packet_slave_init</h2></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" title="16. ao_packet_master_init"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
2737784"></a>16. ao_packet_master_init</h2></div></div></div><pre class="programlisting">
+ </p></div><div class="section" title="16. ao_packet_master_init"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
3484688"></a>16. ao_packet_master_init</h2></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.76.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="book" title="The Altus Metrum System"><div class="titlepage"><div><div><h1 class="title"><a name="idm1
5092880"></a>The Altus Metrum System</h1></div><div><h2 class="subtitle">An Owner's Manual for TeleMetrum, TeleMini and TeleDongle Devices</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 © 2012 Bdale Garbee and Keith Packard</p></div><div><div class="legalnotice" title="Legal Notice"><a name="idp191472"></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.76.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="book" title="The Altus Metrum System"><div class="titlepage"><div><div><h1 class="title"><a name="idm1
4876008"></a>The Altus Metrum System</h1></div><div><h2 class="subtitle">An Owner's Manual for TeleMetrum, TeleMini and TeleDongle Devices</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 © 2012 Bdale Garbee and Keith Packard</p></div><div><div class="legalnotice" title="Legal Notice"><a name="idp127112"></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 border="1" 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">13 September 2012</td></tr><tr><td align="left" colspan="2">
+ </p></div></div><div><div class="revhistory"><table border="1" 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.1</td><td align="left">16 September 2012</td></tr><tr><td align="left" colspan="2">
+ Updated for software version 1.1.1 Version 1.1.1 fixes a few
+ bugs found in version 1.1.
+ </td></tr><tr><td align="left">Revision 1.1</td><td align="left">13 September 2012</td></tr><tr><td align="left" colspan="2">
Updated for software version 1.1. Version 1.1 has new
features but is otherwise compatible with version 1.0.
</td></tr><tr><td align="left">Revision 1.0</td><td align="left">24 August 2011</td></tr><tr><td align="left" colspan="2">
Updated for software version 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="acknowledgements" title="Acknowledgements"><div class="titlepage"><div><div><h2 class="title"><a name="idp108936"></a>Acknowledgements</h2></div></div></div>
+ </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="acknowledgements" title="Acknowledgements"><div class="titlepage"><div><div><h2 class="title"><a name="idp98856"></a>Acknowledgements</h2></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
NAR #88757, TRA #12200<br>
</p></div><p>
</p>
- </div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="#idp1
11040">1. Introduction and Overview</a></span></dt><dt><span class="chapter"><a href="#idp1178312">2. Getting Started</a></span></dt><dt><span class="chapter"><a href="#idp1458272">3. Handling Precautions</a></span></dt><dt><span class="chapter"><a href="#idp2203968">4. Hardware Overview</a></span></dt><dt><span class="chapter"><a href="#idp3576752">5. System Operation</a></span></dt><dd><dl><dt><span class="section"><a href="#idp2648960">1. Firmware Modes </a></span></dt><dt><span class="section"><a href="#idp843848">2. GPS </a></span></dt><dt><span class="section"><a href="#idp1474008">3. Controlling An Altimeter Over The Radio Link</a></span></dt><dt><span class="section"><a href="#idp8640">4. Ground Testing </a></span></dt><dt><span class="section"><a href="#idp53640">5. Radio Link </a></span></dt><dt><span class="section"><a href="#idp13080">6. Configurable Parameters</a></span></dt><dd><dl><dt><span class="section"><a href="#idp54304">6.1. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp55472">6.2. Apogee Delay</a></span></dt><dt><span class="section"><a href="#idp57856">6.3. Main Deployment Altitude</a></span></dt><dt><span class="section"><a href="#idp58968">6.4. Maximum Flight Log</a></span></dt><dt><span class="section"><a href="#idp62744">6.5. Ignite Mode</a></span></dt><dt><span class="section"><a href="#idp64088">6.6. Pad Orientation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#idp65864">6. AltosUI</a></span></dt><dd><dl><dt><span class="section"><a href="#idp66944">1. Monitor Flight</a></span></dt><dd><dl><dt><span class="section"><a href="#idp72832">1.1. Launch Pad</a></span></dt><dt><span class="section"><a href="#idp78800">1.2. Ascent</a></span></dt><dt><span class="section"><a href="#idp80968">1.3. Descent</a></span></dt><dt><span class="section"><a href="#idp84192">1.4. Landed</a></span></dt><dt><span class="section"><a href="#idp3850320">1.5. Site Map</a></span></dt></dl></dd><dt><span class="section"><a href="#idp3852600">2. Save Flight Data</a></span></dt><dt><span class="section"><a href="#idp3855520">3. Replay Flight</a></span></dt><dt><span class="section"><a href="#idp3856768">4. Graph Data</a></span></dt><dt><span class="section"><a href="#idp3859280">5. Export Data</a></span></dt><dd><dl><dt><span class="section"><a href="#idp3860288">5.1. Comma Separated Value Format</a></span></dt><dt><span class="section"><a href="#idp3861864">5.2. Keyhole Markup Language (for Google Earth)</a></span></dt></dl></dd><dt><span class="section"><a href="#idp3862696">6. Configure Altimeter</a></span></dt><dd><dl><dt><span class="section"><a href="#idp3866872">6.1. Main Deploy Altitude</a></span></dt><dt><span class="section"><a href="#idp3867856">6.2. Apogee Delay</a></span></dt><dt><span class="section"><a href="#idp3868896">6.3. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp3869808">6.4. Radio Calibration</a></span></dt><dt><span class="section"><a href="#idp3870872">6.5. Callsign</a></span></dt><dt><span class="section"><a href="#idp3871608">6.6. Maximum Flight Log Size</a></span></dt><dt><span class="section"><a href="#idp3872472">6.7. Ignite Mode</a></span></dt><dt><span class="section"><a href="#idp3875312">6.8. Pad Orientation</a></span></dt></dl></dd><dt><span class="section"><a href="#idp3877536">7. Configure AltosUI</a></span></dt><dd><dl><dt><span class="section"><a href="#idp3878160">7.1. Voice Settings</a></span></dt><dt><span class="section"><a href="#idp3880432">7.2. Log Directory</a></span></dt><dt><span class="section"><a href="#idp3881656">7.3. Callsign</a></span></dt><dt><span class="section"><a href="#idp3882624">7.4. Imperial Units</a></span></dt><dt><span class="section"><a href="#idp3883528">7.5. Font Size</a></span></dt><dt><span class="section"><a href="#idp3884232">7.6. Serial Debug</a></span></dt><dt><span class="section"><a href="#idp3885144">7.7. Manage Frequencies</a></span></dt></dl></dd><dt><span class="section"><a href="#idp3886128">8. Configure Groundstation</a></span></dt><dd><dl><dt><span class="section"><a href="#idp3890048">8.1. Frequency</a></span></dt><dt><span class="section"><a href="#idp3891032">8.2. Radio Calibration</a></span></dt></dl></dd><dt><span class="section"><a href="#idp3892024">9. Flash Image</a></span></dt><dt><span class="section"><a href="#idp3895096">10. Fire Igniter</a></span></dt><dt><span class="section"><a href="#idp3897200">11. Scan Channels</a></span></dt><dt><span class="section"><a href="#idp3898104">12. Load Maps</a></span></dt><dt><span class="section"><a href="#idp3900232">13. Monitor Idle</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp3901104">7. Using Altus Metrum Products</a></span></dt><dd><dl><dt><span class="section"><a href="#idp3901424">1. Being Legal</a></span></dt><dt><span class="section"><a href="#idp3902440">2. In the Rocket</a></span></dt><dt><span class="section"><a href="#idp3904984">3. On the Ground</a></span></dt><dt><span class="section"><a href="#idp3911792">4. Data Analysis</a></span></dt><dt><span class="section"><a href="#idp3913544">5. Future Plans</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp3915584">8. Altimeter Installation Recommendations</a></span></dt><dd><dl><dt><span class="section"><a href="#idp3916568">1. Mounting the Altimeter</a></span></dt><dt><span class="section"><a href="#idp3918904">2. Dealing with the Antenna</a></span></dt><dt><span class="section"><a href="#idp3923232">3. Preserving GPS Reception</a></span></dt><dt><span class="section"><a href="#idp3925616">4. Radio Frequency Interference</a></span></dt><dt><span class="section"><a href="#idp3929344">5. The Barometric Sensor</a></span></dt><dt><span class="section"><a href="#idp3931184">6. Ground Testing</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp3933320">9. Updating Device Firmware</a></span></dt><dd><dl><dt><span class="section"><a href="#idp3935760">1. Updating TeleMetrum Firmware</a></span></dt><dt><span class="section"><a href="#idp3941064">2. Updating TeleMini Firmware</a></span></dt><dt><span class="section"><a href="#idp3946480">3. Updating TeleDongle Firmware</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp3953536">10. Hardware Specifications</a></span></dt><dd><dl><dt><span class="section"><a href="#idp3953856">1. TeleMetrum Specifications</a></span></dt><dt><span class="section"><a href="#idp3959584">2. TeleMini Specifications</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp3964408">11. FAQ</a></span></dt><dt><span class="appendix"><a href="#idp3968152">A. Notes for Older Software</a></span></dt><dt><span class="appendix"><a href="#idp3984384">B. Calibration</a></span></dt><dd><dl><dt><span class="section"><a href="#idp3985360">1. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp3988680">2. TeleMetrum Accelerometer</a></span></dt></dl></dd><dt><span class="appendix"><a href="#idp3993576">C. Release Notes</a></span></dt></dl></div><div class="chapter" title="Chapter 1. Introduction and Overview"><div class="titlepage"><div><div><h2 class="title"><a name="idp111040"></a>Chapter 1. Introduction and Overview</h2></div></div></div><p>
+ </div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="#idp1
00944">1. Introduction and Overview</a></span></dt><dt><span class="chapter"><a href="#idp765272">2. Getting Started</a></span></dt><dt><span class="chapter"><a href="#idp2464288">3. Handling Precautions</a></span></dt><dt><span class="chapter"><a href="#idp2424088">4. Hardware Overview</a></span></dt><dt><span class="chapter"><a href="#idp2180232">5. System Operation</a></span></dt><dd><dl><dt><span class="section"><a href="#idp1125224">1. Firmware Modes </a></span></dt><dt><span class="section"><a href="#idp2147600">2. GPS </a></span></dt><dt><span class="section"><a href="#idp2942696">3. Controlling An Altimeter Over The Radio Link</a></span></dt><dt><span class="section"><a href="#idp2301664">4. Ground Testing </a></span></dt><dt><span class="section"><a href="#idp2250232">5. Radio Link </a></span></dt><dt><span class="section"><a href="#idp2942904">6. Configurable Parameters</a></span></dt><dd><dl><dt><span class="section"><a href="#idp3488592">6.1. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp951896">6.2. Apogee Delay</a></span></dt><dt><span class="section"><a href="#idp2731600">6.3. Main Deployment Altitude</a></span></dt><dt><span class="section"><a href="#idp3129392">6.4. Maximum Flight Log</a></span></dt><dt><span class="section"><a href="#idp2670464">6.5. Ignite Mode</a></span></dt><dt><span class="section"><a href="#idp2903736">6.6. Pad Orientation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#idp3111552">6. AltosUI</a></span></dt><dd><dl><dt><span class="section"><a href="#idp1977952">1. Monitor Flight</a></span></dt><dd><dl><dt><span class="section"><a href="#idp2190152">1.1. Launch Pad</a></span></dt><dt><span class="section"><a href="#idp984840">1.2. Ascent</a></span></dt><dt><span class="section"><a href="#idp2815128">1.3. Descent</a></span></dt><dt><span class="section"><a href="#idp1778752">1.4. Landed</a></span></dt><dt><span class="section"><a href="#idp2529176">1.5. Site Map</a></span></dt></dl></dd><dt><span class="section"><a href="#idp1702472">2. Save Flight Data</a></span></dt><dt><span class="section"><a href="#idp1611424">3. Replay Flight</a></span></dt><dt><span class="section"><a href="#idp2095720">4. Graph Data</a></span></dt><dt><span class="section"><a href="#idp1776584">5. Export Data</a></span></dt><dd><dl><dt><span class="section"><a href="#idp2325688">5.1. Comma Separated Value Format</a></span></dt><dt><span class="section"><a href="#idp2607232">5.2. Keyhole Markup Language (for Google Earth)</a></span></dt></dl></dd><dt><span class="section"><a href="#idp2903528">6. Configure Altimeter</a></span></dt><dd><dl><dt><span class="section"><a href="#idp2459720">6.1. Main Deploy Altitude</a></span></dt><dt><span class="section"><a href="#idp1773368">6.2. Apogee Delay</a></span></dt><dt><span class="section"><a href="#idp3135080">6.3. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp2214616">6.4. Radio Calibration</a></span></dt><dt><span class="section"><a href="#idp2100744">6.5. Callsign</a></span></dt><dt><span class="section"><a href="#idp3049840">6.6. Maximum Flight Log Size</a></span></dt><dt><span class="section"><a href="#idp2695760">6.7. Ignite Mode</a></span></dt><dt><span class="section"><a href="#idp2751336">6.8. Pad Orientation</a></span></dt></dl></dd><dt><span class="section"><a href="#idp2353688">7. Configure AltosUI</a></span></dt><dd><dl><dt><span class="section"><a href="#idp3404600">7.1. Voice Settings</a></span></dt><dt><span class="section"><a href="#idp2310768">7.2. Log Directory</a></span></dt><dt><span class="section"><a href="#idp1596232">7.3. Callsign</a></span></dt><dt><span class="section"><a href="#idp2062808">7.4. Imperial Units</a></span></dt><dt><span class="section"><a href="#idp2195968">7.5. Font Size</a></span></dt><dt><span class="section"><a href="#idp1445032">7.6. Serial Debug</a></span></dt><dt><span class="section"><a href="#idp2086440">7.7. Manage Frequencies</a></span></dt></dl></dd><dt><span class="section"><a href="#idp2372272">8. Configure Groundstation</a></span></dt><dd><dl><dt><span class="section"><a href="#idp2225688">8.1. Frequency</a></span></dt><dt><span class="section"><a href="#idp1993736">8.2. Radio Calibration</a></span></dt></dl></dd><dt><span class="section"><a href="#idp3457272">9. Flash Image</a></span></dt><dt><span class="section"><a href="#idp3527432">10. Fire Igniter</a></span></dt><dt><span class="section"><a href="#idp3529536">11. Scan Channels</a></span></dt><dt><span class="section"><a href="#idp3530440">12. Load Maps</a></span></dt><dt><span class="section"><a href="#idp3532568">13. Monitor Idle</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp3533440">7. Using Altus Metrum Products</a></span></dt><dd><dl><dt><span class="section"><a href="#idp3533760">1. Being Legal</a></span></dt><dt><span class="section"><a href="#idp3534720">2. In the Rocket</a></span></dt><dt><span class="section"><a href="#idp3536872">3. On the Ground</a></span></dt><dt><span class="section"><a href="#idp3543680">4. Data Analysis</a></span></dt><dt><span class="section"><a href="#idp3545432">5. Future Plans</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp3547472">8. Altimeter Installation Recommendations</a></span></dt><dd><dl><dt><span class="section"><a href="#idp3548456">1. Mounting the Altimeter</a></span></dt><dt><span class="section"><a href="#idp3550792">2. Dealing with the Antenna</a></span></dt><dt><span class="section"><a href="#idp3554776">3. Preserving GPS Reception</a></span></dt><dt><span class="section"><a href="#idp3557160">4. Radio Frequency Interference</a></span></dt><dt><span class="section"><a href="#idp3561200">5. The Barometric Sensor</a></span></dt><dt><span class="section"><a href="#idp3563040">6. Ground Testing</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp3565176">9. Updating Device Firmware</a></span></dt><dd><dl><dt><span class="section"><a href="#idp3567176">1. Updating TeleMetrum Firmware</a></span></dt><dt><span class="section"><a href="#idp3572480">2. Updating TeleMini Firmware</a></span></dt><dt><span class="section"><a href="#idp3578376">3. Updating TeleDongle Firmware</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp3585824">10. Hardware Specifications</a></span></dt><dd><dl><dt><span class="section"><a href="#idp3586144">1. TeleMetrum Specifications</a></span></dt><dt><span class="section"><a href="#idp3591872">2. TeleMini Specifications</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp3596696">11. FAQ</a></span></dt><dt><span class="appendix"><a href="#idp3600440">A. Notes for Older Software</a></span></dt><dt><span class="appendix"><a href="#idp3616576">B. Calibration</a></span></dt><dd><dl><dt><span class="section"><a href="#idp3617552">1. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp3620872">2. TeleMetrum Accelerometer</a></span></dt></dl></dd><dt><span class="appendix"><a href="#idp3624920">C. Release Notes</a></span></dt></dl></div><div class="chapter" title="Chapter 1. Introduction and Overview"><div class="titlepage"><div><div><h2 class="title"><a name="idp100944"></a>Chapter 1. Introduction and Overview</h2></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" title="Chapter 2. Getting Started"><div class="titlepage"><div><div><h2 class="title"><a name="idp
1178312"></a>Chapter 2. Getting Started</h2></div></div></div><p>
+ </p></div><div class="chapter" title="Chapter 2. Getting Started"><div class="titlepage"><div><div><h2 class="title"><a name="idp
765272"></a>Chapter 2. Getting Started</h2></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>
Full source code and build instructions are also available.
The latest version may always be downloaded from
<a class="ulink" href="http://altusmetrum.org/AltOS" target="_top">http://altusmetrum.org/AltOS</a>.
- </p></div><div class="chapter" title="Chapter 3. Handling Precautions"><div class="titlepage"><div><div><h2 class="title"><a name="idp
1458272"></a>Chapter 3. Handling Precautions</h2></div></div></div><p>
+ </p></div><div class="chapter" title="Chapter 3. Handling Precautions"><div class="titlepage"><div><div><h2 class="title"><a name="idp
2464288"></a>Chapter 3. Handling Precautions</h2></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" title="Chapter 4. Hardware Overview"><div class="titlepage"><div><div><h2 class="title"><a name="idp2
203968"></a>Chapter 4. Hardware Overview</h2></div></div></div><p>
+ </p></div><div class="chapter" title="Chapter 4. Hardware Overview"><div class="titlepage"><div><div><h2 class="title"><a name="idp2
424088"></a>Chapter 4. Hardware Overview</h2></div></div></div><p>
TeleMetrum is a 1 inch by 2.75 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
connection, and, on TeleMetrum, you can unplug the integrated GPS
antenna and select an appropriate off-board GPS antenna with
cable terminating in a U.FL connector.
- </p></div><div class="chapter" title="Chapter 5. System Operation"><div class="titlepage"><div><div><h2 class="title"><a name="idp
3576752"></a>Chapter 5. System Operation</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#idp2648960">1. Firmware Modes </a></span></dt><dt><span class="section"><a href="#idp843848">2. GPS </a></span></dt><dt><span class="section"><a href="#idp1474008">3. Controlling An Altimeter Over The Radio Link</a></span></dt><dt><span class="section"><a href="#idp8640">4. Ground Testing </a></span></dt><dt><span class="section"><a href="#idp53640">5. Radio Link </a></span></dt><dt><span class="section"><a href="#idp13080">6. Configurable Parameters</a></span></dt><dd><dl><dt><span class="section"><a href="#idp54304">6.1. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp55472">6.2. Apogee Delay</a></span></dt><dt><span class="section"><a href="#idp57856">6.3. Main Deployment Altitude</a></span></dt><dt><span class="section"><a href="#idp58968">6.4. Maximum Flight Log</a></span></dt><dt><span class="section"><a href="#idp62744">6.5. Ignite Mode</a></span></dt><dt><span class="section"><a href="#idp64088">6.6. Pad Orientation</a></span></dt></dl></dd></dl></div><div class="section" title="1. Firmware Modes"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp2648960"></a>1. Firmware Modes </h2></div></div></div><p>
+ </p></div><div class="chapter" title="Chapter 5. System Operation"><div class="titlepage"><div><div><h2 class="title"><a name="idp
2180232"></a>Chapter 5. System Operation</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#idp1125224">1. Firmware Modes </a></span></dt><dt><span class="section"><a href="#idp2147600">2. GPS </a></span></dt><dt><span class="section"><a href="#idp2942696">3. Controlling An Altimeter Over The Radio Link</a></span></dt><dt><span class="section"><a href="#idp2301664">4. Ground Testing </a></span></dt><dt><span class="section"><a href="#idp2250232">5. Radio Link </a></span></dt><dt><span class="section"><a href="#idp2942904">6. Configurable Parameters</a></span></dt><dd><dl><dt><span class="section"><a href="#idp3488592">6.1. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp951896">6.2. Apogee Delay</a></span></dt><dt><span class="section"><a href="#idp2731600">6.3. Main Deployment Altitude</a></span></dt><dt><span class="section"><a href="#idp3129392">6.4. Maximum Flight Log</a></span></dt><dt><span class="section"><a href="#idp2670464">6.5. Ignite Mode</a></span></dt><dt><span class="section"><a href="#idp2903736">6.6. Pad Orientation</a></span></dt></dl></dd></dl></div><div class="section" title="1. Firmware Modes"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp1125224"></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
step of a rickety step-ladder or hanging off the side of a launch
tower with a screw-driver trying to turn on your avionics before
installing igniters!
- </p></div><div class="section" title="2. GPS"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
843848"></a>2. GPS </h2></div></div></div><p>
+ </p></div><div class="section" title="2. GPS"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
2147600"></a>2. GPS </h2></div></div></div><p>
TeleMetrum includes 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 TeleMetrum GPS receiver needs to lock onto at least
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" title="3. Controlling An Altimeter Over The Radio Link"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
1474008"></a>3. Controlling An Altimeter Over The Radio Link</h2></div></div></div><p>
+ </p></div><div class="section" title="3. Controlling An Altimeter Over The Radio Link"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
2942696"></a>3. Controlling An Altimeter Over The Radio Link</h2></div></div></div><p>
One of the unique features of the Altus Metrum system is
the ability to create a two way command link between TeleDongle
and an altimeter using the digital radio transceivers built into
lights on the devices. The red LED will flash each time a packet
is tramsitted, 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" title="4. Ground Testing"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
8640"></a>4. Ground Testing </h2></div></div></div><p>
+ </p></div><div class="section" title="4. Ground Testing"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
2301664"></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" title="5. Radio Link"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
53640"></a>5. Radio Link </h2></div></div></div><p>
+ </p></div><div class="section" title="5. Radio Link"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
2250232"></a>5. Radio Link </h2></div></div></div><p>
The chip our boards are based on incorporates 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
with a 5-element yagi on the ground. We hope to fly boards to higher
altitudes over time, and would of course appreciate customer feedback
on performance in higher altitude flights!
- </p></div><div class="section" title="6. Configurable Parameters"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
13080"></a>6. Configurable Parameters</h2></div></div></div><p>
+ </p></div><div class="section" title="6. Configurable Parameters"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
2942904"></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 board, 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" title="6.1. Radio Frequency"><div class="titlepage"><div><div><h3 class="title"><a name="idp
54304"></a>6.1. Radio Frequency</h3></div></div></div><p>
+ </p><div class="section" title="6.1. Radio Frequency"><div class="titlepage"><div><div><h3 class="title"><a name="idp
3488592"></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" title="6.2. Apogee Delay"><div class="titlepage"><div><div><h3 class="title"><a name="idp
55472"></a>6.2. Apogee Delay</h3></div></div></div><p>
+ </p></div><div class="section" title="6.2. Apogee Delay"><div class="titlepage"><div><div><h3 class="title"><a name="idp
951896"></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" title="6.3. Main Deployment Altitude"><div class="titlepage"><div><div><h3 class="title"><a name="idp
57856"></a>6.3. Main Deployment Altitude</h3></div></div></div><p>
+ </p></div><div class="section" title="6.3. Main Deployment Altitude"><div class="titlepage"><div><div><h3 class="title"><a name="idp
2731600"></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" title="6.4. Maximum Flight Log"><div class="titlepage"><div><div><h3 class="title"><a name="idp
58968"></a>6.4. Maximum Flight Log</h3></div></div></div><p>
+ </p></div><div class="section" title="6.4. Maximum Flight Log"><div class="titlepage"><div><div><h3 class="title"><a name="idp
3129392"></a>6.4. Maximum Flight Log</h3></div></div></div><p>
TeleMetrum version 1.1 and 1.2 have 2MB of on-board flash storage,
enough to hold over 40 minutes of data at full data rate
(100 samples/second). TeleMetrum 1.0 has 1MB of on-board
the limited storage, TeleMini cannot hold data for more than
one flight, and so must be erased after each flight or it
will not capture data for subsequent flights.
- </p></div><div class="section" title="6.5. Ignite Mode"><div class="titlepage"><div><div><h3 class="title"><a name="idp
62744"></a>6.5. Ignite Mode</h3></div></div></div><p>
+ </p></div><div class="section" title="6.5. Ignite Mode"><div class="titlepage"><div><div><h3 class="title"><a name="idp
2670464"></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" title="6.6. Pad Orientation"><div class="titlepage"><div><div><h3 class="title"><a name="idp
64088"></a>6.6. Pad Orientation</h3></div></div></div><p>
+ </p></div><div class="section" title="6.6. Pad Orientation"><div class="titlepage"><div><div><h3 class="title"><a name="idp
2903736"></a>6.6. Pad Orientation</h3></div></div></div><p>
TeleMetrum measures acceleration along the axis of the
board. Which way the board is oriented affects the sign of
the acceleration value. Instead of trying to guess which way
TeleMetrum 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></div><div class="chapter" title="Chapter 6. AltosUI"><div class="titlepage"><div><div><h2 class="title"><a name="idp
65864"></a>Chapter 6. AltosUI</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#idp66944">1. Monitor Flight</a></span></dt><dd><dl><dt><span class="section"><a href="#idp72832">1.1. Launch Pad</a></span></dt><dt><span class="section"><a href="#idp78800">1.2. Ascent</a></span></dt><dt><span class="section"><a href="#idp80968">1.3. Descent</a></span></dt><dt><span class="section"><a href="#idp84192">1.4. Landed</a></span></dt><dt><span class="section"><a href="#idp3850320">1.5. Site Map</a></span></dt></dl></dd><dt><span class="section"><a href="#idp3852600">2. Save Flight Data</a></span></dt><dt><span class="section"><a href="#idp3855520">3. Replay Flight</a></span></dt><dt><span class="section"><a href="#idp3856768">4. Graph Data</a></span></dt><dt><span class="section"><a href="#idp3859280">5. Export Data</a></span></dt><dd><dl><dt><span class="section"><a href="#idp3860288">5.1. Comma Separated Value Format</a></span></dt><dt><span class="section"><a href="#idp3861864">5.2. Keyhole Markup Language (for Google Earth)</a></span></dt></dl></dd><dt><span class="section"><a href="#idp3862696">6. Configure Altimeter</a></span></dt><dd><dl><dt><span class="section"><a href="#idp3866872">6.1. Main Deploy Altitude</a></span></dt><dt><span class="section"><a href="#idp3867856">6.2. Apogee Delay</a></span></dt><dt><span class="section"><a href="#idp3868896">6.3. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp3869808">6.4. Radio Calibration</a></span></dt><dt><span class="section"><a href="#idp3870872">6.5. Callsign</a></span></dt><dt><span class="section"><a href="#idp3871608">6.6. Maximum Flight Log Size</a></span></dt><dt><span class="section"><a href="#idp3872472">6.7. Ignite Mode</a></span></dt><dt><span class="section"><a href="#idp3875312">6.8. Pad Orientation</a></span></dt></dl></dd><dt><span class="section"><a href="#idp3877536">7. Configure AltosUI</a></span></dt><dd><dl><dt><span class="section"><a href="#idp3878160">7.1. Voice Settings</a></span></dt><dt><span class="section"><a href="#idp3880432">7.2. Log Directory</a></span></dt><dt><span class="section"><a href="#idp3881656">7.3. Callsign</a></span></dt><dt><span class="section"><a href="#idp3882624">7.4. Imperial Units</a></span></dt><dt><span class="section"><a href="#idp3883528">7.5. Font Size</a></span></dt><dt><span class="section"><a href="#idp3884232">7.6. Serial Debug</a></span></dt><dt><span class="section"><a href="#idp3885144">7.7. Manage Frequencies</a></span></dt></dl></dd><dt><span class="section"><a href="#idp3886128">8. Configure Groundstation</a></span></dt><dd><dl><dt><span class="section"><a href="#idp3890048">8.1. Frequency</a></span></dt><dt><span class="section"><a href="#idp3891032">8.2. Radio Calibration</a></span></dt></dl></dd><dt><span class="section"><a href="#idp3892024">9. Flash Image</a></span></dt><dt><span class="section"><a href="#idp3895096">10. Fire Igniter</a></span></dt><dt><span class="section"><a href="#idp3897200">11. Scan Channels</a></span></dt><dt><span class="section"><a href="#idp3898104">12. Load Maps</a></span></dt><dt><span class="section"><a href="#idp3900232">13. Monitor Idle</a></span></dt></dl></div><p>
+ </p></div></div></div><div class="chapter" title="Chapter 6. AltosUI"><div class="titlepage"><div><div><h2 class="title"><a name="idp
3111552"></a>Chapter 6. AltosUI</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#idp1977952">1. Monitor Flight</a></span></dt><dd><dl><dt><span class="section"><a href="#idp2190152">1.1. Launch Pad</a></span></dt><dt><span class="section"><a href="#idp984840">1.2. Ascent</a></span></dt><dt><span class="section"><a href="#idp2815128">1.3. Descent</a></span></dt><dt><span class="section"><a href="#idp1778752">1.4. Landed</a></span></dt><dt><span class="section"><a href="#idp2529176">1.5. Site Map</a></span></dt></dl></dd><dt><span class="section"><a href="#idp1702472">2. Save Flight Data</a></span></dt><dt><span class="section"><a href="#idp1611424">3. Replay Flight</a></span></dt><dt><span class="section"><a href="#idp2095720">4. Graph Data</a></span></dt><dt><span class="section"><a href="#idp1776584">5. Export Data</a></span></dt><dd><dl><dt><span class="section"><a href="#idp2325688">5.1. Comma Separated Value Format</a></span></dt><dt><span class="section"><a href="#idp2607232">5.2. Keyhole Markup Language (for Google Earth)</a></span></dt></dl></dd><dt><span class="section"><a href="#idp2903528">6. Configure Altimeter</a></span></dt><dd><dl><dt><span class="section"><a href="#idp2459720">6.1. Main Deploy Altitude</a></span></dt><dt><span class="section"><a href="#idp1773368">6.2. Apogee Delay</a></span></dt><dt><span class="section"><a href="#idp3135080">6.3. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp2214616">6.4. Radio Calibration</a></span></dt><dt><span class="section"><a href="#idp2100744">6.5. Callsign</a></span></dt><dt><span class="section"><a href="#idp3049840">6.6. Maximum Flight Log Size</a></span></dt><dt><span class="section"><a href="#idp2695760">6.7. Ignite Mode</a></span></dt><dt><span class="section"><a href="#idp2751336">6.8. Pad Orientation</a></span></dt></dl></dd><dt><span class="section"><a href="#idp2353688">7. Configure AltosUI</a></span></dt><dd><dl><dt><span class="section"><a href="#idp3404600">7.1. Voice Settings</a></span></dt><dt><span class="section"><a href="#idp2310768">7.2. Log Directory</a></span></dt><dt><span class="section"><a href="#idp1596232">7.3. Callsign</a></span></dt><dt><span class="section"><a href="#idp2062808">7.4. Imperial Units</a></span></dt><dt><span class="section"><a href="#idp2195968">7.5. Font Size</a></span></dt><dt><span class="section"><a href="#idp1445032">7.6. Serial Debug</a></span></dt><dt><span class="section"><a href="#idp2086440">7.7. Manage Frequencies</a></span></dt></dl></dd><dt><span class="section"><a href="#idp2372272">8. Configure Groundstation</a></span></dt><dd><dl><dt><span class="section"><a href="#idp2225688">8.1. Frequency</a></span></dt><dt><span class="section"><a href="#idp1993736">8.2. Radio Calibration</a></span></dt></dl></dd><dt><span class="section"><a href="#idp3457272">9. Flash Image</a></span></dt><dt><span class="section"><a href="#idp3527432">10. Fire Igniter</a></span></dt><dt><span class="section"><a href="#idp3529536">11. Scan Channels</a></span></dt><dt><span class="section"><a href="#idp3530440">12. Load Maps</a></span></dt><dt><span class="section"><a href="#idp3532568">13. Monitor Idle</a></span></dt></dl></div><p>
The AltosUI program provides a graphical user interface for
interacting with the Altus Metrum product family, including
TeleMetrum, TeleMini and TeleDongle. AltosUI can monitor telemetry data,
buttons, one for each major activity in the system. This manual
is split into chapters, each of which documents one of the tasks
provided from the top-level toolbar.
- </p><div class="section" title="1. Monitor Flight"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
66944"></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" title="1. Monitor Flight"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
1977952"></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
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" title="1.1. Launch Pad"><div class="titlepage"><div><div><h3 class="title"><a name="idp
72832"></a>1.1. Launch Pad</h3></div></div></div><p>
+ </p><div class="section" title="1.1. Launch Pad"><div class="titlepage"><div><div><h3 class="title"><a name="idp
2190152"></a>1.1. Launch 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
and altitude, averaging many reported positions to improve the
accuracy of the fix.
</p><p>
- </p></div><div class="section" title="1.2. Ascent"><div class="titlepage"><div><div><h3 class="title"><a name="idp
78800"></a>1.2. Ascent</h3></div></div></div><p>
+ </p></div><div class="section" title="1.2. Ascent"><div class="titlepage"><div><div><h3 class="title"><a name="idp
984840"></a>1.2. Ascent</h3></div></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.
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" title="1.3. Descent"><div class="titlepage"><div><div><h3 class="title"><a name="idp
80968"></a>1.3. Descent</h3></div></div></div><p>
+ </p></div><div class="section" title="1.3. Descent"><div class="titlepage"><div><div><h3 class="title"><a name="idp
2815128"></a>1.3. Descent</h3></div></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,
components, but generally range from 15-30m/s on drogue and should
be below 10m/s when under the main parachute in a dual-deploy flight.
</p><p>
- For TeleMetrum altimeters, you can locate the rocket in the sky
- using the elevation and
- bearing information to figure out where to look. Elevation is
- in degrees above the horizon. Bearing is reported in degrees
- relative to true north. Range can help figure out how big the
- rocket will appear. Note that all of these values are relative
- to the pad location. If the elevation is near 90°, the rocket
- is over the pad, not over you.
+ For TeleMetrum altimeters, you can locate the rocket in the
+ sky using the elevation and bearing information to figure
+ out where to look. Elevation is in degrees above the
+ horizon. Bearing is reported in degrees relative to true
+ north. Range can help figure out how big the rocket will
+ appear. Ground Distance shows how far it is to a point
+ directly under the rocket and can help figure out where the
+ rocket is likely to land. Note that all of these values are
+ relative to the pad location. If the elevation is near 90°,
+ the rocket is over the pad, not over you.
</p><p>
Finally, the igniter voltages are reported in this tab as
well, both to monitor the main charge as well as to see what
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" title="1.4. Landed"><div class="titlepage"><div><div><h3 class="title"><a name="idp
84192"></a>1.4. Landed</h3></div></div></div><p>
+ </p></div><div class="section" title="1.4. Landed"><div class="titlepage"><div><div><h3 class="title"><a name="idp
1778752"></a>1.4. Landed</h3></div></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" title="1.5. Site Map"><div class="titlepage"><div><div><h3 class="title"><a name="idp
3850320"></a>1.5. Site Map</h3></div></div></div><p>
+ </p></div><div class="section" title="1.5. Site Map"><div class="titlepage"><div><div><h3 class="title"><a name="idp
2529176"></a>1.5. Site Map</h3></div></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" title="2. Save Flight Data"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
3852600"></a>2. Save Flight Data</h2></div></div></div><p>
+ </p></div></div><div class="section" title="2. Save Flight Data"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
1702472"></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" title="3. Replay Flight"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
3855520"></a>3. Replay Flight</h2></div></div></div><p>
+ </p></div><div class="section" title="3. Replay Flight"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
1611424"></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" title="4. Graph Data"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
3856768"></a>4. Graph Data</h2></div></div></div><p>
+ </p></div><div class="section" title="4. Graph Data"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
2095720"></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
Note that telemetry files will generally produce poor graphs
due to the lower sampling rate and missed telemetry packets.
Use saved flight data in .eeprom files for graphing where possible.
- </p></div><div class="section" title="5. Export Data"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
3859280"></a>5. Export Data</h2></div></div></div><p>
+ </p></div><div class="section" title="5. Export Data"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
1776584"></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). 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" title="5.1. Comma Separated Value Format"><div class="titlepage"><div><div><h3 class="title"><a name="idp
3860288"></a>5.1. Comma Separated Value Format</h3></div></div></div><p>
+ </p><div class="section" title="5.1. Comma Separated Value Format"><div class="titlepage"><div><div><h3 class="title"><a name="idp
2325688"></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" title="5.2. Keyhole Markup Language (for Google Earth)"><div class="titlepage"><div><div><h3 class="title"><a name="idp
3861864"></a>5.2. Keyhole Markup Language (for Google Earth)</h3></div></div></div><p>
+ </p></div><div class="section" title="5.2. Keyhole Markup Language (for Google Earth)"><div class="titlepage"><div><div><h3 class="title"><a name="idp
2607232"></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" title="6. Configure Altimeter"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
3862696"></a>6. Configure Altimeter</h2></div></div></div><p>
+ </p></div></div><div class="section" title="6. Configure Altimeter"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
2903528"></a>6. Configure Altimeter</h2></div></div></div><p>
Select this button and then select either a TeleMetrum or
TeleDongle Device from the list provided. Selecting a TeleDongle
device will use the radio link to configure a remote altimeter.
lost.
</p></li></ul></div><p>
The rest of the dialog contains the parameters to be configured.
- </p><div class="section" title="6.1. Main Deploy Altitude"><div class="titlepage"><div><div><h3 class="title"><a name="idp
3866872"></a>6.1. Main Deploy Altitude</h3></div></div></div><p>
+ </p><div class="section" title="6.1. Main Deploy Altitude"><div class="titlepage"><div><div><h3 class="title"><a name="idp
2459720"></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" title="6.2. Apogee Delay"><div class="titlepage"><div><div><h3 class="title"><a name="idp
3867856"></a>6.2. Apogee Delay</h3></div></div></div><p>
+ </p></div><div class="section" title="6.2. Apogee Delay"><div class="titlepage"><div><div><h3 class="title"><a name="idp
1773368"></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" title="6.3. Radio Frequency"><div class="titlepage"><div><div><h3 class="title"><a name="idp3
868896"></a>6.3. Radio Frequency</h3></div></div></div><p>
+ </p></div><div class="section" title="6.3. Radio Frequency"><div class="titlepage"><div><div><h3 class="title"><a name="idp3
135080"></a>6.3. Radio Frequency</h3></div></div></div><p>
This configures which of the configured frequencies to use for both
telemetry and packet command mode. Note that if you set this
value via packet command mode, you will have to reconfigure
the TeleDongle frequency before you will be able to use packet
command mode again.
- </p></div><div class="section" title="6.4. Radio Calibration"><div class="titlepage"><div><div><h3 class="title"><a name="idp
3869808"></a>6.4. Radio Calibration</h3></div></div></div><p>
+ </p></div><div class="section" title="6.4. Radio Calibration"><div class="titlepage"><div><div><h3 class="title"><a name="idp
2214616"></a>6.4. 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. 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" title="6.5. Callsign"><div class="titlepage"><div><div><h3 class="title"><a name="idp
3870872"></a>6.5. Callsign</h3></div></div></div><p>
+ </p></div><div class="section" title="6.5. Callsign"><div class="titlepage"><div><div><h3 class="title"><a name="idp
2100744"></a>6.5. 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" title="6.6. Maximum Flight Log Size"><div class="titlepage"><div><div><h3 class="title"><a name="idp3
871608"></a>6.6. Maximum Flight Log Size</h3></div></div></div><p>
+ </p></div><div class="section" title="6.6. Maximum Flight Log Size"><div class="titlepage"><div><div><h3 class="title"><a name="idp3
049840"></a>6.6. 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" title="6.7. Ignite Mode"><div class="titlepage"><div><div><h3 class="title"><a name="idp
3872472"></a>6.7. Ignite Mode</h3></div></div></div><p>
+ </p></div><div class="section" title="6.7. Ignite Mode"><div class="titlepage"><div><div><h3 class="title"><a name="idp
2695760"></a>6.7. 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></li></ul></div></div><div class="section" title="6.8. Pad Orientation"><div class="titlepage"><div><div><h3 class="title"><a name="idp
3875312"></a>6.8. Pad Orientation</h3></div></div></div><p>
+ </p></li></ul></div></div><div class="section" title="6.8. Pad Orientation"><div class="titlepage"><div><div><h3 class="title"><a name="idp
2751336"></a>6.8. Pad Orientation</h3></div></div></div><p>
Because it includes an accelerometer, TeleMetrum is
sensitive to the orientation of the board. By default, it
expects the antenna end to point forward. This parameter
Antenna Down. In this mode, the antenna end of the
TeleMetrum board must point aft, in line with the
expected flight path.
- </p></li></ul></div></div></div><div class="section" title="7. Configure AltosUI"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
3877536"></a>7. Configure AltosUI</h2></div></div></div><p>
+ </p></li></ul></div></div></div><div class="section" title="7. Configure AltosUI"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
2353688"></a>7. Configure AltosUI</h2></div></div></div><p>
This button presents a dialog so that you can configure the AltosUI global settings.
- </p><div class="section" title="7.1. Voice Settings"><div class="titlepage"><div><div><h3 class="title"><a name="idp3
878160"></a>7.1. Voice Settings</h3></div></div></div><p>
+ </p><div class="section" title="7.1. Voice Settings"><div class="titlepage"><div><div><h3 class="title"><a name="idp3
404600"></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
Test Voice—Plays a short message allowing you to verify
that the audio system is working and the volume settings
are reasonable
- </p></li></ul></div></div><div class="section" title="7.2. Log Directory"><div class="titlepage"><div><div><h3 class="title"><a name="idp
3880432"></a>7.2. Log Directory</h3></div></div></div><p>
+ </p></li></ul></div></div><div class="section" title="7.2. Log Directory"><div class="titlepage"><div><div><h3 class="title"><a name="idp
2310768"></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" title="7.3. Callsign"><div class="titlepage"><div><div><h3 class="title"><a name="idp
3881656"></a>7.3. Callsign</h3></div></div></div><p>
+ </p></div><div class="section" title="7.3. Callsign"><div class="titlepage"><div><div><h3 class="title"><a name="idp
1596232"></a>7.3. Callsign</h3></div></div></div><p>
This value is transmitted in each command packet sent from
TeleDongle and received from an altimeter. It is not used in
telemetry mode, as the callsign configured in the altimeter board
is included in all telemetry packets. Configure this
with the AltosUI operators call sign as needed to comply with
your local radio regulations.
- </p></div><div class="section" title="7.4. Imperial Units"><div class="titlepage"><div><div><h3 class="title"><a name="idp
3882624"></a>7.4. Imperial Units</h3></div></div></div><p>
+ </p></div><div class="section" title="7.4. Imperial Units"><div class="titlepage"><div><div><h3 class="title"><a name="idp
2062808"></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, 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" title="7.5. Font Size"><div class="titlepage"><div><div><h3 class="title"><a name="idp
3883528"></a>7.5. Font Size</h3></div></div></div><p>
+ </p></div><div class="section" title="7.5. Font Size"><div class="titlepage"><div><div><h3 class="title"><a name="idp
2195968"></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" title="7.6. Serial Debug"><div class="titlepage"><div><div><h3 class="title"><a name="idp
3884232"></a>7.6. Serial Debug</h3></div></div></div><p>
+ </p></div><div class="section" title="7.6. Serial Debug"><div class="titlepage"><div><div><h3 class="title"><a name="idp
1445032"></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" title="7.7. Manage Frequencies"><div class="titlepage"><div><div><h3 class="title"><a name="idp
3885144"></a>7.7. Manage Frequencies</h3></div></div></div><p>
+ </p></div><div class="section" title="7.7. Manage Frequencies"><div class="titlepage"><div><div><h3 class="title"><a name="idp
2086440"></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" title="8. Configure Groundstation"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
3886128"></a>8. Configure Groundstation</h2></div></div></div><p>
+ </p></div></div><div class="section" title="8. Configure Groundstation"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp
2372272"></a>8. Configure Groundstation</h2></div></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></li></ul></div><p>
The rest of the dialog contains the parameters to be configured.
- </p><div class="section" title="8.1. Frequency"><div class="titlepage"><div><div><h3 class="title"><a name="idp
3890048"></a>8.1. Frequency</h3></div></div></div><p>
+ </p><div class="section" title="8.1. Frequency"><div class="titlepage"><div><div><h3 class="title"><a name="idp
2225688"></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" title="8.2. Radio Calibration"><div class="titlepage"><div><div><h3 class="title"><a name="idp
3891032"></a>8.2. Radio Calibration</h3></div></div></div><p>
+ </p></div><div class="section" title="8.2. Radio Calibration"><div class="titlepage"><div><div><h3 class="title"><a name="idp
1993736"></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" title="9. Flash Image"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
892024"></a>9. Flash Image</h2></div></div></div><p>
+ </p></div></div><div class="section" title="9. Flash Image"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
457272"></a>9. Flash Image</h2></div></div></div><p>
This reprograms any Altus Metrum device by using a TeleMetrum
or TeleDongle as a programming dongle. Please read the
directions for flashing devices in the Updating Device
will have to unplug it and then plug it back in for the USB
connection to reset so that you can communicate with the device
again.
- </p></div><div class="section" title="10. Fire Igniter"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
895096"></a>10. Fire Igniter</h2></div></div></div><p>
+ </p></div><div class="section" title="10. Fire Igniter"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
527432"></a>10. Fire Igniter</h2></div></div></div><p>
This activates the igniter circuits in TeleMetrum to help test
recovery systems deployment. Because this command can operate
over the Packet Command Link, you can prepare the rocket as
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" title="11. Scan Channels"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
897200"></a>11. Scan Channels</h2></div></div></div><p>
+ </p></div><div class="section" title="11. Scan Channels"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
529536"></a>11. Scan Channels</h2></div></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" title="12. Load Maps"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
898104"></a>12. Load Maps</h2></div></div></div><p>
+ </p></div><div class="section" title="12. Load Maps"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
530440"></a>12. Load Maps</h2></div></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" title="13. Monitor Idle"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
900232"></a>13. Monitor Idle</h2></div></div></div><p>
+ </p></div><div class="section" title="13. Monitor Idle"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
532568"></a>13. Monitor Idle</h2></div></div></div><p>
This brings up a dialog similar to the Monitor Flight UI,
except it works with the altimeter in "idle" mode by sending
query commands to discover the current state rather than
listening for telemetry packets.
- </p></div></div><div class="chapter" title="Chapter 7. Using Altus Metrum Products"><div class="titlepage"><div><div><h2 class="title"><a name="idp3
901104"></a>Chapter 7. Using Altus Metrum Products</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#idp3901424">1. Being Legal</a></span></dt><dt><span class="section"><a href="#idp3902440">2. In the Rocket</a></span></dt><dt><span class="section"><a href="#idp3904984">3. On the Ground</a></span></dt><dt><span class="section"><a href="#idp3911792">4. Data Analysis</a></span></dt><dt><span class="section"><a href="#idp3913544">5. Future Plans</a></span></dt></dl></div><div class="section" title="1. Being Legal"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3901424"></a>1. Being Legal</h2></div></div></div><p>
+ </p></div></div><div class="chapter" title="Chapter 7. Using Altus Metrum Products"><div class="titlepage"><div><div><h2 class="title"><a name="idp3
533440"></a>Chapter 7. Using Altus Metrum Products</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#idp3533760">1. Being Legal</a></span></dt><dt><span class="section"><a href="#idp3534720">2. In the Rocket</a></span></dt><dt><span class="section"><a href="#idp3536872">3. On the Ground</a></span></dt><dt><span class="section"><a href="#idp3543680">4. Data Analysis</a></span></dt><dt><span class="section"><a href="#idp3545432">5. Future Plans</a></span></dt></dl></div><div class="section" title="1. Being Legal"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3533760"></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" title="2. In the Rocket"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
902440"></a>2. In the Rocket</h2></div></div></div><p>
+ </p></div><div class="section" title="2. In the Rocket"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
534720"></a>2. In the Rocket</h2></div></div></div><p>
In the rocket itself, you just need a <a class="ulink" href="http://www.altusmetrum.org/TeleMetrum/" target="_top">TeleMetrum</a> or
<a class="ulink" href="http://www.altusmetrum.org/TeleMini/" target="_top">TeleMini</a> board and
a single-cell, 3.7 volt nominal Li-Po rechargeable battery. An
which is opaque to RF signals, you may choose to have an SMA connector
installed so that you can run a coaxial cable to an antenna mounted
elsewhere in the rocket.
- </p></div><div class="section" title="3. On the Ground"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
904984"></a>3. On the Ground</h2></div></div></div><p>
+ </p></div><div class="section" title="3. On the Ground"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
536872"></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. The
TeleDongle in turn plugs directly into the USB port on a notebook
</a>
The 440-3 and 440-5 are both good choices for finding a
TeleMetrum- or TeleMini- equipped rocket when used with a suitable 70cm HT.
- </p></div><div class="section" title="4. Data Analysis"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
911792"></a>4. Data Analysis</h2></div></div></div><p>
+ </p></div><div class="section" title="4. Data Analysis"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
543680"></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" title="5. Future Plans"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
913544"></a>5. Future Plans</h2></div></div></div><p>
+ </p></div><div class="section" title="5. Future Plans"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
545432"></a>5. Future Plans</h2></div></div></div><p>
In the future, we intend to offer "companion boards" for the rocket that will
plug in to TeleMetrum to collect additional data, provide more pyro channels,
and so forth.
if you have some great idea for an addition to the current Altus Metrum family,
feel free to dive in and help! Or let us know what you'd like to see that
we aren't already working on, and maybe we'll get excited about it too...
- </p></div></div><div class="chapter" title="Chapter 8. Altimeter Installation Recommendations"><div class="titlepage"><div><div><h2 class="title"><a name="idp3
915584"></a>Chapter 8. Altimeter Installation Recommendations</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#idp3916568">1. Mounting the Altimeter</a></span></dt><dt><span class="section"><a href="#idp3918904">2. Dealing with the Antenna</a></span></dt><dt><span class="section"><a href="#idp3923232">3. Preserving GPS Reception</a></span></dt><dt><span class="section"><a href="#idp3925616">4. Radio Frequency Interference</a></span></dt><dt><span class="section"><a href="#idp3929344">5. The Barometric Sensor</a></span></dt><dt><span class="section"><a href="#idp3931184">6. Ground Testing</a></span></dt></dl></div><p>
+ </p></div></div><div class="chapter" title="Chapter 8. Altimeter Installation Recommendations"><div class="titlepage"><div><div><h2 class="title"><a name="idp3
547472"></a>Chapter 8. Altimeter Installation Recommendations</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#idp3548456">1. Mounting the Altimeter</a></span></dt><dt><span class="section"><a href="#idp3550792">2. Dealing with the Antenna</a></span></dt><dt><span class="section"><a href="#idp3554776">3. Preserving GPS Reception</a></span></dt><dt><span class="section"><a href="#idp3557160">4. Radio Frequency Interference</a></span></dt><dt><span class="section"><a href="#idp3561200">5. The Barometric Sensor</a></span></dt><dt><span class="section"><a href="#idp3563040">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 oftentimes you find few perfect solutions. This chapter
contains some suggestions about how to install Altus Metrum
products into the rocket air-frame, including how to safely and
reliably mix a variety of electronics into the same air-frame.
- </p><div class="section" title="1. Mounting the Altimeter"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
916568"></a>1. Mounting the Altimeter</h2></div></div></div><p>
+ </p><div class="section" title="1. Mounting the Altimeter"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
548456"></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 TeleMetrum, we use
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.
- </li></ol></div></div><div class="section" title="2. Dealing with the Antenna"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
918904"></a>2. Dealing with the Antenna</h2></div></div></div><p>
+ </li></ol></div></div><div class="section" title="2. Dealing with the Antenna"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
550792"></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" title="3. Preserving GPS Reception"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
923232"></a>3. Preserving GPS Reception</h2></div></div></div><p>
+ </p></div><div class="section" title="3. Preserving GPS Reception"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
554776"></a>3. Preserving GPS Reception</h2></div></div></div><p>
The GPS antenna and receiver in TeleMetrum are 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.
</li></ol></div><p>
- </p></div><div class="section" title="4. Radio Frequency Interference"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
925616"></a>4. Radio Frequency Interference</h2></div></div></div><p>
+ </p></div><div class="section" title="4. Radio Frequency Interference"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
557160"></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 1/4
of the wavelength (17.5cm).
- </li></ul></div></div><div class="section" title="5. The Barometric Sensor"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
929344"></a>5. The Barometric Sensor</h2></div></div></div><p>
+ </li></ul></div></div><div class="section" title="5. The Barometric Sensor"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
561200"></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
chemical damage from the products of APCP or BP combustion, so
make sure the ebay is carefully sealed from any compartment
which contains ejection charges or motors.
- </p></div><div class="section" title="6. Ground Testing"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
931184"></a>6. Ground Testing</h2></div></div></div><p>
+ </p></div><div class="section" title="6. Ground Testing"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
563040"></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" title="Chapter 9. Updating Device Firmware"><div class="titlepage"><div><div><h2 class="title"><a name="idp3
933320"></a>Chapter 9. Updating Device Firmware</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#idp3935760">1. Updating TeleMetrum Firmware</a></span></dt><dt><span class="section"><a href="#idp3941064">2. Updating TeleMini Firmware</a></span></dt><dt><span class="section"><a href="#idp3946480">3. Updating TeleDongle Firmware</a></span></dt></dl></div><p>
+ </p></div></div><div class="chapter" title="Chapter 9. Updating Device Firmware"><div class="titlepage"><div><div><h2 class="title"><a name="idp3
565176"></a>Chapter 9. Updating Device Firmware</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#idp3567176">1. Updating TeleMetrum Firmware</a></span></dt><dt><span class="section"><a href="#idp3572480">2. Updating TeleMini Firmware</a></span></dt><dt><span class="section"><a href="#idp3578376">3. Updating TeleDongle Firmware</a></span></dt></dl></div><p>
The big concept to understand is that you have to use a
TeleDongle as a programmer to update a TeleMetrum or TeleMini,
and a TeleMetrum or other TeleDongle to program the TeleDongle
version from <a class="ulink" href="http://www.altusmetrum.org/AltOS/" target="_top">http://www.altusmetrum.org/AltOS/</a>.
</p><p>
We recommend updating the altimeter first, before updating TeleDongle.
- </p><div class="section" title="1. Updating TeleMetrum Firmware"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
935760"></a>1. Updating TeleMetrum Firmware</h2></div></div></div><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
+ </p><div class="section" title="1. Updating TeleMetrum Firmware"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
567176"></a>1. Updating TeleMetrum Firmware</h2></div></div></div><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
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.
</li><li class="listitem">
If something goes wrong, give it another try.
- </li></ol></div></div><div class="section" title="2. Updating TeleMini Firmware"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
941064"></a>2. Updating TeleMini Firmware</h2></div></div></div><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
+ </li></ol></div></div><div class="section" title="2. Updating TeleMini Firmware"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
572480"></a>2. Updating TeleMini Firmware</h2></div></div></div><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
You'll need a special 'programming cable' to reprogram the
TeleMini. It's available on the Altus Metrum web store, or
you can make your own using an 8-pin MicroMaTch connector on
letting it come up in "flight" mode and listening for telemetry.
</li><li class="listitem">
If something goes wrong, give it another try.
- </li></ol></div></div><div class="section" title="3. Updating TeleDongle Firmware"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
946480"></a>3. Updating TeleDongle Firmware</h2></div></div></div><p>
+ </li></ol></div></div><div class="section" title="3. Updating TeleDongle Firmware"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
578376"></a>3. 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">
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" title="Chapter 10. Hardware Specifications"><div class="titlepage"><div><div><h2 class="title"><a name="idp3
953536"></a>Chapter 10. Hardware Specifications</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#idp3953856">1. TeleMetrum Specifications</a></span></dt><dt><span class="section"><a href="#idp3959584">2. TeleMini Specifications</a></span></dt></dl></div><div class="section" title="1. TeleMetrum Specifications"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3953856"></a>1. TeleMetrum Specifications</h2></div></div></div><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>
+ </p></div></div><div class="chapter" title="Chapter 10. Hardware Specifications"><div class="titlepage"><div><div><h2 class="title"><a name="idp3
585824"></a>Chapter 10. Hardware Specifications</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#idp3586144">1. TeleMetrum Specifications</a></span></dt><dt><span class="section"><a href="#idp3591872">2. TeleMini Specifications</a></span></dt></dl></div><div class="section" title="1. TeleMetrum Specifications"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3586144"></a>1. TeleMetrum Specifications</h2></div></div></div><div class="itemizedlist"><ul class="itemizedlist" 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" title="2. TeleMini Specifications"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
959584"></a>2. TeleMini Specifications</h2></div></div></div><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>
+ </p></li></ul></div></div><div class="section" title="2. TeleMini Specifications"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
591872"></a>2. TeleMini Specifications</h2></div></div></div><div class="itemizedlist"><ul class="itemizedlist" 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>
1.5 x .5 inch board designed to fit inside 18mm air-frame coupler tube.
- </p></li></ul></div></div></div><div class="chapter" title="Chapter 11. FAQ"><div class="titlepage"><div><div><h2 class="title"><a name="idp3
964408"></a>Chapter 11. FAQ</h2></div></div></div><p>
+ </p></li></ul></div></div></div><div class="chapter" title="Chapter 11. FAQ"><div class="titlepage"><div><div><h2 class="title"><a name="idp3
596696"></a>Chapter 11. FAQ</h2></div></div></div><p>
TeleMetrum seems to shut off when disconnected from the
computer. Make sure the battery is adequately charged. Remember the
unit will pull more power than the USB port can deliver before 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" title="Appendix A. Notes for Older Software"><div class="titlepage"><div><div><h2 class="title"><a name="idp3
968152"></a>Appendix A. Notes for Older Software</h2></div></div></div><p>
+ </p></div><div class="appendix" title="Appendix A. Notes for Older Software"><div class="titlepage"><div><div><h2 class="title"><a name="idp3
600440"></a>Appendix A. Notes for Older Software</h2></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
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" title="Appendix B. Calibration"><div class="titlepage"><div><div><h2 class="title"><a name="idp3
984384"></a>Appendix B. Calibration</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#idp3985360">1. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp3988680">2. TeleMetrum Accelerometer</a></span></dt></dl></div><p>
+ </p></div><div class="appendix" title="Appendix B. Calibration"><div class="titlepage"><div><div><h2 class="title"><a name="idp3
616576"></a>Appendix B. Calibration</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#idp3617552">1. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp3620872">2. TeleMetrum Accelerometer</a></span></dt></dl></div><p>
There are only two calibrations required for a TeleMetrum board, and
only one for TeleDongle and TeleMini. All boards are shipped from
the factory pre-calibrated, but the procedures are documented here
AltosUI, you must connect to the board with a serial terminal program
and interact directly with the on-board command interpreter to effect
calibration.
- </p><div class="section" title="1. Radio Frequency"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
985360"></a>1. Radio Frequency</h2></div></div></div><p>
+ </p><div class="section" title="1. Radio Frequency"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
617552"></a>1. Radio Frequency</h2></div></div></div><p>
The radio frequency is synthesized from a clock based on the 48 MHz
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" title="2. TeleMetrum Accelerometer"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
988680"></a>2. TeleMetrum Accelerometer</h2></div></div></div><p>
+ </p></div><div class="section" title="2. TeleMetrum Accelerometer"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3
620872"></a>2. TeleMetrum Accelerometer</h2></div></div></div><p>
The TeleMetrum accelerometer we use has its own 5 volt power
supply and
the output must be passed through a resistive voltage divider to match
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" title="Appendix C. Release Notes"><div class="titlepage"><div><div><h2 class="title"><a name="idp3993576"></a>Appendix C. Release Notes</h2></div></div></div><p>
+ </p></div></div><div class="appendix" title="Appendix C. Release Notes"><div class="titlepage"><div><div><h2 class="title"><a name="idp3624920"></a>Appendix C. Release Notes</h2></div></div></div><p>
+ Version 1.1.1 is a bug-fix release. It fixes a couple of bugs in
+ AltosUI and one firmware bug that affects TeleMetrum version 1.0
+ boards. Thanks to Bob Brown for help diagnosing the Google Earth
+ file export issue, and for suggesting the addition of the Ground
+ Distance value in the Descent tab.
+ </p><p>
+ AltOS Firmware Changes
+ </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">
+ TeleMetrum v1.0 boards use the AT45DB081D flash memory part to
+ store flight data, which is different from later TeleMetrum
+ boards. The AltOS v1.1 driver for this chip couldn't erase
+ memory, leaving it impossible to delete flight data or update
+ configuration values. This bug doesn't affect newer TeleMetrum
+ boards, and it doesn't affect the safety of rockets flying
+ version 1.1 firmware.
+ </li></ul></div><p>
+ </p><p>
+ AltosUI Changes
+ </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">
+ Creating a Google Earth file (KML) from on-board flight data
+ (EEPROM) would generate an empty file. The code responsible
+ for reading the EEPROM file wasn't ever setting the GPS valid
+ bits, and so the KML export code thought there was no GPS data
+ in the file.
+ </li><li class="listitem">
+ The “Landed” tab was displaying all values in metric units,
+ even when AltosUI was configured to display imperial
+ units. Somehow I just missed this tab when doing the units stuff.
+ </li><li class="listitem">
+ The “Descent” tab displays the range to the rocket, which is a
+ combination of the over-the-ground distance to the rockets
+ current latitude/longitude and the height of the rocket. As
+ such, it's useful for knowing how far away the rocket is, but
+ difficult to use when estimating where the rocket might
+ eventually land. A new “Ground Distance” field has been added
+ which displays the distance to a spot right underneath the
+ rocket.
+ </li><li class="listitem">
+ Sensor data wasn't being displayed for TeleMini flight
+ computers in Monitor Idle mode, including things like battery
+ voltage. The code that picked which kinds of data to fetch
+ from the flight computer was missing a check for TeleMini when
+ deciding whether to fetch the analog sensor data.
+ </li></ul></div><p>
+ </p><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>
projects / web / altusmetrum / commitdiff