X-Git-Url: https://git.gag.com/?p=fw%2Faltos;a=blobdiff_plain;f=doc%2Faltusmetrum.xsl;h=ee809f081f971d15bac1af75b77b046087f45979;hp=5375e8c29462065bc775a141101b7856ac750ded;hb=8da565bbafa2925aa889cf9249497a709a814b7f;hpb=9953a5f0440b269dac5c675f120e6a31dde8ec69 diff --git a/doc/altusmetrum.xsl b/doc/altusmetrum.xsl index 5375e8c2..ee809f08 100644 --- a/doc/altusmetrum.xsl +++ b/doc/altusmetrum.xsl @@ -3,7 +3,7 @@ "/usr/share/xml/docbook/schema/dtd/4.5/docbookx.dtd"> The Altus Metrum System - An Owner's Manual for TeleMetrum, TeleMini, TeleDongle and TeleBT Devices + An Owner's Manual for Altus Metrum Rocketry Electronics Bdale @@ -106,9 +106,9 @@ Acknowledgements - Thanks to Bob Finch, W9YA, NAR 12965, TRA 12350 for writing "The + Thanks to Bob Finch, W9YA, NAR 12965, TRA 12350 for writing “The Mere-Mortals Quick Start/Usage Guide to the Altus Metrum Starter - Kit" which formed the basis of the original Getting Started chapter + Kit” which formed the basis of the original Getting Started chapter in this manual. Bob was one of our first customers for a production TeleMetrum, and his continued enthusiasm and contributions are immensely gratifying and highly appreciated! @@ -145,7 +145,7 @@ NAR #88757, TRA #12200 The first device created for our community was TeleMetrum, a dual deploy altimeter with fully integrated GPS and radio telemetry - as standard features, and a "companion interface" that will + as standard features, and a “companion interface” that will support optional capabilities in the future. The latest version of TeleMetrum, v2.0, has all of the same features but with improved sensors and radio to offer increased performance. @@ -194,7 +194,7 @@ NAR #88757, TRA #12200 Getting Started The first thing to do after you check the inventory of parts in your - "starter kit" is to charge the battery. + “starter kit” is to charge the battery. For TeleMetrum and TeleMega, the battery can be charged by plugging it into the @@ -243,7 +243,7 @@ NAR #88757, TRA #12200 The other active device in the starter kit is the TeleDongle USB to RF interface. If you plug it in to your Mac or Linux computer it should - "just work", showing up as a serial port device. Windows systems need + “just work”, showing up as a serial port device. Windows systems need driver information that is part of the AltOS download to know that the existing USB modem driver will work. We therefore recommend installing our software before plugging in TeleDongle if you are using a Windows @@ -296,19 +296,19 @@ NAR #88757, TRA #12200 The barometric sensors used on all of our flight computers are sensitive to sunlight. In normal mounting situations, the baro sensor and all of the other surface mount components - are "down" towards whatever the underlying mounting surface is, so + are “down” towards whatever the underlying mounting surface is, so this is not normally a problem. Please consider this, though, when designing an installation, for example, in an air-frame with a see-through plastic payload bay. It is particularly important to consider this with TeleMini v1.0, both because the baro sensor is on the - "top" of the board, and because many model rockets with payload bays + “top” of the board, and because many model rockets with payload bays use clear plastic for the payload bay! Replacing these with an opaque cardboard tube, painting them, or wrapping them with a layer of masking tape are all reasonable approaches to keep the sensor out of direct sunlight. - The barometric sensor sampling port must be able to "breathe", + The barometric sensor sampling port must be able to “breathe”, both by not being covered by foam or tape or other materials that might directly block the hole on the top of the sensor, and also by having a suitable static vent to outside air. @@ -320,102 +320,454 @@ NAR #88757, TRA #12200 - Hardware Overview - - TeleMetrum is a 1 inch by 2¾ inch circuit board. It was designed to - fit inside coupler for 29mm air-frame tubing, but using it in a tube that - small in diameter may require some creativity in mounting and wiring - to succeed! The presence of an accelerometer means TeleMetrum should - be aligned along the flight axis of the airframe, and by default the 1/4 - wave UHF wire antenna should be on the nose-cone end of the board. The - antenna wire is about 7 inches long, and wiring for a power switch and - the e-matches for apogee and main ejection charges depart from the - fin can end of the board, meaning an ideal "simple" avionics - bay for TeleMetrum should have at least 10 inches of interior length. - - - TeleMini v1.0 is a ½ inch by 1½ inch circuit board. It was designed to - fit inside an 18mm air-frame tube, but using it in a tube that - small in diameter may require some creativity in mounting and wiring - to succeed! Since there is no accelerometer, TeleMini can be mounted - in any convenient orientation. The default ¼ - wave UHF wire antenna attached to the center of one end of - the board is about 7 inches long, and wiring for a power switch and - the e-matches for apogee and main ejection charges depart from the - other end of the board, meaning an ideal "simple" avionics - bay for TeleMini should have at least 9 inches of interior length. - - - TeleMini v2.0 and EasyMini are both built on a 0.8 inch by 1½ - inch circuit board. They're designed to fit in a 24mm coupler - tube. TeleMini has an antenna, which must be run straight out - fro the board. Bending or folding it will dramatically reduce RF - performance. For smaller rockets, it's often best to drill a - hole in the bulkhead forward of TeleMini and run the antenna - wire through that and alongside any recovery components - there. Be careful to seal the hole to prevent ejection gasses - from passing through the hole and damaging the electronics. - - - TeleMega is a 1¼ inch by 3¼ inch circuit board. It was - designed to easily fit in a 38mm coupler. Like TeleMetrum, - TeleMega has an accelerometer and so it must be mounted so that - the board is aligned with the flight axis. It can be mounted - either antenna up or down. - - - A typical installation involves attaching - only a suitable battery, a single pole switch for - power on/off, and two pairs of wires connecting e-matches for the - apogee and main ejection charges. All Altus Metrum products are - designed for use with single-cell batteries with 3.7 volts - nominal. TeleMini v2.0 and EasyMini may also be used with other - batteries as long as they supply between 4 and 12 volts. - - - The battery connectors are a standard 2-pin JST connector and - match batteries sold by Spark Fun. These batteries are - single-cell Lithium Polymer batteries that nominally provide 3.7 - volts. Other vendors sell similar batteries for RC aircraft - using mating connectors, however the polarity for those is - generally reversed from the batteries used by Altus Metrum - products. In particular, the Tenergy batteries supplied for use - in Featherweight flight computers are not compatible with Altus - Metrum flight computers or battery chargers. Check - polarity and voltage before connecting any battery not purchased - from Altus Metrum or Spark Fun. - - - By default, we use the unregulated output of the battery directly - to fire ejection charges. This works marvelously with standard - low-current e-matches like the J-Tek from MJG Technologies, and with - Quest Q2G2 igniters. However, if you want or need to use a separate - pyro battery, check out the "External Pyro Battery" section in this - manual for instructions on how to wire that up. The altimeters are - designed to work with an external pyro battery of no more than 15 volts. - - - Ejection charges are wired directly to the screw terminal block - at the aft end of the altimeter. You'll need a very small straight - blade screwdriver for these screws, such as you might find in a - jeweler's screwdriver set. - - - Except for TeleMini v1.0, the flight computers also use the - screw terminal block for the power switch leads. On TeleMini v1.0, - the power switch leads are soldered directly to the board and - can be connected directly to a switch. - - - For most air-frames, the integrated antennas are more than - adequate. However, if you are installing in a carbon-fiber or - metal electronics bay which is opaque to RF signals, you may need to - use off-board external antennas instead. In this case, you can - order an altimeter with an SMA connector for the UHF antenna - connection, and, on TeleMetrum v1, you can unplug the integrated GPS - antenna and select an appropriate off-board GPS antenna with - cable terminating in a U.FL connector. - + Altus Metrum Hardware +
+ Overview + + Here's the full set of Altus Metrum products, both in + production and retired. + + + Altus Metrum Electronics + + + + + + + + + + + + Device + Barometer + Z-axis accelerometer + GPS + 3D sensors + Storage + RF Output + Battery + + + + + TeleMetrum v1.0 + MP3H6115 10km (33k') + MMA2202 50g + SkyTraq + - + 1MB + 10mW + 3.7V + + + TeleMetrum v1.1 + MP3H6115 10km (33k') + MMA2202 50g + SkyTraq + - + 2MB + 10mW + 3.7V + + + TeleMetrum v1.2 + MP3H6115 10km (33k') + ADXL78 70g + SkyTraq + - + 2MB + 10mW + 3.7V + + + TeleMetrum v2.0 + MS5607 30km (100k') + MMA6555 102g + uBlox Max-7Q + - + 8MB + 40mW + 3.7V + + + TeleMini v1.0 + MP3H6115 10km (33k') + - + - + - + 5kB + 10mW + 3.7V + + + TeleMini v2.0 + MS5607 30km (100k') + - + - + - + 1MB + 10mW + 3.7-12V + + + EasyMini v1.0 + MS5607 30km (100k') + - + - + - + 1MB + - + 3.7-12V + + + TeleMega v1.0 + MS5607 30km (100k') + MMA6555 102g + uBlox Max-7Q + MPU6000 HMC5883 + 8MB + 40mW + 3.7V + + + +
+ + Altus Metrum Boards + + + + + + + + + + Device + Connectors + Screw Terminals + Width + Length + Tube Size + + + + + TeleMetrum + + Antenna + Debug + Companion + USB + Battery + + Apogee pyro Main pyro Switch + 1 inch (2.54cm) + 2 ¾ inch (6.99cm) + 29mm coupler + + + TeleMini v1.0 + + Antenna + Debug + Battery + + + Apogee pyro + Main pyro + + ½ inch (1.27cm) + 1½ inch (3.81cm) + 18mm aiframe + + + TeleMini v2.0 + + Antenna + Debug + USB + Battery + + + Apogee pyro + Main pyro + Battery + Switch + + 0.8 inch (2.03cm) + 1½ inch (3.81cm) + 24mm coupler + + + EasyMini + + Debug + USB + Battery + + + Apogee pyro + Main pyro + Battery + Switch + + 0.8 inch (2.03cm) + 1½ inch (3.81cm) + 24mm coupler + + + TeleMega + + Antenna + Debug + Companion + USB + Battery + + + Apogee pyro + Main pyro + Pyro A-D + Switch + Pyro battery + + 1¼ inch (3.18cm) + 3¼ inch (8.26cm) + 38mm coupler + + + +
+
+
+ TeleMetrum + + TeleMetrum is a 1 inch by 2¾ inch circuit board. It was designed to + fit inside coupler for 29mm air-frame tubing, but using it in a tube that + small in diameter may require some creativity in mounting and wiring + to succeed! The presence of an accelerometer means TeleMetrum should + be aligned along the flight axis of the airframe, and by default the ¼ + wave UHF wire antenna should be on the nose-cone end of the board. The + antenna wire is about 7 inches long, and wiring for a power switch and + the e-matches for apogee and main ejection charges depart from the + fin can end of the board, meaning an ideal “simple” avionics + bay for TeleMetrum should have at least 10 inches of interior length. + +
+
+ TeleMini + + TeleMini v1.0 is ½ inches by 1½ inches. It was + designed to fit inside an 18mm air-frame tube, but using it in + a tube that small in diameter may require some creativity in + mounting and wiring to succeed! Since there is no + accelerometer, TeleMini can be mounted in any convenient + orientation. The default ¼ wave UHF wire antenna attached to + the center of one end of the board is about 7 inches long. Two + wires for the power switch are connected to holes in the + middle of the board. Screw terminals for the e-matches for + apogee and main ejection charges depart from the other end of + the board, meaning an ideal “simple” avionics bay for TeleMini + should have at least 9 inches of interior length. + + + TeleMini v2.0 is 0.8 inches by 1½ inches. It adds more + on-board data logging memory, a built-in USB connector and + screw terminals for the battery and power switch. The larger + board fits in a 24mm coupler. There's also a battery connector + for a LiPo battery if you want to use one of those. + +
+
+ EasyMini + + EasyMini is built on a 0.8 inch by 1½ inch circuit board. It's + designed to fit in a 24mm coupler tube. The connectors and + screw terminals match TeleMini, so you can swap an EasyMini + with a TeleMini. + +
+
+ TeleMega + + TeleMega is a 1¼ inch by 3¼ inch circuit board. It was + designed to easily fit in a 38mm coupler. Like TeleMetrum, + TeleMega has an accelerometer and so it must be mounted so that + the board is aligned with the flight axis. It can be mounted + either antenna up or down. + +
+
+ Flight Data Recording + + Each flight computer logs data at 100 samples per second + during ascent and 10 samples per second during descent, except + for TeleMini v1.0, which records ascent at 10 samples per + second and descent at 1 sample per second. Data are logged to + an on-board flash memory part, which can be partitioned into + several equal-sized blocks, one for each flight. + + + Data Storage on Altus Metrum altimeters + + + + + + + + Device + Bytes per Sample + Total Storage + Minutes at Full Rate + + + + + TeleMetrum v1.0 + 8 + 1MB + 20 + + + TeleMetrum v1.1 v1.2 + 8 + 2MB + 40 + + + TeleMetrum v2.0 + 16 + 8MB + 80 + + + TeleMini v1.0 + 2 + 5kB + 4 + + + TeleMini v2.0 + 16 + 1MB + 10 + + + EasyMini + 16 + 1MB + 10 + + + TeleMega + 32 + 8MB + 40 + + + +
+ + The on-board flash is partitioned into separate flight logs, + each of a fixed maximum size. Increase the maximum size of + each log and you reduce the number of flights that can be + stored. Decrease the size and you can store more flights. + + + Configuration data is also stored in the flash memory on + TeleMetrum v1.x, TeleMini and EasyMini. This consumes 64kB + of flash space. This configuration space is not available + for storing flight log data. TeleMetrum v2.0 and TeleMega + store configuration data in a bit of eeprom available within + the processor chip, leaving that space available in flash for + more flight data. + + + To compute the amount of space needed for a single flight, you + can multiply the expected ascent time (in seconds) by 100 + times bytes-per-sample, multiply the expected descent time (in + seconds) by 10 times the bytes per sample and add the two + together. That will slightly under-estimate the storage (in + bytes) needed for the flight. For instance, a TeleMetrum v2.0 flight spending + 20 seconds in ascent and 150 seconds in descent will take + about (20 * 1600) + (150 * 160) = 56000 bytes of storage. You + could store dozens of these flights in the on-board flash. + + + The default size allows for several flights on each flight + computer, except for TeleMini v1.0, which only holds data for a + single flight. You can adjust the size. + + + Altus Metrum flight computers will not overwrite existing + flight data, so be sure to download flight data and erase it + from the flight computer before it fills up. The flight + computer will still successfully control the flight even if it + cannot log data, so the only thing you will lose is the data. + +
+
+ Installation + + A typical installation involves attaching + only a suitable battery, a single pole switch for + power on/off, and two pairs of wires connecting e-matches for the + apogee and main ejection charges. All Altus Metrum products are + designed for use with single-cell batteries with 3.7 volts + nominal. TeleMini v2.0 and EasyMini may also be used with other + batteries as long as they supply between 4 and 12 volts. + + + The battery connectors are a standard 2-pin JST connector and + match batteries sold by Spark Fun. These batteries are + single-cell Lithium Polymer batteries that nominally provide 3.7 + volts. Other vendors sell similar batteries for RC aircraft + using mating connectors, however the polarity for those is + generally reversed from the batteries used by Altus Metrum + products. In particular, the Tenergy batteries supplied for use + in Featherweight flight computers are not compatible with Altus + Metrum flight computers or battery chargers. Check + polarity and voltage before connecting any battery not purchased + from Altus Metrum or Spark Fun. + + + By default, we use the unregulated output of the battery directly + to fire ejection charges. This works marvelously with standard + low-current e-matches like the J-Tek from MJG Technologies, and with + Quest Q2G2 igniters. However, if you want or need to use a separate + pyro battery, check out the “External Pyro Battery” section in this + manual for instructions on how to wire that up. The altimeters are + designed to work with an external pyro battery of no more than 15 volts. + + + + Ejection charges are wired directly to the screw terminal block + at the aft end of the altimeter. You'll need a very small straight + blade screwdriver for these screws, such as you might find in a + jeweler's screwdriver set. + + + Except for TeleMini v1.0, the flight computers also use the + screw terminal block for the power switch leads. On TeleMini v1.0, + the power switch leads are soldered directly to the board and + can be connected directly to a switch. + + + For most air-frames, the integrated antennas are more than + adequate. However, if you are installing in a carbon-fiber or + metal electronics bay which is opaque to RF signals, you may need to + use off-board external antennas instead. In this case, you can + order an altimeter with an SMA connector for the UHF antenna + connection, and, on TeleMetrum v1, you can unplug the integrated GPS + antenna and select an appropriate off-board GPS antenna with + cable terminating in a U.FL connector. + +
System Operation @@ -423,45 +775,45 @@ NAR #88757, TRA #12200 Firmware Modes The AltOS firmware build for the altimeters has two - fundamental modes, "idle" and "flight". Which of these modes + fundamental modes, “idle” and “flight”. Which of these modes the firmware operates in is determined at start up time. For TeleMetrum, the mode is controlled by the orientation of the rocket (well, actually the board, of course...) at the time - power is switched on. If the rocket is "nose up", then + power is switched on. If the rocket is “nose up”, then TeleMetrum assumes it's on a rail or rod being prepared for launch, so the firmware chooses flight mode. However, if the rocket is more or less horizontal, the firmware instead enters idle mode. Since TeleMini v2.0 and EasyMini don't have an - accelerometer we can use to determine orientation, "idle" mode + accelerometer we can use to determine orientation, “idle” mode is selected if the board is connected via USB to a computer, - otherwise the board enters "flight" mode. TeleMini v1.0 - selects "idle" mode if it receives a command packet within the + otherwise the board enters “flight” mode. TeleMini v1.0 + selects “idle” mode if it receives a command packet within the first five seconds of operation. At power on, you will hear three beeps or see three flashes - ("S" in Morse code for start up) and then a pause while + (“S” in Morse code for start up) and then a pause while the altimeter completes initialization and self test, and decides which mode to enter next. - In flight or "pad" mode, the altimeter engages the flight + In flight or “pad” mode, the altimeter engages the flight state machine, goes into transmit-only mode to send telemetry, and waits for launch to be detected. - Flight mode is indicated by an "di-dah-dah-dit" ("P" for pad) + Flight mode is indicated by an “di-dah-dah-dit” (“P” for pad) on the beeper or lights, followed by beeps or flashes indicating the state of the pyrotechnic igniter continuity. One beep/flash indicates apogee continuity, two beeps/flashes indicate main continuity, three beeps/flashes indicate both - apogee and main continuity, and one longer "brap" sound or + apogee and main continuity, and one longer “brap” sound or rapidly alternating lights indicates no continuity. For a dual deploy flight, make sure you're getting three beeps or flashes before launching! For apogee-only or motor eject flights, do what makes sense. - If idle mode is entered, you will hear an audible "di-dit" or - see two short flashes ("I" for idle), and the flight state + If idle mode is entered, you will hear an audible “di-dit” or + see two short flashes (“I” for idle), and the flight state machine is disengaged, thus no ejection charges will fire. The altimeters also listen for the radio link when in idle mode for requests sent via TeleDongle. Commands can be issued @@ -472,7 +824,7 @@ NAR #88757, TRA #12200 ground testing pyro charges. - One "neat trick" of particular value when TeleMetrum or TeleMega are used with + One “neat trick” of particular value when TeleMetrum or TeleMega are used with very large air-frames, is that you can power the board up while the rocket is horizontal, such that it comes up in idle mode. Then you can raise the air-frame to launch position, and issue a 'reset' command @@ -532,9 +884,9 @@ NAR #88757, TRA #12200 The flight computers provide backup power to the GPS chip any time a - battery is connected. This allows the receiver to "warm start" on + battery is connected. This allows the receiver to “warm start” on the launch rail much faster than if every power-on were a GPS - "cold start". In typical operations, powering up + “cold start”. In typical operations, powering up on the flight line in idle mode while performing final air-frame preparation will be sufficient to allow the GPS receiver to cold start and acquire lock. Then the board can be powered down during @@ -588,7 +940,7 @@ NAR #88757, TRA #12200 and additional pyro event conditions to respond to changing launch conditions. You can also 'reboot' the altimeter. Use this to remotely enable the - flight computer by turning TeleMetrum or TeleMega on in "idle" mode, + flight computer by turning TeleMetrum or TeleMega on in “idle” mode, then once the air-frame is oriented for launch, you can reboot the altimeter and have it restart in pad mode without having to climb the scary ladder. @@ -648,9 +1000,9 @@ NAR #88757, TRA #12200 Just prep the rocket for flight, then power up the altimeter - in "idle" mode (placing air-frame horizontal for TeleMetrum or TeleMega, or + in “idle” mode (placing air-frame horizontal for TeleMetrum or TeleMega, or selecting the Configure Altimeter tab for TeleMini). This will cause - the firmware to go into "idle" mode, in which the normal flight + the firmware to go into “idle” mode, in which the normal flight state machine is disabled and charges will not fire without manual command. You can now command the altimeter to fire the apogee or main charges from a safe distance using your computer and @@ -667,11 +1019,11 @@ NAR #88757, TRA #12200 By design, the altimeter firmware listens for the radio link when - it's in "idle mode", which + it's in “idle mode”, which allows us to use the radio link to configure the rocket, do things like ejection tests, and extract data after a flight without having to - crack open the air-frame. However, when the board is in "flight - mode", the altimeter only + crack open the air-frame. However, when the board is in “flight + mode”, the altimeter only transmits and doesn't listen at all. That's because we want to put ultimate priority on event detection and getting telemetry out of the rocket through @@ -679,25 +1031,28 @@ NAR #88757, TRA #12200 data later... - We don't generally use a 'normal packet radio' mode like APRS because they're - just too inefficient. The GFSK modulation we use is FSK with the - base-band pulses passed through a - Gaussian filter before they go into the modulator to limit the - transmitted bandwidth. When combined with the hardware forward error - correction support in the cc1111 chip, this allows us to have a very - robust 38.4 kilobit data link with only 10 milliwatts of transmit - power, a whip antenna in the rocket, and a hand-held Yagi on the - ground. We've had flights to above 21k feet AGL with great reception, - and calculations suggest we should be good to well over 40k feet AGL - with a 5-element yagi on the ground. We hope to fly boards to higher - altitudes over time, and would of course appreciate customer feedback - on performance in higher altitude flights! - - - However, TeleMetrum v2.0 and TeleMega can send APRS if - desired, the interval between APRS packets can be - configured. As each APRS packet takes a full second to - transmit, we recommend an interval of at least 5 seconds. + We don't generally use a 'normal packet radio' mode like APRS + because they're just too inefficient. The GFSK modulation we + use is FSK with the base-band pulses passed through a Gaussian + filter before they go into the modulator to limit the + transmitted bandwidth. When combined with forward error + correction and interleaving, this allows us to have a very + robust 19.2 kilobit data link with only 10-40 milliwatts of + transmit power, a whip antenna in the rocket, and a hand-held + Yagi on the ground. We've had flights to above 21k feet AGL + with great reception, and calculations suggest we should be + good to well over 40k feet AGL with a 5-element yagi on the + ground with our 10mW units and over 100k feet AGL with the + 40mW devices. We hope to fly boards to higher altitudes over + time, and would of course appreciate customer feedback on + performance in higher altitude flights! + + + TeleMetrum v2.0 and TeleMega can send APRS if desired, the + interval between APRS packets can be configured. As each APRS + packet takes a full second to transmit, we recommend an + interval of at least 5 seconds to avoid consuming too much + battery power or radio channel bandwidth.
@@ -705,7 +1060,7 @@ NAR #88757, TRA #12200 Configuring an Altus Metrum altimeter for flight is very simple. Even on our baro-only TeleMini and EasyMini boards, the use of a Kalman - filter means there is no need to set a "mach delay". The few + filter means there is no need to set a “mach delay”. The few configurable parameters can all be set using AltosUI over USB or or radio link via TeleDongle. @@ -714,7 +1069,7 @@ NAR #88757, TRA #12200 Altus Metrum boards support radio frequencies in the 70cm band. By default, the configuration interface provides a - list of 10 "standard" frequencies in 100kHz channels starting at + list of 10 “standard” frequencies in 100kHz channels starting at 434.550MHz. However, the firmware supports use of any 50kHz multiple within the 70cm band. At any given launch, we highly recommend coordinating when and by whom each @@ -760,57 +1115,13 @@ NAR #88757, TRA #12200
Maximum Flight Log - TeleMetrum version 1.1 and 1.2 have 2MB of on-board flash storage, - enough to hold over 40 minutes of data at full data rate - (100 samples/second). TeleMetrum 1.0 has 1MB of on-board - storage. As data are stored at a reduced rate during descent - (10 samples/second), there's plenty of space to store many - flights worth of data. - - - TeleMetrum v2.0 and TeleMega have 8MB of on-board flash stroage, enough to hold - - - The on-board flash is partitioned into separate flight logs, - each of a fixed maximum size. Increase the maximum size of - each log and you reduce the number of flights that can be - stored. Decrease the size and TeleMetrum can store more - flights. - - - All of the configuration data is also stored in the flash - memory, which consumes 64kB on TeleMetrum v1.1/v1.2 and 256B on - TeleMetrum v1.0. This configuration space is not available - for storing flight log data. - - - To compute the amount of space needed for a single flight, - you can multiply the expected ascent time (in seconds) by - 800, multiply the expected descent time (in seconds) by 80 - and add the two together. That will slightly under-estimate - the storage (in bytes) needed for the flight. For instance, - a flight spending 20 seconds in ascent and 150 seconds in - descent will take about (20 * 800) + (150 * 80) = 28000 - bytes of storage. You could store dozens of these flights in - the on-board flash. - - - The default size, 192kB, allows for 10 flights of storage on - TeleMetrum v1.1/v1.2 and 5 flights on TeleMetrum v1.0. This - ensures that you won't need to erase the memory before - flying each time while still allowing more than sufficient - storage for each flight. - - - As TeleMini does not contain an accelerometer, it stores - data at 10 samples per second during ascent and one sample - per second during descent. Each sample is a two byte reading - from the barometer. These are stored in 5kB of - on-chip flash memory which can hold 256 seconds at the - ascent rate or 2560 seconds at the descent rate. Because of - the limited storage, TeleMini cannot hold data for more than - one flight, and so must be erased after each flight or it - will not capture data for subsequent flights. + Changing this value will set the maximum amount of flight + log storage that an individual flight will use. The + available storage is divided into as many flights of the + specified size as can fit in the available space. You can + download and erase individual flight logs. If you fill up + the available storage, future flights will not get logged + until you erase some of the stored ones.
@@ -820,7 +1131,7 @@ NAR #88757, TRA #12200 a fixed height above the ground, you can configure the altimeter to fire both at apogee or both during descent. This was added to support an airframe that has two - TeleMetrum computers, one in the fin can and one in the + altimeters, one in the fin can and one in the nose. @@ -833,17 +1144,175 @@ NAR #88757, TRA #12200
Pad Orientation - TeleMetrum measures acceleration along the axis of the - board. Which way the board is oriented affects the sign of - the acceleration value. Instead of trying to guess which way - the board is mounted in the air frame, TeleMetrum must be - explicitly configured for either Antenna Up or Antenna - Down. The default, Antenna Up, expects the end of the - TeleMetrum board connected to the 70cm antenna to be nearest - the nose of the rocket, with the end containing the screw + TeleMetrum and TeleMega measure acceleration along the axis + of the board. Which way the board is oriented affects the + sign of the acceleration value. Instead of trying to guess + which way the board is mounted in the air frame, the + altimeter must be explicitly configured for either Antenna + Up or Antenna Down. The default, Antenna Up, expects the end + of the board connected to the 70cm antenna to be nearest the + nose of the rocket, with the end containing the screw terminals nearest the tail.
+
+ Pyro Channels + + In addition to the usual Apogee and Main pyro channels, + TeleMega has four additional channels that can be configured + to activate when various flight conditions are + satisfied. You can select as many conditions as necessary; + all of them must be met in order to activate the + channel. The conditions available are: + + + + + Acceleration away from the ground. Select a value, and + then choose whether acceleration should be above or + below that value. Acceleration is positive upwards, so + accelerating towards the ground would produce negative + numbers. Acceleration during descent is noisy and + inaccurate, so be careful when using it during these + phases of the flight. + + + + + Vertical speed. Select a value, and then choose whether + vertical speed should be above or below that + value. Speed is positive upwards, so moving towards the + ground would produce negative numbers. Speed during + descent is a bit noisy and so be careful when using it + during these phases of the flight. + + + + + Height. Select a value, and then choose whether the + height above the launch pad should be above or below + that value. + + + + + Orientation. TeleMega contains a 3-axis gyroscope and + accelerometer which is used to measure the current + angle. Note that this angle is not the change in angle + from the launch pad, but rather absolute relative to + gravity; the 3-axis accelerometer is used to compute the + angle of the rocket on the launch pad and initialize the + system. Because this value is computed by integrating + rate gyros, it gets progressively less accurate as the + flight goes on. It should have an accumulated error of + less than .2°/second (after 10 seconds of flight, the + error should be less than 2°). + + + The usual use of the orientation configuration is to + ensure that the rocket is traveling mostly upwards when + deciding whether to ignite air starts or additional + stages. For that, choose a reasonable maximum angle + (like 20°) and set the motor igniter to require an angle + of less than that value. + + + + + Flight Time. Time since boost was detected. Select a + value and choose whether to activate the pyro channel + before or after that amount of time. + + + + + Ascending. A simple test saying whether the rocket is + going up or not. This is exactly equivalent to testing + whether the speed is > 0. + + + + + Descending. A simple test saying whether the rocket is + going down or not. This is exactly equivalent to testing + whether the speed is < 0. + + + + + After Motor. The flight software counts each time the + rocket starts accelerating (presumably due to a motor or + motors igniting). Use this value to count ignitions for + multi-staged or multi-airstart launches. + + + + + Delay. This value doesn't perform any checks, instead it + inserts a delay between the time when the other + parameters become true and when the pyro channel is + activated. + + + + + Flight State. The flight software tracks the flight + through a sequence of states: + + + + Boost. The motor has lit and the rocket is + accelerating upwards. + + + + + Fast. The motor has burned out and the rocket is + descellerating, but it is going faster than 200m/s. + + + + + Coast. The rocket is still moving upwards and + decelerating, but the speed is less than 200m/s. + + + + + Drogue. The rocket has reached apogee and is heading + back down, but is above the configured Main + altitude. + + + + + Main. The rocket is still descending, and is blow + the Main altitude + + + + + Landed. The rocket is no longer moving. + + + + + + You can select a state to limit when the pyro channel + may activate; note that the check is based on when the + rocket transitions *into* the state, and so checking for + 'greater than Boost' means that the rocket is currently + in boost state. + + + When a motor burns out, the rocket enters either Fast or + Coast state (depending on how fast it is moving). If the + computer detects upwards acceleration again, it will + move back to Boost state. + + + +
@@ -852,9 +1321,8 @@ NAR #88757, TRA #12200 AltosUI The AltosUI program provides a graphical user interface for - interacting with the Altus Metrum product family, including - TeleMetrum, TeleMini and TeleDongle. AltosUI can monitor telemetry data, - configure TeleMetrum, TeleMini and TeleDongle devices and many other + interacting with the Altus Metrum product family. AltosUI can + monitor telemetry data, configure devices and many other tasks. The primary interface window provides a selection of buttons, one for each major activity in the system. This manual is split into chapters, each of which documents one of the tasks @@ -1261,7 +1729,7 @@ NAR #88757, TRA #12200
Configure Altimeter - Select this button and then select either a TeleMetrum or + Select this button and then select either an altimeter or TeleDongle Device from the list provided. Selecting a TeleDongle device will use the radio link to configure a remote altimeter. @@ -1332,15 +1800,15 @@ NAR #88757, TRA #12200
Radio Frequency - This configures which of the configured frequencies to use for both + This configures which of the frequencies to use for both telemetry and packet command mode. Note that if you set this - value via packet command mode, you will have to reconfigure - the TeleDongle frequency before you will be able to use packet - command mode again. + value via packet command mode, the TeleDongle frequency will + also be automatically reconfigured to match so that + communication will continue afterwards.
- Radio Calibration + RF Calibration The radios in every Altus Metrum device are calibrated at the factory to ensure that they transmit and receive on the @@ -1351,6 +1819,25 @@ NAR #88757, TRA #12200 you must reprogram the unit completely.
+
+ Telemetry/RDF/APRS Enable + + Enables the radio for transmission during flight. When + disabled, the radio will not transmit anything during flight + at all. + +
+
+ APRS Interval + + How often to transmit GPS information via APRS. This option + is available on TeleMetrum v2 and TeleMega + boards. TeleMetrum v1 boards cannot transmit APRS + packets. Note that a single APRS packet takes nearly a full + second to transmit, so enabling this option will prevent + sending any other telemetry during that time. + +
Callsign @@ -1405,11 +1892,11 @@ NAR #88757, TRA #12200
Pad Orientation - Because it includes an accelerometer, TeleMetrum is - sensitive to the orientation of the board. By default, it - expects the antenna end to point forward. This parameter - allows that default to be changed, permitting the board to - be mounted with the antenna pointing aft instead. + Because it includes an accelerometer, TeleMetrum and + TeleMega are sensitive to the orientation of the board. By + default, it expects the antenna end to point forward. This + parameter allows that default to be changed, permitting the + board to be mounted with the antenna pointing aft instead. @@ -1428,6 +1915,23 @@ NAR #88757, TRA #12200
+
+ Configure Pyro Channels + + This opens a separate window to configure the additional + pyro channels available on TeleMega. One column is presented + for each channel. Each row represents a single parameter, if + enabled the parameter must meet the specified test for the + pyro channel to be fired. + + + + + + + + +
Configure AltosUI @@ -1699,7 +2203,7 @@ NAR #88757, TRA #12200 Monitor Idle This brings up a dialog similar to the Monitor Flight UI, - except it works with the altimeter in "idle" mode by sending + except it works with the altimeter in “idle” mode by sending query commands to discover the current state rather than listening for telemetry packets. @@ -1725,8 +2229,8 @@ NAR #88757, TRA #12200 AltosDroid is included in the Google Play store. To install it on your Android device, open open the Google Play Store - application and search for "altosdroid". Make sure you don't - have a space between "altos" and "droid" or you probably won't + application and search for “altosdroid”. Make sure you don't + have a space between “altos” and “droid” or you probably won't find what you want. That should bring you to the right page from which you can download and install the application. @@ -1910,7 +2414,7 @@ NAR #88757, TRA #12200 Geo-Caching... just go to the way-point and look around starting from there. - You may also enjoy having a ham radio "HT" that covers the 70cm band... you + You may also enjoy having a ham radio “HT” that covers the 70cm band... you can use that with your antenna to direction-find the rocket on the ground the same way you can use a Walston or Beeline tracker. This can be handy if the rocket is hiding in sage brush or a tree, or if the last GPS position @@ -1983,7 +2487,7 @@ NAR #88757, TRA #12200
Future Plans - In the future, we intend to offer "companion boards" for the rocket + In the future, we intend to offer “companion boards” for the rocket that will plug in to TeleMetrum to collect additional data, provide more pyro channels, and so forth. @@ -2033,7 +2537,7 @@ NAR #88757, TRA #12200 securely fastened to the air-frame. For TeleMetrum, we use nylon standoffs and nylon screws; they're good to at least 50G and cannot cause any electrical issues on the board. For - TeleMini, we usually cut small pieces of 1/16" balsa to fit + TeleMini, we usually cut small pieces of 1/16 inch balsa to fit under the screw holes, and then take 2x56 nylon screws and screw them through the TeleMini mounting holes, through the balsa and into the underlying material. @@ -2189,7 +2693,7 @@ NAR #88757, TRA #12200 in the environment and avoid having wire lengths near a natural resonant length. Altusmetrum products transmit on the 70cm amateur band, so you should avoid lengths that are a - simple ratio of that length; essentially any multiple of 1/4 + simple ratio of that length; essentially any multiple of ¼ of the wavelength (17.5cm). @@ -2428,7 +2932,7 @@ NAR #88757, TRA #12200 Confirm that the TeleMini board seems to have updated OK, which you can do by configuring it over the radio link through the TeleDongle, or - letting it come up in "flight" mode and listening for telemetry. + letting it come up in “flight” mode and listening for telemetry. @@ -2455,7 +2959,7 @@ NAR #88757, TRA #12200 Find the USB cable that you got as part of the starter kit, and - plug the "mini" end in to the mating connector on TeleMetrum or TeleDongle. + plug the “mini” end in to the mating connector on TeleMetrum or TeleDongle. @@ -2509,7 +3013,7 @@ NAR #88757, TRA #12200 Make sure the configuration parameters are reasonable looking. If the serial number and/or RF configuration values aren't right, you'll need to change them. The TeleDongle - serial number is on the "bottom" of the circuit board, and can + serial number is on the “bottom” of the circuit board, and can usually be read through the translucent blue plastic case without needing to remove the board from the case. @@ -2667,15 +3171,15 @@ NAR #88757, TRA #12200 TeleMetrum seems to shut off when disconnected from the computer. Make sure the battery is adequately charged. Remember the unit will pull more power than the USB port can deliver before the - GPS enters "locked" mode. The battery charges best when TeleMetrum + GPS enters “locked” mode. The battery charges best when TeleMetrum is turned off. - It's impossible to stop the TeleDongle when it's in "p" mode, I have - to unplug the USB cable? Make sure you have tried to "escape out" of + It's impossible to stop the TeleDongle when it's in “p” mode, I have + to unplug the USB cable? Make sure you have tried to “escape out” of this mode. If this doesn't work the reboot procedure for the TeleDongle *is* to simply unplug it. 'cu' however will retain it's - outgoing buffer IF your "escape out" ('~~') does not work. + outgoing buffer IF your “escape out” ('~~') does not work. At this point using either 'ao-view' (or possibly 'cutemon') instead of 'cu' will 'clear' the issue and allow renewed communication. @@ -2688,11 +3192,11 @@ NAR #88757, TRA #12200 then the battery is being charged at a 'trickle' rate. - There are no "dit-dah-dah-dit" sound or lights like the manual mentions? - That's the "pad" mode. Weak batteries might be the problem. + There are no “dit-dah-dah-dit” sound or lights like the manual mentions? + That's the “pad” mode. Weak batteries might be the problem. It is also possible that the TeleMetrum is horizontal and the output - is instead a "dit-dit" meaning 'idle'. For TeleMini, it's possible that - it received a command packet which would have left it in "pad" mode. + is instead a “dit-dit” meaning 'idle'. For TeleMini, it's possible that + it received a command packet which would have left it in “pad” mode. How do I save flight data? @@ -2833,18 +3337,18 @@ NAR #88757, TRA #12200 Now might be a good time to take a break and read the rest of this - manual, particularly about the two "modes" that the altimeters + manual, particularly about the two “modes” that the altimeters can be placed in. TeleMetrum uses the position of the device when booting - up will determine whether the unit is in "pad" or "idle" mode. TeleMini - enters "idle" mode when it receives a command packet within the first 5 seconds - of being powered up, otherwise it enters "pad" mode. + up will determine whether the unit is in “pad” or “idle” mode. TeleMini + enters “idle” mode when it receives a command packet within the first 5 seconds + of being powered up, otherwise it enters “pad” mode. You can access an altimeter in idle mode from the TeleDongle's USB connection using the radio link by issuing a 'p' command to the TeleDongle. Practice connecting and disconnecting ('~~' while using 'cu') from the altimeter. If - you cannot escape out of the "p" command, (by using a '~~' when in + you cannot escape out of the “p” command, (by using a '~~' when in CU) then it is likely that your kernel has issues. Try a newer version. @@ -2854,7 +3358,7 @@ NAR #88757, TRA #12200 is in 'idle mode' and then place the rocket vertically on the launch pad, walk away and then issue a reboot command. The altimeter will reboot and start sending data - having changed to the "pad" mode. If the TeleDongle is not receiving + having changed to the “pad” mode. If the TeleDongle is not receiving this data, you can disconnect 'cu' from the TeleDongle using the procedures mentioned above and THEN connect to the TeleDongle from inside 'ao-view'. If this doesn't work, disconnect from the @@ -3024,8 +3528,8 @@ NAR #88757, TRA #12200 The +1g and -1g calibration points are included in each telemetry frame and are part of the header stored in onboard flash to be downloaded after flight. We always store and return raw ADC - samples for each sensor... so nothing is permanently "lost" or - "damaged" if the calibration is poor. + samples for each sensor... so nothing is permanently “lost” or + “damaged” if the calibration is poor. In the unlikely event an accel cal goes badly, it is possible