| Neither | brap |
No continuity detected on either apogee or main
igniters.
@@ -566,7 +569,7 @@ NAR
together, then power TeleMini up. Once the red LED is lit,
disconnect the wire and the board should signal that it's in
'idle' mode after the initial five second startup period.
-
TeleMetrum and TeleMega include a complete GPS receiver. A
complete explanation of how GPS works is beyond the scope of
this manual, but the bottom line is that the GPS receiver
@@ -584,7 +587,7 @@ NAR
is turned back on, the GPS system should lock very quickly, typically
long before igniter installation and return to the flight line are
complete.
- 3. Controlling An Altimeter Over The Radio Link
+ 3. Controlling An Altimeter Over The Radio Link
One of the unique features of the Altus Metrum system is the
ability to create a two way command link between TeleDongle
and an altimeter using the digital radio transceivers
@@ -655,7 +658,7 @@ NAR
lights on the devices. The red LED will flash each time a packet
is transmitted, while the green LED will light up on TeleDongle when
it is waiting to receive a packet from the altimeter.
-
An important aspect of preparing a rocket using electronic deployment
for flight is ground testing the recovery system. Thanks
to the bi-directional radio link central to the Altus Metrum system,
@@ -671,7 +674,7 @@ NAR
manual command. You can now command the altimeter to fire the apogee
or main charges from a safe distance using your computer and
TeleDongle and the Fire Igniter tab to complete ejection testing.
-
Our flight computers all incorporate an RF transceiver, but
it's not a full duplex system... each end can only be transmitting or
receiving at any given moment. So we had to decide how to manage the
@@ -710,13 +713,13 @@ NAR
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.
- 6. Configurable Parameters
+ 6. Configurable Parameters
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
configurable parameters can all be set using AltosUI over USB or
or radio link via TeleDongle.
-
+
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
@@ -726,7 +729,7 @@ NAR
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.
-
Apogee delay is the number of seconds after the altimeter detects flight
apogee that the drogue charge should be fired. In most cases, this
should be left at the default of 0. However, if you are flying
@@ -742,7 +745,7 @@ NAR
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.
- 6.3. Main Deployment Altitude
+ 6.3. Main Deployment Altitude
By default, the altimeter will fire the main deployment charge at an
elevation of 250 meters (about 820 feet) above ground. We think this
is a good elevation for most air-frames, but feel free to change this
@@ -751,7 +754,7 @@ NAR
deployment elevation for the backup altimeter to be something lower
than the primary so that both pyrotechnic charges don't fire
simultaneously.
-
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
@@ -763,7 +766,7 @@ NAR
Even though our flight computers (except TeleMini v1.0) can store
multiple flights, we strongly recommend downloading and saving
flight data after each flight.
-
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
@@ -774,7 +777,7 @@ NAR
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.
-
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
@@ -784,7 +787,7 @@ NAR
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.
- 6.7. Configurable Pyro Channels
+ 6.7. Configurable 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
@@ -884,7 +887,7 @@ NAR
Coast state (depending on how fast it is moving). If the
computer detects upwards acceleration again, it will
move back to Boost state.
-
The AltosUI program provides a graphical user interface for
interacting with the Altus Metrum product family. AltosUI can
monitor telemetry data, configure devices and many other
@@ -892,12 +895,12 @@ NAR
buttons, one for each major activity in the system. This chapter
is split into sections, each of which documents one of the tasks
provided from the top-level toolbar.
- Receive, Record and Display Telemetry Data
+ Receive, Record and Display Telemetry Data
Selecting this item brings up a dialog box listing all of the
connected TeleDongle devices. When you choose one of these,
AltosUI will create a window to display telemetry data as
received by the selected TeleDongle device.
-
+
All telemetry data received are automatically recorded in
suitable log files. The name of the files includes the current
date and rocket serial and flight numbers.
@@ -939,7 +942,7 @@ NAR
data relevant to the current state of the flight. You can select
other tabs at any time. The final 'table' tab displays all of
the raw telemetry values in one place in a spreadsheet-like format.
-
+
The 'Launch 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
@@ -989,15 +992,15 @@ NAR
The Launchpad tab also shows the computed launch pad position
and altitude, averaging many reported positions to improve the
accuracy of the fix.
-
This tab is shown during Boost, Fast and Coast
phases. The information displayed here helps monitor the
rocket as it heads towards apogee.
- The height, speed and acceleration are shown along with the
- maximum values for each of them. This allows you to quickly
- answer the most commonly asked questions you'll hear during
- flight.
+ The height, speed, acceleration and tilt are shown along
+ with the maximum values for each of them. This allows you to
+ quickly answer the most commonly asked questions you'll hear
+ during flight.
The current latitude and longitude reported by the GPS are
also shown. Note that under high acceleration, these values
@@ -1008,7 +1011,7 @@ NAR
Finally, the current igniter voltages are reported as in the
Launch Pad tab. This can help diagnose deployment failures
caused by wiring which comes loose under high acceleration.
-
Once the rocket has reached apogee and (we hope) activated the
apogee charge, attention switches to tracking the rocket on
the way back to the ground, and for dual-deploy flights,
@@ -1037,7 +1040,7 @@ NAR
e-matches are designed to retain continuity even after being
fired, and will continue to show as green or return from red to
green after firing.
-
Once the rocket is on the ground, attention switches to
recovery. While the radio signal is often lost once the
rocket is on the ground, the last reported GPS position is
@@ -1066,13 +1069,13 @@ NAR
To get more detailed information about the flight, you can
click on the 'Graph Flight' button which will bring up a
graph window for the current flight.
-
The table view shows all of the data available from the
flight computer. Probably the most useful data on
this tab is the detailed GPS information, which includes
horizontal dilution of precision information, and
information about the signal being received from the satellites.
-
When the TeleMetrum has a GPS fix, the Site Map tab will map
the rocket's position to make it easier for you to locate the
rocket, both while it is in the air, and when it has landed. The
@@ -1091,7 +1094,7 @@ NAR
You can pre-load images for your favorite launch sites
before you leave home; check out the 'Preload Maps' section below.
-
The altimeter records flight data to its internal flash memory.
TeleMetrum data is recorded at a much higher rate than the telemetry
system can handle, and is not subject to radio drop-outs. As
@@ -1120,7 +1123,7 @@ NAR
The file name for each flight log is computed automatically
from the recorded flight date, altimeter serial number and
flight number information.
-
Select this button and you are prompted to select a flight
record file, either a .telem file recording telemetry data or a
.eeprom file containing flight data saved from the altimeter
@@ -1129,7 +1132,7 @@ NAR
Once a flight record is selected, the flight monitor interface
is displayed and the flight is re-enacted in real time. Check
the Monitor Flight chapter above to learn how this window operates.
-
Select this button and you are prompted to select a flight
record file, either a .telem file recording telemetry data or a
.eeprom file containing flight data saved from
@@ -1141,7 +1144,7 @@ NAR
Once a flight record is selected, a window with multiple tabs is
opened.
-
+
By default, the graph contains acceleration (blue),
velocity (green) and altitude (red).
@@ -1151,18 +1154,18 @@ NAR
control and clicking and dragging allows the graph to be panned.
The right mouse button causes a pop-up menu to be displayed, giving
you the option save or print the plot.
-
This selects which graph elements to show, and, at the
very bottom, lets you switch between metric and
imperial units
-
Shows overall data computed from the flight.
-
Shows a satellite image of the flight area overlaid
with the path of the flight. The red concentric
circles mark the launch pad, the black concentric
circles mark the landing location.
-
This tool takes the raw data files and makes them available for
external analysis. When you select this button, you are prompted to
select a flight data file, which can be either a .eeprom or .telem.
@@ -1171,7 +1174,7 @@ NAR
Next, a second dialog appears which is used to select
where to write the resulting file. It has a selector to choose
between CSV and KML file formats.
- 5.1. Comma Separated Value Format
+ 5.1. Comma Separated Value Format
This is a text file containing the data in a form suitable for
import into a spreadsheet or other external data analysis
tool. The first few lines of the file contain the version and
@@ -1185,11 +1188,11 @@ NAR
the sensor values are converted to standard units, with the
barometric data reported in both pressure, altitude and
height above pad units.
- 5.2. Keyhole Markup Language (for Google Earth)
+ 5.2. Keyhole Markup Language (for Google Earth)
This is the format used by Google Earth to provide an overlay
within that application. With this, you can use Google Earth to
see the whole flight path in 3D.
-
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.
@@ -1217,14 +1220,14 @@ NAR
lost.
The rest of the dialog contains the parameters to be configured.
- 6.1. Main Deploy Altitude
+ 6.1. Main Deploy Altitude
This sets the altitude (above the recorded pad altitude) at
which the 'main' igniter will fire. The drop-down menu shows
some common values, but you can edit the text directly and
choose whatever you like. If the apogee charge fires below
this altitude, then the main charge will fire two seconds
after the apogee charge fires.
-
When flying redundant electronics, it's often important to
ensure that multiple apogee charges don't fire at precisely
the same time, as that can over pressurize the apogee deployment
@@ -1232,13 +1235,13 @@ NAR
Delay parameter tells the flight computer to fire the apogee
charge a certain number of seconds after apogee has been
detected.
-
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, the TeleDongle frequency will
also be automatically reconfigured to match so that
communication will continue afterwards.
-
The radios in every Altus Metrum device are calibrated at the
factory to ensure that they transmit and receive on the
specified frequency. If you need to you can adjust the calibration
@@ -1246,26 +1249,26 @@ NAR
the value means, read the appendix on calibration and/or the source
code for more information. To change a TeleDongle's calibration,
you must reprogram the unit completely.
- 6.5. Telemetry/RDF/APRS Enable
+ 6.5. Telemetry/RDF/APRS Enable
Enables the radio for transmission during flight. When
disabled, the radio will not transmit anything during flight
at all.
-
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.
-
This sets the call sign included in each telemetry packet. Set this
as needed to conform to your local radio regulations.
- 6.8. Maximum Flight Log Size
+ 6.8. Maximum Flight Log Size
This sets the space (in kilobytes) allocated for each flight
log. The available space will be divided into chunks of this
size. A smaller value will allow more flights to be stored,
a larger value will record data from longer flights.
-
TeleMetrum and TeleMini provide two igniter channels as they
were originally designed as dual-deploy flight
computers. This configuration parameter allows the two
@@ -1285,7 +1288,7 @@ NAR
Altitude setting during descent. The 'apogee'
channel is fired first, followed after a two second
delay by the 'main' channel.
-
Because they include accelerometers, TeleMetrum and
TeleMega are sensitive to the orientation of the board. By
default, they expect the antenna end to point forward. This
@@ -1299,7 +1302,7 @@ NAR
In this mode, the antenna end of the
flight computer must point aft, in line with the
expected flight path.
- 6.11. Configure Pyro Channels
+ 6.11. 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
@@ -1319,9 +1322,9 @@ NAR
configuration along with the rest of the flight computer
configuration by pressing the 'Save' button in the main
Configure Flight Computer window.
-
This button presents a dialog so that you can configure the AltosUI global settings.
-
+
AltosUI provides voice announcements during flight so that you
can keep your eyes on the sky and still get information about
the current flight status. However, sometimes you don't want
@@ -1330,7 +1333,7 @@ NAR
Plays a short message allowing you to verify
that the audio system is working and the volume settings
are reasonable
-
AltosUI logs all telemetry data and saves all TeleMetrum flash
data to this directory. This directory is also used as the
staring point when selecting data files for display or export.
@@ -1338,7 +1341,7 @@ NAR
Click on the directory name to bring up a directory choosing
dialog, select a new directory and click 'Select Directory' to
change where AltosUI reads and writes data files.
-
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
@@ -1351,30 +1354,30 @@ NAR
the callsign configured here must exactly match the callsign
configured in the flight computer. This matching is case
sensitive.
-
This switches between metric units (meters) and imperial
units (feet and miles). This affects the display of values
use during flight monitoring, configuration, data graphing
and all of the voice announcements. It does not change the
units used when exporting to CSV files, those are always
produced in metric units.
-
Selects the set of fonts used in the flight monitor
window. Choose between the small, medium and large sets.
-
This causes all communication with a connected device to be
dumped to the console from which AltosUI was started. If
you've started it from an icon or menu entry, the output
will simply be discarded. This mode can be useful to debug
various serial communication issues.
-
This brings up a dialog where you can configure the set of
frequencies shown in the various frequency menus. You can
add as many as you like, or even reconfigure the default
set. Changing this list does not affect the frequency
settings of any devices, it only changes the set of
frequencies shown in the menus.
- 8. Configure Groundstation
+ 8. Configure Groundstation
Select this button and then select a TeleDongle Device from the list provided.
The first few lines of the dialog provide information about the
@@ -1401,20 +1404,20 @@ NAR
lost.
The rest of the dialog contains the parameters to be configured.
-
+
This configures the frequency to use for both telemetry and
packet command mode. Set this before starting any operation
involving packet command mode so that it will use the right
frequency. Telemetry monitoring mode also provides a menu to
change the frequency, and that menu also sets the same Java
preference value used here.
-
The radios in every Altus Metrum device are calibrated at the
factory to ensure that they transmit and receive on the
specified frequency. To change a TeleDongle's calibration,
you must reprogram the unit completely, so this entry simply
shows the current value and doesn't allow any changes.
-
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
@@ -1422,7 +1425,7 @@ NAR
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.
-
This activates the igniter circuits in the flight computer to help
test recovery systems deployment. Because this command can operate
over the Packet Command Link, you can prepare the rocket as
@@ -1431,8 +1434,8 @@ NAR
Selecting the 'Fire Igniter' button brings up the usual device
selection dialog. Pick the desired device. This brings up another
- window which shows the current continuity test status for both
- apogee and main charges.
+ window which shows the current continuity test status for all
+ of the pyro channels.
Next, select the desired igniter to fire. This will enable the
'Arm' button.
@@ -1442,14 +1445,14 @@ NAR
you have 10 seconds to press the 'Fire' button or the system
will deactivate, at which point you start over again at
selecting the desired igniter.
-
This listens for telemetry packets on all of the configured
frequencies, displaying information about each device it
receives a packet from. You can select which of the three
telemetry formats should be tried; by default, it only listens
for the standard telemetry packets used in v1.0 and later
firmware.
-
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
@@ -1468,7 +1471,7 @@ NAR
once, so if you load more than one launch site, you may get
some gray areas in the map which indicate that Google is tired
of sending data to you. Try again later.
-
This brings up a dialog similar to the Monitor Flight UI,
except it works with the altimeter in “idle” mode by sending
query commands to discover the current state rather than
@@ -1477,7 +1480,7 @@ NAR
callsigns match exactly. If you can receive telemetry, but
cannot manage to run Monitor Idle, then it's very likely that
your callsigns are different in some way.
-
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
@@ -1488,14 +1491,14 @@ NAR
This manual will explain how to configure AltosDroid, connect
to TeleBT, operate the flight monitoring interface and describe
what the displayed data means.
-
+
AltosDroid is available from the Google Play store. To install
it on your Android device, 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
find what you want. That should bring you to the right page
from which you can download and install the application.
-
Press the Android 'Menu' button or soft-key to see the
configuration options available. Select the 'Connect a device'
option and then the 'Scan for devices' entry at the bottom to
@@ -1505,19 +1508,19 @@ NAR
Subsequent connections will not require you to enter that
code, and your 'paired' device will appear in the list without
scanning.
- 3. Configuring AltosDroid
+ 3. Configuring AltosDroid
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.
- 4. AltosDroid Flight Monitoring
+ 4. AltosDroid Flight Monitoring
AltosDroid is designed to mimic the AltosUI flight monitoring
display, providing separate tabs for each stage of your rocket
flight along with a tab containing a map of the local area
with icons marking the current location of the altimeter and
the Android device.
-
+
The 'Launch 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
@@ -1565,18 +1568,18 @@ NAR
The Launchpad tab also shows the computed launch pad position
and altitude, averaging many reported positions to improve the
accuracy of the fix.
- 5. Downloading Flight Logs
+ 5. Downloading Flight Logs
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
directory that will work with AltosUI directly.
- Chapter 8. Using Altus Metrum ProductsChapter 8. Using Altus Metrum Products
First off, in the US, you need an amateur radio license or
other authorization to legally operate the radio transmitters that are part
of our products.
-
In the rocket itself, you just need a flight computer and
a single-cell, 3.7 volt nominal Li-Po rechargeable battery. An
850mAh battery weighs less than a 9V alkaline battery, and will
@@ -1592,7 +1595,7 @@ NAR
GPS antenna is fixed on all current products, so you really want
to install the flight computer in a bay made of RF-transparent
materials if at all possible.
-
To receive the data stream from the rocket, you need an antenna and short
feed-line connected to one of our TeleDongle units. If possible, use an SMA to BNC
adapter instead of feedline between the antenna feedpoint and
@@ -1654,7 +1657,7 @@ NAR
TeleMetrum- or TeleMini- equipped rocket when used with a suitable
70cm HT. TeleDongle and an SMA to BNC adapter fit perfectly
between the driven element and reflector of Arrow antennas.
-
Our software makes it easy to log the data from each flight, both the
telemetry received during the flight itself, and the more
complete data log recorded in the flash memory on the altimeter
@@ -1669,7 +1672,7 @@ NAR
Our ultimate goal is to emit a set of files for each flight that can be
published as a web page per flight, or just viewed on your local disk with
a web browser.
-
We've designed a simple GPS based radio tracker called TeleGPS.
If all goes well, we hope to introduce this in the first
half of 2014.
@@ -1692,14 +1695,14 @@ NAR
Watch our
web site for more news
and information as our family of products evolves!
- Chapter 9. Altimeter Installation Recommendations
+ Chapter 9. Altimeter Installation Recommendations
Building high-power rockets that fly safely is hard enough. Mix
in some sophisticated electronics and a bunch of radio energy
and some creativity and/or compromise may be required. This chapter
contains some suggestions about how to install Altus Metrum
products into a rocket air-frame, including how to safely and
reliably mix a variety of electronics into the same air-frame.
- 1. Mounting the Altimeter
+ 1. Mounting the Altimeter
The first consideration is to ensure that the altimeter is
securely fastened to the air-frame. For most of our products, we
prefer nylon standoffs and nylon screws; they're good to at least 50G
@@ -1719,7 +1722,7 @@ NAR
Watch for any metal touching components on the
board. Shorting out connections on the bottom of the board
can cause the altimeter to fail during flight.
- 2. Dealing with the Antenna
+ 2. Dealing with the Antenna
The antenna supplied is just a piece of solid, insulated,
wire. If it gets damaged or broken, it can be easily
replaced. It should be kept straight and not cut; bending or
@@ -1762,7 +1765,7 @@ NAR
SMA connector, and then run 50Ω coax from the board to the
antenna. Building a remote antenna is beyond the scope of this
manual.
- 3. Preserving GPS Reception
+ 3. Preserving GPS Reception
The GPS antenna and receiver used in TeleMetrum and TeleMega is
highly sensitive and normally have no trouble tracking enough
satellites to provide accurate position information for
@@ -1781,7 +1784,7 @@ NAR
antenna as that's covered with a ground plane. But, keep
wires and metal out from above the patch antenna.
- 4. Radio Frequency Interference
+ 4. Radio Frequency Interference
Any altimeter will generate RFI; the digital circuits use
high-frequency clocks that spray radio interference across a
wide band. Altus Metrum altimeters generate intentional radio
@@ -1819,7 +1822,7 @@ NAR
70cm amateur band, so you should avoid lengths that are a
simple ratio of that length; essentially any multiple of ¼
of the wavelength (17.5cm).
-
Altusmetrum altimeters measure altitude with a barometric
sensor, essentially measuring the amount of air above the
rocket to figure out how high it is. A large number of
@@ -1837,7 +1840,7 @@ NAR
the products of APCP or BP combustion, so make sure the ebay is
carefully sealed from any compartment which contains ejection
charges or motors.
-
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
@@ -1859,9 +1862,9 @@ NAR
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.
- Chapter 10. Updating Device Firmware
TeleMega, TeleMetrum v2 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
@@ -1884,7 +1887,7 @@ NAR
Self-programmable devices (TeleMega, TeleMetrum v2 and EasyMini)
are reprogrammed by connecting them to your computer over USB
- 1.
+ 1.
Updating TeleMega, TeleMetrum v2 or EasyMini Firmware
Attach a battery and power switch to the target
@@ -1911,7 +1914,7 @@ NAR
Verify that the device is working by using the 'Configure
Altimeter' item to check over the configuration.
-
1.1. Recovering From Self-Flashing Failure
+ 1.1. Recovering From Self-Flashing Failure
If the firmware loading fails, it can leave the device
unable to boot. Not to worry, you can force the device to
start the boot loader instead, which will let you try to
@@ -1942,13 +1945,13 @@ NAR
by the square pad around it, and then the pins could
sequentially across the board, making Pin 6 the one on the
other end of the row.
-
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.
- 3. Updating TeleMetrum v1.x Firmware3. Updating TeleMetrum v1.x 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.
@@ -1991,7 +1994,7 @@ NAR
the version, etc.
If something goes wrong, give it another try.
-
4. Updating TeleMini Firmware4. Updating TeleMini Firmware
You'll need a special 'programming cable' to reprogram the
TeleMini. You can make your own using an 8-pin MicroMaTch
connector on one end and a set of four pins on the other.
@@ -2034,7 +2037,7 @@ NAR
letting it come up in “flight” mode and listening for telemetry.
If something goes wrong, give it another try.
-
5. Updating TeleDongle Firmware
+ 5. 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.
@@ -2094,17 +2097,17 @@ NAR
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.
-
Chapter 11. Hardware SpecificationsChapter 11. Hardware Specifications1.
TeleMega Specifications
Recording altimeter for model rocketry.
@@ -2134,7 +2137,7 @@ NAR
to fire e-matches.
3.25 x 1.25 inch board designed to fit inside 38mm air-frame coupler tube.
-
2.
TeleMetrum v2 Specifications
Recording altimeter for model rocketry.
@@ -2160,7 +2163,7 @@ NAR
optional separate pyro battery if needed.
2.75 x 1 inch board designed to fit inside 29mm air-frame coupler tube.
-
3. TeleMetrum v1 Specifications3. TeleMetrum v1 Specifications
Recording altimeter for model rocketry.
Supports dual deployment (can fire 2 ejection charges).
@@ -2184,7 +2187,7 @@ NAR
optional separate pyro battery if needed.
2.75 x 1 inch board designed to fit inside 29mm air-frame coupler tube.
-
4.
TeleMini v2.0 Specifications
Recording altimeter for model rocketry.
@@ -2206,7 +2209,7 @@ NAR
optional separate pyro battery if needed.
1.5 x .8 inch board designed to fit inside 24mm air-frame coupler tube.
-
5.
TeleMini v1.0 Specifications
Recording altimeter for model rocketry.
@@ -2227,7 +2230,7 @@ NAR
optional separate pyro battery if needed.
1.5 x .5 inch board designed to fit inside 18mm air-frame coupler tube.
-
6.
EasyMini Specifications
Recording altimeter for model rocketry.
@@ -2247,7 +2250,7 @@ NAR
optional separate pyro battery if needed.
1.5 x .8 inch board designed to fit inside 24mm air-frame coupler tube.
-
TeleMetrum seems to shut off when disconnected from the
computer.
Make sure the battery is adequately charged. Remember the
@@ -2292,7 +2295,7 @@ NAR
data after physically retrieving your altimeter. Make sure to save
the on-board data after each flight; while the TeleMetrum can store
multiple flights, you never know when you'll lose the altimeter...
- Appendix A. Notes for Older Software
+ Appendix A. Notes for Older Software
Before AltosUI was written, using Altus Metrum devices required
some finesse with the Linux command line. There was a limited
@@ -2385,11 +2388,12 @@ NAR
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'
+ is 1186611 for cc1111 based products and 7119667 for cc1120
+ based products. 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.
+ change to the configuration memory.
Note that the 'reboot' command, which is very useful on the altimeters,
will likely just cause problems with the dongle. The *correct* way
@@ -2468,22 +2472,22 @@ NAR
the Log and Device menus. It has a wonderful display of the incoming
flight data and I am sure you will enjoy what it has to say to you
once you enable the voice output!
- Appendix B. Drill Templates
+ Appendix B. Drill Templates
These images, when printed, provide precise templates for the
mounting holes in Altus Metrum flight computers
-
+
TeleMega has overall dimensions of 1.250 x 3.250 inches, and
the mounting holes are sized for use with 4-40 or M3 screws.
-
TeleMetrum has overall dimensions of 1.000 x 2.750 inches, and the
mounting holes are sized for use with 4-40 or M3 screws.
- 3. TeleMini v2/EasyMini template
+ 3. TeleMini v2/EasyMini template
TeleMini v2 and EasyMini have overall dimensions of 0.800 x 1.500 inches, and the
mounting holes are sized for use with 4-40 or M3 screws.
-
TeleMini has overall dimensions of 0.500 x 1.500 inches, and the
mounting holes are sized for use with 2-56 or M2 screws.
-
There are only two calibrations required for TeleMetrum and
TeleMega, and only one for TeleDongle, TeleMini and EasyMini.
All boards are shipped from the factory pre-calibrated, but
@@ -2492,7 +2496,7 @@ NAR
connect to the board with a serial terminal program and
interact directly with the on-board command interpreter to
effect calibration.
-
+
The radio frequency is synthesized from a clock based on the
crystal on the board. The actual frequency of this oscillator
must be measured to generate a calibration constant. While our
@@ -2528,7 +2532,7 @@ NAR
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.
- 2. TeleMetrum and TeleMega Accelerometers
+ 2. TeleMetrum and TeleMega Accelerometers
While barometric sensors are factory-calibrated,
accelerometers are not, and so each must be calibrated once
installed in a flight computer. Explicitly calibrating the
@@ -2565,7 +2569,49 @@ NAR
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.
- Appendix D. Release NotesAppendix D. Release Notes
+ Version 1.3.1 is a minor release. It improves support for TeleMega,
+ TeleMetrum v2.0, TeleMini v2.0 and EasyMini.
+
+ AltOS Firmware Changes
+
+ Improve sensor boot code. If sensors fail to self-test, the
+ device will still boot up and check for pad/idle modes. If
+ in idle mode, the device will warn the user with a distinct
+ beep, if in Pad mode, the unit will operate as best it
+ can. Also, the Z-axis accelerometer now uses the factory
+ calibration values instead of re-calibrating on the pad each
+ time. This avoids accidental boost detect when moving the
+ device around while in Pad mode.
+
+ Fix antenna-down mode accelerometer configuration. Antenna
+ down mode wasn't working because the accelerometer
+ calibration values were getting re-computed incorrectly in
+ inverted mode.
+
+ Improved APRS mode. Now uses compressed position format for
+ smaller data size, improved precision and to include
+ altitude data as well as latitude and longitude. Also added
+ battery and pyro voltage reports in the APRS comment field
+ so you can confirm that the unit is ready for launch.
+
+
+ AltosUI changes
+
+ Display additional TeleMega sensor values in real
+ units. Make all of these values available for
+ plotting. Display TeleMega orientation value in the Ascent
+ and Table tabs.
+
+ Support additional TeleMega pyro channels in the Fire
+ Igniter dialog. This lets you do remote testing of all of
+ the channels, rather than just Apogee and Main.
+
+ Limit data rate when downloading satellite images from
+ Google to make sure we stay within their limits so that all
+ of the map tiles download successfully.
+
+
Version 1.3 is a major release. It adds support for TeleMega,
TeleMetrum v2.0, TeleMini v2.0 and EasyMini.
@@ -2606,7 +2652,7 @@ NAR
Save the last log directory and offer that as the default for new downloads
-
Version 1.2.1 is a minor release. It adds support for TeleBT and
the AltosDroid application, provides several new features in
AltosUI and fixes some bugs in the AltOS firmware.
@@ -2666,7 +2712,7 @@ NAR
a complete summary of the flight without needing to 'replay'
the whole thing.
-
Version 1.2 is a major release. It adds support for MicroPeak and
the MicroPeak USB adapter.
@@ -2692,7 +2738,7 @@ NAR
Altus Metrum software packages to be installed in the same
directory at the same time.
-
Version 1.1.1 is a bug-fix release. It fixes a couple of bugs in
AltosUI and one firmware bug that affects TeleMetrum version 1.0
boards. Thanks to Bob Brown for help diagnosing the Google Earth
@@ -2737,7 +2783,7 @@ NAR
from the flight computer was missing a check for TeleMini when
deciding whether to fetch the analog sensor data.
-
Version 1.1 is a minor release. It provides a few new features in AltosUI
and the AltOS firmware and fixes bugs.
@@ -2809,7 +2855,7 @@ NAR
Add Imperial units mode to present data in feet instead of
meters.
-
Version 1.0.1 is a major release, adding support for the TeleMini
device and lots of new AltosUI features
@@ -2889,7 +2935,7 @@ NAR
Flight window so you can immediately see the results of a
flight.
-
Version 0.9.2 is an AltosUI bug-fix release, with no firmware changes.
Fix plotting problems due to missing file in the Mac OS install image.
@@ -2897,7 +2943,7 @@ NAR
Always read whole eeprom blocks, mark empty records invalid, display parsing errors to user.
Add software version to Configure AltosUI dialog
-
Version 0.9 adds a few new firmware features and accompanying
AltosUI changes, along with new hardware support.
Version 0.8 offers a major upgrade in the AltosUI
interface. Significant new features include:
@@ -2956,7 +3002,7 @@ NAR
Exports Google Earth flight tracks. Using the Keyhole Markup
Language (.kml) file format, this provides a 3D view of your
rocket flight through the Google Earth program.
-
Version 0.7.1 is the first release containing our new cross-platform Java-based user interface. AltosUI can:
|
