1 <?xml version="1.0" encoding="utf-8"?>
2 <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
3 "/usr/share/xml/docbook/schema/dtd/4.5/docbookx.dtd">
5 <title>The Altus Metrum System</title>
6 <subtitle>An Owner's Manual for Altus Metrum Rocketry Electronics</subtitle>
9 <firstname>Bdale</firstname>
10 <surname>Garbee</surname>
13 <firstname>Keith</firstname>
14 <surname>Packard</surname>
17 <firstname>Bob</firstname>
18 <surname>Finch</surname>
21 <firstname>Anthony</firstname>
22 <surname>Towns</surname>
26 <holder>Bdale Garbee and Keith Packard</holder>
30 This document is released under the terms of the
31 <ulink url="http://creativecommons.org/licenses/by-sa/3.0/">
32 Creative Commons ShareAlike 3.0
39 <revnumber>1.3</revnumber>
40 <date>12 November 2013</date>
42 Updated for software version 1.3. Version 1.3 adds support
43 for TeleMega, TeleMetrum v2.0, TeleMini v2.0 and EasyMini
44 and fixes bugs in AltosUI and the AltOS firmware.
48 <revnumber>1.2.1</revnumber>
49 <date>21 May 2013</date>
51 Updated for software version 1.2. Version 1.2 adds support
52 for TeleBT and AltosDroid. It also adds a few minor features
53 and fixes bugs in AltosUI and the AltOS firmware.
57 <revnumber>1.2</revnumber>
58 <date>18 April 2013</date>
60 Updated for software version 1.2. Version 1.2 adds support
61 for MicroPeak and the MicroPeak USB interface.
65 <revnumber>1.1.1</revnumber>
66 <date>16 September 2012</date>
68 Updated for software version 1.1.1 Version 1.1.1 fixes a few
69 bugs found in version 1.1.
73 <revnumber>1.1</revnumber>
74 <date>13 September 2012</date>
76 Updated for software version 1.1. Version 1.1 has new
77 features but is otherwise compatible with version 1.0.
81 <revnumber>1.0</revnumber>
82 <date>24 August 2011</date>
84 Updated for software version 1.0. Note that 1.0 represents a
85 telemetry format change, meaning both ends of a link
86 (TeleMetrum/TeleMini and TeleDongle) must be updated or
87 communications will fail.
91 <revnumber>0.9</revnumber>
92 <date>18 January 2011</date>
94 Updated for software version 0.9. Note that 0.9 represents a
95 telemetry format change, meaning both ends of a link (TeleMetrum and
96 TeleDongle) must be updated or communications will fail.
100 <revnumber>0.8</revnumber>
101 <date>24 November 2010</date>
102 <revremark>Updated for software version 0.8 </revremark>
107 <title>Acknowledgments</title>
109 Thanks to Bob Finch, W9YA, NAR 12965, TRA 12350 for writing “The
110 Mere-Mortals Quick Start/Usage Guide to the Altus Metrum Starter
111 Kit” which formed the basis of the original Getting Started chapter
112 in this manual. Bob was one of our first customers for a production
113 TeleMetrum, and his continued enthusiasm and contributions
114 are immensely gratifying and highly appreciated!
117 And thanks to Anthony (AJ) Towns for major contributions including
118 the AltosUI graphing and site map code and associated documentation.
119 Free software means that our customers and friends can become our
120 collaborators, and we certainly appreciate this level of
124 Have fun using these products, and we hope to meet all of you
125 out on the rocket flight line somewhere.
128 NAR #87103, TRA #12201
130 Keith Packard, KD7SQG
131 NAR #88757, TRA #12200
136 <title>Introduction and Overview</title>
138 Welcome to the Altus Metrum community! Our circuits and software reflect
139 our passion for both hobby rocketry and Free Software. We hope their
140 capabilities and performance will delight you in every way, but by
141 releasing all of our hardware and software designs under open licenses,
142 we also hope to empower you to take as active a role in our collective
146 The first device created for our community was TeleMetrum, a dual
147 deploy altimeter with fully integrated GPS and radio telemetry
148 as standard features, and a “companion interface” that will
149 support optional capabilities in the future. The latest version
150 of TeleMetrum, v2.0, has all of the same features but with
151 improved sensors and radio to offer increased performance.
154 Our second device was TeleMini, a dual deploy altimeter with
155 radio telemetry and radio direction finding. The first version
156 of this device was only 13mm by 38mm (½ inch by 1½ inches) and
157 could fit easily in an 18mm air-frame. The latest version, v2.0,
158 includes a beeper, USB data download and extended on-board
159 flight logging, along with an improved barometric sensor.
162 TeleMega is our most sophisticated device, including six pyro
163 channels (four of which are fully programmable), integrated GPS,
164 integrated gyroscopes for staging/air-start inhibit and high
165 performance telemetry.
168 EasyMini is a dual-deploy altimeter with logging and built-in
172 TeleDongle was our first ground station, providing a USB to RF
173 interfaces for communicating with the altimeters. Combined with
174 your choice of antenna and notebook computer, TeleDongle and our
175 associated user interface software form a complete ground
176 station capable of logging and displaying in-flight telemetry,
177 aiding rocket recovery, then processing and archiving flight
178 data for analysis and review.
181 For a slightly more portable ground station experience that also
182 provides direct rocket recovery support, TeleBT offers flight
183 monitoring and data logging using a Bluetooth connection between
184 the receiver and an Android device that has the Altos Droid
185 application installed from the Google Play store.
188 More products will be added to the Altus Metrum family over time, and
189 we currently envision that this will be a single, comprehensive manual
190 for the entire product family.
194 <title>Getting Started</title>
196 The first thing to do after you check the inventory of parts in your
197 “starter kit” is to charge the battery.
200 For TeleMetrum and TeleMega, the battery can be charged by plugging it into the
201 corresponding socket of the device and then using the USB
202 cable to plug the flight computer into your computer's USB socket. The
203 on-board circuitry will charge the battery whenever it is plugged
204 in, because the on-off switch does NOT control the
208 On TeleMetrum v1 boards, when the GPS chip is initially
209 searching for satellites, TeleMetrum will consume more current
210 than it can pull from the USB port, so the battery must be
211 attached in order to get satellite lock. Once GPS is locked,
212 the current consumption goes back down enough to enable charging
213 while running. So it's a good idea to fully charge the battery
214 as your first item of business so there is no issue getting and
215 maintaining satellite lock. The yellow charge indicator led
216 will go out when the battery is nearly full and the charger goes
217 to trickle charge. It can take several hours to fully recharge a
218 deeply discharged battery.
221 TeleMetrum v2.0 and TeleMega use a higher power battery charger,
222 allowing them to charge the battery while running the board at
223 maximum power. When the battery is charging, or when the board
224 is consuming a lot of power, the red LED will be lit. When the
225 battery is fully charged, the green LED will be lit. When the
226 battery is damaged or missing, both LEDs will be lit, which
230 The Lithium Polymer TeleMini and EasyMini battery can be charged by
231 disconnecting it from the board and plugging it into a
232 standalone battery charger such as the LipoCharger product
233 included in TeleMini Starter Kits, and connecting that via a USB
234 cable to a laptop or other USB power source.
237 You can also choose to use another battery with TeleMini v2.0
238 and EasyMini, anything supplying between 4 and 12 volts should
239 work fine (like a standard 9V battery), but if you are planning
240 to fire pyro charges, ground testing is required to verify that
241 the battery supplies enough current.
244 The other active device in the starter kit is the TeleDongle USB to
245 RF interface. If you plug it in to your Mac or Linux computer it should
246 “just work”, showing up as a serial port device. Windows systems need
247 driver information that is part of the AltOS download to know that the
248 existing USB modem driver will work. We therefore recommend installing
249 our software before plugging in TeleDongle if you are using a Windows
250 computer. If you are using Linux and are having problems, try moving
251 to a fresher kernel (2.6.33 or newer), as the USB serial driver had
252 ugly bugs in some earlier versions.
255 Next you should obtain and install the AltOS software. These
256 include the AltosUI ground station program, current firmware
257 images for all of the hardware, and a number of standalone
258 utilities that are rarely needed. Pre-built binary packages are
259 available for Linux, Microsoft Windows, and recent MacOSX
260 versions. Full source code and build instructions are also
261 available. The latest version may always be downloaded from
262 <ulink url="http://altusmetrum.org/AltOS"/>.
265 If you're using a TeleBT instead of the TeleDongle, you'll want
266 to go install the Altos Droid application from the Google Play
267 store. You don't need a data plan to use Altos Droid, but
268 without network access, the Map view will be less useful as it
269 won't contain any map data. You can also use TeleBT connected
270 over USB with your laptop computer; it acts exactly like a
271 TeleDongle. Anywhere this manual talks about TeleDongle, you can
272 also read that as 'and TeleBT when connected via USB'.
276 <title>Handling Precautions</title>
278 All Altus Metrum products are sophisticated electronic devices.
279 When handled gently and properly installed in an air-frame, they
280 will deliver impressive results. However, as with all electronic
281 devices, there are some precautions you must take.
284 The Lithium Polymer rechargeable batteries have an
285 extraordinary power density. This is great because we can fly with
286 much less battery mass than if we used alkaline batteries or previous
287 generation rechargeable batteries... but if they are punctured
288 or their leads are allowed to short, they can and will release their
290 Thus we recommend that you take some care when handling our batteries
291 and consider giving them some extra protection in your air-frame. We
292 often wrap them in suitable scraps of closed-cell packing foam before
293 strapping them down, for example.
296 The barometric sensors used on all of our flight computers are
297 sensitive to sunlight. In normal mounting situations, the baro sensor
298 and all of the other surface mount components
299 are “down” towards whatever the underlying mounting surface is, so
300 this is not normally a problem. Please consider this, though, when
301 designing an installation, for example, in an air-frame with a
302 see-through plastic payload bay. It is particularly important to
303 consider this with TeleMini v1.0, both because the baro sensor is on the
304 “top” of the board, and because many model rockets with payload bays
305 use clear plastic for the payload bay! Replacing these with an opaque
306 cardboard tube, painting them, or wrapping them with a layer of masking
307 tape are all reasonable approaches to keep the sensor out of direct
311 The barometric sensor sampling port must be able to “breathe”,
312 both by not being covered by foam or tape or other materials that might
313 directly block the hole on the top of the sensor, and also by having a
314 suitable static vent to outside air.
317 As with all other rocketry electronics, Altus Metrum altimeters must
318 be protected from exposure to corrosive motor exhaust and ejection
323 <title>Altus Metrum Hardware</title>
325 <title>Overview</title>
327 Here's the full set of Altus Metrum products, both in
328 production and retired.
331 <title>Altus Metrum Electronics</title>
332 <tgroup cols='8' align='center' colsep='1' rowsep='1'>
333 <colspec align='center' colwidth='*' colname='Device'/>
334 <colspec align='center' colwidth='*' colname='Barometer'/>
335 <colspec align='center' colwidth='*' colname='Z-axis accelerometer'/>
336 <colspec align='center' colwidth='*' colname='GPS'/>
337 <colspec align='center' colwidth='*' colname='3D sensors'/>
338 <colspec align='center' colwidth='*' colname='Storage'/>
339 <colspec align='center' colwidth='*' colname='RF'/>
340 <colspec align='center' colwidth='*' colname='Battery'/>
343 <entry align='center'>Device</entry>
344 <entry align='center'>Barometer</entry>
345 <entry align='center'>Z-axis accelerometer</entry>
346 <entry align='center'>GPS</entry>
347 <entry align='center'>3D sensors</entry>
348 <entry align='center'>Storage</entry>
349 <entry align='center'>RF Output</entry>
350 <entry align='center'>Battery</entry>
355 <entry>TeleMetrum v1.0</entry>
356 <entry><para>MP3H6115 10km (33k')</para></entry>
357 <entry><para>MMA2202 50g</para></entry>
358 <entry>SkyTraq</entry>
365 <entry>TeleMetrum v1.1</entry>
366 <entry><para>MP3H6115 10km (33k')</para></entry>
367 <entry><para>MMA2202 50g</para></entry>
368 <entry>SkyTraq</entry>
375 <entry>TeleMetrum v1.2</entry>
376 <entry><para>MP3H6115 10km (33k')</para></entry>
377 <entry><para>ADXL78 70g</para></entry>
378 <entry>SkyTraq</entry>
385 <entry>TeleMetrum v2.0</entry>
386 <entry><para>MS5607 30km (100k')</para></entry>
387 <entry><para>MMA6555 102g</para></entry>
388 <entry>uBlox Max-7Q</entry>
395 <entry><para>TeleMini <?linebreak?>v1.0</para></entry>
396 <entry><para>MP3H6115 10km (33k')</para></entry>
405 <entry>TeleMini <?linebreak?>v2.0</entry>
406 <entry><para>MS5607 30km (100k')</para></entry>
412 <entry>3.7-12V</entry>
415 <entry>EasyMini <?linebreak?>v1.0</entry>
416 <entry><para>MS5607 30km (100k')</para></entry>
422 <entry>3.7-12V</entry>
425 <entry>TeleMega <?linebreak?>v1.0</entry>
426 <entry><para>MS5607 30km (100k')</para></entry>
427 <entry><para>MMA6555 102g</para></entry>
428 <entry>uBlox Max-7Q</entry>
429 <entry><para>MPU6000 HMC5883</para></entry>
438 <title>Altus Metrum Boards</title>
439 <tgroup cols='6' align='center' colsep='1' rowsep='1'>
440 <colspec align='center' colwidth='*' colname='Device'/>
441 <colspec align='center' colwidth='*' colname='Connectors'/>
442 <colspec align='center' colwidth='*' colname='Screw Terminals'/>
443 <colspec align='center' colwidth='*' colname='Width'/>
444 <colspec align='center' colwidth='*' colname='Length'/>
445 <colspec align='center' colwidth='*' colname='Tube Size'/>
448 <entry align='center'>Device</entry>
449 <entry align='center'>Connectors</entry>
450 <entry align='center'>Screw Terminals</entry>
451 <entry align='center'>Width</entry>
452 <entry align='center'>Length</entry>
453 <entry align='center'>Tube Size</entry>
458 <entry>TeleMetrum</entry>
462 Companion<?linebreak?>
466 <entry><para>Apogee pyro <?linebreak?>Main pyro <?linebreak?>Switch</para></entry>
467 <entry>1 inch (2.54cm)</entry>
468 <entry>2 ¾ inch (6.99cm)</entry>
469 <entry>29mm coupler</entry>
472 <entry><para>TeleMini <?linebreak?>v1.0</para></entry>
479 Apogee pyro <?linebreak?>
482 <entry>½ inch (1.27cm)</entry>
483 <entry>1½ inch (3.81cm)</entry>
484 <entry>18mm airframe</entry>
487 <entry>TeleMini <?linebreak?>v2.0</entry>
495 Apogee pyro <?linebreak?>
496 Main pyro <?linebreak?>
497 Battery <?linebreak?>
500 <entry>0.8 inch (2.03cm)</entry>
501 <entry>1½ inch (3.81cm)</entry>
502 <entry>24mm coupler</entry>
505 <entry>EasyMini</entry>
512 Apogee pyro <?linebreak?>
513 Main pyro <?linebreak?>
514 Battery <?linebreak?>
517 <entry>0.8 inch (2.03cm)</entry>
518 <entry>1½ inch (3.81cm)</entry>
519 <entry>24mm coupler</entry>
522 <entry>TeleMega</entry>
526 Companion<?linebreak?>
531 Apogee pyro <?linebreak?>
532 Main pyro<?linebreak?>
533 Pyro A-D<?linebreak?>
537 <entry>1¼ inch (3.18cm)</entry>
538 <entry>3¼ inch (8.26cm)</entry>
539 <entry>38mm coupler</entry>
546 <title>TeleMetrum</title>
548 TeleMetrum is a 1 inch by 2¾ inch circuit board. It was designed to
549 fit inside coupler for 29mm air-frame tubing, but using it in a tube that
550 small in diameter may require some creativity in mounting and wiring
551 to succeed! The presence of an accelerometer means TeleMetrum should
552 be aligned along the flight axis of the airframe, and by default the ¼
553 wave UHF wire antenna should be on the nose-cone end of the board. The
554 antenna wire is about 7 inches long, and wiring for a power switch and
555 the e-matches for apogee and main ejection charges depart from the
556 fin can end of the board, meaning an ideal “simple” avionics
557 bay for TeleMetrum should have at least 10 inches of interior length.
561 <title>TeleMini</title>
563 TeleMini v1.0 is ½ inches by 1½ inches. It was
564 designed to fit inside an 18mm air-frame tube, but using it in
565 a tube that small in diameter may require some creativity in
566 mounting and wiring to succeed! Since there is no
567 accelerometer, TeleMini can be mounted in any convenient
568 orientation. The default ¼ wave UHF wire antenna attached to
569 the center of one end of the board is about 7 inches long. Two
570 wires for the power switch are connected to holes in the
571 middle of the board. Screw terminals for the e-matches for
572 apogee and main ejection charges depart from the other end of
573 the board, meaning an ideal “simple” avionics bay for TeleMini
574 should have at least 9 inches of interior length.
577 TeleMini v2.0 is 0.8 inches by 1½ inches. It adds more
578 on-board data logging memory, a built-in USB connector and
579 screw terminals for the battery and power switch. The larger
580 board fits in a 24mm coupler. There's also a battery connector
581 for a LiPo battery if you want to use one of those.
585 <title>EasyMini</title>
587 EasyMini is built on a 0.8 inch by 1½ inch circuit board. It's
588 designed to fit in a 24mm coupler tube. The connectors and
589 screw terminals match TeleMini, so you can swap an EasyMini
594 <title>TeleMega</title>
596 TeleMega is a 1¼ inch by 3¼ inch circuit board. It was
597 designed to easily fit in a 38mm coupler. Like TeleMetrum,
598 TeleMega has an accelerometer and so it must be mounted so that
599 the board is aligned with the flight axis. It can be mounted
600 either antenna up or down.
604 <title>Flight Data Recording</title>
606 Each flight computer logs data at 100 samples per second
607 during ascent and 10 samples per second during descent, except
608 for TeleMini v1.0, which records ascent at 10 samples per
609 second and descent at 1 sample per second. Data are logged to
610 an on-board flash memory part, which can be partitioned into
611 several equal-sized blocks, one for each flight.
614 <title>Data Storage on Altus Metrum altimeters</title>
615 <tgroup cols='4' align='center' colsep='1' rowsep='1'>
616 <colspec align='center' colwidth='*' colname='Device'/>
617 <colspec align='center' colwidth='*' colname='Bytes per sample'/>
618 <colspec align='center' colwidth='*' colname='Total storage'/>
619 <colspec align='center' colwidth='*' colname='Minutes of
623 <entry align='center'>Device</entry>
624 <entry align='center'>Bytes per Sample</entry>
625 <entry align='center'>Total Storage</entry>
626 <entry align='center'>Minutes at Full Rate</entry>
631 <entry>TeleMetrum v1.0</entry>
637 <entry>TeleMetrum v1.1 v1.2</entry>
643 <entry>TeleMetrum v2.0</entry>
649 <entry>TeleMini v1.0</entry>
655 <entry>TeleMini v2.0</entry>
661 <entry>EasyMini</entry>
667 <entry>TeleMega</entry>
676 The on-board flash is partitioned into separate flight logs,
677 each of a fixed maximum size. Increase the maximum size of
678 each log and you reduce the number of flights that can be
679 stored. Decrease the size and you can store more flights.
682 Configuration data is also stored in the flash memory on
683 TeleMetrum v1.x, TeleMini and EasyMini. This consumes 64kB
684 of flash space. This configuration space is not available
685 for storing flight log data. TeleMetrum v2.0 and TeleMega
686 store configuration data in a bit of eeprom available within
687 the processor chip, leaving that space available in flash for
691 To compute the amount of space needed for a single flight, you
692 can multiply the expected ascent time (in seconds) by 100
693 times bytes-per-sample, multiply the expected descent time (in
694 seconds) by 10 times the bytes per sample and add the two
695 together. That will slightly under-estimate the storage (in
696 bytes) needed for the flight. For instance, a TeleMetrum v2.0 flight spending
697 20 seconds in ascent and 150 seconds in descent will take
698 about (20 * 1600) + (150 * 160) = 56000 bytes of storage. You
699 could store dozens of these flights in the on-board flash.
702 The default size allows for several flights on each flight
703 computer, except for TeleMini v1.0, which only holds data for a
704 single flight. You can adjust the size.
707 Altus Metrum flight computers will not overwrite existing
708 flight data, so be sure to download flight data and erase it
709 from the flight computer before it fills up. The flight
710 computer will still successfully control the flight even if it
711 cannot log data, so the only thing you will lose is the data.
715 <title>Installation</title>
717 A typical installation involves attaching
718 only a suitable battery, a single pole switch for
719 power on/off, and two pairs of wires connecting e-matches for the
720 apogee and main ejection charges. All Altus Metrum products are
721 designed for use with single-cell batteries with 3.7 volts
722 nominal. TeleMini v2.0 and EasyMini may also be used with other
723 batteries as long as they supply between 4 and 12 volts.
726 The battery connectors are a standard 2-pin JST connector and
727 match batteries sold by Spark Fun. These batteries are
728 single-cell Lithium Polymer batteries that nominally provide 3.7
729 volts. Other vendors sell similar batteries for RC aircraft
730 using mating connectors, however the polarity for those is
731 generally reversed from the batteries used by Altus Metrum
732 products. In particular, the Tenergy batteries supplied for use
733 in Featherweight flight computers are not compatible with Altus
734 Metrum flight computers or battery chargers. <emphasis>Check
735 polarity and voltage before connecting any battery not purchased
736 from Altus Metrum or Spark Fun.</emphasis>
739 By default, we use the unregulated output of the battery directly
740 to fire ejection charges. This works marvelously with standard
741 low-current e-matches like the J-Tek from MJG Technologies, and with
742 Quest Q2G2 igniters. However, if you want or need to use a separate
743 pyro battery, check out the “External Pyro Battery” section in this
744 manual for instructions on how to wire that up. The altimeters are
745 designed to work with an external pyro battery of no more than 15 volts.
749 Ejection charges are wired directly to the screw terminal block
750 at the aft end of the altimeter. You'll need a very small straight
751 blade screwdriver for these screws, such as you might find in a
752 jeweler's screwdriver set.
755 Except for TeleMini v1.0, the flight computers also use the
756 screw terminal block for the power switch leads. On TeleMini v1.0,
757 the power switch leads are soldered directly to the board and
758 can be connected directly to a switch.
761 For most air-frames, the integrated antennas are more than
762 adequate. However, if you are installing in a carbon-fiber or
763 metal electronics bay which is opaque to RF signals, you may need to
764 use off-board external antennas instead. In this case, you can
765 order an altimeter with an SMA connector for the UHF antenna
766 connection, and, on TeleMetrum v1, you can unplug the integrated GPS
767 antenna and select an appropriate off-board GPS antenna with
768 cable terminating in a U.FL connector.
773 <title>System Operation</title>
775 <title>Firmware Modes </title>
777 The AltOS firmware build for the altimeters has two
778 fundamental modes, “idle” and “flight”. Which of these modes
779 the firmware operates in is determined at start up time. For
780 TeleMetrum, the mode is controlled by the orientation of the
781 rocket (well, actually the board, of course...) at the time
782 power is switched on. If the rocket is “nose up”, then
783 TeleMetrum assumes it's on a rail or rod being prepared for
784 launch, so the firmware chooses flight mode. However, if the
785 rocket is more or less horizontal, the firmware instead enters
786 idle mode. Since TeleMini v2.0 and EasyMini don't have an
787 accelerometer we can use to determine orientation, “idle” mode
788 is selected if the board is connected via USB to a computer,
789 otherwise the board enters “flight” mode. TeleMini v1.0
790 selects “idle” mode if it receives a command packet within the
791 first five seconds of operation.
794 At power on, you will hear three beeps or see three flashes
795 (“S” in Morse code for start up) and then a pause while
796 the altimeter completes initialization and self test, and decides
797 which mode to enter next.
800 In flight or “pad” mode, the altimeter engages the flight
801 state machine, goes into transmit-only mode to
802 send telemetry, and waits for launch to be detected.
803 Flight mode is indicated by an “di-dah-dah-dit” (“P” for pad)
804 on the beeper or lights, followed by beeps or flashes
805 indicating the state of the pyrotechnic igniter continuity.
806 One beep/flash indicates apogee continuity, two beeps/flashes
807 indicate main continuity, three beeps/flashes indicate both
808 apogee and main continuity, and one longer “brap” sound or
809 rapidly alternating lights indicates no continuity. For a
810 dual deploy flight, make sure you're getting three beeps or
811 flashes before launching! For apogee-only or motor eject
812 flights, do what makes sense.
815 If idle mode is entered, you will hear an audible “di-dit” or
816 see two short flashes (“I” for idle), and the flight state
817 machine is disengaged, thus no ejection charges will fire.
818 The altimeters also listen for the radio link when in idle
819 mode for requests sent via TeleDongle. Commands can be issued
820 in idle mode over either USB or the radio link
821 equivalently. TeleMini v1.0 only has the radio link. Idle
822 mode is useful for configuring the altimeter, for extracting
823 data from the on-board storage chip after flight, and for
824 ground testing pyro charges.
827 One “neat trick” of particular value when TeleMetrum or TeleMega are used with
828 very large air-frames, is that you can power the board up while the
829 rocket is horizontal, such that it comes up in idle mode. Then you can
830 raise the air-frame to launch position, and issue a 'reset' command
831 via TeleDongle over the radio link to cause the altimeter to reboot and
832 come up in flight mode. This is much safer than standing on the top
833 step of a rickety step-ladder or hanging off the side of a launch
834 tower with a screw-driver trying to turn on your avionics before
838 TeleMini v1.0 is configured solely via the radio link. Of course, that
839 means you need to know the TeleMini radio configuration values
840 or you won't be able to communicate with it. For situations
841 when you don't have the radio configuration values, TeleMini v1.0
842 offers an 'emergency recovery' mode. In this mode, TeleMini is
843 configured as follows:
847 Sets the radio frequency to 434.550MHz
852 Sets the radio calibration back to the factory value.
857 Sets the callsign to N0CALL
862 Does not go to 'pad' mode after five seconds.
868 To get into 'emergency recovery' mode, first find the row of
869 four small holes opposite the switch wiring. Using a short
870 piece of small gauge wire, connect the outer two holes
871 together, then power TeleMini up. Once the red LED is lit,
872 disconnect the wire and the board should signal that it's in
873 'idle' mode after the initial five second startup period.
879 TeleMetrum and TeleMega include a complete GPS receiver. A
880 complete explanation of how GPS works is beyond the scope of
881 this manual, but the bottom line is that the GPS receiver
882 needs to lock onto at least four satellites to obtain a solid
883 3 dimensional position fix and know what time it is.
886 The flight computers provide backup power to the GPS chip any time a
887 battery is connected. This allows the receiver to “warm start” on
888 the launch rail much faster than if every power-on were a GPS
889 “cold start”. In typical operations, powering up
890 on the flight line in idle mode while performing final air-frame
891 preparation will be sufficient to allow the GPS receiver to cold
892 start and acquire lock. Then the board can be powered down during
893 RSO review and installation on a launch rod or rail. When the board
894 is turned back on, the GPS system should lock very quickly, typically
895 long before igniter installation and return to the flight line are
900 <title>Controlling An Altimeter Over The Radio Link</title>
902 One of the unique features of the Altus Metrum system is the
903 ability to create a two way command link between TeleDongle
904 and an altimeter using the digital radio transceivers
905 built into each device. This allows you to interact with the
906 altimeter from afar, as if it were directly connected to the
910 Any operation which can be performed with a flight computer can
911 either be done with the device directly connected to the
912 computer via the USB cable, or through the radio
913 link. TeleMini v1.0 doesn't provide a USB connector and so it is
914 always communicated with over radio. Select the appropriate
915 TeleDongle device when the list of devices is presented and
916 AltosUI will interact with an altimeter over the radio link.
919 One oddity in the current interface is how AltosUI selects the
920 frequency for radio communications. Instead of providing
921 an interface to specifically configure the frequency, it uses
922 whatever frequency was most recently selected for the target
923 TeleDongle device in Monitor Flight mode. If you haven't ever
924 used that mode with the TeleDongle in question, select the
925 Monitor Flight button from the top level UI, and pick the
926 appropriate TeleDongle device. Once the flight monitoring
927 window is open, select the desired frequency and then close it
928 down again. All radio communications will now use that frequency.
933 Save Flight Data—Recover flight data from the rocket without
939 Configure altimeter apogee delays, main deploy heights
940 and additional pyro event conditions
941 to respond to changing launch conditions. You can also
942 'reboot' the altimeter. Use this to remotely enable the
943 flight computer by turning TeleMetrum or TeleMega on in “idle” mode,
944 then once the air-frame is oriented for launch, you can
945 reboot the altimeter and have it restart in pad mode
946 without having to climb the scary ladder.
951 Fire Igniters—Test your deployment charges without snaking
952 wires out through holes in the air-frame. Simply assemble the
953 rocket as if for flight with the apogee and main charges
954 loaded, then remotely command the altimeter to fire the
960 Operation over the radio link for configuring an altimeter, ground
961 testing igniters, and so forth uses the same RF frequencies as flight
962 telemetry. To configure the desired TeleDongle frequency, select
963 the monitor flight tab, then use the frequency selector and
964 close the window before performing other desired radio operations.
967 The flight computers only enable radio commanding in 'idle' mode.
968 TeleMetrum and TeleMega use the accelerometer to detect which orientation they
969 start up in, so make sure you have the flight computer lying horizontally when you turn
970 it on. Otherwise, it will start in 'pad' mode ready for
971 flight, and will not be listening for command packets from TeleDongle.
974 TeleMini listens for a command packet for five seconds after
975 first being turned on, if it doesn't hear anything, it enters
976 'pad' mode, ready for flight and will no longer listen for
977 command packets. The easiest way to connect to TeleMini is to
978 initiate the command and select the TeleDongle device. At this
979 point, the TeleDongle will be attempting to communicate with
980 the TeleMini. Now turn TeleMini on, and it should immediately
981 start communicating with the TeleDongle and the desired
982 operation can be performed.
985 You can monitor the operation of the radio link by watching the
986 lights on the devices. The red LED will flash each time a packet
987 is transmitted, while the green LED will light up on TeleDongle when
988 it is waiting to receive a packet from the altimeter.
992 <title>Ground Testing </title>
994 An important aspect of preparing a rocket using electronic deployment
995 for flight is ground testing the recovery system. Thanks
996 to the bi-directional radio link central to the Altus Metrum system,
997 this can be accomplished in a TeleMega, TeleMetrum or TeleMini equipped rocket
998 with less work than you may be accustomed to with other systems. It
1002 Just prep the rocket for flight, then power up the altimeter
1003 in “idle” mode (placing air-frame horizontal for TeleMetrum or TeleMega, or
1004 selecting the Configure Altimeter tab for TeleMini). This will cause
1005 the firmware to go into “idle” mode, in which the normal flight
1006 state machine is disabled and charges will not fire without
1007 manual command. You can now command the altimeter to fire the apogee
1008 or main charges from a safe distance using your computer and
1009 TeleDongle and the Fire Igniter tab to complete ejection testing.
1013 <title>Radio Link </title>
1015 The chip our boards are based on incorporates an RF transceiver, but
1016 it's not a full duplex system... each end can only be transmitting or
1017 receiving at any given moment. So we had to decide how to manage the
1021 By design, the altimeter firmware listens for the radio link when
1022 it's in “idle mode”, which
1023 allows us to use the radio link to configure the rocket, do things like
1024 ejection tests, and extract data after a flight without having to
1025 crack open the air-frame. However, when the board is in “flight
1026 mode”, the altimeter only
1027 transmits and doesn't listen at all. That's because we want to put
1028 ultimate priority on event detection and getting telemetry out of
1030 the radio in case the rocket crashes and we aren't able to extract
1034 We don't generally use a 'normal packet radio' mode like APRS
1035 because they're just too inefficient. The GFSK modulation we
1036 use is FSK with the base-band pulses passed through a Gaussian
1037 filter before they go into the modulator to limit the
1038 transmitted bandwidth. When combined with forward error
1039 correction and interleaving, this allows us to have a very
1040 robust 19.2 kilobit data link with only 10-40 milliwatts of
1041 transmit power, a whip antenna in the rocket, and a hand-held
1042 Yagi on the ground. We've had flights to above 21k feet AGL
1043 with great reception, and calculations suggest we should be
1044 good to well over 40k feet AGL with a 5-element yagi on the
1045 ground with our 10mW units and over 100k feet AGL with the
1046 40mW devices. We hope to fly boards to higher altitudes over
1047 time, and would of course appreciate customer feedback on
1048 performance in higher altitude flights!
1051 TeleMetrum v2.0 and TeleMega can send APRS if desired, the
1052 interval between APRS packets can be configured. As each APRS
1053 packet takes a full second to transmit, we recommend an
1054 interval of at least 5 seconds to avoid consuming too much
1055 battery power or radio channel bandwidth.
1059 <title>Configurable Parameters</title>
1061 Configuring an Altus Metrum altimeter for flight is very
1062 simple. Even on our baro-only TeleMini and EasyMini boards, the use of a Kalman
1063 filter means there is no need to set a “mach delay”. The few
1064 configurable parameters can all be set using AltosUI over USB or
1065 or radio link via TeleDongle.
1068 <title>Radio Frequency</title>
1070 Altus Metrum boards support radio frequencies in the 70cm
1071 band. By default, the configuration interface provides a
1072 list of 10 “standard” frequencies in 100kHz channels starting at
1073 434.550MHz. However, the firmware supports use of
1074 any 50kHz multiple within the 70cm band. At any given
1075 launch, we highly recommend coordinating when and by whom each
1076 frequency will be used to avoid interference. And of course, both
1077 altimeter and TeleDongle must be configured to the same
1078 frequency to successfully communicate with each other.
1082 <title>Apogee Delay</title>
1084 Apogee delay is the number of seconds after the altimeter detects flight
1085 apogee that the drogue charge should be fired. In most cases, this
1086 should be left at the default of 0. However, if you are flying
1087 redundant electronics such as for an L3 certification, you may wish
1088 to set one of your altimeters to a positive delay so that both
1089 primary and backup pyrotechnic charges do not fire simultaneously.
1092 The Altus Metrum apogee detection algorithm fires exactly at
1093 apogee. If you are also flying an altimeter like the
1094 PerfectFlite MAWD, which only supports selecting 0 or 1
1095 seconds of apogee delay, you may wish to set the MAWD to 0
1096 seconds delay and set the TeleMetrum to fire your backup 2
1097 or 3 seconds later to avoid any chance of both charges
1098 firing simultaneously. We've flown several air-frames this
1099 way quite happily, including Keith's successful L3 cert.
1103 <title>Main Deployment Altitude</title>
1105 By default, the altimeter will fire the main deployment charge at an
1106 elevation of 250 meters (about 820 feet) above ground. We think this
1107 is a good elevation for most air-frames, but feel free to change this
1108 to suit. In particular, if you are flying two altimeters, you may
1110 deployment elevation for the backup altimeter to be something lower
1111 than the primary so that both pyrotechnic charges don't fire
1116 <title>Maximum Flight Log</title>
1118 Changing this value will set the maximum amount of flight
1119 log storage that an individual flight will use. The
1120 available storage is divided into as many flights of the
1121 specified size as can fit in the available space. You can
1122 download and erase individual flight logs. If you fill up
1123 the available storage, future flights will not get logged
1124 until you erase some of the stored ones.
1128 <title>Ignite Mode</title>
1130 Instead of firing one charge at apogee and another charge at
1131 a fixed height above the ground, you can configure the
1132 altimeter to fire both at apogee or both during
1133 descent. This was added to support an airframe that has two
1134 altimeters, one in the fin can and one in the
1138 Providing the ability to use both igniters for apogee or
1139 main allows some level of redundancy without needing two
1140 flight computers. In Redundant Apogee or Redundant Main
1141 mode, the two charges will be fired two seconds apart.
1145 <title>Pad Orientation</title>
1147 TeleMetrum and TeleMega measure acceleration along the axis
1148 of the board. Which way the board is oriented affects the
1149 sign of the acceleration value. Instead of trying to guess
1150 which way the board is mounted in the air frame, the
1151 altimeter must be explicitly configured for either Antenna
1152 Up or Antenna Down. The default, Antenna Up, expects the end
1153 of the board connected to the 70cm antenna to be nearest the
1154 nose of the rocket, with the end containing the screw
1155 terminals nearest the tail.
1159 <title>Pyro Channels</title>
1161 In addition to the usual Apogee and Main pyro channels,
1162 TeleMega has four additional channels that can be configured
1163 to activate when various flight conditions are
1164 satisfied. You can select as many conditions as necessary;
1165 all of them must be met in order to activate the
1166 channel. The conditions available are:
1171 Acceleration away from the ground. Select a value, and
1172 then choose whether acceleration should be above or
1173 below that value. Acceleration is positive upwards, so
1174 accelerating towards the ground would produce negative
1175 numbers. Acceleration during descent is noisy and
1176 inaccurate, so be careful when using it during these
1177 phases of the flight.
1182 Vertical speed. Select a value, and then choose whether
1183 vertical speed should be above or below that
1184 value. Speed is positive upwards, so moving towards the
1185 ground would produce negative numbers. Speed during
1186 descent is a bit noisy and so be careful when using it
1187 during these phases of the flight.
1192 Height. Select a value, and then choose whether the
1193 height above the launch pad should be above or below
1199 Orientation. TeleMega contains a 3-axis gyroscope and
1200 accelerometer which is used to measure the current
1201 angle. Note that this angle is not the change in angle
1202 from the launch pad, but rather absolute relative to
1203 gravity; the 3-axis accelerometer is used to compute the
1204 angle of the rocket on the launch pad and initialize the
1205 system. Because this value is computed by integrating
1206 rate gyros, it gets progressively less accurate as the
1207 flight goes on. It should have an accumulated error of
1208 less than .2°/second (after 10 seconds of flight, the
1209 error should be less than 2°).
1212 The usual use of the orientation configuration is to
1213 ensure that the rocket is traveling mostly upwards when
1214 deciding whether to ignite air starts or additional
1215 stages. For that, choose a reasonable maximum angle
1216 (like 20°) and set the motor igniter to require an angle
1217 of less than that value.
1222 Flight Time. Time since boost was detected. Select a
1223 value and choose whether to activate the pyro channel
1224 before or after that amount of time.
1229 Ascending. A simple test saying whether the rocket is
1230 going up or not. This is exactly equivalent to testing
1231 whether the speed is > 0.
1236 Descending. A simple test saying whether the rocket is
1237 going down or not. This is exactly equivalent to testing
1238 whether the speed is < 0.
1243 After Motor. The flight software counts each time the
1244 rocket starts accelerating (presumably due to a motor or
1245 motors igniting). Use this value to count ignitions for
1246 multi-staged or multi-airstart launches.
1251 Delay. This value doesn't perform any checks, instead it
1252 inserts a delay between the time when the other
1253 parameters become true and when the pyro channel is
1259 Flight State. The flight software tracks the flight
1260 through a sequence of states:
1264 Boost. The motor has lit and the rocket is
1265 accelerating upwards.
1270 Fast. The motor has burned out and the rocket is
1271 descellerating, but it is going faster than 200m/s.
1276 Coast. The rocket is still moving upwards and
1277 decelerating, but the speed is less than 200m/s.
1282 Drogue. The rocket has reached apogee and is heading
1283 back down, but is above the configured Main
1289 Main. The rocket is still descending, and is below
1295 Landed. The rocket is no longer moving.
1301 You can select a state to limit when the pyro channel
1302 may activate; note that the check is based on when the
1303 rocket transitions <emphasis>into</emphasis> the state, and so checking for
1304 “greater than Boost” means that the rocket is currently
1305 in boost or some later state.
1308 When a motor burns out, the rocket enters either Fast or
1309 Coast state (depending on how fast it is moving). If the
1310 computer detects upwards acceleration again, it will
1311 move back to Boost state.
1321 <title>AltosUI</title>
1323 The AltosUI program provides a graphical user interface for
1324 interacting with the Altus Metrum product family. AltosUI can
1325 monitor telemetry data, configure devices and many other
1326 tasks. The primary interface window provides a selection of
1327 buttons, one for each major activity in the system. This manual
1328 is split into chapters, each of which documents one of the tasks
1329 provided from the top-level toolbar.
1332 <title>Monitor Flight</title>
1333 <subtitle>Receive, Record and Display Telemetry Data</subtitle>
1335 Selecting this item brings up a dialog box listing all of the
1336 connected TeleDongle devices. When you choose one of these,
1337 AltosUI will create a window to display telemetry data as
1338 received by the selected TeleDongle device.
1341 All telemetry data received are automatically recorded in
1342 suitable log files. The name of the files includes the current
1343 date and rocket serial and flight numbers.
1346 The radio frequency being monitored by the TeleDongle device is
1347 displayed at the top of the window. You can configure the
1348 frequency by clicking on the frequency box and selecting the desired
1349 frequency. AltosUI remembers the last frequency selected for each
1350 TeleDongle and selects that automatically the next time you use
1354 Below the TeleDongle frequency selector, the window contains a few
1355 significant pieces of information about the altimeter providing
1356 the telemetry data stream:
1360 <para>The configured call-sign</para>
1363 <para>The device serial number</para>
1366 <para>The flight number. Each altimeter remembers how many
1372 The rocket flight state. Each flight passes through several
1373 states including Pad, Boost, Fast, Coast, Drogue, Main and
1379 The Received Signal Strength Indicator value. This lets
1380 you know how strong a signal TeleDongle is receiving. The
1381 radio inside TeleDongle operates down to about -99dBm;
1382 weaker signals may not be receivable. The packet link uses
1383 error detection and correction techniques which prevent
1384 incorrect data from being reported.
1389 The age of the displayed data, in seconds since the last
1390 successfully received telemetry packet. In normal operation
1391 this will stay in the low single digits. If the number starts
1392 counting up, then you are no longer receiving data over the radio
1393 link from the flight computer.
1398 Finally, the largest portion of the window contains a set of
1399 tabs, each of which contain some information about the rocket.
1400 They're arranged in 'flight order' so that as the flight
1401 progresses, the selected tab automatically switches to display
1402 data relevant to the current state of the flight. You can select
1403 other tabs at any time. The final 'table' tab displays all of
1404 the raw telemetry values in one place in a spreadsheet-like format.
1407 <title>Launch Pad</title>
1409 The 'Launch Pad' tab shows information used to decide when the
1410 rocket is ready for flight. The first elements include red/green
1411 indicators, if any of these is red, you'll want to evaluate
1412 whether the rocket is ready to launch:
1415 <term>Battery Voltage</term>
1418 This indicates whether the Li-Po battery
1419 powering the TeleMetrum has sufficient charge to last for
1420 the duration of the flight. A value of more than
1421 3.8V is required for a 'GO' status.
1426 <term>Apogee Igniter Voltage</term>
1429 This indicates whether the apogee
1430 igniter has continuity. If the igniter has a low
1431 resistance, then the voltage measured here will be close
1432 to the Li-Po battery voltage. A value greater than 3.2V is
1433 required for a 'GO' status.
1438 <term>Main Igniter Voltage</term>
1441 This indicates whether the main
1442 igniter has continuity. If the igniter has a low
1443 resistance, then the voltage measured here will be close
1444 to the Li-Po battery voltage. A value greater than 3.2V is
1445 required for a 'GO' status.
1450 <term>On-board Data Logging</term>
1453 This indicates whether there is
1454 space remaining on-board to store flight data for the
1455 upcoming flight. If you've downloaded data, but failed
1456 to erase flights, there may not be any space
1457 left. TeleMetrum can store multiple flights, depending
1458 on the configured maximum flight log size. TeleMini
1459 stores only a single flight, so it will need to be
1460 downloaded and erased after each flight to capture
1461 data. This only affects on-board flight logging; the
1462 altimeter will still transmit telemetry and fire
1463 ejection charges at the proper times.
1468 <term>GPS Locked</term>
1471 For a TeleMetrum or TeleMega device, this indicates whether the GPS receiver is
1472 currently able to compute position information. GPS requires
1473 at least 4 satellites to compute an accurate position.
1478 <term>GPS Ready</term>
1481 For a TeleMetrum or TeleMega device, this indicates whether GPS has reported at least
1482 10 consecutive positions without losing lock. This ensures
1483 that the GPS receiver has reliable reception from the
1491 The Launchpad tab also shows the computed launch pad position
1492 and altitude, averaging many reported positions to improve the
1493 accuracy of the fix.
1497 <title>Ascent</title>
1499 This tab is shown during Boost, Fast and Coast
1500 phases. The information displayed here helps monitor the
1501 rocket as it heads towards apogee.
1504 The height, speed and acceleration are shown along with the
1505 maximum values for each of them. This allows you to quickly
1506 answer the most commonly asked questions you'll hear during
1510 The current latitude and longitude reported by the TeleMetrum GPS are
1511 also shown. Note that under high acceleration, these values
1512 may not get updated as the GPS receiver loses position
1513 fix. Once the rocket starts coasting, the receiver should
1514 start reporting position again.
1517 Finally, the current igniter voltages are reported as in the
1518 Launch Pad tab. This can help diagnose deployment failures
1519 caused by wiring which comes loose under high acceleration.
1523 <title>Descent</title>
1525 Once the rocket has reached apogee and (we hope) activated the
1526 apogee charge, attention switches to tracking the rocket on
1527 the way back to the ground, and for dual-deploy flights,
1528 waiting for the main charge to fire.
1531 To monitor whether the apogee charge operated correctly, the
1532 current descent rate is reported along with the current
1533 height. Good descent rates vary based on the choice of recovery
1534 components, but generally range from 15-30m/s on drogue and should
1535 be below 10m/s when under the main parachute in a dual-deploy flight.
1538 For TeleMetrum altimeters, you can locate the rocket in the
1539 sky using the elevation and bearing information to figure
1540 out where to look. Elevation is in degrees above the
1541 horizon. Bearing is reported in degrees relative to true
1542 north. Range can help figure out how big the rocket will
1543 appear. Ground Distance shows how far it is to a point
1544 directly under the rocket and can help figure out where the
1545 rocket is likely to land. Note that all of these values are
1546 relative to the pad location. If the elevation is near 90°,
1547 the rocket is over the pad, not over you.
1550 Finally, the igniter voltages are reported in this tab as
1551 well, both to monitor the main charge as well as to see what
1552 the status of the apogee charge is. Note that some commercial
1553 e-matches are designed to retain continuity even after being
1554 fired, and will continue to show as green or return from red to
1559 <title>Landed</title>
1561 Once the rocket is on the ground, attention switches to
1562 recovery. While the radio signal is often lost once the
1563 rocket is on the ground, the last reported GPS position is
1564 generally within a short distance of the actual landing location.
1567 The last reported GPS position is reported both by
1568 latitude and longitude as well as a bearing and distance from
1569 the launch pad. The distance should give you a good idea of
1570 whether to walk or hitch a ride. Take the reported
1571 latitude and longitude and enter them into your hand-held GPS
1572 unit and have that compute a track to the landing location.
1575 Both TeleMini and TeleMetrum will continue to transmit RDF
1576 tones after landing, allowing you to locate the rocket by
1577 following the radio signal if necessary. You may need to get
1578 away from the clutter of the flight line, or even get up on
1579 a hill (or your neighbor's RV roof) to receive the RDF signal.
1582 The maximum height, speed and acceleration reported
1583 during the flight are displayed for your admiring observers.
1584 The accuracy of these immediate values depends on the quality
1585 of your radio link and how many packets were received.
1586 Recovering the on-board data after flight will likely yield
1587 more precise results.
1590 To get more detailed information about the flight, you can
1591 click on the 'Graph Flight' button which will bring up a
1592 graph window for the current flight.
1596 <title>Site Map</title>
1598 When the TeleMetrum has a GPS fix, the Site Map tab will map
1599 the rocket's position to make it easier for you to locate the
1600 rocket, both while it is in the air, and when it has landed. The
1601 rocket's state is indicated by color: white for pad, red for
1602 boost, pink for fast, yellow for coast, light blue for drogue,
1603 dark blue for main, and black for landed.
1606 The map's scale is approximately 3m (10ft) per pixel. The map
1607 can be dragged using the left mouse button. The map will attempt
1608 to keep the rocket roughly centered while data is being received.
1611 Images are fetched automatically via the Google Maps Static API,
1612 and cached on disk for reuse. If map images cannot be downloaded,
1613 the rocket's path will be traced on a dark gray background
1617 You can pre-load images for your favorite launch sites
1618 before you leave home; check out the 'Preload Maps' section below.
1623 <title>Save Flight Data</title>
1625 The altimeter records flight data to its internal flash memory.
1626 TeleMetrum data is recorded at a much higher rate than the telemetry
1627 system can handle, and is not subject to radio drop-outs. As
1628 such, it provides a more complete and precise record of the
1629 flight. The 'Save Flight Data' button allows you to read the
1630 flash memory and write it to disk. As TeleMini has only a barometer, it
1631 records data at the same rate as the telemetry signal, but there will be
1632 no data lost due to telemetry drop-outs.
1635 Clicking on the 'Save Flight Data' button brings up a list of
1636 connected TeleMetrum and TeleDongle devices. If you select a
1637 TeleMetrum device, the flight data will be downloaded from that
1638 device directly. If you select a TeleDongle device, flight data
1639 will be downloaded from an altimeter over radio link via the
1640 specified TeleDongle. See the chapter on Controlling An Altimeter
1641 Over The Radio Link for more information.
1644 After the device has been selected, a dialog showing the
1645 flight data saved in the device will be shown allowing you to
1646 select which flights to download and which to delete. With
1647 version 0.9 or newer firmware, you must erase flights in order
1648 for the space they consume to be reused by another
1649 flight. This prevents accidentally losing flight data
1650 if you neglect to download data before flying again. Note that
1651 if there is no more space available in the device, then no
1652 data will be recorded during the next flight.
1655 The file name for each flight log is computed automatically
1656 from the recorded flight date, altimeter serial number and
1657 flight number information.
1661 <title>Replay Flight</title>
1663 Select this button and you are prompted to select a flight
1664 record file, either a .telem file recording telemetry data or a
1665 .eeprom file containing flight data saved from the altimeter
1669 Once a flight record is selected, the flight monitor interface
1670 is displayed and the flight is re-enacted in real time. Check
1671 the Monitor Flight chapter above to learn how this window operates.
1675 <title>Graph Data</title>
1677 Select this button and you are prompted to select a flight
1678 record file, either a .telem file recording telemetry data or a
1679 .eeprom file containing flight data saved from
1683 Once a flight record is selected, a window with multiple tabs is
1687 <term>Flight Graph</term>
1690 By default, the graph contains acceleration (blue),
1691 velocity (green) and altitude (red).
1696 <term>Configure Graph</term>
1699 This selects which graph elements to show, and, at the
1700 very bottom, lets you switch between metric and
1706 <term>Flight Statistics</term>
1709 Shows overall data computed from the flight.
1717 Shows a satellite image of the flight area overlaid
1718 with the path of the flight. The red concentric
1719 circles mark the launch pad, the black concentric
1720 circles mark the landing location.
1727 The graph can be zoomed into a particular area by clicking and
1728 dragging down and to the right. Once zoomed, the graph can be
1729 reset by clicking and dragging up and to the left. Holding down
1730 control and clicking and dragging allows the graph to be panned.
1731 The right mouse button causes a pop-up menu to be displayed, giving
1732 you the option save or print the plot.
1735 Note that telemetry files will generally produce poor graphs
1736 due to the lower sampling rate and missed telemetry packets.
1737 Use saved flight data in .eeprom files for graphing where possible.
1741 <title>Export Data</title>
1743 This tool takes the raw data files and makes them available for
1744 external analysis. When you select this button, you are prompted to
1746 data file (either .eeprom or .telem will do, remember that
1747 .eeprom files contain higher resolution and more continuous
1748 data). Next, a second dialog appears which is used to select
1749 where to write the resulting file. It has a selector to choose
1750 between CSV and KML file formats.
1753 <title>Comma Separated Value Format</title>
1755 This is a text file containing the data in a form suitable for
1756 import into a spreadsheet or other external data analysis
1757 tool. The first few lines of the file contain the version and
1758 configuration information from the altimeter, then
1759 there is a single header line which labels all of the
1760 fields. All of these lines start with a '#' character which
1761 many tools can be configured to skip over.
1764 The remaining lines of the file contain the data, with each
1765 field separated by a comma and at least one space. All of
1766 the sensor values are converted to standard units, with the
1767 barometric data reported in both pressure, altitude and
1768 height above pad units.
1772 <title>Keyhole Markup Language (for Google Earth)</title>
1774 This is the format used by Google Earth to provide an overlay
1775 within that application. With this, you can use Google Earth to
1776 see the whole flight path in 3D.
1781 <title>Configure Altimeter</title>
1783 Select this button and then select either an altimeter or
1784 TeleDongle Device from the list provided. Selecting a TeleDongle
1785 device will use the radio link to configure a remote altimeter.
1788 The first few lines of the dialog provide information about the
1789 connected device, including the product name,
1790 software version and hardware serial number. Below that are the
1791 individual configuration entries.
1794 At the bottom of the dialog, there are four buttons:
1801 This writes any changes to the
1802 configuration parameter block in flash memory. If you don't
1803 press this button, any changes you make will be lost.
1811 This resets the dialog to the most recently saved values,
1812 erasing any changes you have made.
1820 This reboots the device. Use this to
1821 switch from idle to pad mode by rebooting once the rocket is
1822 oriented for flight, or to confirm changes you think you saved
1831 This closes the dialog. Any unsaved changes will be
1838 The rest of the dialog contains the parameters to be configured.
1841 <title>Main Deploy Altitude</title>
1843 This sets the altitude (above the recorded pad altitude) at
1844 which the 'main' igniter will fire. The drop-down menu shows
1845 some common values, but you can edit the text directly and
1846 choose whatever you like. If the apogee charge fires below
1847 this altitude, then the main charge will fire two seconds
1848 after the apogee charge fires.
1852 <title>Apogee Delay</title>
1854 When flying redundant electronics, it's often important to
1855 ensure that multiple apogee charges don't fire at precisely
1856 the same time, as that can over pressurize the apogee deployment
1857 bay and cause a structural failure of the air-frame. The Apogee
1858 Delay parameter tells the flight computer to fire the apogee
1859 charge a certain number of seconds after apogee has been
1864 <title>Radio Frequency</title>
1866 This configures which of the frequencies to use for both
1867 telemetry and packet command mode. Note that if you set this
1868 value via packet command mode, the TeleDongle frequency will
1869 also be automatically reconfigured to match so that
1870 communication will continue afterwards.
1874 <title>RF Calibration</title>
1876 The radios in every Altus Metrum device are calibrated at the
1877 factory to ensure that they transmit and receive on the
1878 specified frequency. If you need to you can adjust the calibration
1879 by changing this value. Do not do this without understanding what
1880 the value means, read the appendix on calibration and/or the source
1881 code for more information. To change a TeleDongle's calibration,
1882 you must reprogram the unit completely.
1886 <title>Telemetry/RDF/APRS Enable</title>
1888 Enables the radio for transmission during flight. When
1889 disabled, the radio will not transmit anything during flight
1894 <title>APRS Interval</title>
1896 How often to transmit GPS information via APRS. This option
1897 is available on TeleMetrum v2 and TeleMega
1898 boards. TeleMetrum v1 boards cannot transmit APRS
1899 packets. Note that a single APRS packet takes nearly a full
1900 second to transmit, so enabling this option will prevent
1901 sending any other telemetry during that time.
1905 <title>Callsign</title>
1907 This sets the call sign included in each telemetry packet. Set this
1908 as needed to conform to your local radio regulations.
1912 <title>Maximum Flight Log Size</title>
1914 This sets the space (in kilobytes) allocated for each flight
1915 log. The available space will be divided into chunks of this
1916 size. A smaller value will allow more flights to be stored,
1917 a larger value will record data from longer flights.
1921 <title>Ignite Mode</title>
1923 TeleMetrum and TeleMini provide two igniter channels as they
1924 were originally designed as dual-deploy flight
1925 computers. This configuration parameter allows the two
1926 channels to be used in different configurations.
1930 <term>Dual Deploy</term>
1933 This is the usual mode of operation; the
1934 'apogee' channel is fired at apogee and the 'main'
1935 channel at the height above ground specified by the
1936 'Main Deploy Altitude' during descent.
1941 <term>Redundant Apogee</term>
1944 This fires both channels at
1945 apogee, the 'apogee' channel first followed after a two second
1946 delay by the 'main' channel.
1951 <term>Redundant Main</term>
1954 This fires both channels at the
1955 height above ground specified by the Main Deploy
1956 Altitude setting during descent. The 'apogee'
1957 channel is fired first, followed after a two second
1958 delay by the 'main' channel.
1965 <title>Pad Orientation</title>
1967 Because it includes an accelerometer, TeleMetrum and
1968 TeleMega are sensitive to the orientation of the board. By
1969 default, it expects the antenna end to point forward. This
1970 parameter allows that default to be changed, permitting the
1971 board to be mounted with the antenna pointing aft instead.
1975 <term>Antenna Up</term>
1978 In this mode, the antenna end of the
1979 TeleMetrum board must point forward, in line with the
1980 expected flight path.
1985 <term>Antenna Down</term>
1988 In this mode, the antenna end of the
1989 TeleMetrum board must point aft, in line with the
1990 expected flight path.
1997 <title>Configure Pyro Channels</title>
1999 This opens a separate window to configure the additional
2000 pyro channels available on TeleMega. One column is
2001 presented for each channel. Each row represents a single
2002 parameter, if enabled the parameter must meet the specified
2003 test for the pyro channel to be fired. See the Pyro Channels
2004 section in the System Operation chapter above for a
2005 description of these parameters.
2008 Select conditions and set the related value; the pyro
2009 channel will be activated when <emphasis>all</emphasis> of the
2010 conditions are met. Each pyro channel has a separate set of
2011 configuration values, so you can use different values for
2012 the same condition with different channels.
2015 Once you have selected the appropriate configuration for all
2016 of the necessary pyro channels, you can save the pyro
2017 configuration along with the rest of the flight computer
2018 configuration by pressing the 'Save' button in the main
2019 Configure Flight Computer window.
2024 <title>Configure AltosUI</title>
2026 This button presents a dialog so that you can configure the AltosUI global settings.
2029 <title>Voice Settings</title>
2031 AltosUI provides voice announcements during flight so that you
2032 can keep your eyes on the sky and still get information about
2033 the current flight status. However, sometimes you don't want
2038 <para>Enable—turns all voice announcements on and off</para>
2042 Test Voice—Plays a short message allowing you to verify
2043 that the audio system is working and the volume settings
2050 <title>Log Directory</title>
2052 AltosUI logs all telemetry data and saves all TeleMetrum flash
2053 data to this directory. This directory is also used as the
2054 staring point when selecting data files for display or export.
2057 Click on the directory name to bring up a directory choosing
2058 dialog, select a new directory and click 'Select Directory' to
2059 change where AltosUI reads and writes data files.
2063 <title>Callsign</title>
2065 This value is transmitted in each command packet sent from
2066 TeleDongle and received from an altimeter. It is not used in
2067 telemetry mode, as the callsign configured in the altimeter board
2068 is included in all telemetry packets. Configure this
2069 with the AltosUI operators call sign as needed to comply with
2070 your local radio regulations.
2073 Note that to successfully command a flight computer over the radio
2074 (to configure the altimeter, monitor idle, or fire pyro charges),
2075 the callsign configured here must exactly match the callsign
2076 configured in the flight computer. This matching is case
2081 <title>Imperial Units</title>
2083 This switches between metric units (meters) and imperial
2084 units (feet and miles). This affects the display of values
2085 use during flight monitoring, configuration, data graphing
2086 and all of the voice announcements. It does not change the
2087 units used when exporting to CSV files, those are always
2088 produced in metric units.
2092 <title>Font Size</title>
2094 Selects the set of fonts used in the flight monitor
2095 window. Choose between the small, medium and large sets.
2099 <title>Serial Debug</title>
2101 This causes all communication with a connected device to be
2102 dumped to the console from which AltosUI was started. If
2103 you've started it from an icon or menu entry, the output
2104 will simply be discarded. This mode can be useful to debug
2105 various serial communication issues.
2109 <title>Manage Frequencies</title>
2111 This brings up a dialog where you can configure the set of
2112 frequencies shown in the various frequency menus. You can
2113 add as many as you like, or even reconfigure the default
2114 set. Changing this list does not affect the frequency
2115 settings of any devices, it only changes the set of
2116 frequencies shown in the menus.
2121 <title>Configure Groundstation</title>
2123 Select this button and then select a TeleDongle Device from the list provided.
2126 The first few lines of the dialog provide information about the
2127 connected device, including the product name,
2128 software version and hardware serial number. Below that are the
2129 individual configuration entries.
2132 Note that the TeleDongle itself doesn't save any configuration
2133 data, the settings here are recorded on the local machine in
2134 the Java preferences database. Moving the TeleDongle to
2135 another machine, or using a different user account on the same
2136 machine will cause settings made here to have no effect.
2139 At the bottom of the dialog, there are three buttons:
2146 This writes any changes to the
2147 local Java preferences file. If you don't
2148 press this button, any changes you make will be lost.
2156 This resets the dialog to the most recently saved values,
2157 erasing any changes you have made.
2165 This closes the dialog. Any unsaved changes will be
2172 The rest of the dialog contains the parameters to be configured.
2175 <title>Frequency</title>
2177 This configures the frequency to use for both telemetry and
2178 packet command mode. Set this before starting any operation
2179 involving packet command mode so that it will use the right
2180 frequency. Telemetry monitoring mode also provides a menu to
2181 change the frequency, and that menu also sets the same Java
2182 preference value used here.
2186 <title>Radio Calibration</title>
2188 The radios in every Altus Metrum device are calibrated at the
2189 factory to ensure that they transmit and receive on the
2190 specified frequency. To change a TeleDongle's calibration,
2191 you must reprogram the unit completely, so this entry simply
2192 shows the current value and doesn't allow any changes.
2197 <title>Flash Image</title>
2199 This reprograms Altus Metrum device with new
2200 firmware. TeleMetrum v1.x, TeleDongle, TeleMini and TeleBT are
2201 all reprogrammed by using another similar unit as a
2202 programming dongle (pair programming). TeleMega, TeleMetrum v2
2203 and EasyMini are all programmed directly over their USB ports
2204 (self programming). Please read the directions for flashing
2205 devices in the Updating Device Firmware chapter below.
2208 For “self programming”, connect USB to the device to be
2209 programmed and push the 'Flash Image' button. That will
2210 present a dialog box listing all of the connected
2211 devices. Carefully select the device to be programmed.
2214 For “pair programming”, once you have the programmer and
2215 target devices connected, push the 'Flash Image' button. That
2216 will present a dialog box listing all of the connected
2217 devices. Carefully select the programmer device, not the
2218 device to be programmed.
2221 Next, select the image to flash to the device. These are named
2222 with the product name and firmware version. The file selector
2223 will start in the directory containing the firmware included
2224 with the AltosUI package. Navigate to the directory containing
2225 the desired firmware if it isn't there.
2228 Next, a small dialog containing the device serial number and
2229 RF calibration values should appear. If these values are
2230 incorrect (possibly due to a corrupted image in the device),
2231 enter the correct values here.
2234 Finally, a dialog containing a progress bar will follow the
2235 programming process.
2238 When programming is complete, the target device will
2239 reboot. Note that if a pair programmed target device is
2240 connected via USB, you will have to unplug it and then plug it
2241 back in for the USB connection to reset so that you can
2242 communicate with the device again.
2246 <title>Fire Igniter</title>
2248 This activates the igniter circuits in TeleMetrum to help test
2249 recovery systems deployment. Because this command can operate
2250 over the Packet Command Link, you can prepare the rocket as
2251 for flight and then test the recovery system without needing
2252 to snake wires inside the air-frame.
2255 Selecting the 'Fire Igniter' button brings up the usual device
2256 selection dialog. Pick the desired TeleDongle or TeleMetrum
2257 device. This brings up another window which shows the current
2258 continuity test status for both apogee and main charges.
2261 Next, select the desired igniter to fire. This will enable the
2265 Select the 'Arm' button. This enables the 'Fire' button. The
2266 word 'Arm' is replaced by a countdown timer indicating that
2267 you have 10 seconds to press the 'Fire' button or the system
2268 will deactivate, at which point you start over again at
2269 selecting the desired igniter.
2273 <title>Scan Channels</title>
2275 This listens for telemetry packets on all of the configured
2276 frequencies, displaying information about each device it
2277 receives a packet from. You can select which of the three
2278 telemetry formats should be tried; by default, it only listens
2279 for the standard telemetry packets used in v1.0 and later
2284 <title>Load Maps</title>
2286 Before heading out to a new launch site, you can use this to
2287 load satellite images in case you don't have internet
2288 connectivity at the site. This loads a fairly large area
2289 around the launch site, which should cover any flight you're likely to make.
2292 There's a drop-down menu of launch sites we know about; if
2293 your favorites aren't there, please let us know the lat/lon
2294 and name of the site. The contents of this list are actually
2295 downloaded at run-time, so as new sites are sent in, they'll
2296 get automatically added to this list.
2299 If the launch site isn't in the list, you can manually enter the lat/lon values
2302 Clicking the 'Load Map' button will fetch images from Google
2303 Maps; note that Google limits how many images you can fetch at
2304 once, so if you load more than one launch site, you may get
2305 some gray areas in the map which indicate that Google is tired
2306 of sending data to you. Try again later.
2310 <title>Monitor Idle</title>
2312 This brings up a dialog similar to the Monitor Flight UI,
2313 except it works with the altimeter in “idle” mode by sending
2314 query commands to discover the current state rather than
2315 listening for telemetry packets. Because this uses command
2316 mode, it needs to have the TeleDongle and flight computer
2317 callsigns match exactly. If you can receive telemetry, but
2318 cannot manage to run Monitor Idle, then it's very likely that
2319 your callsigns are different in some way.
2324 <title>AltosDroid</title>
2326 AltosDroid provides the same flight monitoring capabilities as
2327 AltosUI, but runs on Android devices and is designed to connect
2328 to a TeleBT receiver over Bluetooth™. Altos Droid monitors
2329 telemetry data, logging it to internal storage in the Android
2330 device, and presents that data in a UI the same way the 'Monitor
2331 Flight' window does in AltosUI.
2334 This manual will explain how to configure AltosDroid, connect
2335 to TeleBT, operate the flight monitoring interface and describe
2336 what the displayed data means.
2339 <title>Installing AltosDroid</title>
2341 AltosDroid is included in the Google Play store. To install
2342 it on your Android device, open open the Google Play Store
2343 application and search for “altosdroid”. Make sure you don't
2344 have a space between “altos” and “droid” or you probably won't
2345 find what you want. That should bring you to the right page
2346 from which you can download and install the application.
2350 <title>Connecting to TeleBT</title>
2352 Press the Android 'Menu' button or soft-key to see the
2353 configuration options available. Select the 'Connect a device'
2354 option and then the 'Scan for devices' entry at the bottom to
2355 look for your TeleBT device. Select your device, and when it
2356 asks for the code, enter '1234'.
2359 Subsequent connections will not require you to enter that
2360 code, and your 'paired' device will appear in the list without
2365 <title>Configuring AltosDroid</title>
2367 The only configuration option available for AltosDroid is
2368 which frequency to listen on. Press the Android 'Menu' button
2369 or soft-key and pick the 'Select radio frequency' entry. That
2370 brings up a menu of pre-set radio frequencies; pick the one
2371 which matches your altimeter.
2375 <title>Altos Droid Flight Monitoring</title>
2377 Altos Droid is designed to mimic the AltosUI flight monitoring
2378 display, providing separate tabs for each stage of your rocket
2379 flight along with a tab containing a map of the local area
2380 with icons marking the current location of the altimeter and
2386 The 'Launch Pad' tab shows information used to decide when the
2387 rocket is ready for flight. The first elements include red/green
2388 indicators, if any of these is red, you'll want to evaluate
2389 whether the rocket is ready to launch:
2392 <term>Battery Voltage</term>
2395 This indicates whether the Li-Po battery
2396 powering the TeleMetrum has sufficient charge to last for
2397 the duration of the flight. A value of more than
2398 3.8V is required for a 'GO' status.
2403 <term>Apogee Igniter Voltage</term>
2406 This indicates whether the apogee
2407 igniter has continuity. If the igniter has a low
2408 resistance, then the voltage measured here will be close
2409 to the Li-Po battery voltage. A value greater than 3.2V is
2410 required for a 'GO' status.
2415 <term>Main Igniter Voltage</term>
2418 This indicates whether the main
2419 igniter has continuity. If the igniter has a low
2420 resistance, then the voltage measured here will be close
2421 to the Li-Po battery voltage. A value greater than 3.2V is
2422 required for a 'GO' status.
2427 <term>On-board Data Logging</term>
2430 This indicates whether there is
2431 space remaining on-board to store flight data for the
2432 upcoming flight. If you've downloaded data, but failed
2433 to erase flights, there may not be any space
2434 left. TeleMetrum can store multiple flights, depending
2435 on the configured maximum flight log size. TeleMini
2436 stores only a single flight, so it will need to be
2437 downloaded and erased after each flight to capture
2438 data. This only affects on-board flight logging; the
2439 altimeter will still transmit telemetry and fire
2440 ejection charges at the proper times.
2445 <term>GPS Locked</term>
2448 For a TeleMetrum or TeleMega device, this indicates whether the GPS receiver is
2449 currently able to compute position information. GPS requires
2450 at least 4 satellites to compute an accurate position.
2455 <term>GPS Ready</term>
2458 For a TeleMetrum or TeleMega device, this indicates whether GPS has reported at least
2459 10 consecutive positions without losing lock. This ensures
2460 that the GPS receiver has reliable reception from the
2468 The Launchpad tab also shows the computed launch pad position
2469 and altitude, averaging many reported positions to improve the
2470 accuracy of the fix.
2475 <title>Downloading Flight Logs</title>
2477 Altos Droid always saves every bit of telemetry data it
2478 receives. To download that to a computer for use with AltosUI,
2479 simply remove the SD card from your Android device, or connect
2480 your device to your computer's USB port and browse the files
2481 on that device. You will find '.telem' files in the TeleMetrum
2482 directory that will work with AltosUI directly.
2487 <title>Using Altus Metrum Products</title>
2489 <title>Being Legal</title>
2491 First off, in the US, you need an <ulink url="http://www.altusmetrum.org/Radio/">amateur radio license</ulink> or
2492 other authorization to legally operate the radio transmitters that are part
2497 <title>In the Rocket</title>
2499 In the rocket itself, you just need a <ulink url="http://www.altusmetrum.org/TeleMetrum/">TeleMetrum</ulink> or
2500 <ulink url="http://www.altusmetrum.org/TeleMini/">TeleMini</ulink> board and
2501 a single-cell, 3.7 volt nominal Li-Po rechargeable battery. An
2502 850mAh battery weighs less than a 9V alkaline battery, and will
2503 run a TeleMetrum for hours.
2504 A 110mAh battery weighs less than a triple A battery and will run a TeleMetrum for
2505 a few hours, or a TeleMini for much (much) longer.
2508 By default, we ship the altimeters with a simple wire antenna. If your
2509 electronics bay or the air-frame it resides within is made of carbon fiber,
2510 which is opaque to RF signals, you may choose to have an SMA connector
2511 installed so that you can run a coaxial cable to an antenna mounted
2512 elsewhere in the rocket.
2516 <title>On the Ground</title>
2518 To receive the data stream from the rocket, you need an antenna and short
2519 feed-line connected to one of our <ulink url="http://www.altusmetrum.org/TeleDongle/">TeleDongle</ulink> units. If possible, use an SMA to BNC
2520 adapter instead of feedline between the antenna feedpoint and
2521 TeleDongle, as this will give you the best performance. The
2522 TeleDongle in turn plugs directly into the USB port on a notebook
2523 computer. Because TeleDongle looks like a simple serial port, your computer
2524 does not require special device drivers... just plug it in.
2527 The GUI tool, AltosUI, is written in Java and runs across
2528 Linux, Mac OS and Windows. There's also a suite of C tools
2529 for Linux which can perform most of the same tasks.
2532 After the flight, you can use the radio link to extract the more detailed data
2533 logged in either TeleMetrum or TeleMini devices, or you can use a mini USB cable to plug into the
2534 TeleMetrum board directly. Pulling out the data without having to open up
2535 the rocket is pretty cool! A USB cable is also how you charge the Li-Po
2536 battery, so you'll want one of those anyway... the same cable used by lots
2537 of digital cameras and other modern electronic stuff will work fine.
2540 If your TeleMetrum-equipped rocket lands out of sight, you may enjoy having a hand-held GPS
2541 receiver, so that you can put in a way-point for the last reported rocket
2542 position before touch-down. This makes looking for your rocket a lot like
2543 Geo-Caching... just go to the way-point and look around starting from there.
2546 You may also enjoy having a ham radio “HT” that covers the 70cm band... you
2547 can use that with your antenna to direction-find the rocket on the ground
2548 the same way you can use a Walston or Beeline tracker. This can be handy
2549 if the rocket is hiding in sage brush or a tree, or if the last GPS position
2550 doesn't get you close enough because the rocket dropped into a canyon, or
2551 the wind is blowing it across a dry lake bed, or something like that... Keith
2552 currently uses a Yaesu VX-7R, Bdale has a Baofung UV-5R
2553 which isn't as nice, but was a whole lot cheaper.
2556 So, to recap, on the ground the hardware you'll need includes:
2557 <orderedlist inheritnum='inherit' numeration='arabic'>
2560 an antenna and feed-line or adapter
2575 optionally, a hand-held GPS receiver
2580 optionally, an HT or receiver covering 435 MHz
2586 The best hand-held commercial directional antennas we've found for radio
2587 direction finding rockets are from
2588 <ulink url="http://www.arrowantennas.com/" >
2591 The 440-3 and 440-5 are both good choices for finding a
2592 TeleMetrum- or TeleMini- equipped rocket when used with a suitable
2593 70cm HT. TeleDongle and an SMA to BNC adapter fit perfectly
2594 between the driven element and reflector of Arrow antennas.
2598 <title>Data Analysis</title>
2600 Our software makes it easy to log the data from each flight, both the
2601 telemetry received during the flight itself, and the more
2602 complete data log recorded in the flash memory on the altimeter
2603 board. Once this data is on your computer, our post-flight tools make it
2604 easy to quickly get to the numbers everyone wants, like apogee altitude,
2605 max acceleration, and max velocity. You can also generate and view a
2606 standard set of plots showing the altitude, acceleration, and
2607 velocity of the rocket during flight. And you can even export a TeleMetrum data file
2608 usable with Google Maps and Google Earth for visualizing the flight path
2609 in two or three dimensions!
2612 Our ultimate goal is to emit a set of files for each flight that can be
2613 published as a web page per flight, or just viewed on your local disk with
2618 <title>Future Plans</title>
2620 In the future, we intend to offer “companion boards” for the rocket
2621 that will plug in to TeleMetrum to collect additional data, provide
2622 more pyro channels, and so forth.
2625 Also under design is a new flight computer with more sensors, more
2626 pyro channels, and a more powerful radio system designed for use
2627 in multi-stage, complex, and extreme altitude projects.
2630 We are also working on alternatives to TeleDongle. One is a
2631 a stand-alone, hand-held ground terminal that will allow monitoring
2632 the rocket's status, collecting data during flight, and logging data
2633 after flight without the need for a notebook computer on the
2634 flight line. Particularly since it is so difficult to read most
2635 notebook screens in direct sunlight, we think this will be a great
2636 thing to have. We are also working on a TeleDongle variant with
2637 Bluetooth that will work with Android phones and tablets.
2640 Because all of our work is open, both the hardware designs and the
2641 software, if you have some great idea for an addition to the current
2642 Altus Metrum family, feel free to dive in and help! Or let us know
2643 what you'd like to see that we aren't already working on, and maybe
2644 we'll get excited about it too...
2648 <ulink url="http://altusmetrum.org/">web site</ulink> for more news
2649 and information as our family of products evolves!
2654 <title>Altimeter Installation Recommendations</title>
2656 Building high-power rockets that fly safely is hard enough. Mix
2657 in some sophisticated electronics and a bunch of radio energy
2658 and oftentimes you find few perfect solutions. This chapter
2659 contains some suggestions about how to install Altus Metrum
2660 products into the rocket air-frame, including how to safely and
2661 reliably mix a variety of electronics into the same air-frame.
2664 <title>Mounting the Altimeter</title>
2666 The first consideration is to ensure that the altimeter is
2667 securely fastened to the air-frame. For TeleMetrum, we use
2668 nylon standoffs and nylon screws; they're good to at least 50G
2669 and cannot cause any electrical issues on the board. For
2670 TeleMini, we usually cut small pieces of 1/16 inch balsa to fit
2671 under the screw holes, and then take 2x56 nylon screws and
2672 screw them through the TeleMini mounting holes, through the
2673 balsa and into the underlying material.
2675 <orderedlist inheritnum='inherit' numeration='arabic'>
2678 Make sure TeleMetrum is aligned precisely along the axis of
2679 acceleration so that the accelerometer can accurately
2680 capture data during the flight.
2685 Watch for any metal touching components on the
2686 board. Shorting out connections on the bottom of the board
2687 can cause the altimeter to fail during flight.
2693 <title>Dealing with the Antenna</title>
2695 The antenna supplied is just a piece of solid, insulated,
2696 wire. If it gets damaged or broken, it can be easily
2697 replaced. It should be kept straight and not cut; bending or
2698 cutting it will change the resonant frequency and/or
2699 impedance, making it a less efficient radiator and thus
2700 reducing the range of the telemetry signal.
2703 Keeping metal away from the antenna will provide better range
2704 and a more even radiation pattern. In most rockets, it's not
2705 entirely possible to isolate the antenna from metal
2706 components; there are often bolts, all-thread and wires from other
2707 electronics to contend with. Just be aware that the more stuff
2708 like this around the antenna, the lower the range.
2711 Make sure the antenna is not inside a tube made or covered
2712 with conducting material. Carbon fiber is the most common
2713 culprit here -- CF is a good conductor and will effectively
2714 shield the antenna, dramatically reducing signal strength and
2715 range. Metallic flake paint is another effective shielding
2716 material which is to be avoided around any antennas.
2719 If the ebay is large enough, it can be convenient to simply
2720 mount the altimeter at one end and stretch the antenna out
2721 inside. Taping the antenna to the sled can keep it straight
2722 under acceleration. If there are metal rods, keep the
2723 antenna as far away as possible.
2726 For a shorter ebay, it's quite practical to have the antenna
2727 run through a bulkhead and into an adjacent bay. Drill a small
2728 hole in the bulkhead, pass the antenna wire through it and
2729 then seal it up with glue or clay. We've also used acrylic
2730 tubing to create a cavity for the antenna wire. This works a
2731 bit better in that the antenna is known to stay straight and
2732 not get folded by recovery components in the bay. Angle the
2733 tubing towards the side wall of the rocket and it ends up
2734 consuming very little space.
2737 If you need to place the antenna at a distance from the
2738 altimeter, you can replace the antenna with an edge-mounted
2739 SMA connector, and then run 50Ω coax from the board to the
2740 antenna. Building a remote antenna is beyond the scope of this
2745 <title>Preserving GPS Reception</title>
2747 The GPS antenna and receiver in TeleMetrum are highly
2748 sensitive and normally have no trouble tracking enough
2749 satellites to provide accurate position information for
2750 recovering the rocket. However, there are many ways to
2751 attenuate the GPS signal.
2752 <orderedlist inheritnum='inherit' numeration='arabic'>
2755 Conductive tubing or coatings. Carbon fiber and metal
2756 tubing, or metallic paint will all dramatically attenuate the
2757 GPS signal. We've never heard of anyone successfully
2758 receiving GPS from inside these materials.
2763 Metal components near the GPS patch antenna. These will
2764 de-tune the patch antenna, changing the resonant frequency
2765 away from the L1 carrier and reduce the effectiveness of the
2766 antenna. You can place as much stuff as you like beneath the
2767 antenna as that's covered with a ground plane. But, keep
2768 wires and metal out from above the patch antenna.
2775 <title>Radio Frequency Interference</title>
2777 Any altimeter will generate RFI; the digital circuits use
2778 high-frequency clocks that spray radio interference across a
2779 wide band. Altus Metrum altimeters generate intentional radio
2780 signals as well, increasing the amount of RF energy around the board.
2783 Rocketry altimeters also use precise sensors measuring air
2784 pressure and acceleration. Tiny changes in voltage can cause
2785 these sensor readings to vary by a huge amount. When the
2786 sensors start mis-reporting data, the altimeter can either
2787 fire the igniters at the wrong time, or not fire them at all.
2790 Voltages are induced when radio frequency energy is
2791 transmitted from one circuit to another. Here are things that
2792 influence the induced voltage and current:
2797 Keep wires from different circuits apart. Moving circuits
2798 further apart will reduce RFI.
2803 Avoid parallel wires from different circuits. The longer two
2804 wires run parallel to one another, the larger the amount of
2805 transferred energy. Cross wires at right angles to reduce
2811 Twist wires from the same circuits. Two wires the same
2812 distance from the transmitter will get the same amount of
2813 induced energy which will then cancel out. Any time you have
2814 a wire pair running together, twist the pair together to
2815 even out distances and reduce RFI. For altimeters, this
2816 includes battery leads, switch hookups and igniter
2822 Avoid resonant lengths. Know what frequencies are present
2823 in the environment and avoid having wire lengths near a
2824 natural resonant length. Altusmetrum products transmit on the
2825 70cm amateur band, so you should avoid lengths that are a
2826 simple ratio of that length; essentially any multiple of ¼
2827 of the wavelength (17.5cm).
2833 <title>The Barometric Sensor</title>
2835 Altusmetrum altimeters measure altitude with a barometric
2836 sensor, essentially measuring the amount of air above the
2837 rocket to figure out how high it is. A large number of
2838 measurements are taken as the altimeter initializes itself to
2839 figure out the pad altitude. Subsequent measurements are then
2840 used to compute the height above the pad.
2843 To accurately measure atmospheric pressure, the ebay
2844 containing the altimeter must be vented outside the
2845 air-frame. The vent must be placed in a region of linear
2846 airflow, have smooth edges, and away from areas of increasing or
2847 decreasing pressure.
2850 The barometric sensor in the altimeter is quite sensitive to
2851 chemical damage from the products of APCP or BP combustion, so
2852 make sure the ebay is carefully sealed from any compartment
2853 which contains ejection charges or motors.
2857 <title>Ground Testing</title>
2859 The most important aspect of any installation is careful
2860 ground testing. Bringing an air-frame up to the LCO table which
2861 hasn't been ground tested can lead to delays or ejection
2862 charges firing on the pad, or, even worse, a recovery system
2866 Do a 'full systems' test that includes wiring up all igniters
2867 without any BP and turning on all of the electronics in flight
2868 mode. This will catch any mistakes in wiring and any residual
2869 RFI issues that might accidentally fire igniters at the wrong
2870 time. Let the air-frame sit for several minutes, checking for
2871 adequate telemetry signal strength and GPS lock. If any igniters
2872 fire unexpectedly, find and resolve the issue before loading any
2876 Ground test the ejection charges. Prepare the rocket for
2877 flight, loading ejection charges and igniters. Completely
2878 assemble the air-frame and then use the 'Fire Igniters'
2879 interface through a TeleDongle to command each charge to
2880 fire. Make sure the charge is sufficient to robustly separate
2881 the air-frame and deploy the recovery system.
2886 <title>Updating Device Firmware</title>
2888 TeleMega, TeleMetrum v2 and EasyMini are all programmed directly
2889 over their USB connectors (self programming). TeleMetrum v1, TeleMini and
2890 TeleDongle are all programmed by using another device as a
2891 programmer (pair programming). It's important to recognize which
2892 kind of devices you have before trying to reprogram them.
2895 You may wish to begin by ensuring you have current firmware images.
2896 These are distributed as part of the AltOS software bundle that
2897 also includes the AltosUI ground station program. Newer ground
2898 station versions typically work fine with older firmware versions,
2899 so you don't need to update your devices just to try out new
2900 software features. You can always download the most recent
2901 version from <ulink url="http://www.altusmetrum.org/AltOS/"/>.
2904 We recommend updating the altimeter first, before updating TeleDongle.
2907 Self-programmable devices (TeleMega, TeleMetrum v2 and EasyMini)
2908 are reprogrammed by connecting them to your computer over USB
2912 Updating TeleMega, TeleMetrum v2 or EasyMini Firmware
2914 <orderedlist inheritnum='inherit' numeration='arabic'>
2917 Attach a battery and power switch to the target
2918 device. Power up the device.
2923 Using a Micro USB cable, connect the target device to your
2924 computer's USB socket.
2929 Run AltosUI, and select 'Flash Image' from the File menu.
2934 Select the target device in the Device Selection dialog.
2939 Select the image you want to flash to the device, which
2940 should have a name in the form
2941 <product>-v<product-version>-<software-version>.ihx, such
2942 as TeleMega-v1.0-1.3.0.ihx.
2947 Make sure the configuration parameters are reasonable
2948 looking. If the serial number and/or RF configuration
2949 values aren't right, you'll need to change them.
2954 Hit the 'OK' button and the software should proceed to flash
2955 the device with new firmware, showing a progress bar.
2960 Verify that the device is working by using the 'Configure
2961 Altimeter' item to check over the configuration.
2966 <title>Recovering From Self-Flashing Failure</title>
2968 If the firmware loading fails, it can leave the device
2969 unable to boot. Not to worry, you can force the device to
2970 start the boot loader instead, which will let you try to
2971 flash the device again.
2974 On each device, connecting two pins from one of the exposed
2975 connectors will force the boot loader to start, even if the
2976 regular operating system has been corrupted in some way.
2980 <term>TeleMega</term>
2983 Connect pin 6 and pin 1 of the companion connector. Pin 1
2984 can be identified by the square pad around it, and then
2985 the pins could sequentially across the board. Be very
2986 careful to <emphasis>not</emphasis> short pin 8 to
2987 anything as that is connected directly to the battery. Pin
2988 7 carries 3.3V and the board will crash if that is
2989 connected to pin 1, but shouldn't damage the board.
2994 <term>TeleMetrum v2</term>
2997 Connect pin 6 and pin 1 of the companion connector. Pin 1
2998 can be identified by the square pad around it, and then
2999 the pins could sequentially across the board. Be very
3000 careful to <emphasis>not</emphasis> short pin 8 to
3001 anything as that is connected directly to the battery. Pin
3002 7 carries 3.3V and the board will crash if that is
3003 connected to pin 1, but shouldn't damage the board.
3008 <term>EasyMini</term>
3011 Connect pin 6 and pin 1 of the debug connector, which is
3012 the six holes next to the beeper. Pin 1 can be identified
3013 by the square pad around it, and then the pins could
3014 sequentially across the board, making Pin 6 the one on the
3015 other end of the row.
3023 <title>Pair Programming</title>
3025 The big concept to understand is that you have to use a
3026 TeleMega, TeleMetrum or TeleDongle as a programmer to update a
3027 pair programmed device. Due to limited memory resources in the
3028 cc1111, we don't support programming directly over USB for these
3033 <title>Updating TeleMetrum v1.x Firmware</title>
3034 <orderedlist inheritnum='inherit' numeration='arabic'>
3037 Find the 'programming cable' that you got as part of the starter
3038 kit, that has a red 8-pin MicroMaTch connector on one end and a
3039 red 4-pin MicroMaTch connector on the other end.
3044 Take the 2 screws out of the TeleDongle case to get access
3045 to the circuit board.
3050 Plug the 8-pin end of the programming cable to the
3051 matching connector on the TeleDongle, and the 4-pin end to the
3052 matching connector on the TeleMetrum.
3053 Note that each MicroMaTch connector has an alignment pin that
3054 goes through a hole in the PC board when you have the cable
3060 Attach a battery to the TeleMetrum board.
3065 Plug the TeleDongle into your computer's USB port, and power
3071 Run AltosUI, and select 'Flash Image' from the File menu.
3076 Pick the TeleDongle device from the list, identifying it as the
3082 Select the image you want put on the TeleMetrum, which should have a
3083 name in the form telemetrum-v1.2-1.0.0.ihx. It should be visible
3084 in the default directory, if not you may have to poke around
3085 your system to find it.
3090 Make sure the configuration parameters are reasonable
3091 looking. If the serial number and/or RF configuration
3092 values aren't right, you'll need to change them.
3097 Hit the 'OK' button and the software should proceed to flash
3098 the TeleMetrum with new firmware, showing a progress bar.
3103 Confirm that the TeleMetrum board seems to have updated OK, which you
3104 can do by plugging in to it over USB and using a terminal program
3105 to connect to the board and issue the 'v' command to check
3111 If something goes wrong, give it another try.
3117 <title>Updating TeleMini Firmware</title>
3118 <orderedlist inheritnum='inherit' numeration='arabic'>
3121 You'll need a special 'programming cable' to reprogram the
3122 TeleMini. It's available on the Altus Metrum web store, or
3123 you can make your own using an 8-pin MicroMaTch connector on
3124 one end and a set of four pins on the other.
3129 Take the 2 screws out of the TeleDongle case to get access
3130 to the circuit board.
3135 Plug the 8-pin end of the programming cable to the matching
3136 connector on the TeleDongle, and the 4-pins into the holes
3137 in the TeleMini circuit board. Note that the MicroMaTch
3138 connector has an alignment pin that goes through a hole in
3139 the PC board when you have the cable oriented correctly, and
3140 that pin 1 on the TeleMini board is marked with a square pad
3141 while the other pins have round pads.
3146 Attach a battery to the TeleMini board.
3151 Plug the TeleDongle into your computer's USB port, and power
3157 Run AltosUI, and select 'Flash Image' from the File menu.
3162 Pick the TeleDongle device from the list, identifying it as the
3168 Select the image you want put on the TeleMini, which should have a
3169 name in the form telemini-v1.0-1.0.0.ihx. It should be visible
3170 in the default directory, if not you may have to poke around
3171 your system to find it.
3176 Make sure the configuration parameters are reasonable
3177 looking. If the serial number and/or RF configuration
3178 values aren't right, you'll need to change them.
3183 Hit the 'OK' button and the software should proceed to flash
3184 the TeleMini with new firmware, showing a progress bar.
3189 Confirm that the TeleMini board seems to have updated OK, which you
3190 can do by configuring it over the radio link through the TeleDongle, or
3191 letting it come up in “flight” mode and listening for telemetry.
3196 If something goes wrong, give it another try.
3202 <title>Updating TeleDongle Firmware</title>
3204 Updating TeleDongle's firmware is just like updating TeleMetrum or TeleMini
3205 firmware, but you use either a TeleMetrum or another TeleDongle as the programmer.
3207 <orderedlist inheritnum='inherit' numeration='arabic'>
3210 Find the 'programming cable' that you got as part of the starter
3211 kit, that has a red 8-pin MicroMaTch connector on one end and a
3212 red 4-pin MicroMaTch connector on the other end.
3217 Find the USB cable that you got as part of the starter kit, and
3218 plug the “mini” end in to the mating connector on TeleMetrum or TeleDongle.
3223 Take the 2 screws out of the TeleDongle case to get access
3224 to the circuit board.
3229 Plug the 8-pin end of the programming cable to the
3230 matching connector on the programmer, and the 4-pin end to the
3231 matching connector on the TeleDongle.
3232 Note that each MicroMaTch connector has an alignment pin that
3233 goes through a hole in the PC board when you have the cable
3239 Attach a battery to the TeleMetrum board if you're using one.
3244 Plug both the programmer and the TeleDongle into your computer's USB
3245 ports, and power up the programmer.
3250 Run AltosUI, and select 'Flash Image' from the File menu.
3255 Pick the programmer device from the list, identifying it as the
3261 Select the image you want put on the TeleDongle, which should have a
3262 name in the form teledongle-v0.2-1.0.0.ihx. It should be visible
3263 in the default directory, if not you may have to poke around
3264 your system to find it.
3269 Make sure the configuration parameters are reasonable
3270 looking. If the serial number and/or RF configuration
3271 values aren't right, you'll need to change them. The TeleDongle
3272 serial number is on the “bottom” of the circuit board, and can
3273 usually be read through the translucent blue plastic case without
3274 needing to remove the board from the case.
3279 Hit the 'OK' button and the software should proceed to flash
3280 the TeleDongle with new firmware, showing a progress bar.
3285 Confirm that the TeleDongle board seems to have updated OK, which you
3286 can do by plugging in to it over USB and using a terminal program
3287 to connect to the board and issue the 'v' command to check
3288 the version, etc. Once you're happy, remove the programming cable
3289 and put the cover back on the TeleDongle.
3294 If something goes wrong, give it another try.
3299 Be careful removing the programming cable from the locking 8-pin
3300 connector on TeleMetrum. You'll need a fingernail or perhaps a thin
3301 screwdriver or knife blade to gently pry the locking ears out
3302 slightly to extract the connector. We used a locking connector on
3303 TeleMetrum to help ensure that the cabling to companion boards
3304 used in a rocket don't ever come loose accidentally in flight.
3309 <title>Hardware Specifications</title>
3312 TeleMega Specifications
3317 Recording altimeter for model rocketry.
3322 Supports dual deployment and four auxiliary pyro channels
3323 (a total of 6 events).
3328 70cm 40mW ham-band transceiver for telemetry down-link.
3333 Barometric pressure sensor good to 100k feet MSL.
3338 1-axis high-g accelerometer for motor characterization, capable of
3344 9-axis IMU including integrated 3-axis accelerometer,
3345 3-axis gyroscope and 3-axis magnetometer.
3350 On-board, integrated uBlox Max 7 GPS receiver with 5Hz update rate capability.
3355 On-board 8 Megabyte non-volatile memory for flight data storage.
3360 USB interface for battery charging, configuration, and data recovery.
3365 Fully integrated support for Li-Po rechargeable batteries.
3370 Uses Li-Po to fire e-matches, can be modified to support
3371 optional separate pyro battery if needed.
3376 3.25 x 1.25 inch board designed to fit inside 38mm air-frame coupler tube.
3383 TeleMetrum v2 Specifications
3388 Recording altimeter for model rocketry.
3393 Supports dual deployment (can fire 2 ejection charges).
3398 70cm, 40mW ham-band transceiver for telemetry down-link.
3403 Barometric pressure sensor good to 100k feet MSL.
3408 1-axis high-g accelerometer for motor characterization, capable of
3414 On-board, integrated uBlox Max 7 GPS receiver with 5Hz update rate capability.
3419 On-board 8 Megabyte non-volatile memory for flight data storage.
3424 USB interface for battery charging, configuration, and data recovery.
3429 Fully integrated support for Li-Po rechargeable batteries.
3434 Uses Li-Po to fire e-matches, can be modified to support
3435 optional separate pyro battery if needed.
3440 2.75 x 1 inch board designed to fit inside 29mm air-frame coupler tube.
3446 <title>TeleMetrum v1 Specifications</title>
3450 Recording altimeter for model rocketry.
3455 Supports dual deployment (can fire 2 ejection charges).
3460 70cm, 10mW ham-band transceiver for telemetry down-link.
3465 Barometric pressure sensor good to 45k feet MSL.
3470 1-axis high-g accelerometer for motor characterization, capable of
3471 +/- 50g using default part.
3476 On-board, integrated GPS receiver with 5Hz update rate capability.
3481 On-board 1 megabyte non-volatile memory for flight data storage.
3486 USB interface for battery charging, configuration, and data recovery.
3491 Fully integrated support for Li-Po rechargeable batteries.
3496 Uses Li-Po to fire e-matches, can be modified to support
3497 optional separate pyro battery if needed.
3502 2.75 x 1 inch board designed to fit inside 29mm air-frame coupler tube.
3509 TeleMini v2.0 Specifications
3514 Recording altimeter for model rocketry.
3519 Supports dual deployment (can fire 2 ejection charges).
3524 70cm, 10mW ham-band transceiver for telemetry down-link.
3529 Barometric pressure sensor good to 100k feet MSL.
3534 On-board 1 megabyte non-volatile memory for flight data storage.
3539 USB interface for configuration, and data recovery.
3544 Support for Li-Po rechargeable batteries (using an
3545 external charger), or any 3.7-15V external battery.
3550 Uses Li-Po to fire e-matches, can be modified to support
3551 optional separate pyro battery if needed.
3556 1.5 x .8 inch board designed to fit inside 24mm air-frame coupler tube.
3563 TeleMini v1.0 Specifications
3568 Recording altimeter for model rocketry.
3573 Supports dual deployment (can fire 2 ejection charges).
3578 70cm, 10mW ham-band transceiver for telemetry down-link.
3583 Barometric pressure sensor good to 45k feet MSL.
3588 On-board 5 kilobyte non-volatile memory for flight data storage.
3593 RF interface for configuration, and data recovery.
3598 Support for Li-Po rechargeable batteries, using an external charger.
3603 Uses Li-Po to fire e-matches, can be modified to support
3604 optional separate pyro battery if needed.
3609 1.5 x .5 inch board designed to fit inside 18mm air-frame coupler tube.
3616 EasyMini Specifications
3621 Recording altimeter for model rocketry.
3626 Supports dual deployment (can fire 2 ejection charges).
3631 Barometric pressure sensor good to 100k feet MSL.
3636 On-board 1 megabyte non-volatile memory for flight data storage.
3641 USB interface for configuration, and data recovery.
3646 Support for Li-Po rechargeable batteries (using an
3647 external charger), or any 3.7-15V external battery.
3652 Uses Li-Po to fire e-matches, can be modified to support
3653 optional separate pyro battery if needed.
3658 1.5 x .8 inch board designed to fit inside 24mm air-frame coupler tube.
3667 TeleMetrum seems to shut off when disconnected from the
3668 computer. Make sure the battery is adequately charged. Remember the
3669 unit will pull more power than the USB port can deliver before the
3670 GPS enters “locked” mode. The battery charges best when TeleMetrum
3674 It's impossible to stop the TeleDongle when it's in “p” mode, I have
3675 to unplug the USB cable? Make sure you have tried to “escape out” of
3676 this mode. If this doesn't work the reboot procedure for the
3677 TeleDongle *is* to simply unplug it. 'cu' however will retain it's
3678 outgoing buffer IF your “escape out” ('~~') does not work.
3679 At this point using either 'ao-view' (or possibly
3680 'cutemon') instead of 'cu' will 'clear' the issue and allow renewed
3684 The amber LED (on the TeleMetrum) lights up when both
3685 battery and USB are connected. Does this mean it's charging?
3686 Yes, the yellow LED indicates the charging at the 'regular' rate.
3687 If the led is out but the unit is still plugged into a USB port,
3688 then the battery is being charged at a 'trickle' rate.
3691 There are no “dit-dah-dah-dit” sound or lights like the manual mentions?
3692 That's the “pad” mode. Weak batteries might be the problem.
3693 It is also possible that the TeleMetrum is horizontal and the output
3694 is instead a “dit-dit” meaning 'idle'. For TeleMini, it's possible that
3695 it received a command packet which would have left it in “pad” mode.
3698 How do I save flight data?
3699 Live telemetry is written to file(s) whenever AltosUI is connected
3700 to the TeleDongle. The file area defaults to ~/TeleMetrum
3701 but is easily changed using the menus in AltosUI. The files that
3702 are written end in '.telem'. The after-flight
3703 data-dumped files will end in .eeprom and represent continuous data
3704 unlike the .telem files that are subject to losses
3705 along the RF data path.
3706 See the above instructions on what and how to save the eeprom stored
3707 data after physically retrieving your altimeter. Make sure to save
3708 the on-board data after each flight; while the TeleMetrum can store
3709 multiple flights, you never know when you'll lose the altimeter...
3713 <title>Notes for Older Software</title>
3716 Before AltosUI was written, using Altus Metrum devices required
3717 some finesse with the Linux command line. There was a limited
3718 GUI tool, ao-view, which provided functionality similar to the
3719 Monitor Flight window in AltosUI, but everything else was a
3720 fairly 80's experience. This appendix includes documentation for
3721 using that software.
3725 Both TeleMetrum and TeleDongle can be directly communicated
3726 with using USB ports. The first thing you should try after getting
3727 both units plugged into to your computer's USB port(s) is to run
3728 'ao-list' from a terminal-window to see what port-device-name each
3729 device has been assigned by the operating system.
3730 You will need this information to access the devices via their
3731 respective on-board firmware and data using other command line
3732 programs in the AltOS software suite.
3735 TeleMini can be communicated with through a TeleDongle device
3736 over the radio link. When first booted, TeleMini listens for a
3737 TeleDongle device and if it receives a packet, it goes into
3738 'idle' mode. Otherwise, it goes into 'pad' mode and waits to be
3739 launched. The easiest way to get it talking is to start the
3740 communication link on the TeleDongle and the power up the
3744 To access the device's firmware for configuration you need a terminal
3745 program such as you would use to talk to a modem. The software
3746 authors prefer using the program 'cu' which comes from the UUCP package
3747 on most Unix-like systems such as Linux. An example command line for
3748 cu might be 'cu -l /dev/ttyACM0', substituting the correct number
3749 indicated from running the
3750 ao-list program. Another reasonable terminal program for Linux is
3751 'cutecom'. The default 'escape'
3752 character used by CU (i.e. the character you use to
3753 issue commands to cu itself instead of sending the command as input
3754 to the connected device) is a '~'. You will need this for use in
3755 only two different ways during normal operations. First is to exit
3756 the program by sending a '~.' which is called a 'escape-disconnect'
3757 and allows you to close-out from 'cu'. The
3758 second use will be outlined later.
3761 All of the Altus Metrum devices share the concept of a two level
3762 command set in their firmware.
3763 The first layer has several single letter commands. Once
3764 you are using 'cu' (or 'cutecom') sending (typing) a '?'
3765 returns a full list of these
3766 commands. The second level are configuration sub-commands accessed
3767 using the 'c' command, for
3768 instance typing 'c?' will give you this second level of commands
3769 (all of which require the
3770 letter 'c' to access). Please note that most configuration options
3771 are stored only in Flash memory; TeleDongle doesn't provide any storage
3772 for these options and so they'll all be lost when you unplug it.
3775 Try setting these configuration ('c' or second level menu) values. A good
3776 place to start is by setting your call sign. By default, the boards
3777 use 'N0CALL' which is cute, but not exactly legal!
3778 Spend a few minutes getting comfortable with the units, their
3779 firmware, and 'cu' (or possibly 'cutecom').
3780 For instance, try to send
3781 (type) a 'c r 2' and verify the channel change by sending a 'c s'.
3782 Verify you can connect and disconnect from the units while in your
3783 terminal program by sending the escape-disconnect mentioned above.
3786 To set the radio frequency, use the 'c R' command to specify the
3787 radio transceiver configuration parameter. This parameter is computed
3788 using the desired frequency, 'F', the radio calibration parameter, 'C' (showed by the 'c s' command) and
3789 the standard calibration reference frequency, 'S', (normally 434.550MHz):
3793 Round the result to the nearest integer value.
3794 As with all 'c' sub-commands, follow this with a 'c w' to write the
3795 change to the parameter block in the on-board flash on
3796 your altimeter board if you want the change to stay in place across reboots.
3799 To set the apogee delay, use the 'c d' command.
3800 As with all 'c' sub-commands, follow this with a 'c w' to write the
3801 change to the parameter block in the on-board DataFlash chip.
3804 To set the main deployment altitude, use the 'c m' command.
3805 As with all 'c' sub-commands, follow this with a 'c w' to write the
3806 change to the parameter block in the on-board DataFlash chip.
3809 To calibrate the radio frequency, connect the UHF antenna port to a
3810 frequency counter, set the board to 434.550MHz, and use the 'C'
3811 command to generate a CW carrier. Wait for the transmitter temperature
3812 to stabilize and the frequency to settle down.
3813 Then, divide 434.550 MHz by the
3814 measured frequency and multiply by the current radio cal value show
3815 in the 'c s' command. For an unprogrammed board, the default value
3816 is 1186611. Take the resulting integer and program it using the 'c f'
3817 command. Testing with the 'C' command again should show a carrier
3818 within a few tens of Hertz of the intended frequency.
3819 As with all 'c' sub-commands, follow this with a 'c w' to write the
3820 change to the parameter block in the on-board DataFlash chip.
3823 Note that the 'reboot' command, which is very useful on the altimeters,
3824 will likely just cause problems with the dongle. The *correct* way
3825 to reset the dongle is just to unplug and re-plug it.
3828 A fun thing to do at the launch site and something you can do while
3829 learning how to use these units is to play with the radio link access
3830 between an altimeter and the TeleDongle. Be aware that you *must* create
3831 some physical separation between the devices, otherwise the link will
3832 not function due to signal overload in the receivers in each device.
3835 Now might be a good time to take a break and read the rest of this
3836 manual, particularly about the two “modes” that the altimeters
3837 can be placed in. TeleMetrum uses the position of the device when booting
3838 up will determine whether the unit is in “pad” or “idle” mode. TeleMini
3839 enters “idle” mode when it receives a command packet within the first 5 seconds
3840 of being powered up, otherwise it enters “pad” mode.
3843 You can access an altimeter in idle mode from the TeleDongle's USB
3844 connection using the radio link
3845 by issuing a 'p' command to the TeleDongle. Practice connecting and
3846 disconnecting ('~~' while using 'cu') from the altimeter. If
3847 you cannot escape out of the “p” command, (by using a '~~' when in
3848 CU) then it is likely that your kernel has issues. Try a newer version.
3851 Using this radio link allows you to configure the altimeter, test
3852 fire e-matches and igniters from the flight line, check pyro-match
3853 continuity and so forth. You can leave the unit turned on while it
3854 is in 'idle mode' and then place the
3855 rocket vertically on the launch pad, walk away and then issue a
3856 reboot command. The altimeter will reboot and start sending data
3857 having changed to the “pad” mode. If the TeleDongle is not receiving
3858 this data, you can disconnect 'cu' from the TeleDongle using the
3859 procedures mentioned above and THEN connect to the TeleDongle from
3860 inside 'ao-view'. If this doesn't work, disconnect from the
3861 TeleDongle, unplug it, and try again after plugging it back in.
3864 In order to reduce the chance of accidental firing of pyrotechnic
3865 charges, the command to fire a charge is intentionally somewhat
3866 difficult to type, and the built-in help is slightly cryptic to
3867 prevent accidental echoing of characters from the help text back at
3868 the board from firing a charge. The command to fire the apogee
3869 drogue charge is 'i DoIt drogue' and the command to fire the main
3870 charge is 'i DoIt main'.
3873 On TeleMetrum, the GPS will eventually find enough satellites, lock in on them,
3874 and 'ao-view' will both auditorily announce and visually indicate
3876 Now you can launch knowing that you have a good data path and
3877 good satellite lock for flight data and recovery. Remember
3878 you MUST tell ao-view to connect to the TeleDongle explicitly in
3879 order for ao-view to be able to receive data.
3882 The altimeters provide RDF (radio direction finding) tones on
3883 the pad, during descent and after landing. These can be used to
3884 locate the rocket using a directional antenna; the signal
3885 strength providing an indication of the direction from receiver to rocket.
3888 TeleMetrum also provides GPS tracking data, which can further simplify
3889 locating the rocket once it has landed. (The last good GPS data
3890 received before touch-down will be on the data screen of 'ao-view'.)
3893 Once you have recovered the rocket you can download the eeprom
3894 contents using either 'ao-dumplog' (or possibly 'ao-eeprom'), over
3895 either a USB cable or over the radio link using TeleDongle.
3896 And by following the man page for 'ao-postflight' you can create
3897 various data output reports, graphs, and even KML data to see the
3898 flight trajectory in Google-earth. (Moving the viewing angle making
3899 sure to connect the yellow lines while in Google-earth is the proper
3903 As for ao-view.... some things are in the menu but don't do anything
3904 very useful. The developers have stopped working on ao-view to focus
3905 on a new, cross-platform ground station program. So ao-view may or
3906 may not be updated in the future. Mostly you just use
3907 the Log and Device menus. It has a wonderful display of the incoming
3908 flight data and I am sure you will enjoy what it has to say to you
3909 once you enable the voice output!
3913 <title>Drill Templates</title>
3915 These images, when printed, provide precise templates for the
3916 mounting holes in Altus Metrum flight computers
3919 <title>TeleMega template</title>
3921 TeleMega has overall dimensions of 1.250 x 3.250 inches, and
3922 the mounting holes are sized for use with 4-40 or M3 screws.
3924 <mediaobject id="TeleMegaTemplate">
3926 <imagedata format="SVG" fileref="telemega-outline.svg"/>
3931 <title>TeleMetrum template</title>
3933 TeleMetrum has overall dimensions of 1.000 x 2.750 inches, and the
3934 mounting holes are sized for use with 4-40 or M3 screws.
3936 <mediaobject id="TeleMetrumTemplate">
3938 <imagedata format="SVG" fileref="telemetrum.svg"/>
3943 <title>TeleMini v2/EasyMini template</title>
3945 TeleMini v2 and EasyMini have overall dimensions of 0.800 x 1.500 inches, and the
3946 mounting holes are sized for use with 4-40 or M3 screws.
3948 <mediaobject id="MiniTemplate">
3950 <imagedata format="SVG" fileref="easymini-outline.svg"/>
3955 <title>TeleMini v1 template</title>
3957 TeleMini has overall dimensions of 0.500 x 1.500 inches, and the
3958 mounting holes are sized for use with 2-56 or M2 screws.
3960 <mediaobject id="TeleMiniTemplate">
3962 <imagedata format="SVG" fileref="telemini.svg"/>
3968 <title>Calibration</title>
3970 There are only two calibrations required for TeleMetrum and
3971 TeleMega, and only one for TeleDongle, TeleMini and EasyMini.
3972 All boards are shipped from the factory pre-calibrated, but
3973 the procedures are documented here in case they are ever
3974 needed. Re-calibration is not supported by AltosUI, you must
3975 connect to the board with a serial terminal program and
3976 interact directly with the on-board command interpreter to
3980 <title>Radio Frequency</title>
3982 The radio frequency is synthesized from a clock based on the
3983 crystal on the board. The actual frequency of this oscillator
3984 must be measured to generate a calibration constant. While our
3986 bandwidth is wide enough to allow boards to communicate even when
3987 their oscillators are not on exactly the same frequency, performance
3988 is best when they are closely matched.
3989 Radio frequency calibration requires a calibrated frequency counter.
3990 Fortunately, once set, the variation in frequency due to aging and
3991 temperature changes is small enough that re-calibration by customers
3992 should generally not be required.
3995 To calibrate the radio frequency, connect the UHF antenna
3996 port to a frequency counter, set the board to 434.550MHz,
3997 and use the 'C' command in the on-board command interpreter
3998 to generate a CW carrier. For USB-enabled boards, this is
3999 best done over USB. For TeleMini v1, note that the only way
4000 to escape the 'C' command is via power cycle since the board
4001 will no longer be listening for commands once it starts
4002 generating a CW carrier.
4005 Wait for the transmitter temperature to stabilize and the frequency
4006 to settle down. Then, divide 434.550 MHz by the
4007 measured frequency and multiply by the current radio cal value show
4008 in the 'c s' command. For an unprogrammed board, the default value
4009 is 1186611. Take the resulting integer and program it using the 'c f'
4010 command. Testing with the 'C' command again should show a carrier
4011 within a few tens of Hertz of the intended frequency.
4012 As with all 'c' sub-commands, follow this with a 'c w' to write the
4013 change to the parameter block in the on-board storage chip.
4016 Note that any time you re-do the radio frequency calibration, the
4017 radio frequency is reset to the default 434.550 Mhz. If you want
4018 to use another frequency, you will have to set that again after
4019 calibration is completed.
4023 <title>TeleMetrum and TeleMega Accelerometers</title>
4025 While barometric sensors are factory-calibrated,
4026 accelerometers are not, and so each must be calibrated once
4027 installed in a flight computer. Explicitly calibrating the
4028 accelerometers also allows us to load any compatible device.
4029 We perform a two-point calibration using gravity.
4032 To calibrate the acceleration sensor, use the 'c a 0' command. You
4033 will be prompted to orient the board vertically with the UHF antenna
4034 up and press a key, then to orient the board vertically with the
4035 UHF antenna down and press a key. Note that the accuracy of this
4036 calibration depends primarily on how perfectly vertical and still
4037 the board is held during the cal process. As with all 'c'
4038 sub-commands, follow this with a 'c w' to write the
4039 change to the parameter block in the on-board DataFlash chip.
4042 The +1g and -1g calibration points are included in each telemetry
4043 frame and are part of the header stored in onboard flash to be
4044 downloaded after flight. We always store and return raw ADC
4045 samples for each sensor... so nothing is permanently “lost” or
4046 “damaged” if the calibration is poor.
4049 In the unlikely event an accel cal goes badly, it is possible
4050 that TeleMetrum or TeleMega may always come up in 'pad mode'
4051 and as such not be listening to either the USB or radio link.
4052 If that happens, there is a special hook in the firmware to
4053 force the board back in to 'idle mode' so you can re-do the
4054 cal. To use this hook, you just need to ground the SPI clock
4055 pin at power-on. This pin is available as pin 2 on the 8-pin
4056 companion connector, and pin 1 is ground. So either
4057 carefully install a fine-gauge wire jumper between the two
4058 pins closest to the index hole end of the 8-pin connector, or
4059 plug in the programming cable to the 8-pin connector and use
4060 a small screwdriver or similar to short the two pins closest
4061 to the index post on the 4-pin end of the programming cable,
4062 and power up the board. It should come up in 'idle mode'
4063 (two beeps), allowing a re-cal.
4068 <title>Release Notes</title>
4070 <title>Version 1.3</title>
4072 xmlns:xi="http://www.w3.org/2001/XInclude"
4073 href="release-notes-1.3.xsl"
4074 xpointer="xpointer(/article/*)"/>
4077 <title>Version 1.2.1</title>
4079 xmlns:xi="http://www.w3.org/2001/XInclude"
4080 href="release-notes-1.2.1.xsl"
4081 xpointer="xpointer(/article/*)"/>
4084 <title>Version 1.2</title>
4086 xmlns:xi="http://www.w3.org/2001/XInclude"
4087 href="release-notes-1.2.xsl"
4088 xpointer="xpointer(/article/*)"/>
4091 <title>Version 1.1.1</title>
4093 xmlns:xi="http://www.w3.org/2001/XInclude"
4094 href="release-notes-1.1.1.xsl"
4095 xpointer="xpointer(/article/*)"/>
4098 <title>Version 1.1</title>
4100 xmlns:xi="http://www.w3.org/2001/XInclude"
4101 href="release-notes-1.1.xsl"
4102 xpointer="xpointer(/article/*)"/>
4105 <title>Version 1.0.1</title>
4107 xmlns:xi="http://www.w3.org/2001/XInclude"
4108 href="release-notes-1.0.1.xsl"
4109 xpointer="xpointer(/article/*)"/>
4112 <title>Version 0.9.2</title>
4114 xmlns:xi="http://www.w3.org/2001/XInclude"
4115 href="release-notes-0.9.2.xsl"
4116 xpointer="xpointer(/article/*)"/>
4119 <title>Version 0.9</title>
4121 xmlns:xi="http://www.w3.org/2001/XInclude"
4122 href="release-notes-0.9.xsl"
4123 xpointer="xpointer(/article/*)"/>
4126 <title>Version 0.8</title>
4128 xmlns:xi="http://www.w3.org/2001/XInclude"
4129 href="release-notes-0.8.xsl"
4130 xpointer="xpointer(/article/*)"/>
4133 <title>Version 0.7.1</title>
4135 xmlns:xi="http://www.w3.org/2001/XInclude"
4136 href="release-notes-0.7.1.xsl"
4137 xpointer="xpointer(/article/*)"/>
4142 <!-- LocalWords: Altusmetrum
projects / fw / altos / blob