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 TeleMetrum, TeleMini and TeleDongle Devices</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.1.1</revnumber>
40 <date>16 September 2012</date>
42 Updated for software version 1.1.1 Version 1.1.1 fixes a few
43 bugs found in version 1.1.
47 <revnumber>1.1</revnumber>
48 <date>13 September 2012</date>
50 Updated for software version 1.1. Version 1.1 has new
51 features but is otherwise compatible with version 1.0.
55 <revnumber>1.0</revnumber>
56 <date>24 August 2011</date>
58 Updated for software version 1.0. Note that 1.0 represents a
59 telemetry format change, meaning both ends of a link
60 (TeleMetrum/TeleMini and TeleDongle) must be updated or
61 communications will fail.
65 <revnumber>0.9</revnumber>
66 <date>18 January 2011</date>
68 Updated for software version 0.9. Note that 0.9 represents a
69 telemetry format change, meaning both ends of a link (TeleMetrum and
70 TeleDongle) must be updated or communications will fail.
74 <revnumber>0.8</revnumber>
75 <date>24 November 2010</date>
76 <revremark>Updated for software version 0.8 </revremark>
82 Thanks to Bob Finch, W9YA, NAR 12965, TRA 12350 for writing "The
83 Mere-Mortals Quick Start/Usage Guide to the Altus Metrum Starter
84 Kit" which formed the basis of the original Getting Started chapter
85 in this manual. Bob was one of our first customers for a production
86 TeleMetrum, and his continued enthusiasm and contributions
87 are immensely gratifying and highly appreciated!
90 And thanks to Anthony (AJ) Towns for major contributions including
91 the AltosUI graphing and site map code and associated documentation.
92 Free software means that our customers and friends can become our
93 collaborators, and we certainly appreciate this level of
97 Have fun using these products, and we hope to meet all of you
98 out on the rocket flight line somewhere.
101 NAR #87103, TRA #12201
103 Keith Packard, KD7SQG
104 NAR #88757, TRA #12200
109 <title>Introduction and Overview</title>
111 Welcome to the Altus Metrum community! Our circuits and software reflect
112 our passion for both hobby rocketry and Free Software. We hope their
113 capabilities and performance will delight you in every way, but by
114 releasing all of our hardware and software designs under open licenses,
115 we also hope to empower you to take as active a role in our collective
119 The first device created for our community was TeleMetrum, a dual
120 deploy altimeter with fully integrated GPS and radio telemetry
121 as standard features, and a "companion interface" that will
122 support optional capabilities in the future.
125 The newest device is TeleMini, a dual deploy altimeter with
126 radio telemetry and radio direction finding. This device is only
127 13mm by 38mm (½ inch by 1½ inches) and can fit easily in an 18mm
131 Complementing TeleMetrum and TeleMini is TeleDongle, a USB to RF
132 interface for communicating with the altimeters. Combined with your
133 choice of antenna and
134 notebook computer, TeleDongle and our associated user interface software
135 form a complete ground station capable of logging and displaying in-flight
136 telemetry, aiding rocket recovery, then processing and archiving flight
137 data for analysis and review.
140 More products will be added to the Altus Metrum family over time, and
141 we currently envision that this will be a single, comprehensive manual
142 for the entire product family.
146 <title>Getting Started</title>
148 The first thing to do after you check the inventory of parts in your
149 "starter kit" is to charge the battery.
152 The TeleMetrum battery can be charged by plugging it into the
153 corresponding socket of the TeleMetrum and then using the USB A to
155 cable to plug the TeleMetrum into your computer's USB socket. The
156 TeleMetrum circuitry will charge the battery whenever it is plugged
157 in, because the TeleMetrum's on-off switch does NOT control the
161 When the GPS chip is initially searching for
162 satellites, TeleMetrum will consume more current than it can pull
163 from the USB port, so the battery must be attached in order to get
164 satellite lock. Once GPS is locked, the current consumption goes back
165 down enough to enable charging while
166 running. So it's a good idea to fully charge the battery as your
167 first item of business so there is no issue getting and maintaining
168 satellite lock. The yellow charge indicator led will go out when the
169 battery is nearly full and the charger goes to trickle charge. It
170 can take several hours to fully recharge a deeply discharged battery.
173 The TeleMini battery can be charged by disconnecting it from the
174 TeleMini board and plugging it into a standalone battery charger
175 board, and connecting that via a USB cable to a laptop or other USB
179 The other active device in the starter kit is the TeleDongle USB to
180 RF interface. If you plug it in to your Mac or Linux computer it should
181 "just work", showing up as a serial port device. Windows systems need
182 driver information that is part of the AltOS download to know that the
183 existing USB modem driver will work. We therefore recommend installing
184 our software before plugging in TeleDongle if you are using a Windows
185 computer. If you are using Linux and are having problems, try moving
186 to a fresher kernel (2.6.33 or newer), as the USB serial driver had
187 ugly bugs in some earlier versions.
190 Next you should obtain and install the AltOS software. These include
191 the AltosUI ground station program, current firmware images for
192 TeleMetrum, TeleMini and TeleDongle, and a number of standalone
193 utilities that are rarely needed. Pre-built binary packages are
194 available for Linux, Microsoft Windows, and recent MacOSX versions.
195 Full source code and build instructions are also available.
196 The latest version may always be downloaded from
197 <ulink url="http://altusmetrum.org/AltOS"/>.
201 <title>Handling Precautions</title>
203 All Altus Metrum products are sophisticated electronic devices.
204 When handled gently and properly installed in an air-frame, they
205 will deliver impressive results. However, as with all electronic
206 devices, there are some precautions you must take.
209 The Lithium Polymer rechargeable batteries have an
210 extraordinary power density. This is great because we can fly with
211 much less battery mass than if we used alkaline batteries or previous
212 generation rechargeable batteries... but if they are punctured
213 or their leads are allowed to short, they can and will release their
215 Thus we recommend that you take some care when handling our batteries
216 and consider giving them some extra protection in your air-frame. We
217 often wrap them in suitable scraps of closed-cell packing foam before
218 strapping them down, for example.
221 The barometric sensors used on both TeleMetrum and TeleMini are
222 sensitive to sunlight. In normal TeleMetrum mounting situations, it
223 and all of the other surface mount components
224 are "down" towards whatever the underlying mounting surface is, so
225 this is not normally a problem. Please consider this, though, when
226 designing an installation, for example, in an air-frame with a
227 see-through plastic payload bay. It is particularly important to
228 consider this with TeleMini, both because the baro sensor is on the
229 "top" of the board, and because many model rockets with payload bays
230 use clear plastic for the payload bay! Replacing these with an opaque
231 cardboard tube, painting them, or wrapping them with a layer of masking
232 tape are all reasonable approaches to keep the sensor out of direct
236 The barometric sensor sampling port must be able to "breathe",
237 both by not being covered by foam or tape or other materials that might
238 directly block the hole on the top of the sensor, and also by having a
239 suitable static vent to outside air.
242 As with all other rocketry electronics, Altus Metrum altimeters must
243 be protected from exposure to corrosive motor exhaust and ejection
248 <title>Hardware Overview</title>
250 TeleMetrum is a 1 inch by 2.75 inch circuit board. It was designed to
251 fit inside coupler for 29mm air-frame tubing, but using it in a tube that
252 small in diameter may require some creativity in mounting and wiring
253 to succeed! The presence of an accelerometer means TeleMetrum should
254 be aligned along the flight axis of the airframe, and by default the 1/4
255 wave UHF wire antenna should be on the nose-cone end of the board. The
256 antenna wire is about 7 inches long, and wiring for a power switch and
257 the e-matches for apogee and main ejection charges depart from the
258 fin can end of the board, meaning an ideal "simple" avionics
259 bay for TeleMetrum should have at least 10 inches of interior length.
262 TeleMini is a 0.5 inch by 1.5 inch circuit board. It was designed to
263 fit inside an 18mm air-frame tube, but using it in a tube that
264 small in diameter may require some creativity in mounting and wiring
265 to succeed! Since there is no accelerometer, TeleMini can be mounted
266 in any convenient orientation. The default 1/4
267 wave UHF wire antenna attached to the center of one end of
268 the board is about 7 inches long, and wiring for a power switch and
269 the e-matches for apogee and main ejection charges depart from the
270 other end of the board, meaning an ideal "simple" avionics
271 bay for TeleMini should have at least 9 inches of interior length.
274 A typical TeleMetrum or TeleMini installation involves attaching
275 only a suitable Lithium Polymer battery, a single pole switch for
276 power on/off, and two pairs of wires connecting e-matches for the
277 apogee and main ejection charges. All Altus Metrum products are
278 designed for use with single-cell batteries with 3.7 volts nominal.
281 The battery connectors are a standard 2-pin JST connector and
282 match batteries sold by Spark Fun. These batteries are
283 single-cell Lithium Polymer batteries that nominally provide 3.7
284 volts. Other vendors sell similar batteries for RC aircraft
285 using mating connectors, however the polarity for those is
286 generally reversed from the batteries used by Altus Metrum
287 products. In particular, the Tenergy batteries supplied for use
288 in Featherweight flight computers are not compatible with Altus
289 Metrum flight computers or battery chargers. <emphasis>Check
290 polarity and voltage before connecting any battery not purchased
291 from Altus Metrum or Spark Fun.</emphasis>
294 By default, we use the unregulated output of the Li-Po battery directly
295 to fire ejection charges. This works marvelously with standard
296 low-current e-matches like the J-Tek from MJG Technologies, and with
297 Quest Q2G2 igniters. However, if you want or need to use a separate
298 pyro battery, check out the "External Pyro Battery" section in this
299 manual for instructions on how to wire that up. The altimeters are
300 designed to work with an external pyro battery of no more than 15 volts.
303 Ejection charges are wired directly to the screw terminal block
304 at the aft end of the altimeter. You'll need a very small straight
305 blade screwdriver for these screws, such as you might find in a
306 jeweler's screwdriver set.
309 TeleMetrum also uses the screw terminal block for the power
310 switch leads. On TeleMini, the power switch leads are soldered
311 directly to the board and can be connected directly to a switch.
314 For most air-frames, the integrated antennas are more than
315 adequate. However, if you are installing in a carbon-fiber or
316 metal electronics bay which is opaque to RF signals, you may need to
317 use off-board external antennas instead. In this case, you can
318 order an altimeter with an SMA connector for the UHF antenna
319 connection, and, on TeleMetrum, you can unplug the integrated GPS
320 antenna and select an appropriate off-board GPS antenna with
321 cable terminating in a U.FL connector.
325 <title>System Operation</title>
327 <title>Firmware Modes </title>
329 The AltOS firmware build for the altimeters has two
330 fundamental modes, "idle" and "flight". Which of these modes
331 the firmware operates in is determined at start up time. For
332 TeleMetrum, the mode is controlled by the orientation of the
333 rocket (well, actually the board, of course...) at the time
334 power is switched on. If the rocket is "nose up", then
335 TeleMetrum assumes it's on a rail or rod being prepared for
336 launch, so the firmware chooses flight mode. However, if the
337 rocket is more or less horizontal, the firmware instead enters
338 idle mode. Since TeleMini doesn't have an accelerometer we can
339 use to determine orientation, "idle" mode is selected when the
340 board receives a command packet within the first five seconds
341 of operation; if no packet is received, the board enters
345 At power on, you will hear three beeps or see three flashes
346 ("S" in Morse code for start up) and then a pause while
347 the altimeter completes initialization and self test, and decides
348 which mode to enter next.
351 In flight or "pad" mode, the altimeter engages the flight
352 state machine, goes into transmit-only mode to
353 send telemetry, and waits for launch to be detected.
354 Flight mode is indicated by an "di-dah-dah-dit" ("P" for pad)
355 on the beeper or lights, followed by beeps or flashes
356 indicating the state of the pyrotechnic igniter continuity.
357 One beep/flash indicates apogee continuity, two beeps/flashes
358 indicate main continuity, three beeps/flashes indicate both
359 apogee and main continuity, and one longer "brap" sound or
360 rapidly alternating lights indicates no continuity. For a
361 dual deploy flight, make sure you're getting three beeps or
362 flashes before launching! For apogee-only or motor eject
363 flights, do what makes sense.
366 If idle mode is entered, you will hear an audible "di-dit" or see
367 two short flashes ("I" for idle), and the flight state machine is
368 disengaged, thus no ejection charges will fire. The altimeters also
369 listen for the radio link when in idle mode for requests sent via
370 TeleDongle. Commands can be issued to a TeleMetrum in idle mode
372 USB or the radio link equivalently. TeleMini only has the radio link.
373 Idle mode is useful for configuring the altimeter, for extracting data
374 from the on-board storage chip after flight, and for ground testing
378 One "neat trick" of particular value when TeleMetrum is used with
379 very large air-frames, is that you can power the board up while the
380 rocket is horizontal, such that it comes up in idle mode. Then you can
381 raise the air-frame to launch position, and issue a 'reset' command
382 via TeleDongle over the radio link to cause the altimeter to reboot and
383 come up in flight mode. This is much safer than standing on the top
384 step of a rickety step-ladder or hanging off the side of a launch
385 tower with a screw-driver trying to turn on your avionics before
392 TeleMetrum includes a complete GPS receiver. A complete explanation
393 of how GPS works is beyond the scope of this manual, but the bottom
394 line is that the TeleMetrum GPS receiver needs to lock onto at least
395 four satellites to obtain a solid 3 dimensional position fix and know
399 TeleMetrum provides backup power to the GPS chip any time a
400 battery is connected. This allows the receiver to "warm start" on
401 the launch rail much faster than if every power-on were a GPS
402 "cold start". In typical operations, powering up TeleMetrum
403 on the flight line in idle mode while performing final air-frame
404 preparation will be sufficient to allow the GPS receiver to cold
405 start and acquire lock. Then the board can be powered down during
406 RSO review and installation on a launch rod or rail. When the board
407 is turned back on, the GPS system should lock very quickly, typically
408 long before igniter installation and return to the flight line are
413 <title>Controlling An Altimeter Over The Radio Link</title>
415 One of the unique features of the Altus Metrum system is
416 the ability to create a two way command link between TeleDongle
417 and an altimeter using the digital radio transceivers built into
418 each device. This allows you to interact with the altimeter from
419 afar, as if it were directly connected to the computer.
422 Any operation which can be performed with TeleMetrum can
423 either be done with TeleMetrum directly connected to the
424 computer via the USB cable, or through the radio
425 link. TeleMini doesn't provide a USB connector and so it is
426 always communicated with over radio. Select the appropriate
427 TeleDongle device when the list of devices is presented and
428 AltosUI will interact with an altimeter over the radio link.
431 One oddity in the current interface is how AltosUI selects the
432 frequency for radio communications. Instead of providing
433 an interface to specifically configure the frequency, it uses
434 whatever frequency was most recently selected for the target
435 TeleDongle device in Monitor Flight mode. If you haven't ever
436 used that mode with the TeleDongle in question, select the
437 Monitor Flight button from the top level UI, and pick the
438 appropriate TeleDongle device. Once the flight monitoring
439 window is open, select the desired frequency and then close it
440 down again. All radio communications will now use that frequency.
445 Save Flight Data—Recover flight data from the rocket without
451 Configure altimeter apogee delays or main deploy heights
452 to respond to changing launch conditions. You can also
453 'reboot' the altimeter. Use this to remotely enable the
454 flight computer by turning TeleMetrum on in "idle" mode,
455 then once the air-frame is oriented for launch, you can
456 reboot the altimeter and have it restart in pad mode
457 without having to climb the scary ladder.
462 Fire Igniters—Test your deployment charges without snaking
463 wires out through holes in the air-frame. Simply assembly the
464 rocket as if for flight with the apogee and main charges
465 loaded, then remotely command the altimeter to fire the
471 Operation over the radio link for configuring an altimeter, ground
472 testing igniters, and so forth uses the same RF frequencies as flight
473 telemetry. To configure the desired TeleDongle frequency, select
474 the monitor flight tab, then use the frequency selector and
475 close the window before performing other desired radio operations.
478 TeleMetrum only enables radio commanding in 'idle' mode, so
479 make sure you have TeleMetrum lying horizontally when you turn
480 it on. Otherwise, TeleMetrum will start in 'pad' mode ready for
481 flight, and will not be listening for command packets from TeleDongle.
484 TeleMini listens for a command packet for five seconds after
485 first being turned on, if it doesn't hear anything, it enters
486 'pad' mode, ready for flight and will no longer listen for
487 command packets. The easiest way to connect to TeleMini is to
488 initiate the command and select the TeleDongle device. At this
489 point, the TeleDongle will be attempting to communicate with
490 the TeleMini. Now turn TeleMini on, and it should immediately
491 start communicating with the TeleDongle and the desired
492 operation can be performed.
495 You can monitor the operation of the radio link by watching the
496 lights on the devices. The red LED will flash each time a packet
497 is transmitted, while the green LED will light up on TeleDongle when
498 it is waiting to receive a packet from the altimeter.
502 <title>Ground Testing </title>
504 An important aspect of preparing a rocket using electronic deployment
505 for flight is ground testing the recovery system. Thanks
506 to the bi-directional radio link central to the Altus Metrum system,
507 this can be accomplished in a TeleMetrum or TeleMini equipped rocket
508 with less work than you may be accustomed to with other systems. It
512 Just prep the rocket for flight, then power up the altimeter
513 in "idle" mode (placing air-frame horizontal for TeleMetrum or
514 selected the Configure Altimeter tab for TeleMini). This will cause
515 the firmware to go into "idle" mode, in which the normal flight
516 state machine is disabled and charges will not fire without
517 manual command. You can now command the altimeter to fire the apogee
518 or main charges from a safe distance using your computer and
519 TeleDongle and the Fire Igniter tab to complete ejection testing.
523 <title>Radio Link </title>
525 The chip our boards are based on incorporates an RF transceiver, but
526 it's not a full duplex system... each end can only be transmitting or
527 receiving at any given moment. So we had to decide how to manage the
531 By design, the altimeter firmware listens for the radio link when
532 it's in "idle mode", which
533 allows us to use the radio link to configure the rocket, do things like
534 ejection tests, and extract data after a flight without having to
535 crack open the air-frame. However, when the board is in "flight
536 mode", the altimeter only
537 transmits and doesn't listen at all. That's because we want to put
538 ultimate priority on event detection and getting telemetry out of
540 the radio in case the rocket crashes and we aren't able to extract
544 We don't use a 'normal packet radio' mode like APRS because they're
545 just too inefficient. The GFSK modulation we use is FSK with the
546 base-band pulses passed through a
547 Gaussian filter before they go into the modulator to limit the
548 transmitted bandwidth. When combined with the hardware forward error
549 correction support in the cc1111 chip, this allows us to have a very
550 robust 38.4 kilobit data link with only 10 milliwatts of transmit
551 power, a whip antenna in the rocket, and a hand-held Yagi on the
552 ground. We've had flights to above 21k feet AGL with great reception,
553 and calculations suggest we should be good to well over 40k feet AGL
554 with a 5-element yagi on the ground. We hope to fly boards to higher
555 altitudes over time, and would of course appreciate customer feedback
556 on performance in higher altitude flights!
560 <title>Configurable Parameters</title>
562 Configuring an Altus Metrum altimeter for flight is very
563 simple. Even on our baro-only TeleMini board, the use of a Kalman
564 filter means there is no need to set a "mach delay". The few
565 configurable parameters can all be set using AltosUI over USB or
566 or radio link via TeleDongle.
569 <title>Radio Frequency</title>
571 Altus Metrum boards support radio frequencies in the 70cm
572 band. By default, the configuration interface provides a
573 list of 10 "standard" frequencies in 100kHz channels starting at
574 434.550MHz. However, the firmware supports use of
575 any 50kHz multiple within the 70cm band. At any given
576 launch, we highly recommend coordinating when and by whom each
577 frequency will be used to avoid interference. And of course, both
578 altimeter and TeleDongle must be configured to the same
579 frequency to successfully communicate with each other.
583 <title>Apogee Delay</title>
585 Apogee delay is the number of seconds after the altimeter detects flight
586 apogee that the drogue charge should be fired. In most cases, this
587 should be left at the default of 0. However, if you are flying
588 redundant electronics such as for an L3 certification, you may wish
589 to set one of your altimeters to a positive delay so that both
590 primary and backup pyrotechnic charges do not fire simultaneously.
593 The Altus Metrum apogee detection algorithm fires exactly at
594 apogee. If you are also flying an altimeter like the
595 PerfectFlite MAWD, which only supports selecting 0 or 1
596 seconds of apogee delay, you may wish to set the MAWD to 0
597 seconds delay and set the TeleMetrum to fire your backup 2
598 or 3 seconds later to avoid any chance of both charges
599 firing simultaneously. We've flown several air-frames this
600 way quite happily, including Keith's successful L3 cert.
604 <title>Main Deployment Altitude</title>
606 By default, the altimeter will fire the main deployment charge at an
607 elevation of 250 meters (about 820 feet) above ground. We think this
608 is a good elevation for most air-frames, but feel free to change this
609 to suit. In particular, if you are flying two altimeters, you may
611 deployment elevation for the backup altimeter to be something lower
612 than the primary so that both pyrotechnic charges don't fire
617 <title>Maximum Flight Log</title>
619 TeleMetrum version 1.1 and 1.2 have 2MB of on-board flash storage,
620 enough to hold over 40 minutes of data at full data rate
621 (100 samples/second). TeleMetrum 1.0 has 1MB of on-board
622 storage. As data are stored at a reduced rate during descent
623 (10 samples/second), there's plenty of space to store many
624 flights worth of data.
627 The on-board flash is partitioned into separate flight logs,
628 each of a fixed maximum size. Increase the maximum size of
629 each log and you reduce the number of flights that can be
630 stored. Decrease the size and TeleMetrum can store more
634 All of the configuration data is also stored in the flash
635 memory, which consumes 64kB on TeleMetrum v1.1/v1.2 and 256B on
636 TeleMetrum v1.0. This configuration space is not available
637 for storing flight log data.
640 To compute the amount of space needed for a single flight,
641 you can multiply the expected ascent time (in seconds) by
642 800, multiply the expected descent time (in seconds) by 80
643 and add the two together. That will slightly under-estimate
644 the storage (in bytes) needed for the flight. For instance,
645 a flight spending 20 seconds in ascent and 150 seconds in
646 descent will take about (20 * 800) + (150 * 80) = 28000
647 bytes of storage. You could store dozens of these flights in
651 The default size, 192kB, allows for 10 flights of storage on
652 TeleMetrum v1.1/v1.2 and 5 flights on TeleMetrum v1.0. This
653 ensures that you won't need to erase the memory before
654 flying each time while still allowing more than sufficient
655 storage for each flight.
658 As TeleMini does not contain an accelerometer, it stores
659 data at 10 samples per second during ascent and one sample
660 per second during descent. Each sample is a two byte reading
661 from the barometer. These are stored in 5kB of
662 on-chip flash memory which can hold 256 seconds at the
663 ascent rate or 2560 seconds at the descent rate. Because of
664 the limited storage, TeleMini cannot hold data for more than
665 one flight, and so must be erased after each flight or it
666 will not capture data for subsequent flights.
670 <title>Ignite Mode</title>
672 Instead of firing one charge at apogee and another charge at
673 a fixed height above the ground, you can configure the
674 altimeter to fire both at apogee or both during
675 descent. This was added to support an airframe that has two
676 TeleMetrum computers, one in the fin can and one in the
680 Providing the ability to use both igniters for apogee or
681 main allows some level of redundancy without needing two
682 flight computers. In Redundant Apogee or Redundant Main
683 mode, the two charges will be fired two seconds apart.
687 <title>Pad Orientation</title>
689 TeleMetrum measures acceleration along the axis of the
690 board. Which way the board is oriented affects the sign of
691 the acceleration value. Instead of trying to guess which way
692 the board is mounted in the air frame, TeleMetrum must be
693 explicitly configured for either Antenna Up or Antenna
694 Down. The default, Antenna Up, expects the end of the
695 TeleMetrum board connected to the 70cm antenna to be nearest
696 the nose of the rocket, with the end containing the screw
697 terminals nearest the tail.
705 <title>AltosUI</title>
707 The AltosUI program provides a graphical user interface for
708 interacting with the Altus Metrum product family, including
709 TeleMetrum, TeleMini and TeleDongle. AltosUI can monitor telemetry data,
710 configure TeleMetrum, TeleMini and TeleDongle devices and many other
711 tasks. The primary interface window provides a selection of
712 buttons, one for each major activity in the system. This manual
713 is split into chapters, each of which documents one of the tasks
714 provided from the top-level toolbar.
717 <title>Monitor Flight</title>
718 <subtitle>Receive, Record and Display Telemetry Data</subtitle>
720 Selecting this item brings up a dialog box listing all of the
721 connected TeleDongle devices. When you choose one of these,
722 AltosUI will create a window to display telemetry data as
723 received by the selected TeleDongle device.
726 All telemetry data received are automatically recorded in
727 suitable log files. The name of the files includes the current
728 date and rocket serial and flight numbers.
731 The radio frequency being monitored by the TeleDongle device is
732 displayed at the top of the window. You can configure the
733 frequency by clicking on the frequency box and selecting the desired
734 frequency. AltosUI remembers the last frequency selected for each
735 TeleDongle and selects that automatically the next time you use
739 Below the TeleDongle frequency selector, the window contains a few
740 significant pieces of information about the altimeter providing
741 the telemetry data stream:
745 <para>The configured call-sign</para>
748 <para>The device serial number</para>
751 <para>The flight number. Each altimeter remembers how many
757 The rocket flight state. Each flight passes through several
758 states including Pad, Boost, Fast, Coast, Drogue, Main and
764 The Received Signal Strength Indicator value. This lets
765 you know how strong a signal TeleDongle is receiving. The
766 radio inside TeleDongle operates down to about -99dBm;
767 weaker signals may not be receivable. The packet link uses
768 error detection and correction techniques which prevent
769 incorrect data from being reported.
774 Finally, the largest portion of the window contains a set of
775 tabs, each of which contain some information about the rocket.
776 They're arranged in 'flight order' so that as the flight
777 progresses, the selected tab automatically switches to display
778 data relevant to the current state of the flight. You can select
779 other tabs at any time. The final 'table' tab displays all of
780 the raw telemetry values in one place in a spreadsheet-like format.
783 <title>Launch Pad</title>
785 The 'Launch Pad' tab shows information used to decide when the
786 rocket is ready for flight. The first elements include red/green
787 indicators, if any of these is red, you'll want to evaluate
788 whether the rocket is ready to launch:
792 Battery Voltage. This indicates whether the Li-Po battery
793 powering the TeleMetrum has sufficient charge to last for
794 the duration of the flight. A value of more than
795 3.7V is required for a 'GO' status.
800 Apogee Igniter Voltage. This indicates whether the apogee
801 igniter has continuity. If the igniter has a low
802 resistance, then the voltage measured here will be close
803 to the Li-Po battery voltage. A value greater than 3.2V is
804 required for a 'GO' status.
809 Main Igniter Voltage. This indicates whether the main
810 igniter has continuity. If the igniter has a low
811 resistance, then the voltage measured here will be close
812 to the Li-Po battery voltage. A value greater than 3.2V is
813 required for a 'GO' status.
818 On-board Data Logging. This indicates whether there is
819 space remaining on-board to store flight data for the
820 upcoming flight. If you've downloaded data, but failed
821 to erase flights, there may not be any space
822 left. TeleMetrum can store multiple flights, depending
823 on the configured maximum flight log size. TeleMini
824 stores only a single flight, so it will need to be
825 downloaded and erased after each flight to capture
826 data. This only affects on-board flight logging; the
827 altimeter will still transmit telemetry and fire
828 ejection charges at the proper times.
833 GPS Locked. For a TeleMetrum device, this indicates whether the GPS receiver is
834 currently able to compute position information. GPS requires
835 at least 4 satellites to compute an accurate position.
840 GPS Ready. For a TeleMetrum device, this indicates whether GPS has reported at least
841 10 consecutive positions without losing lock. This ensures
842 that the GPS receiver has reliable reception from the
848 The Launchpad tab also shows the computed launch pad position
849 and altitude, averaging many reported positions to improve the
855 <title>Ascent</title>
857 This tab is shown during Boost, Fast and Coast
858 phases. The information displayed here helps monitor the
859 rocket as it heads towards apogee.
862 The height, speed and acceleration are shown along with the
863 maximum values for each of them. This allows you to quickly
864 answer the most commonly asked questions you'll hear during
868 The current latitude and longitude reported by the TeleMetrum GPS are
869 also shown. Note that under high acceleration, these values
870 may not get updated as the GPS receiver loses position
871 fix. Once the rocket starts coasting, the receiver should
872 start reporting position again.
875 Finally, the current igniter voltages are reported as in the
876 Launch Pad tab. This can help diagnose deployment failures
877 caused by wiring which comes loose under high acceleration.
881 <title>Descent</title>
883 Once the rocket has reached apogee and (we hope) activated the
884 apogee charge, attention switches to tracking the rocket on
885 the way back to the ground, and for dual-deploy flights,
886 waiting for the main charge to fire.
889 To monitor whether the apogee charge operated correctly, the
890 current descent rate is reported along with the current
891 height. Good descent rates vary based on the choice of recovery
892 components, but generally range from 15-30m/s on drogue and should
893 be below 10m/s when under the main parachute in a dual-deploy flight.
896 For TeleMetrum altimeters, you can locate the rocket in the
897 sky using the elevation and bearing information to figure
898 out where to look. Elevation is in degrees above the
899 horizon. Bearing is reported in degrees relative to true
900 north. Range can help figure out how big the rocket will
901 appear. Ground Distance shows how far it is to a point
902 directly under the rocket and can help figure out where the
903 rocket is likely to land. Note that all of these values are
904 relative to the pad location. If the elevation is near 90°,
905 the rocket is over the pad, not over you.
908 Finally, the igniter voltages are reported in this tab as
909 well, both to monitor the main charge as well as to see what
910 the status of the apogee charge is. Note that some commercial
911 e-matches are designed to retain continuity even after being
912 fired, and will continue to show as green or return from red to
917 <title>Landed</title>
919 Once the rocket is on the ground, attention switches to
920 recovery. While the radio signal is often lost once the
921 rocket is on the ground, the last reported GPS position is
922 generally within a short distance of the actual landing location.
925 The last reported GPS position is reported both by
926 latitude and longitude as well as a bearing and distance from
927 the launch pad. The distance should give you a good idea of
928 whether to walk or hitch a ride. Take the reported
929 latitude and longitude and enter them into your hand-held GPS
930 unit and have that compute a track to the landing location.
933 Both TeleMini and TeleMetrum will continue to transmit RDF
934 tones after landing, allowing you to locate the rocket by
935 following the radio signal if necessary. You may need to get
936 away from the clutter of the flight line, or even get up on
937 a hill (or your neighbor's RV roof) to receive the RDF signal.
940 The maximum height, speed and acceleration reported
941 during the flight are displayed for your admiring observers.
942 The accuracy of these immediate values depends on the quality
943 of your radio link and how many packets were received.
944 Recovering the on-board data after flight will likely yield
945 more precise results.
948 To get more detailed information about the flight, you can
949 click on the 'Graph Flight' button which will bring up a
950 graph window for the current flight.
954 <title>Site Map</title>
956 When the TeleMetrum has a GPS fix, the Site Map tab will map
957 the rocket's position to make it easier for you to locate the
958 rocket, both while it is in the air, and when it has landed. The
959 rocket's state is indicated by color: white for pad, red for
960 boost, pink for fast, yellow for coast, light blue for drogue,
961 dark blue for main, and black for landed.
964 The map's scale is approximately 3m (10ft) per pixel. The map
965 can be dragged using the left mouse button. The map will attempt
966 to keep the rocket roughly centered while data is being received.
969 Images are fetched automatically via the Google Maps Static API,
970 and cached on disk for reuse. If map images cannot be downloaded,
971 the rocket's path will be traced on a dark gray background
975 You can pre-load images for your favorite launch sites
976 before you leave home; check out the 'Preload Maps' section below.
981 <title>Save Flight Data</title>
983 The altimeter records flight data to its internal flash memory.
984 TeleMetrum data is recorded at a much higher rate than the telemetry
985 system can handle, and is not subject to radio drop-outs. As
986 such, it provides a more complete and precise record of the
987 flight. The 'Save Flight Data' button allows you to read the
988 flash memory and write it to disk. As TeleMini has only a barometer, it
989 records data at the same rate as the telemetry signal, but there will be
990 no data lost due to telemetry drop-outs.
993 Clicking on the 'Save Flight Data' button brings up a list of
994 connected TeleMetrum and TeleDongle devices. If you select a
995 TeleMetrum device, the flight data will be downloaded from that
996 device directly. If you select a TeleDongle device, flight data
997 will be downloaded from an altimeter over radio link via the
998 specified TeleDongle. See the chapter on Controlling An Altimeter
999 Over The Radio Link for more information.
1002 After the device has been selected, a dialog showing the
1003 flight data saved in the device will be shown allowing you to
1004 select which flights to download and which to delete. With
1005 version 0.9 or newer firmware, you must erase flights in order
1006 for the space they consume to be reused by another
1007 flight. This prevents accidentally losing flight data
1008 if you neglect to download data before flying again. Note that
1009 if there is no more space available in the device, then no
1010 data will be recorded during the next flight.
1013 The file name for each flight log is computed automatically
1014 from the recorded flight date, altimeter serial number and
1015 flight number information.
1019 <title>Replay Flight</title>
1021 Select this button and you are prompted to select a flight
1022 record file, either a .telem file recording telemetry data or a
1023 .eeprom file containing flight data saved from the altimeter
1027 Once a flight record is selected, the flight monitor interface
1028 is displayed and the flight is re-enacted in real time. Check
1029 the Monitor Flight chapter above to learn how this window operates.
1033 <title>Graph Data</title>
1035 Select this button and you are prompted to select a flight
1036 record file, either a .telem file recording telemetry data or a
1037 .eeprom file containing flight data saved from
1041 Once a flight record is selected, a window with two tabs is
1042 opened. The first tab contains a graph with acceleration
1043 (blue), velocity (green) and altitude (red) of the flight,
1044 measured in metric units. The
1045 apogee(yellow) and main(magenta) igniter voltages are also
1046 displayed; high voltages indicate continuity, low voltages
1047 indicate open circuits. The second tab contains some basic
1051 The graph can be zoomed into a particular area by clicking and
1052 dragging down and to the right. Once zoomed, the graph can be
1053 reset by clicking and dragging up and to the left. Holding down
1054 control and clicking and dragging allows the graph to be panned.
1055 The right mouse button causes a pop-up menu to be displayed, giving
1056 you the option save or print the plot.
1059 Note that telemetry files will generally produce poor graphs
1060 due to the lower sampling rate and missed telemetry packets.
1061 Use saved flight data in .eeprom files for graphing where possible.
1065 <title>Export Data</title>
1067 This tool takes the raw data files and makes them available for
1068 external analysis. When you select this button, you are prompted to
1070 data file (either .eeprom or .telem will do, remember that
1071 .eeprom files contain higher resolution and more continuous
1072 data). Next, a second dialog appears which is used to select
1073 where to write the resulting file. It has a selector to choose
1074 between CSV and KML file formats.
1077 <title>Comma Separated Value Format</title>
1079 This is a text file containing the data in a form suitable for
1080 import into a spreadsheet or other external data analysis
1081 tool. The first few lines of the file contain the version and
1082 configuration information from the altimeter, then
1083 there is a single header line which labels all of the
1084 fields. All of these lines start with a '#' character which
1085 many tools can be configured to skip over.
1088 The remaining lines of the file contain the data, with each
1089 field separated by a comma and at least one space. All of
1090 the sensor values are converted to standard units, with the
1091 barometric data reported in both pressure, altitude and
1092 height above pad units.
1096 <title>Keyhole Markup Language (for Google Earth)</title>
1098 This is the format used by Google Earth to provide an overlay
1099 within that application. With this, you can use Google Earth to
1100 see the whole flight path in 3D.
1105 <title>Configure Altimeter</title>
1107 Select this button and then select either a TeleMetrum or
1108 TeleDongle Device from the list provided. Selecting a TeleDongle
1109 device will use the radio link to configure a remote altimeter.
1112 The first few lines of the dialog provide information about the
1113 connected device, including the product name,
1114 software version and hardware serial number. Below that are the
1115 individual configuration entries.
1118 At the bottom of the dialog, there are four buttons:
1123 Save. This writes any changes to the
1124 configuration parameter block in flash memory. If you don't
1125 press this button, any changes you make will be lost.
1130 Reset. This resets the dialog to the most recently saved values,
1131 erasing any changes you have made.
1136 Reboot. This reboots the device. Use this to
1137 switch from idle to pad mode by rebooting once the rocket is
1138 oriented for flight, or to confirm changes you think you saved
1144 Close. This closes the dialog. Any unsaved changes will be
1150 The rest of the dialog contains the parameters to be configured.
1153 <title>Main Deploy Altitude</title>
1155 This sets the altitude (above the recorded pad altitude) at
1156 which the 'main' igniter will fire. The drop-down menu shows
1157 some common values, but you can edit the text directly and
1158 choose whatever you like. If the apogee charge fires below
1159 this altitude, then the main charge will fire two seconds
1160 after the apogee charge fires.
1164 <title>Apogee Delay</title>
1166 When flying redundant electronics, it's often important to
1167 ensure that multiple apogee charges don't fire at precisely
1168 the same time, as that can over pressurize the apogee deployment
1169 bay and cause a structural failure of the air-frame. The Apogee
1170 Delay parameter tells the flight computer to fire the apogee
1171 charge a certain number of seconds after apogee has been
1176 <title>Radio Frequency</title>
1178 This configures which of the configured frequencies to use for both
1179 telemetry and packet command mode. Note that if you set this
1180 value via packet command mode, you will have to reconfigure
1181 the TeleDongle frequency before you will be able to use packet
1186 <title>Radio Calibration</title>
1188 The radios in every Altus Metrum device are calibrated at the
1189 factory to ensure that they transmit and receive on the
1190 specified frequency. If you need to you can adjust the calibration
1191 by changing this value. Do not do this without understanding what
1192 the value means, read the appendix on calibration and/or the source
1193 code for more information. To change a TeleDongle's calibration,
1194 you must reprogram the unit completely.
1198 <title>Callsign</title>
1200 This sets the call sign included in each telemetry packet. Set this
1201 as needed to conform to your local radio regulations.
1205 <title>Maximum Flight Log Size</title>
1207 This sets the space (in kilobytes) allocated for each flight
1208 log. The available space will be divided into chunks of this
1209 size. A smaller value will allow more flights to be stored,
1210 a larger value will record data from longer flights.
1214 <title>Ignite Mode</title>
1216 TeleMetrum and TeleMini provide two igniter channels as they
1217 were originally designed as dual-deploy flight
1218 computers. This configuration parameter allows the two
1219 channels to be used in different configurations.
1224 Dual Deploy. This is the usual mode of operation; the
1225 'apogee' channel is fired at apogee and the 'main'
1226 channel at the height above ground specified by the
1227 'Main Deploy Altitude' during descent.
1232 Redundant Apogee. This fires both channels at
1233 apogee, the 'apogee' channel first followed after a two second
1234 delay by the 'main' channel.
1239 Redundant Main. This fires both channels at the
1240 height above ground specified by the Main Deploy
1241 Altitude setting during descent. The 'apogee'
1242 channel is fired first, followed after a two second
1243 delay by the 'main' channel.
1249 <title>Pad Orientation</title>
1251 Because it includes an accelerometer, TeleMetrum is
1252 sensitive to the orientation of the board. By default, it
1253 expects the antenna end to point forward. This parameter
1254 allows that default to be changed, permitting the board to
1255 be mounted with the antenna pointing aft instead.
1260 Antenna Up. In this mode, the antenna end of the
1261 TeleMetrum board must point forward, in line with the
1262 expected flight path.
1267 Antenna Down. In this mode, the antenna end of the
1268 TeleMetrum board must point aft, in line with the
1269 expected flight path.
1276 <title>Configure AltosUI</title>
1278 This button presents a dialog so that you can configure the AltosUI global settings.
1281 <title>Voice Settings</title>
1283 AltosUI provides voice announcements during flight so that you
1284 can keep your eyes on the sky and still get information about
1285 the current flight status. However, sometimes you don't want
1290 <para>Enable—turns all voice announcements on and off</para>
1294 Test Voice—Plays a short message allowing you to verify
1295 that the audio system is working and the volume settings
1302 <title>Log Directory</title>
1304 AltosUI logs all telemetry data and saves all TeleMetrum flash
1305 data to this directory. This directory is also used as the
1306 staring point when selecting data files for display or export.
1309 Click on the directory name to bring up a directory choosing
1310 dialog, select a new directory and click 'Select Directory' to
1311 change where AltosUI reads and writes data files.
1315 <title>Callsign</title>
1317 This value is transmitted in each command packet sent from
1318 TeleDongle and received from an altimeter. It is not used in
1319 telemetry mode, as the callsign configured in the altimeter board
1320 is included in all telemetry packets. Configure this
1321 with the AltosUI operators call sign as needed to comply with
1322 your local radio regulations.
1326 <title>Imperial Units</title>
1328 This switches between metric units (meters) and imperial
1329 units (feet and miles). This affects the display of values
1330 use during flight monitoring, data graphing and all of the
1331 voice announcements. It does not change the units used when
1332 exporting to CSV files, those are always produced in metric units.
1336 <title>Font Size</title>
1338 Selects the set of fonts used in the flight monitor
1339 window. Choose between the small, medium and large sets.
1343 <title>Serial Debug</title>
1345 This causes all communication with a connected device to be
1346 dumped to the console from which AltosUI was started. If
1347 you've started it from an icon or menu entry, the output
1348 will simply be discarded. This mode can be useful to debug
1349 various serial communication issues.
1353 <title>Manage Frequencies</title>
1355 This brings up a dialog where you can configure the set of
1356 frequencies shown in the various frequency menus. You can
1357 add as many as you like, or even reconfigure the default
1358 set. Changing this list does not affect the frequency
1359 settings of any devices, it only changes the set of
1360 frequencies shown in the menus.
1365 <title>Configure Groundstation</title>
1367 Select this button and then select a TeleDongle Device from the list provided.
1370 The first few lines of the dialog provide information about the
1371 connected device, including the product name,
1372 software version and hardware serial number. Below that are the
1373 individual configuration entries.
1376 Note that the TeleDongle itself doesn't save any configuration
1377 data, the settings here are recorded on the local machine in
1378 the Java preferences database. Moving the TeleDongle to
1379 another machine, or using a different user account on the same
1380 machine will cause settings made here to have no effect.
1383 At the bottom of the dialog, there are three buttons:
1388 Save. This writes any changes to the
1389 local Java preferences file. If you don't
1390 press this button, any changes you make will be lost.
1395 Reset. This resets the dialog to the most recently saved values,
1396 erasing any changes you have made.
1401 Close. This closes the dialog. Any unsaved changes will be
1407 The rest of the dialog contains the parameters to be configured.
1410 <title>Frequency</title>
1412 This configures the frequency to use for both telemetry and
1413 packet command mode. Set this before starting any operation
1414 involving packet command mode so that it will use the right
1415 frequency. Telemetry monitoring mode also provides a menu to
1416 change the frequency, and that menu also sets the same Java
1417 preference value used here.
1421 <title>Radio Calibration</title>
1423 The radios in every Altus Metrum device are calibrated at the
1424 factory to ensure that they transmit and receive on the
1425 specified frequency. To change a TeleDongle's calibration,
1426 you must reprogram the unit completely, so this entry simply
1427 shows the current value and doesn't allow any changes.
1432 <title>Flash Image</title>
1434 This reprograms any Altus Metrum device by using a TeleMetrum
1435 or TeleDongle as a programming dongle. Please read the
1436 directions for flashing devices in the Updating Device
1437 Firmware chapter below.
1440 Once you have the programmer and target devices connected,
1441 push the 'Flash Image' button. That will present a dialog box
1442 listing all of the connected devices. Carefully select the
1443 programmer device, not the device to be programmed.
1446 Next, select the image to flash to the device. These are named
1447 with the product name and firmware version. The file selector
1448 will start in the directory containing the firmware included
1449 with the AltosUI package. Navigate to the directory containing
1450 the desired firmware if it isn't there.
1453 Next, a small dialog containing the device serial number and
1454 RF calibration values should appear. If these values are
1455 incorrect (possibly due to a corrupted image in the device),
1456 enter the correct values here.
1459 Finally, a dialog containing a progress bar will follow the
1460 programming process.
1463 When programming is complete, the target device will
1464 reboot. Note that if the target device is connected via USB, you
1465 will have to unplug it and then plug it back in for the USB
1466 connection to reset so that you can communicate with the device
1471 <title>Fire Igniter</title>
1473 This activates the igniter circuits in TeleMetrum to help test
1474 recovery systems deployment. Because this command can operate
1475 over the Packet Command Link, you can prepare the rocket as
1476 for flight and then test the recovery system without needing
1477 to snake wires inside the air-frame.
1480 Selecting the 'Fire Igniter' button brings up the usual device
1481 selection dialog. Pick the desired TeleDongle or TeleMetrum
1482 device. This brings up another window which shows the current
1483 continuity test status for both apogee and main charges.
1486 Next, select the desired igniter to fire. This will enable the
1490 Select the 'Arm' button. This enables the 'Fire' button. The
1491 word 'Arm' is replaced by a countdown timer indicating that
1492 you have 10 seconds to press the 'Fire' button or the system
1493 will deactivate, at which point you start over again at
1494 selecting the desired igniter.
1498 <title>Scan Channels</title>
1500 This listens for telemetry packets on all of the configured
1501 frequencies, displaying information about each device it
1502 receives a packet from. You can select which of the three
1503 telemetry formats should be tried; by default, it only listens
1504 for the standard telemetry packets used in v1.0 and later
1509 <title>Load Maps</title>
1511 Before heading out to a new launch site, you can use this to
1512 load satellite images in case you don't have internet
1513 connectivity at the site. This loads a fairly large area
1514 around the launch site, which should cover any flight you're likely to make.
1517 There's a drop-down menu of launch sites we know about; if
1518 your favorites aren't there, please let us know the lat/lon
1519 and name of the site. The contents of this list are actually
1520 downloaded at run-time, so as new sites are sent in, they'll
1521 get automatically added to this list.
1524 If the launch site isn't in the list, you can manually enter the lat/lon values
1527 Clicking the 'Load Map' button will fetch images from Google
1528 Maps; note that Google limits how many images you can fetch at
1529 once, so if you load more than one launch site, you may get
1530 some gray areas in the map which indicate that Google is tired
1531 of sending data to you. Try again later.
1535 <title>Monitor Idle</title>
1537 This brings up a dialog similar to the Monitor Flight UI,
1538 except it works with the altimeter in "idle" mode by sending
1539 query commands to discover the current state rather than
1540 listening for telemetry packets.
1545 <title>Using Altus Metrum Products</title>
1547 <title>Being Legal</title>
1549 First off, in the US, you need an <ulink url="http://www.altusmetrum.org/Radio/">amateur radio license</ulink> or
1550 other authorization to legally operate the radio transmitters that are part
1555 <title>In the Rocket</title>
1557 In the rocket itself, you just need a <ulink url="http://www.altusmetrum.org/TeleMetrum/">TeleMetrum</ulink> or
1558 <ulink url="http://www.altusmetrum.org/TeleMini/">TeleMini</ulink> board and
1559 a single-cell, 3.7 volt nominal Li-Po rechargeable battery. An
1560 850mAh battery weighs less than a 9V alkaline battery, and will
1561 run a TeleMetrum for hours.
1562 A 110mAh battery weighs less than a triple A battery and will run a TeleMetrum for
1563 a few hours, or a TeleMini for much (much) longer.
1566 By default, we ship the altimeters with a simple wire antenna. If your
1567 electronics bay or the air-frame it resides within is made of carbon fiber,
1568 which is opaque to RF signals, you may choose to have an SMA connector
1569 installed so that you can run a coaxial cable to an antenna mounted
1570 elsewhere in the rocket.
1574 <title>On the Ground</title>
1576 To receive the data stream from the rocket, you need an antenna and short
1577 feed-line connected to one of our <ulink url="http://www.altusmetrum.org/TeleDongle/">TeleDongle</ulink> units. The
1578 TeleDongle in turn plugs directly into the USB port on a notebook
1579 computer. Because TeleDongle looks like a simple serial port, your computer
1580 does not require special device drivers... just plug it in.
1583 The GUI tool, AltosUI, is written in Java and runs across
1584 Linux, Mac OS and Windows. There's also a suite of C tools
1585 for Linux which can perform most of the same tasks.
1588 After the flight, you can use the radio link to extract the more detailed data
1589 logged in either TeleMetrum or TeleMini devices, or you can use a mini USB cable to plug into the
1590 TeleMetrum board directly. Pulling out the data without having to open up
1591 the rocket is pretty cool! A USB cable is also how you charge the Li-Po
1592 battery, so you'll want one of those anyway... the same cable used by lots
1593 of digital cameras and other modern electronic stuff will work fine.
1596 If your TeleMetrum-equipped rocket lands out of sight, you may enjoy having a hand-held GPS
1597 receiver, so that you can put in a way-point for the last reported rocket
1598 position before touch-down. This makes looking for your rocket a lot like
1599 Geo-Caching... just go to the way-point and look around starting from there.
1602 You may also enjoy having a ham radio "HT" that covers the 70cm band... you
1603 can use that with your antenna to direction-find the rocket on the ground
1604 the same way you can use a Walston or Beeline tracker. This can be handy
1605 if the rocket is hiding in sage brush or a tree, or if the last GPS position
1606 doesn't get you close enough because the rocket dropped into a canyon, or
1607 the wind is blowing it across a dry lake bed, or something like that... Keith
1608 and Bdale both currently own and use the Yaesu VX-7R at launches.
1611 So, to recap, on the ground the hardware you'll need includes:
1612 <orderedlist inheritnum='inherit' numeration='arabic'>
1614 an antenna and feed-line
1623 optionally, a hand-held GPS receiver
1626 optionally, an HT or receiver covering 435 MHz
1631 The best hand-held commercial directional antennas we've found for radio
1632 direction finding rockets are from
1633 <ulink url="http://www.arrowantennas.com/" >
1636 The 440-3 and 440-5 are both good choices for finding a
1637 TeleMetrum- or TeleMini- equipped rocket when used with a suitable 70cm HT.
1641 <title>Data Analysis</title>
1643 Our software makes it easy to log the data from each flight, both the
1644 telemetry received during the flight itself, and the more
1645 complete data log recorded in the flash memory on the altimeter
1646 board. Once this data is on your computer, our post-flight tools make it
1647 easy to quickly get to the numbers everyone wants, like apogee altitude,
1648 max acceleration, and max velocity. You can also generate and view a
1649 standard set of plots showing the altitude, acceleration, and
1650 velocity of the rocket during flight. And you can even export a TeleMetrum data file
1651 usable with Google Maps and Google Earth for visualizing the flight path
1652 in two or three dimensions!
1655 Our ultimate goal is to emit a set of files for each flight that can be
1656 published as a web page per flight, or just viewed on your local disk with
1661 <title>Future Plans</title>
1663 In the future, we intend to offer "companion boards" for the rocket that will
1664 plug in to TeleMetrum to collect additional data, provide more pyro channels,
1668 We are also working on the design of a hand-held ground terminal that will
1669 allow monitoring the rocket's status, collecting data during flight, and
1670 logging data after flight without the need for a notebook computer on the
1671 flight line. Particularly since it is so difficult to read most notebook
1672 screens in direct sunlight, we think this will be a great thing to have.
1675 Because all of our work is open, both the hardware designs and the software,
1676 if you have some great idea for an addition to the current Altus Metrum family,
1677 feel free to dive in and help! Or let us know what you'd like to see that
1678 we aren't already working on, and maybe we'll get excited about it too...
1683 <title>Altimeter Installation Recommendations</title>
1685 Building high-power rockets that fly safely is hard enough. Mix
1686 in some sophisticated electronics and a bunch of radio energy
1687 and oftentimes you find few perfect solutions. This chapter
1688 contains some suggestions about how to install Altus Metrum
1689 products into the rocket air-frame, including how to safely and
1690 reliably mix a variety of electronics into the same air-frame.
1693 <title>Mounting the Altimeter</title>
1695 The first consideration is to ensure that the altimeter is
1696 securely fastened to the air-frame. For TeleMetrum, we use
1697 nylon standoffs and nylon screws; they're good to at least 50G
1698 and cannot cause any electrical issues on the board. For
1699 TeleMini, we usually cut small pieces of 1/16" balsa to fit
1700 under the screw holes, and then take 2x56 nylon screws and
1701 screw them through the TeleMini mounting holes, through the
1702 balsa and into the underlying material.
1704 <orderedlist inheritnum='inherit' numeration='arabic'>
1706 Make sure TeleMetrum is aligned precisely along the axis of
1707 acceleration so that the accelerometer can accurately
1708 capture data during the flight.
1711 Watch for any metal touching components on the
1712 board. Shorting out connections on the bottom of the board
1713 can cause the altimeter to fail during flight.
1718 <title>Dealing with the Antenna</title>
1720 The antenna supplied is just a piece of solid, insulated,
1721 wire. If it gets damaged or broken, it can be easily
1722 replaced. It should be kept straight and not cut; bending or
1723 cutting it will change the resonant frequency and/or
1724 impedance, making it a less efficient radiator and thus
1725 reducing the range of the telemetry signal.
1728 Keeping metal away from the antenna will provide better range
1729 and a more even radiation pattern. In most rockets, it's not
1730 entirely possible to isolate the antenna from metal
1731 components; there are often bolts, all-thread and wires from other
1732 electronics to contend with. Just be aware that the more stuff
1733 like this around the antenna, the lower the range.
1736 Make sure the antenna is not inside a tube made or covered
1737 with conducting material. Carbon fiber is the most common
1738 culprit here -- CF is a good conductor and will effectively
1739 shield the antenna, dramatically reducing signal strength and
1740 range. Metallic flake paint is another effective shielding
1741 material which is to be avoided around any antennas.
1744 If the ebay is large enough, it can be convenient to simply
1745 mount the altimeter at one end and stretch the antenna out
1746 inside. Taping the antenna to the sled can keep it straight
1747 under acceleration. If there are metal rods, keep the
1748 antenna as far away as possible.
1751 For a shorter ebay, it's quite practical to have the antenna
1752 run through a bulkhead and into an adjacent bay. Drill a small
1753 hole in the bulkhead, pass the antenna wire through it and
1754 then seal it up with glue or clay. We've also used acrylic
1755 tubing to create a cavity for the antenna wire. This works a
1756 bit better in that the antenna is known to stay straight and
1757 not get folded by recovery components in the bay. Angle the
1758 tubing towards the side wall of the rocket and it ends up
1759 consuming very little space.
1762 If you need to place the antenna at a distance from the
1763 altimeter, you can replace the antenna with an edge-mounted
1764 SMA connector, and then run 50Ω coax from the board to the
1765 antenna. Building a remote antenna is beyond the scope of this
1770 <title>Preserving GPS Reception</title>
1772 The GPS antenna and receiver in TeleMetrum are highly
1773 sensitive and normally have no trouble tracking enough
1774 satellites to provide accurate position information for
1775 recovering the rocket. However, there are many ways to
1776 attenuate the GPS signal.
1777 <orderedlist inheritnum='inherit' numeration='arabic'>
1779 Conductive tubing or coatings. Carbon fiber and metal
1780 tubing, or metallic paint will all dramatically attenuate the
1781 GPS signal. We've never heard of anyone successfully
1782 receiving GPS from inside these materials.
1785 Metal components near the GPS patch antenna. These will
1786 de-tune the patch antenna, changing the resonant frequency
1787 away from the L1 carrier and reduce the effectiveness of the
1788 antenna. You can place as much stuff as you like beneath the
1789 antenna as that's covered with a ground plane. But, keep
1790 wires and metal out from above the patch antenna.
1796 <title>Radio Frequency Interference</title>
1798 Any altimeter will generate RFI; the digital circuits use
1799 high-frequency clocks that spray radio interference across a
1800 wide band. Altus Metrum altimeters generate intentional radio
1801 signals as well, increasing the amount of RF energy around the board.
1804 Rocketry altimeters also use precise sensors measuring air
1805 pressure and acceleration. Tiny changes in voltage can cause
1806 these sensor readings to vary by a huge amount. When the
1807 sensors start mis-reporting data, the altimeter can either
1808 fire the igniters at the wrong time, or not fire them at all.
1811 Voltages are induced when radio frequency energy is
1812 transmitted from one circuit to another. Here are things that
1813 influence the induced voltage and current:
1817 Keep wires from different circuits apart. Moving circuits
1818 further apart will reduce RFI.
1821 Avoid parallel wires from different circuits. The longer two
1822 wires run parallel to one another, the larger the amount of
1823 transferred energy. Cross wires at right angles to reduce
1827 Twist wires from the same circuits. Two wires the same
1828 distance from the transmitter will get the same amount of
1829 induced energy which will then cancel out. Any time you have
1830 a wire pair running together, twist the pair together to
1831 even out distances and reduce RFI. For altimeters, this
1832 includes battery leads, switch hookups and igniter
1836 Avoid resonant lengths. Know what frequencies are present
1837 in the environment and avoid having wire lengths near a
1838 natural resonant length. Altusmetrum products transmit on the
1839 70cm amateur band, so you should avoid lengths that are a
1840 simple ratio of that length; essentially any multiple of 1/4
1841 of the wavelength (17.5cm).
1846 <title>The Barometric Sensor</title>
1848 Altusmetrum altimeters measure altitude with a barometric
1849 sensor, essentially measuring the amount of air above the
1850 rocket to figure out how high it is. A large number of
1851 measurements are taken as the altimeter initializes itself to
1852 figure out the pad altitude. Subsequent measurements are then
1853 used to compute the height above the pad.
1856 To accurately measure atmospheric pressure, the ebay
1857 containing the altimeter must be vented outside the
1858 air-frame. The vent must be placed in a region of linear
1859 airflow, have smooth edges, and away from areas of increasing or
1860 decreasing pressure.
1863 The barometric sensor in the altimeter is quite sensitive to
1864 chemical damage from the products of APCP or BP combustion, so
1865 make sure the ebay is carefully sealed from any compartment
1866 which contains ejection charges or motors.
1870 <title>Ground Testing</title>
1872 The most important aspect of any installation is careful
1873 ground testing. Bringing an air-frame up to the LCO table which
1874 hasn't been ground tested can lead to delays or ejection
1875 charges firing on the pad, or, even worse, a recovery system
1879 Do a 'full systems' test that includes wiring up all igniters
1880 without any BP and turning on all of the electronics in flight
1881 mode. This will catch any mistakes in wiring and any residual
1882 RFI issues that might accidentally fire igniters at the wrong
1883 time. Let the air-frame sit for several minutes, checking for
1884 adequate telemetry signal strength and GPS lock. If any igniters
1885 fire unexpectedly, find and resolve the issue before loading any
1889 Ground test the ejection charges. Prepare the rocket for
1890 flight, loading ejection charges and igniters. Completely
1891 assemble the air-frame and then use the 'Fire Igniters'
1892 interface through a TeleDongle to command each charge to
1893 fire. Make sure the charge is sufficient to robustly separate
1894 the air-frame and deploy the recovery system.
1899 <title>Updating Device Firmware</title>
1901 The big concept to understand is that you have to use a
1902 TeleDongle as a programmer to update a TeleMetrum or TeleMini,
1903 and a TeleMetrum or other TeleDongle to program the TeleDongle
1904 Due to limited memory resources in the cc1111, we don't support
1905 programming directly over USB.
1908 You may wish to begin by ensuring you have current firmware images.
1909 These are distributed as part of the AltOS software bundle that
1910 also includes the AltosUI ground station program. Newer ground
1911 station versions typically work fine with older firmware versions,
1912 so you don't need to update your devices just to try out new
1913 software features. You can always download the most recent
1914 version from <ulink url="http://www.altusmetrum.org/AltOS/"/>.
1917 We recommend updating the altimeter first, before updating TeleDongle.
1920 <title>Updating TeleMetrum Firmware</title>
1921 <orderedlist inheritnum='inherit' numeration='arabic'>
1923 Find the 'programming cable' that you got as part of the starter
1924 kit, that has a red 8-pin MicroMaTch connector on one end and a
1925 red 4-pin MicroMaTch connector on the other end.
1928 Take the 2 screws out of the TeleDongle case to get access
1929 to the circuit board.
1932 Plug the 8-pin end of the programming cable to the
1933 matching connector on the TeleDongle, and the 4-pin end to the
1934 matching connector on the TeleMetrum.
1935 Note that each MicroMaTch connector has an alignment pin that
1936 goes through a hole in the PC board when you have the cable
1940 Attach a battery to the TeleMetrum board.
1943 Plug the TeleDongle into your computer's USB port, and power
1947 Run AltosUI, and select 'Flash Image' from the File menu.
1950 Pick the TeleDongle device from the list, identifying it as the
1954 Select the image you want put on the TeleMetrum, which should have a
1955 name in the form telemetrum-v1.2-1.0.0.ihx. It should be visible
1956 in the default directory, if not you may have to poke around
1957 your system to find it.
1960 Make sure the configuration parameters are reasonable
1961 looking. If the serial number and/or RF configuration
1962 values aren't right, you'll need to change them.
1965 Hit the 'OK' button and the software should proceed to flash
1966 the TeleMetrum with new firmware, showing a progress bar.
1969 Confirm that the TeleMetrum board seems to have updated OK, which you
1970 can do by plugging in to it over USB and using a terminal program
1971 to connect to the board and issue the 'v' command to check
1975 If something goes wrong, give it another try.
1980 <title>Updating TeleMini Firmware</title>
1981 <orderedlist inheritnum='inherit' numeration='arabic'>
1983 You'll need a special 'programming cable' to reprogram the
1984 TeleMini. It's available on the Altus Metrum web store, or
1985 you can make your own using an 8-pin MicroMaTch connector on
1986 one end and a set of four pins on the other.
1989 Take the 2 screws out of the TeleDongle case to get access
1990 to the circuit board.
1993 Plug the 8-pin end of the programming cable to the matching
1994 connector on the TeleDongle, and the 4-pins into the holes
1995 in the TeleMini circuit board. Note that the MicroMaTch
1996 connector has an alignment pin that goes through a hole in
1997 the PC board when you have the cable oriented correctly, and
1998 that pin 1 on the TeleMini board is marked with a square pad
1999 while the other pins have round pads.
2002 Attach a battery to the TeleMini board.
2005 Plug the TeleDongle into your computer's USB port, and power
2009 Run AltosUI, and select 'Flash Image' from the File menu.
2012 Pick the TeleDongle device from the list, identifying it as the
2016 Select the image you want put on the TeleMini, which should have a
2017 name in the form telemini-v1.0-1.0.0.ihx. It should be visible
2018 in the default directory, if not you may have to poke around
2019 your system to find it.
2022 Make sure the configuration parameters are reasonable
2023 looking. If the serial number and/or RF configuration
2024 values aren't right, you'll need to change them.
2027 Hit the 'OK' button and the software should proceed to flash
2028 the TeleMini with new firmware, showing a progress bar.
2031 Confirm that the TeleMini board seems to have updated OK, which you
2032 can do by configuring it over the radio link through the TeleDongle, or
2033 letting it come up in "flight" mode and listening for telemetry.
2036 If something goes wrong, give it another try.
2041 <title>Updating TeleDongle Firmware</title>
2043 Updating TeleDongle's firmware is just like updating TeleMetrum or TeleMini
2044 firmware, but you use either a TeleMetrum or another TeleDongle as the programmer.
2046 <orderedlist inheritnum='inherit' numeration='arabic'>
2048 Find the 'programming cable' that you got as part of the starter
2049 kit, that has a red 8-pin MicroMaTch connector on one end and a
2050 red 4-pin MicroMaTch connector on the other end.
2053 Find the USB cable that you got as part of the starter kit, and
2054 plug the "mini" end in to the mating connector on TeleMetrum or TeleDongle.
2057 Take the 2 screws out of the TeleDongle case to get access
2058 to the circuit board.
2061 Plug the 8-pin end of the programming cable to the
2062 matching connector on the programmer, and the 4-pin end to the
2063 matching connector on the TeleDongle.
2064 Note that each MicroMaTch connector has an alignment pin that
2065 goes through a hole in the PC board when you have the cable
2069 Attach a battery to the TeleMetrum board if you're using one.
2072 Plug both the programmer and the TeleDongle into your computer's USB
2073 ports, and power up the programmer.
2076 Run AltosUI, and select 'Flash Image' from the File menu.
2079 Pick the programmer device from the list, identifying it as the
2083 Select the image you want put on the TeleDongle, which should have a
2084 name in the form teledongle-v0.2-1.0.0.ihx. It should be visible
2085 in the default directory, if not you may have to poke around
2086 your system to find it.
2089 Make sure the configuration parameters are reasonable
2090 looking. If the serial number and/or RF configuration
2091 values aren't right, you'll need to change them. The TeleDongle
2092 serial number is on the "bottom" of the circuit board, and can
2093 usually be read through the translucent blue plastic case without
2094 needing to remove the board from the case.
2097 Hit the 'OK' button and the software should proceed to flash
2098 the TeleDongle with new firmware, showing a progress bar.
2101 Confirm that the TeleDongle board seems to have updated OK, which you
2102 can do by plugging in to it over USB and using a terminal program
2103 to connect to the board and issue the 'v' command to check
2104 the version, etc. Once you're happy, remove the programming cable
2105 and put the cover back on the TeleDongle.
2108 If something goes wrong, give it another try.
2112 Be careful removing the programming cable from the locking 8-pin
2113 connector on TeleMetrum. You'll need a fingernail or perhaps a thin
2114 screwdriver or knife blade to gently pry the locking ears out
2115 slightly to extract the connector. We used a locking connector on
2116 TeleMetrum to help ensure that the cabling to companion boards
2117 used in a rocket don't ever come loose accidentally in flight.
2122 <title>Hardware Specifications</title>
2124 <title>TeleMetrum Specifications</title>
2128 Recording altimeter for model rocketry.
2133 Supports dual deployment (can fire 2 ejection charges).
2138 70cm ham-band transceiver for telemetry down-link.
2143 Barometric pressure sensor good to 45k feet MSL.
2148 1-axis high-g accelerometer for motor characterization, capable of
2149 +/- 50g using default part.
2154 On-board, integrated GPS receiver with 5Hz update rate capability.
2159 On-board 1 megabyte non-volatile memory for flight data storage.
2164 USB interface for battery charging, configuration, and data recovery.
2169 Fully integrated support for Li-Po rechargeable batteries.
2174 Uses Li-Po to fire e-matches, can be modified to support
2175 optional separate pyro battery if needed.
2180 2.75 x 1 inch board designed to fit inside 29mm air-frame coupler tube.
2186 <title>TeleMini Specifications</title>
2190 Recording altimeter for model rocketry.
2195 Supports dual deployment (can fire 2 ejection charges).
2200 70cm ham-band transceiver for telemetry down-link.
2205 Barometric pressure sensor good to 45k feet MSL.
2210 On-board 5 kilobyte non-volatile memory for flight data storage.
2215 RF interface for configuration, and data recovery.
2220 Support for Li-Po rechargeable batteries, using an external charger.
2225 Uses Li-Po to fire e-matches, can be modified to support
2226 optional separate pyro battery if needed.
2231 1.5 x .5 inch board designed to fit inside 18mm air-frame coupler tube.
2240 TeleMetrum seems to shut off when disconnected from the
2241 computer. Make sure the battery is adequately charged. Remember the
2242 unit will pull more power than the USB port can deliver before the
2243 GPS enters "locked" mode. The battery charges best when TeleMetrum
2247 It's impossible to stop the TeleDongle when it's in "p" mode, I have
2248 to unplug the USB cable? Make sure you have tried to "escape out" of
2249 this mode. If this doesn't work the reboot procedure for the
2250 TeleDongle *is* to simply unplug it. 'cu' however will retain it's
2251 outgoing buffer IF your "escape out" ('~~') does not work.
2252 At this point using either 'ao-view' (or possibly
2253 'cutemon') instead of 'cu' will 'clear' the issue and allow renewed
2257 The amber LED (on the TeleMetrum) lights up when both
2258 battery and USB are connected. Does this mean it's charging?
2259 Yes, the yellow LED indicates the charging at the 'regular' rate.
2260 If the led is out but the unit is still plugged into a USB port,
2261 then the battery is being charged at a 'trickle' rate.
2264 There are no "dit-dah-dah-dit" sound or lights like the manual mentions?
2265 That's the "pad" mode. Weak batteries might be the problem.
2266 It is also possible that the TeleMetrum is horizontal and the output
2267 is instead a "dit-dit" meaning 'idle'. For TeleMini, it's possible that
2268 it received a command packet which would have left it in "pad" mode.
2271 How do I save flight data?
2272 Live telemetry is written to file(s) whenever AltosUI is connected
2273 to the TeleDongle. The file area defaults to ~/TeleMetrum
2274 but is easily changed using the menus in AltosUI. The files that
2275 are written end in '.telem'. The after-flight
2276 data-dumped files will end in .eeprom and represent continuous data
2277 unlike the .telem files that are subject to losses
2278 along the RF data path.
2279 See the above instructions on what and how to save the eeprom stored
2280 data after physically retrieving your altimeter. Make sure to save
2281 the on-board data after each flight; while the TeleMetrum can store
2282 multiple flights, you never know when you'll lose the altimeter...
2286 <title>Notes for Older Software</title>
2289 Before AltosUI was written, using Altus Metrum devices required
2290 some finesse with the Linux command line. There was a limited
2291 GUI tool, ao-view, which provided functionality similar to the
2292 Monitor Flight window in AltosUI, but everything else was a
2293 fairly 80's experience. This appendix includes documentation for
2294 using that software.
2298 Both TeleMetrum and TeleDongle can be directly communicated
2299 with using USB ports. The first thing you should try after getting
2300 both units plugged into to your computer's USB port(s) is to run
2301 'ao-list' from a terminal-window to see what port-device-name each
2302 device has been assigned by the operating system.
2303 You will need this information to access the devices via their
2304 respective on-board firmware and data using other command line
2305 programs in the AltOS software suite.
2308 TeleMini can be communicated with through a TeleDongle device
2309 over the radio link. When first booted, TeleMini listens for a
2310 TeleDongle device and if it receives a packet, it goes into
2311 'idle' mode. Otherwise, it goes into 'pad' mode and waits to be
2312 launched. The easiest way to get it talking is to start the
2313 communication link on the TeleDongle and the power up the
2317 To access the device's firmware for configuration you need a terminal
2318 program such as you would use to talk to a modem. The software
2319 authors prefer using the program 'cu' which comes from the UUCP package
2320 on most Unix-like systems such as Linux. An example command line for
2321 cu might be 'cu -l /dev/ttyACM0', substituting the correct number
2322 indicated from running the
2323 ao-list program. Another reasonable terminal program for Linux is
2324 'cutecom'. The default 'escape'
2325 character used by CU (i.e. the character you use to
2326 issue commands to cu itself instead of sending the command as input
2327 to the connected device) is a '~'. You will need this for use in
2328 only two different ways during normal operations. First is to exit
2329 the program by sending a '~.' which is called a 'escape-disconnect'
2330 and allows you to close-out from 'cu'. The
2331 second use will be outlined later.
2334 All of the Altus Metrum devices share the concept of a two level
2335 command set in their firmware.
2336 The first layer has several single letter commands. Once
2337 you are using 'cu' (or 'cutecom') sending (typing) a '?'
2338 returns a full list of these
2339 commands. The second level are configuration sub-commands accessed
2340 using the 'c' command, for
2341 instance typing 'c?' will give you this second level of commands
2342 (all of which require the
2343 letter 'c' to access). Please note that most configuration options
2344 are stored only in Flash memory; TeleDongle doesn't provide any storage
2345 for these options and so they'll all be lost when you unplug it.
2348 Try setting these configuration ('c' or second level menu) values. A good
2349 place to start is by setting your call sign. By default, the boards
2350 use 'N0CALL' which is cute, but not exactly legal!
2351 Spend a few minutes getting comfortable with the units, their
2352 firmware, and 'cu' (or possibly 'cutecom').
2353 For instance, try to send
2354 (type) a 'c r 2' and verify the channel change by sending a 'c s'.
2355 Verify you can connect and disconnect from the units while in your
2356 terminal program by sending the escape-disconnect mentioned above.
2359 To set the radio frequency, use the 'c R' command to specify the
2360 radio transceiver configuration parameter. This parameter is computed
2361 using the desired frequency, 'F', the radio calibration parameter, 'C' (showed by the 'c s' command) and
2362 the standard calibration reference frequency, 'S', (normally 434.550MHz):
2366 Round the result to the nearest integer value.
2367 As with all 'c' sub-commands, follow this with a 'c w' to write the
2368 change to the parameter block in the on-board flash on
2369 your altimeter board if you want the change to stay in place across reboots.
2372 To set the apogee delay, use the 'c d' command.
2373 As with all 'c' sub-commands, follow this with a 'c w' to write the
2374 change to the parameter block in the on-board DataFlash chip.
2377 To set the main deployment altitude, use the 'c m' command.
2378 As with all 'c' sub-commands, follow this with a 'c w' to write the
2379 change to the parameter block in the on-board DataFlash chip.
2382 To calibrate the radio frequency, connect the UHF antenna port to a
2383 frequency counter, set the board to 434.550MHz, and use the 'C'
2384 command to generate a CW carrier. Wait for the transmitter temperature
2385 to stabilize and the frequency to settle down.
2386 Then, divide 434.550 MHz by the
2387 measured frequency and multiply by the current radio cal value show
2388 in the 'c s' command. For an unprogrammed board, the default value
2389 is 1186611. Take the resulting integer and program it using the 'c f'
2390 command. Testing with the 'C' command again should show a carrier
2391 within a few tens of Hertz of the intended frequency.
2392 As with all 'c' sub-commands, follow this with a 'c w' to write the
2393 change to the parameter block in the on-board DataFlash chip.
2396 Note that the 'reboot' command, which is very useful on the altimeters,
2397 will likely just cause problems with the dongle. The *correct* way
2398 to reset the dongle is just to unplug and re-plug it.
2401 A fun thing to do at the launch site and something you can do while
2402 learning how to use these units is to play with the radio link access
2403 between an altimeter and the TeleDongle. Be aware that you *must* create
2404 some physical separation between the devices, otherwise the link will
2405 not function due to signal overload in the receivers in each device.
2408 Now might be a good time to take a break and read the rest of this
2409 manual, particularly about the two "modes" that the altimeters
2410 can be placed in. TeleMetrum uses the position of the device when booting
2411 up will determine whether the unit is in "pad" or "idle" mode. TeleMini
2412 enters "idle" mode when it receives a command packet within the first 5 seconds
2413 of being powered up, otherwise it enters "pad" mode.
2416 You can access an altimeter in idle mode from the TeleDongle's USB
2417 connection using the radio link
2418 by issuing a 'p' command to the TeleDongle. Practice connecting and
2419 disconnecting ('~~' while using 'cu') from the altimeter. If
2420 you cannot escape out of the "p" command, (by using a '~~' when in
2421 CU) then it is likely that your kernel has issues. Try a newer version.
2424 Using this radio link allows you to configure the altimeter, test
2425 fire e-matches and igniters from the flight line, check pyro-match
2426 continuity and so forth. You can leave the unit turned on while it
2427 is in 'idle mode' and then place the
2428 rocket vertically on the launch pad, walk away and then issue a
2429 reboot command. The altimeter will reboot and start sending data
2430 having changed to the "pad" mode. If the TeleDongle is not receiving
2431 this data, you can disconnect 'cu' from the TeleDongle using the
2432 procedures mentioned above and THEN connect to the TeleDongle from
2433 inside 'ao-view'. If this doesn't work, disconnect from the
2434 TeleDongle, unplug it, and try again after plugging it back in.
2437 In order to reduce the chance of accidental firing of pyrotechnic
2438 charges, the command to fire a charge is intentionally somewhat
2439 difficult to type, and the built-in help is slightly cryptic to
2440 prevent accidental echoing of characters from the help text back at
2441 the board from firing a charge. The command to fire the apogee
2442 drogue charge is 'i DoIt drogue' and the command to fire the main
2443 charge is 'i DoIt main'.
2446 On TeleMetrum, the GPS will eventually find enough satellites, lock in on them,
2447 and 'ao-view' will both auditorily announce and visually indicate
2449 Now you can launch knowing that you have a good data path and
2450 good satellite lock for flight data and recovery. Remember
2451 you MUST tell ao-view to connect to the TeleDongle explicitly in
2452 order for ao-view to be able to receive data.
2455 The altimeters provide RDF (radio direction finding) tones on
2456 the pad, during descent and after landing. These can be used to
2457 locate the rocket using a directional antenna; the signal
2458 strength providing an indication of the direction from receiver to rocket.
2461 TeleMetrum also provides GPS tracking data, which can further simplify
2462 locating the rocket once it has landed. (The last good GPS data
2463 received before touch-down will be on the data screen of 'ao-view'.)
2466 Once you have recovered the rocket you can download the eeprom
2467 contents using either 'ao-dumplog' (or possibly 'ao-eeprom'), over
2468 either a USB cable or over the radio link using TeleDongle.
2469 And by following the man page for 'ao-postflight' you can create
2470 various data output reports, graphs, and even KML data to see the
2471 flight trajectory in Google-earth. (Moving the viewing angle making
2472 sure to connect the yellow lines while in Google-earth is the proper
2476 As for ao-view.... some things are in the menu but don't do anything
2477 very useful. The developers have stopped working on ao-view to focus
2478 on a new, cross-platform ground station program. So ao-view may or
2479 may not be updated in the future. Mostly you just use
2480 the Log and Device menus. It has a wonderful display of the incoming
2481 flight data and I am sure you will enjoy what it has to say to you
2482 once you enable the voice output!
2486 <title>Calibration</title>
2488 There are only two calibrations required for a TeleMetrum board, and
2489 only one for TeleDongle and TeleMini. All boards are shipped from
2490 the factory pre-calibrated, but the procedures are documented here
2491 in case they are ever needed. Re-calibration is not supported by
2492 AltosUI, you must connect to the board with a serial terminal program
2493 and interact directly with the on-board command interpreter to effect
2497 <title>Radio Frequency</title>
2499 The radio frequency is synthesized from a clock based on the 48 MHz
2500 crystal on the board. The actual frequency of this oscillator
2501 must be measured to generate a calibration constant. While our
2503 bandwidth is wide enough to allow boards to communicate even when
2504 their oscillators are not on exactly the same frequency, performance
2505 is best when they are closely matched.
2506 Radio frequency calibration requires a calibrated frequency counter.
2507 Fortunately, once set, the variation in frequency due to aging and
2508 temperature changes is small enough that re-calibration by customers
2509 should generally not be required.
2512 To calibrate the radio frequency, connect the UHF antenna port to a
2513 frequency counter, set the board to 434.550MHz, and use the 'C'
2514 command in the on-board command interpreter to generate a CW
2515 carrier. For TeleMetrum, this is best done over USB. For TeleMini,
2516 note that the only way to escape the 'C' command is via power cycle
2517 since the board will no longer be listening for commands once it
2518 starts generating a CW carrier.
2521 Wait for the transmitter temperature to stabilize and the frequency
2522 to settle down. Then, divide 434.550 MHz by the
2523 measured frequency and multiply by the current radio cal value show
2524 in the 'c s' command. For an unprogrammed board, the default value
2525 is 1186611. Take the resulting integer and program it using the 'c f'
2526 command. Testing with the 'C' command again should show a carrier
2527 within a few tens of Hertz of the intended frequency.
2528 As with all 'c' sub-commands, follow this with a 'c w' to write the
2529 change to the parameter block in the on-board DataFlash chip.
2532 Note that any time you re-do the radio frequency calibration, the
2533 radio frequency is reset to the default 434.550 Mhz. If you want
2534 to use another frequency, you will have to set that again after
2535 calibration is completed.
2539 <title>TeleMetrum Accelerometer</title>
2541 The TeleMetrum accelerometer we use has its own 5 volt power
2543 the output must be passed through a resistive voltage divider to match
2544 the input of our 3.3 volt ADC. This means that unlike the barometric
2545 sensor, the output of the acceleration sensor is not ratio-metric to
2546 the ADC converter, and calibration is required. Explicitly
2547 calibrating the accelerometers also allows us to load any device
2548 from a Freescale family that includes at least +/- 40g, 50g, 100g,
2549 and 200g parts. Using gravity,
2550 a simple 2-point calibration yields acceptable results capturing both
2551 the different sensitivities and ranges of the different accelerometer
2552 parts and any variation in power supply voltages or resistor values
2553 in the divider network.
2556 To calibrate the acceleration sensor, use the 'c a 0' command. You
2557 will be prompted to orient the board vertically with the UHF antenna
2558 up and press a key, then to orient the board vertically with the
2559 UHF antenna down and press a key. Note that the accuracy of this
2560 calibration depends primarily on how perfectly vertical and still
2561 the board is held during the cal process. As with all 'c'
2562 sub-commands, follow this with a 'c w' to write the
2563 change to the parameter block in the on-board DataFlash chip.
2566 The +1g and -1g calibration points are included in each telemetry
2567 frame and are part of the header stored in onboard flash to be
2568 downloaded after flight. We always store and return raw ADC
2569 samples for each sensor... so nothing is permanently "lost" or
2570 "damaged" if the calibration is poor.
2573 In the unlikely event an accel cal goes badly, it is possible
2574 that TeleMetrum may always come up in 'pad mode' and as such not be
2575 listening to either the USB or radio link. If that happens,
2576 there is a special hook in the firmware to force the board back
2577 in to 'idle mode' so you can re-do the cal. To use this hook, you
2578 just need to ground the SPI clock pin at power-on. This pin is
2579 available as pin 2 on the 8-pin companion connector, and pin 1 is
2580 ground. So either carefully install a fine-gauge wire jumper
2581 between the two pins closest to the index hole end of the 8-pin
2582 connector, or plug in the programming cable to the 8-pin connector
2583 and use a small screwdriver or similar to short the two pins closest
2584 to the index post on the 4-pin end of the programming cable, and
2585 power up the board. It should come up in 'idle mode' (two beeps),
2591 xmlns:xi="http://www.w3.org/2001/XInclude">
2592 <title>Release Notes</title>
2593 <xi:include href="release-notes-1.1.1.xsl" xpointer="xpointer(/article/*)"/>
2594 <xi:include href="release-notes-1.1.xsl" xpointer="xpointer(/article/*)"/>
2595 <xi:include href="release-notes-1.0.1.xsl" xpointer="xpointer(/article/*)"/>
2596 <xi:include href="release-notes-0.9.2.xsl" xpointer="xpointer(/article/*)"/>
2597 <xi:include href="release-notes-0.9.xsl" xpointer="xpointer(/article/*)"/>
2598 <xi:include href="release-notes-0.8.xsl" xpointer="xpointer(/article/*)"/>
2599 <xi:include href="release-notes-0.7.1.xsl" xpointer="xpointer(/article/*)"/>
2603 <!-- LocalWords: Altusmetrum
projects / fw / altos / blob