Storage Full | warble | On-board data logging storage is full. This will
+seconds. Table 3.2. Pad/Idle Indications Name | Beeps | Description |
---|
Neither | brap | No continuity detected on either apogee or main igniters. | Apogee | dit | Continuity detected only on apogee igniter. | Main | dit dit | Continuity detected only on main igniter. | Both | dit dit dit | Continuity detected on both igniters. | Storage Full | warble | On-board data logging storage is full. This will
not prevent the flight computer from safely
controlling the flight or transmitting telemetry
signals, but no record of the flight will be
@@ -166,7 +166,7 @@ primary igniter channels. |
Table 3.3. Pad Radio Indications Name | Beeps | Description |
---|
Neither | ½ second tone | No continuity detected on either apogee or main igniters. | Apogee | dit | Continuity detected only on apogee igniter. | Main | dit dit | Continuity detected only on main igniter. | Both | dit dit dit | Continuity detected on both igniters. |
During ascent, the tones will be muted to allow the
+igniter status once every five seconds. Table 3.3. Pad Radio Indications Name | Beeps | Description |
---|
Neither | ½ second tone | No continuity detected on either apogee or main igniters. | Apogee | dit | Continuity detected only on apogee igniter. | Main | dit dit | Continuity detected only on main igniter. | Both | dit dit dit | Continuity detected on both igniters. |
During ascent, the tones will be muted to allow the
telemetry data to consume the full radio bandwidth. During descent and after landing, a ½ second tone will
be transmitted every five seconds. This can be used to
find the rocket using RDF techniques when the signal
@@ -184,7 +184,8 @@ launch and then fly the rocket. In this mode, the USB
link is
disabled, and the radio goes into transmit-only mode.
The only way to get out of this
-mode is to power the flight computer down.
+mode is to power the flight computer down. See below for how to get the flight
+computer to come up in Flight/Pad mode at power on.
Idle
@@ -192,7 +193,8 @@ The flight computer is ready to communicate over USB
and in packet mode over the radio.
You can configure
the flight computer, download data or display
-the current state.
+the current state. See below for how to get the flight
+computer to come up in Idle mode at power on.
For flight computers with accelerometers (TeleMetrum,
EasyMega and TeleMega), the mode is selected by the
orientation of the board during the self test
@@ -234,7 +236,7 @@ battery. TeleMetrum is a 1 inch by 2¾ inch circuit board. It was designed to
+the board. TeleMetrum is a 1 inch by 2¾ inch circuit board. It was designed to
fit inside coupler for 29mm air-frame tubing, but using it in a tube that
small in diameter may require some creativity in mounting and wiring
to succeed! The presence of an accelerometer means TeleMetrum should
@@ -255,7 +257,7 @@ screw terminals in the same position. Table 4.1. TeleMetrum Screw Terminals Terminal # | Terminal Name | Description |
---|
1 | Switch Output | Switch connection to flight computer | 2 | Switch Input | Switch connection to positive battery terminal | 3 | Main + | Main pyro channel common connection to battery | 4 | Main - | Main pyro channel connection to pyro circuit | 5 | Apogee + | Apogee pyro channel common connection to battery | 6 | Apogee - | Apogee pyro channel connection to pyro circuit |
4.2. Using a Separate Pyro Battery with TeleMetrumAs described above, using an external pyro battery involves
+the terminals are as follows: Table 4.1. TeleMetrum Screw Terminals Terminal # | Terminal Name | Description |
---|
1 | Switch Output | Switch connection to flight computer | 2 | Switch Input | Switch connection to positive battery terminal | 3 | Main + | Main pyro channel common connection to battery | 4 | Main - | Main pyro channel connection to pyro circuit | 5 | Apogee + | Apogee pyro channel common connection to battery | 6 | Apogee - | Apogee pyro channel connection to pyro circuit |
4.2. Using a Separate Pyro Battery with TeleMetrumAs described above, using an external pyro battery involves
connecting the negative battery terminal to the flight
computer ground, connecting the positive battery terminal to
one of the igniter leads and connecting the other igniter
@@ -271,7 +273,7 @@ connections, one to the positive battery terminal, one to
the flight computer positive input and one to ground. The positive battery terminal is available on screw terminal
2, the positive flight computer input is on terminal 1. To
hook a lead to ground, solder a piece of wire, 24 to 28
-gauge stranded, to the GND hole just above terminal 1. TeleMini v3 is 0.5 inches by 1.67 inches. It was
+gauge stranded, to the GND hole just above terminal 1. TeleMini v3 is 0.5 inches by 1.67 inches. It was
designed to fit inside an 18mm air-frame tube, but using it in
a tube that small in diameter may require some creativity in
mounting and wiring to succeed! Since there is no
@@ -289,7 +291,7 @@ screw terminals are located in the middle of the board
for the power switch. Using the
picture above and starting from the top for the pyro terminals
and from the left for the power switch terminals, the
-connections are as follows: Table 5.1. TeleMini v3 Screw Terminals Terminal # | Terminal Name | Description |
---|
1 | Apogee - | Apogee pyro channel connection to pyro circuit | 2 | Apogee | Apogee pyro channel common connection to battery | 3 | Main - | Main pyro channel connection to pyro circuit | 4 | Main | Main pyro channel common connection to battery | Left | Switch Output | Switch connection to flight computer | Right | Switch Input | Switch connection to positive battery terminal |
5.2. Using a Separate Pyro Battery with TeleMini v3As described above, using an external pyro battery involves
+connections are as follows: Table 5.1. TeleMini v3 Screw Terminals Terminal # | Terminal Name | Description |
---|
1 | Apogee - | Apogee pyro channel connection to pyro circuit | 2 | Apogee | Apogee pyro channel common connection to battery | 3 | Main - | Main pyro channel connection to pyro circuit | 4 | Main | Main pyro channel common connection to battery | Left | Switch Output | Switch connection to flight computer | Right | Switch Input | Switch connection to positive battery terminal |
5.2. Using a Separate Pyro Battery with TeleMini v3As described above, using an external pyro battery involves
connecting the negative battery terminal to the flight
computer ground, connecting the positive battery terminal to
one of the igniter leads and connecting the other igniter
@@ -312,7 +314,7 @@ the left power switch wire. Hook a lead to either of the
mounting holes for a ground connection. TeleMini v1 is the earlier version of this product. It
has a lower-power radio, less storage, no beeper and
soldered-in wires instead of screw terminals for the
-power switch. EasyMini is built on a 0.8 inch by 1½ inch circuit board. Itâs
+power switch. EasyMini is built on a 0.8 inch by 1½ inch circuit board. Itâs
designed to fit in a 24mm coupler tube. You usually donât need to configure EasyMini at all; itâs set
up to do dual-deployment with an event at apogee to separate
the airframe and deploy a drogue and another event at 250m
@@ -323,7 +325,7 @@ board. Using the picture
above, the top four have connections for the main pyro
circuit and an external battery and the bottom four have
connections for the apogee pyro circuit and the power
-switch. Counting from the left, the connections are as follows: Table 6.1. EasyMini Screw Terminals Terminal # | Terminal Name | Description |
---|
Top 1 | Main - | Main pyro channel connection to pyro circuit | Top 2 | Main | Main pyro channel common connection to battery | Top 3 | Battery | Positive external battery terminal | Top 4 | Battery - | Negative external battery terminal | Bottom 1 | Apogee - | Apogee pyro channel connection to pyro circuit | Bottom 2 | Apogee | Apogee pyro channel common connection to battery | Bottom 3 | Switch Output | Switch connection to flight computer | Bottom 4 | Switch Input | Switch connection to positive battery terminal |
6.2. Connecting A Battery To EasyMiniThere are two possible battery connections on
+switch. Counting from the left, the connections are as follows: Table 6.1. EasyMini Screw Terminals Terminal # | Terminal Name | Description |
---|
Top 1 | Main - | Main pyro channel connection to pyro circuit | Top 2 | Main | Main pyro channel common connection to battery | Top 3 | Battery | Positive external battery terminal | Top 4 | Battery - | Negative external battery terminal | Bottom 1 | Apogee - | Apogee pyro channel connection to pyro circuit | Bottom 2 | Apogee | Apogee pyro channel common connection to battery | Bottom 3 | Switch Output | Switch connection to flight computer | Bottom 4 | Switch Input | Switch connection to positive battery terminal |
6.2. Connecting A Battery To EasyMiniThere are two possible battery connections on
EasyMini. You can use either method; both feed
through the power switch terminals. One battery connection is the standard Altus Metrum
white JST plug. This mates with single-cell Lithium
@@ -351,7 +353,7 @@ the flight computer positive input and one to ground. Use
the negative external battery connection, top terminal 4 for
ground. The positive battery terminal is available on bottom
terminal 4, the positive flight computer input is on the
-bottom terminal 3. TeleMega is a 1¼ inch by 3¼ inch circuit board. It was
+bottom terminal 3. TeleMega is a 1¼ inch by 3¼ inch circuit board. It was
designed to easily fit in a 38mm coupler. Like TeleMetrum,
TeleMega has an accelerometer and so it must be mounted so that
the board is aligned with the flight axis. It can be mounted
@@ -366,7 +368,7 @@ Radio switched from cc1120 to cc1200.
they do mean that the device needs different firmware to
operate correctly, so make sure you load the right firmware
when reflashing the device. 7.1. TeleMega Screw TerminalsTeleMega has two sets of nine screw terminals on the end of
-the board opposite the telemetry antenna. They are as follows: Table 7.1. TeleMega Screw Terminals Terminal # | Terminal Name | Description |
---|
Top 1 | Switch Input | Switch connection to positive battery terminal | Top 2 | Switch Output | Switch connection to flight computer | Top 3 | GND | Ground connection for use with external active switch | Top 4 | Main - | Main pyro channel connection to pyro circuit | Top 5 | Main | Main pyro channel common connection to battery | Top 6 | Apogee - | Apogee pyro channel connection to pyro circuit | Top 7 | Apogee | Apogee pyro channel common connection to battery | Top 8 | D - | D pyro channel connection to pyro circuit | Top 9 | D | D pyro channel common connection to battery | Bottom 1 | GND | Ground connection for negative pyro battery terminal | Bottom 2 | Pyro | Positive pyro battery terminal | Bottom 3 | Lipo | Power switch output. Use to connect main battery to pyro battery input | Bottom 4 | A - | A pyro channel connection to pyro circuit | Bottom 5 | A | A pyro channel common connection to battery | Bottom 6 | B - | B pyro channel connection to pyro circuit | Bottom 7 | B | B pyro channel common connection to battery | Bottom 8 | C - | C pyro channel connection to pyro circuit | Bottom 9 | C | C pyro channel common connection to battery |
7.2. Using a Separate Pyro Battery with TeleMegaTeleMega provides explicit support for an external pyro
+the board opposite the telemetry antenna. They are as follows: Table 7.1. TeleMega Screw Terminals Terminal # | Terminal Name | Description |
---|
Top 1 | Switch Input | Switch connection to positive battery terminal | Top 2 | Switch Output | Switch connection to flight computer | Top 3 | GND | Ground connection for use with external active switch | Top 4 | Main - | Main pyro channel connection to pyro circuit | Top 5 | Main | Main pyro channel common connection to battery | Top 6 | Apogee - | Apogee pyro channel connection to pyro circuit | Top 7 | Apogee | Apogee pyro channel common connection to battery | Top 8 | D - | D pyro channel connection to pyro circuit | Top 9 | D | D pyro channel common connection to battery | Bottom 1 | GND | Ground connection for negative pyro battery terminal | Bottom 2 | Pyro | Positive pyro battery terminal | Bottom 3 | Lipo | Power switch output. Use to connect main battery to pyro battery input | Bottom 4 | A - | A pyro channel connection to pyro circuit | Bottom 5 | A | A pyro channel common connection to battery | Bottom 6 | B - | B pyro channel connection to pyro circuit | Bottom 7 | B | B pyro channel common connection to battery | Bottom 8 | C - | C pyro channel connection to pyro circuit | Bottom 9 | C | C pyro channel common connection to battery |
7.2. Using a Separate Pyro Battery with TeleMegaTeleMega provides explicit support for an external pyro
battery. All that is required is to remove the jumper
between the lipo terminal (Bottom 3) and the pyro terminal
(Bottom 2). Then hook the negative pyro battery terminal to ground
@@ -382,12 +384,12 @@ wire from the Lipo terminal (Bottom 3) to the Pyro terminal
connections, one to the positive battery terminal, one to
the flight computer positive input and one to ground. The positive battery terminal is available on Top terminal
1, the positive flight computer input is on Top terminal
-2. Ground is on Top terminal 3. EasyMega is a 1¼ inch by 2¼ inch circuit board. It was
+2. Ground is on Top terminal 3. EasyMega is a 1¼ inch by 2¼ inch circuit board. It was
designed to easily fit in a 38mm coupler. Like TeleMetrum,
EasyMega has an accelerometer and so it must be mounted so that
the board is aligned with the flight axis. It can be mounted
either antenna up or down. 8.1. EasyMega Screw TerminalsEasyMega has two sets of nine screw terminals on the end of
-the board opposite the telemetry antenna. They are as follows: Table 8.1. EasyMega Screw Terminals Terminal # | Terminal Name | Description |
---|
Top 1 | Switch Input | Switch connection to positive battery terminal | Top 2 | Switch Output | Switch connection to flight computer | Top 3 | GND | Ground connection for use with external active switch | Top 4 | Main - | Main pyro channel connection to pyro circuit | Top 5 | Main | Main pyro channel common connection to battery | Top 6 | Apogee - | Apogee pyro channel connection to pyro circuit | Top 7 | Apogee | Apogee pyro channel common connection to battery | Top 8 | D - | D pyro channel connection to pyro circuit | Top 9 | D | D pyro channel common connection to battery | Bottom 1 | GND | Ground connection for negative pyro battery terminal | Bottom 2 | Pyro | Positive pyro battery terminal | Bottom 3 | Lipo | Power switch output. Use to connect main battery to pyro battery input | Bottom 4 | A - | A pyro channel connection to pyro circuit | Bottom 5 | A | A pyro channel common connection to battery | Bottom 6 | B - | B pyro channel connection to pyro circuit | Bottom 7 | B | B pyro channel common connection to battery | Bottom 8 | C - | C pyro channel connection to pyro circuit | Bottom 9 | C | C pyro channel common connection to battery |
8.2. Using a Separate Pyro Battery with EasyMegaEasyMega provides explicit support for an external pyro
+the board opposite the telemetry antenna. They are as follows: Table 8.1. EasyMega Screw Terminals Terminal # | Terminal Name | Description |
---|
Top 1 | Switch Input | Switch connection to positive battery terminal | Top 2 | Switch Output | Switch connection to flight computer | Top 3 | GND | Ground connection for use with external active switch | Top 4 | Main - | Main pyro channel connection to pyro circuit | Top 5 | Main | Main pyro channel common connection to battery | Top 6 | Apogee - | Apogee pyro channel connection to pyro circuit | Top 7 | Apogee | Apogee pyro channel common connection to battery | Top 8 | D - | D pyro channel connection to pyro circuit | Top 9 | D | D pyro channel common connection to battery | Bottom 1 | GND | Ground connection for negative pyro battery terminal | Bottom 2 | Pyro | Positive pyro battery terminal | Bottom 3 | Lipo | Power switch output. Use to connect main battery to pyro battery input | Bottom 4 | A - | A pyro channel connection to pyro circuit | Bottom 5 | A | A pyro channel common connection to battery | Bottom 6 | B - | B pyro channel connection to pyro circuit | Bottom 7 | B | B pyro channel common connection to battery | Bottom 8 | C - | C pyro channel connection to pyro circuit | Bottom 9 | C | C pyro channel common connection to battery |
8.2. Using a Separate Pyro Battery with EasyMegaEasyMega provides explicit support for an external pyro
battery. All that is required is to remove the jumper
between the lipo terminal (Bottom 3) and the pyro terminal
(Bottom 2). Then hook the negative pyro battery terminal to ground
@@ -556,7 +558,7 @@ feel free to dive in and help! Or let us know what
youâd like to see that we arenât already working on,
and maybe weâll get excited about it too⦠Watch our web site for
more news and information as our family of products
-evolves! The AltosUI program provides a graphical user interface for
+evolves! 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
tasks. The primary interface window provides a selection of
@@ -566,7 +568,7 @@ the tasks provided from the top-level toolbar. All telemetry data received are automatically recorded
+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. The radio frequency being monitored by the TeleDongle
device is displayed at the top of the window. You can
@@ -613,7 +615,7 @@ automatically switches to display 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
+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
whether the rocket is ready to launch: -
@@ -671,7 +673,7 @@ GPS receiver has reliable reception from the
satellites.
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
+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, acceleration and tilt are shown along
with the maximum values for each of them. This allows you to
@@ -682,7 +684,7 @@ may not get updated as the GPS receiver loses position
fix. Once the rocket starts coasting, the receiver should
start reporting position again. 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)
+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, waiting for the main charge
@@ -708,7 +710,7 @@ see what the status of the apogee charge is. Note
that some commercial 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
+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 generally within a short distance of the
@@ -730,11 +732,11 @@ depends on the quality of your radio link and how many
packets were received. Recovering the on-board data
after flight may yield more precise results. 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
+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
+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 rocketâs state is
@@ -753,7 +755,7 @@ units will be shown at the start of the line. Images are fetched automatic
Static API, and cached on disk for reuse. If map
images cannot be downloaded, the rocketâs path will be
traced on a dark gray background instead. You can pre-load images for your favorite launch sites
-before you leave home; check out Section 11.12, âLoad Mapsâ. TeleMega includes four additional programmable pyro
channels. The Ignitor tab shows whether each of them has
continuity. If an ignitor has a low resistance, then the
voltage measured here will be close to the pyro battery
@@ -798,7 +800,7 @@ record file, either a .telem file recording telemetry data or a
flash memory. Note that telemetry files will generally produce poor graphs
due to the lower sampling rate and missed telemetry packets.
Use saved flight data in .eeprom files for graphing where possible. Once a flight record is selected, a window with multiple tabs is
-opened. By default, the graph contains acceleration (blue),
+opened. By default, the graph contains acceleration (blue),
velocity (green) and altitude (red). The graph can be zoomed into a particular area by
clicking and dragging down and to the right. Once
zoomed, the graph can be reset by clicking and
@@ -806,9 +808,28 @@ dragging up and to the left. Holding down 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 11.4.3. Flight StatisticsShows overall data computed from the flight. Shows a satellite image of the flight area overlaid
+plot. This selects which graph elements to show, and, at the
+very bottom. It also lets you configure how
+the graph is drawn: -
+Whether to use metric or imperial units
+
-
+Whether to show a marker at each data
+point. When displaying a small section of
+the graph, these can be useful to know what
+data values were recorded.
+
-
+How wide to draw the lines in the graph
+
-
+How to filter speed and acceleration data
+computed from barometric data. Flight
+computers with accelerometers never display
+computed acceleration data, and only use
+barometric data to compute speed during
+descent. Flight computers without
+accelerometers always compute both speed and
+acceleration from barometric data. A larger
+value smooths the data more.
+
11.4.3. Flight StatisticsShows 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
@@ -835,7 +856,7 @@ standard units, with the barometric data reported in
both pressure, altitude and height above pad units. 11.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. 11.6. Configure AltimeterSelect this button and then select either an altimeter or
+in 3D. 11.6. Configure AltimeterSelect 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. The first few lines of the dialog provide information about the
@@ -993,7 +1014,13 @@ skipped, which saves storage space. 11.6.18. Configure Pyro ChannelsThis opens a separate window to configure the
+in the log. 11.6.18. Calibrate AccelerometerThis opens a separate window to recalibrate the
+accelerometers. Follow the instructions, orienting the
+flight computer with the antenna end, or end opposite
+the screw terminals, in the case of EasyMega, first up
+and then down. When the calibration is complete, return to the
+Configure Altimeter window and save the new
+calibration values. 11.6.19. Configure Pyro ChannelsThis opens a separate window to configure the
additional pyro channels available on TeleMega
and EasyMega. One column is presented for
each channel. Each row represents a single
@@ -1120,7 +1147,7 @@ note that the check is based on when the rocket transitions When a motor burns out, the rocket enters either Fast or Coast state
(depending on how fast it is moving). If the computer detects upwards
-acceleration again, it will move back to Boost state. This button presents a dialog so that you can
+acceleration again, it will move back to Boost state. 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
@@ -1185,7 +1212,7 @@ 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. 11.8. Configure GroundstationSelect this button and then select a TeleDongle or
+menus. 11.8. Configure GroundstationSelect this button and then select a TeleDongle or
TeleBT Device from the list provided. The first few lines of the dialog provide information
about the connected device, including the product
name, software version and hardware serial
@@ -1240,7 +1267,7 @@ EasyMini and TeleDongle v3 are all
programmed directly
over USB (self programming). Please read
the directions for flashing devices in
-Appendix C, Updating Device Firmware. This activates the igniter circuits in the flight
computer to help test recovery systems
deployment.
Because this command can operate over the
@@ -1256,13 +1283,13 @@ button. The word Arm is replaced by a cou
timer indicating that 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
+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 baud rates and telemetry formats should
be tried; by default, it only listens at 38400 baud
with the standard telemetry format used in v1.0 and
-later firmware. Before heading out to a new launch site, you can use
+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. Thereâs a drop-down menu of launch sites we know
about; if your favorites arenât there, please let us
@@ -1310,7 +1337,7 @@ Google Maps; note that Google limits how many images
you can fetch at 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
+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 listening for telemetry
@@ -1923,7 +1950,7 @@ same time while keeping the identify of each one separate in
the receiver. By default, the SSID is set to the last digit of
the device serial number. The APRS packet format includes a comment field that
can have arbitrary text in it. AltOS uses this to send
-status information as shown in the following table. Table A.1. Altus Metrum APRS Comments Field | Example | Description |
---|
1 | L | GPS Status U for unlocked, L for locked | 2 | 6 | Number of Satellites in View | 3 | B4.0 | Altimeter Battery Voltage | 4 | A3.7 | Apogee Igniter Voltage | 5 | M3.7 | Main Igniter Voltage | 6 | 1286 | Device Serial Number | 4 | 1286 | Device Serial Number |
Hereâs an example of an APRS comment showing GPS lock with 6
+status information as shown in the following table. Table A.1. Altus Metrum APRS Comments Field | Example | Description |
---|
1 | L | GPS Status U for unlocked, L for locked | 2 | 6 | Number of Satellites in View | 3 | B4.0 | Altimeter Battery Voltage | 4 | A3.7 | Apogee Igniter Voltage | 5 | M3.7 | Main Igniter Voltage | 6 | 1286 | Device Serial Number | 4 | 1286 | Device Serial Number |
Hereâs an example of an APRS comment showing GPS lock with 6
satellites in view, a primary battery at 4.0V, and
apogee and main igniters both at 3.7V from device 1286. L6 B4.0 A3.7 M3.7 1286 Hereâs an example of an APRS comment showing GPS lock with 6
satellites in view and a primary battery at 4.0V from device 1876. L6 B4.0 1876 Make sure your primary battery is above 3.8V
@@ -2276,7 +2303,7 @@ descent, except for TeleMini v1.0, which records ascent at 10 samples
per second and descent at 1 sample per second.
Data are logged to
an on-board flash memory part, which can be partitioned into
-several equal-sized blocks, one for each flight. Table D.1. Data Storage on Altus Metrum altimeters Device | Bytes per Sample | Total Storage | Minutes at Full Rate |
---|
TeleMetrum v1.0 | 8 | 1MB | 20 | TeleMetrum v1.1 v1.2 | 8 | 2MB | 40 | TeleMetrum v2.0 | 16 | 8MB | 80 | TeleMini v1.0 | 2 | 5kB | 4 | TeleMini v3.0 | 16 | 512kB | 5 | EasyMini | 16 | 1MB | 10 | TeleMega | 32 | 8MB | 40 | EasyMega | 32 | 8MB | 40 |
The on-board flash is partitioned into separate flight logs,
+several equal-sized blocks, one for each flight. Table D.1. Data Storage on Altus Metrum altimeters Device | Bytes per Sample | Total Storage | Minutes at Full Rate |
---|
TeleMetrum v1.0 | 8 | 1MB | 20 | TeleMetrum v1.1 v1.2 | 8 | 2MB | 40 | TeleMetrum v2.0 | 16 | 8MB | 80 | TeleMini v1.0 | 2 | 5kB | 4 | TeleMini v3.0 | 16 | 512kB | 5 | EasyMini | 16 | 1MB | 10 | TeleMega | 32 | 8MB | 40 | EasyMega | 32 | 8MB | 40 |
The on-board flash is partitioned into separate flight logs,
each of a fixed maximum size. Increase the maximum size of
each log and you reduce the number of flights that can be
stored. Decrease the size and you can store more flights. Configuration data is also stored in the flash memory on
@@ -2305,12 +2332,102 @@ flight data, so be sure to download flight data and erase it
from the flight computer before it fills up. The flight
computer will still successfully control the flight even if it
cannot log data, so the only thing you will lose is the data. Appendix E. Altus Metrum Hardware SpecificationsHereâs the full set of Altus Metrum products, both in
-production and retired. Table E.1. Altus Metrum Flight Computer Electronics Device | Barometer | Z-axis accel | GPS | 3D sensors | Storage | RF Output | Battery |
---|
TeleMetrum v1.0 | MP3H6115 10km (33k') | MMA2202 50g | SkyTraq | - | 1MB | 10mW | 3.7V | TeleMetrum v1.1 | MP3H6115 10km (33k') | MMA2202 50g | SkyTraq | - | 2MB | 10mW | 3.7V | TeleMetrum v1.2 | MP3H6115 10km (33k') | ADXL78 70g | SkyTraq | - | 2MB | 10mW | 3.7V | TeleMetrum v2.0 | MS5607 30km (100k') | MMA6555 102g | uBlox Max-7Q | - | 8MB | 40mW | 3.7V | TeleMini v1.0 | MP3H6115 10km (33k') | - | - | - | 5kB | 10mW | 3.7V | TeleMini v3.0 | MS5607 30km (100k') | - | - | - | 512kB | 40mW | 3.7V | EasyMini v1.0 | MS5607 30km (100k') | - | - | - | 1MB | - | 3.7-12V | TeleMega v1.0 | MS5607 30km (100k') | MMA6555 102g | uBlox Max-7Q | MPU6000 HMC5883 | 8MB | 40mW | 3.7V | TeleMega v2.0 | MS5607 30km (100k') | MMA6555 102g | uBlox Max-7Q | MPU6000 HMC5883 | 8MB | 40mW | 3.7V | EasyMega v1.0 | MS5607 30km (100k') | MMA6555 102g | - | MPU6000 HMC5883 | 8MB | - | 3.7V |
Table E.2. Altus Metrum Flight Computer Mechanical Components Device | Connectors | Screw Terminals | Width | Length | Tube Size |
---|
TeleMetrum | Antenna Debug Companion USB Battery | Apogee pyro Main pyro Switch | 1 inch (2.54cm) | 2 ¾ inch (6.99cm) | 29mm coupler | TeleMini v1.0 | Antenna Debug Battery | Apogee pyro Main pyro | ½ inch (1.27cm) | 1½ inch (3.81cm) | 18mm coupler | TeleMini v2.0 | Antenna Debug USB Battery | Apogee pyro Main pyro Battery Switch | 0.8 inch (2.03cm) | 1½ inch (3.81cm) | 24mm coupler | EasyMini | Debug USB Battery | Apogee pyro Main pyro Battery | 0.8 inch (2.03cm) | 1½ inch (3.81cm) | 24mm coupler | TeleMega | Antenna Debug Companion USB Battery | Apogee pyro Main pyro Pyro A-D Switch Pyro battery | 1¼ inch (3.18cm) | 3¼ inch (8.26cm) | 38mm coupler | EasyMega | Debug Companion USB Battery | Apogee pyro Main pyro Pyro A-D Switch Pyro battery | 1¼ inch (3.18cm) | 2¼ inch (5.62cm) | 38mm coupler |
Appendix F. Release NotesF.1. Release Notes for Version 1.8Version 1.8 includes support for our new TeleBT v4.0 ground
+production and retired. Table E.1. Altus Metrum Flight Computer Electronics Device | Barometer | Z-axis accel | GPS | 3D sensors | Storage | RF Output | Battery |
---|
TeleMetrum v1.0 | MP3H6115 10km (33k') | MMA2202 50g | SkyTraq | - | 1MB | 10mW | 3.7V | TeleMetrum v1.1 | MP3H6115 10km (33k') | MMA2202 50g | SkyTraq | - | 2MB | 10mW | 3.7V | TeleMetrum v1.2 | MP3H6115 10km (33k') | ADXL78 70g | SkyTraq | - | 2MB | 10mW | 3.7V | TeleMetrum v2.0 | MS5607 30km (100k') | MMA6555 102g | uBlox Max-7Q | - | 8MB | 40mW | 3.7V | TeleMini v1.0 | MP3H6115 10km (33k') | - | - | - | 5kB | 10mW | 3.7V | TeleMini v3.0 | MS5607 30km (100k') | - | - | - | 512kB | 40mW | 3.7V | EasyMini v1.0 | MS5607 30km (100k') | - | - | - | 1MB | - | 3.7-12V | TeleMega v1.0 | MS5607 30km (100k') | MMA6555 102g | uBlox Max-7Q | MPU6000 HMC5883 | 8MB | 40mW | 3.7V | TeleMega v2.0 | MS5607 30km (100k') | MMA6555 102g | uBlox Max-7Q | MPU6000 HMC5883 | 8MB | 40mW | 3.7V | EasyMega v1.0 | MS5607 30km (100k') | MMA6555 102g | - | MPU6000 HMC5883 | 8MB | - | 3.7V |
Table E.2. Altus Metrum Flight Computer Mechanical Components Device | Connectors | Screw Terminals | Width | Length | Tube Size |
---|
TeleMetrum | Antenna Debug Companion USB Battery | Apogee pyro Main pyro Switch | 1 inch (2.54cm) | 2 ¾ inch (6.99cm) | 29mm coupler | TeleMini v1.0 | Antenna Debug Battery | Apogee pyro Main pyro | ½ inch (1.27cm) | 1½ inch (3.81cm) | 18mm coupler | TeleMini v2.0 | Antenna Debug USB Battery | Apogee pyro Main pyro Battery Switch | 0.8 inch (2.03cm) | 1½ inch (3.81cm) | 24mm coupler | EasyMini | Debug USB Battery | Apogee pyro Main pyro Battery | 0.8 inch (2.03cm) | 1½ inch (3.81cm) | 24mm coupler | TeleMega | Antenna Debug Companion USB Battery | Apogee pyro Main pyro Pyro A-D Switch Pyro battery | 1¼ inch (3.18cm) | 3¼ inch (8.26cm) | 38mm coupler | EasyMega | Debug Companion USB Battery | Apogee pyro Main pyro Pyro A-D Switch Pyro battery | 1¼ inch (3.18cm) | 2¼ inch (5.62cm) | 38mm coupler |
Appendix F. Release NotesF.1. Release Notes for Version 1.8.5Version 1.8.5 includes fixes to the ground software support
+for TeleBT v4, along with a few other minor updates. -
+Fix startup beeps that indicate sensor failures.
+
-
+When updating device firmware, make sure selected firmware
+matches target device.
+
-
+Correct Bluetooth device matching when looking for TeleBT
+devices.
+
F.2. Release Notes for Version 1.8.4Version 1.8.4 includes support for EasyMini version 2.0 -
+Support for EasyMini version 2.0 hardware.
+
F.3. Release Notes for Version 1.8.3Version 1.8.3 includes support for TeleMega version 3.0 along
+with two important flight computer fixes. This version also
+changes KML export data to make Tripoli Record reporting
+better and some updates to graph presentation and data
+downloading. -
+Support for TeleMega version 3.0 hardware.
+
-
+Ground testing EasyMega and TeleMega additional pyro
+channels could result in a sticky fired status which would
+prevent these channels from firing on future flights.
+
-
+Corrupted flight log records could prevent future flights
+from capturing log data.
+
-
+Fixed saving of pyro configuration that ended with
+Descending.
+
F.3.2. AltosUI and TeleGPS Applications-
+Support for TeleMega version 3.0.
+
-
+Graph lines have improved appearance to make them easier to
+distinguish. Markers may be placed at data points to show
+captured recorded data values.
+
-
+Graphing offers the ability to adjust the smoothing of
+computed speed and acceleration data.
+
-
+The download dialog now offers to graph new flights, checks
+for existing files to avoid overwriting data and reports if
+there are checksum errors in the downloaded data.
+
AltosUI/TeleGPS Bug Fixes-
+Restore TeleGPS tracking behavior.
+
-
+Display flight computer call sign and serial number in
+Monitor Idle mode instead of ground station values.
+
AltosUI and TeleGPS Changes-
+KML export now reports both barometric and GPS altitude data
+to make it more useful for Tripoli record reporting.
+
-
+CSV export now includes TeleMega/EasyMega pyro voltages and
+tilt angle.
+
F.4. Release Notes for Version 1.8.2Version 1.8.2 includes support for TeleGPS version 2.0 along
+with accelerometer recalibration support in AltosUI. 1.8.2 also contains a couple of minor fixes for AltosUI when
+analyzing saved data files. AltOS New Features -
+Support for TeleGPS version 2.0 hardware.
+
F.4.2. AltosUI and TeleGPS ApplicationsAltosUI and TeleGPS New Features -
+Support for TeleGPS version 2.0.
+
-
+Accelerometer re-calibration user interface.
+
AltosUI and TeleGPS Bug Fixes -
+Prevent some crashes when reading older saved flight data
+for graphing or KML export.
+
F.5. Release Notes for Version 1.8.1Version 1.8.1 includes an important bug fix for Apogee Lockout
+operation in all flight computers. Anyone using this option
+must update firmware. This release also contains a change in how flight computers
+with accelerometers deal with speeds around and above Mach
+1. In previous versions, the flight computer would completely
+disregard the barometric sensor above 330m/s (around Mach
+1). Now, the data from the barometric sensor is reduced in
+effect without ever going away entirely. This prevents early
+drogue deployment for flights which spend considerable time
+above Mach 1. 1.8.1 also contains a couple of minor fixes for AltosUI when
+analyzing saved data files. AltOS Bug Fixes -
+Handle time value wrapping in Apogee Lockout
+correctly. Without this, apogee lockout would sometimes
+prevent any drogue charge from firing.
+
-
+Change Kalman filter on flight computers with accelerometer
+to continue using the barometric sensor even at high speeds
+to avoid unintentional drogue deployment during
+deceleration.
+
F.5.2. AltosUI and TeleGPS ApplicationsAltosUI New Features -
+Add new Huge font size to make text even bigger on high
+resolution monitors.
+
AltosUI Bug Fixes -
+Prevent some crashes when reading older saved flight data
+for graphing or KML export.
+
-
+Load frequency preference at startup. The loading code was
+broken, so youâd see only the default frequencies.
+
F.6. Release Notes for Version 1.8Version 1.8 includes support for our new TeleBT v4.0 ground
station, updates for data analysis in our ground station
software and bug fixes in in the flight software for all our
-boards and ground station interfaces. AltOS New Features -
+boards and ground station interfaces.
AltOS New Features -
Add support for TeleBT v4.0 boards.
-
F.1.2. AltosUI and TeleGPS ApplicationsAltosUI New Features F.6.2. AltosUI and TeleGPS ApplicationsAltosUI New Features -
Add support for TeleBT v4.0 hardware
-
Rewrite graphing and export functions. This code now handles
@@ -2321,20 +2438,20 @@ acceleration data more accurate.
AltosUI Bug Fixes -
Correct axis labeling of magnetic sensor in TeleMega and
EasyMega. The Y and Z axes were flipped.
-
F.2. Release Notes for Version 1.7Version 1.7 includes support for our new TeleMini v3.0
+ F.7. Release Notes for Version 1.7Version 1.7 includes support for our new TeleMini v3.0
flight computer and bug fixes in in the flight software for all our boards
-and ground station interfaces. AltOS New Features -
+and ground station interfaces.
AltOS New Features -
Add support for TeleMini v3.0 boards.
AltOS Fixes -
Fix interrupt priorities on STM32L processors. Run timer
interrupt at lowest priority so that device interrupts get
serviced first.
-
F.2.2. AltosUI and TeleGPS ApplicationsAltosUI New Features F.7.2. AltosUI and TeleGPS ApplicationsAltosUI New Features -
Add support for TeleMini v3.0 hardware
-
F.3. Release Notes for Version 1.6.8Version 1.6.8 fixes a TeleMega and TeleMetrum v2.0 bug where
+ F.8. Release Notes for Version 1.6.8Version 1.6.8 fixes a TeleMega and TeleMetrum v2.0 bug where
the device could stop logging data and transmitting
telemetry in flight. All TeleMega v1.0, v2.0 and TeleMetrum
-v2.0 users should update their flight firmware. AltOS fixes: -
+v2.0 users should update their flight firmware.
AltOS fixes: -
Fix STM32L DMA driver to work around STM32L SoC DMA priority
issue t lock-up in the logging or radio code, either of
which could stop data logging and telemetry.
@@ -2347,7 +2464,7 @@ flight.
AltOS changes: -
Flash LEDS on all products briefly during power up so that
they can be tested during production.
-
F.3.2. AltosUI, TeleGPS and AltosDroid ApplicationsAltosUI fixes: F.8.2. AltosUI, TeleGPS and AltosDroid ApplicationsAltosUI fixes: -
Re-enable go/no-go entries after theyâve been disabled due
to lack of data. If telemetry information is delayed when
the Ui starts up, sometimes important fields would get
@@ -2355,20 +2472,20 @@ disabled to never re-appear.
-
Deal with ground station failure better during Configure
Ground Station operation by cleaning up pending operations.
-
F.4. Release Notes for Version 1.6.5Version 1.6.5 fixes a TeleMega and TeleMetrum v2.0 bug where
+ F.9. Release Notes for Version 1.6.5Version 1.6.5 fixes a TeleMega and TeleMetrum v2.0 bug where
the device would often stop logging data and transmitting
telemetry in flight. All TeleMega v1.0, v2.0 and TeleMetrum
-v2.0 users should update their flight firmware. AltOS fixes: -
+v2.0 users should update their flight firmware.
AltOS fixes: -
Fix STM32L SPI driver to prevent lock-up in the logging or
radio code, either of which could stop data logging and
telemetry. Found and characterized by Chuck Haskin, who also
tested the new firmware before release.
-
F.4.2. AltosUI, TeleGPS and AltosDroid ApplicationsAltosUI fixes: F.9.2. AltosUI, TeleGPS and AltosDroid ApplicationsAltosUI fixes: -
Deliver firmward for TeleMega v2.0 and TeleBT v3.0 with
Windows package.
-
F.5. Release Notes for Version 1.6.4Version 1.6.4 fixes a bluetooth communication problem with
+ F.10. Release Notes for Version 1.6.4Version 1.6.4 fixes a bluetooth communication problem with
TeleBT v1.0 devices, along with some altosui and altosdroid
-minor nits. It also now ships firmware for some newer devices. AltOS fixes: -
+minor nits. It also now ships firmware for some newer devices.
AltOS fixes: -
Fix hardware flow control on TeleBT v1.0. Hardware RTS/CTS
doesnât seem to work, switch from using the hardware to
driving these pins with software.
@@ -2376,7 +2493,7 @@ driving these pins with software.
Fix ARM USB drivers to deal with OS restarts. Needed to
reset all USB-related state when the USB bus is reset. These
fixes affect all STM32L, STM32F0 and LPC11U14 based devices.
-
F.5.2. AltosUI, TeleGPS and AltosDroid ApplicationsAltosUI, TeleGPS and AltosDroid New Features: F.10.2. AltosUI, TeleGPS and AltosDroid ApplicationsAltosUI, TeleGPS and AltosDroid New Features: -
Automatically switch from meters or feet to kilometers or
miles for distance units.
-
@@ -2387,17 +2504,17 @@ Abort map preloading when the preload map dialog is closed.
In AltosDroid, Donât reconnect to last device if the user
had disconnected it the last time the application was
active.
-
-
Mention TeleMega v2.0 in hardware specs table.
-
Document TeleGPS RF output in telegps manual.
-
F.6. Release Notes for Version 1.6.3Version 1.6.3 adds idle mode to AltosDroid and has bug fixes
+ F.11. Release Notes for Version 1.6.3Version 1.6.3 adds idle mode to AltosDroid and has bug fixes
for our host software on desktops, laptops an android devices
-along with BlueTooth support for Windows. AltOS fixes: -
+along with BlueTooth support for Windows.
AltOS fixes: -
Fix hardware flow control on TeleBT v3.0. RTS/CTS is
wired backwards on this board, switch from using the
hardware to driving these pins with software.
-
F.6.2. AltosUI and TeleGPS ApplicationsAltosUI and TeleGPS New Features: F.11.2. AltosUI and TeleGPS ApplicationsAltosUI and TeleGPS New Features: -
Add BlueTooth support for Windows operating system. This
supports connections to TeleBT over BlueTooth rather than
just USB.
@@ -2419,7 +2536,7 @@ the connected Altus Metrum USB devices appear again.
-
Fix acceleration data presented in MonitorIdle mode for
TeleMetrum v2.0 flight computers.
-
AltosDroid new features: -
Monitor Idle mode. Check state of flight computer while in
idle mode over the radio link
-
@@ -2457,12 +2574,12 @@ Recover old tracker positions when restarting
application. This finally allows you to safely stop and
restart the application without losing the last known
location of any tracker.
-
-
Document TeleMega and EasyMega additional pyro channel
continuity audio alert pattern.
-
F.7. Release Notes for Version 1.6.2Version 1.6.2 includes support for our updated TeleMega v2.0
+ F.12. Release Notes for Version 1.6.2Version 1.6.2 includes support for our updated TeleMega v2.0
product and bug fixes in in the flight software for all our boards
-and ground station interfaces. AltOS New Features: -
+and ground station interfaces.
AltOS New Features: -
Add support for TeleMega v2.0 boards.
-
Add PWM servo driver. Thereâs no higher level code using
@@ -2471,14 +2588,14 @@ servo output connector.
AltOS Fixes: -
Slow down telemetry packets to allow receiver to keep
up.
-
F.7.2. AltosUI and TeleGPS ApplicationsAltosUI and TeleGPS Fixes: F.12.2. AltosUI and TeleGPS ApplicationsAltosUI and TeleGPS Fixes: -
Fix post-flight orientation computation when processing
TeleMega and EasyMega eeprom data files.
-
Capture complete eeprom data even when there are invalid
entries in the data. This keeps reading eeprom contents and
writing the associated .eeprom file when an error is detected.
-
We spent a bunch of time trying to improve our documentation We spent a bunch of time trying to improve our documentation -
HTML versions now have a table of contents on the left side.
-
EasyMini now has its own shorter manual.
@@ -2487,9 +2604,9 @@ Provide links between sections in each document.
-
Lots of minor rewriting and restructuring to avoid
duplication of information
-
F.8. Release Notes for Version 1.6.1Version 1.6.1 includes support for our updated TeleBT v3.0
+ F.13. Release Notes for Version 1.6.1Version 1.6.1 includes support for our updated TeleBT v3.0
product and bug fixes in in the flight software for all our boards
-and ground station interfaces. AltOS New Features: -
+and ground station interfaces.
AltOS New Features: -
Add support for TeleBT v3.0 boards.
-
Add support for uncompressed APRS data, providing support
@@ -2499,7 +2616,7 @@ altitude data.
AltOS Fixes: -
Make TeleDongle and TeleBT more tolerant of data rate
variations from transmitting devices.
-
F.8.2. AltosUI and TeleGPS ApplicationsAltosUI and TeleGPS New Features: F.13.2. AltosUI and TeleGPS ApplicationsAltosUI and TeleGPS New Features: -
Add map to Monitor Idle display. Itâs nice to be able to
verify that maps are working, instead of needing to use
Monitor Flight.
@@ -2537,7 +2654,7 @@ will take longer to respond to changes now.
-
Make Replay Flight run in realtime again. It had been set to
run at 10x speed by mistake.
-
AltosDroid New Features: -
Add offline map support using mapping code from AltosUI.
-
Support TeleDongle (and TeleBT via USB) on devices
@@ -2565,9 +2682,9 @@ Make voice announcements depend on current tab.
-
Compute adjustment to current travel direction while in
motion towards rocket.
-
F.9. Release Notes for Version 1.6Version 1.6 includes support for our updated TeleDongle v3.0
+ F.14. Release Notes for Version 1.6Version 1.6 includes support for our updated TeleDongle v3.0
product and bug fixes in in the flight software for all our boards
-and ground station interfaces. AltOS New Features -
+and ground station interfaces.
AltOS New Features -
Add support for TeleDongle v3.0 boards.
AltOS Fixes -
Donât beep out the continuity twice by accident in idle mode.
@@ -2587,7 +2704,7 @@ interrupt code would occasionally wedge on long transfers
if interrupts were blocked for too long. This affects all
released TeleGPS products; if you have a TeleGPS device,
youâll want to reflash the firmware.
-
F.9.2. AltosUI and TeleGPS ApplicationsAltosUI and TeleGPS New Features F.14.2. AltosUI and TeleGPS ApplicationsAltosUI and TeleGPS New Features -
Compute tilt angle from TeleMega and EasyMega log
files. This duplicates the quaternion-based angle tracking
code from the flight firmware inside the ground station
@@ -2633,9 +2750,9 @@ five seconds these days.
In the Scan Channels code, reset pending flight state
information each time we change channels. This avoids having
flight computers appear on multiple frequencies by accident.
-
F.10. Release Notes for Version 1.5Version 1.5 is a major release. It includes support for our new
+ F.15. Release Notes for Version 1.5Version 1.5 is a major release. It includes support for our new
EasyMega product, new features and bug fixes in in the flight
-software for all our boards and the AltosUI ground station AltOS New Features -
+software for all our boards and the AltosUI ground station
AltOS New Features -
Add support for EasyMega boards.
-
Make the APRS SSID be configurable. This lets you track
@@ -2669,7 +2786,7 @@ the delay, but become bad before the delay expires.
Allow negative numbers in pyro configuration values. This
lets you specify things like descending speed or
deceleration.
-
F.10.2. AltosUI and TeleGPS ApplicationsAltosUI and TeleGPS New Features F.15.2. AltosUI and TeleGPS ApplicationsAltosUI and TeleGPS New Features -
Support telemetry baud rate selection. Adds menus to
the flight monitoring and configuration for baud rate
selection.
@@ -2686,18 +2803,18 @@ Make the Graph button on the landed tab w
Make tests for Java on Windows a bit smarter, and also
provide the user with the option to skip installing Java for
cases where we just canât figure out what version is installed.
-
F.11. Release Notes for Version 1.4.2Version 1.4.2 is a minor release. It fixes Java-related install issues on
-Windows F.11.1. AltosUI and TeleGPS ApplicationsWindows Install Fixes F.16. Release Notes for Version 1.4.2Version 1.4.2 is a minor release. It fixes Java-related install issues on
+Windows F.16.1. AltosUI and TeleGPS ApplicationsWindows Install Fixes -
Checks for Java installation data in more registry locations.
-
Allows user to bypass Java installation in case the
detection fails.
-
F.12. Release Notes for Version 1.4.1Version 1.4.1 is a minor release. It fixes install issues on
+ F.17. Release Notes for Version 1.4.1Version 1.4.1 is a minor release. It fixes install issues on
Windows and provides the missing TeleMetrum V2.0 firmware. There
arenât any changes to the firmware or host applications at
all. All Windows users will want to upgrade to get the signed
driver, but Mac and Linux users who do not need the TeleMetrum
-V2.0 firmware image will not need to upgrade. F.12.1. AltosUI and TeleGPS Applications:Windows Install Fixes -
+V2.0 firmware image will not need to upgrade.
F.17.1. AltosUI and TeleGPS Applications:Windows Install Fixes -
Provide signed Windows driver files. This should avoid any need to
disable driver signature checking on Windows 7 or 8.
-
@@ -2715,9 +2832,9 @@ packages for Linux, Mac and Windows.
Include Google Application Key for map downloading. The 1.4
release didnât have this key in the released version of the
software, making map downloading fail for most people.
-
F.13. Release Notes for Version 1.4Version 1.4 is a major release. It includes support for our new
+ F.18. Release Notes for Version 1.4Version 1.4 is a major release. It includes support for our new
TeleGPS product, new features and bug fixes in in the flight
-software for all our boards and the AltosUI ground station AltOS new features: -
+software for all our boards and the AltosUI ground station
AltOS new features: -
Add support for TeleGPS boards.
-
Make the beeper tone configurable, making it
@@ -2747,7 +2864,7 @@ number to 2 on TeleMega and TeleMetrum v2.
-
Fix u-Blox GPS driver to mark course and speed data
as being present.
-
F.13.2. AltosUI ApplicationAltosUI new features: F.18.2. AltosUI ApplicationAltosUI new features: -
Add zooming and new content types (terrain and road
maps) to map view. Change map storage format from
PNG to Jpeg, which saves a huge amount of disk
@@ -2804,12 +2921,12 @@ Handle TeleMetrum and TeleMini eeprom files
generated with pre-1.0 firmware. Those ancient
versions didnât report the log format, so just use
the product name instead.
-
F.13.3. TeleGPS ApplicationF.18.3. TeleGPS Application-
New application designed for use with TeleGPS boards.
-
Shares code with AltosUI, mostly just trimmed down
to focus on TeleGPS-related functions.
-
Documentation changes: -
Re-create the drill template images; they should
print correctly from Firefox at least. Ship these as
individual PDF files so theyâre easy to print.
@@ -2817,8 +2934,8 @@ individual PDF files so theyâre easy to print.
Add a description of the Apogee Lockout setting,
which prevents the apogee charge from firing for a
configurable amount of time after boost.
-
F.14. Release Notes for Version 1.3.2Version 1.3.2 is a minor release. It includes small bug fixes for
-the TeleMega flight software and AltosUI ground station F.19. Release Notes for Version 1.3.2Version 1.3.2 is a minor release. It includes small bug fixes for
+the TeleMega flight software and AltosUI ground station AltOS fixes: -
On TeleMega, limit number of logged GPS status
information to 12 satellites. Thatâs all there is
room for in the log structure.
@@ -2828,7 +2945,7 @@ position and keeps sending that if we lose GPS
lock. Marks locked/unlocked by sending L/U in the
APRS comment field along with the number of sats in
view and voltages.
-
F.14.2. AltosUI ApplicationAltosUI fixes: F.19.2. AltosUI ApplicationAltosUI fixes: -
If the TeleMega flight firmware reports that it has
logged information about more than 12 satellites,
donât believe it as the log only holds 12 satellite
@@ -2841,8 +2958,8 @@ data.
Use letters (A, B, C, D) for alternate pyro channel
names instead of numbers (0, 1, 2, 3) in the Fire
Igniter dialog.
-
F.15. Release Notes for Version 1.3.1Version 1.3.1 is a minor release. It improves support for
-TeleMega, TeleMetrum v2.0, TeleMini v2.0 and EasyMini. F.20. Release Notes for Version 1.3.1Version 1.3.1 is a minor release. It improves support for
+TeleMega, TeleMetrum v2.0, TeleMini v2.0 and EasyMini. AltOS new features: -
Improved APRS mode. Now uses compressed position
format for smaller data size, improved precision and
to include altitude data as well as latitude and
@@ -2864,7 +2981,7 @@ 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.
-
F.15.2. AltosUI ApplicationAltosUI new features: F.20.2. AltosUI ApplicationAltosUI new features: -
Display additional TeleMega sensor values in real
units. Make all of these values available for
plotting. Display TeleMega orientation value in the
@@ -2878,8 +2995,8 @@ 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.
-
F.16. Release Notes for Version 1.3Version 1.3 is a major release. It adds support for TeleMega,
-TeleMetrum v2.0, TeleMini v2.0 and EasyMini. F.21. Release Notes for Version 1.3Version 1.3 is a major release. It adds support for TeleMega,
+TeleMetrum v2.0, TeleMini v2.0 and EasyMini. AltOS new features: -
Add STM32L processor support. This includes
enhancements to the scheduler to support products
with many threads.
@@ -2903,7 +3020,7 @@ accelerometer, Invensense MPU6000 3-axis
accelerometer + 3 axis gyro, Honeywell HMC5883
3-axis magnetic sensor and the TI CC1120 and CC115L
digital FM transceivers
-
F.16.2. AltosUI ApplicationAltosUI new features: F.21.2. AltosUI ApplicationAltosUI new features: -
Support TeleMega, TeleMetrum v2.0, TeleMini v2.0 and
EasyMini telemetry and log formats.
AltosUI fixes: -
@@ -2916,9 +3033,9 @@ Add Download button to menu bar.
-
Save the last log directory and offer that as the
default for new downloads
-
F.17. Release Notes for Version 1.2.1Version 1.2.1 is a minor release. It adds support for TeleBT and
+ F.22. Release Notes for Version 1.2.1Version 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. AltOS new features: -
+AltosUI and fixes some bugs in the AltOS firmware.
AltOS new features: AltOS fixes: -
In TeleMini recovery mode (when booted with the
@@ -2938,7 +3055,7 @@ Adjusted the automatic gain control parameters that
affect receive performance for TeleDongle. Field
tests indicate that this may improve receive
performance somewhat.
-
F.17.2. AltosUI ApplicationAltosUI application new features: F.22.2. AltosUI ApplicationAltosUI application new features: -
Make the initial position of the AltosUI top level
window configurable. Along with this change, the
other windows will pop up at sensible places now,
@@ -2972,15 +3089,15 @@ progress. Unfortunately, we donât know how many
blocks will need to be downloaded, but at least it
isnât just sitting there doing nothing for a long
time.
-
-
First version of this application
-
F.18. Release Notes for Version 1.2Version 1.2 is a major release. It adds support for MicroPeak
-and the MicroPeak USB adapter. F.23. Release Notes for Version 1.2Version 1.2 is a major release. It adds support for MicroPeak
+and the MicroPeak USB adapter. AltOS New Features: -
Add MicroPeak support. This includes support for the
ATtiny85 processor and adaptations to the core code
to allow for devices too small to run the
multi-tasking scheduler.
-
F.18.2. AltosUI and MicroPeak ApplicationNew Features: F.23.2. AltosUI and MicroPeak ApplicationNew Features: -
Added MicroPeak application
AltosUI and MicroPeak fixes: -
Distribute Mac OS X packages in disk image (.dmg)
@@ -2991,11 +3108,11 @@ libraries to ensure that upgrades work properly, and
to allow for multiple Altus Metrum software packages
to be installed in the same directory at the same
time.
-
F.19. Release Notes for Version 1.1Version 1.1.1 is a bug-fix release. It fixes a couple of bugs
+ F.24. Release Notes for Version 1.1Version 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 file export issue, and for suggesting the
-addition of the Ground Distance value in the Descent tab. AltOS fixes: -
+addition of the Ground Distance value in the Descent tab.
AltOS fixes: -
TeleMetrum v1.0 boards use the AT45DB081D flash
memory part to store flight data, which is different
from later TeleMetrum boards. The AltOS v1.1 driver
@@ -3004,7 +3121,7 @@ impossible to delete flight data or update
configuration values. This bug doesnât affect newer
TeleMetrum boards, and it doesnât affect the safety
of rockets flying version 1.1 firmware.
-
AltosUI new features: -
The âDescentâ tab displays the range to the rocket,
which is a combination of the over-the-ground
distance to the rockets current latitude/longitude
@@ -3033,8 +3150,8 @@ things like battery voltage. The code that picked
which kinds of data to fetch from the flight
computer was missing a check for TeleMini when
deciding whether to fetch the analog sensor data.
-
F.20. Release Notes for Version 1.1Version 1.1 is a minor release. It provides a few new features
-in AltosUI and the AltOS firmware and fixes bugs. AltOS Firmware New Features: F.25. Release Notes for Version 1.1Version 1.1 is a minor release. It provides a few new features
+in AltosUI and the AltOS firmware and fixes bugs. AltOS Firmware New Features: -
Add apogee-lockout value. Overrides the apogee
detection logic to prevent incorrect apogee charge
firing.
@@ -3054,7 +3171,7 @@ packets was from 320ms ago.
Fix a bug which caused the old received telemetry
packets to be retransmitted over the USB link when
the radio was turned off and back on.
-
AltosUI New Features: -
Make the look-n-feel configurable, providing a choice from
the available options.
-
@@ -3108,8 +3225,8 @@ the flight monitoring window. This eliminates
entries duplicated from the header and adds both
current altitude and pad altitude, which are useful
in Monitor Idle mode.
-
F.21. Release Notes for Version 1.0.1Version 1.0.1 is a major release, adding support for the
-TeleMini device and lots of new AltosUI features F.26. Release Notes for Version 1.0.1Version 1.0.1 is a major release, adding support for the
+TeleMini device and lots of new AltosUI features AltOS New Features -
Add TeleMini v1.0 support.
-
Support operation of TeleMetrum with the antenna pointing
@@ -3144,7 +3261,7 @@ within a fraction of a second. In addition, this approach
allows the baro-only TeleMini device to correctly identify
Mach transitions, avoiding the error-prone selection of a
Mach delay.
-
F.21.2. AltosUI ApplicationAltosUI New Features F.26.2. AltosUI ApplicationAltosUI New Features -
Add main/apogee voltage graphs to the data
plot. This provides a visual indication if the
igniters fail before being fired.
@@ -3188,8 +3305,8 @@ waits indefinitely for the remote device to appear,
providing a cancel button should the user get
bored. This is necessary as the TeleMini can only be
placed in "Idle" mode if AltosUI is polling it.
-
F.22. Release Notes for Version 0.9.2Version 0.9.2 is an AltosUI bug-fix release, with no firmware
-changes. F.27. Release Notes for Version 0.9.2Version 0.9.2 is an AltosUI bug-fix release, with no firmware
+changes. AltosUI fixes: -
Fix plotting problems due to missing file in the Mac
OS install image.
-
@@ -3197,8 +3314,8 @@ Always read whole eeprom blocks, mark empty records
invalid, display parsing errors to user.
-
Add software version to Configure AltosUI dialog
-
F.23. Release Notes for Version 0.9Version 0.9 adds a few new firmware features and accompanying
-AltosUI changes, along with new hardware support. F.28. Release Notes for Version 0.9Version 0.9 adds a few new firmware features and accompanying
+AltosUI changes, along with new hardware support. -
Support for TeleMetrum v1.1 hardware. Sources for the flash
memory part used in v1.0 dried up, so v1.1 uses a different
part which required a new driver and support for explicit
@@ -3215,12 +3332,12 @@ Previous versions used a telemetry packet format that
provided only 8 bits for the device serial number. This
change requires that both ends of the telemetry link be
running the 0.9 firmware or they will not communicate.
-
F.23.2. AltosUI ApplicationF.28.2. AltosUI Application-
Support for telemetry format changes.
-
Support for multiple flight logs.
-
F.24. Release Notes for Version 0.8Version 0.8 offers a major upgrade in the AltosUI
-interface. F.24.1. AltosUI Application:F.29. Release Notes for Version 0.8Version 0.8 offers a major upgrade in the AltosUI
+interface. F.29.1. AltosUI Application:-
Post-flight graphing tool. This lets you explore the
behaviour of your rocket after flight with a scroll-able and
zoom-able chart showing the altitude, speed and acceleration
@@ -3259,8 +3376,8 @@ automatically connect to it and prepare to monitor a flight.
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.
-
F.25. Release Notes for Version 0.7.1Version 0.7.1 is the first release containing our new
-cross-platform Java-based user interface. F.25.1. AltosUI ApplicationF.30. Release Notes for Version 0.7.1Version 0.7.1 is the first release containing our new
+cross-platform Java-based user interface. F.30.1. AltosUI Application-
Receive and log telemetry from a connected TeleDongle
device. All data received is saved to log files named with
the current date and the connected rocket serial and flight
|