@@ -3317,6 +3353,19 @@ to get the correct behavior.
12.6.20. Configure Pyro Channels
+12.6.21. Configure Pyro Channels
@@ -3317,6 +3353,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. + | +
- Ascending @@ -3349,6 +3398,23 @@ false, then the pyro channel is disabled and will not fire. If the timer expires and all of the other parameters have remained true for the entire time, then the pyro channel is fired. +
+
+
+
+|
+
+ |
++Firmware versions older than 1.9.8 cannot use delays longer +than 327.67 seconds. Update firmware if you need a longer delay. + | +
+
- Flight State
-
The flight software tracks the flight @@ -3880,6 +3946,11 @@ battery fault.
13.3. Connecting to TeleBT over Bluetoothâ¢
++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 device' option and then the 'Scan for devices' entry @@ -4796,7 +4867,267 @@ configurable parameters can be set using AltosUI. Read
-+Appendix B: Handling Precautions
+Appendix B: Example Pyro Channel Configurations
+++++Programming configurable pyro channels on Altus Metrum products that +include them isn’t difficult, but in an attempt to aid understanding +of the configuration interface and help "keep simple things simple", +we offer the following examples of the simplest configurations for +common situations, along with some hints on avoiding unexpected +results.
+++The rich set of conditions provided can be used to configure almost +any pyro event you can imagine, for a wide variety of objectives. +But don’t be fooled! Typical events need only one or a few simple +conditions to be configured for success. A key thing to remember is +that all configured conditions must be true to allow a pyro channel +to fire. Trying to include too many conditions often results in +conflicting rules that never allow a channel to fire. The most +important advice we can offer is, therefore, to try and find the +simplest set of conditions that will do what you need for a given +project.
+++B.1. Two-Stage Flights
+++Successful completion of a two-stage flight often involves +programming of two events. The first is firing a separation +charge, the second is igniting the sustainer’s (primary) +motor.
+++Separation charges are best fired as soon as possible after +the previous stage has completed providing acceleration, to +minimize drag of the sustainer’s coast phase before ignition. +Recovery, whether the remainder of the flight is nominal or +not, usually works best when the stages are separated. So, +the "best" way to configure a pyro channel for a separation +charge is to just set "after motor number". For a 2-stage +project, set this to "1". This will cause the pyro channel +to fire as soon as the firmware’s flight state machine +determines the first motor has burned out.
+++Safe ignition of a sustainer (primary) motor requires that +it happen after the previous stage burns out, while the +airframe remains mostly vertical, and typically after the +sustainer has coasted away from the booster a bit. A good +starting point is thus "after motor number" set the same as +the separation charge, which is "1" for a 2-stage rocket. +Then "angle from vertical less than" set to some +reasonably vertical amount, perhaps 20 degrees. Then "delay +after other conditions" set for the desired duration of coast. +Use simulations to figure out what a reasonable value here is, +but for typical high power rocketry sport flights that aren’t +trying to set records, something like 2 seconds is usually a +good place to start.
+++B.2. Triggered Clusters and Air Starts
+++When an airframe has a cluster of motors, one of which is +"primary" and centered, surrounding by a ring of "secondary" +motors, you may want to use the launch control system to fire the primary motor and use onboard electronics to light +the rest of the cluster as soon as launch is detected. This +is particularly true if the primary motor is significantly +different in geometry and may take longer to come up to +pressure than the secondary motors. In this case, a simple +configuration to light secondary motors is is "time since +boost greater than" enabled and set to "0". There’s +really no point in setting an angle limit since no time has +transpired for the airframe to change orientation.
+++Air starts can use the same simple configuration, but with +the time set to a non-zero value. However, if air starts +are going to light after the airframe leaves the launch rail +or tower, add an "angle from vertical less than" +condition just you would for a 2-stage sustainer to stay safe.
+++B.3. Redundant Apogee
+++When flying a board like TeleMega or EasyMega, it’s easy to +configure a programmable channel to fire a redundant apogee +charge. This is of course not fully redundant, since it’s +always possible that the board itself or its battery could +the the failure source, but far more often, pyro events fail +due to broken wires, bad connectors, or bad e-matches… so +firing two charges from one board can add useful redundancy.
+++The simplest configuration for redundant apogee is "flight +state after" set to "drogue", and then "delay after other +conditions" set to a second or two.
+++B.4. Redundant Main
+++Similarly to apogee, configuring a redundant main charge can +provide useful redundancy. What we want is to configure an +altitude for deployment lower than the primary main deploy +altitude, and then ensure we only trigger on that condition +while descending.
+++The simplest configuration for redundant main is "flight +state after" set to "drogue", which will ensure we’re in to +the descent phase, then "height less than" set to a number +lower than you’ve chosen for the primary main channel +deployment height.
+++B.5. Apogee Above Baro Sensor Limit
+++A question we’ve seen increasingly often is "How does the +Telemega/Easymega detect apogee for flights above 100,000 +feet?" Flights above that height are a bit outside +our original design envelope, but can be made to work… +This is not a simple flight, and the configuration for it +is also not simple, but we think including this information +is important for anyone contemplating such a project with our +electronics!
+++Our flight computers use a Kalman sensor-fusing filter to +estimate the flight state, which consists of three values:
+++-
+
-
+
Height above ground
+
+ -
+
Vertical speed
+
+ -
+
Vertical acceleration
+
+
++Apogee is assumed to be where vertical speed crosses zero.
+++Below 30km altitude (about 100k'), we use both the barometer +and the accelerometer to update the flight state, along with +a basic Newtonian model of motion. That works well, pegging +apogee within a few sensor samples essentially every time.
+++Above 30km, the barometric sensor doesn’t provide useful data, +so we can’t use it to update the flight state. Instead, the +Kalman filter falls back to a single sensor mode, using only +the accelerometer.
+++At all altitudes, we de-sense the barometric data when we +estimate the speed is near or above mach as the sensor is +often subjected to significant transients, which would +otherwise push the flight state estimates too fast and could +trigger a false apogee event.
+++That means the filter is no longer getting the benefit of two +sensors, and relies on just the accelerometer. The trouble +with accelerometers is they’re measuring the derivative of +speed, so you have to integrate their values to compute speed. +Any offset error in acceleration measurement gets constantly +added to that speed.
+++In addition, we assume the axial acceleration is actually +vertical acceleration; our tilt measurements have enough +integration error during coast that we can’t usefully use +that to get vertical acceleration. Because we don’t live in +an inertial frame, that means we’re mis-computing the total +acceleration acting on the airframe as we have to add gravity +into the mix, and simply adding that to the axial acceleration +value doesn’t generate the right value.
+++The effect of this is to under-estimate apogee when you base +the computation purely on acceleration as the rocket flies a +parabolic path.
+++For flights near 100k', all of this works pretty well - +you’ve got the flight state estimates adjusted using the +barometric sensor up to 30km, then you’re flying on inertial +data to apogee.
+++For flights well above 100k', it’s not great; you’re usually +going fast enough through 100k' that the baro sensor is still +de-sensed through the end of its useful range, so the flight +state estimates are not as close. After that, as you’re flying +purely on accelerometer data, there’s no way to re-correct the +state, so the apogee estimates can be off by quite a bit.
+++In the worst cases we have seen, the baro sensor data was +wildly incorrect above mach due to poor static port design, +leaving the state estimate of speed across the 30km boundary +way off and causing the apogee detection to happen far from +the correct time.
+++The good news is that correctly determining apogee is not +really all that important at high altitudes; there’s so little +density that a drogue will have almost no drag anyways. Data +from customer flights shows a very parabolic path down to +about 50-60k feet, even with a recovery system deployed.
+++So, what we recommend is to set up two apogee plans:
+++-
+
-
+
Use the built-in apogee detection, but add a +significant delay (as much as 30 seconds). This +will probably fire near enough to apogee to not +have a significant impact on the maximum height +achieved.
+
+ -
+
Add a back-up apogee which fires after apogee +when the height is below about 20-25km. This +way, if the flight isn’t nominal, and the sustainer +ends up reaching apogee in dense air, you aren’t +hoping the chutes come out before it gets going +too fast. And, you get a second pyro channel firing +at that altitude even if it reached a higher +altitude before.
+
+
++You can wire these two pyro channels to the same pyro device; +you just need to make sure they’re wired + to + and - to - +(the manual shows which screw terminals are which).
+++The bottom line is that flights to altitudes modestly above +the range of the baro sensor with Altus Metrum products can +be accomplished safely, but flying "way high" (like 300k') +demands a deployment mechanism which doesn’t solely rely on +altimeters (like ours) which are designed for modest altitude +rocketry. Flights to those altitudes also probably need +active stabilization to make sure they follow the prescribed +trajectory and stay inside their waiver.
++Appendix C: Handling Precautions
All Altus Metrum products are sophisticated electronic devices. @@ -4854,7 +5185,7 @@ charge gasses.
-Appendix C: Updating Device Firmware
+Appendix D: Updating Device Firmware
TeleMega, TeleMetrum v2 and newer, EasyMega, EasyMini and TeleDongle v3 @@ -4867,6 +5198,16 @@ programming). It’s important to recognize which kind of devices you have before trying to reprogram them.
++TeleMini v3 can be updated directly over USB, but has no USB connector +on the board. Instead, the USB signals are present on a row of 6 +holes adjacent to the copyright assertion in the silk screen. Thus, +updating firmware on TeleMini v3 requires making up a special cable, +after which you can treat it just like TeleMetrum or TeleMega. Many +USB cables seem to follow the color code of red is +5V, black is GND, +green is USB +, and white is USB -. On TeleMini v3, pin 3 which has +a square copper pad is ground, pin 1 is USB -, and pin 2 is USB +.
+You may wish to begin by ensuring you have current firmware images. These are distributed as part of the AltOS software bundle that also includes the AltosUI ground station program. @@ -4877,7 +5218,7 @@ download the most recent version from http://www.altusmetrum.org/AltOS/
-C.1. Updating TeleMega, TeleMetrum v2 or newer, EasyMega, EasyMini, TeleDongle v3 or TeleBT v3 Firmware
+D.1. Updating TeleMega, TeleMetrum v2 or newer, TeleMini v3, EasyMega, EasyMini, TeleDongle v3 or TeleBT v3 Firmware
Self-programmable devices are reprogrammed by connecting them to your computer over USB.
@@ -4890,7 +5231,8 @@ the target device. Power up the device.Using a Micro USB cable, connect the target device to your -computer’s USB socket.
+computer’s USB socket. If the target is a TeleMini v3, +make up and attach a special USB cable.Run AltosUI, and select 'Flash Image' from the File menu.
@@ -4923,7 +5265,7 @@ item to check over the configuration.-C.1.1. Recovering From Self-Flashing Failure
+D.1.1. Recovering From Self-Flashing Failure
If the firmware loading fails, it can leave the device unable to boot. Not to worry, you can force the device to @@ -5053,7 +5395,7 @@ piece of wire.
-C.2. Pair Programming
+D.2. Pair Programming
The big concept to understand is that you have to use a TeleMetrum v1.0, TeleBT v1.0 or TeleDongle v0.2 as a @@ -5071,7 +5413,7 @@ version 1.0.1 or later will work, version 1.2.1 may have improved receiver performance slightly.
-C.2.1. Updating TeleMetrum v1.x Firmware
+D.2.1. Updating TeleMetrum v1.x Firmware
- @@ -5147,7 +5489,7 @@ etc.
-C.2.2. Updating TeleMini v1.0 Firmware
+D.2.2. Updating TeleMini v1.0 Firmware
You’ll need a special 'programming cable' to reprogram the TeleMini v1.0. You can make your own @@ -5223,7 +5565,7 @@ the TeleDongle, or letting it come up in
-C.2.3. Updating TeleDongle v0.2 Firmware
+D.2.3. Updating TeleDongle v0.2 Firmware
Updating TeleDongle v0.2 firmware is just like updating TeleMetrum v1.x or TeleMini v1.0 firmware, but you @@ -5324,7 +5666,100 @@ loose accidentally in flight.
-+Appendix D: Flight Data Recording
+Appendix E: Frequency Calibration
+++++All products that have radio interfaces require calibration of the radio +frequency. Normally, this calibration is done once during the production +process and the resulting cal value is saved into non-volatile memory. The +procedure decribed here should only be used outside of the factory if you +are really convinced the radio calibration is bad, and you have access to +the required tools to do the calibration.
+++Because this procedure is only rarely needed in the field, we have not +written any fancy user interface for doing it .. some interaction with +and careful typing in a command-like style interface are required!
+++E.1. Background Information
+++The radio system on each board uses a quartz crystal to control +a frequency synthesizer that can be programmed to a range of operating +frequencies. While these crystals are very stable, they have an accuracy +specification that means once the base frequency they set is multiplied up +to the typical operating range of our products, any variation also gets +multiplied. The objective of the calibration process is, indirectly, to +measure the actual operating frequency of the crystal and adjust the way +the frequency synthesizer is programmed to account for this variation.
+++The frequency may shift a few tens of Hz over the full operating temperature +range, and it may also shift a bit over time as the crystal ages. But once +properly calibrated, none of those changes are likely to ever cause any +operational problem, as the shift in operating frequency due to these factors +is tiny compared to the bandwidth of our transmitted signal.
+++E.2. Required Equipment
+++The calibration process requires the ability to precisely measure the actual +frequency of a steady CW carrier on or about the intended operating frequency +in the vicinity of 435 MHz.
+++In production, we use an HP 5385A that is locked to a 10 MHz reference that +is in turn locked to GPS, which provides a highly accurate calibration. Any +reasonably accurate frequency counter is likely to be sufficient.
+++You also need a computer with terminal program and USB cable to attach to +the board in question, along with a battery and power switch suitable for +powering the board up.
+++E.3. RF Calibration Procedure
+++Using the terminal program, connect to the board over USB. You will find +that you are now interacting with a command interpreter on the board. Using +'?' will show the available commands. Of interest for this process are the +'C' command which turns on a steady transmitted carrier on the currently +selected operating frequency, and the 'c' subcommands that allow interaction +with the saved configuration.
+++Use the 'c s' command to discover and note the current radio calibration +value, and the operating frequency the board is configured for in kHz.
+++Set up your frequency counter with a suitable antenna near the board’s +antenna and use the 'C' command to turn on a steady carrier. Let the +frequency stabilize, and note what it is to as many digits as are steady +on your counter’s display.
+++To calculate the new calibration value, the equation is:
+++-
+
-
+
(intended_frequency / measured_frequency) * current_cal_value
+
+
++Set the new calibration value using 'c f <value>', then use 'c w' to save +that cal value into non-volatile memory. You can use the 'C' command again +to confirm the operating frequency is now within a few 10’s of Hz of the +intended operating frequency.
++Appendix F: Flight Data Recording
Each flight computer logs data at 100 samples per second @@ -5457,7 +5892,7 @@ cannot log data, so the only thing you will lose is the data.
-Appendix E: Altus Metrum Hardware Specifications
+Appendix G: Altus Metrum Hardware Specifications
Here’s the full set of Altus Metrum products, both in @@ -5539,6 +5974,16 @@ production and retired.
3.7V
+ +TeleMetrum v4.0
MS5607 30km (100k')
ADXL375 200g
uBlox Max-8C/10S
-
8MB
40mW
3.7V
TeleMini v1.0
MP3H6115 10km (33k')
-
3.7V
- -EasyMini v1.0
MS5607 30km (100k')
-
-
-
1MB
-
3.7-12V
- EasyMini v2.0
EasyMini v1.0-v3.0
MS5607 30km (100k')
-
-
3.7V
+ +TeleMega v5.0
MS5607 30km (100k')
ADXL375 200g
uBlox Max-8Q
MPU6000 MMC5983
8MB
40mW
3.7V
+ +TeleMega v6.0
MS5607 30km (100k')
ADXL375 200g
uBlox Max-8Q
BMI088 MMC5983
8MB
40mW
3.7V
EasyMega v1.0
MS5607 30km (100k')
MMA6555 102g
-
3.7-12V
+ +EasyTimer v2.0
-
24g
-
BMI088
1MB
-
3.7-12V
+ @@ -5721,27 +6196,524 @@ production and retired.EasyMotor v3.0
-
ADXL375 200g
-
-
8MB
-
6.5-15V
38mm coupler
- +EasyMini
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
-Appendix F: Release Notes
+Appendix H: Release Notes
-+F.1. Release Notes for Version 1.9.5
+H.1. Release Notes for Version 1.9.18
+++Version 1.9.18
+++H.1.1. AltOS
+++-
+
-
+
Add support for EasyTimer V2. The new version of this +product has on-board storage to log data during flight.
+
+
++H.1.2. AltosUI & TeleGPS application
+++ +-
+
-
+
Add support for EasyTimer V2. This includes support for +analyizing flight data from the on-board logs.
+
+ -
+
Allow on-board beepers to be disabled by setting the +frequency to 0.
+
+
++H.2. Release Notes for Version 1.9.17
+++Version 1.9.17
+++H.2.1. AltOS
+++-
+
-
+
Fix TeleMini v3 Monitor Idle support
+
+ -
+
Support TeleMetrum v4.0 with uBlox-10 GPS module
+
+ -
+
Improve igniter reporting via the beeper.
+
+
++H.2.2. AltosUI & TeleGPS application
+++ +-
+
-
+
Add support for EasyMini v3 Monitor Idle
+
+
++H.3. Release Notes for Version 1.9.16
+++Version 1.9.16
+++H.3.1. AltOS
+++-
+
-
+
Add TeleGPS v3.0 support
+
+
++H.3.2. AltosUI & TeleGPS application
+++ +-
+
-
+
Add TeleGPS v3.0 support
+
+
++H.4. Release Notes for Version 1.9.15
+++Version 1.9.15
+++H.4.1. AltOS
+++ +-
+
-
+
Add TeleMega v6.0 support
+
+ -
+
Add TeleMetrum v4.0 support
+
+ -
+
Fix sign of IMU values for TeleMega v5 boards in the +'across' axis. This affects IMU acceleration and gyro reports +for that axis, but has no effect on in-flight operation of +the tilt computation.
+
+
++H.5. Release Notes for Version 1.9.14
+++Version 1.9.14
+++H.5.1. AltOS
+++ +-
+
-
+
Fix 1.9.13 regression in TeleLCO startup sequence that +detects available TeleFire units.
+
+
++H.6. Release Notes for Version 1.9.13
+++Version 1.9.13
+++H.6.1. AltOS
+++-
+
-
+
Add option to beep max height in feet after landing
+
+ -
+
Fix APRS reports to be sent at the correct time and spacing.
+
+ -
+
Fix possible barometric sensor communication failure when +the CPU is busy talking to the radio at the same time. This +would cause loss of telemetry and failure to track the state +of the rocket during flight. This was aggrevated by the APRS +reports getting sent more often than they should.
+
+ -
+
Change EasyMotor v3 code to base logging on motor pressure +rather than the accelerometer. This allows use of EasyMotor +v3 in a static test stand.
+
+
++H.6.2. AltosUI
+++ +-
+
-
+
Add support for configuring the units used to report height +after landing on the beeper.
+
+
++H.7. Release Notes for Version 1.9.12
+++Version 1.9.12
+++H.7.1. AltOS
+++-
+
-
+
Add EasyMini v3.0 and EasyMotor v3.0 support
+
+ -
+
Fix TeleMetrum v2.0 configuration. Saving config would +crash the board.
+
+
++H.7.2. AltosUI
+++ +-
+
-
+
Add EasyMotor log parsing and graphing.
+
+
++H.8. Release Notes for Version 1.9.11
+++Version 1.9.11
+++H.8.1. AltOS
+++-
+
-
+
Make Apogee Delay work again.
+
+ -
+
Allow TX power to be limited to 10mW for compliance with +some uses under UK regulations.
+
+ -
+
Fix numerous minor issues with 16- vs 32- bit time values.
+
+
++H.8.2. AltosUI
+++-
+
-
+
Support M1-based Macs, follow AdoptOpenJDK to Adoptium
+
+
++H.8.3. AltosDroid
+++ +-
+
-
+
Handle Bluetooth permissions reliably.
+
+ -
+
Fix some screen rotation bugs.
+
+
++H.9. Release Notes for Version 1.9.10
+++Version 1.9.10
+++This release contains a couple of bug fixes for ground station software.
+++H.9.1. AltosUI
+++-
+
-
+
Rework the windows DLL build to make AltosUI run on more +instances of Windows 10.
+
+
++H.9.2. AltosDroid
+++ +-
+
-
+
Adapt to Android security changes which prevent AltosDroid +from storing flights in +/storage/emulated/0/AltusMetrum. Now, flights are stored in +/storage/emulated/0/media/org.altusmetrum.AltosDroid/AltusMetrum +instead. Also, AltosDroid will display an error message if +flight data cannot be logged.
+
+
++H.10. Release Notes for Version 1.9.9
+++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.
+++H.10.1. AltOS
+++-
+
-
+
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.
+
+
++H.10.2. AltosUI
+++ +-
+
-
+
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.
+
+
++H.11. Release Notes for Version 1.9.8
+++Version 1.9.8
+++H.11.1. AltOS
+++-
+
-
+
Add support for TeleMega v5.0
+
+ -
+
Extend extra pyro channel times to support delay > 327 seconds
+
+
++H.11.2. AltosUI
+++-
+
-
+
Support ARM devices in Linux binary release
+
+ -
+
Add support for TeleMega v5.0
+
+
++H.11.3. AltosDroid
+++-
+
-
+
Show tilt angle in pad and flight tabs
+
+ -
+
Show altitude as well as height (useful for TeleGPS)
+
+ -
+
Support devices without GPS receivers
+
+
++H.11.4. MicroPeak GUI
+++ +-
+
-
+
Show error dialog if device open fails
+
+
++H.12. Release Notes for Version 1.9.7
+++Version 1.9.7
+++H.12.1. AltOS
+++-
+
-
+
Fix TeleGPS logging so that new data are appended to an existing log correctly
+
+
++H.12.2. AltosUI
+++-
+
-
+
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
+
+
++H.12.3. AltosDroid
+++ +-
+
-
+
Support older devices back to Android version 5.1
+
+ -
+
Fix a number of issues that could result in app crashes
+
+
++H.13. Release Notes for Version 1.9.6
+++Version 1.9.6
+++H.13.1. AltOS
+++ +-
+
-
+
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.
+
+
+H.14. Release Notes for Version 1.9.5
Version 1.9.5
-F.1.1. AltOS
+H.14.1. AltOS
- @@ -5773,7 +6745,7 @@ never report as having been fired.
-F.1.2. AltosUI
+H.14.2. AltosUI
- @@ -5803,12 +6775,12 @@ AltosUI packages.
-F.2. Release Notes for Version 1.9.4
+H.15. Release Notes for Version 1.9.4
Version 1.9.4
-F.2.1. AltOS
+H.15.1. AltOS
- @@ -5825,7 +6797,7 @@ the device to panic at startup time.
-F.2.2. AltosUI
+H.15.2. AltosUI
- @@ -5838,12 +6810,12 @@ AltosUI packages.
-F.3. Release Notes for Version 1.9.3
+H.16. Release Notes for Version 1.9.3
Version 1.9.3
-F.3.1. AltOS
+H.16.1. AltOS
- @@ -5865,7 +6837,7 @@ middle.
-F.3.2. AltosUI, TeleGPS, MicroPeak
+H.16.2. AltosUI, TeleGPS, MicroPeak
- @@ -5884,12 +6856,12 @@ computer erase block size.
-F.4. Release Notes for Version 1.9.2
+H.17. Release Notes for Version 1.9.2
Version 1.9.2
-F.4.1. AltOS
+H.17.1. AltOS
- @@ -5902,7 +6874,7 @@ computer erase block size.
-F.4.2. AltosUI, TeleGPS, MicroPeak
+H.17.2. AltosUI, TeleGPS, MicroPeak
- @@ -5912,7 +6884,7 @@ computer erase block size.
-F.4.3. AltosDroid
+H.17.3. AltosDroid
- @@ -5930,12 +6902,12 @@ computer erase block size.
-F.5. Release Notes for Version 1.9.1
+H.18. Release Notes for Version 1.9.1
Version 1.9.1
-F.5.1. AltOS
+H.18.1. AltOS
- @@ -5957,7 +6929,7 @@ computer erase block size.
-F.5.2. AltosUI, TeleGPS, MicroPeak
+H.18.2. AltosUI, TeleGPS, MicroPeak
- @@ -5982,12 +6954,12 @@ upgrade. This should avoid the âCOMxx: open failedâ message.
-F.6. Release Notes for Version 1.9
+H.19. Release Notes for Version 1.9
Version 1.9
-F.6.1. AltOS
+H.19.1. AltOS
- @@ -6003,7 +6975,7 @@ upgrade. This should avoid the âCOMxx: open failedâ message.
-F.6.2. AltosUI, TeleGPS, MicroPeak
+H.19.2. AltosUI, TeleGPS, MicroPeak
- @@ -6018,12 +6990,12 @@ upgrade. This should avoid the âCOMxx: open failedâ message.
-F.7. Release Notes for Version 1.8.7
+H.20. Release Notes for Version 1.8.7
Version 1.8.7
-F.7.1. AltOS
+H.20.1. AltOS
- @@ -6033,7 +7005,7 @@ upgrade. This should avoid the âCOMxx: open failedâ message.
-F.7.2. AltosUI, TeleGPS, MicroPeak
+H.20.2. AltosUI, TeleGPS, MicroPeak
- @@ -6075,12 +7047,12 @@ applications will run with Oracle Java.
-F.8. Release Notes for Version 1.8.6
+H.21. Release Notes for Version 1.8.6
Version 1.8.6
-F.8.1. AltOS
+H.21.1. AltOS
- @@ -6099,7 +7071,7 @@ applications will run with Oracle Java.
-F.8.2. AltosUI, TeleGPS
+H.21.2. AltosUI, TeleGPS
- @@ -6121,7 +7093,7 @@ applications will run with Oracle Java.
-F.8.3. MicroPeak
+H.21.3. MicroPeak
- @@ -6133,13 +7105,13 @@ applications will run with Oracle Java.
-F.9. Release Notes for Version 1.8.5
+H.22. Release Notes for Version 1.8.5
Version 1.8.5 includes fixes to the ground software support for TeleBT v4, along with a few other minor updates.
-F.9.1. AltOS
+H.22.1. AltOS
- @@ -6149,7 +7121,7 @@ for TeleBT v4, along with a few other minor updates.
-F.9.2. AltosUI, TeleGPS
+H.22.2. AltosUI, TeleGPS
- @@ -6166,12 +7138,12 @@ devices.
-F.10. Release Notes for Version 1.8.4
+H.23. Release Notes for Version 1.8.4
Version 1.8.4 includes support for EasyMini version 2.0
-F.10.1. AltOS
+H.23.1. AltOS
- @@ -6183,7 +7155,7 @@ devices.
-F.11. Release Notes for Version 1.8.3
+H.24. Release Notes for Version 1.8.3
Version 1.8.3 includes support for TeleMega version 3.0 along with two important flight computer fixes. This version also @@ -6192,7 +7164,7 @@ better and some updates to graph presentation and data downloading.
-F.11.1. AltOS
+H.24.1. AltOS
AltOS New Features
@@ -6225,7 +7197,7 @@ from capturing log data.-F.11.2. AltosUI and TeleGPS Applications
+H.24.2. AltosUI and TeleGPS Applications
AltosUI New Features
@@ -6283,7 +7255,7 @@ tilt angle.-F.12. Release Notes for Version 1.8.2
+H.25. Release Notes for Version 1.8.2
Version 1.8.2 includes support for TeleGPS version 2.0 along with accelerometer recalibration support in AltosUI.
@@ -6293,7 +7265,7 @@ with accelerometer recalibration support in AltosUI. analyzing saved data files.-F.12.1. AltOS
+H.25.1. AltOS
@@ -6306,7 +7278,7 @@ analyzing saved data files.AltOS New Features
-F.12.2. AltosUI and TeleGPS Applications
+H.25.2. AltosUI and TeleGPS Applications
@@ -6335,7 +7307,7 @@ for graphing or KML export.AltosUI and TeleGPS New Features
-F.13. Release Notes for Version 1.8.1
+H.26. Release Notes for Version 1.8.1
Version 1.8.1 includes an important bug fix for Apogee Lockout operation in all flight computers. Anyone using this option @@ -6356,7 +7328,7 @@ above Mach 1.
analyzing saved data files.-F.13.1. AltOS
+H.26.1. AltOS
@@ -6377,7 +7349,7 @@ deceleration.AltOS Bug Fixes
-F.13.2. AltosUI and TeleGPS Applications
+H.26.2. AltosUI and TeleGPS Applications
@@ -6408,7 +7380,7 @@ broken, so you’d see only the default frequencies.AltosUI New Features
-F.14. Release Notes for Version 1.8
+H.27. Release Notes for Version 1.8
Version 1.8 includes support for our new TeleBT v4.0 ground station, updates for data analysis in our ground station @@ -6416,7 +7388,7 @@ software and bug fixes in in the flight software for all our boards and ground station interfaces.
-F.14.1. AltOS
+H.27.1. AltOS
@@ -6429,7 +7401,7 @@ boards and ground station interfaces.AltOS New Features
-F.14.2. AltosUI and TeleGPS Applications
+H.27.2. AltosUI and TeleGPS Applications
@@ -6462,14 +7434,14 @@ EasyMega. The Y and Z axes were flipped.AltosUI New Features
-F.15. Release Notes for Version 1.7
+H.28. Release Notes for Version 1.7
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.
-F.15.1. AltOS
+H.28.1. AltOS
@@ -6494,7 +7466,7 @@ serviced first.AltOS New Features
-F.15.2. AltosUI and TeleGPS Applications
+H.28.2. AltosUI and TeleGPS Applications
@@ -6509,7 +7481,7 @@ serviced first.AltosUI New Features
-F.16. Release Notes for Version 1.6.8
+H.29. Release Notes for Version 1.6.8
Version 1.6.8 fixes a TeleMega and TeleMetrum v2.0 bug where the device could stop logging data and transmitting @@ -6517,7 +7489,7 @@ telemetry in flight. All TeleMega v1.0, v2.0 and TeleMetrum v2.0 users should update their flight firmware.
-F.16.1. AltOS
+H.29.1. AltOS
@@ -6551,7 +7523,7 @@ they can be tested during production.AltOS fixes:
-F.16.2. AltosUI, TeleGPS and AltosDroid Applications
+H.29.2. AltosUI, TeleGPS and AltosDroid Applications
@@ -6573,7 +7545,7 @@ Ground Station operation by cleaning up pending operations.AltosUI fixes:
-F.17. Release Notes for Version 1.6.5
+H.30. Release Notes for Version 1.6.5
Version 1.6.5 fixes a TeleMega and TeleMetrum v2.0 bug where the device would often stop logging data and transmitting @@ -6581,7 +7553,7 @@ telemetry in flight. All TeleMega v1.0, v2.0 and TeleMetrum v2.0 users should update their flight firmware.
-F.17.1. AltOS
+H.30.1. AltOS
@@ -6597,7 +7569,7 @@ tested the new firmware before release.AltOS fixes:
-F.17.2. AltosUI, TeleGPS and AltosDroid Applications
+H.30.2. AltosUI, TeleGPS and AltosDroid Applications
@@ -6613,14 +7585,14 @@ Windows package.AltosUI fixes:
-F.18. Release Notes for Version 1.6.4
+H.31. Release Notes for Version 1.6.4
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.
-F.18.1. AltOS
+H.31.1. AltOS
@@ -6640,7 +7612,7 @@ fixes affect all STM32L, STM32F0 and LPC11U14 based devices.AltOS fixes:
-F.18.2. AltosUI, TeleGPS and AltosDroid Applications
+H.31.2. AltosUI, TeleGPS and AltosDroid Applications
@@ -6672,7 +7644,7 @@ active.AltosUI, TeleGPS and AltosDroid New Features:
-F.18.3. Documentation
+H.31.3. Documentation
- @@ -6687,14 +7659,14 @@ active.
-F.19. Release Notes for Version 1.6.3
+H.32. Release Notes for Version 1.6.3
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.
-F.19.1. AltOS
+H.32.1. AltOS
@@ -6709,7 +7681,7 @@ hardware to driving these pins with software.AltOS fixes:
-F.19.2. AltosUI and TeleGPS Applications
+H.32.2. AltosUI and TeleGPS Applications
@@ -6754,7 +7726,7 @@ TeleMetrum v2.0 flight computers.AltosUI and TeleGPS New Features:
-F.19.3. AltosDroid
+H.32.3. AltosDroid
@@ -6819,7 +7791,7 @@ location of any tracker.AltosDroid new features:
-F.19.4. Documentation
+H.32.4. Documentation
- @@ -6832,14 +7804,14 @@ continuity audio alert pattern.
-F.20. Release Notes for Version 1.6.2
+H.33. Release Notes for Version 1.6.2
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.
-F.20.1. AltOS
+H.33.1. AltOS
@@ -6868,7 +7840,7 @@ up.AltOS New Features:
-F.20.2. AltosUI and TeleGPS Applications
+H.33.2. AltosUI and TeleGPS Applications
@@ -6887,7 +7859,7 @@ writing the associated .eeprom file when an error is detected.AltosUI and TeleGPS Fixes:
-F.20.3. Documentation
+H.33.3. Documentation
@@ -6912,14 +7884,14 @@ duplication of informationWe spent a bunch of time trying to improve our documentation
-F.21. Release Notes for Version 1.6.1
+H.34. Release Notes for Version 1.6.1
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.
-F.21.1. AltOS
+H.34.1. AltOS
@@ -6949,7 +7921,7 @@ variations from transmitting devices.AltOS New Features:
-F.21.2. AltosUI and TeleGPS Applications
+H.34.2. AltosUI and TeleGPS Applications
@@ -7014,7 +7986,7 @@ run at 10x speed by mistake.AltosUI and TeleGPS New Features:
-F.21.3. AltosDroid
+H.34.3. AltosDroid
@@ -7072,14 +8044,14 @@ motion towards rocket.AltosDroid New Features:
-F.22. Release Notes for Version 1.6
+H.35. Release Notes for Version 1.6
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.
-F.22.1. AltOS
+H.35.1. AltOS
@@ -7121,7 +8093,7 @@ you’ll want to reflash the firmware.AltOS New Features
-F.22.2. AltosUI and TeleGPS Applications
+H.35.2. AltosUI and TeleGPS Applications
@@ -7196,14 +8168,14 @@ flight computers appear on multiple frequencies by accident.AltosUI and TeleGPS New Features
-F.23. Release Notes for Version 1.5
+H.36. Release Notes for Version 1.5
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
-F.23.1. AltOS
+H.36.1. AltOS
@@ -7262,7 +8234,7 @@ deceleration.AltOS New Features
-F.23.2. AltosUI and TeleGPS Applications
+H.36.2. AltosUI and TeleGPS Applications
@@ -7303,13 +8275,13 @@ cases where we just can’t figure out what version is installed.AltosUI and TeleGPS New Features
-F.24. Release Notes for Version 1.4.2
+H.37. Release Notes for Version 1.4.2
Version 1.4.2 is a minor release. It fixes Java-related install issues on Windows
-F.24.1. AltosUI and TeleGPS Applications
+H.37.1. AltosUI and TeleGPS Applications
@@ -7328,7 +8300,7 @@ detection fails.Windows Install Fixes
-F.25. Release Notes for Version 1.4.1
+H.38. Release Notes for Version 1.4.1
Version 1.4.1 is a minor release. It fixes install issues on Windows and provides the missing TeleMetrum V2.0 firmware. There @@ -7338,7 +8310,7 @@ driver, but Mac and Linux users who do not need the TeleMetrum V2.0 firmware image will not need to upgrade.
-F.25.1. AltosUI and TeleGPS Applications:
+H.38.1. AltosUI and TeleGPS Applications:
@@ -7379,14 +8351,14 @@ software, making map downloading fail for most people.Windows Install Fixes
-F.26. Release Notes for Version 1.4
+H.39. Release Notes for Version 1.4
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
-F.26.1. AltOS
+H.39.1. AltOS
@@ -7441,7 +8413,7 @@ as being present.AltOS new features:
-F.26.2. AltosUI Application
+H.39.2. AltosUI Application
@@ -7527,7 +8499,7 @@ the product name instead.AltosUI new features:
-F.26.3. TeleGPS Application
+H.39.3. TeleGPS Application
- @@ -7541,7 +8513,7 @@ to focus on TeleGPS-related functions.
-F.26.4. Documentation
+H.39.4. Documentation
@@ -7563,13 +8535,13 @@ configurable amount of time after boost.Documentation changes:
-F.27. Release Notes for Version 1.3.2
+H.40. Release Notes for Version 1.3.2
Version 1.3.2 is a minor release. It includes small bug fixes for the TeleMega flight software and AltosUI ground station
-F.27.1. AltOS
+H.40.1. AltOS
@@ -7591,7 +8563,7 @@ view and voltages.AltOS fixes:
-F.27.2. AltosUI Application
+H.40.2. AltosUI Application
@@ -7619,13 +8591,13 @@ Igniter dialog.AltosUI fixes:
-F.28. Release Notes for Version 1.3.1
+H.41. Release Notes for Version 1.3.1
Version 1.3.1 is a minor release. It improves support for TeleMega, TeleMetrum v2.0, TeleMini v2.0 and EasyMini.
-F.28.1. AltOS
+H.41.1. AltOS
@@ -7667,7 +8639,7 @@ getting re-computed incorrectly in inverted mode.AltOS new features:
-F.28.2. AltosUI Application
+H.41.2. AltosUI Application
@@ -7703,13 +8675,13 @@ so that all of the map tiles download successfully.AltosUI new features:
-F.29. Release Notes for Version 1.3
+H.42. Release Notes for Version 1.3
Version 1.3 is a major release. It adds support for TeleMega, TeleMetrum v2.0, TeleMini v2.0 and EasyMini.
-F.29.1. AltOS
+H.42.1. AltOS
@@ -7748,7 +8720,7 @@ digital FM transceiversAltOS new features:
-F.29.2. AltosUI Application
+H.42.2. AltosUI Application
@@ -7784,14 +8756,14 @@ default for new downloadsAltosUI new features:
-F.30. Release Notes for Version 1.2.1
+H.43. Release Notes for Version 1.2.1
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.
-F.30.1. AltOS
+H.43.1. AltOS
@@ -7833,7 +8805,7 @@ performance somewhat.AltOS new features:
-F.30.2. AltosUI Application
+H.43.2. AltosUI Application
@@ -7890,7 +8862,7 @@ time.AltosUI application new features:
-F.30.3. AltosDroid
+H.43.3. AltosDroid
- @@ -7902,13 +8874,13 @@ time.
-F.31. Release Notes for Version 1.2
+H.44. Release Notes for Version 1.2
Version 1.2 is a major release. It adds support for MicroPeak and the MicroPeak USB adapter.
-F.31.1. AltOS
+H.44.1. AltOS
@@ -7924,7 +8896,7 @@ multi-tasking scheduler.AltOS New Features:
-F.31.2. AltosUI and MicroPeak Application
+H.44.2. AltosUI and MicroPeak Application
@@ -7957,7 +8929,7 @@ time.New Features:
-F.32. Release Notes for Version 1.1
+H.45. Release Notes for Version 1.1
Version 1.1.1 is a bug-fix release. It fixes a couple of bugs in AltosUI and one firmware bug that affects TeleMetrum @@ -7966,7 +8938,7 @@ the Google Earth file export issue, and for suggesting the addition of the Ground Distance value in the Descent tab.
-F.32.1. AltOS
+H.45.1. AltOS
@@ -7986,7 +8958,7 @@ of rockets flying version 1.1 firmware.AltOS fixes:
-F.32.2. AltosUI
+H.45.2. AltosUI
@@ -8038,13 +9010,13 @@ deciding whether to fetch the analog sensor data.AltosUI new features:
-
+
-
F.33. Release Notes for Version 1.1
+H.46. Release Notes for Version 1.1
Version 1.1 is a minor release. It provides a few new features in AltosUI and the AltOS firmware and fixes bugs.
-
@@ -8086,7 +9058,7 @@ the radio was turned off and back on.
F.33.1. AltOS
+H.46.1. AltOS
AltOS Firmware New Features:
-
@@ -8170,13 +9142,13 @@ in 'Monitor Idle' mode.
F.33.2. AltosUI
+H.46.2. AltosUI
AltosUI New Features:
-
F.34. Release Notes for Version 1.0.1
+H.47. Release Notes for Version 1.0.1
Version 1.0.1 is a major release, adding support for the TeleMini device and lots of new AltosUI features
-
@@ -8234,7 +9206,7 @@ Mach delay.
F.34.1. AltOS
+H.47.1. AltOS
AltOS New Features
-
@@ -8303,13 +9275,13 @@ placed in "Idle" mode if AltosUI is polling it.
F.34.2. AltosUI Application
+H.47.2. AltosUI Application
AltosUI New Features