<surname>Towns</surname>
</author>
<copyright>
- <year>2014</year>
+ <year>2015</year>
<holder>Bdale Garbee and Keith Packard</holder>
</copyright>
<mediaobject>
</para>
</legalnotice>
<revhistory>
+ <revision>
+ <revnumber>1.6.1</revnumber>
+ <date>15 July 2015</date>
+ <revremark>
+ Minor release adding TeleBT v3.0 support.
+ </revremark>
+ </revision>
+ <revision>
+ <revnumber>1.6</revnumber>
+ <date>8 January 2015</date>
+ <revremark>
+ Major release adding TeleDongle v3.0 support.
+ </revremark>
+ </revision>
<revision>
<revnumber>1.5</revnumber>
<date>6 September 2014</date>
channels and integrated gyroscopes for staging/air-start inhibit.
</para>
<para>
- TeleDongle was our first ground station, providing a USB to RF
+ TeleDongle v0.2 was our first ground station, providing a USB to RF
interfaces for communicating with the altimeters. Combined with
your choice of antenna and notebook computer, TeleDongle and our
associated user interface software form a complete ground
station capable of logging and displaying in-flight telemetry,
aiding rocket recovery, then processing and archiving flight
- data for analysis and review.
+ data for analysis and review. The latest version, TeleDongle
+ v3, has all new electronics with a higher performance radio
+ for improved range.
</para>
<para>
For a slightly more portable ground station experience that also
<listitem>
<para>
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.
+ rocket starts accelerating and then decelerating
+ (presumably due to a motor or motors burning). Use this
+ value for multi-staged or multi-airstart launches.
</para>
</listitem>
<listitem>
<listitem>
<para>
The Received Signal Strength Indicator value. This lets
- you know how strong a signal TeleDongle is receiving. The
- radio inside TeleDongle operates down to about -99dBm;
- weaker signals may not be receivable. The packet link uses
+ you know how strong a signal TeleDongle is receiving. At
+ the default data rate, 38400 bps, in bench testing, the
+ radio inside TeleDongle v0.2 operates down to about
+ -106dBm, while the v3 radio works down to about -111dBm.
+ Weaker signals, or an environment with radio noise may
+ cause the data to not be received. The packet link uses
error detection and correction techniques which prevent
incorrect data from being reported.
</para>
<title>Flash Image</title>
<para>
This reprograms Altus Metrum devices with new
- firmware. TeleMetrum v1.x, TeleDongle, TeleMini and TeleBT are
- all reprogrammed by using another similar unit as a
- programming dongle (pair programming). TeleMega, EasyMega, TeleMetrum v2
- and EasyMini are all programmed directly over their USB ports
- (self programming). Please read the directions for flashing
- devices in the Updating Device Firmware chapter below.
+ firmware. TeleMetrum v1.x, TeleDongle v0.2, TeleMini and
+ TeleBT are all reprogrammed by using another similar unit as a
+ programming dongle (pair programming). TeleMega, EasyMega,
+ TeleMetrum v2, EasyMini and TeleDongle v3 are all programmed
+ directly over their USB ports (self programming). Please read
+ the directions for flashing devices in the Updating Device
+ Firmware chapter below.
</para>
</section>
<section>
<para>
Before heading out to a new launch site, you can use this to
load satellite images in case you don't have internet
- connectivity at the site. This loads a fairly large area
- around the launch site, which should cover any flight you're likely to make.
+ connectivity at the site.
</para>
<para>
There's a drop-down menu of launch sites we know about; if
You can specify the range of zoom levels to download; smaller
numbers show more area with less resolution. The default
level, 0, shows about 3m/pixel. One zoom level change
- doubles or halves that number.
+ doubles or halves that number. Larger zoom levels show more
+ detail, smaller zoom levels less.
</para>
<para>
- The Tile Radius value sets how large an area around the center
- point to download. Each tile is 512x512 pixels, and the
- 'radius' value specifies how many tiles away from the center
- will be downloaded. Specify a radius of 0 and you get only the
- center tile. A radius of 1 loads a 3x3 grid, centered on the
- specified location.
+ The Map Radius value sets how large an area around the center
+ point to download. Select a value large enough to cover any
+ plausible flight from that site. Be aware that loading a large
+ area with a high maximum zoom level can attempt to download a
+ lot of data. Loading hybrid maps with a 10km radius at a
+ minimum zoom of -2 and a maximum zoom of 2 consumes about
+ 120MB of space. Terrain and road maps consume about 1/10 as
+ much space as satellite or hybrid maps.
</para>
<para>
Clicking the 'Load Map' button will fetch images from Google
</section>
<section>
<title>Monitor Idle</title>
+ <informalfigure>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="monitor-idle.png" width="5.2in" scalefit="1"/>
+ </imageobject>
+ </mediaobject>
+ </informalfigure>
<para>
This brings up a dialog similar to the Monitor Flight UI,
except it works with the altimeter in “idle” mode by sending
cannot manage to run Monitor Idle, then it's very likely that
your callsigns are different in some way.
</para>
+ <para>
+ You can change the frequency and callsign used to communicate
+ with the flight computer; they must both match the
+ configuration in the flight computer exactly.
+ </para>
</section>
</chapter>
<chapter>
<title>AltosDroid</title>
<para>
AltosDroid provides the same flight monitoring capabilities as
- AltosUI, but runs on Android devices and is designed to connect
- to a TeleBT receiver over Bluetooth™. AltosDroid monitors
+ AltosUI, but runs on Android devices. AltosDroid is designed to connect
+ to a TeleBT receiver over Bluetooth™ and (on Android devices supporting
+ USB On-the-go) TeleDongle and TeleBT devices over USB. AltosDroid monitors
telemetry data, logging it to internal storage in the Android
- device, and presents that data in a UI the same way the 'Monitor
- Flight' window does in AltosUI.
+ device, and presents that data in a UI similar to the 'Monitor
+ Flight' window in AltosUI.
</para>
<para>
- This manual will explain how to configure AltosDroid, connect
- to TeleBT, operate the flight monitoring interface and describe
- what the displayed data means.
+ This manual will explain how to configure AltosDroid, connect to
+ TeleBT or TeleDongle, operate the flight monitoring interface
+ and describe what the displayed data means.
</para>
<section>
<title>Installing AltosDroid</title>
</para>
</section>
<section>
- <title>Connecting to TeleBT</title>
+ <title>Connecting to TeleBT over Bluetooth™</title>
<para>
Press the Android 'Menu' button or soft-key to see the
configuration options available. Select the 'Connect a device'
scanning.
</para>
</section>
+ <section>
+ <title>Connecting to TeleDongle or TeleBT over USB</title>
+ <para>
+ Get a special USB On-the-go adapter cable. These cables have a USB
+ micro-B male connector on one end and a standard A female
+ connector on the other end. Plug in your TeleDongle or TeleBT
+ device to the adapter cable and the adapter cable into your
+ phone and AltosDroid should automatically start up. If it
+ doesn't, the most likely reason is that your Android device
+ doesn't support USB On-the-go.
+ </para>
+ </section>
<section>
<title>Configuring AltosDroid</title>
<para>
- The only configuration option available for AltosDroid is
- which frequency to listen on. Press the Android 'Menu' button
- or soft-key and pick the 'Select radio frequency' entry. That
- brings up a menu of pre-set radio frequencies; pick the one
- which matches your altimeter.
+ There are several configuration and operation parameters
+ available in the AltosDroid menu.
</para>
+ <section>
+ <title>Select radio frequency</title>
+ <para>
+ This selects which frequency to listen on by bringing up a
+ menu of pre-set radio frequencies. Pick the one which matches
+ your altimeter.
+ </para>
+ </section>
+ <section>
+ <title>Select data rate</title>
+ <para>
+ Altus Metrum transmitters can be configured to operate at
+ lower data rates to improve transmission range. If you have
+ configured your device to do this, this menu item allows you
+ to change the receiver to match.
+ </para>
+ </section>
+ <section>
+ <title>Change units</title>
+ <para>
+ This toggles between metric and imperial units.
+ </para>
+ </section>
+ <section>
+ <title>Load maps</title>
+ <para>
+ Brings up a dialog allowing you to download offline map
+ tiles so that you can have maps available even if you have
+ no network connectivity at the launch site.
+ </para>
+ </section>
+ <section>
+ <title>Map type</title>
+ <para>
+ Displays a menu of map types and lets you select one. Hybrid
+ maps include satellite images with a roadmap
+ overlaid. Satellite maps dispense with the roadmap
+ overlay. Roadmap shows just the roads. Terrain includes
+ roads along with shadows indicating changes in elevation,
+ and other geographical features.
+ </para>
+ </section>
+ <section>
+ <title>Toggle Online/Offline maps</title>
+ <para>
+ Switches between online and offline maps. Online maps will
+ show a 'move to current position' icon in the upper right
+ corner, while offline maps will have copyright information
+ all over the map. Otherwise, they're pretty similar.
+ </para>
+ </section>
+ <section>
+ <title>Select Tracker</title>
+ <para>
+ Switches the information displays to show data for a
+ different transmitting device. The map will always show all
+ of the devices in view. Trackers are shown and selected by
+ serial number, so make sure you note the serial number of
+ devices in each airframe.
+ </para>
+ </section>
+ <section>
+ <title>Delete Track</title>
+ <para>
+ Deletes all information about a transmitting device.
+ </para>
+ </section>
</section>
<section>
<title>AltosDroid Flight Monitoring</title>
<section>
<title>Pad</title>
<para>
- The 'Launch Pad' tab shows information used to decide when the
+ The 'Pad' tab shows information used to decide when the
rocket is ready for flight. The first elements include red/green
indicators, if any of these is red, you'll want to evaluate
- whether the rocket is ready to launch:
- <variablelist>
- <varlistentry>
- <term>Battery Voltage</term>
- <listitem>
- <para>
- This indicates whether the Li-Po battery
- powering the TeleMetrum has sufficient charge to last for
- the duration of the flight. A value of more than
- 3.8V is required for a 'GO' status.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Apogee Igniter Voltage</term>
- <listitem>
- <para>
- This indicates whether the apogee
- igniter has continuity. If the igniter has a low
- resistance, then the voltage measured here will be close
- to the Li-Po battery voltage. A value greater than 3.2V is
- required for a 'GO' status.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Main Igniter Voltage</term>
- <listitem>
- <para>
- This indicates whether the main
- igniter has continuity. If the igniter has a low
- resistance, then the voltage measured here will be close
- to the Li-Po battery voltage. A value greater than 3.2V is
- required for a 'GO' status.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>On-board Data Logging</term>
- <listitem>
- <para>
- This indicates whether there is
- space remaining on-board to store flight data for the
- upcoming flight. If you've downloaded data, but failed
- to erase flights, there may not be any space
- left. TeleMetrum can store multiple flights, depending
- on the configured maximum flight log size. TeleMini
- stores only a single flight, so it will need to be
- downloaded and erased after each flight to capture
- data. This only affects on-board flight logging; the
- altimeter will still transmit telemetry and fire
- ejection charges at the proper times.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>GPS Locked</term>
- <listitem>
- <para>
- For a TeleMetrum or TeleMega device, this indicates whether the GPS receiver is
- currently able to compute position information. GPS requires
- at least 4 satellites to compute an accurate position.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>GPS Ready</term>
- <listitem>
- <para>
- For a TeleMetrum or TeleMega device, this indicates whether GPS has reported at least
- 10 consecutive positions without losing lock. This ensures
- that the GPS receiver has reliable reception from the
- satellites.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
+ whether the rocket is ready to launch.
</para>
<para>
- The Launchpad tab also shows the computed launch pad position
- and altitude, averaging many reported positions to improve the
- accuracy of the fix.
+ When the pad tab is selected, the voice responses will
+ include status changes to the igniters and GPS reception,
+ letting you know if the rocket is still ready for launch.
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term>Battery</term>
+ <listitem>
+ <para>
+ This indicates whether the Li-Po battery
+ powering the transmitter has sufficient charge to last for
+ the duration of the flight. A value of more than
+ 3.8V is required for a 'GO' status.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Receiver Battery</term>
+ <listitem>
+ <para>
+ This indicates whether the Li-Po battery
+ powering the TeleBT has sufficient charge to last for
+ the duration of the flight. A value of more than
+ 3.8V is required for a 'GO' status.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Data Logging</term>
+ <listitem>
+ <para>
+ This indicates whether there is space remaining
+ on-board to store flight data for the upcoming
+ flight. If you've downloaded data, but failed to
+ erase flights, there may not be any space
+ left. TeleMetrum and TeleMega can store multiple
+ flights, depending on the configured maximum flight
+ log size. TeleGPS logs data continuously. TeleMini
+ stores only a single flight, so it will need to be
+ downloaded and erased after each flight to capture
+ data. This only affects on-board flight logging; the
+ altimeter will still transmit telemetry and fire
+ ejection charges at the proper times.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>GPS Locked</term>
+ <listitem>
+ <para>
+ For a TeleMetrum or TeleMega device, this indicates whether the GPS receiver is
+ currently able to compute position information. GPS requires
+ at least 4 satellites to compute an accurate position.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>GPS Ready</term>
+ <listitem>
+ <para>
+ For a TeleMetrum or TeleMega device, this indicates whether GPS has reported at least
+ 10 consecutive positions without losing lock. This ensures
+ that the GPS receiver has reliable reception from the
+ satellites.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Apogee Igniter</term>
+ <listitem>
+ <para>
+ This indicates whether the apogee
+ igniter has continuity. If the igniter has a low
+ resistance, then the voltage measured here will be close
+ to the Li-Po battery voltage. A value greater than 3.2V is
+ required for a 'GO' status.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Main Igniter</term>
+ <listitem>
+ <para>
+ This indicates whether the main
+ igniter has continuity. If the igniter has a low
+ resistance, then the voltage measured here will be close
+ to the Li-Po battery voltage. A value greater than 3.2V is
+ required for a 'GO' status.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Igniter A-D</term>
+ <listitem>
+ <para>
+ This indicates whether the indicated additional pyro
+ channel igniter has continuity. If the igniter has a
+ low resistance, then the voltage measured here will
+ be close to the Li-Po battery voltage. A value
+ greater than 3.2V is required for a 'GO' status.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ <para>
+ The Pad tab also shows the location of the Android device.
+ </para>
+ </section>
+ <section>
+ <title>Flight</title>
+ <para>
+ The 'Flight' tab shows information used to evaluate and spot
+ a rocket while in flight. It displays speed and height data
+ to monitor the health of the rocket, along with elevation,
+ range and bearing to help locate the rocket in the sky.
+ </para>
+ <para>
+ While the Flight tab is displayed, the voice announcements
+ will include current speed, height, elevation and bearing
+ information.
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term>Speed</term>
+ <listitem>
+ <para>
+ Shows current vertical speed. During descent, the
+ speed values are averaged over a fairly long time to
+ try and make them steadier.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Height</term>
+ <listitem>
+ <para>
+ Shows the current height above the launch pad.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Max Speed</term>
+ <listitem>
+ <para>
+ Shows the maximum vertical speed seen during the flight.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Max Height</term>
+ <listitem>
+ <para>
+ Shows the maximum height above launch pad.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Elevation</term>
+ <listitem>
+ <para>
+ This is the angle above the horizon from the android
+ devices current position.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Range</term>
+ <listitem>
+ <para>
+ The total distance from the android device to the
+ rocket, including both ground distance and
+ difference in altitude. Use this to gauge how large
+ the rocket is likely to appear in the sky.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Bearing</term>
+ <listitem>
+ <para>
+ This is the aziumuth from true north for the rocket
+ from the android device. Use this in combination
+ with the Elevation value to help locate the rocket
+ in the sky, or at least to help point the antenna in
+ the general direction. This is provided in both
+ degrees and a compass point (like West South
+ West). You'll want to know which direction is true
+ north before launching your rocket.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Ground Distance</term>
+ <listitem>
+ <para>
+ This shows the distance across the ground to the
+ lat/lon where the rocket is located. Use this to
+ estimate what is currently under the rocket.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Latitude/Longitude</term>
+ <listitem>
+ <para>
+ Displays the last known location of the rocket.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Apogee Igniter</term>
+ <listitem>
+ <para>
+ This indicates whether the apogee
+ igniter has continuity. If the igniter has a low
+ resistance, then the voltage measured here will be close
+ to the Li-Po battery voltage. A value greater than 3.2V is
+ required for a 'GO' status.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Main Igniter</term>
+ <listitem>
+ <para>
+ This indicates whether the main
+ igniter has continuity. If the igniter has a low
+ resistance, then the voltage measured here will be close
+ to the Li-Po battery voltage. A value greater than 3.2V is
+ required for a 'GO' status.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </section>
+ <section>
+ <title>Recover</title>
+ <para>
+ The 'Recover' tab shows information used while recovering the
+ rocket on the ground after flight.
+ </para>
+ <para>
+ While the Recover tab is displayed, the voice announcements
+ will include distance along with either bearing or
+ direction, depending on whether you are moving.
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term>Bearing</term>
+ <listitem>
+ <para>
+ This is the aziumuth from true north for the rocket
+ from the android device. Use this in combination
+ with the Elevation value to help locate the rocket
+ in the sky, or at least to help point the antenna in
+ the general direction. This is provided in both
+ degrees and a compass point (like West South
+ West). You'll want to know which direction is true
+ north before launching your rocket.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Direction</term>
+ <listitem>
+ <para>
+ When you are in motion, this provides the angle from
+ your current direction of motion towards the rocket.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Distance</term>
+ <listitem>
+ <para>
+ Distance over the ground to the rocket.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Tar Lat/Tar Lon</term>
+ <listitem>
+ <para>
+ Displays the last known location of the rocket.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>My Lat/My Lon</term>
+ <listitem>
+ <para>
+ Displays the location of the Android device.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Max Height</term>
+ <listitem>
+ <para>
+ Shows the maximum height above launch pad.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Max Speed</term>
+ <listitem>
+ <para>
+ Shows the maximum vertical speed seen during the flight.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Max Accel</term>
+ <listitem>
+ <para>
+ Shows the maximum vertical acceleration seen during the flight.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </section>
+ <section>
+ <title>Map</title>
+ <para>
+ The 'Map' tab shows a map of the area around the rocket
+ being tracked along with information needed to recover it.
+ </para>
+ <para>
+ On the map itself, icons showing the location of the android
+ device along with the last known location of each tracker. A
+ blue line is drawn from the android device location to the
+ currently selected tracker.
+ </para>
+ <para>
+ Below the map, the distance and either bearing or direction
+ along with the lat/lon of the target and the android device
+ are shown
+ </para>
+ <para>
+ The Map tab provides the same voice announcements as the
+ Recover tab.
</para>
</section>
</section>
<para>
AltosDroid always saves every bit of telemetry data it
receives. To download that to a computer for use with AltosUI,
- simply remove the SD card from your Android device, or connect
- your device to your computer's USB port and browse the files
- on that device. You will find '.telem' files in the TeleMetrum
+ remove the SD card from your Android device, or connect your
+ device to your computer's USB port and browse the files on
+ that device. You will find '.telem' files in the TeleMetrum
directory that will work with AltosUI directly.
</para>
</section>
<chapter>
<title>Updating Device Firmware</title>
<para>
- TeleMega, TeleMetrum v2, EasyMega and EasyMini are all programmed directly
- over their USB connectors (self programming). TeleMetrum v1, TeleMini and
- TeleDongle are all programmed by using another device as a
- programmer (pair programming). It's important to recognize which
- kind of devices you have before trying to reprogram them.
+ TeleMega, TeleMetrum v2, EasyMega, EasyMini and TeleDongle v3
+ are all programmed directly over their USB connectors (self
+ programming). TeleMetrum v1, TeleMini and TeleDongle v0.2 are
+ all programmed by using another device as a programmer (pair
+ programming). It's important to recognize which kind of devices
+ you have before trying to reprogram them.
</para>
<para>
You may wish to begin by ensuring you have current firmware images.
version from <ulink url="http://www.altusmetrum.org/AltOS/"/>.
</para>
<para>
- If you need to update the firmware on a TeleDongle, we recommend
+ If you need to update the firmware on a TeleDongle v0.2, we recommend
updating the altimeter first, before updating TeleDongle. However,
note that TeleDongle rarely need to be updated. Any firmware version
1.0.1 or later will work, version 1.2.1 may have improved receiver
</para>
<section>
<title>
- Updating TeleMega, TeleMetrum v2, EasyMega or EasyMini Firmware
+ Updating TeleMega, TeleMetrum v2, EasyMega, EasyMini or
+ TeleDongle v3 Firmware
</title>
<orderedlist inheritnum='inherit' numeration='arabic'>
<listitem>
<para>
- Attach a battery and power switch to the target
+ Attach a battery if necessary and power switch to the target
device. Power up the device.
</para>
</listitem>
<listitem>
<para>
Verify that the device is working by using the 'Configure
- Altimeter' item to check over the configuration.
+ Altimeter' or 'Configure Groundstation' item to check over
+ the configuration.
</para>
</listitem>
</orderedlist>
</para>
</listitem>
</varlistentry>
+ <varlistentry>
+ <term>TeleDongle v3</term>
+ <listitem>
+ <para>
+ Connect pin 32 on the CPU to ground. Pin 32 is closest
+ to the USB wires on the row of pins towards the center
+ of the board. Ground is available on the capacitor
+ next to it, on the end towards the USB wires.
+ </para>
+ </listitem>
+ </varlistentry>
</variablelist>
<para>
Once you've located the right pins:
<title>Pair Programming</title>
<para>
The big concept to understand is that you have to use a
- TeleMega, TeleMetrum or TeleDongle as a programmer to update a
- pair programmed device. Due to limited memory resources in the
- cc1111, we don't support programming directly over USB for these
- devices.
+ TeleMetrum v1.0, TeleBT v1.0 or TeleDongle v0.2 as a
+ programmer to update a pair programmed device. Due to limited
+ memory resources in the cc1111, we don't support programming
+ directly over USB for these devices.
</para>
</section>
<section>
</listitem>
<listitem>
<para>
- Take the 2 screws out of the TeleDongle case to get access
- to the circuit board.
+ Take the 2 screws out of the TeleDongle v0.2 or TeleBT v1.0
+ case to get access to the circuit board.
</para>
</listitem>
<listitem>
<para>
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 TeleDongle v0.2 or TeleBT v1.0, 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
</listitem>
<listitem>
<para>
- Plug the TeleDongle into your computer's USB port, and power
+ Plug the TeleDongle v0.2 or TeleBT v1.0 into your computer's USB port, and power
up the TeleMetrum.
</para>
</listitem>
</listitem>
<listitem>
<para>
- Pick the TeleDongle device from the list, identifying it as the
+ Pick the TeleDongle v0.2 or TeleBT v1.0 device from the list, identifying it as the
programming device.
</para>
</listitem>
</listitem>
<listitem>
<para>
- Take the 2 screws out of the TeleDongle case to get access
+ Take the 2 screws out of the TeleDongle v0.2 or TeleBT v1.0 case to get access
to the circuit board.
</para>
</listitem>
<listitem>
<para>
Plug the 8-pin end of the programming cable to the matching
- connector on the TeleDongle, and the 4-pins into the holes
+ connector on the TeleDongle v0.2 or TeleBT v1.0, 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
</listitem>
<listitem>
<para>
- Plug the TeleDongle into your computer's USB port, and power
+ Plug the TeleDongle v0.2 or TeleBT v1.0 into your computer's USB port, and power
up the TeleMini
</para>
</listitem>
</listitem>
<listitem>
<para>
- Pick the TeleDongle device from the list, identifying it as the
+ Pick the TeleDongle v0.2 or TeleBT v1.0 device from the list, identifying it as the
programming device.
</para>
</listitem>
</orderedlist>
</section>
<section>
- <title>Updating TeleDongle Firmware</title>
+ <title>Updating TeleDongle v0.2 Firmware</title>
<para>
- Updating TeleDongle's firmware is just like updating TeleMetrum or TeleMini
- firmware, but you use either a TeleMetrum or another TeleDongle as the programmer.
+ Updating TeleDongle v0.2 firmware is just like updating
+ TeleMetrum v1.x or TeleMini
+ firmware, but you use either a TeleMetrum v1.x, TeleDongle
+ v0.2 or TeleBT v1.0 as the programmer.
</para>
<orderedlist inheritnum='inherit' numeration='arabic'>
<listitem>
<listitem>
<para>
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
+ v1.x, TeleDongle v0.2 or TeleBT v1.0.
</para>
</listitem>
<listitem>
<para>
- Take the 2 screws out of the TeleDongle case to get access
+ Take the 2 screws out of the TeleDongle v0.2 or TeleBT v1.0 case to get access
to the circuit board.
</para>
</listitem>
<para>
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.
+ matching connector on the TeleDongle v0.2.
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.
</listitem>
<listitem>
<para>
- Attach a battery to the TeleMetrum board if you're using one.
+ Attach a battery to the TeleMetrum v1.x board if you're using one.
</para>
</listitem>
<listitem>
</listitem>
<listitem>
<para>
- Select the image you want put on the TeleDongle, which should have a
+ Select the image you want put on the TeleDongle v0.2, 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.
<para>
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
+ values aren't right, you'll need to change them. The
+ TeleDongle v0.2
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.
<listitem>
<para>
Hit the 'OK' button and the software should proceed to flash
- the TeleDongle with new firmware, showing a progress bar.
+ the TeleDongle v0.2 with new firmware, showing a progress bar.
</para>
</listitem>
<listitem>
<para>
- Confirm that the TeleDongle board seems to have updated OK, which you
+ Confirm that the TeleDongle v0.2 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.
+ and put the cover back on the TeleDongle v0.2.
</para>
</listitem>
<listitem>
</para>
</section>
</appendix>
+ <appendix>
+ <title>Igniter Current</title>
+ <para>
+ The question "how much igniter current can Altus Metrum products
+ handle?" comes up fairly frequently. The short answer is "more than
+ you're likely to need", the remainder of this appendix provides a
+ longer answer.
+ </para>
+ <section>
+ <title>Current Products</title>
+ <para>
+ The FET switches we're using on all of our current products that
+ have pyro channels are the Vishay Siliconix Si7232DN. These parts
+ have exceptionally low Rds(on) values, better than 0.02 ohms! That
+ means they aren't making a lot of heat... and the limit on current
+ is "package limited", meaning it's all about how much you can heat
+ the die before something breaks.
+ </para>
+ <para>
+ Cutting to the chase, the Si7232DN specs are 25 amps <emphasis>continuous</emphasis> at
+ 20V at a temperature of 25C. In pulsed mode, they're rated for 40A.
+ However, those specs are a little mis-leading because it really is
+ all about the heat generated... you can get something like 85A
+ through one briefly. Note that a typical commercial e-match only
+ needed about 13 microseconds to fire in tests on my bench a couple
+ years ago!
+ </para>
+ <para>
+ So a great plan is to use something like an e-match as the initiator
+ and build up pyrogen(s) as required to actually light what you're
+ trying to light... But if you want to use a high-current igniter,
+ we can probably handle it!
+ </para>
+ </section>
+ <section>
+ <title>Version 1 Products</title>
+ <para>
+ The FET switches used on TeleMetrum v1 and TeleMini v1 products
+ were Fairchild FDS9926A. The Rds(on) values under our operating
+ conditions are on the order of 0.04 ohms. These parts were rated
+ for a continuous current-carrying capacity of 6.5A, and a pulsed
+ current capacity of 20A.
+ </para>
+ <para>
+ As with the more modern parts, the real limit is based on the heat
+ generated in the part during the firing interval. So, while the
+ specs on these parts aren't as good as the ones we use on current
+ products, they were still great, and we never had a complaint about
+ current carrying capacity with any of our v1 boards.
+ </para>
+ </section>
+ </appendix>
<appendix>
<title>Release Notes</title>
<simplesect>
- <title>Version 1.4.1</title>
+ <title>Version 1.6.1</title>
<xi:include
xmlns:xi="http://www.w3.org/2001/XInclude"
- href="release-notes-1.4.1.xsl"
+ href="release-notes-1.6.1.xsl"
+ xpointer="xpointer(/article/*)"/>
+ </simplesect>
+ <simplesect>
+ <title>Version 1.6</title>
+ <xi:include
+ xmlns:xi="http://www.w3.org/2001/XInclude"
+ href="release-notes-1.6.xsl"
xpointer="xpointer(/article/*)"/>
</simplesect>
<simplesect>
href="release-notes-1.5.xsl"
xpointer="xpointer(/article/*)"/>
</simplesect>
+ <simplesect>
+ <title>Version 1.4.1</title>
+ <xi:include
+ xmlns:xi="http://www.w3.org/2001/XInclude"
+ href="release-notes-1.4.1.xsl"
+ xpointer="xpointer(/article/*)"/>
+ </simplesect>
<simplesect>
<title>Version 1.4</title>
<xi:include
projects / fw / altos / blobdiff