From 4862bec43b29264c361950700f935604f41b840b Mon Sep 17 00:00:00 2001 From: Keith Packard Date: Sat, 7 Mar 2015 12:33:36 -0800 Subject: doc: Update telemetry docs to include new packet formats Add TeleMega TeleMetrum v2 and companion data packet formats. List which radio parts each product uses. Document modulation parameters for new data rates. Signed-off-by: Keith Packard --- doc/telemetry.xsl | 499 +++++++++++++++++++++++++++++++++++++++++++++++++----- 1 file changed, 459 insertions(+), 40 deletions(-) (limited to 'doc') diff --git a/doc/telemetry.xsl b/doc/telemetry.xsl index e4101507..2e0b3ea1 100644 --- a/doc/telemetry.xsl +++ b/doc/telemetry.xsl @@ -110,7 +110,7 @@
- Sensor Data + TeleMetrum v1.x, TeleMini and TeleNano Sensor Data @@ -124,7 +124,7 @@ 0x01 - TeleMetrum Sensor Data + TeleMetrum v1.x Sensor Data 0x02 @@ -138,7 +138,7 @@ - TeleMetrum, TeleMini and TeleNano share this same packet + TeleMetrum v1.x, TeleMini and TeleNano share this same packet format for sensor data. Each uses a distinct packet type so that the receiver knows which data values are valid and which are undefined. @@ -213,6 +213,316 @@
+
+ TeleMega Sensor Data + + + + + + + Type + Description + + + + + 0x08 + TeleMega IMU Sensor Data + + + 0x09 + TeleMega Kalman and Voltage Data + + + + + + TeleMega has a lot of sensors, and so it splits the sensor + data into two packets. The raw IMU data are sent more often; + the voltage values don't change very fast, and the Kalman + values can be reconstructed from the IMU data. + + + IMU Sensor Data packets are transmitted once per second on the + ground, 10 times per second during ascent and once per second + during descent and landing + + + Kalman and Voltage Data packets are transmitted once per second on the + ground, 5 times per second during ascent and once per second + during descent and landing + + + The high-g accelerometer is reported separately from the data + for the 9-axis IMU (accel/gyro/mag). The 9-axis IMU is mounted + so that the X axis is "across" the board (along the short + axis0, the Y axis is "along" the board (along the long axis, + with the high-g accelerometer) and the Z axis is "through" the + board (perpendicular to the board). Rotation measurements are + around the respective axis, so Y rotation measures the spin + rate of the rocket while X and Z rotation measure the tilt + rate. + + + The overall tilt angle of the rocket is computed by first + measuring the orientation of the rocket on the pad using the 3 + axis accelerometer, and then integrating the overall tilt rate + from the 3 axis gyroscope to compute the total orientation + change of the airframe since liftoff. + + + TeleMega IMU Sensor Packet Contents + + + + + + + + Offset + Data Type + Name + Description + + + + + 5uint8_torientAngle from vertical in degrees + + + 6int16_taccelHigh G accelerometer + + + 8int32_tprespressure (Pa * 10) + + + 12int16_ttemptemperature (°C * 100) + + + 14int16_taccel_xX axis acceleration (across) + + + 16int16_taccel_yY axis acceleration (along) + + + 18int16_taccel_zZ axis acceleration (through) + + + 20int16_tgyro_xX axis rotation (across) + + + 22int16_tgyro_yY axis rotation (along) + + + 24int16_tgyro_zZ axis rotation (through) + + + 26int16_tmag_xX field strength (across) + + + 28int16_tmag_yY field strength (along) + + + 30int16_tmag_zZ field strength (through) + + + 32 + + + +
+ + TeleMega Kalman and Voltage Data Packet Contents + + + + + + + + Offset + Data Type + Name + Description + + + + + 5uint8_tstateFlight state + + + 6int16_tv_battbattery voltage + + + 8int16_tv_pyropyro battery voltage + + + 10int8_t[6]sensepyro continuity sense + + + 16int32_tground_presAverage barometer reading on ground + + + 20int16_tground_accelAverage accelerometer reading on ground + + + 22int16_taccel_plus_gAccel calibration at +1g + + + 24int16_taccel_minus_gAccel calibration at -1g + + + 26int16_taccelerationm/s² * 16 + + + 28int16_tspeedm/s * 16 + + + 30int16_theightm + + + 32 + + + +
+
+
+ TeleMetrum v2 Sensor Data + + + + + + + Type + Description + + + + + 0x0A + TeleMetrum v2 Sensor Data + + + 0x0B + TeleMetrum v2 Calibration Data + + + + + + TeleMetrum v2 has higher resolution barometric data than + TeleMetrum v1, and so the constant calibration data is + split out into a separate packet. + + + TeleMetrum v2 Sensor Data packets are transmitted once per second on the + ground, 10 times per second during ascent and once per second + during descent and landing + + + TeleMetrum v2 Calibration Data packets are always transmitted once per second. + + + TeleMetrum v2 Sensor Packet Contents + + + + + + + + Offset + Data Type + Name + Description + + + + + 5uint8_tstateFlight state + + + 6int16_taccelaccelerometer + + + 8int32_tprespressure sensor (Pa * 10) + + + 12int16_ttemptemperature sensor (°C * 100) + + + + 14int16_taccelerationm/s² * 16 + + + 16int16_tspeedm/s * 16 + + + 18int16_theightm + + + + 20int16_tv_battbattery voltage + + + 22int16_tsense_ddrogue continuity sense + + + 24int16_tsense_mmain continuity sense + + + 26pad[6]pad bytes + + + 32 + + + +
+ + TeleMetrum v2 Calibration Data Packet Contents + + + + + + + + Offset + Data Type + Name + Description + + + + + 5pad[3]pad bytes + + + 8int32_tground_presAverage barometer reading on ground + + + 12int16_tground_accelAverage accelerometer reading on ground + + + 14int16_taccel_plus_gAccel calibration at +1g + + + 16int16_taccel_minus_gAccel calibration at -1g + + + 18pad[14]pad bytes + + + 32 + + + +
+
Configuration Data @@ -315,7 +625,7 @@ This packet provides all of the information available from the - Venus SkyTraq GPS receiver—position, time, speed and precision + GPS receiver—position, time, speed and precision estimates. @@ -604,62 +914,169 @@
+
+ Companion Data Data + + + + + + + Type + Description + + + + + 0x07 + Companion Data Data + + + + + + When a companion board is attached to TeleMega or TeleMetrum, + it can provide telemetry data to be included in the + downlink. The companion board can provide up to 12 16-bit data + values. + + + The companion board itself specifies the transmission rate. On + the ground and during descent, that rate is limited to one + packet per second. During ascent, that rate is limited to 10 + packets per second. + + + Companion Data Contents + + + + + + + + Offset + Data Type + Name + Description + + + + + 5uint8_tboard_id + Type of companion board attached + + + 6uint8_tupdate_period + How often telemetry is sent, in 1/100ths of a second + + + 7uint8_tchannels + Number of data channels supplied + + + 8uint16_t[12]companion_data + Up to 12 channels of 16-bit companion data + + + 32 + + + +
+
Data Transmission - Altus Metrum devices use the Texas Instruments CC1111 - microcontroller which includes an integrated sub-GHz digital - transceiver. This transceiver is used to both transmit and - receive the telemetry packets. This section discusses what - modulation scheme is used and how this device is configured. + Altus Metrum devices use Texas Instruments sub-GHz digital radio + products. Ground stations use parts with HW FEC while some + flight computers perform FEC in software. TeleGPS is + transmit-only. + + Altus Metrum Radio Parts + + + + + + + Part Number + Description + Used in + + + + + CC111110mW transceiver with integrated SoC + TeleDongle v0.2, TeleBT v1.0, TeleMetrum v1.x, TeleMini + + + CC112035mW transceiver with SW FEC + TeleMetrum v2, TeleMega + + + CC120035mW transceiver with HW FEC + TeleDongle v3.0, TeleBT v3.0 + + + CC115L14mW transmitter with SW FEC + TeleGPS + + + +
Modulation Scheme Texas Instruments provides a tool for computing modulation parameters given a desired modulation format and basic bit - rate. For AltOS, the basic bit rate was specified as 38 kBaud, - resulting in the following signal parmeters: + rate. + + While we might like to use something with better low-signal + performance like BPSK, the radios we use don't support that, + but do support Gaussian frequency shift keying (GFSK). Regular + frequency shift keying (FSK) encodes the signal by switching + the carrier between two frequencies. The Gaussian version is + essentially the same, but the shift between frequencies gently + follows a gaussian curve, rather than switching + immediately. This tames the bandwidth of the signal without + affecting the ability to transmit data. + + For AltOS, there are three available bit rates, 38.4kBaud, + 9.6kBaud and 2.4kBaud resulting in the following signal + parmeters: + Modulation Scheme - - - + + + - Parameter - Value - Description + Rate + Deviation + Receiver Bandwidth - Modulation - GFSK - Gaussian Frequency Shift Keying - - - Deviation - 20.507812 kHz - Frequency modulation - - - Data rate - 38.360596 kBaud - Raw bit rate + 38.4kBaud + 20.5kHz + 100kHz - RX Filter Bandwidth - 93.75 kHz - Receiver Band pass filter bandwidth + 9.6kBaud + 5.125kHz + 25kHz - IF Frequency - 140.62 kHz - Receiver intermediate frequency + 2.4kBaud + 1.5kHz + 5kHz @@ -668,10 +1085,12 @@
Error Correction - The cc1111 provides forward error correction in hardware, - which AltOS uses to improve reception of weak signals. The - overall effect of this is to halve the available bandwidth for - data from 38 kBaud to 19 kBaud. + The cc1111 and cc1200 provide forward error correction in + hardware; on the cc1120 and cc115l that's done in + software. AltOS uses this to improve reception of weak + signals. As it's a rate 1/2 encoding, each bit of data takes + two bits when transmitted, so the effective data rate is half + of the raw transmitted bit rate.
Error Correction -- cgit v1.2.3 From fcb523cd083503591fa1277648e5deb258bbbaf4 Mon Sep 17 00:00:00 2001 From: Keith Packard Date: Tue, 19 May 2015 10:16:10 -0700 Subject: doc: Clarify what 'after motor' means Note that this means after motor burn-out, not after motor start. Signed-off-by: Keith Packard --- doc/altusmetrum.xsl | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'doc') diff --git a/doc/altusmetrum.xsl b/doc/altusmetrum.xsl index 1631983a..d44cd784 100644 --- a/doc/altusmetrum.xsl +++ b/doc/altusmetrum.xsl @@ -2620,9 +2620,9 @@ NAR #88757, TRA #12200 After Motor. The flight software counts each time the - rocket starts accelerating (presumably due to a motor or - motors igniting). Use this value to count ignitions for - multi-staged or multi-airstart launches. + rocket starts accelerating and then decelerating + (presumably due to a motor or motors burning). Use this + value for multi-staged or multi-airstart launches. -- cgit v1.2.3 From 3cb5b31a534ab0c987667f37c976a5cd589d42a5 Mon Sep 17 00:00:00 2001 From: Keith Packard Date: Wed, 15 Jul 2015 11:40:24 -0700 Subject: doc: Update for 1.6.1 Signed-off-by: Keith Packard --- doc/Makefile | 4 +- doc/altusmetrum.xsl | 579 ++++++++++++++++++++++++++++++++++++-------- doc/load-maps.png | Bin 520872 -> 572796 bytes doc/monitor-idle.png | Bin 0 -> 64749 bytes doc/release-notes-1.6.1.xsl | 189 +++++++++++++++ 5 files changed, 665 insertions(+), 107 deletions(-) create mode 100644 doc/monitor-idle.png create mode 100644 doc/release-notes-1.6.1.xsl (limited to 'doc') diff --git a/doc/Makefile b/doc/Makefile index 2887a229..9c6189b4 100644 --- a/doc/Makefile +++ b/doc/Makefile @@ -18,7 +18,8 @@ RELNOTES=\ release-notes-1.4.html \ release-notes-1.4.1.html \ release-notes-1.5.html \ - release-notes-1.6.html + release-notes-1.6.html \ + release-notes-1.6.1.html PICTURES=\ altosui.png \ @@ -51,6 +52,7 @@ PICTURES=\ micropeak-statistics.png \ MicroPeakUSB-2.0-inuse.jpg \ MicroPeakUSB-2.0.jpg \ + monitor-idle.png \ scan-channels.png \ site-map.png \ table.png \ diff --git a/doc/altusmetrum.xsl b/doc/altusmetrum.xsl index d44cd784..a40481f1 100644 --- a/doc/altusmetrum.xsl +++ b/doc/altusmetrum.xsl @@ -40,6 +40,13 @@ + + 1.6.1 + 15 July 2015 + + Minor release adding TeleBT v3.0 support. + + 1.6 8 January 2015 @@ -3853,8 +3860,7 @@ NAR #88757, TRA #12200 Before heading out to a new launch site, you can use this to load satellite images in case you don't have internet - connectivity at the site. This loads a fairly large area - around the launch site, which should cover any flight you're likely to make. + connectivity at the site. There's a drop-down menu of launch sites we know about; if @@ -3909,15 +3915,18 @@ NAR #88757, TRA #12200 You can specify the range of zoom levels to download; smaller numbers show more area with less resolution. The default level, 0, shows about 3m/pixel. One zoom level change - doubles or halves that number. + doubles or halves that number. Larger zoom levels show more + detail, smaller zoom levels less. - The Tile Radius value sets how large an area around the center - point to download. Each tile is 512x512 pixels, and the - 'radius' value specifies how many tiles away from the center - will be downloaded. Specify a radius of 0 and you get only the - center tile. A radius of 1 loads a 3x3 grid, centered on the - specified location. + The Map Radius value sets how large an area around the center + point to download. Select a value large enough to cover any + plausible flight from that site. Be aware that loading a large + area with a high maximum zoom level can attempt to download a + lot of data. Loading hybrid maps with a 10km radius at a + minimum zoom of -2 and a maximum zoom of 2 consumes about + 120MB of space. Terrain and road maps consume about 1/10 as + much space as satellite or hybrid maps. Clicking the 'Load Map' button will fetch images from Google @@ -3929,6 +3938,13 @@ NAR #88757, TRA #12200
Monitor Idle + + + + + + + This brings up a dialog similar to the Monitor Flight UI, except it works with the altimeter in “idle” mode by sending @@ -3939,22 +3955,28 @@ NAR #88757, TRA #12200 cannot manage to run Monitor Idle, then it's very likely that your callsigns are different in some way. + + You can change the frequency and callsign used to communicate + with the flight computer; they must both match the + configuration in the flight computer exactly. +
AltosDroid AltosDroid provides the same flight monitoring capabilities as - AltosUI, but runs on Android devices and is designed to connect - to a TeleBT receiver over Bluetooth™. AltosDroid monitors + AltosUI, but runs on Android devices. AltosDroid is designed to connect + to a TeleBT receiver over Bluetooth™ and (on Android devices supporting + USB On-the-go) TeleDongle and TeleBT devices over USB. AltosDroid monitors telemetry data, logging it to internal storage in the Android - device, and presents that data in a UI the same way the 'Monitor - Flight' window does in AltosUI. + device, and presents that data in a UI similar to the 'Monitor + Flight' window in AltosUI. - This manual will explain how to configure AltosDroid, connect - to TeleBT, operate the flight monitoring interface and describe - what the displayed data means. + This manual will explain how to configure AltosDroid, connect to + TeleBT or TeleDongle, operate the flight monitoring interface + and describe what the displayed data means.
Installing AltosDroid @@ -3968,7 +3990,7 @@ NAR #88757, TRA #12200
- Connecting to TeleBT + Connecting to TeleBT over Bluetooth™ Press the Android 'Menu' button or soft-key to see the configuration options available. Select the 'Connect a device' @@ -3982,15 +4004,91 @@ NAR #88757, TRA #12200 scanning.
+
+ 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 and a standard A female + connector on the other end. Plug in your TeleDongle or TeleBT + device to the adapter cable and the adapter cable into your + phone and AltosDroid should automatically start up. If it + doesn't, the most likely reason is that your Android device + doesn't support USB On-the-go. + +
Configuring AltosDroid - The only configuration option available for AltosDroid is - which frequency to listen on. Press the Android 'Menu' button - or soft-key and pick the 'Select radio frequency' entry. That - brings up a menu of pre-set radio frequencies; pick the one - which matches your altimeter. + There are several configuration and operation parameters + available in the AltosDroid menu. +
+ Select radio frequency + + This selects which frequency to listen on by bringing up a + menu of pre-set radio frequencies. Pick the one which matches + your altimeter. + +
+
+ Select data rate + + Altus Metrum transmitters can be configured to operate at + lower data rates to improve transmission range. If you have + configured your device to do this, this menu item allows you + to change the receiver to match. + +
+
+ Change units + + This toggles between metric and imperial units. + +
+
+ Load maps + + Brings up a dialog allowing you to download offline map + tiles so that you can have maps available even if you have + no network connectivity at the launch site. + +
+
+ Map type + + Displays a menu of map types and lets you select one. Hybrid + maps include satellite images with a roadmap + overlaid. Satellite maps dispense with the roadmap + overlay. Roadmap shows just the roads. Terrain includes + roads along with shadows indicating changes in elevation, + and other geographical features. + +
+
+ Toggle Online/Offline maps + + Switches between online and offline maps. Online maps will + show a 'move to current position' icon in the upper right + corner, while offline maps will have copyright information + all over the map. Otherwise, they're pretty similar. + +
+
+ Select Tracker + + Switches the information displays to show data for a + different transmitting device. The map will always show all + of the devices in view. Trackers are shown and selected by + serial number, so make sure you note the serial number of + devices in each airframe. + +
+
+ Delete Track + + Deletes all information about a transmitting device. + +
AltosDroid Flight Monitoring @@ -4004,91 +4102,353 @@ NAR #88757, TRA #12200
Pad - The 'Launch Pad' tab shows information used to decide when the + The 'Pad' tab shows information used to decide when the rocket is ready for flight. The first elements include red/green indicators, if any of these is red, you'll want to evaluate - whether the rocket is ready to launch: - - - Battery Voltage - - - This indicates whether the Li-Po battery - powering the TeleMetrum has sufficient charge to last for - the duration of the flight. A value of more than - 3.8V is required for a 'GO' status. - - - - - Apogee Igniter Voltage - - - This indicates whether the apogee - igniter has continuity. If the igniter has a low - resistance, then the voltage measured here will be close - to the Li-Po battery voltage. A value greater than 3.2V is - required for a 'GO' status. - - - - - Main Igniter Voltage - - - This indicates whether the main - igniter has continuity. If the igniter has a low - resistance, then the voltage measured here will be close - to the Li-Po battery voltage. A value greater than 3.2V is - required for a 'GO' status. - - - - - On-board Data Logging - - - This indicates whether there is - space remaining on-board to store flight data for the - upcoming flight. If you've downloaded data, but failed - to erase flights, there may not be any space - left. TeleMetrum can store multiple flights, depending - on the configured maximum flight log size. TeleMini - stores only a single flight, so it will need to be - downloaded and erased after each flight to capture - data. This only affects on-board flight logging; the - altimeter will still transmit telemetry and fire - ejection charges at the proper times. - - - - - GPS Locked - - - For a TeleMetrum or TeleMega device, this indicates whether the GPS receiver is - currently able to compute position information. GPS requires - at least 4 satellites to compute an accurate position. - - - - - GPS Ready - - - For a TeleMetrum or TeleMega device, this indicates whether GPS has reported at least - 10 consecutive positions without losing lock. This ensures - that the GPS receiver has reliable reception from the - satellites. - - - - + whether the rocket is ready to launch. - The Launchpad tab also shows the computed launch pad position - and altitude, averaging many reported positions to improve the - accuracy of the fix. + When the pad tab is selected, the voice responses will + include status changes to the igniters and GPS reception, + letting you know if the rocket is still ready for launch. + + + + Battery + + + This indicates whether the Li-Po battery + powering the transmitter has sufficient charge to last for + the duration of the flight. A value of more than + 3.8V is required for a 'GO' status. + + + + + Receiver Battery + + + This indicates whether the Li-Po battery + powering the TeleBT has sufficient charge to last for + the duration of the flight. A value of more than + 3.8V is required for a 'GO' status. + + + + + Data Logging + + + This indicates whether there is space remaining + on-board to store flight data for the upcoming + flight. If you've downloaded data, but failed to + erase flights, there may not be any space + left. TeleMetrum and TeleMega can store multiple + flights, depending on the configured maximum flight + log size. TeleGPS logs data continuously. TeleMini + stores only a single flight, so it will need to be + downloaded and erased after each flight to capture + data. This only affects on-board flight logging; the + altimeter will still transmit telemetry and fire + ejection charges at the proper times. + + + + + GPS Locked + + + For a TeleMetrum or TeleMega device, this indicates whether the GPS receiver is + currently able to compute position information. GPS requires + at least 4 satellites to compute an accurate position. + + + + + GPS Ready + + + For a TeleMetrum or TeleMega device, this indicates whether GPS has reported at least + 10 consecutive positions without losing lock. This ensures + that the GPS receiver has reliable reception from the + satellites. + + + + + Apogee Igniter + + + This indicates whether the apogee + igniter has continuity. If the igniter has a low + resistance, then the voltage measured here will be close + to the Li-Po battery voltage. A value greater than 3.2V is + required for a 'GO' status. + + + + + Main Igniter + + + This indicates whether the main + igniter has continuity. If the igniter has a low + resistance, then the voltage measured here will be close + to the Li-Po battery voltage. A value greater than 3.2V is + required for a 'GO' status. + + + + + Igniter A-D + + + This indicates whether the indicated additional pyro + channel igniter has continuity. If the igniter has a + low resistance, then the voltage measured here will + be close to the Li-Po battery voltage. A value + greater than 3.2V is required for a 'GO' status. + + + + + + The Pad tab also shows the location of the Android device. + +
+
+ Flight + + The 'Flight' tab shows information used to evaluate and spot + a rocket while in flight. It displays speed and height data + to monitor the health of the rocket, along with elevation, + range and bearing to help locate the rocket in the sky. + + + While the Flight tab is displayed, the voice announcements + will include current speed, height, elevation and bearing + information. + + + + Speed + + + Shows current vertical speed. During descent, the + speed values are averaged over a fairly long time to + try and make them steadier. + + + + + Height + + + Shows the current height above the launch pad. + + + + + Max Speed + + + Shows the maximum vertical speed seen during the flight. + + + + + Max Height + + + Shows the maximum height above launch pad. + + + + + Elevation + + + This is the angle above the horizon from the android + devices current position. + + + + + Range + + + The total distance from the android device to the + rocket, including both ground distance and + difference in altitude. Use this to gauge how large + the rocket is likely to appear in the sky. + + + + + Bearing + + + This is the aziumuth from true north for the rocket + from the android device. Use this in combination + with the Elevation value to help locate the rocket + in the sky, or at least to help point the antenna in + the general direction. This is provided in both + degrees and a compass point (like West South + West). You'll want to know which direction is true + north before launching your rocket. + + + + + Ground Distance + + + This shows the distance across the ground to the + lat/lon where the rocket is located. Use this to + estimate what is currently under the rocket. + + + + + Latitude/Longitude + + + Displays the last known location of the rocket. + + + + + Apogee Igniter + + + This indicates whether the apogee + igniter has continuity. If the igniter has a low + resistance, then the voltage measured here will be close + to the Li-Po battery voltage. A value greater than 3.2V is + required for a 'GO' status. + + + + + Main Igniter + + + This indicates whether the main + igniter has continuity. If the igniter has a low + resistance, then the voltage measured here will be close + to the Li-Po battery voltage. A value greater than 3.2V is + required for a 'GO' status. + + + + +
+
+ Recover + + The 'Recover' tab shows information used while recovering the + rocket on the ground after flight. + + + While the Recover tab is displayed, the voice announcements + will include distance along with either bearing or + direction, depending on whether you are moving. + + + + Bearing + + + This is the aziumuth from true north for the rocket + from the android device. Use this in combination + with the Elevation value to help locate the rocket + in the sky, or at least to help point the antenna in + the general direction. This is provided in both + degrees and a compass point (like West South + West). You'll want to know which direction is true + north before launching your rocket. + + + + + Direction + + + When you are in motion, this provides the angle from + your current direction of motion towards the rocket. + + + + + Distance + + + Distance over the ground to the rocket. + + + + + Tar Lat/Tar Lon + + + Displays the last known location of the rocket. + + + + + My Lat/My Lon + + + Displays the location of the Android device. + + + + + Max Height + + + Shows the maximum height above launch pad. + + + + + Max Speed + + + Shows the maximum vertical speed seen during the flight. + + + + + Max Accel + + + Shows the maximum vertical acceleration seen during the flight. + + + + +
+
+ Map + + The 'Map' tab shows a map of the area around the rocket + being tracked along with information needed to recover it. + + + On the map itself, icons showing the location of the android + device along with the last known location of each tracker. A + blue line is drawn from the android device location to the + currently selected tracker. + + + Below the map, the distance and either bearing or direction + along with the lat/lon of the target and the android device + are shown + + + The Map tab provides the same voice announcements as the + Recover tab.
@@ -4097,9 +4457,9 @@ NAR #88757, TRA #12200 AltosDroid always saves every bit of telemetry data it receives. To download that to a computer for use with AltosUI, - simply remove the SD card from your Android device, or connect - your device to your computer's USB port and browse the files - on that device. You will find '.telem' files in the TeleMetrum + remove the SD card from your Android device, or connect your + device to your computer's USB port and browse the files on + that device. You will find '.telem' files in the TeleMetrum directory that will work with AltosUI directly. @@ -5915,6 +6275,13 @@ NAR #88757, TRA #12200 Release Notes + + Version 1.6.1 + + Version 1.6 + + +
+ + Version 1.6.1 includes support for our updated TeleBT v3.0 + product and bug fixes in in the flight software for all our boards + and ground station interfaces. + + + AltOS New Features + + + + Add support for TeleBT v3.0 boards. + + + + + Add support for uncompressed APRS data, providing support + for older APRS receivers. Uncompressed APRS data is less + precise, takes more bandwidth and doesn't have integrated + altitude data. + + + + + + AltOS Fixes + + + + Make TeleDongle and TeleBT more tolerant of data rate + variations from transmitting devices. + + + + + + AltosUI and TeleGPS New Features + + + + Add map to Monitor Idle display. It's nice to be able to + verify that maps are working, instead of needing to use + Monitor Flight. + + + + + + AltosUI Fixes + + + + Fix frequency configuration to round values instead of + truncate them, avoiding a common 1kHz error in the setting. + + + + + Turn the Windows stub into a more useful program that can + launch the application with parameters so that file manager + icons work more reliably. + + + + + Force KML export to use a C locale so that numbers are + formatted with '.' instead of ',' for a decimal separator in + non-US locales. + + + + + Preload map tiles based on distance rather than number of + tiles; this means you get the same resolution covering the + entire area, rather than having high resolution near the + center and low resolution further away. + + + + + Allow configuration of frequency and callsign in Monitor + Idle mode. + + + + + Fix layout weirdness when resizing windows on + Windows. Windows shouldn't have giant blank spaces around + the useful content anymore. + + + + + Fix layout weirdness when resizing windows on + Windows. Windows shouldn't have giant blank spaces around + the useful content anymore. + + + + + Use a longer filter for descent speed values. This should + provide something more useful on the display, although it + will take longer to respond to changes now. + + + + + Make Replay Flight run in realtime again. It had been set to + run at 10x speed by mistake. + + + + + + AltosDroid New Features + + + + Add offline map support using mapping code from AltosUI. + + + + + Support TeleDongle (and TeleBT via USB) on devices + supporting USB On-The-Go. + + + + + Display additional TeleMega pyro channel status in Pad tab. + + + + + Switch between metric and imperial units. + + + + + Monitor TeleBT battery voltage. + + + + + Track multiple devices at the same time, selecting between + them with a menu or using the map. + + + + + Add hybrid, satellite and terrain map types. + + + + + + AltosDroid Fixes + + + + Use standard Android display conventions so that a menu + button is available in the application title bar. + + + + + Adjust layout to work on large and small screens; shrinking + the go/no-go lights in smaller environments to try and make + everything visible. + + + + + Make voice announcements depend on current tab. + + + + + Compute adjustment to current travel direction while in + motion towards rocket. + + + + +
-- cgit v1.2.3