+
3.9. Using a Different Kind of 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 @@ -841,6 +864,7 @@ battery.
There are two generations of the TeleMetrum design. The -major changes in the v2 generation are:
+major changes after v1 generation are:-
@@ -959,8 +983,8 @@ the terminals are as follows:
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
-
Connecting the positive battery terminal to the pyro +
Connecting the switched positive battery terminal to the pyro charges must be done separate from TeleMetrum, by soldering -them together or using some other connector.
+them together or using some other connector. Note that you +must include a switch in the positive lead from the pyro +battery for safety!The other lead from each pyro charge is then inserted into -the appropriate per-pyro channel screw terminal (terminal 4 for the -Main charge, terminal 6 for the Apogee charge).
+the appropriate per-pyro channel screw terminal (terminal 4 +for the Main charge, terminal 6 for the Apogee charge).
@@ -1084,8 +1110,8 @@ connections are as follows:
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
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. Because -there is no solid ground connection to use on TeleMini, this -is not recommended.
+computer ground, connecting the switched positive battery +terminal to one of the igniter leads and connecting the other +igniter lead to the per-channel pyro circuit connection. +Because there is no solid ground connection to use on +TeleMini, this is not recommended.The only available ground connection on TeleMini v3 are @@ -1130,7 +1156,9 @@ those holes and hook it to the negative pyro battery terminal.
Connecting the positive battery terminal to the pyro charges must be done separate from TeleMini v3, by soldering -them together or using some other connector.
+them together or using some other connector. Note that you +must include a switch in the pyro battery positive lead for +safety!The other lead from each pyro charge is then inserted into @@ -1289,12 +1317,12 @@ switch. Counting from the left, the connections are as follows:
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
-
Connecting the positive battery terminal to the pyro +
Connecting the switched positive battery terminal to the pyro charges must be done separate from EasyMini, by soldering -them together or using some other connector.
+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 @@ -1479,8 +1509,8 @@ the board opposite the telemetry antenna. They are as follows:
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 +
TeleMega 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 -(Bottom 1) and the positive pyro battery to the pyro battery -input (Bottom 2). You can then use the existing pyro screw +(Bottom 2). Then hook the negative pyro battery terminal to +ground (Bottom 1) and the switched positive pyro battery to +the pyro battery input (Bottom 2). Note that you must include +a switch between the pyro battery and the board for safety, +as the on-board power switch circuit only supports the primary +battery! You can then use the existing pyro screw terminals to hook up all of the pyro charges.
-
+
+
Figure 7. EasyMega Board
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 +
EasyMega 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 -(Bottom 1) and the positive pyro battery to the pyro battery -input (Bottom 2). You can then use the existing pyro screw +(Bottom 2). Then hook the negative pyro battery terminal to +ground (Bottom 1) and the switched positive pyro battery to +the pyro battery input (Bottom 2). Note that you must include +a switch between the pyro battery and the board for safety, +as the on-board power switch circuit only supports the primary +battery! You can then use the existing pyro screw terminals to hook up all of the pyro charges.
-
+9. Installation
+9. EasyTimer
+
+
+
+
+
+
+
+
+Figure 8. EasyTimer Board
+
+
+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.
+
+
+
+
+9.1. EasyTimer Screw Terminals
+
+
+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 |
+
+
+9.2. Connecting A Battery To EasyTimer
+
+
+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.
+
+
+9.3. Charging Lithium Batteries
+
+
+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.
+
+
+9.4. Using a Separate Pyro Battery with EasyTimer
+
+
+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).
+
+
+9.5. Using an Active Switch with EasyTimer
+
+
+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.
+
+
10. Installation
A typical installation involves attaching @@ -1848,10 +2049,10 @@ cable terminating in a U.FL connector.
-
10. Using Altus Metrum Products
+11. Using Altus Metrum Products
-
10.1. Being Legal
+11.1. Being Legal
In the US, you need an amateur radio license @@ -1860,14 +2061,14 @@ transmitters that are part of our products.
-
10.2. In the Rocket
+11.2. In the Rocket
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 @@ -1888,7 +2089,7 @@ made of RF-transparent materials if at all possible.
-
10.3. On the Ground
+11.3. On the Ground
To receive the data stream from the rocket, you need an antenna and short feed-line connected to one of our @@ -1986,7 +2187,7 @@ reflector of Arrow antennas.
-
10.4. Data Analysis
+11.4. Data Analysis
Our software makes it easy to log the data from each flight, both the telemetry received during the flight @@ -2009,7 +2210,7 @@ or just viewed on your local disk with a web browser.
-
10.5. Future Plans
+11.5. Future Plans
We have designed and prototyped several âcompanion boardsâ that can attach to the companion connector on @@ -2039,13 +2240,13 @@ evolves!
-
-
11. AltosUI
+12. AltosUI
Figure 8. AltosUI Main Window
+Figure 9. AltosUI Main Window
The AltosUI program provides a graphical user interface for @@ -2057,7 +2258,7 @@ chapter is split into sections, each of which documents one of the tasks provided from the top-level toolbar.
-
-
11.1. Monitor Flight
+12.1. Monitor Flight
Selecting this item brings up a dialog box listing all of the connected TeleDongle devices. When you choose @@ -2069,7 +2270,7 @@ device.
Figure 9. Device Selection Dialog
+Figure 10. Device Selection Dialog
All telemetry data received are automatically recorded @@ -2141,12 +2342,12 @@ raw telemetry values in one place in a spreadsheet-like format.
-
-
11.1.1. Launch Pad
+12.1.1. Launch Pad
Figure 10. Monitor Flight Launch Pad View
+Figure 11. Monitor Flight Launch Pad View
The 'Launch Pad' tab shows information used to decide when the @@ -2218,12 +2419,12 @@ positions to improve the accuracy of the fix.
-
-
11.1.2. Ascent
+12.1.2. Ascent
Figure 11. Monitor Flight Ascent View
+Figure 12. Monitor Flight Ascent View
This tab is shown during Boost, Fast and Coast @@ -2250,12 +2451,12 @@ caused by wiring which comes loose under high acceleration.
-
-
11.1.3. Descent
+12.1.3. Descent
Figure 12. Monitor Flight Descent View
+Figure 13. Monitor Flight Descent View
Once the rocket has reached apogee and (we hope) @@ -2297,12 +2498,12 @@ firing.
-
-
11.1.4. Landed
+12.1.4. Landed
Figure 13. Monitor Flight Landed View
+Figure 14. Monitor Flight Landed View
Once the rocket is on the ground, attention switches @@ -2343,12 +2544,12 @@ bring up a graph window for the current flight.
-
-
11.1.5. Table
+12.1.5. Table
Figure 14. Monitor Flight Table View
+Figure 15. Monitor Flight Table View
The table view shows all of the data available from the @@ -2359,12 +2560,12 @@ information about the signal being received from the satellites.
-
-
11.1.6. Site Map
+12.1.6. Site Map
Figure 15. Monitor Flight Site Map View
+Figure 16. Monitor Flight Site Map View
When the TeleMetrum has a GPS fix, the Site Map tab @@ -2402,12 +2603,12 @@ before you leave home; check out Load Maps.
-
-
11.1.7. Igniter
+12.1.7. Igniter
Figure 16. Monitor Flight Additional Igniter View
+Figure 17. Monitor Flight Additional Igniter View
TeleMega includes four additional programmable pyro @@ -2420,7 +2621,7 @@ status.
-
11.2. Save Flight Data
+12.2. Save Flight Data
The altimeter records flight data to its internal flash memory. @@ -2462,7 +2663,7 @@ serial number and flight number information.
-
11.3. Replay Flight
+12.3. Replay Flight
Select this button and you are prompted to select a flight record file, either a .telem file recording telemetry data or a @@ -2478,7 +2679,7 @@ Check
-
11.4. Graph Data
+12.4. Graph Data
Select this button and you are prompted to select a flight record file, either a .telem file recording telemetry data or a @@ -2495,12 +2696,12 @@ Use saved flight data in .eeprom files for graphing where possible.
opened.
-
-
11.4.1. Flight Graph
+12.4.1. Flight Graph
Figure 17. Flight Data Graph
+Figure 18. Flight Data Graph
By default, the graph contains acceleration (blue), @@ -2518,12 +2719,12 @@ plot.
-
-
11.4.2. Configure Graph
+12.4.2. Configure Graph
Figure 18. Flight Graph Configuration
+Figure 19. Flight Graph Configuration
This selects which graph elements to show, and, at the @@ -2559,35 +2760,52 @@ value smooths the data more.
-
-
11.4.3. Flight Statistics
+12.4.3. Flight Statistics
Figure 19. Flight Statistics
+Figure 20. Flight Statistics
Shows overall data computed from the flight.
-
-
11.4.4. Map
+12.4.4. Map
Figure 20. Flight Map
+Figure 21. Flight Map
-
+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.
+Shows a satellite image of the flight area +overlaid with the path of the flight. The +flight path will have different colored +sections for each state of the flight (just +like the Site Map in Monitor Flight mode): +white for pad, red for boost, pink for fast, +yellow for coast, light blue for drogue, dark +blue for main, and black for landed.
+
+
The red concentric circles mark the launch +pad, the black concentric circles mark the +landing location. Data for the point along the +along the flight path nearest the cursor will +be displayed at the bottom of the window. This +data includes flight time (so you can +correlate data in the graph window), latitude, +longitude, height above ground and vertical +speed. The selected point will be highlighted +with concentric circles in the same color as +the flight path at that point.
-
11.5. Export Data
+12.5. Export Data
This tool takes the raw data files and makes them available for external analysis. When you select this @@ -2602,7 +2820,7 @@ It has a selector to choose between CSV and KML file formats.
-
11.5.1. Comma Separated Value Format
+12.5.1. Comma Separated Value Format
This is a text file containing the data in a form suitable for import into a spreadsheet or other @@ -2622,7 +2840,7 @@ both pressure, altitude and height above pad units.
-
11.5.2. Keyhole Markup Language (for Google Earth)
+12.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 @@ -2632,12 +2850,12 @@ in 3D.
-
-
11.6. Configure Altimeter
+12.6. Configure Altimeter
Figure 21. Altimeter Configuration
+Figure 22. Altimeter Configuration
Select this button and then select either an altimeter or @@ -2685,7 +2903,7 @@ lost.
The rest of the dialog contains the parameters to be configured.
-
11.6.1. Main Deploy Altitude
+12.6.1. Main Deploy Altitude
This sets the altitude (above the recorded pad altitude) at which the 'main' igniter will fire. The @@ -2697,7 +2915,7 @@ apogee charge fires.
-
11.6.2. Apogee Delay
+12.6.2. Apogee Delay
When flying redundant electronics, it’s often important to ensure that multiple apogee charges don’t @@ -2710,7 +2928,7 @@ been detected.
-
11.6.3. Apogee Lockout
+12.6.3. Apogee Lockout
Apogee lockout is the number of seconds after launch where the flight computer will not fire the apogee @@ -2741,7 +2959,7 @@ the correct behavior.
-
11.6.4. Frequency
+12.6.4. Frequency
This configures which of the frequencies to use for both telemetry and packet command mode. Note that if @@ -2752,7 +2970,7 @@ continue afterwards.
-
11.6.5. RF Calibration
+12.6.5. RF Calibration
The radios in every Altus Metrum device are calibrated at the factory to ensure that they transmit and @@ -2766,7 +2984,7 @@ completely.
-
11.6.6. Telemetry/RDF/APRS Enable
+12.6.6. Telemetry/RDF/APRS Enable
Enables the radio for transmission during flight. When disabled, the radio will not @@ -2774,7 +2992,7 @@ transmit anything during flight at all.
-
11.6.7. Telemetry baud rate
+12.6.7. Telemetry baud rate
This sets the modulation bit rate for data transmission for both telemetry and packet @@ -2788,13 +3006,13 @@ rate specified here.
-
11.6.8. APRS Interval
+12.6.8. APRS Interval
How often to transmit GPS information via APRS (in seconds). When set to zero, APRS transmission is disabled. This option is -available on TeleMetrum v2 and TeleMega +available on TeleMetrum v2 or newer and TeleMega boards. TeleMetrum v1 boards cannot transmit APRS packets. Note that a single APRS packet @@ -2804,7 +3022,7 @@ other telemetry during that time.
-
11.6.9. APRS SSID
+12.6.9. APRS SSID
Which SSID to report in APRS packets. By default, this is set to the last digit of the @@ -2813,7 +3031,7 @@ value from 0 to 9.
-
11.6.10. APRS Format
+12.6.10. APRS Format
Whether to send APRS data in Compressed or Uncompressed format. Compressed format is @@ -2827,7 +3045,19 @@ you fly to see which to use.
-
+11.6.11. Callsign
+12.6.11. APRS Offset
+
+
+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.
+
+
12.6.12. Callsign
This sets the call sign included in each telemetry packet. Set this as needed to @@ -2835,7 +3065,7 @@ conform to your local radio regulations.
-
11.6.12. Maximum Flight Log Size
+12.6.13. Maximum Flight Log Size
This sets the space (in kilobytes) allocated for each flight log. The available space will @@ -2846,7 +3076,7 @@ flights.
-
Separation & Apogee
+
+
11.6.13. Ignitor Firing Mode
+12.6.14. Ignitor Firing Mode
This configuration parameter allows the two standard ignitor channels (Apogee and Main) to be used in different @@ -2876,11 +3106,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.
+
-
11.6.14. Pad Orientation
+12.6.15. Pad Orientation
Because they include accelerometers, TeleMetrum, TeleMega and EasyMega are @@ -2894,21 +3129,21 @@ with the antenna pointing aft instead.
- Antenna Up
-
-
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.
- Antenna Down
-
-
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.
-
11.6.15. Beeper Frequency
+12.6.16. Beeper Frequency
The beeper on all Altus Metrum flight computers works best at 4000Hz, however if you @@ -2920,7 +3155,7 @@ value.
-
11.6.16. Logging Trigger Motion
+12.6.17. Logging Trigger Motion
This sets the amount of motion that TeleGPS needs to see before logging the new @@ -2929,7 +3164,7 @@ skipped, which saves storage space.
-
11.6.17. Position Reporting Interval
+12.6.18. Position Reporting Interval
The interval between TeleGPS position reports, both over the air and in the log. Increase @@ -2939,7 +3174,7 @@ in the log.
-
11.6.18. Calibrate Accelerometer
+12.6.19. Calibrate Accelerometer
This opens a separate window to recalibrate the accelerometers. Follow the instructions, orienting the @@ -2954,17 +3189,17 @@ calibration values.
-
-
Height above pad
Orientation
-
-
11.6.19. Configure Pyro Channels
+12.6.20. Configure Pyro Channels
Figure 22. Additional Pyro Channel Configuration
+Figure 23. Additional Pyro Channel Configuration
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 @@ -3014,14 +3249,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 @@ -3136,14 +3373,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 @@ -3153,7 +3390,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.
@@ -3177,19 +3414,19 @@ acceleration again, it will move back to Boost state.
-
-
11.7. Configure AltosUI
+12.7. Configure AltosUI
Figure 23. Configure AltosUI Dialog
+Figure 24. Configure AltosUI Dialog
This button presents a dialog so that you can configure the AltosUI global settings.
-
11.7.1. Voice Settings
+12.7.1. Voice Settings
AltosUI provides voice announcements during flight so that you can keep your eyes on the @@ -3213,7 +3450,7 @@ are reasonable
-
11.7.2. Log Directory
+12.7.2. Log Directory
AltosUI logs all telemetry data and saves all flash data to this directory. This @@ -3230,7 +3467,7 @@ files.
-
11.7.3. Callsign
+12.7.3. Callsign
This value is transmitted in each command packet sent from TeleDongle and received from @@ -3252,7 +3489,7 @@ sensitive.
-
11.7.4. Imperial Units
+12.7.4. Imperial Units
This switches between metric units (meters) and imperial units (feet and miles). This @@ -3265,7 +3502,7 @@ always produced in metric units.
-
11.7.5. Serial Debug
+12.7.5. Serial Debug
This causes all communication with a connected device to be dumped to the console from which @@ -3276,7 +3513,7 @@ various serial communication issues.
-
11.7.6. Font size
+12.7.6. Font size
Selects the set of fonts used in the flight monitor window. Choose between the small, @@ -3284,7 +3521,7 @@ medium and large sets.
-
11.7.7. Look & feel
+12.7.7. Look & feel
Switches between the available Java user interface appearances. The default selection @@ -3293,7 +3530,7 @@ appearance for the target platform.
-
11.7.8. Menu position
+12.7.8. Menu position
Selects the initial position for the main AltosUI window that includes all of the @@ -3301,7 +3538,7 @@ command buttons.
-
11.7.9. Map Cache Size
+12.7.9. Map Cache Size
Sets the number of map 'tiles' kept in memory while the application is running. More tiles @@ -3310,7 +3547,7 @@ around the map faster.
-
11.7.10. Manage Frequencies
+12.7.10. Manage Frequencies
This brings up a dialog where you can configure the set of frequencies shown in the @@ -3324,12 +3561,12 @@ menus.
-
-
11.8. Configure Groundstation
+12.8. Configure Groundstation
Figure 24. Configure Groundstation Dialog
+Figure 25. Configure Groundstation Dialog
Select this button and then select a TeleDongle or @@ -3380,7 +3617,7 @@ will be lost.
to be configured.
-
11.8.1. Frequency
+12.8.1. Frequency
This configures the frequency to use for both telemetry and packet command mode. Set this @@ -3393,7 +3630,7 @@ value used here.
-
11.8.2. RF Calibration
+12.8.2. RF Calibration
The radios in every Altus Metrum device are calibrated at the factory to ensure that they @@ -3405,7 +3642,7 @@ current value and doesn’t allow any changes.
-
11.8.3. Telemetry Rate
+12.8.3. Telemetry Rate
This lets you match the telemetry and packet link rate from the transmitter. If they don’t @@ -3414,7 +3651,7 @@ match, the device won’t receive any data.
-
11.9. Flash Image
+12.9. Flash Image
This reprograms Altus Metrum devices with new firmware. @@ -3422,8 +3659,9 @@ TeleMetrum v1.x, TeleDongle v0.2, TeleMini v1.0 and TeleBT v1.0 are all reprogrammed by using another similar unit as a programming dongle (pair programming). -TeleMega, EasyMega, TeleMetrum v2, -EasyMini and TeleDongle v3 are all +TeleMega, EasyMega, TeleMetrum v2 or newer, +EasyMini, EasyTimer, TeleBT v3 or newer and TeleDongle v3 +or newer are all programmed directly over USB (self programming). Please read the directions for flashing devices in @@ -3431,12 +3669,12 @@ the directions for flashing devices in
-
-
11.10. Fire Igniter
+12.10. Fire Igniter
Figure 25. Fire Igniter Window
+Figure 26. Fire Igniter Window
This activates the igniter circuits in the flight @@ -3468,12 +3706,12 @@ igniter.
-
-
11.11. Scan Channels
+12.11. Scan Channels
Figure 26. Scan Channels Window
+Figure 27. Scan Channels Window
This listens for telemetry packets on all of the @@ -3486,12 +3724,12 @@ later firmware.
-
-
11.12. Load Maps
+12.12. Load Maps
Figure 27. Load Maps Window
+Figure 28. Load Maps Window
Before heading out to a new launch site, you can use @@ -3569,12 +3807,12 @@ you. Try again later.
-
-
11.13. Monitor Idle
+12.13. Monitor Idle
Figure 28. Monitor Idle Window
+Figure 29. Monitor Idle Window
This brings up a dialog similar to the Monitor Flight @@ -3597,7 +3835,7 @@ exactly.
-
12. AltosDroid
+13. AltosDroid
AltosDroid provides the same flight monitoring capabilities as @@ -3615,7 +3853,7 @@ to TeleBT or TeleDongle, operate the flight monitoring interface and describe what the displayed data means.
-
12.1. Installing AltosDroid
+13.1. Installing AltosDroid
AltosDroid is available from the Google Play store. To install it on your Android device, open the Google @@ -3627,7 +3865,7 @@ which you can download and install the application.
-
12.2. Charging TeleBT Battery
+13.2. Charging TeleBT Battery
Before using TeleBT with AltosDroid, make sure the internal TeleBT battery is charged. To do this, @@ -3640,7 +3878,7 @@ battery fault.
-
12.3. Connecting to TeleBT over Bluetoothâ¢
+13.3. Connecting to TeleBT over Bluetoothâ¢
Press the Android 'Menu' button or soft-key to see the configuration options available. Select the 'Connect a @@ -3656,7 +3894,7 @@ list without scanning.
-
12.4. Connecting to TeleDongle or TeleBT over USB
+13.4. Connecting to TeleDongle or TeleBT over USB
Get a special USB On-the-go adapter cable. These cables have a USB micro-B male connector on one end @@ -3669,7 +3907,7 @@ device doesn’t support USB On-the-go.
-
12.5. AltosDroid Menu
+13.5. AltosDroid Menu
The main AltosDroid menu has a selection of operation and configuration options.
@@ -3723,7 +3961,7 @@ the serial number of devices in each airframe.
-
12.6. Setup
+13.6. Setup
- Telemetry Rate @@ -3771,7 +4009,7 @@ frequencies, delete or add new frequencies.
-
12.7. Idle Mode
+13.7. Idle Mode
- Callsign @@ -3807,7 +4045,7 @@ systems.
-
12.8. AltosDroid Flight Monitoring
+13.8. AltosDroid Flight Monitoring
AltosDroid is designed to mimic the AltosUI flight monitoring display, providing separate tabs for each @@ -3818,7 +4056,7 @@ device.
-
12.9. Pad
+13.9. Pad
The 'Pad' tab shows information used to decide when the rocket is ready for flight. The first elements @@ -3910,7 +4148,7 @@ device.
-
12.10. Flight
+13.10. Flight
The 'Flight' tab shows information used to evaluate and spot a rocket while in flight. It displays speed @@ -3997,7 +4235,7 @@ for a 'GO' status.
-
12.11. Recover
+13.11. Recover
The 'Recover' tab shows information used while recovering the rocket on the ground after flight.
@@ -4057,7 +4295,7 @@ the flight.
-
12.12. Map
+13.12. Map
The 'Map' tab shows a map of the area around the rocket being tracked along with information needed to @@ -4080,7 +4318,7 @@ the Recover tab.
-
-
12.13. Downloading Flight Logs
+13.13. Downloading Flight Logs
AltosDroid always saves every bit of telemetry data it receives. To download that to a computer for use with @@ -4104,7 +4342,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 @@ -4415,13 +4653,20 @@ feedback on performance in higher altitude flights!
A.6. APRS
-
TeleMetrum v2.0 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.
+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 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 @@ -4449,7 +4694,7 @@ can have arbitrary text in it. AltOS uses this to send status information as shown in the following table.
80 |
||||||||||||||||||||||||||||||||||||||||||||
TeleMetrum v3.0 |
+16 |
+8MB |
+80 |
+|||||||||||||||||||||||||||||||||||||||||
TeleMini v1.0 |
2 |
5kB |
@@ -5146,7 +5424,7 @@ of flash space. This configuration space is not available
for storing flight log data.
3.7V |
|||||||
TeleMetrum v3.0 |
+MS5607 30km (100k') |
+ADXL375 200g |
+uBlox Max-8Q |
+- |
+8MB |
+40mW |
+3.7V |
+
TeleMini v1.0 |
MP3H6115 10km (33k') |
- |
@@ -5321,6 +5609,16 @@ production and retired.
3.7V |
||||
TeleMega v4.0 |
+MS5607 30km (100k') |
+ADXL375 200g |
+uBlox Max-8Q |
+BMX160 |
+8MB |
+40mW |
+3.7V |
+
EasyMega v1.0 |
MS5607 30km (100k') |
MMA6555 102g |
@@ -5340,11 +5638,21 @@ production and retired.
- |
3.7V |
|||
EasyTimer v1.0 |
+- |
+16g |
+- |
+BMX160 |
+- |
+- |
+3.7-12V |
+
2¼ inch (5.62cm) |
38mm coupler |
+||||
EasyMini |
+Debug USB Battery |
+Pyro A Pyro B Battery |
+0.8 inch (2.03cm) |
+1½ inch (3.81cm) |
+24mm coupler |
+
Appendix F: Release Notes
-
+
+
+F.1. Release Notes for Version 1.9
+F.1. Release Notes for Version 1.9.5
-
Version 1.9
+Version 1.9.5
F.1.1. AltOS
-
+
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.
+
+
+
+F.1.2. AltosUI
+
+
+
+-
+
-
+
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.
+
+
+
+F.2. Release Notes for Version 1.9.4
+
+
+Version 1.9.4
+
+
+F.2.1. AltOS
+
+
+-
+
-
+
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.
+
+
+
+F.2.2. AltosUI
+
+
+
+-
+
-
+
Add TeleMetrum v3.0 firmware to the Linux and Mac OSX +AltosUI packages.
+
+
+
+F.3. Release Notes for Version 1.9.3
+
+
+Version 1.9.3
+
+
+F.3.1. AltOS
+
+
+-
+
-
+
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.
+
+
+
+F.3.2. AltosUI, TeleGPS, MicroPeak
+
+
+
+-
+
-
+
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.
+
+
+
+F.4. Release Notes for Version 1.9.2
+
+
+Version 1.9.2
+
+
+F.4.1. AltOS
+
+
+-
+
-
+
Add support for TeleMega v4.0
+
+ -
+
Fix time wrapping issue with TeleLCO and TeleFire
+
+
+
+F.4.2. AltosUI, TeleGPS, MicroPeak
+
+
+-
+
-
+
Add column in AltosUI for IMU data from TeleMega and EasyMega
+
+
+
+F.4.3. AltosDroid
+
+
+
+-
+
-
+
Allow sorting of trackers by call, serial, frequency or age
+
+ -
+
Offer selection of font sizes
+
+ -
+
Various bug fixes for older Android versions
+
+
+
+F.5. Release Notes for Version 1.9.1
+
+
+Version 1.9.1
+
+
+F.5.1. AltOS
+
+
+-
+
-
+
Add support for TeleMetrum v3.0
+
+ -
+
Fix accel cal value when changing EasyMega v2.0 pad orientation
+
+ -
+
Correct EasyMega v2.0 magnetometer data axes
+
+ -
+
Fix EasyMega v2.0 idle monitor display of IMU data
+
+ -
+
Report all sensor failures at power-up time.
+
+
+
+F.5.2. AltosUI, TeleGPS, MicroPeak
+
+
+
+-
+
-
+
Display error message when attempting to graph unknown format file.
+
+ -
+
Make it possible to disable APRS once enabled.
+
+ -
+
Display some data for point near cursor in map tab.
+
+ -
+
Support upgrading devices from pre-1.8 firmware
+
+ -
+
Wait for Windows to prepare new devices during firmware +upgrade. This should avoid the âCOMxx: open failedâ message.
+
+
+
F.6. Release Notes for Version 1.9
+
+
+Version 1.9
+
+
F.6.1. AltOS
+
+
-
+
-
Add support for EasyMega v2.0
- @@ -5441,7 +6003,7 @@ production and retired.
-
F.1.2. AltosUI, TeleGPS, MicroPeak
+F.6.2. AltosUI, TeleGPS, MicroPeak
- @@ -5456,12 +6018,12 @@ production and retired.
-
F.2. Release Notes for Version 1.8.7
+F.7. Release Notes for Version 1.8.7
Version 1.8.7
-
F.2.1. AltOS
+F.7.1. AltOS
- @@ -5471,7 +6033,7 @@ production and retired.
-
F.2.2. AltosUI, TeleGPS, MicroPeak
+F.7.2. AltosUI, TeleGPS, MicroPeak
- @@ -5513,12 +6075,12 @@ applications will run with Oracle Java.
-
F.3. Release Notes for Version 1.8.6
+F.8. Release Notes for Version 1.8.6
Version 1.8.6
-
F.3.1. AltOS
+F.8.1. AltOS
- @@ -5537,7 +6099,7 @@ applications will run with Oracle Java.
-
F.3.2. AltosUI, TeleGPS
+F.8.2. AltosUI, TeleGPS
- @@ -5559,7 +6121,7 @@ applications will run with Oracle Java.
-
F.3.3. MicroPeak
+F.8.3. MicroPeak
- @@ -5571,13 +6133,13 @@ applications will run with Oracle Java.
-
F.4. Release Notes for Version 1.8.5
+F.9. 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.4.1. AltOS
+F.9.1. AltOS
- @@ -5587,7 +6149,7 @@ for TeleBT v4, along with a few other minor updates.
-
F.4.2. AltosUI, TeleGPS
+F.9.2. AltosUI, TeleGPS
- @@ -5604,12 +6166,12 @@ devices.
-
F.5. Release Notes for Version 1.8.4
+F.10. Release Notes for Version 1.8.4
Version 1.8.4 includes support for EasyMini version 2.0
-
F.5.1. AltOS
+F.10.1. AltOS
- @@ -5621,7 +6183,7 @@ devices.
-
F.6. Release Notes for Version 1.8.3
+F.11. 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 @@ -5630,7 +6192,7 @@ better and some updates to graph presentation and data downloading.
-
F.6.1. AltOS
+F.11.1. AltOS
AltOS New Features
@@ -5663,7 +6225,7 @@ from capturing log data.
-
F.6.2. AltosUI and TeleGPS Applications
+F.11.2. AltosUI and TeleGPS Applications
AltosUI New Features
@@ -5721,7 +6283,7 @@ tilt angle.
-
F.7. Release Notes for Version 1.8.2
+F.12. 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.
@@ -5731,7 +6293,7 @@ with accelerometer recalibration support in AltosUI. analyzing saved data files.
-
@@ -5744,7 +6306,7 @@ analyzing saved data files.
F.7.1. AltOS
+F.12.1. AltOS
AltOS New Features
-
@@ -5773,7 +6335,7 @@ for graphing or KML export.
F.7.2. AltosUI and TeleGPS Applications
+F.12.2. AltosUI and TeleGPS Applications
AltosUI and TeleGPS New Features
-
F.8. Release Notes for Version 1.8.1
+F.13. 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 @@ -5794,7 +6356,7 @@ above Mach 1.
analyzing saved data files.
-
@@ -5815,7 +6377,7 @@ deceleration.
F.8.1. AltOS
+F.13.1. AltOS
AltOS Bug Fixes
-
@@ -5846,7 +6408,7 @@ broken, so you’d see only the default frequencies.
F.8.2. AltosUI and TeleGPS Applications
+F.13.2. AltosUI and TeleGPS Applications
AltosUI New Features
-
F.9. Release Notes for Version 1.8
+F.14. 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 @@ -5854,7 +6416,7 @@ software and bug fixes in in the flight software for all our boards and ground station interfaces.
-
@@ -5867,7 +6429,7 @@ boards and ground station interfaces.
F.9.1. AltOS
+F.14.1. AltOS
AltOS New Features
-
@@ -5900,14 +6462,14 @@ EasyMega. The Y and Z axes were flipped.
F.9.2. AltosUI and TeleGPS Applications
+F.14.2. AltosUI and TeleGPS Applications
AltosUI New Features
-
F.10. Release Notes for Version 1.7
+F.15. 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.
-
@@ -5932,7 +6494,7 @@ serviced first.
F.10.1. AltOS
+F.15.1. AltOS
AltOS New Features
-
@@ -5947,7 +6509,7 @@ serviced first.
F.10.2. AltosUI and TeleGPS Applications
+F.15.2. AltosUI and TeleGPS Applications
AltosUI New Features
-
F.11. Release Notes for Version 1.6.8
+F.16. 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 @@ -5955,7 +6517,7 @@ telemetry in flight. All TeleMega v1.0, v2.0 and TeleMetrum v2.0 users should update their flight firmware.
-
@@ -5989,7 +6551,7 @@ they can be tested during production.
F.11.1. AltOS
+F.16.1. AltOS
AltOS fixes:
-
@@ -6011,7 +6573,7 @@ Ground Station operation by cleaning up pending operations.
F.11.2. AltosUI, TeleGPS and AltosDroid Applications
+F.16.2. AltosUI, TeleGPS and AltosDroid Applications
AltosUI fixes:
-
F.12. Release Notes for Version 1.6.5
+F.17. 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 @@ -6019,7 +6581,7 @@ telemetry in flight. All TeleMega v1.0, v2.0 and TeleMetrum v2.0 users should update their flight firmware.
-
@@ -6035,7 +6597,7 @@ tested the new firmware before release.
F.12.1. AltOS
+F.17.1. AltOS
AltOS fixes:
-
@@ -6051,14 +6613,14 @@ Windows package.
F.12.2. AltosUI, TeleGPS and AltosDroid Applications
+F.17.2. AltosUI, TeleGPS and AltosDroid Applications
AltosUI fixes:
-
F.13. Release Notes for Version 1.6.4
+F.18. 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.
-
@@ -6078,7 +6640,7 @@ fixes affect all STM32L, STM32F0 and LPC11U14 based devices.
F.13.1. AltOS
+F.18.1. AltOS
AltOS fixes:
-
@@ -6110,7 +6672,7 @@ active.
F.13.2. AltosUI, TeleGPS and AltosDroid Applications
+F.18.2. AltosUI, TeleGPS and AltosDroid Applications
AltosUI, TeleGPS and AltosDroid New Features:
-
F.13.3. Documentation
+F.18.3. Documentation
- @@ -6125,14 +6687,14 @@ active.
-
F.14. Release Notes for Version 1.6.3
+F.19. 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.
-
@@ -6147,7 +6709,7 @@ hardware to driving these pins with software.
F.14.1. AltOS
+F.19.1. AltOS
AltOS fixes:
-
@@ -6192,7 +6754,7 @@ TeleMetrum v2.0 flight computers.
F.14.2. AltosUI and TeleGPS Applications
+F.19.2. AltosUI and TeleGPS Applications
AltosUI and TeleGPS New Features:
-
@@ -6257,7 +6819,7 @@ location of any tracker.
F.14.3. AltosDroid
+F.19.3. AltosDroid
AltosDroid new features:
-
F.14.4. Documentation
+F.19.4. Documentation
- @@ -6270,14 +6832,14 @@ continuity audio alert pattern.
-
F.15. Release Notes for Version 1.6.2
+F.20. 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.
-
@@ -6306,7 +6868,7 @@ up.
F.15.1. AltOS
+F.20.1. AltOS
AltOS New Features:
-
@@ -6325,7 +6887,7 @@ writing the associated .eeprom file when an error is detected.
F.15.2. AltosUI and TeleGPS Applications
+F.20.2. AltosUI and TeleGPS Applications
AltosUI and TeleGPS Fixes:
-
@@ -6350,14 +6912,14 @@ duplication of information
F.15.3. Documentation
+F.20.3. Documentation
We spent a bunch of time trying to improve our documentation
-
F.16. Release Notes for Version 1.6.1
+F.21. 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.
-
@@ -6387,7 +6949,7 @@ variations from transmitting devices.
F.16.1. AltOS
+F.21.1. AltOS
AltOS New Features:
-
@@ -6452,7 +7014,7 @@ run at 10x speed by mistake.
F.16.2. AltosUI and TeleGPS Applications
+F.21.2. AltosUI and TeleGPS Applications
AltosUI and TeleGPS New Features:
-
@@ -6510,14 +7072,14 @@ motion towards rocket.
F.16.3. AltosDroid
+F.21.3. AltosDroid
AltosDroid New Features:
-
F.17. Release Notes for Version 1.6
+F.22. 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.
-
@@ -6559,7 +7121,7 @@ you’ll want to reflash the firmware.
F.17.1. AltOS
+F.22.1. AltOS
AltOS New Features
-
@@ -6634,14 +7196,14 @@ flight computers appear on multiple frequencies by accident.
F.17.2. AltosUI and TeleGPS Applications
+F.22.2. AltosUI and TeleGPS Applications
AltosUI and TeleGPS New Features
-
F.18. Release Notes for Version 1.5
+F.23. 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
-
@@ -6700,7 +7262,7 @@ deceleration.
F.18.1. AltOS
+F.23.1. AltOS
AltOS New Features
-
@@ -6741,13 +7303,13 @@ cases where we just can’t figure out what version is installed.
F.18.2. AltosUI and TeleGPS Applications
+F.23.2. AltosUI and TeleGPS Applications
AltosUI and TeleGPS New Features
-
F.19. Release Notes for Version 1.4.2
+F.24. Release Notes for Version 1.4.2
Version 1.4.2 is a minor release. It fixes Java-related install issues on Windows
-
@@ -6766,7 +7328,7 @@ detection fails.
F.19.1. AltosUI and TeleGPS Applications
+F.24.1. AltosUI and TeleGPS Applications
Windows Install Fixes
-
F.20. Release Notes for Version 1.4.1
+F.25. 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 @@ -6776,7 +7338,7 @@ driver, but Mac and Linux users who do not need the TeleMetrum V2.0 firmware image will not need to upgrade.
-
@@ -6817,14 +7379,14 @@ software, making map downloading fail for most people.
F.20.1. AltosUI and TeleGPS Applications:
+F.25.1. AltosUI and TeleGPS Applications:
Windows Install Fixes
-
F.21. Release Notes for Version 1.4
+F.26. 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
-
@@ -6879,7 +7441,7 @@ as being present.
F.21.1. AltOS
+F.26.1. AltOS
AltOS new features:
-
@@ -6965,7 +7527,7 @@ the product name instead.
F.21.2. AltosUI Application
+F.26.2. AltosUI Application
AltosUI new features:
-
F.21.3. TeleGPS Application
+F.26.3. TeleGPS Application
- @@ -6979,7 +7541,7 @@ to focus on TeleGPS-related functions.
-
@@ -7001,13 +7563,13 @@ configurable amount of time after boost.
F.21.4. Documentation
+F.26.4. Documentation
Documentation changes:
-
F.22. Release Notes for Version 1.3.2
+F.27. 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
-
@@ -7029,7 +7591,7 @@ view and voltages.
F.22.1. AltOS
+F.27.1. AltOS
AltOS fixes:
-
@@ -7057,13 +7619,13 @@ Igniter dialog.
F.22.2. AltosUI Application
+F.27.2. AltosUI Application
AltosUI fixes:
-
F.23. Release Notes for Version 1.3.1
+F.28. 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.
-
@@ -7105,7 +7667,7 @@ getting re-computed incorrectly in inverted mode.
F.23.1. AltOS
+F.28.1. AltOS
AltOS new features:
-
@@ -7141,13 +7703,13 @@ so that all of the map tiles download successfully.
F.23.2. AltosUI Application
+F.28.2. AltosUI Application
AltosUI new features:
-
F.24. Release Notes for Version 1.3
+F.29. 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.
-
@@ -7186,7 +7748,7 @@ digital FM transceivers
F.24.1. AltOS
+F.29.1. AltOS
AltOS new features:
-
@@ -7222,14 +7784,14 @@ default for new downloads
F.24.2. AltosUI Application
+F.29.2. AltosUI Application
AltosUI new features:
-
F.25. Release Notes for Version 1.2.1
+F.30. 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.
-
@@ -7271,7 +7833,7 @@ performance somewhat.
F.25.1. AltOS
+F.30.1. AltOS
AltOS new features:
-
@@ -7328,7 +7890,7 @@ time.
F.25.2. AltosUI Application
+F.30.2. AltosUI Application
AltosUI application new features:
-
F.25.3. AltosDroid
+F.30.3. AltosDroid
- @@ -7340,13 +7902,13 @@ time.
-
F.26. Release Notes for Version 1.2
+F.31. Release Notes for Version 1.2
Version 1.2 is a major release. It adds support for MicroPeak and the MicroPeak USB adapter.
-
@@ -7362,7 +7924,7 @@ multi-tasking scheduler.
F.26.1. AltOS
+F.31.1. AltOS
AltOS New Features:
-
@@ -7395,7 +7957,7 @@ time.
F.26.2. AltosUI and MicroPeak Application
+F.31.2. AltosUI and MicroPeak Application
New Features:
-
F.27. Release Notes for Version 1.1
+F.32. 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 @@ -7404,7 +7966,7 @@ the Google Earth file export issue, and for suggesting the addition of the Ground Distance value in the Descent tab.
-
@@ -7424,7 +7986,7 @@ of rockets flying version 1.1 firmware.
F.27.1. AltOS
+F.32.1. AltOS
AltOS fixes:
-
@@ -7476,13 +8038,13 @@ deciding whether to fetch the analog sensor data.
F.27.2. AltosUI
+F.32.2. AltosUI
AltosUI new features:
-
F.28. Release Notes for Version 1.1
+F.33. 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.
-
@@ -7524,7 +8086,7 @@ the radio was turned off and back on.
F.28.1. AltOS
+F.33.1. AltOS
AltOS Firmware New Features:
-
@@ -7608,13 +8170,13 @@ in 'Monitor Idle' mode.
F.28.2. AltosUI
+F.33.2. AltosUI
AltosUI New Features:
-
F.29. Release Notes for Version 1.0.1
+F.34. 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
-
@@ -7672,7 +8234,7 @@ Mach delay.
F.29.1. AltOS
+F.34.1. AltOS
AltOS New Features
-
@@ -7741,13 +8303,13 @@ placed in "Idle" mode if AltosUI is polling it.
F.29.2. AltosUI Application
+F.34.2. AltosUI Application
AltosUI New Features
-
F.30. Release Notes for Version 0.9.2
+F.35. Release Notes for Version 0.9.2
Version 0.9.2 is an AltosUI bug-fix release, with no firmware changes.
-
@@ -7770,13 +8332,13 @@ invalid, display parsing errors to user.
F.30.1. AltosUI
+F.35.1. AltosUI
AltosUI fixes:
-
F.31. Release Notes for Version 0.9
+F.36. Release Notes for Version 0.9
Version 0.9 adds a few new firmware features and accompanying AltosUI changes, along with new hardware support.
-
F.31.1. AltOS
+F.36.1. AltOS
- @@ -7803,7 +8365,7 @@ running the 0.9 firmware or they will not communicate.
-
F.31.2. AltosUI Application
+F.36.2. AltosUI Application
- @@ -7818,13 +8380,13 @@ running the 0.9 firmware or they will not communicate.
-
F.32. Release Notes for Version 0.8
+F.37. Release Notes for Version 0.8
Version 0.8 offers a major upgrade in the AltosUI interface.
-
F.32.1. AltosUI Application:
+F.37.1. AltosUI Application:
- @@ -7879,13 +8441,13 @@ rocket flight through the Google Earth program.
-
F.33. Release Notes for Version 0.7.1
+F.38. Release Notes for Version 0.7.1
Version 0.7.1 is the first release containing our new cross-platform Java-based user interface.
-
F.33.1. AltosUI Application
+F.38.1. AltosUI Application
- @@ -7943,8 +8505,8 @@ and distance are reported.