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.0</revnumber>
40 <date>24 August 2011</date>
42 Updated for software version 1.0. Note that 1.0 represents a
43 telemetry format change, meaning both ends of a link
44 (TeleMetrum/TeleMini and TeleDongle) must be updated or
45 communications will fail.
49 <revnumber>0.9</revnumber>
50 <date>18 January 2011</date>
52 Updated for software version 0.9. Note that 0.9 represents a
53 telemetry format change, meaning both ends of a link (TeleMetrum and
54 TeleDongle) must be updated or communications will fail.
58 <revnumber>0.8</revnumber>
59 <date>24 November 2010</date>
60 <revremark>Updated for software version 0.8 </revremark>
66 Thanks to Bob Finch, W9YA, NAR 12965, TRA 12350 for writing "The
67 Mere-Mortals Quick Start/Usage Guide to the Altus Metrum Starter
68 Kit" which formed the basis of the original Getting Started chapter
69 in this manual. Bob was one of our first customers for a production
70 TeleMetrum, and his continued enthusiasm and contributions
71 are immensely gratifying and highly appreciated!
74 And thanks to Anthony (AJ) Towns for major contributions including
75 the AltosUI graphing and site map code and associated documentation.
76 Free software means that our customers and friends can become our
77 collaborators, and we certainly appreciate this level of
81 Have fun using these products, and we hope to meet all of you
82 out on the rocket flight line somewhere.
85 NAR #87103, TRA #12201
88 NAR #88757, TRA #12200
93 <title>Introduction and Overview</title>
95 Welcome to the Altus Metrum community! Our circuits and software reflect
96 our passion for both hobby rocketry and Free Software. We hope their
97 capabilities and performance will delight you in every way, but by
98 releasing all of our hardware and software designs under open licenses,
99 we also hope to empower you to take as active a role in our collective
103 The first device created for our community was TeleMetrum, a dual
104 deploy altimeter with fully integrated GPS and radio telemetry
105 as standard features, and a "companion interface" that will
106 support optional capabilities in the future.
109 The newest device is TeleMini, a dual deploy altimeter with
110 radio telemetry and radio direction finding. This device is only
111 13mm by 38mm (½ inch by 1½ inches) and can fit easily in an 18mm
115 Complementing TeleMetrum and TeleMini is TeleDongle, a USB to RF
116 interface for communicating with the altimeters. Combined with your
117 choice of antenna and
118 notebook computer, TeleDongle and our associated user interface software
119 form a complete ground station capable of logging and displaying in-flight
120 telemetry, aiding rocket recovery, then processing and archiving flight
121 data for analysis and review.
124 More products will be added to the Altus Metrum family over time, and
125 we currently envision that this will be a single, comprehensive manual
126 for the entire product family.
130 <title>Getting Started</title>
132 The first thing to do after you check the inventory of parts in your
133 "starter kit" is to charge the battery.
136 The TeleMetrum battery can be charged by plugging it into the
137 corresponding socket of the TeleMetrum and then using the USB A to
139 cable to plug the TeleMetrum into your computer's USB socket. The
140 TeleMetrum circuitry will charge the battery whenever it is plugged
141 in, because the TeleMetrum's on-off switch does NOT control the
145 When the GPS chip is initially searching for
146 satellites, TeleMetrum will consume more current than it can pull
147 from the USB port, so the battery must be attached in order to get
148 satellite lock. Once GPS is locked, the current consumption goes back
149 down enough to enable charging while
150 running. So it's a good idea to fully charge the battery as your
151 first item of business so there is no issue getting and maintaining
152 satellite lock. The yellow charge indicator led will go out when the
153 battery is nearly full and the charger goes to trickle charge. It
154 can take several hours to fully recharge a deeply discharged battery.
157 The TeleMini battery can be charged by disconnecting it from the
158 TeleMini board and plugging it into a standalone battery charger
159 board, and connecting that via a USB cable to a laptop or other USB
163 The other active device in the starter kit is the TeleDongle USB to
164 RF interface. If you plug it in to your Mac or Linux computer it should
165 "just work", showing up as a serial port device. Windows systems need
166 driver information that is part of the AltOS download to know that the
167 existing USB modem driver will work. We therefore recommend installing
168 our software before plugging in TeleDongle if you are using a Windows
169 computer. If you are using Linux and are having problems, try moving
170 to a fresher kernel (2.6.33 or newer), as the USB serial driver had
171 ugly bugs in some earlier versions.
174 Next you should obtain and install the AltOS software. These include
175 the AltosUI ground station program, current firmware images for
176 TeleMetrum, TeleMini and TeleDongle, and a number of standalone
177 utilities that are rarely needed. Pre-built binary packages are
178 available for Linux, Microsoft Windows, and recent MacOSX versions.
179 Full source code and build instructions are also available.
180 The latest version may always be downloaded from
181 <ulink url="http://altusmetrum.org/AltOS"/>.
185 <title>Handling Precautions</title>
187 All Altus Metrum products are sophisticated electronic devices.
188 When handled gently and properly installed in an air-frame, they
189 will deliver impressive results. However, as with all electronic
190 devices, there are some precautions you must take.
193 The Lithium Polymer rechargeable batteries have an
194 extraordinary power density. This is great because we can fly with
195 much less battery mass than if we used alkaline batteries or previous
196 generation rechargeable batteries... but if they are punctured
197 or their leads are allowed to short, they can and will release their
199 Thus we recommend that you take some care when handling our batteries
200 and consider giving them some extra protection in your air-frame. We
201 often wrap them in suitable scraps of closed-cell packing foam before
202 strapping them down, for example.
205 The barometric sensors used on both TeleMetrum and TeleMini are
206 sensitive to sunlight. In normal TeleMetrum mounting situations, it
207 and all of the other surface mount components
208 are "down" towards whatever the underlying mounting surface is, so
209 this is not normally a problem. Please consider this, though, when
210 designing an installation, for example, in an air-frame with a
211 see-through plastic payload bay. It is particularly important to
212 consider this with TeleMini, both because the baro sensor is on the
213 "top" of the board, and because many model rockets with payload bays
214 use clear plastic for the payload bay! Replacing these with an opaque
215 cardboard tube, painting them, or wrapping them with a layer of masking
216 tape are all reasonable approaches to keep the sensor out of direct
220 The barometric sensor sampling port must be able to "breathe",
221 both by not being covered by foam or tape or other materials that might
222 directly block the hole on the top of the sensor, and also by having a
223 suitable static vent to outside air.
226 As with all other rocketry electronics, Altus Metrum altimeters must
227 be protected from exposure to corrosive motor exhaust and ejection
232 <title>Hardware Overview</title>
234 TeleMetrum is a 1 inch by 2.75 inch circuit board. It was designed to
235 fit inside coupler for 29mm air-frame tubing, but using it in a tube that
236 small in diameter may require some creativity in mounting and wiring
237 to succeed! The presence of an accelerometer means TeleMetrum should
238 be aligned along the flight axis of the airframe, and by default the 1/4
239 wave UHF wire antenna should be on the nose-cone end of the board. The
240 antenna wire is about 7 inches long, and wiring for a power switch and
241 the e-matches for apogee and main ejection charges depart from the
242 fin can end of the board, meaning an ideal "simple" avionics
243 bay for TeleMetrum should have at least 10 inches of interior length.
246 TeleMini is a 0.5 inch by 1.5 inch circuit board. It was designed to
247 fit inside an 18mm air-frame tube, but using it in a tube that
248 small in diameter may require some creativity in mounting and wiring
249 to succeed! Since there is no accelerometer, TeleMini can be mounted
250 in any convenient orientation. The default 1/4
251 wave UHF wire antenna attached to the center of one end of
252 the board is about 7 inches long, and wiring for a power switch and
253 the e-matches for apogee and main ejection charges depart from the
254 other end of the board, meaning an ideal "simple" avionics
255 bay for TeleMini should have at least 9 inches of interior length.
258 A typical TeleMetrum or TeleMini installation involves attaching
259 only a suitable Lithium Polymer battery, a single pole switch for
260 power on/off, and two pairs of wires connecting e-matches for the
261 apogee and main ejection charges. All Altus Metrum products are
262 designed for use with single-cell batteries with 3.7 volts nominal.
265 By default, we use the unregulated output of the Li-Po battery directly
266 to fire ejection charges. This works marvelously with standard
267 low-current e-matches like the J-Tek from MJG Technologies, and with
268 Quest Q2G2 igniters. However, if you want or need to use a separate
269 pyro battery, check out the "External Pyro Battery" section in this
270 manual for instructions on how to wire that up. The altimeters are
271 designed to work with an external pyro battery of no more than 15 volts.
274 Ejection charges are wired directly to the screw terminal block
275 at the aft end of the altimeter. You'll need a very small straight
276 blade screwdriver for these screws, such as you might find in a
277 jeweler's screwdriver set.
280 TeleMetrum also uses the screw terminal block for the power
281 switch leads. On TeleMini, the power switch leads are soldered
282 directly to the board and can be connected directly to a switch.
285 For most air-frames, the integrated antennas are more than
286 adequate. However, if you are installing in a carbon-fiber or
287 metal electronics bay which is opaque to RF signals, you may need to
288 use off-board external antennas instead. In this case, you can
289 order an altimeter with an SMA connector for the UHF antenna
290 connection, and, on TeleMetrum, you can unplug the integrated GPS
291 antenna and select an appropriate off-board GPS antenna with
292 cable terminating in a U.FL connector.
296 <title>System Operation</title>
298 <title>Firmware Modes </title>
300 The AltOS firmware build for the altimeters has two
301 fundamental modes, "idle" and "flight". Which of these modes
302 the firmware operates in is determined at start up time. For
303 TeleMetrum, the mode is controlled by the orientation of the
304 rocket (well, actually the board, of course...) at the time
305 power is switched on. If the rocket is "nose up", then
306 TeleMetrum assumes it's on a rail or rod being prepared for
307 launch, so the firmware chooses flight mode. However, if the
308 rocket is more or less horizontal, the firmware instead enters
309 idle mode. Since TeleMini doesn't have an accelerometer we can
310 use to determine orientation, "idle" mode is selected when the
311 board receives a command packet within the first five seconds
312 of operation; if no packet is received, the board enters
316 At power on, you will hear three beeps or see three flashes
317 ("S" in Morse code for start up) and then a pause while
318 the altimeter completes initialization and self test, and decides
319 which mode to enter next.
322 In flight or "pad" mode, the altimeter engages the flight
323 state machine, goes into transmit-only mode to
324 send telemetry, and waits for launch to be detected.
325 Flight mode is indicated by an "di-dah-dah-dit" ("P" for pad)
326 on the beeper or lights, followed by beeps or flashes
327 indicating the state of the pyrotechnic igniter continuity.
328 One beep/flash indicates apogee continuity, two beeps/flashes
329 indicate main continuity, three beeps/flashes indicate both
330 apogee and main continuity, and one longer "brap" sound or
331 rapidly alternating lights indicates no continuity. For a
332 dual deploy flight, make sure you're getting three beeps or
333 flashes before launching! For apogee-only or motor eject
334 flights, do what makes sense.
337 If idle mode is entered, you will hear an audible "di-dit" or see
338 two short flashes ("I" for idle), and the flight state machine is
339 disengaged, thus no ejection charges will fire. The altimeters also
340 listen for the radio link when in idle mode for requests sent via
341 TeleDongle. Commands can be issued to a TeleMetrum in idle mode
343 USB or the radio link equivalently. TeleMini only has the radio link.
344 Idle mode is useful for configuring the altimeter, for extracting data
345 from the on-board storage chip after flight, and for ground testing
349 One "neat trick" of particular value when TeleMetrum is used with
350 very large air-frames, is that you can power the board up while the
351 rocket is horizontal, such that it comes up in idle mode. Then you can
352 raise the air-frame to launch position, and issue a 'reset' command
353 via TeleDongle over the radio link to cause the altimeter to reboot and
354 come up in flight mode. This is much safer than standing on the top
355 step of a rickety step-ladder or hanging off the side of a launch
356 tower with a screw-driver trying to turn on your avionics before
363 TeleMetrum includes a complete GPS receiver. A complete explanation
364 of how GPS works is beyond the scope of this manual, but the bottom
365 line is that the TeleMetrum GPS receiver needs to lock onto at least
366 four satellites to obtain a solid 3 dimensional position fix and know
370 TeleMetrum provides backup power to the GPS chip any time a
371 battery is connected. This allows the receiver to "warm start" on
372 the launch rail much faster than if every power-on were a GPS
373 "cold start". In typical operations, powering up TeleMetrum
374 on the flight line in idle mode while performing final air-frame
375 preparation will be sufficient to allow the GPS receiver to cold
376 start and acquire lock. Then the board can be powered down during
377 RSO review and installation on a launch rod or rail. When the board
378 is turned back on, the GPS system should lock very quickly, typically
379 long before igniter installation and return to the flight line are
384 <title>Controlling An Altimeter Over The Radio Link</title>
386 One of the unique features of the Altus Metrum system is
387 the ability to create a two way command link between TeleDongle
388 and an altimeter using the digital radio transceivers built into
389 each device. This allows you to interact with the altimeter from
390 afar, as if it were directly connected to the computer.
393 Any operation which can be performed with TeleMetrum can
394 either be done with TeleMetrum directly connected to the
395 computer via the USB cable, or through the radio
396 link. TeleMini doesn't provide a USB connector and so it is
397 always communicated with over radio. Select the appropriate
398 TeleDongle device when the list of devices is presented and
399 AltosUI will interact with an altimeter over the radio link.
402 One oddity in the current interface is how AltosUI selects the
403 frequency for radio communications. Instead of providing
404 an interface to specifically configure the frequency, it uses
405 whatever frequency was most recently selected for the target
406 TeleDongle device in Monitor Flight mode. If you haven't ever
407 used that mode with the TeleDongle in question, select the
408 Monitor Flight button from the top level UI, and pick the
409 appropriate TeleDongle device. Once the flight monitoring
410 window is open, select the desired frequency and then close it
411 down again. All radio communications will now use that frequency.
416 Save Flight Data—Recover flight data from the rocket without
422 Configure altimeter apogee delays or main deploy heights
423 to respond to changing launch conditions. You can also
424 'reboot' the altimeter. Use this to remotely enable the
425 flight computer by turning TeleMetrum on in "idle" mode,
426 then once the air-frame is oriented for launch, you can
427 reboot the altimeter and have it restart in pad mode
428 without having to climb the scary ladder.
433 Fire Igniters—Test your deployment charges without snaking
434 wires out through holes in the air-frame. Simply assembly the
435 rocket as if for flight with the apogee and main charges
436 loaded, then remotely command the altimeter to fire the
442 Operation over the radio link for configuring an altimeter, ground
443 testing igniters, and so forth uses the same RF frequencies as flight
444 telemetry. To configure the desired TeleDongle frequency, select
445 the monitor flight tab, then use the frequency selector and
446 close the window before performing other desired radio operations.
449 TeleMetrum only enables radio commanding in 'idle' mode, so
450 make sure you have TeleMetrum lying horizontally when you turn
451 it on. Otherwise, TeleMetrum will start in 'pad' mode ready for
452 flight, and will not be listening for command packets from TeleDongle.
455 TeleMini listens for a command packet for five seconds after
456 first being turned on, if it doesn't hear anything, it enters
457 'pad' mode, ready for flight and will no longer listen for
458 command packets. The easiest way to connect to TeleMini is to
459 initiate the command and select the TeleDongle device. At this
460 point, the TeleDongle will be attempting to communicate with
461 the TeleMini. Now turn TeleMini on, and it should immediately
462 start communicating with the TeleDongle and the desired
463 operation can be performed.
466 You can monitor the operation of the radio link by watching the
467 lights on the devices. The red LED will flash each time a packet
468 is tramsitted, while the green LED will light up on TeleDongle when
469 it is waiting to receive a packet from the altimeter.
473 <title>Ground Testing </title>
475 An important aspect of preparing a rocket using electronic deployment
476 for flight is ground testing the recovery system. Thanks
477 to the bi-directional radio link central to the Altus Metrum system,
478 this can be accomplished in a TeleMetrum or TeleMini equipped rocket
479 with less work than you may be accustomed to with other systems. It
483 Just prep the rocket for flight, then power up the altimeter
484 in "idle" mode (placing air-frame horizontal for TeleMetrum or
485 selected the Configure Altimeter tab for TeleMini). This will cause
486 the firmware to go into "idle" mode, in which the normal flight
487 state machine is disabled and charges will not fire without
488 manual command. You can now command the altimeter to fire the apogee
489 or main charges from a safe distance using your computer and
490 TeleDongle and the Fire Igniter tab to complete ejection testing.
494 <title>Radio Link </title>
496 The chip our boards are based on incorporates an RF transceiver, but
497 it's not a full duplex system... each end can only be transmitting or
498 receiving at any given moment. So we had to decide how to manage the
502 By design, the altimeter firmware listens for the radio link when
503 it's in "idle mode", which
504 allows us to use the radio link to configure the rocket, do things like
505 ejection tests, and extract data after a flight without having to
506 crack open the air-frame. However, when the board is in "flight
507 mode", the altimeter only
508 transmits and doesn't listen at all. That's because we want to put
509 ultimate priority on event detection and getting telemetry out of
511 the radio in case the rocket crashes and we aren't able to extract
515 We don't use a 'normal packet radio' mode like APRS because they're
516 just too inefficient. The GFSK modulation we use is FSK with the
517 base-band pulses passed through a
518 Gaussian filter before they go into the modulator to limit the
519 transmitted bandwidth. When combined with the hardware forward error
520 correction support in the cc1111 chip, this allows us to have a very
521 robust 38.4 kilobit data link with only 10 milliwatts of transmit
522 power, a whip antenna in the rocket, and a hand-held Yagi on the
523 ground. We've had flights to above 21k feet AGL with great reception,
524 and calculations suggest we should be good to well over 40k feet AGL
525 with a 5-element yagi on the ground. We hope to fly boards to higher
526 altitudes over time, and would of course appreciate customer feedback
527 on performance in higher altitude flights!
531 <title>Configurable Parameters</title>
533 Configuring an Altus Metrum altimeter for flight is very
534 simple. Even on our baro-only TeleMini board, the use of a Kalman
535 filter means there is no need to set a "mach delay". The few
536 configurable parameters can all be set using AltosUI over USB or
537 or radio link via TeleDongle.
540 <title>Radio Frequency</title>
542 Altus Metrum boards support radio frequencies in the 70cm
543 band. By default, the configuration interface provides a
544 list of 10 "standard" frequencies in 100kHz channels starting at
545 434.550MHz. However, the firmware supports use of
546 any 50kHz multiple within the 70cm band. At any given
547 launch, we highly recommend coordinating when and by whom each
548 frequency will be used to avoid interference. And of course, both
549 altimeter and TeleDongle must be configured to the same
550 frequency to successfully communicate with each other.
554 <title>Apogee Delay</title>
556 Apogee delay is the number of seconds after the altimeter detects flight
557 apogee that the drogue charge should be fired. In most cases, this
558 should be left at the default of 0. However, if you are flying
559 redundant electronics such as for an L3 certification, you may wish
560 to set one of your altimeters to a positive delay so that both
561 primary and backup pyrotechnic charges do not fire simultaneously.
564 The Altus Metrum apogee detection algorithm fires exactly at
565 apogee. If you are also flying an altimeter like the
566 PerfectFlite MAWD, which only supports selecting 0 or 1
567 seconds of apogee delay, you may wish to set the MAWD to 0
568 seconds delay and set the TeleMetrum to fire your backup 2
569 or 3 seconds later to avoid any chance of both charges
570 firing simultaneously. We've flown several air-frames this
571 way quite happily, including Keith's successful L3 cert.
575 <title>Main Deployment Altitude</title>
577 By default, the altimeter will fire the main deployment charge at an
578 elevation of 250 meters (about 820 feet) above ground. We think this
579 is a good elevation for most air-frames, but feel free to change this
580 to suit. In particular, if you are flying two altimeters, you may
582 deployment elevation for the backup altimeter to be something lower
583 than the primary so that both pyrotechnic charges don't fire
588 <title>Maximum Flight Log</title>
590 TeleMetrum version 1.1 and 1.2 have 2MB of on-board flash storage,
591 enough to hold over 40 minutes of data at full data rate
592 (100 samples/second). TeleMetrum 1.0 has 1MB of on-board
593 storage. As data are stored at a reduced rate during descent
594 (10 samples/second), there's plenty of space to store many
595 flights worth of data.
598 The on-board flash is partitioned into separate flight logs,
599 each of a fixed maximum size. Increase the maximum size of
600 each log and you reduce the number of flights that can be
601 stored. Decrease the size and TeleMetrum can store more
605 All of the configuration data is also stored in the flash
606 memory, which consumes 64kB on TeleMetrum v1.1/v1.2 and 256B on
607 TeleMetrum v1.0. This configuration space is not available
608 for storing flight log data.
611 To compute the amount of space needed for a single flight,
612 you can multiply the expected ascent time (in seconds) by
613 800, multiply the expected descent time (in seconds) by 80
614 and add the two together. That will slightly under-estimate
615 the storage (in bytes) needed for the flight. For instance,
616 a flight spending 20 seconds in ascent and 150 seconds in
617 descent will take about (20 * 800) + (150 * 80) = 28000
618 bytes of storage. You could store dozens of these flights in
622 The default size, 192kB, allows for 10 flights of storage on
623 TeleMetrum v1.1/v1.2 and 5 flights on TeleMetrum v1.0. This
624 ensures that you won't need to erase the memory before
625 flying each time while still allowing more than sufficient
626 storage for each flight.
629 As TeleMini does not contain an accelerometer, it stores
630 data at 10 samples per second during ascent and one sample
631 per second during descent. Each sample is a two byte reading
632 from the barometer. These are stored in 5kB of
633 on-chip flash memory which can hold 256 seconds at the
634 ascent rate or 2560 seconds at the descent rate. Because of
635 the limited storage, TeleMini cannot hold data for more than
636 one flight, and so must be erased after each flight or it
637 will not capture data for subsequent flights.
641 <title>Ignite Mode</title>
643 Instead of firing one charge at apogee and another charge at
644 a fixed height above the ground, you can configure the
645 altimeter to fire both at apogee or both during
646 descent. This was added to support an airframe that has two
647 TeleMetrum computers, one in the fin can and one in the
651 Providing the ability to use both igniters for apogee or
652 main allows some level of redundancy without needing two
653 flight computers. In Redundant Apogee or Redundant Main
654 mode, the two charges will be fired two seconds apart.
658 <title>Pad Orientation</title>
660 TeleMetrum measures acceleration along the axis of the
661 board. Which way the board is oriented affects the sign of
662 the acceleration value. Instead of trying to guess which way
663 the board is mounted in the air frame, TeleMetrum must be
664 explicitly configured for either Antenna Up or Antenna
665 Down. The default, Antenna Up, expects the end of the
666 TeleMetrum board connected to the 70cm antenna to be nearest
667 the nose of the rocket, with the end containing the screw
668 terminals nearest the tail.
676 <title>AltosUI</title>
678 The AltosUI program provides a graphical user interface for
679 interacting with the Altus Metrum product family, including
680 TeleMetrum, TeleMini and TeleDongle. AltosUI can monitor telemetry data,
681 configure TeleMetrum, TeleMini and TeleDongle devices and many other
682 tasks. The primary interface window provides a selection of
683 buttons, one for each major activity in the system. This manual
684 is split into chapters, each of which documents one of the tasks
685 provided from the top-level toolbar.
688 <title>Monitor Flight</title>
689 <subtitle>Receive, Record and Display Telemetry Data</subtitle>
691 Selecting this item brings up a dialog box listing all of the
692 connected TeleDongle devices. When you choose one of these,
693 AltosUI will create a window to display telemetry data as
694 received by the selected TeleDongle device.
697 All telemetry data received are automatically recorded in
698 suitable log files. The name of the files includes the current
699 date and rocket serial and flight numbers.
702 The radio frequency being monitored by the TeleDongle device is
703 displayed at the top of the window. You can configure the
704 frequency by clicking on the frequency box and selecting the desired
705 frequency. AltosUI remembers the last frequency selected for each
706 TeleDongle and selects that automatically the next time you use
710 Below the TeleDongle frequency selector, the window contains a few
711 significant pieces of information about the altimeter providing
712 the telemetry data stream:
716 <para>The configured call-sign</para>
719 <para>The device serial number</para>
722 <para>The flight number. Each altimeter remembers how many
728 The rocket flight state. Each flight passes through several
729 states including Pad, Boost, Fast, Coast, Drogue, Main and
735 The Received Signal Strength Indicator value. This lets
736 you know how strong a signal TeleDongle is receiving. The
737 radio inside TeleDongle operates down to about -99dBm;
738 weaker signals may not be receivable. The packet link uses
739 error detection and correction techniques which prevent
740 incorrect data from being reported.
745 Finally, the largest portion of the window contains a set of
746 tabs, each of which contain some information about the rocket.
747 They're arranged in 'flight order' so that as the flight
748 progresses, the selected tab automatically switches to display
749 data relevant to the current state of the flight. You can select
750 other tabs at any time. The final 'table' tab displays all of
751 the raw telemetry values in one place in a spreadsheet-like format.
754 <title>Launch Pad</title>
756 The 'Launch Pad' tab shows information used to decide when the
757 rocket is ready for flight. The first elements include red/green
758 indicators, if any of these is red, you'll want to evaluate
759 whether the rocket is ready to launch:
763 Battery Voltage. This indicates whether the Li-Po battery
764 powering the TeleMetrum has sufficient charge to last for
765 the duration of the flight. A value of more than
766 3.7V is required for a 'GO' status.
771 Apogee Igniter Voltage. This indicates whether the apogee
772 igniter has continuity. If the igniter has a low
773 resistance, then the voltage measured here will be close
774 to the Li-Po battery voltage. A value greater than 3.2V is
775 required for a 'GO' status.
780 Main Igniter Voltage. This indicates whether the main
781 igniter has continuity. If the igniter has a low
782 resistance, then the voltage measured here will be close
783 to the Li-Po battery voltage. A value greater than 3.2V is
784 required for a 'GO' status.
789 On-board Data Logging. This indicates whether there is
790 space remaining on-board to store flight data for the
791 upcoming flight. If you've downloaded data, but failed
792 to erase flights, there may not be any space
793 left. TeleMetrum can store multiple flights, depending
794 on the configured maximum flight log size. TeleMini
795 stores only a single flight, so it will need to be
796 downloaded and erased after each flight to capture
797 data. This only affects on-board flight logging; the
798 altimeter will still transmit telemetry and fire
799 ejection charges at the proper times.
804 GPS Locked. For a TeleMetrum device, this indicates whether the GPS receiver is
805 currently able to compute position information. GPS requires
806 at least 4 satellites to compute an accurate position.
811 GPS Ready. For a TeleMetrum device, this indicates whether GPS has reported at least
812 10 consecutive positions without losing lock. This ensures
813 that the GPS receiver has reliable reception from the
819 The Launchpad tab also shows the computed launch pad position
820 and altitude, averaging many reported positions to improve the
826 <title>Ascent</title>
828 This tab is shown during Boost, Fast and Coast
829 phases. The information displayed here helps monitor the
830 rocket as it heads towards apogee.
833 The height, speed and acceleration are shown along with the
834 maximum values for each of them. This allows you to quickly
835 answer the most commonly asked questions you'll hear during
839 The current latitude and longitude reported by the TeleMetrum GPS are
840 also shown. Note that under high acceleration, these values
841 may not get updated as the GPS receiver loses position
842 fix. Once the rocket starts coasting, the receiver should
843 start reporting position again.
846 Finally, the current igniter voltages are reported as in the
847 Launch Pad tab. This can help diagnose deployment failures
848 caused by wiring which comes loose under high acceleration.
852 <title>Descent</title>
854 Once the rocket has reached apogee and (we hope) activated the
855 apogee charge, attention switches to tracking the rocket on
856 the way back to the ground, and for dual-deploy flights,
857 waiting for the main charge to fire.
860 To monitor whether the apogee charge operated correctly, the
861 current descent rate is reported along with the current
862 height. Good descent rates vary based on the choice of recovery
863 components, but generally range from 15-30m/s on drogue and should
864 be below 10m/s when under the main parachute in a dual-deploy flight.
867 For TeleMetrum altimeters, you can locate the rocket in the sky
868 using the elevation and
869 bearing information to figure out where to look. Elevation is
870 in degrees above the horizon. Bearing is reported in degrees
871 relative to true north. Range can help figure out how big the
872 rocket will appear. Note that all of these values are relative
873 to the pad location. If the elevation is near 90°, the rocket
874 is over the pad, not over you.
877 Finally, the igniter voltages are reported in this tab as
878 well, both to monitor the main charge as well as to see what
879 the status of the apogee charge is. Note that some commercial
880 e-matches are designed to retain continuity even after being
881 fired, and will continue to show as green or return from red to
886 <title>Landed</title>
888 Once the rocket is on the ground, attention switches to
889 recovery. While the radio signal is often lost once the
890 rocket is on the ground, the last reported GPS position is
891 generally within a short distance of the actual landing location.
894 The last reported GPS position is reported both by
895 latitude and longitude as well as a bearing and distance from
896 the launch pad. The distance should give you a good idea of
897 whether to walk or hitch a ride. Take the reported
898 latitude and longitude and enter them into your hand-held GPS
899 unit and have that compute a track to the landing location.
902 Both TeleMini and TeleMetrum will continue to transmit RDF
903 tones after landing, allowing you to locate the rocket by
904 following the radio signal if necessary. You may need to get
905 away from the clutter of the flight line, or even get up on
906 a hill (or your neighbor's RV roof) to receive the RDF signal.
909 The maximum height, speed and acceleration reported
910 during the flight are displayed for your admiring observers.
911 The accuracy of these immediate values depends on the quality
912 of your radio link and how many packets were received.
913 Recovering the on-board data after flight will likely yield
914 more precise results.
917 To get more detailed information about the flight, you can
918 click on the 'Graph Flight' button which will bring up a
919 graph window for the current flight.
923 <title>Site Map</title>
925 When the TeleMetrum has a GPS fix, the Site Map tab will map
926 the rocket's position to make it easier for you to locate the
927 rocket, both while it is in the air, and when it has landed. The
928 rocket's state is indicated by color: white for pad, red for
929 boost, pink for fast, yellow for coast, light blue for drogue,
930 dark blue for main, and black for landed.
933 The map's scale is approximately 3m (10ft) per pixel. The map
934 can be dragged using the left mouse button. The map will attempt
935 to keep the rocket roughly centered while data is being received.
938 Images are fetched automatically via the Google Maps Static API,
939 and cached on disk for reuse. If map images cannot be downloaded,
940 the rocket's path will be traced on a dark gray background
944 You can pre-load images for your favorite launch sites
945 before you leave home; check out the 'Preload Maps' section below.
950 <title>Save Flight Data</title>
952 The altimeter records flight data to its internal flash memory.
953 TeleMetrum data is recorded at a much higher rate than the telemetry
954 system can handle, and is not subject to radio drop-outs. As
955 such, it provides a more complete and precise record of the
956 flight. The 'Save Flight Data' button allows you to read the
957 flash memory and write it to disk. As TeleMini has only a barometer, it
958 records data at the same rate as the telemetry signal, but there will be
959 no data lost due to telemetry drop-outs.
962 Clicking on the 'Save Flight Data' button brings up a list of
963 connected TeleMetrum and TeleDongle devices. If you select a
964 TeleMetrum device, the flight data will be downloaded from that
965 device directly. If you select a TeleDongle device, flight data
966 will be downloaded from an altimeter over radio link via the
967 specified TeleDongle. See the chapter on Controlling An Altimeter
968 Over The Radio Link for more information.
971 After the device has been selected, a dialog showing the
972 flight data saved in the device will be shown allowing you to
973 select which flights to download and which to delete. With
974 version 0.9 or newer firmware, you must erase flights in order
975 for the space they consume to be reused by another
976 flight. This prevents accidentally losing flight data
977 if you neglect to download data before flying again. Note that
978 if there is no more space available in the device, then no
979 data will be recorded during the next flight.
982 The file name for each flight log is computed automatically
983 from the recorded flight date, altimeter serial number and
984 flight number information.
988 <title>Replay Flight</title>
990 Select this button and you are prompted to select a flight
991 record file, either a .telem file recording telemetry data or a
992 .eeprom file containing flight data saved from the altimeter
996 Once a flight record is selected, the flight monitor interface
997 is displayed and the flight is re-enacted in real time. Check
998 the Monitor Flight chapter above to learn how this window operates.
1002 <title>Graph Data</title>
1004 Select this button and you are prompted to select a flight
1005 record file, either a .telem file recording telemetry data or a
1006 .eeprom file containing flight data saved from
1010 Once a flight record is selected, a window with two tabs is
1011 opened. The first tab contains a graph with acceleration
1012 (blue), velocity (green) and altitude (red) of the flight,
1013 measured in metric units. The
1014 apogee(yellow) and main(magenta) igniter voltages are also
1015 displayed; high voltages indicate continuity, low voltages
1016 indicate open circuits. The second tab contains some basic
1020 The graph can be zoomed into a particular area by clicking and
1021 dragging down and to the right. Once zoomed, the graph can be
1022 reset by clicking and dragging up and to the left. Holding down
1023 control and clicking and dragging allows the graph to be panned.
1024 The right mouse button causes a pop-up menu to be displayed, giving
1025 you the option save or print the plot.
1028 Note that telemetry files will generally produce poor graphs
1029 due to the lower sampling rate and missed telemetry packets.
1030 Use saved flight data in .eeprom files for graphing where possible.
1034 <title>Export Data</title>
1036 This tool takes the raw data files and makes them available for
1037 external analysis. When you select this button, you are prompted to
1039 data file (either .eeprom or .telem will do, remember that
1040 .eeprom files contain higher resolution and more continuous
1041 data). Next, a second dialog appears which is used to select
1042 where to write the resulting file. It has a selector to choose
1043 between CSV and KML file formats.
1046 <title>Comma Separated Value Format</title>
1048 This is a text file containing the data in a form suitable for
1049 import into a spreadsheet or other external data analysis
1050 tool. The first few lines of the file contain the version and
1051 configuration information from the altimeter, then
1052 there is a single header line which labels all of the
1053 fields. All of these lines start with a '#' character which
1054 many tools can be configured to skip over.
1057 The remaining lines of the file contain the data, with each
1058 field separated by a comma and at least one space. All of
1059 the sensor values are converted to standard units, with the
1060 barometric data reported in both pressure, altitude and
1061 height above pad units.
1065 <title>Keyhole Markup Language (for Google Earth)</title>
1067 This is the format used by Google Earth to provide an overlay
1068 within that application. With this, you can use Google Earth to
1069 see the whole flight path in 3D.
1074 <title>Configure Altimeter</title>
1076 Select this button and then select either a TeleMetrum or
1077 TeleDongle Device from the list provided. Selecting a TeleDongle
1078 device will use the radio link to configure a remote altimeter.
1081 The first few lines of the dialog provide information about the
1082 connected device, including the product name,
1083 software version and hardware serial number. Below that are the
1084 individual configuration entries.
1087 At the bottom of the dialog, there are four buttons:
1092 Save. This writes any changes to the
1093 configuration parameter block in flash memory. If you don't
1094 press this button, any changes you make will be lost.
1099 Reset. This resets the dialog to the most recently saved values,
1100 erasing any changes you have made.
1105 Reboot. This reboots the device. Use this to
1106 switch from idle to pad mode by rebooting once the rocket is
1107 oriented for flight, or to confirm changes you think you saved
1113 Close. This closes the dialog. Any unsaved changes will be
1119 The rest of the dialog contains the parameters to be configured.
1122 <title>Main Deploy Altitude</title>
1124 This sets the altitude (above the recorded pad altitude) at
1125 which the 'main' igniter will fire. The drop-down menu shows
1126 some common values, but you can edit the text directly and
1127 choose whatever you like. If the apogee charge fires below
1128 this altitude, then the main charge will fire two seconds
1129 after the apogee charge fires.
1133 <title>Apogee Delay</title>
1135 When flying redundant electronics, it's often important to
1136 ensure that multiple apogee charges don't fire at precisely
1137 the same time, as that can over pressurize the apogee deployment
1138 bay and cause a structural failure of the air-frame. The Apogee
1139 Delay parameter tells the flight computer to fire the apogee
1140 charge a certain number of seconds after apogee has been
1145 <title>Radio Frequency</title>
1147 This configures which of the configured frequencies to use for both
1148 telemetry and packet command mode. Note that if you set this
1149 value via packet command mode, you will have to reconfigure
1150 the TeleDongle frequency before you will be able to use packet
1155 <title>Radio Calibration</title>
1157 The radios in every Altus Metrum device are calibrated at the
1158 factory to ensure that they transmit and receive on the
1159 specified frequency. If you need to you can adjust the calibration
1160 by changing this value. Do not do this without understanding what
1161 the value means, read the appendix on calibration and/or the source
1162 code for more information. To change a TeleDongle's calibration,
1163 you must reprogram the unit completely.
1167 <title>Callsign</title>
1169 This sets the call sign included in each telemetry packet. Set this
1170 as needed to conform to your local radio regulations.
1174 <title>Maximum Flight Log Size</title>
1176 This sets the space (in kilobytes) allocated for each flight
1177 log. The available space will be divided into chunks of this
1178 size. A smaller value will allow more flights to be stored,
1179 a larger value will record data from longer flights.
1183 <title>Ignite Mode</title>
1185 TeleMetrum and TeleMini provide two igniter channels as they
1186 were originally designed as dual-deploy flight
1187 computers. This configuration parameter allows the two
1188 channels to be used in different configurations.
1193 Dual Deploy. This is the usual mode of operation; the
1194 'apogee' channel is fired at apogee and the 'main'
1195 channel at the height above ground specified by the
1196 'Main Deploy Altitude' during descent.
1201 Redundant Apogee. This fires both channels at
1202 apogee, the 'apogee' channel first followed after a two second
1203 delay by the 'main' channel.
1208 Redundant Main. This fires both channels at the
1209 height above ground specified by the Main Deploy
1210 Altitude setting during descent. The 'apogee'
1211 channel is fired first, followed after a two second
1212 delay by the 'main' channel.
1218 <title>Pad Orientation</title>
1220 Because it includes an accelerometer, TeleMetrum is
1221 sensitive to the orientation of the board. By default, it
1222 expects the antenna end to point forward. This parameter
1223 allows that default to be changed, permitting the board to
1224 be mounted with the antenna pointing aft instead.
1229 Antenna Up. In this mode, the antenna end of the
1230 TeleMetrum board must point forward, in line with the
1231 expected flight path.
1236 Antenna Down. In this mode, the antenna end of the
1237 TeleMetrum board must point aft, in line with the
1238 expected flight path.
1245 <title>Configure AltosUI</title>
1247 This button presents a dialog so that you can configure the AltosUI global settings.
1250 <title>Voice Settings</title>
1252 AltosUI provides voice announcements during flight so that you
1253 can keep your eyes on the sky and still get information about
1254 the current flight status. However, sometimes you don't want
1259 <para>Enable—turns all voice announcements on and off</para>
1263 Test Voice—Plays a short message allowing you to verify
1264 that the audio system is working and the volume settings
1271 <title>Log Directory</title>
1273 AltosUI logs all telemetry data and saves all TeleMetrum flash
1274 data to this directory. This directory is also used as the
1275 staring point when selecting data files for display or export.
1278 Click on the directory name to bring up a directory choosing
1279 dialog, select a new directory and click 'Select Directory' to
1280 change where AltosUI reads and writes data files.
1284 <title>Callsign</title>
1286 This value is transmitted in each command packet sent from
1287 TeleDongle and received from an altimeter. It is not used in
1288 telemetry mode, as the callsign configured in the altimeter board
1289 is included in all telemetry packets. Configure this
1290 with the AltosUI operators call sign as needed to comply with
1291 your local radio regulations.
1295 <title>Imperial Units</title>
1297 This switches between metric units (meters) and imperial
1298 units (feet and miles). This affects the display of values
1299 use during flight monitoring, data graphing and all of the
1300 voice announcements. It does not change the units used when
1301 exporting to CSV files, those are always produced in metric units.
1305 <title>Font Size</title>
1307 Selects the set of fonts used in the flight monitor
1308 window. Choose between the small, medium and large sets.
1312 <title>Serial Debug</title>
1314 This causes all communication with a connected device to be
1315 dumped to the console from which AltosUI was started. If
1316 you've started it from an icon or menu entry, the output
1317 will simply be discarded. This mode can be useful to debug
1318 various serial communication issues.
1322 <title>Manage Frequencies</title>
1324 This brings up a dialog where you can configure the set of
1325 frequencies shown in the various frequency menus. You can
1326 add as many as you like, or even reconfigure the default
1327 set. Changing this list does not affect the frequency
1328 settings of any devices, it only changes the set of
1329 frequencies shown in the menus.
1334 <title>Configure Groundstation</title>
1336 Select this button and then select a TeleDongle Device from the list provided.
1339 The first few lines of the dialog provide information about the
1340 connected device, including the product name,
1341 software version and hardware serial number. Below that are the
1342 individual configuration entries.
1345 Note that the TeleDongle itself doesn't save any configuration
1346 data, the settings here are recorded on the local machine in
1347 the Java preferences database. Moving the TeleDongle to
1348 another machine, or using a different user account on the same
1349 machine will cause settings made here to have no effect.
1352 At the bottom of the dialog, there are three buttons:
1357 Save. This writes any changes to the
1358 local Java preferences file. If you don't
1359 press this button, any changes you make will be lost.
1364 Reset. This resets the dialog to the most recently saved values,
1365 erasing any changes you have made.
1370 Close. This closes the dialog. Any unsaved changes will be
1376 The rest of the dialog contains the parameters to be configured.
1379 <title>Frequency</title>
1381 This configures the frequency to use for both telemetry and
1382 packet command mode. Set this before starting any operation
1383 involving packet command mode so that it will use the right
1384 frequency. Telemetry monitoring mode also provides a menu to
1385 change the frequency, and that menu also sets the same Java
1386 preference value used here.
1390 <title>Radio Calibration</title>
1392 The radios in every Altus Metrum device are calibrated at the
1393 factory to ensure that they transmit and receive on the
1394 specified frequency. To change a TeleDongle's calibration,
1395 you must reprogram the unit completely, so this entry simply
1396 shows the current value and doesn't allow any changes.
1401 <title>Flash Image</title>
1403 This reprograms any Altus Metrum device by using a TeleMetrum
1404 or TeleDongle as a programming dongle. Please read the
1405 directions for flashing devices in the Updating Device
1406 Firmware chapter below.
1409 Once you have the programmer and target devices connected,
1410 push the 'Flash Image' button. That will present a dialog box
1411 listing all of the connected devices. Carefully select the
1412 programmer device, not the device to be programmed.
1415 Next, select the image to flash to the device. These are named
1416 with the product name and firmware version. The file selector
1417 will start in the directory containing the firmware included
1418 with the AltosUI package. Navigate to the directory containing
1419 the desired firmware if it isn't there.
1422 Next, a small dialog containing the device serial number and
1423 RF calibration values should appear. If these values are
1424 incorrect (possibly due to a corrupted image in the device),
1425 enter the correct values here.
1428 Finally, a dialog containing a progress bar will follow the
1429 programming process.
1432 When programming is complete, the target device will
1433 reboot. Note that if the target device is connected via USB, you
1434 will have to unplug it and then plug it back in for the USB
1435 connection to reset so that you can communicate with the device
1440 <title>Fire Igniter</title>
1442 This activates the igniter circuits in TeleMetrum to help test
1443 recovery systems deployment. Because this command can operate
1444 over the Packet Command Link, you can prepare the rocket as
1445 for flight and then test the recovery system without needing
1446 to snake wires inside the air-frame.
1449 Selecting the 'Fire Igniter' button brings up the usual device
1450 selection dialog. Pick the desired TeleDongle or TeleMetrum
1451 device. This brings up another window which shows the current
1452 continuity test status for both apogee and main charges.
1455 Next, select the desired igniter to fire. This will enable the
1459 Select the 'Arm' button. This enables the 'Fire' button. The
1460 word 'Arm' is replaced by a countdown timer indicating that
1461 you have 10 seconds to press the 'Fire' button or the system
1462 will deactivate, at which point you start over again at
1463 selecting the desired igniter.
1467 <title>Scan Channels</title>
1469 This listens for telemetry packets on all of the configured
1470 frequencies, displaying information about each device it
1471 receives a packet from. You can select which of the three
1472 telemetry formats should be tried; by default, it only listens
1473 for the standard telemetry packets used in v1.0 and later
1478 <title>Load Maps</title>
1480 Before heading out to a new launch site, you can use this to
1481 load satellite images in case you don't have internet
1482 connectivity at the site. This loads a fairly large area
1483 around the launch site, which should cover any flight you're likely to make.
1486 There's a drop-down menu of launch sites we know about; if
1487 your favorites aren't there, please let us know the lat/lon
1488 and name of the site. The contents of this list are actually
1489 downloaded at run-time, so as new sites are sent in, they'll
1490 get automatically added to this list.
1493 If the launch site isn't in the list, you can manually enter the lat/lon values
1496 Clicking the 'Load Map' button will fetch images from Google
1497 Maps; note that Google limits how many images you can fetch at
1498 once, so if you load more than one launch site, you may get
1499 some gray areas in the map which indicate that Google is tired
1500 of sending data to you. Try again later.
1504 <title>Monitor Idle</title>
1506 This brings up a dialog similar to the Monitor Flight UI,
1507 except it works with the altimeter in "idle" mode by sending
1508 query commands to discover the current state rather than
1509 listening for telemetry packets.
1514 <title>Using Altus Metrum Products</title>
1516 <title>Being Legal</title>
1518 First off, in the US, you need an <ulink url="http://www.altusmetrum.org/Radio/">amateur radio license</ulink> or
1519 other authorization to legally operate the radio transmitters that are part
1524 <title>In the Rocket</title>
1526 In the rocket itself, you just need a <ulink url="http://www.altusmetrum.org/TeleMetrum/">TeleMetrum</ulink> or
1527 <ulink url="http://www.altusmetrum.org/TeleMini/">TeleMini</ulink> board and
1528 a single-cell, 3.7 volt nominal Li-Po rechargeable battery. An
1529 850mAh battery weighs less than a 9V alkaline battery, and will
1530 run a TeleMetrum for hours.
1531 A 110mAh battery weighs less than a triple A battery and will run a TeleMetrum for
1532 a few hours, or a TeleMini for much (much) longer.
1535 By default, we ship the altimeters with a simple wire antenna. If your
1536 electronics bay or the air-frame it resides within is made of carbon fiber,
1537 which is opaque to RF signals, you may choose to have an SMA connector
1538 installed so that you can run a coaxial cable to an antenna mounted
1539 elsewhere in the rocket.
1543 <title>On the Ground</title>
1545 To receive the data stream from the rocket, you need an antenna and short
1546 feed-line connected to one of our <ulink url="http://www.altusmetrum.org/TeleDongle/">TeleDongle</ulink> units. The
1547 TeleDongle in turn plugs directly into the USB port on a notebook
1548 computer. Because TeleDongle looks like a simple serial port, your computer
1549 does not require special device drivers... just plug it in.
1552 The GUI tool, AltosUI, is written in Java and runs across
1553 Linux, Mac OS and Windows. There's also a suite of C tools
1554 for Linux which can perform most of the same tasks.
1557 After the flight, you can use the radio link to extract the more detailed data
1558 logged in either TeleMetrum or TeleMini devices, or you can use a mini USB cable to plug into the
1559 TeleMetrum board directly. Pulling out the data without having to open up
1560 the rocket is pretty cool! A USB cable is also how you charge the Li-Po
1561 battery, so you'll want one of those anyway... the same cable used by lots
1562 of digital cameras and other modern electronic stuff will work fine.
1565 If your TeleMetrum-equipped rocket lands out of sight, you may enjoy having a hand-held GPS
1566 receiver, so that you can put in a way-point for the last reported rocket
1567 position before touch-down. This makes looking for your rocket a lot like
1568 Geo-Caching... just go to the way-point and look around starting from there.
1571 You may also enjoy having a ham radio "HT" that covers the 70cm band... you
1572 can use that with your antenna to direction-find the rocket on the ground
1573 the same way you can use a Walston or Beeline tracker. This can be handy
1574 if the rocket is hiding in sage brush or a tree, or if the last GPS position
1575 doesn't get you close enough because the rocket dropped into a canyon, or
1576 the wind is blowing it across a dry lake bed, or something like that... Keith
1577 and Bdale both currently own and use the Yaesu VX-7R at launches.
1580 So, to recap, on the ground the hardware you'll need includes:
1581 <orderedlist inheritnum='inherit' numeration='arabic'>
1583 an antenna and feed-line
1592 optionally, a hand-held GPS receiver
1595 optionally, an HT or receiver covering 435 MHz
1600 The best hand-held commercial directional antennas we've found for radio
1601 direction finding rockets are from
1602 <ulink url="http://www.arrowantennas.com/" >
1605 The 440-3 and 440-5 are both good choices for finding a
1606 TeleMetrum- or TeleMini- equipped rocket when used with a suitable 70cm HT.
1610 <title>Data Analysis</title>
1612 Our software makes it easy to log the data from each flight, both the
1613 telemetry received during the flight itself, and the more
1614 complete data log recorded in the flash memory on the altimeter
1615 board. Once this data is on your computer, our post-flight tools make it
1616 easy to quickly get to the numbers everyone wants, like apogee altitude,
1617 max acceleration, and max velocity. You can also generate and view a
1618 standard set of plots showing the altitude, acceleration, and
1619 velocity of the rocket during flight. And you can even export a TeleMetrum data file
1620 usable with Google Maps and Google Earth for visualizing the flight path
1621 in two or three dimensions!
1624 Our ultimate goal is to emit a set of files for each flight that can be
1625 published as a web page per flight, or just viewed on your local disk with
1630 <title>Future Plans</title>
1632 In the future, we intend to offer "companion boards" for the rocket that will
1633 plug in to TeleMetrum to collect additional data, provide more pyro channels,
1637 We are also working on the design of a hand-held ground terminal that will
1638 allow monitoring the rocket's status, collecting data during flight, and
1639 logging data after flight without the need for a notebook computer on the
1640 flight line. Particularly since it is so difficult to read most notebook
1641 screens in direct sunlight, we think this will be a great thing to have.
1644 Because all of our work is open, both the hardware designs and the software,
1645 if you have some great idea for an addition to the current Altus Metrum family,
1646 feel free to dive in and help! Or let us know what you'd like to see that
1647 we aren't already working on, and maybe we'll get excited about it too...
1652 <title>Altimeter Installation Recommendations</title>
1654 Building high-power rockets that fly safely is hard enough. Mix
1655 in some sophisticated electronics and a bunch of radio energy
1656 and oftentimes you find few perfect solutions. This chapter
1657 contains some suggestions about how to install Altus Metrum
1658 products into the rocket air-frame, including how to safely and
1659 reliably mix a variety of electronics into the same air-frame.
1662 <title>Mounting the Altimeter</title>
1664 The first consideration is to ensure that the altimeter is
1665 securely fastened to the air-frame. For TeleMetrum, we use
1666 nylon standoffs and nylon screws; they're good to at least 50G
1667 and cannot cause any electrical issues on the board. For
1668 TeleMini, we usually cut small pieces of 1/16" balsa to fit
1669 under the screw holes, and then take 2x56 nylon screws and
1670 screw them through the TeleMini mounting holes, through the
1671 balsa and into the underlying material.
1673 <orderedlist inheritnum='inherit' numeration='arabic'>
1675 Make sure TeleMetrum is aligned precisely along the axis of
1676 acceleration so that the accelerometer can accurately
1677 capture data during the flight.
1680 Watch for any metal touching components on the
1681 board. Shorting out connections on the bottom of the board
1682 can cause the altimeter to fail during flight.
1687 <title>Dealing with the Antenna</title>
1689 The antenna supplied is just a piece of solid, insulated,
1690 wire. If it gets damaged or broken, it can be easily
1691 replaced. It should be kept straight and not cut; bending or
1692 cutting it will change the resonant frequency and/or
1693 impedance, making it a less efficient radiator and thus
1694 reducing the range of the telemetry signal.
1697 Keeping metal away from the antenna will provide better range
1698 and a more even radiation pattern. In most rockets, it's not
1699 entirely possible to isolate the antenna from metal
1700 components; there are often bolts, all-thread and wires from other
1701 electronics to contend with. Just be aware that the more stuff
1702 like this around the antenna, the lower the range.
1705 Make sure the antenna is not inside a tube made or covered
1706 with conducting material. Carbon fiber is the most common
1707 culprit here -- CF is a good conductor and will effectively
1708 shield the antenna, dramatically reducing signal strength and
1709 range. Metallic flake paint is another effective shielding
1710 material which is to be avoided around any antennas.
1713 If the ebay is large enough, it can be convenient to simply
1714 mount the altimeter at one end and stretch the antenna out
1715 inside. Taping the antenna to the sled can keep it straight
1716 under acceleration. If there are metal rods, keep the
1717 antenna as far away as possible.
1720 For a shorter ebay, it's quite practical to have the antenna
1721 run through a bulkhead and into an adjacent bay. Drill a small
1722 hole in the bulkhead, pass the antenna wire through it and
1723 then seal it up with glue or clay. We've also used acrylic
1724 tubing to create a cavity for the antenna wire. This works a
1725 bit better in that the antenna is known to stay straight and
1726 not get folded by recovery components in the bay. Angle the
1727 tubing towards the side wall of the rocket and it ends up
1728 consuming very little space.
1731 If you need to place the antenna at a distance from the
1732 altimeter, you can replace the antenna with an edge-mounted
1733 SMA connector, and then run 50Ω coax from the board to the
1734 antenna. Building a remote antenna is beyond the scope of this
1739 <title>Preserving GPS Reception</title>
1741 The GPS antenna and receiver in TeleMetrum are highly
1742 sensitive and normally have no trouble tracking enough
1743 satellites to provide accurate position information for
1744 recovering the rocket. However, there are many ways to
1745 attenuate the GPS signal.
1746 <orderedlist inheritnum='inherit' numeration='arabic'>
1748 Conductive tubing or coatings. Carbon fiber and metal
1749 tubing, or metallic paint will all dramatically attenuate the
1750 GPS signal. We've never heard of anyone successfully
1751 receiving GPS from inside these materials.
1754 Metal components near the GPS patch antenna. These will
1755 de-tune the patch antenna, changing the resonant frequency
1756 away from the L1 carrier and reduce the effectiveness of the
1757 antenna. You can place as much stuff as you like beneath the
1758 antenna as that's covered with a ground plane. But, keep
1759 wires and metal out from above the patch antenna.
1765 <title>Radio Frequency Interference</title>
1767 Any altimeter will generate RFI; the digital circuits use
1768 high-frequency clocks that spray radio interference across a
1769 wide band. Altus Metrum altimeters generate intentional radio
1770 signals as well, increasing the amount of RF energy around the board.
1773 Rocketry altimeters also use precise sensors measuring air
1774 pressure and acceleration. Tiny changes in voltage can cause
1775 these sensor readings to vary by a huge amount. When the
1776 sensors start mis-reporting data, the altimeter can either
1777 fire the igniters at the wrong time, or not fire them at all.
1780 Voltages are induced when radio frequency energy is
1781 transmitted from one circuit to another. Here are things that
1782 influence the induced voltage and current:
1786 Keep wires from different circuits apart. Moving circuits
1787 further apart will reduce RFI.
1790 Avoid parallel wires from different circuits. The longer two
1791 wires run parallel to one another, the larger the amount of
1792 transferred energy. Cross wires at right angles to reduce
1796 Twist wires from the same circuits. Two wires the same
1797 distance from the transmitter will get the same amount of
1798 induced energy which will then cancel out. Any time you have
1799 a wire pair running together, twist the pair together to
1800 even out distances and reduce RFI. For altimeters, this
1801 includes battery leads, switch hookups and igniter
1805 Avoid resonant lengths. Know what frequencies are present
1806 in the environment and avoid having wire lengths near a
1807 natural resonant length. Altusmetrum products transmit on the
1808 70cm amateur band, so you should avoid lengths that are a
1809 simple ratio of that length; essentially any multiple of 1/4
1810 of the wavelength (17.5cm).
1815 <title>The Barometric Sensor</title>
1817 Altusmetrum altimeters measure altitude with a barometric
1818 sensor, essentially measuring the amount of air above the
1819 rocket to figure out how high it is. A large number of
1820 measurements are taken as the altimeter initializes itself to
1821 figure out the pad altitude. Subsequent measurements are then
1822 used to compute the height above the pad.
1825 To accurately measure atmospheric pressure, the ebay
1826 containing the altimeter must be vented outside the
1827 air-frame. The vent must be placed in a region of linear
1828 airflow, have smooth edges, and away from areas of increasing or
1829 decreasing pressure.
1832 The barometric sensor in the altimeter is quite sensitive to
1833 chemical damage from the products of APCP or BP combustion, so
1834 make sure the ebay is carefully sealed from any compartment
1835 which contains ejection charges or motors.
1839 <title>Ground Testing</title>
1841 The most important aspect of any installation is careful
1842 ground testing. Bringing an air-frame up to the LCO table which
1843 hasn't been ground tested can lead to delays or ejection
1844 charges firing on the pad, or, even worse, a recovery system
1848 Do a 'full systems' test that includes wiring up all igniters
1849 without any BP and turning on all of the electronics in flight
1850 mode. This will catch any mistakes in wiring and any residual
1851 RFI issues that might accidentally fire igniters at the wrong
1852 time. Let the air-frame sit for several minutes, checking for
1853 adequate telemetry signal strength and GPS lock. If any igniters
1854 fire unexpectedly, find and resolve the issue before loading any
1858 Ground test the ejection charges. Prepare the rocket for
1859 flight, loading ejection charges and igniters. Completely
1860 assemble the air-frame and then use the 'Fire Igniters'
1861 interface through a TeleDongle to command each charge to
1862 fire. Make sure the charge is sufficient to robustly separate
1863 the air-frame and deploy the recovery system.
1868 <title>Updating Device Firmware</title>
1870 The big concept to understand is that you have to use a
1871 TeleDongle as a programmer to update a TeleMetrum or TeleMini,
1872 and a TeleMetrum or other TeleDongle to program the TeleDongle
1873 Due to limited memory resources in the cc1111, we don't support
1874 programming directly over USB.
1877 You may wish to begin by ensuring you have current firmware images.
1878 These are distributed as part of the AltOS software bundle that
1879 also includes the AltosUI ground station program. Newer ground
1880 station versions typically work fine with older firmware versions,
1881 so you don't need to update your devices just to try out new
1882 software features. You can always download the most recent
1883 version from <ulink url="http://www.altusmetrum.org/AltOS/"/>.
1886 We recommend updating the altimeter first, before updating TeleDongle.
1889 <title>Updating TeleMetrum Firmware</title>
1890 <orderedlist inheritnum='inherit' numeration='arabic'>
1892 Find the 'programming cable' that you got as part of the starter
1893 kit, that has a red 8-pin MicroMaTch connector on one end and a
1894 red 4-pin MicroMaTch connector on the other end.
1897 Take the 2 screws out of the TeleDongle case to get access
1898 to the circuit board.
1901 Plug the 8-pin end of the programming cable to the
1902 matching connector on the TeleDongle, and the 4-pin end to the
1903 matching connector on the TeleMetrum.
1904 Note that each MicroMaTch connector has an alignment pin that
1905 goes through a hole in the PC board when you have the cable
1909 Attach a battery to the TeleMetrum board.
1912 Plug the TeleDongle into your computer's USB port, and power
1916 Run AltosUI, and select 'Flash Image' from the File menu.
1919 Pick the TeleDongle device from the list, identifying it as the
1923 Select the image you want put on the TeleMetrum, which should have a
1924 name in the form telemetrum-v1.2-1.0.0.ihx. It should be visible
1925 in the default directory, if not you may have to poke around
1926 your system to find it.
1929 Make sure the configuration parameters are reasonable
1930 looking. If the serial number and/or RF configuration
1931 values aren't right, you'll need to change them.
1934 Hit the 'OK' button and the software should proceed to flash
1935 the TeleMetrum with new firmware, showing a progress bar.
1938 Confirm that the TeleMetrum board seems to have updated OK, which you
1939 can do by plugging in to it over USB and using a terminal program
1940 to connect to the board and issue the 'v' command to check
1944 If something goes wrong, give it another try.
1949 <title>Updating TeleMini Firmware</title>
1950 <orderedlist inheritnum='inherit' numeration='arabic'>
1952 You'll need a special 'programming cable' to reprogram the
1953 TeleMini. It's available on the Altus Metrum web store, or
1954 you can make your own using an 8-pin MicroMaTch connector on
1955 one end and a set of four pins on the other.
1958 Take the 2 screws out of the TeleDongle case to get access
1959 to the circuit board.
1962 Plug the 8-pin end of the programming cable to the matching
1963 connector on the TeleDongle, and the 4-pins into the holes
1964 in the TeleMini circuit board. Note that the MicroMaTch
1965 connector has an alignment pin that goes through a hole in
1966 the PC board when you have the cable oriented correctly, and
1967 that pin 1 on the TeleMini board is marked with a square pad
1968 while the other pins have round pads.
1971 Attach a battery to the TeleMini board.
1974 Plug the TeleDongle into your computer's USB port, and power
1978 Run AltosUI, and select 'Flash Image' from the File menu.
1981 Pick the TeleDongle device from the list, identifying it as the
1985 Select the image you want put on the TeleMini, which should have a
1986 name in the form telemini-v1.0-1.0.0.ihx. It should be visible
1987 in the default directory, if not you may have to poke around
1988 your system to find it.
1991 Make sure the configuration parameters are reasonable
1992 looking. If the serial number and/or RF configuration
1993 values aren't right, you'll need to change them.
1996 Hit the 'OK' button and the software should proceed to flash
1997 the TeleMini with new firmware, showing a progress bar.
2000 Confirm that the TeleMini board seems to have updated OK, which you
2001 can do by configuring it over the radio link through the TeleDongle, or
2002 letting it come up in "flight" mode and listening for telemetry.
2005 If something goes wrong, give it another try.
2010 <title>Updating TeleDongle Firmware</title>
2012 Updating TeleDongle's firmware is just like updating TeleMetrum or TeleMini
2013 firmware, but you use either a TeleMetrum or another TeleDongle as the programmer.
2015 <orderedlist inheritnum='inherit' numeration='arabic'>
2017 Find the 'programming cable' that you got as part of the starter
2018 kit, that has a red 8-pin MicroMaTch connector on one end and a
2019 red 4-pin MicroMaTch connector on the other end.
2022 Find the USB cable that you got as part of the starter kit, and
2023 plug the "mini" end in to the mating connector on TeleMetrum or TeleDongle.
2026 Take the 2 screws out of the TeleDongle case to get access
2027 to the circuit board.
2030 Plug the 8-pin end of the programming cable to the
2031 matching connector on the programmer, and the 4-pin end to the
2032 matching connector on the TeleDongle.
2033 Note that each MicroMaTch connector has an alignment pin that
2034 goes through a hole in the PC board when you have the cable
2038 Attach a battery to the TeleMetrum board if you're using one.
2041 Plug both the programmer and the TeleDongle into your computer's USB
2042 ports, and power up the programmer.
2045 Run AltosUI, and select 'Flash Image' from the File menu.
2048 Pick the programmer device from the list, identifying it as the
2052 Select the image you want put on the TeleDongle, which should have a
2053 name in the form teledongle-v0.2-1.0.0.ihx. It should be visible
2054 in the default directory, if not you may have to poke around
2055 your system to find it.
2058 Make sure the configuration parameters are reasonable
2059 looking. If the serial number and/or RF configuration
2060 values aren't right, you'll need to change them. The TeleDongle
2061 serial number is on the "bottom" of the circuit board, and can
2062 usually be read through the translucent blue plastic case without
2063 needing to remove the board from the case.
2066 Hit the 'OK' button and the software should proceed to flash
2067 the TeleDongle with new firmware, showing a progress bar.
2070 Confirm that the TeleDongle board seems to have updated OK, which you
2071 can do by plugging in to it over USB and using a terminal program
2072 to connect to the board and issue the 'v' command to check
2073 the version, etc. Once you're happy, remove the programming cable
2074 and put the cover back on the TeleDongle.
2077 If something goes wrong, give it another try.
2081 Be careful removing the programming cable from the locking 8-pin
2082 connector on TeleMetrum. You'll need a fingernail or perhaps a thin
2083 screwdriver or knife blade to gently pry the locking ears out
2084 slightly to extract the connector. We used a locking connector on
2085 TeleMetrum to help ensure that the cabling to companion boards
2086 used in a rocket don't ever come loose accidentally in flight.
2091 <title>Hardware Specifications</title>
2093 <title>TeleMetrum Specifications</title>
2097 Recording altimeter for model rocketry.
2102 Supports dual deployment (can fire 2 ejection charges).
2107 70cm ham-band transceiver for telemetry down-link.
2112 Barometric pressure sensor good to 45k feet MSL.
2117 1-axis high-g accelerometer for motor characterization, capable of
2118 +/- 50g using default part.
2123 On-board, integrated GPS receiver with 5Hz update rate capability.
2128 On-board 1 megabyte non-volatile memory for flight data storage.
2133 USB interface for battery charging, configuration, and data recovery.
2138 Fully integrated support for Li-Po rechargeable batteries.
2143 Uses Li-Po to fire e-matches, can be modified to support
2144 optional separate pyro battery if needed.
2149 2.75 x 1 inch board designed to fit inside 29mm air-frame coupler tube.
2155 <title>TeleMini Specifications</title>
2159 Recording altimeter for model rocketry.
2164 Supports dual deployment (can fire 2 ejection charges).
2169 70cm ham-band transceiver for telemetry down-link.
2174 Barometric pressure sensor good to 45k feet MSL.
2179 On-board 5 kilobyte non-volatile memory for flight data storage.
2184 RF interface for battery charging, configuration, and data recovery.
2189 Support for Li-Po rechargeable batteries, using an external charger.
2194 Uses Li-Po to fire e-matches, can be modified to support
2195 optional separate pyro battery if needed.
2200 1.5 x .5 inch board designed to fit inside 18mm air-frame coupler tube.
2209 TeleMetrum seems to shut off when disconnected from the
2210 computer. Make sure the battery is adequately charged. Remember the
2211 unit will pull more power than the USB port can deliver before the
2212 GPS enters "locked" mode. The battery charges best when TeleMetrum
2216 It's impossible to stop the TeleDongle when it's in "p" mode, I have
2217 to unplug the USB cable? Make sure you have tried to "escape out" of
2218 this mode. If this doesn't work the reboot procedure for the
2219 TeleDongle *is* to simply unplug it. 'cu' however will retain it's
2220 outgoing buffer IF your "escape out" ('~~') does not work.
2221 At this point using either 'ao-view' (or possibly
2222 'cutemon') instead of 'cu' will 'clear' the issue and allow renewed
2226 The amber LED (on the TeleMetrum) lights up when both
2227 battery and USB are connected. Does this mean it's charging?
2228 Yes, the yellow LED indicates the charging at the 'regular' rate.
2229 If the led is out but the unit is still plugged into a USB port,
2230 then the battery is being charged at a 'trickle' rate.
2233 There are no "dit-dah-dah-dit" sound or lights like the manual mentions?
2234 That's the "pad" mode. Weak batteries might be the problem.
2235 It is also possible that the TeleMetrum is horizontal and the output
2236 is instead a "dit-dit" meaning 'idle'. For TeleMini, it's possible that
2237 it received a command packet which would have left it in "pad" mode.
2240 How do I save flight data?
2241 Live telemetry is written to file(s) whenever AltosUI is connected
2242 to the TeleDongle. The file area defaults to ~/TeleMetrum
2243 but is easily changed using the menus in AltosUI. The files that
2244 are written end in '.telem'. The after-flight
2245 data-dumped files will end in .eeprom and represent continuous data
2246 unlike the .telem files that are subject to losses
2247 along the RF data path.
2248 See the above instructions on what and how to save the eeprom stored
2249 data after physically retrieving your altimeter. Make sure to save
2250 the on-board data after each flight; while the TeleMetrum can store
2251 multiple flights, you never know when you'll lose the altimeter...
2255 <title>Notes for Older Software</title>
2258 Before AltosUI was written, using Altus Metrum devices required
2259 some finesse with the Linux command line. There was a limited
2260 GUI tool, ao-view, which provided functionality similar to the
2261 Monitor Flight window in AltosUI, but everything else was a
2262 fairly 80's experience. This appendix includes documentation for
2263 using that software.
2267 Both TeleMetrum and TeleDongle can be directly communicated
2268 with using USB ports. The first thing you should try after getting
2269 both units plugged into to your computer's USB port(s) is to run
2270 'ao-list' from a terminal-window to see what port-device-name each
2271 device has been assigned by the operating system.
2272 You will need this information to access the devices via their
2273 respective on-board firmware and data using other command line
2274 programs in the AltOS software suite.
2277 TeleMini can be communicated with through a TeleDongle device
2278 over the radio link. When first booted, TeleMini listens for a
2279 TeleDongle device and if it receives a packet, it goes into
2280 'idle' mode. Otherwise, it goes into 'pad' mode and waits to be
2281 launched. The easiest way to get it talking is to start the
2282 communication link on the TeleDongle and the power up the
2286 To access the device's firmware for configuration you need a terminal
2287 program such as you would use to talk to a modem. The software
2288 authors prefer using the program 'cu' which comes from the UUCP package
2289 on most Unix-like systems such as Linux. An example command line for
2290 cu might be 'cu -l /dev/ttyACM0', substituting the correct number
2291 indicated from running the
2292 ao-list program. Another reasonable terminal program for Linux is
2293 'cutecom'. The default 'escape'
2294 character used by CU (i.e. the character you use to
2295 issue commands to cu itself instead of sending the command as input
2296 to the connected device) is a '~'. You will need this for use in
2297 only two different ways during normal operations. First is to exit
2298 the program by sending a '~.' which is called a 'escape-disconnect'
2299 and allows you to close-out from 'cu'. The
2300 second use will be outlined later.
2303 All of the Altus Metrum devices share the concept of a two level
2304 command set in their firmware.
2305 The first layer has several single letter commands. Once
2306 you are using 'cu' (or 'cutecom') sending (typing) a '?'
2307 returns a full list of these
2308 commands. The second level are configuration sub-commands accessed
2309 using the 'c' command, for
2310 instance typing 'c?' will give you this second level of commands
2311 (all of which require the
2312 letter 'c' to access). Please note that most configuration options
2313 are stored only in Flash memory; TeleDongle doesn't provide any storage
2314 for these options and so they'll all be lost when you unplug it.
2317 Try setting these configuration ('c' or second level menu) values. A good
2318 place to start is by setting your call sign. By default, the boards
2319 use 'N0CALL' which is cute, but not exactly legal!
2320 Spend a few minutes getting comfortable with the units, their
2321 firmware, and 'cu' (or possibly 'cutecom').
2322 For instance, try to send
2323 (type) a 'c r 2' and verify the channel change by sending a 'c s'.
2324 Verify you can connect and disconnect from the units while in your
2325 terminal program by sending the escape-disconnect mentioned above.
2328 To set the radio frequency, use the 'c R' command to specify the
2329 radio transceiver configuration parameter. This parameter is computed
2330 using the desired frequency, 'F', the radio calibration parameter, 'C' (showed by the 'c s' command) and
2331 the standard calibration reference frequency, 'S', (normally 434.550MHz):
2335 Round the result to the nearest integer value.
2336 As with all 'c' sub-commands, follow this with a 'c w' to write the
2337 change to the parameter block in the on-board flash on
2338 your altimeter board if you want the change to stay in place across reboots.
2341 To set the apogee delay, use the 'c d' command.
2342 As with all 'c' sub-commands, follow this with a 'c w' to write the
2343 change to the parameter block in the on-board DataFlash chip.
2346 To set the main deployment altitude, use the 'c m' command.
2347 As with all 'c' sub-commands, follow this with a 'c w' to write the
2348 change to the parameter block in the on-board DataFlash chip.
2351 To calibrate the radio frequency, connect the UHF antenna port to a
2352 frequency counter, set the board to 434.550MHz, and use the 'C'
2353 command to generate a CW carrier. Wait for the transmitter temperature
2354 to stabilize and the frequency to settle down.
2355 Then, divide 434.550 MHz by the
2356 measured frequency and multiply by the current radio cal value show
2357 in the 'c s' command. For an unprogrammed board, the default value
2358 is 1186611. Take the resulting integer and program it using the 'c f'
2359 command. Testing with the 'C' command again should show a carrier
2360 within a few tens of Hertz of the intended frequency.
2361 As with all 'c' sub-commands, follow this with a 'c w' to write the
2362 change to the parameter block in the on-board DataFlash chip.
2365 Note that the 'reboot' command, which is very useful on the altimeters,
2366 will likely just cause problems with the dongle. The *correct* way
2367 to reset the dongle is just to unplug and re-plug it.
2370 A fun thing to do at the launch site and something you can do while
2371 learning how to use these units is to play with the radio link access
2372 between an altimeter and the TeleDongle. Be aware that you *must* create
2373 some physical separation between the devices, otherwise the link will
2374 not function due to signal overload in the receivers in each device.
2377 Now might be a good time to take a break and read the rest of this
2378 manual, particularly about the two "modes" that the altimeters
2379 can be placed in. TeleMetrum uses the position of the device when booting
2380 up will determine whether the unit is in "pad" or "idle" mode. TeleMini
2381 enters "idle" mode when it receives a command packet within the first 5 seconds
2382 of being powered up, otherwise it enters "pad" mode.
2385 You can access an altimeter in idle mode from the TeleDongle's USB
2386 connection using the radio link
2387 by issuing a 'p' command to the TeleDongle. Practice connecting and
2388 disconnecting ('~~' while using 'cu') from the altimeter. If
2389 you cannot escape out of the "p" command, (by using a '~~' when in
2390 CU) then it is likely that your kernel has issues. Try a newer version.
2393 Using this radio link allows you to configure the altimeter, test
2394 fire e-matches and igniters from the flight line, check pyro-match
2395 continuity and so forth. You can leave the unit turned on while it
2396 is in 'idle mode' and then place the
2397 rocket vertically on the launch pad, walk away and then issue a
2398 reboot command. The altimeter will reboot and start sending data
2399 having changed to the "pad" mode. If the TeleDongle is not receiving
2400 this data, you can disconnect 'cu' from the TeleDongle using the
2401 procedures mentioned above and THEN connect to the TeleDongle from
2402 inside 'ao-view'. If this doesn't work, disconnect from the
2403 TeleDongle, unplug it, and try again after plugging it back in.
2406 In order to reduce the chance of accidental firing of pyrotechnic
2407 charges, the command to fire a charge is intentionally somewhat
2408 difficult to type, and the built-in help is slightly cryptic to
2409 prevent accidental echoing of characters from the help text back at
2410 the board from firing a charge. The command to fire the apogee
2411 drogue charge is 'i DoIt drogue' and the command to fire the main
2412 charge is 'i DoIt main'.
2415 On TeleMetrum, the GPS will eventually find enough satellites, lock in on them,
2416 and 'ao-view' will both auditorily announce and visually indicate
2418 Now you can launch knowing that you have a good data path and
2419 good satellite lock for flight data and recovery. Remember
2420 you MUST tell ao-view to connect to the TeleDongle explicitly in
2421 order for ao-view to be able to receive data.
2424 The altimeters provide RDF (radio direction finding) tones on
2425 the pad, during descent and after landing. These can be used to
2426 locate the rocket using a directional antenna; the signal
2427 strength providing an indication of the direction from receiver to rocket.
2430 TeleMetrum also provides GPS tracking data, which can further simplify
2431 locating the rocket once it has landed. (The last good GPS data
2432 received before touch-down will be on the data screen of 'ao-view'.)
2435 Once you have recovered the rocket you can download the eeprom
2436 contents using either 'ao-dumplog' (or possibly 'ao-eeprom'), over
2437 either a USB cable or over the radio link using TeleDongle.
2438 And by following the man page for 'ao-postflight' you can create
2439 various data output reports, graphs, and even KML data to see the
2440 flight trajectory in Google-earth. (Moving the viewing angle making
2441 sure to connect the yellow lines while in Google-earth is the proper
2445 As for ao-view.... some things are in the menu but don't do anything
2446 very useful. The developers have stopped working on ao-view to focus
2447 on a new, cross-platform ground station program. So ao-view may or
2448 may not be updated in the future. Mostly you just use
2449 the Log and Device menus. It has a wonderful display of the incoming
2450 flight data and I am sure you will enjoy what it has to say to you
2451 once you enable the voice output!
2455 <title>Calibration</title>
2457 There are only two calibrations required for a TeleMetrum board, and
2458 only one for TeleDongle and TeleMini. All boards are shipped from
2459 the factory pre-calibrated, but the procedures are documented here
2460 in case they are ever needed. Re-calibration is not supported by
2461 AltosUI, you must connect to the board with a serial terminal program
2462 and interact directly with the on-board command interpreter to effect
2466 <title>Radio Frequency</title>
2468 The radio frequency is synthesized from a clock based on the 48 MHz
2469 crystal on the board. The actual frequency of this oscillator
2470 must be measured to generate a calibration constant. While our
2472 bandwidth is wide enough to allow boards to communicate even when
2473 their oscillators are not on exactly the same frequency, performance
2474 is best when they are closely matched.
2475 Radio frequency calibration requires a calibrated frequency counter.
2476 Fortunately, once set, the variation in frequency due to aging and
2477 temperature changes is small enough that re-calibration by customers
2478 should generally not be required.
2481 To calibrate the radio frequency, connect the UHF antenna port to a
2482 frequency counter, set the board to 434.550MHz, and use the 'C'
2483 command in the on-board command interpreter to generate a CW
2484 carrier. For TeleMetrum, this is best done over USB. For TeleMini,
2485 note that the only way to escape the 'C' command is via power cycle
2486 since the board will no longer be listening for commands once it
2487 starts generating a CW carrier.
2490 Wait for the transmitter temperature to stabilize and the frequency
2491 to settle down. Then, divide 434.550 MHz by the
2492 measured frequency and multiply by the current radio cal value show
2493 in the 'c s' command. For an unprogrammed board, the default value
2494 is 1186611. Take the resulting integer and program it using the 'c f'
2495 command. Testing with the 'C' command again should show a carrier
2496 within a few tens of Hertz of the intended frequency.
2497 As with all 'c' sub-commands, follow this with a 'c w' to write the
2498 change to the parameter block in the on-board DataFlash chip.
2501 Note that any time you re-do the radio frequency calibration, the
2502 radio frequency is reset to the default 434.550 Mhz. If you want
2503 to use another frequency, you will have to set that again after
2504 calibration is completed.
2508 <title>TeleMetrum Accelerometer</title>
2510 The TeleMetrum accelerometer we use has its own 5 volt power
2512 the output must be passed through a resistive voltage divider to match
2513 the input of our 3.3 volt ADC. This means that unlike the barometric
2514 sensor, the output of the acceleration sensor is not ratio-metric to
2515 the ADC converter, and calibration is required. Explicitly
2516 calibrating the accelerometers also allows us to load any device
2517 from a Freescale family that includes at least +/- 40g, 50g, 100g,
2518 and 200g parts. Using gravity,
2519 a simple 2-point calibration yields acceptable results capturing both
2520 the different sensitivities and ranges of the different accelerometer
2521 parts and any variation in power supply voltages or resistor values
2522 in the divider network.
2525 To calibrate the acceleration sensor, use the 'c a 0' command. You
2526 will be prompted to orient the board vertically with the UHF antenna
2527 up and press a key, then to orient the board vertically with the
2528 UHF antenna down and press a key. Note that the accuracy of this
2529 calibration depends primarily on how perfectly vertical and still
2530 the board is held during the cal process. As with all 'c'
2531 sub-commands, follow this with a 'c w' to write the
2532 change to the parameter block in the on-board DataFlash chip.
2535 The +1g and -1g calibration points are included in each telemetry
2536 frame and are part of the header stored in onboard flash to be
2537 downloaded after flight. We always store and return raw ADC
2538 samples for each sensor... so nothing is permanently "lost" or
2539 "damaged" if the calibration is poor.
2542 In the unlikely event an accel cal goes badly, it is possible
2543 that TeleMetrum may always come up in 'pad mode' and as such not be
2544 listening to either the USB or radio link. If that happens,
2545 there is a special hook in the firmware to force the board back
2546 in to 'idle mode' so you can re-do the cal. To use this hook, you
2547 just need to ground the SPI clock pin at power-on. This pin is
2548 available as pin 2 on the 8-pin companion connector, and pin 1 is
2549 ground. So either carefully install a fine-gauge wire jumper
2550 between the two pins closest to the index hole end of the 8-pin
2551 connector, or plug in the programming cable to the 8-pin connector
2552 and use a small screwdriver or similar to short the two pins closest
2553 to the index post on the 4-pin end of the programming cable, and
2554 power up the board. It should come up in 'idle mode' (two beeps),
2560 xmlns:xi="http://www.w3.org/2001/XInclude">
2561 <title>Release Notes</title>
2562 <xi:include href="release-notes-1.1.xsl" xpointer="xpointer(/article/*)"/>
2563 <xi:include href="release-notes-1.0.1.xsl" xpointer="xpointer(/article/*)"/>
2564 <xi:include href="release-notes-0.9.2.xsl" xpointer="xpointer(/article/*)"/>
2565 <xi:include href="release-notes-0.9.xsl" xpointer="xpointer(/article/*)"/>
2566 <xi:include href="release-notes-0.8.xsl" xpointer="xpointer(/article/*)"/>
2567 <xi:include href="release-notes-0.7.1.xsl" xpointer="xpointer(/article/*)"/>
2571 <!-- LocalWords: Altusmetrum
projects / fw / altos / blob