![easymega v1.0 top](easymega-v1.0-top.jpg)
![easymega v1.0 top](easymega-v1.0-top.jpg)
X-Git-Url: https://git.gag.com/?a=blobdiff_plain;f=AltOS%2Fdoc%2Faltusmetrum.html;h=8773af2c7e1ac5256d7974270fcfeb71d449fd54;hb=1a14aa87da04b3112e39469a90f76f6b3cf46e47;hp=fc3719ce134d7c1c63f09c699a047eba6feac542;hpb=f3bceb1ae0246943602c37d3649e3967df3643b9;p=web%2Faltusmetrum diff --git a/AltOS/doc/altusmetrum.html b/AltOS/doc/altusmetrum.html index fc3719c..8773af2 100644 --- a/AltOS/doc/altusmetrum.html +++ b/AltOS/doc/altusmetrum.html @@ -4,9 +4,9 @@ - + - +
Copyright © 2018 Bdale Garbee and Keith Packard
+Copyright © 2021 Bdale Garbee and Keith Packard
This document is released under the terms of the Creative Commons ShareAlike 3.0 License
@@ -347,6 +363,7 @@ on-board circuitry will charge the battery whenever it is plugged in, because the on-off switch does NOT control the charging circuitry. The Lithium Polymer +EasyTimer, TeleMini and EasyMini battery can be charged by disconnecting it from the board and plugging it into a standalone @@ -356,6 +373,7 @@ USB power source.You can also choose to use another battery with +EasyTimer and EasyMini, anything supplying between 4 and 12 volts should work fine (like a standard 9V battery), but if you are planning to fire pyro charges, ground testing is required to verify that @@ -666,9 +684,9 @@ stored in on-board flash.
Additional Igniters
four very short beeps
Continuity indication for the four additional pyro -channels on TeleMega and EasyMega. One high tone for -no continuity, one low tone for continuity. These are +
Continuity indication for the additional pyro +channels on TeleMega, EasyMega and EasyTimer. One high tone for +no continuity, one low tone for continuity. On TeleMega and EasyMegay, these are produced after the continuity indicators for the two primary igniter channels.
For flight computers with accelerometers (TeleMetrum, -EasyMega and TeleMega), the mode is selected by the +EasyMega, TeleMega and EasyTimer), the mode is selected by the orientation of the board during the self test interval. If the board is pointing upwards as if ready to fly, it will enter Flight/Pad mode. Otherwise, it will @@ -837,7 +855,7 @@ the primary or system battery!
EasyMini -and TeleMini v2 are +and EasyTimer are designed to use either a lithium polymer battery or any other battery producing between 4 and 12 volts, such as a rectangular 9V @@ -850,6 +868,7 @@ battery.
3
Main
Main pyro channel common connection to battery
Main +
Main pyro channel common connection to battery +
4
5
Apogee
Apogee pyro channel common connection to battery
Apogee +
Apogee pyro channel common connection to battery +
6
2
Apogee
Apogee pyro channel common connection to battery
Apogee +
Apogee pyro channel common connection to battery +
3
4
Main
Main pyro channel common connection to battery
Main +
Main pyro channel common connection to battery +
Left
Top 2
Main
Main pyro channel common connection to battery
Main +
Main pyro channel common connection to battery +
Top 3
Battery
Battery +
Positive external battery terminal
Bottom 2
Apogee
Apogee pyro channel common connection to battery
Apogee +
Apogee pyro channel common connection to battery +
Bottom 3
Top 5
Main
Main pyro channel common connection to battery
Main +
Main pyro channel common connection to battery +
Top 6
Top 7
Apogee
Apogee pyro channel common connection to battery
Apogee +
Apogee pyro channel common connection to battery +
Top 8
Top 9
D
D pyro channel common connection to battery
D +
D pyro channel common connection to battery +
Bottom 1
Bottom 5
A
A pyro channel common connection to battery
A +
A pyro channel common connection to battery +
Bottom 6
Bottom 7
B
B pyro channel common connection to battery
B +
B pyro channel common connection to battery +
Bottom 8
Bottom 9
C
C pyro channel common connection to battery
C +
C pyro channel common connection to battery +
Top 5
Main
Main pyro channel common connection to battery
Main +
Main pyro channel common connection to battery +
Top 6
Top 7
Apogee
Apogee pyro channel common connection to battery
Apogee +
Apogee pyro channel common connection to battery +
Top 8
Top 9
D
D pyro channel common connection to battery
D +
D pyro channel common connection to battery +
Bottom 1
Bottom 5
A
A pyro channel common connection to battery
A +
A pyro channel common connection to battery +
Bottom 6
Bottom 7
B
B pyro channel common connection to battery
B +
B pyro channel common connection to battery +
Bottom 8
Bottom 9
C
C pyro channel common connection to battery
C +
C pyro channel common connection to battery +
EasyTimer is built on a 0.8 inch by 1½ inch circuit board. It’s +designed to fit in a 24mm coupler tube.
+EasyTimer is designed to control events during ascent. It has +an accelerometer and gyroscope that can measure acceleration +and rotation and compute speed and tilt angle. EasyTimer has +two pyro channels which can be configured to fire at various +points during flight. Because EasyTimer has no barometric +sensor, it cannot be used to fire recovery charges at apogee +or during descent. EasyTimer is configured using the AltosUI +application which is available for Linux, Mac OS X and Windows.
+EasyTimer has two sets of four screw terminals near +one end of the board. Using the picture above, the top +four have connections for pyro channel B and an +external battery and the bottom four have connections +for pyro circuit A and the power switch. Counting from +the left, the connections are as follows:
+Terminal # | +Terminal Name | +Description | +
---|---|---|
Top 1 |
+B - |
+Pyro channel B connection to pyro circuit |
+
Top 2 |
+B + |
+Pyro channel B common connection to battery + |
+
Top 3 |
+Battery + |
+Positive external battery terminal |
+
Top 4 |
+Battery - |
+Negative external battery terminal |
+
Bottom 1 |
+A - |
+Pyro channel A connection to pyro circuit |
+
Bottom 2 |
+A + |
+Pyro channel A common connection to battery + |
+
Bottom 3 |
+Switch Output |
+Switch connection to flight computer |
+
Bottom 4 |
+Switch Input |
+Switch connection to positive battery terminal |
+
There are two possible battery connections on +EasyTimer. 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 +Polymer batteries sold by Altus Metrum.
+The other is a pair of screw terminals marked 'Battery ++' and 'Battery -'. Connect a battery from 4 to 12 +volts to these terminals, being careful to match polarity.
+Because EasyTimer allows for batteries other than the +standard Altus Metrum Lithium Polymer cells, it cannot +incorporate a battery charger circuit. Therefore, when +using a Litium Polymer cell, you’ll need an external +charger. These are available from Altus Metrum, or +from Spark Fun.
+As 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 +lead to the per-channel pyro circuit connection.
+To connect the negative pyro battery terminal to EasyTimer +ground, connect it to the negative external battery +connection, top terminal 4.
+Connecting the switched positive battery terminal to the pyro +charges must be done separate from EasyTimer, by soldering +them together or using some other connector. Note that for +safety, you must put a switch between the pyro battery and +the rest of the circuit!
+The other lead from each pyro charge is then inserted into +the appropriate per-pyro channel screw terminal (top +terminal 1 for pyro channel A charge, bottom terminal 1 for +pyro channel B charge).
+As explained above, an external active switch requires three +connections, one to the positive battery terminal, one to +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.
+A typical installation involves attaching @@ -1869,10 +2053,10 @@ cable terminating in a U.FL connector.
In the US, you need an amateur radio license @@ -1881,14 +2065,14 @@ 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 run a TeleMetrum, TeleMega -or EasyMega for hours. +alkaline battery, and will run a TeleMetrum, TeleMega, +EasyMega or EasyTimer for hours. A 110mAh battery weighs less than a triple A battery and is a good choice for use with @@ -1909,7 +2093,7 @@ 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 @@ -2007,7 +2191,7 @@ reflector of Arrow antennas.
Our software makes it easy to log the data from each flight, both the telemetry received during the flight @@ -2030,7 +2214,7 @@ or just viewed on your local disk with a web browser.
We have designed and prototyped several âcompanion boardsâ that can attach to the companion connector on @@ -2060,13 +2244,13 @@ evolves!
The AltosUI program provides a graphical user interface for @@ -2078,7 +2262,7 @@ chapter is split into sections, each of which documents one of the tasks provided from the top-level toolbar.
Selecting this item brings up a dialog box listing all of the connected TeleDongle devices. When you choose @@ -2090,7 +2274,7 @@ device.
All telemetry data received are automatically recorded @@ -2162,12 +2346,12 @@ raw telemetry values in one place in a spreadsheet-like format.
The 'Launch Pad' tab shows information used to decide when the @@ -2239,12 +2423,12 @@ positions to improve the accuracy of the fix.
This tab is shown during Boost, Fast and Coast @@ -2271,12 +2455,12 @@ caused by wiring which comes loose under high acceleration.
Once the rocket has reached apogee and (we hope) @@ -2318,12 +2502,12 @@ firing.
Once the rocket is on the ground, attention switches @@ -2364,12 +2548,12 @@ bring up a graph window for the current flight.
The table view shows all of the data available from the @@ -2380,12 +2564,12 @@ information about the signal being received from the satellites.
When the TeleMetrum has a GPS fix, the Site Map tab @@ -2423,12 +2607,12 @@ before you leave home; check out Load Maps.
TeleMega includes four additional programmable pyro @@ -2441,7 +2625,7 @@ status.
The altimeter records flight data to its internal flash memory. @@ -2483,7 +2667,7 @@ 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 @@ -2499,7 +2683,7 @@ Check
Select this button and you are prompted to select a flight record file, either a .telem file recording telemetry data or a @@ -2516,12 +2700,12 @@ Use saved flight data in .eeprom files for graphing where possible.
opened.By default, the graph contains acceleration (blue), @@ -2539,12 +2723,12 @@ plot.
This selects which graph elements to show, and, at the @@ -2580,24 +2764,24 @@ value smooths the data more.
Shows overall data computed from the flight.
Shows a satellite image of the flight area @@ -2625,7 +2809,7 @@ the flight path at that point.
This tool takes the raw data files and makes them available for external analysis. When you select this @@ -2640,7 +2824,7 @@ It has a selector to choose between CSV and KML file formats.
This is a text file containing the data in a form suitable for import into a spreadsheet or other @@ -2660,7 +2844,7 @@ both pressure, altitude and height above pad units.
This is the format used by Google Earth to provide an overlay within that application. With this, you can @@ -2670,12 +2854,12 @@ in 3D.
Select this button and then select either an altimeter or @@ -2723,7 +2907,7 @@ lost.
The rest of the dialog contains the parameters to be configured.
This sets the altitude (above the recorded pad altitude) at which the 'main' igniter will fire. The @@ -2735,7 +2919,7 @@ apogee charge fires.
When flying redundant electronics, it’s often important to ensure that multiple apogee charges don’t @@ -2748,7 +2932,7 @@ been detected.
Apogee lockout is the number of seconds after launch where the flight computer will not fire the apogee @@ -2779,7 +2963,7 @@ the correct behavior.
This configures which of the frequencies to use for both telemetry and packet command mode. Note that if @@ -2790,7 +2974,7 @@ continue afterwards.
The radios in every Altus Metrum device are calibrated at the factory to ensure that they transmit and @@ -2804,7 +2988,7 @@ completely.
Enables the radio for transmission during flight. When disabled, the radio will not @@ -2812,7 +2996,7 @@ transmit anything during flight at all.
This sets the modulation bit rate for data transmission for both telemetry and packet @@ -2826,7 +3010,7 @@ rate specified here.
How often to transmit GPS information via APRS (in seconds). When set to zero, APRS @@ -2842,7 +3026,7 @@ other telemetry during that time.
Which SSID to report in APRS packets. By default, this is set to the last digit of the @@ -2851,7 +3035,7 @@ value from 0 to 9.
Whether to send APRS data in Compressed or Uncompressed format. Compressed format is @@ -2865,7 +3049,19 @@ you fly to see which to use.
The delay from the top of the minute before sending +the first APRS packet of the minute. Coordinating +values for this parameter between multiple devices can +allow a single receiver to reliably receive APRS +packets from multiple devices. Note that this offset only +takes effect while the GPS signal is locked so that the +transmitting device knows the current time.
+This sets the call sign included in each telemetry packet. Set this as needed to @@ -2873,7 +3069,7 @@ conform to your local radio regulations.
This sets the space (in kilobytes) allocated for each flight log. The available space will @@ -2884,7 +3080,7 @@ flights.
This configuration parameter allows the two standard ignitor channels (Apogee and Main) to be used in different @@ -2914,11 +3110,16 @@ setting during descent. The 'apogee' channel is fired first, followed after a two second delay by the 'main' channel.
+This fires the 'main' channel when the first motor +burns out and fires the 'apogee' charge at apogee.
+Because they include accelerometers, TeleMetrum, TeleMega and EasyMega are @@ -2932,21 +3133,21 @@ with the antenna pointing aft instead.
In this mode, the antenna end of the flight -computer must point forward, in line with the -expected flight path.
+In this mode, the antenna (or beeper, for devices +without an antenna) of the flight computer must point +forward, in line with the expected flight path.
In this mode, the antenna end of the flight -computer must point aft, in line with the -expected flight path.
+In this mode, the antenna (or beeper, for devices +without an antenna) end of the flight computer must +point aft, in line with the expected flight path.
The beeper on all Altus Metrum flight computers works best at 4000Hz, however if you @@ -2958,7 +3159,7 @@ value.
This sets the amount of motion that TeleGPS needs to see before logging the new @@ -2967,7 +3168,7 @@ skipped, which saves storage space.
The interval between TeleGPS position reports, both over the air and in the log. Increase @@ -2977,7 +3178,7 @@ in the log.
This opens a separate window to recalibrate the accelerometers. Follow the instructions, orienting the @@ -2992,17 +3193,17 @@ calibration values.
This opens a separate window to configure the -additional pyro channels available on TeleMega -and EasyMega. One column is presented for +additional pyro channels available on TeleMega, +EasyMega and EasyTimer. One column is presented for each channel. Each row represents a single parameter, if enabled the parameter must meet the specified test for the pyro channel to be @@ -3052,14 +3253,16 @@ during these phases of the flight.
Select a value, and then choose whether the height -above the launch pad should be above or below that value.
+above the launch pad should be above or below that value. Note that +because EasyTimer has only a low-range accelerometer and no barometer, +this value will not be very reliable on that device.TeleMega and EasyMega contain a 3-axis gyroscope and -accelerometer which is used to compute the orientation of the -rocket. A record of orientations over the last 0.64 seconds is kept -and the largest value within this period is compared with the +
TeleMega, EasyMega and EasyTimer contain a 3-axis +gyroscope and accelerometer which is used to compute the orientation +of the rocket. A record of orientations over the last 0.64 seconds is +kept and the largest value within this period is compared with the specified value. Note that the tilt angle is not the change in angle from the launch pad, but rather absolute relative to gravityâthe 3-axis accelerometer is used to compute the angle of the rocket on the @@ -3118,6 +3321,19 @@ to get the correct behavior.
+ |
++Firmware versions older than 1.9.8 cannot use times longer +than 327.67 seconds. Update firmware if you need a longer time. + | +
+ |
++Firmware versions older than 1.9.8 cannot use delays longer +than 327.67 seconds. Update firmware if you need a longer delay. + | +
The flight software tracks the flight @@ -3174,14 +3407,14 @@ than 200m/s. Ascent rate will greater than zero. Vertical acceleration will be less than zero.
Drogue. The rocket has reached apogee and -is heading back down, but is above the -configured Main altitude. Ascent rate will be less than zero during -this state. Vertical acceleration will be negative until the rocket -reaches a terminal descent rate, at which point Vertical -acceleration will be zero. Both Ascent rate and Vertical +
Drogue. The rocket has reached apogee and is heading back down, but +is above the configured Main altitude. Ascent rate will be less +than zero during this state. Vertical acceleration will be negative +until the rocket reaches a terminal descent rate, at which point +Vertical acceleration will be zero. Both Ascent rate and Vertical acceleration are very noisy in this state, so be careful when -trying to use them to control pyro channels.
+trying to use them to control pyro channels. This state selection +is not available on EasyTimer.Main. The rocket is still descending, and @@ -3191,7 +3424,7 @@ zero as the rocket slows from drogue descent to main descent, but it will settle down to a zero value once the rocket has reached the terminal velocity under the main chute. Ascent rate and Vertical acceleration should be much less noisy once the main chute has -deployed.
+deployed. This state selection is not available on EasyTimer.Landed. The rocket is no longer moving.
@@ -3215,19 +3448,19 @@ 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 @@ -3251,7 +3484,7 @@ are reasonable
AltosUI logs all telemetry data and saves all flash data to this directory. This @@ -3268,7 +3501,7 @@ files.
This value is transmitted in each command packet sent from TeleDongle and received from @@ -3290,7 +3523,7 @@ sensitive.
This switches between metric units (meters) and imperial units (feet and miles). This @@ -3303,7 +3536,7 @@ always produced in metric units.
This causes all communication with a connected device to be dumped to the console from which @@ -3314,7 +3547,7 @@ various serial communication issues.
Selects the set of fonts used in the flight monitor window. Choose between the small, @@ -3322,7 +3555,7 @@ medium and large sets.
Switches between the available Java user interface appearances. The default selection @@ -3331,7 +3564,7 @@ appearance for the target platform.
Selects the initial position for the main AltosUI window that includes all of the @@ -3339,7 +3572,7 @@ command buttons.
Sets the number of map 'tiles' kept in memory while the application is running. More tiles @@ -3348,7 +3581,7 @@ around the map faster.
This brings up a dialog where you can configure the set of frequencies shown in the @@ -3362,12 +3595,12 @@ menus.
Select this button and then select a TeleDongle or @@ -3418,7 +3651,7 @@ will be lost.
to be configured.This configures the frequency to use for both telemetry and packet command mode. Set this @@ -3431,7 +3664,7 @@ value used here.
The radios in every Altus Metrum device are calibrated at the factory to ensure that they @@ -3443,7 +3676,7 @@ current value and doesn’t allow any changes.
This lets you match the telemetry and packet link rate from the transmitter. If they don’t @@ -3452,7 +3685,7 @@ match, the device won’t receive any data.
This reprograms Altus Metrum devices with new firmware. @@ -3461,7 +3694,7 @@ and TeleBT v1.0 are all reprogrammed by using another similar unit as a programming dongle (pair programming). TeleMega, EasyMega, TeleMetrum v2 or newer, -EasyMini, TeleBT v3 or newer and TeleDongle v3 +EasyMini, EasyTimer, TeleBT v3 or newer and TeleDongle v3 or newer are all programmed directly over USB (self programming). Please read @@ -3470,12 +3703,12 @@ the directions for flashing devices in
This activates the igniter circuits in the flight @@ -3507,12 +3740,12 @@ igniter.
This listens for telemetry packets on all of the @@ -3525,12 +3758,12 @@ later firmware.
Before heading out to a new launch site, you can use @@ -3608,12 +3841,12 @@ you. Try again later.
This brings up a dialog similar to the Monitor Flight @@ -3636,7 +3869,7 @@ exactly.
AltosDroid provides the same flight monitoring capabilities as @@ -3654,7 +3887,7 @@ to TeleBT or TeleDongle, 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 @@ -3666,7 +3899,7 @@ which you can download and install the application.
Before using TeleBT with AltosDroid, make sure the internal TeleBT battery is charged. To do this, @@ -3679,7 +3912,12 @@ battery fault.
Note that when turning TeleBT on, you may see a brief LED +flash, but there will be no "activity" indicated until you +pair with the device from AltosDroid.
+Press the Android 'Menu' button or soft-key to see the configuration options available. Select the 'Connect a @@ -3695,7 +3933,7 @@ list without scanning.
Get a special USB On-the-go adapter cable. These cables have a USB micro-B male connector on one end @@ -3708,7 +3946,7 @@ device doesn’t support USB On-the-go.
The main AltosDroid menu has a selection of operation and configuration options.
@@ -3762,7 +4000,7 @@ the serial number of devices in each airframe.AltosDroid is designed to mimic the AltosUI flight monitoring display, providing separate tabs for each @@ -3857,7 +4095,7 @@ device.
The 'Pad' tab shows information used to decide when the rocket is ready for flight. The first elements @@ -3949,7 +4187,7 @@ device.
The 'Flight' tab shows information used to evaluate and spot a rocket while in flight. It displays speed @@ -4036,7 +4274,7 @@ for a 'GO' status.
The 'Recover' tab shows information used while recovering the rocket on the ground after flight.
@@ -4096,7 +4334,7 @@ the flight.The 'Map' tab shows a map of the area around the rocket being tracked along with information needed to @@ -4119,7 +4357,7 @@ the Recover tab.
AltosDroid always saves every bit of telemetry data it receives. To download that to a computer for use with @@ -4143,7 +4381,7 @@ fundamental modes, âidleâ and âflightâ. Which of these modes the firmware operates in is determined at start up time. For -TeleMetrum, TeleMega and EasyMega, which have accelerometers, the mode is +TeleMetrum, TeleMega, EasyMega and EasyTimer, which have accelerometers, the mode is controlled by the orientation of the rocket (well, actually the board, of course…) at the time power is switched on. If the rocket is ânose upâ, then @@ -4455,12 +4693,19 @@ feedback on performance in higher altitude flights!
TeleMetrum v2 and newer and TeleMega can send APRS if desired, and the -interval between APRS packets can be configured. As each APRS -packet takes a full second to transmit, we recommend an -interval of at least 5 seconds to avoid consuming too much -battery power or radio channel bandwidth. You can configure -the APRS interval using AltosUI; that process is described in -Configure Altimeter.
+interval between APRS packets can be configured. As +each APRS packet takes a full second to transmit, we +recommend an interval of at least 5 seconds to avoid +consuming too much battery power or radio channel +bandwidth. You can configure the time within each +minute that APRS transmits by changing the APRS offset +value. When the GPS signal is locked and knows the +current time, the APRS offset selects the time with +each minute for the first APRS transmission; +subsequent transmissions occur each APRS interval +seconds thereafter. You can configure the APRS +interval and APRS offset using AltosUI; that +process is described in Configure Altimeter.AltOS supports both compressed and uncompressed APRS @@ -4488,7 +4733,7 @@ can have arbitrary text in it. AltOS uses this to send status information as shown in the following table.
3.7V |
|||||||
TeleMega v5.0 |
+MS5607 30km (100k') |
+ADXL375 200g |
+uBlox Max-8Q |
+MPU6000 MMC5983 |
+8MB |
+40mW |
+3.7V |
+
EasyMega v1.0 |
MS5607 30km (100k') |
MMA6555 102g |
@@ -5424,11 +5698,31 @@ production and retired.
- |
3.7V |
|||
EasyTimer v1.0 |
+- |
+16g |
+- |
+BMX160 |
+- |
+- |
+3.7-12V |
+
EasyMotor v2.0 |
+- |
+ADXL375 200g |
+- |
+- |
+- |
+- |
+6.5-15V |
+
2¼ inch (5.62cm) |
38mm coupler |
+||||
EasyTimer |
+Debug USB Battery |
+Pyro A Pyro B Battery |
+0.8 inch (2.03cm) |
+1½ inch (3.81cm) |
+24mm coupler |
+
EasyMotor |
+Debug USB |
++5V Pres GND Switch Battery |
+0.8 inch (2.03cm) |
+1½ inch (3.81cm) |
+24mm coupler |
+
Version 1.9.2
+Version 1.9.9
+This release contains a critical bug fix for a problem +introduced in version 1.9.8 for TeleMega and EasyMega +boards. This problem occurs when using the stored +configuration from 1.9.7 or earlier.
+If you are running 1.9.8 or are upgrading from 1.9.8 on any +version of TeleMega or EasyMega, you must reconfigure all pyro +channels, recalibrate accelerometers, reset the APRS interval, +adjust the beep tone and reset the pyro time.
Fix EasyMega and TeleMega upgrade process from 1.9.7 or +earlier. 1.9.8 introduced larger delay values, which +required modifying the configuration in-place, and the 1.9.8 +version had a flaw which broke the pyro channel config and +all of the config values beyond that in memory, including +APRS interval, IMU accel calibation, beep tone and pyro +time.
+Fix TeleMega v5.0 mag sensor driver. This driver was quite +broken due to developing it in the presence of the magnetic +beeper on the board. Because of that beeper, the values this +sensor records are not accurate. Fortunately, they are not +used for controlling the flight.
+Parse TeleMega v5.0 log files. A missing check in the code +meant that the TeleMega v5.0 log files would cause an error +when attempting to load them. Logs saved with AltosUI +1.9.8 were not affected, only the presentation of the data +was broken.
+Version 1.9.8
+Add support for TeleMega v5.0
+Extend extra pyro channel times to support delay > 327 seconds
+Support ARM devices in Linux binary release
+Add support for TeleMega v5.0
+Show tilt angle in pad and flight tabs
+Show altitude as well as height (useful for TeleGPS)
+Support devices without GPS receivers
+Show error dialog if device open fails
+Version 1.9.7
+Fix TeleGPS logging so that new data are appended to an existing log correctly
+Support Mac OS X 11 (Big Sur)
+Support Monitor Idle on Easy Timer
+Fix TeleMega v4.0 and TeleMetrum v3.0 configuration in Antenna Down mode
+Show launch sites in Load Maps view
+Add IMU header names to CSV files
+Clean up TeleGPS log corruption due to firmware bugs during firmware update
+Support older devices back to Android version 5.1
+Fix a number of issues that could result in app crashes
+Version 1.9.6
+Fix EasyTimer bug where it might mis-detect boost (either +detect it early or not at all) due to small errors in +accelerometer calibration leading to large accumulated error +in speed.
+Adjust self-test of new 9-axis IMU (BMX-160) so that it +doesn’t think the part has a failure when tested sitting +horizontally.
+Version 1.9.5
+Add Booster mode for all dual-deploy altimeters. Select +"Separation & Apogee" mode in AltosUI to fire the 'main' +channel at first motor burnout and the 'apogee' channel at +apogee.
+Improve reliability of stm32l firmware under heavy +load. This was found using Monitor Idle on TeleMega with all +flash slots full of data which would occasionally lock up.
+Fix orientation label in AltosUI for devices with +radios. This makes the orientation say 'Antenna up' and +'Antenna Down' for TeleMetrum and TeleMega again.
+Fix log data for pyro channels which were inhibited (often +because of a tilt limit). They used to report 'fired' as +soon as they were inhibited, which was misleading. Now they +never report as having been fired.
+Allow Igniter Test to fire each igniter more than once.
+Improve performance of Monitor Idle mode by sending less data for each +update.
+Improve Mac OS X install scripts so that they work on +Catalina. This involves sending the user to get Java from +the AdoptOpenJDK project which provides a version that works +with Java applications.
+Make larger dialogs scrollable for use on smaller screens.
+Fix troubles re-flashing EasyMega boards running older +firmware.
+Add TeleMetrum v3.0 firmware to the Windows +AltosUI packages.
+Version 1.9.4
+Fixed firmware for TeleDongle v3.0 and TeleBT v4.0. Version 1.9.3 bricked those +devices requiring them to be opened up to get them working again.
+Fixed firmware for EasyMini v1.0. Changes in the storage +code caused it to use significantly more RAM which made the +interrupt stack smash into other data structures and cause +the device to panic at startup time.
+Add TeleMetrum v3.0 firmware to the Linux and Mac OSX +AltosUI packages.
+Version 1.9.3
+Add APRS offset. Allows multiple APRS transmitters to coordinate when +transmission occurs to allow them to share a frequency.
+Fix max log size. Flight computer storage is erased in 64kB chunks. Adjust max +log size to be a multiple of this size.
+Check flight erasing more carefully. Handle interrupting erasing in the +middle.
+Add EasyTimer support.
+Add configuration support for APRS offset.
+Adjust flight log sizes to be a multiple of the flight +computer erase block size.
+Report barometric pad altitude in Pad tab for TeleMini.
+Version 1.9.2
+Add support for TeleMega v4.0
Version 1.9.1
Version 1.9
Version 1.8.7
Version 1.8.6
Version 1.8.5 includes fixes to the ground software support for TeleBT v4, along with a few other minor updates.
Version 1.8.4 includes support for EasyMini version 2.0
Version 1.8.3 includes support for TeleMega version 3.0 along with two important flight computer fixes. This version also @@ -5812,7 +6465,7 @@ better and some updates to graph presentation and data downloading.
Version 1.8.2 includes support for TeleGPS version 2.0 along with accelerometer recalibration support in AltosUI.
@@ -5913,7 +6566,7 @@ with accelerometer recalibration support in AltosUI. analyzing saved data files.AltOS New Features
AltosUI and TeleGPS New Features
Version 1.8.1 includes an important bug fix for Apogee Lockout operation in all flight computers. Anyone using this option @@ -5976,7 +6629,7 @@ above Mach 1.
analyzing saved data files.AltOS Bug Fixes
AltosUI New Features
Version 1.8 includes support for our new TeleBT v4.0 ground station, updates for data analysis in our ground station @@ -6036,7 +6689,7 @@ software and bug fixes in in the flight software for all our boards and ground station interfaces.
AltOS New Features
AltosUI New Features
Version 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
AltosUI New Features
Version 1.6.8 fixes a TeleMega and TeleMetrum v2.0 bug where the device could stop logging data and transmitting @@ -6137,7 +6790,7 @@ telemetry in flight. All TeleMega v1.0, v2.0 and TeleMetrum v2.0 users should update their flight firmware.
AltOS fixes:
AltosUI fixes:
Version 1.6.5 fixes a TeleMega and TeleMetrum v2.0 bug where the device would often stop logging data and transmitting @@ -6201,7 +6854,7 @@ telemetry in flight. All TeleMega v1.0, v2.0 and TeleMetrum v2.0 users should update their flight firmware.
AltOS fixes:
AltosUI fixes:
Version 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:
AltosUI, TeleGPS and AltosDroid New Features:
Version 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:
AltosUI and TeleGPS New Features:
AltosDroid new features:
Version 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:
AltosUI and TeleGPS Fixes:
We spent a bunch of time trying to improve our documentation
Version 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:
AltosUI and TeleGPS New Features:
AltosDroid New Features:
Version 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
AltosUI and TeleGPS New Features
Version 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
AltosUI and TeleGPS New Features
Version 1.4.2 is a minor release. It fixes Java-related install issues on Windows
Windows Install Fixes
Version 1.4.1 is a minor release. It fixes install issues on Windows and provides the missing TeleMetrum V2.0 firmware. There @@ -6958,7 +7611,7 @@ driver, but Mac and Linux users who do not need the TeleMetrum V2.0 firmware image will not need to upgrade.
Windows Install Fixes
Version 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:
AltosUI new features:
Documentation changes:
Version 1.3.2 is a minor release. It includes small bug fixes for the TeleMega flight software and AltosUI ground station
AltOS fixes:
AltosUI fixes:
Version 1.3.1 is a minor release. It improves support for TeleMega, TeleMetrum v2.0, TeleMini v2.0 and EasyMini.
AltOS new features:
AltosUI new features:
Version 1.3 is a major release. It adds support for TeleMega, TeleMetrum v2.0, TeleMini v2.0 and EasyMini.
AltOS new features:
AltosUI new features:
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.
AltOS new features:
AltosUI application new features:
Version 1.2 is a major release. It adds support for MicroPeak and the MicroPeak USB adapter.
AltOS New Features:
New Features:
Version 1.1.1 is a bug-fix release. It fixes a couple of bugs in AltosUI and one firmware bug that affects TeleMetrum @@ -7586,7 +8239,7 @@ the Google Earth file export issue, and for suggesting the addition of the Ground Distance value in the Descent tab.
AltOS fixes:
AltosUI new features:
Version 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:
AltosUI New Features:
Version 1.0.1 is a major release, adding support for the TeleMini device and lots of new AltosUI features
AltOS New Features
AltosUI New Features
Version 0.9.2 is an AltosUI bug-fix release, with no firmware changes.
AltosUI fixes:
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.
Version 0.7.1 is the first release containing our new cross-platform Java-based user interface.