X-Git-Url: https://git.gag.com/?p=fw%2Faltos;a=blobdiff_plain;f=doc%2Faltusmetrum.xsl;h=aeb43acb4a0b8c7fdb6616e1feff9a9ec55ae009;hp=b8aee23842d4eed789b93ca6afdd251570332e70;hb=e268798dc260311f5f0167909481b41c9d27fc1c;hpb=65ca6f0d7c96432413868274b2cfdea4b76683e4
diff --git a/doc/altusmetrum.xsl b/doc/altusmetrum.xsl
index b8aee238..aeb43acb 100644
--- a/doc/altusmetrum.xsl
+++ b/doc/altusmetrum.xsl
@@ -66,7 +66,7 @@
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
- in this book. Bob was one of our first customers for a production
+ 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!
@@ -186,7 +186,7 @@ NAR #88757, TRA #12200
All Altus Metrum products are sophisticated electronic devices.
When handled gently and properly installed in an air-frame, they
- will deliver impressive results. However, like all electronic
+ will deliver impressive results. However, as with all electronic
devices, there are some precautions you must take.
@@ -319,8 +319,8 @@ NAR #88757, TRA #12200
In flight or "pad" mode, the altimeter engages the flight
- state machine, goes into transmit-only mode on the RF link
- sending telemetry, and waits for launch to be detected.
+ 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)
on the beeper or lights, followed by beeps or flashes
indicating the state of the pyrotechnic igniter continuity.
@@ -336,10 +336,10 @@ NAR #88757, TRA #12200
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 on the RF link when in idle mode for requests sent via
+ listen for the radio link when in idle mode for requests sent via
TeleDongle. Commands can be issued to a TeleMetrum in idle mode
over either
- USB or the RF link equivalently. TeleMini only has the RF link.
+ USB or the radio link equivalently. TeleMini only has the radio link.
Idle mode is useful for configuring the altimeter, for extracting data
from the on-board storage chip after flight, and for ground testing
pyro charges.
@@ -349,7 +349,7 @@ NAR #88757, TRA #12200
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
- via TeleDongle over the RF link to cause the altimeter to reboot and
+ via TeleDongle over the radio link to cause the altimeter to reboot and
come up in flight mode. This is much safer than standing on the top
step of a rickety step-ladder or hanging off the side of a launch
tower with a screw-driver trying to turn on your avionics before
@@ -393,23 +393,21 @@ NAR #88757, TRA #12200
either be done with TeleMetrum directly connected to the
computer via the USB cable, or through the radio
link. TeleMini doesn't provide a USB connector and so it is
- always controlled through the radio link. Select the
- appropriate TeleDongle device when the list of devices is
- presented and AltosUI will interact with an altimter over the
- radio link.
+ always communicated with over radio. Select the appropriate
+ TeleDongle device when the list of devices is presented and
+ AltosUI will interact with an altimeter over the radio link.
One oddity in the current interface is how AltosUI selects the
- frequency for packet mode communications. Instead of providing
+ frequency for radio communications. Instead of providing
an interface to specifically configure the frequency, it uses
whatever frequency was most recently selected for the target
TeleDongle device in Monitor Flight mode. If you haven't ever
used that mode with the TeleDongle in question, select the
- Monitor Flight button from the top level UI, pick the
- appropriate TeleDongle device. Once the flight monitoring
+ Monitor Flight button from the top level UI, and pick the
+ appropriate TeleDongle device. Once the flight monitoring
window is open, select the desired frequency and then close it
- down again. All Packet Command Mode operations will now use
- that frequency.
+ down again. All radio communications will now use that frequency.
@@ -440,16 +438,17 @@ NAR #88757, TRA #12200
- Packet command mode uses the same RF frequencies as telemetry
- mode. Configure the desired TeleDongle frequency using the
- flight monitor window frequency selector and then close that
- window before performing the desired operation.
+ Operation over the radio link for configuring an altimeter, ground
+ testing igniters, and so forth uses the same RF frequencies as flight
+ telemetry. To configure the desired TeleDongle frequency, select
+ the monitor flight tab, then use the frequency selector and
+ close the window before performing other desired radio operations.
- TeleMetrum only enables packet command mode in 'idle' mode, so
+ TeleMetrum only enables radio commanding in 'idle' mode, so
make sure you have TeleMetrum lying horizontally when you turn
it on. Otherwise, TeleMetrum will start in 'pad' mode ready for
- flight and will not be listening for command packets from TeleDongle.
+ flight, and will not be listening for command packets from TeleDongle.
TeleMini listens for a command packet for five seconds after
@@ -463,12 +462,10 @@ NAR #88757, TRA #12200
operation can be performed.
- When packet command mode is enabled, you can monitor the link
- by watching the lights on the
- devices. The red LED will flash each time they
- transmit a packet while the green LED will light up
- on TeleDongle while it is waiting to receive a packet from
- the altimeter.
+ You can monitor the operation of the radio link by watching the
+ lights on the devices. The red LED will flash each time a packet
+ is tramsitted, while the green LED will light up on TeleDongle when
+ it is waiting to receive a packet from the altimeter.
@@ -476,7 +473,7 @@ NAR #88757, TRA #12200
An important aspect of preparing a rocket using electronic deployment
for flight is ground testing the recovery system. Thanks
- to the bi-directional RF link central to the Altus Metrum system,
+ to the bi-directional radio link central to the Altus Metrum system,
this can be accomplished in a TeleMetrum or TeleMini equipped rocket
with less work than you may be accustomed to with other systems. It
can even be fun!
@@ -501,16 +498,16 @@ NAR #88757, TRA #12200
link.
- By design, the altimeter firmware listens for an RF connection when
+ By design, the altimeter firmware listens for the radio link when
it's in "idle mode", which
- allows us to use the RF link to configure the rocket, do things like
+ 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
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 and out over
- the RF link in case the rocket crashes and we aren't able to extract
+ the rocket through
+ the radio in case the rocket crashes and we aren't able to extract
data later...
@@ -536,34 +533,21 @@ NAR #88757, TRA #12200
simple. Even on our baro-only TeleMini board, the use of a Kalman
filter means there is no need to set a "mach delay". The few
configurable parameters can all be set using AltosUI over USB or
- or RF link via TeleDongle.
+ or radio link via TeleDongle.
- Radio Frequencies
+ Radio Frequency
- The Altus Metrum boards support frequencies in the 70cm
+ Altus Metrum boards support radio frequencies in the 70cm
band. By default, the configuration interface provides a
- list of 10 common 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 who will use each
- frequency and when to avoid interference. And of course, both
+ launch, we highly recommend coordinating when and by whom each
+ frequency will be used to avoid interference. And of course, both
altimeter and TeleDongle must be configured to the same
frequency to successfully communicate with each other.
-
- To set the radio frequency, use the 'c R' command to specify the
- radio transceiver configuration parameter. This parameter is computed
- using the desired frequency, 'F', the radio calibration parameter, 'C' (showed by the 'c s' command) and
- the standard calibration reference frequency, 'S', (normally 434.550MHz):
-
- R = F / S * C
-
- Round the result to the nearest integer value.
- As with all 'c' sub-commands, follow this with a 'c w' to write the
- change to the parameter block in the on-board flash on
- your altimeter board if you want the change to stay in place across reboots.
-
Apogee Delay
@@ -576,20 +560,14 @@ NAR #88757, TRA #12200
primary and backup pyrotechnic charges do not fire simultaneously.
- To set the apogee delay, use the 'c d' command.
- As with all 'c' sub-commands, follow this with a 'c w' to write the
- change to the parameter block in the on-board DataFlash chip.
-
-
- Please note that the Altus Metrum apogee detection algorithm
- fires exactly at apogee. If you are also flying an
- altimeter like the PerfectFlite MAWD, which only supports
- selecting 0 or 1 seconds of apogee delay, you may wish to
- set the MAWD to 0 seconds delay and set the TeleMetrum to
- fire your backup 2 or 3 seconds later to avoid any chance of
- both charges firing simultaneously. We've flown several
- air-frames this way quite happily, including Keith's
- successful L3 cert.
+ The Altus Metrum apogee detection algorithm fires exactly at
+ apogee. If you are also flying an altimeter like the
+ PerfectFlite MAWD, which only supports selecting 0 or 1
+ seconds of apogee delay, you may wish to set the MAWD to 0
+ seconds delay and set the TeleMetrum to fire your backup 2
+ or 3 seconds later to avoid any chance of both charges
+ firing simultaneously. We've flown several air-frames this
+ way quite happily, including Keith's successful L3 cert.
@@ -604,324 +582,81 @@ NAR #88757, TRA #12200
than the primary so that both pyrotechnic charges don't fire
simultaneously.
-
- To set the main deployment altitude, use the 'c m' command.
- As with all 'c' sub-commands, follow this with a 'c w' to write the
- change to the parameter block in the on-board DataFlash chip.
-
-
-
- Calibration
-
- There are only two calibrations required for a TeleMetrum board, and
- only one for TeleDongle and TeleMini.
-
- Radio Frequency
-
- The radio frequency is synthesized from a clock based on the 48 MHz
- crystal on the board. The actual frequency of this oscillator must be
- measured to generate a calibration constant. While our GFSK modulation
- bandwidth is wide enough to allow boards to communicate even when
- their oscillators are not on exactly the same frequency, performance
- is best when they are closely matched.
- Radio frequency calibration requires a calibrated frequency counter.
- Fortunately, once set, the variation in frequency due to aging and
- temperature changes is small enough that re-calibration by customers
- should generally not be required.
-
-
- To calibrate the radio frequency, connect the UHF antenna port to a
- frequency counter, set the board to 434.550MHz, and use the 'C'
- command to generate a CW carrier. Wait for the transmitter temperature
- to stabilize and the frequency to settle down.
- Then, divide 434.550 MHz by the
- measured frequency and multiply by the current radio cal value show
- in the 'c s' command. For an unprogrammed board, the default value
- is 1186611. Take the resulting integer and program it using the 'c f'
- command. Testing with the 'C' command again should show a carrier
- within a few tens of Hertz of the intended frequency.
- As with all 'c' sub-commands, follow this with a 'c w' to write the
- change to the parameter block in the on-board DataFlash chip.
-
+ Maximum Flight Log
- when the radio calibration value is changed, the radio
- frequency value is reset to the same value, so you'll need
- to recompute and reset the radio frequency value using the
- new radio calibration value.
+ TeleMetrum version 1.1 has 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, there's plenty of space to store many flights worth
+ of data.
+
+
+ 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 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 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.
- TeleMetrum Accelerometer
-
- The TeleMetrum accelerometer we use has its own 5 volt power supply and
- the output must be passed through a resistive voltage divider to match
- the input of our 3.3 volt ADC. This means that unlike the barometric
- sensor, the output of the acceleration sensor is not ratio-metric to
- the ADC converter, and calibration is required. We also support the
- use of any of several accelerometers from a Freescale family that
- includes at least +/- 40g, 50g, 100g, and 200g parts. Using gravity,
- a simple 2-point calibration yields acceptable results capturing both
- the different sensitivities and ranges of the different accelerometer
- parts and any variation in power supply voltages or resistor values
- in the divider network.
-
-
- To calibrate the acceleration sensor, use the 'c a 0' command. You
- will be prompted to orient the board vertically with the UHF antenna
- up and press a key, then to orient the board vertically with the
- UHF antenna down and press a key.
- As with all 'c' sub-commands, follow this with a 'c w' to write the
- change to the parameter block in the on-board DataFlash chip.
-
-
- The +1g and -1g calibration points are included in each telemetry
- frame and are part of the header extracted by ao-dumplog after flight.
- Note that we always store and return raw ADC samples for each
- sensor... nothing is permanently "lost" or "damaged" if the
- calibration is poor.
-
-
- In the unlikely event an accel cal that goes badly, it is possible
- that TeleMetrum may always come up in 'pad mode' and as such not be
- listening to either the USB or radio interfaces. If that happens,
- there is a special hook in the firmware to force the board back
- in to 'idle mode' so you can re-do the cal. To use this hook, you
- just need to ground the SPI clock pin at power-on. This pin is
- available as pin 2 on the 8-pin companion connector, and pin 1 is
- ground. So either carefully install a fine-gauge wire jumper
- between the two pins closest to the index hole end of the 8-pin
- connector, or plug in the programming cable to the 8-pin connector
- and use a small screwdriver or similar to short the two pins closest
- to the index post on the 4-pin end of the programming cable, and
- power up the board. It should come up in 'idle mode' (two beeps).
-
+ Ignite Mode
+
+ Instead of firing one charge at apogee and another charge at
+ a fixed height above the ground, you can configure the
+ altimeter to fire both at apogee or both during
+ descent. This was added to support an airframe that has two
+ TeleMetrum computers, one in the fin can and one in the
+ nose.
+
+
+ Providing the ability to use both igniters for apogee or
+ main allows some level of redundancy without needing two
+ flight computers. In Redundant Apogee or Redundant Main
+ mode, the two charges will be fired two seconds apart.
+
-
-
- Updating Device Firmware
-
- The big conceptual thing to realize is that you have to use a
- TeleDongle as a programmer to update a TeleMetrum or TeleMini,
- and a TeleMetrum or other TeleDongle to program the TeleDongle
- Due to limited memory resources in the cc1111, we don't support
- programming directly over USB.
-
-
- You may wish to begin by ensuring you have current firmware images.
- These are distributed as part of the AltOS software bundle that
- also includes the AltosUI ground station program. Newer ground
- station versions typically work fine with older firmware versions,
- so you don't need to update your devices just to try out new
- software features. You can always download the most recent
- version from .
-
-
- We recommend updating the altimeter first, before updating TeleDongle.
-
-
- Updating TeleMetrum Firmware
-
-
- Find the 'programming cable' that you got as part of the starter
- kit, that has a red 8-pin MicroMaTch connector on one end and a
- red 4-pin MicroMaTch connector on the other end.
-
-
- Take the 2 screws out of the TeleDongle case to get access
- to the circuit board.
-
-
- Plug the 8-pin end of the programming cable to the
- matching connector on the TeleDongle, and the 4-pin end to the
- matching connector on the TeleMetrum.
- Note that each MicroMaTch connector has an alignment pin that
- goes through a hole in the PC board when you have the cable
- oriented correctly.
-
-
- Attach a battery to the TeleMetrum board.
-
-
- Plug the TeleDongle into your computer's USB port, and power
- up the TeleMetrum.
-
-
- Run AltosUI, and select 'Flash Image' from the File menu.
-
-
- Pick the TeleDongle device from the list, identifying it as the
- programming device.
-
-
- Select the image you want put on the TeleMetrum, which should have a
- name in the form telemetrum-v1.1-1.0.0.ihx. It should be visible
- in the default directory, if not you may have to poke around
- your system to find it.
-
-
- 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.
-
-
- Hit the 'OK' button and the software should proceed to flash
- the TeleMetrum with new firmware, showing a progress bar.
-
-
- Confirm that the TeleMetrum board seems to have updated OK, which you
- can do by plugging in to it over USB and using a terminal program
- to connect to the board and issue the 'v' command to check
- the version, etc.
-
-
- If something goes wrong, give it another try.
-
-
-
-
- Updating TeleMini Firmware
-
-
- You'll need a special 'programming cable' to reprogram the
- TeleMini. It's available on the Altus Metrum web store, or
- you can make your own using an 8-pin MicroMaTch connector on
- one end and a set of four pins on the other.
-
-
- Take the 2 screws out of the TeleDongle case to get access
- to the circuit board.
-
-
- Plug the 8-pin end of the programming cable to the matching
- connector on the TeleDongle, and the 4-pins into the holes
- in the TeleMini circuit board. Note that the MicroMaTch
- connector has an alignment pin that goes through a hole in
- the PC board when you have the cable oriented correctly, and
- that pin 1 on the TeleMini board is marked with a square pad
- while the other pins have round pads.
-
-
- Attach a battery to the TeleMini board.
-
-
- Plug the TeleDongle into your computer's USB port, and power
- up the TeleMini
-
-
- Run AltosUI, and select 'Flash Image' from the File menu.
-
-
- Pick the TeleDongle device from the list, identifying it as the
- programming device.
-
-
- Select the image you want put on the TeleMini, which should have a
- name in the form telemini-v1.0-1.0.0.ihx. It should be visible
- in the default directory, if not you may have to poke around
- your system to find it.
-
-
- 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.
-
-
- Hit the 'OK' button and the software should proceed to flash
- the TeleMini with new firmware, showing a progress bar.
-
-
- Confirm that the TeleMini board seems to have updated OK, which you
- can do by configuring it over the RF link through the TeleDongle, or
- letting it come up in "flight" mode and listening for telemetry.
-
-
- If something goes wrong, give it another try.
-
-
-
-
- Updating TeleDongle Firmware
-
- Updating TeleDongle's firmware is just like updating TeleMetrum or TeleMini
- firmware, but you use either a TeleMetrum or another TeleDongle as the programmer.
+
+ 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
+ terminals nearest the tail.
-
-
- Find the 'programming cable' that you got as part of the starter
- kit, that has a red 8-pin MicroMaTch connector on one end and a
- red 4-pin MicroMaTch connector on the other end.
-
-
- 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.
-
-
- Take the 2 screws out of the TeleDongle case to get access
- to the circuit board.
-
-
- Plug the 8-pin end of the programming cable to the
- matching connector on the programmer, and the 4-pin end to the
- matching connector on the TeleDongle.
- Note that each MicroMaTch connector has an alignment pin that
- goes through a hole in the PC board when you have the cable
- oriented correctly.
-
-
- Attach a battery to the TeleMetrum board if you're using one.
-
-
- Plug both the programmer and the TeleDongle into your computer's USB
- ports, and power up the programmer.
-
-
- Run AltosUI, and select 'Flash Image' from the File menu.
-
-
- Pick the programmer device from the list, identifying it as the
- programming device.
-
-
- Select the image you want put on the TeleDongle, which should have a
- name in the form teledongle-v0.2-1.0.0.ihx. It should be visible
- in the default directory, if not you may have to poke around
- your system to find it.
-
-
- 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
- usually be read through the translucent blue plastic case without
- needing to remove the board from the case.
-
-
- Hit the 'OK' button and the software should proceed to flash
- the TeleDongle with new firmware, showing a progress bar.
-
-
- Confirm that the TeleDongle board seems to have updated OK, which you
- can do by plugging in to it over USB and using a terminal program
- to connect to the board and issue the 'v' command to check
- the version, etc. Once you're happy, remove the programming cable
- and put the cover back on the TeleDongle.
-
-
- If something goes wrong, give it another try.
-
-
-
- Be careful removing the programming cable from the locking 8-pin
- connector on TeleMetrum. You'll need a fingernail or perhaps a thin
- screwdriver or knife blade to gently pry the locking ears out
- slightly to extract the connector. We used a locking connector on
- TeleMetrum to help ensure that the cabling to companion boards
- used in a rocket don't ever come loose accidentally in flight.
-
+
-
@@ -1551,10 +1286,10 @@ NAR #88757, TRA #12200
Callsign
- This value is used in command packet mode and is transmitted
- in each packet sent from TeleDongle and received from
- TeleMetrum. It is not used in telemetry mode as that transmits
- packets only from TeleMetrum to TeleDongle. Configure this
+ This value is transmitted in each command packet sent from
+ TeleDongle and received from an altimeter. It is not used in
+ telemetry mode, as the callsign configured in the altimeter board
+ is included in all telemetry packets. Configure this
with the AltosUI operators call sign as needed to comply with
your local radio regulations.
@@ -1594,7 +1329,7 @@ NAR #88757, TRA #12200
This reprograms any Altus Metrum device by using a TeleMetrum
or TeleDongle as a programming dongle. Please read the
directions for flashing devices in the Updating Device
- Firmware section above
+ Firmware chapter below.
Once you have the programmer and target devices connected,
@@ -1744,7 +1479,7 @@ NAR #88757, TRA #12200
for Linux which can perform most of the same tasks.
- After the flight, you can use the RF link to extract the more detailed data
+ After the flight, you can use the radio link to extract the more detailed data
logged in either TeleMetrum or TeleMini devices, or you can use a mini USB cable to plug into the
TeleMetrum board directly. Pulling out the data without having to open up
the rocket is pretty cool! A USB cable is also how you charge the Li-Po
@@ -1800,7 +1535,7 @@ NAR #88757, TRA #12200
Data Analysis
Our software makes it easy to log the data from each flight, both the
- telemetry received over the RF link during the flight itself, and the more
+ telemetry received during the flight itself, and the more
complete data log recorded in the flash memory on the altimeter
board. Once this data is on your computer, our post-flight tools make it
easy to quickly get to the numbers everyone wants, like apogee altitude,
@@ -2027,29 +1762,252 @@ NAR #88757, TRA #12200
- Ground Testing
-
- The most important aspect of any installation is careful
- ground testing. Bringing an air-frame up to the LCO table which
- hasn't been ground tested can lead to delays or ejection
- charges firing on the pad, or, even worse, a recovery system
- failure.
-
+ Ground Testing
+
+ The most important aspect of any installation is careful
+ ground testing. Bringing an air-frame up to the LCO table which
+ hasn't been ground tested can lead to delays or ejection
+ charges firing on the pad, or, even worse, a recovery system
+ failure.
+
+
+ Do a 'full systems' test that includes wiring up all igniters
+ without any BP and turning on all of the electronics in flight
+ mode. This will catch any mistakes in wiring and any residual
+ RFI issues that might accidentally fire igniters at the wrong
+ time. Let the air-frame sit for several minutes, checking for
+ adequate telemetry signal strength and GPS lock.
+
+
+ Ground test the ejection charges. Prepare the rocket for
+ flight, loading ejection charges and igniters. Completely
+ assemble the air-frame and then use the 'Fire Igniters'
+ interface through a TeleDongle to command each charge to
+ fire. Make sure the charge is sufficient to robustly separate
+ the air-frame and deploy the recovery system.
+
+
+
+
+ Updating Device Firmware
+
+ The big conceptual thing to realize is that you have to use a
+ TeleDongle as a programmer to update a TeleMetrum or TeleMini,
+ and a TeleMetrum or other TeleDongle to program the TeleDongle
+ Due to limited memory resources in the cc1111, we don't support
+ programming directly over USB.
+
+
+ You may wish to begin by ensuring you have current firmware images.
+ These are distributed as part of the AltOS software bundle that
+ also includes the AltosUI ground station program. Newer ground
+ station versions typically work fine with older firmware versions,
+ so you don't need to update your devices just to try out new
+ software features. You can always download the most recent
+ version from .
+
+
+ We recommend updating the altimeter first, before updating TeleDongle.
+
+
+ Updating TeleMetrum Firmware
+
+
+ Find the 'programming cable' that you got as part of the starter
+ kit, that has a red 8-pin MicroMaTch connector on one end and a
+ red 4-pin MicroMaTch connector on the other end.
+
+
+ Take the 2 screws out of the TeleDongle case to get access
+ to the circuit board.
+
+
+ Plug the 8-pin end of the programming cable to the
+ matching connector on the TeleDongle, and the 4-pin end to the
+ matching connector on the TeleMetrum.
+ Note that each MicroMaTch connector has an alignment pin that
+ goes through a hole in the PC board when you have the cable
+ oriented correctly.
+
+
+ Attach a battery to the TeleMetrum board.
+
+
+ Plug the TeleDongle into your computer's USB port, and power
+ up the TeleMetrum.
+
+
+ Run AltosUI, and select 'Flash Image' from the File menu.
+
+
+ Pick the TeleDongle device from the list, identifying it as the
+ programming device.
+
+
+ Select the image you want put on the TeleMetrum, which should have a
+ name in the form telemetrum-v1.1-1.0.0.ihx. It should be visible
+ in the default directory, if not you may have to poke around
+ your system to find it.
+
+
+ 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.
+
+
+ Hit the 'OK' button and the software should proceed to flash
+ the TeleMetrum with new firmware, showing a progress bar.
+
+
+ Confirm that the TeleMetrum board seems to have updated OK, which you
+ can do by plugging in to it over USB and using a terminal program
+ to connect to the board and issue the 'v' command to check
+ the version, etc.
+
+
+ If something goes wrong, give it another try.
+
+
+
+
+ Updating TeleMini Firmware
+
+
+ You'll need a special 'programming cable' to reprogram the
+ TeleMini. It's available on the Altus Metrum web store, or
+ you can make your own using an 8-pin MicroMaTch connector on
+ one end and a set of four pins on the other.
+
+
+ Take the 2 screws out of the TeleDongle case to get access
+ to the circuit board.
+
+
+ Plug the 8-pin end of the programming cable to the matching
+ connector on the TeleDongle, and the 4-pins into the holes
+ in the TeleMini circuit board. Note that the MicroMaTch
+ connector has an alignment pin that goes through a hole in
+ the PC board when you have the cable oriented correctly, and
+ that pin 1 on the TeleMini board is marked with a square pad
+ while the other pins have round pads.
+
+
+ Attach a battery to the TeleMini board.
+
+
+ Plug the TeleDongle into your computer's USB port, and power
+ up the TeleMini
+
+
+ Run AltosUI, and select 'Flash Image' from the File menu.
+
+
+ Pick the TeleDongle device from the list, identifying it as the
+ programming device.
+
+
+ Select the image you want put on the TeleMini, which should have a
+ name in the form telemini-v1.0-1.0.0.ihx. It should be visible
+ in the default directory, if not you may have to poke around
+ your system to find it.
+
+
+ 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.
+
+
+ Hit the 'OK' button and the software should proceed to flash
+ the TeleMini with new firmware, showing a progress bar.
+
+
+ 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.
+
+
+ If something goes wrong, give it another try.
+
+
+
+
+ Updating TeleDongle Firmware
- Do a 'full systems' test that includes wiring up all igniters
- without any BP and turning on all of the electronics in flight
- mode. This will catch any mistakes in wiring and any residual
- RFI issues that might accidentally fire igniters at the wrong
- time. Let the air-frame sit for several minutes, checking for
- adequate telemetry signal strength and GPS lock.
-
+ Updating TeleDongle's firmware is just like updating TeleMetrum or TeleMini
+ firmware, but you use either a TeleMetrum or another TeleDongle as the programmer.
+
+
+
+ Find the 'programming cable' that you got as part of the starter
+ kit, that has a red 8-pin MicroMaTch connector on one end and a
+ red 4-pin MicroMaTch connector on the other end.
+
+
+ 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.
+
+
+ Take the 2 screws out of the TeleDongle case to get access
+ to the circuit board.
+
+
+ Plug the 8-pin end of the programming cable to the
+ matching connector on the programmer, and the 4-pin end to the
+ matching connector on the TeleDongle.
+ Note that each MicroMaTch connector has an alignment pin that
+ goes through a hole in the PC board when you have the cable
+ oriented correctly.
+
+
+ Attach a battery to the TeleMetrum board if you're using one.
+
+
+ Plug both the programmer and the TeleDongle into your computer's USB
+ ports, and power up the programmer.
+
+
+ Run AltosUI, and select 'Flash Image' from the File menu.
+
+
+ Pick the programmer device from the list, identifying it as the
+ programming device.
+
+
+ Select the image you want put on the TeleDongle, which should have a
+ name in the form teledongle-v0.2-1.0.0.ihx. It should be visible
+ in the default directory, if not you may have to poke around
+ your system to find it.
+
+
+ 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
+ usually be read through the translucent blue plastic case without
+ needing to remove the board from the case.
+
+
+ Hit the 'OK' button and the software should proceed to flash
+ the TeleDongle with new firmware, showing a progress bar.
+
+
+ Confirm that the TeleDongle board seems to have updated OK, which you
+ can do by plugging in to it over USB and using a terminal program
+ to connect to the board and issue the 'v' command to check
+ the version, etc. Once you're happy, remove the programming cable
+ and put the cover back on the TeleDongle.
+
+
+ If something goes wrong, give it another try.
+
+
- Ground test the ejection charges. Prepare the rocket for
- flight, loading ejection charges and igniters. Completely
- assemble the air-frame and then use the 'Fire Igniters'
- interface through a TeleDongle to command each charge to
- fire. Make sure the charge is sufficient to robustly separate
- the air-frame and deploy the recovery system.
+ Be careful removing the programming cable from the locking 8-pin
+ connector on TeleMetrum. You'll need a fingernail or perhaps a thin
+ screwdriver or knife blade to gently pry the locking ears out
+ slightly to extract the connector. We used a locking connector on
+ TeleMetrum to help ensure that the cabling to companion boards
+ used in a rocket don't ever come loose accidentally in flight.
@@ -2209,7 +2167,7 @@ NAR #88757, TRA #12200
but is easily changed using the menus in AltosUI. The files that
are written end in '.telem'. The after-flight
data-dumped files will end in .eeprom and represent continuous data
- unlike the RF-linked .telem files that are subject to losses
+ unlike the .telem files that are subject to losses
along the RF data path.
See the above instructions on what and how to save the eeprom stored
data after physically retrieving your altimeter. Make sure to save
@@ -2290,6 +2248,43 @@ NAR #88757, TRA #12200
Verify you can connect and disconnect from the units while in your
terminal program by sending the escape-disconnect mentioned above.
+
+ To set the radio frequency, use the 'c R' command to specify the
+ radio transceiver configuration parameter. This parameter is computed
+ using the desired frequency, 'F', the radio calibration parameter, 'C' (showed by the 'c s' command) and
+ the standard calibration reference frequency, 'S', (normally 434.550MHz):
+
+ R = F / S * C
+
+ Round the result to the nearest integer value.
+ As with all 'c' sub-commands, follow this with a 'c w' to write the
+ change to the parameter block in the on-board flash on
+ your altimeter board if you want the change to stay in place across reboots.
+
+
+ To set the apogee delay, use the 'c d' command.
+ As with all 'c' sub-commands, follow this with a 'c w' to write the
+ change to the parameter block in the on-board DataFlash chip.
+
+
+ To set the main deployment altitude, use the 'c m' command.
+ As with all 'c' sub-commands, follow this with a 'c w' to write the
+ change to the parameter block in the on-board DataFlash chip.
+
+
+ To calibrate the radio frequency, connect the UHF antenna port to a
+ frequency counter, set the board to 434.550MHz, and use the 'C'
+ command to generate a CW carrier. Wait for the transmitter temperature
+ to stabilize and the frequency to settle down.
+ Then, divide 434.550 MHz by the
+ measured frequency and multiply by the current radio cal value show
+ in the 'c s' command. For an unprogrammed board, the default value
+ is 1186611. Take the resulting integer and program it using the 'c f'
+ command. Testing with the 'C' command again should show a carrier
+ within a few tens of Hertz of the intended frequency.
+ As with all 'c' sub-commands, follow this with a 'c w' to write the
+ change to the parameter block in the on-board DataFlash chip.
+
Note that the 'reboot' command, which is very useful on the altimeters,
will likely just cause problems with the dongle. The *correct* way
@@ -2297,7 +2292,7 @@ NAR #88757, TRA #12200
A fun thing to do at the launch site and something you can do while
- learning how to use these units is to play with the RF-link access
+ learning how to use these units is to play with the radio link access
between an altimeter and the TeleDongle. Be aware that you *must* create
some physical separation between the devices, otherwise the link will
not function due to signal overload in the receivers in each device.
@@ -2312,14 +2307,14 @@ NAR #88757, TRA #12200
You can access an altimeter in idle mode from the TeleDongle's USB
- connection using the RF link
+ 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
CU) then it is likely that your kernel has issues. Try a newer version.
- Using this RF link allows you to configure the altimeter, test
+ Using this radio link allows you to configure the altimeter, test
fire e-matches and igniters from the flight line, check pyro-match
continuity and so forth. You can leave the unit turned on while it
is in 'idle mode' and then place the
@@ -2356,7 +2351,7 @@ NAR #88757, TRA #12200
strength providing an indication of the direction from receiver to rocket.
- TeleMetrum also provides GPS trekking data, which can further simplify
+ TeleMetrum also provides GPS tracking data, which can further simplify
locating the rocket once it has landed. (The last good GPS data
received before touch-down will be on the data screen of 'ao-view'.)
@@ -2380,6 +2375,111 @@ NAR #88757, TRA #12200
once you enable the voice output!
+
+ Calibration
+
+ There are only two calibrations required for a TeleMetrum board, and
+ only one for TeleDongle and TeleMini. All boards are shipped from
+ the factory pre-calibrated, but the procedures are documented here
+ in case they are ever needed. Re-calibration is not supported by
+ AltosUI, you must connect to the board with a serial terminal program
+ and interact directly with the on-board command interpreter to effect
+ calibration.
+
+
+ Radio Frequency
+
+ The radio frequency is synthesized from a clock based on the 48 MHz
+ crystal on the board. The actual frequency of this oscillator
+ must be measured to generate a calibration constant. While our
+ GFSK modulation
+ bandwidth is wide enough to allow boards to communicate even when
+ their oscillators are not on exactly the same frequency, performance
+ is best when they are closely matched.
+ Radio frequency calibration requires a calibrated frequency counter.
+ Fortunately, once set, the variation in frequency due to aging and
+ temperature changes is small enough that re-calibration by customers
+ should generally not be required.
+
+
+ To calibrate the radio frequency, connect the UHF antenna port to a
+ frequency counter, set the board to 434.550MHz, and use the 'C'
+ command in the on-board command interpreter to generate a CW
+ carrier. For TeleMetrum, this is best done over USB. For TeleMini,
+ note that the only way to escape the 'C' command is via power cycle
+ since the board will no longer be listening for commands once it
+ starts generating a CW carrier.
+
+
+ Wait for the transmitter temperature to stabilize and the frequency
+ to settle down. Then, divide 434.550 MHz by the
+ measured frequency and multiply by the current radio cal value show
+ in the 'c s' command. For an unprogrammed board, the default value
+ is 1186611. Take the resulting integer and program it using the 'c f'
+ command. Testing with the 'C' command again should show a carrier
+ within a few tens of Hertz of the intended frequency.
+ As with all 'c' sub-commands, follow this with a 'c w' to write the
+ change to the parameter block in the on-board DataFlash chip.
+
+
+ Note that any time you re-do the radio frequency calibration, the
+ radio frequency is reset to the default 434.550 Mhz. If you want
+ to use another frequency, you will have to set that again after
+ calibration is completed.
+
+
+
+ TeleMetrum Accelerometer
+
+ The TeleMetrum accelerometer we use has its own 5 volt power
+ supply and
+ the output must be passed through a resistive voltage divider to match
+ the input of our 3.3 volt ADC. This means that unlike the barometric
+ sensor, the output of the acceleration sensor is not ratio-metric to
+ the ADC converter, and calibration is required. Explicitly
+ calibrating the accelerometers also allows us to load any device
+ from a Freescale family that includes at least +/- 40g, 50g, 100g,
+ and 200g parts. Using gravity,
+ a simple 2-point calibration yields acceptable results capturing both
+ the different sensitivities and ranges of the different accelerometer
+ parts and any variation in power supply voltages or resistor values
+ in the divider network.
+
+
+ To calibrate the acceleration sensor, use the 'c a 0' command. You
+ will be prompted to orient the board vertically with the UHF antenna
+ up and press a key, then to orient the board vertically with the
+ UHF antenna down and press a key. Note that the accuracy of this
+ calibration depends primarily on how perfectly vertical and still
+ the board is held during the cal process. As with all 'c'
+ sub-commands, follow this with a 'c w' to write the
+ change to the parameter block in the on-board DataFlash chip.
+
+
+ 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.
+
+
+ In the unlikely event an accel cal goes badly, it is possible
+ that TeleMetrum may always come up in 'pad mode' and as such not be
+ listening to either the USB or radio link. If that happens,
+ there is a special hook in the firmware to force the board back
+ in to 'idle mode' so you can re-do the cal. To use this hook, you
+ just need to ground the SPI clock pin at power-on. This pin is
+ available as pin 2 on the 8-pin companion connector, and pin 1 is
+ ground. So either carefully install a fine-gauge wire jumper
+ between the two pins closest to the index hole end of the 8-pin
+ connector, or plug in the programming cable to the 8-pin connector
+ and use a small screwdriver or similar to short the two pins closest
+ to the index post on the 4-pin end of the programming cable, and
+ power up the board. It should come up in 'idle mode' (two beeps),
+ allowing a re-cal.
+
+
+
Release Notes