From 9953a5f0440b269dac5c675f120e6a31dde8ec69 Mon Sep 17 00:00:00 2001 From: Keith Packard Date: Mon, 18 Nov 2013 12:06:31 -0800 Subject: [PATCH] doc: Get altusmetrum.xsl to validate Mostly involved getting the listitem contents into para elements. Signed-off-by: Keith Packard --- doc/altusmetrum.xsl | 320 +++++++++++++++++++++++++++--------- doc/release-notes-0.7.1.xsl | 28 +++- doc/release-notes-0.8.xsl | 28 +++- doc/release-notes-0.9.2.xsl | 6 + doc/release-notes-0.9.xsl | 6 + doc/release-notes-1.0.1.xsl | 48 ++++-- doc/release-notes-1.1.1.xsl | 20 ++- doc/release-notes-1.1.xsl | 64 ++++++-- doc/release-notes-1.2.1.xsl | 48 ++++-- doc/release-notes-1.2.xsl | 16 +- doc/release-notes-1.3.xsl | 58 ++++--- 11 files changed, 483 insertions(+), 159 deletions(-) diff --git a/doc/altusmetrum.xsl b/doc/altusmetrum.xsl index 1df270bc..5375e8c2 100644 --- a/doc/altusmetrum.xsl +++ b/doc/altusmetrum.xsl @@ -1,4 +1,4 @@ - + @@ -103,7 +103,8 @@ - + + Acknowledgements Thanks to Bob Finch, W9YA, NAR 12965, TRA 12350 for writing "The Mere-Mortals Quick Start/Usage Guide to the Altus Metrum Starter @@ -130,7 +131,7 @@ Keith Packard, KD7SQG NAR #88757, TRA #12200 - + Introduction and Overview @@ -490,16 +491,24 @@ NAR #88757, TRA #12200 configured as follows: + Sets the radio frequency to 434.550MHz + + Sets the radio calibration back to the factory value. + + Sets the callsign to N0CALL + + Does not go to 'pad' mode after five seconds. + @@ -991,12 +1000,12 @@ NAR #88757, TRA #12200 - - The Launchpad tab also shows the computed launch pad position - and altitude, averaging many reported positions to improve the - accuracy of the fix. - + + The Launchpad tab also shows the computed launch pad position + and altitude, averaging many reported positions to improve the + accuracy of the fix. +
Ascent @@ -1821,12 +1830,12 @@ NAR #88757, TRA #12200 - - The Launchpad tab also shows the computed launch pad position - and altitude, averaging many reported positions to improve the - accuracy of the fix. - - + + + The Launchpad tab also shows the computed launch pad position + and altitude, averaging many reported positions to improve the + accuracy of the fix. +
@@ -1913,19 +1922,29 @@ NAR #88757, TRA #12200 So, to recap, on the ground the hardware you'll need includes: - an antenna and feed-line or adapter + + an antenna and feed-line or adapter + - a TeleDongle + + a TeleDongle + - a notebook computer + + a notebook computer + - optionally, a hand-held GPS receiver + + optionally, a hand-held GPS receiver + - optionally, an HT or receiver covering 435 MHz + + optionally, an HT or receiver covering 435 MHz + @@ -2021,14 +2040,18 @@ NAR #88757, TRA #12200 - Make sure TeleMetrum is aligned precisely along the axis of - acceleration so that the accelerometer can accurately - capture data during the flight. + + Make sure TeleMetrum is aligned precisely along the axis of + acceleration so that the accelerometer can accurately + capture data during the flight. + - Watch for any metal touching components on the - board. Shorting out connections on the bottom of the board - can cause the altimeter to fail during flight. + + Watch for any metal touching components on the + board. Shorting out connections on the bottom of the board + can cause the altimeter to fail during flight. +
@@ -2094,18 +2117,22 @@ NAR #88757, TRA #12200 attenuate the GPS signal. - Conductive tubing or coatings. Carbon fiber and metal - tubing, or metallic paint will all dramatically attenuate the - GPS signal. We've never heard of anyone successfully - receiving GPS from inside these materials. + + Conductive tubing or coatings. Carbon fiber and metal + tubing, or metallic paint will all dramatically attenuate the + GPS signal. We've never heard of anyone successfully + receiving GPS from inside these materials. + - Metal components near the GPS patch antenna. These will - de-tune the patch antenna, changing the resonant frequency - away from the L1 carrier and reduce the effectiveness of the - antenna. You can place as much stuff as you like beneath the - antenna as that's covered with a ground plane. But, keep - wires and metal out from above the patch antenna. + + Metal components near the GPS patch antenna. These will + de-tune the patch antenna, changing the resonant frequency + away from the L1 carrier and reduce the effectiveness of the + antenna. You can place as much stuff as you like beneath the + antenna as that's covered with a ground plane. But, keep + wires and metal out from above the patch antenna. + @@ -2132,16 +2159,21 @@ NAR #88757, TRA #12200 - Keep wires from different circuits apart. Moving circuits - further apart will reduce RFI. + + Keep wires from different circuits apart. Moving circuits + further apart will reduce RFI. + + Avoid parallel wires from different circuits. The longer two wires run parallel to one another, the larger the amount of transferred energy. Cross wires at right angles to reduce RFI. + + Twist wires from the same circuits. Two wires the same distance from the transmitter will get the same amount of induced energy which will then cancel out. Any time you have @@ -2149,14 +2181,17 @@ NAR #88757, TRA #12200 even out distances and reduce RFI. For altimeters, this includes battery leads, switch hookups and igniter circuits. + + Avoid resonant lengths. Know what frequencies are present in the environment and avoid having wire lengths near a natural resonant length. Altusmetrum products transmit on the 70cm amateur band, so you should avoid lengths that are a simple ratio of that length; essentially any multiple of 1/4 of the wavelength (17.5cm). + @@ -2238,59 +2273,83 @@ NAR #88757, TRA #12200 Updating TeleMetrum Firmware + Find the 'programming cable' that you got as part of the starter kit, that has a red 8-pin MicroMaTch connector on one end and a red 4-pin MicroMaTch connector on the other end. + + Take the 2 screws out of the TeleDongle case to get access to the circuit board. + + Plug the 8-pin end of the programming cable to the matching connector on the TeleDongle, and the 4-pin end to the matching connector on the TeleMetrum. Note that each MicroMaTch connector has an alignment pin that goes through a hole in the PC board when you have the cable oriented correctly. + + Attach a battery to the TeleMetrum board. + + Plug the TeleDongle into your computer's USB port, and power up the TeleMetrum. + + Run AltosUI, and select 'Flash Image' from the File menu. + + Pick the TeleDongle device from the list, identifying it as the programming device. + + Select the image you want put on the TeleMetrum, which should have a name in the form telemetrum-v1.2-1.0.0.ihx. It should be visible in the default directory, if not you may have to poke around your system to find it. + + Make sure the configuration parameters are reasonable looking. If the serial number and/or RF configuration values aren't right, you'll need to change them. + + Hit the 'OK' button and the software should proceed to flash the TeleMetrum with new firmware, showing a progress bar. + + Confirm that the TeleMetrum board seems to have updated OK, which you can do by plugging in to it over USB and using a terminal program to connect to the board and issue the 'v' command to check the version, etc. + + If something goes wrong, give it another try. + @@ -2298,16 +2357,21 @@ NAR #88757, TRA #12200 Updating TeleMini Firmware + You'll need a special 'programming cable' to reprogram the TeleMini. It's available on the Altus Metrum web store, or you can make your own using an 8-pin MicroMaTch connector on one end and a set of four pins on the other. - + + + Take the 2 screws out of the TeleDongle case to get access to the circuit board. - + + + Plug the 8-pin end of the programming cable to the matching connector on the TeleDongle, and the 4-pins into the holes in the TeleMini circuit board. Note that the MicroMaTch @@ -2315,44 +2379,63 @@ NAR #88757, TRA #12200 the PC board when you have the cable oriented correctly, and that pin 1 on the TeleMini board is marked with a square pad while the other pins have round pads. - + + + Attach a battery to the TeleMini board. - + + + Plug the TeleDongle into your computer's USB port, and power up the TeleMini - + + + Run AltosUI, and select 'Flash Image' from the File menu. - + + + Pick the TeleDongle device from the list, identifying it as the programming device. - + + + Select the image you want put on the TeleMini, which should have a name in the form telemini-v1.0-1.0.0.ihx. It should be visible in the default directory, if not you may have to poke around your system to find it. - + + + Make sure the configuration parameters are reasonable looking. If the serial number and/or RF configuration values aren't right, you'll need to change them. - + + + Hit the 'OK' button and the software should proceed to flash the TeleMini with new firmware, showing a progress bar. - + + + Confirm that the TeleMini board seems to have updated OK, which you can do by configuring it over the radio link through the TeleDongle, or letting it come up in "flight" mode and listening for telemetry. - + + + If something goes wrong, give it another try. - + +
@@ -2363,68 +2446,94 @@ NAR #88757, TRA #12200 + Find the 'programming cable' that you got as part of the starter kit, that has a red 8-pin MicroMaTch connector on one end and a red 4-pin MicroMaTch connector on the other end. - + + + Find the USB cable that you got as part of the starter kit, and plug the "mini" end in to the mating connector on TeleMetrum or TeleDongle. - + + + Take the 2 screws out of the TeleDongle case to get access to the circuit board. - + + + Plug the 8-pin end of the programming cable to the matching connector on the programmer, and the 4-pin end to the matching connector on the TeleDongle. Note that each MicroMaTch connector has an alignment pin that goes through a hole in the PC board when you have the cable oriented correctly. - + + + Attach a battery to the TeleMetrum board if you're using one. - + + + Plug both the programmer and the TeleDongle into your computer's USB ports, and power up the programmer. - + + + Run AltosUI, and select 'Flash Image' from the File menu. - + + + Pick the programmer device from the list, identifying it as the programming device. - + + + Select the image you want put on the TeleDongle, which should have a name in the form teledongle-v0.2-1.0.0.ihx. It should be visible in the default directory, if not you may have to poke around your system to find it. - + + + Make sure the configuration parameters are reasonable looking. If the serial number and/or RF configuration values aren't right, you'll need to change them. The TeleDongle serial number is on the "bottom" of the circuit board, and can usually be read through the translucent blue plastic case without needing to remove the board from the case. - + + + Hit the 'OK' button and the software should proceed to flash the TeleDongle with new firmware, showing a progress bar. - + + + Confirm that the TeleDongle board seems to have updated OK, which you can do by plugging in to it over USB and using a terminal program to connect to the board and issue the 'v' command to check the version, etc. Once you're happy, remove the programming cable and put the cover back on the TeleDongle. - + + + If something goes wrong, give it another try. - + + Be careful removing the programming cable from the locking 8-pin @@ -2936,21 +3045,80 @@ NAR #88757, TRA #12200
- + Release Notes - Version 1.3 - Version 1.2.1 - Version 1.2 - Version 1.1.1 - Version 1.1 - Version 1.0.1 - Version 0.9.2 - Version 0.9 - Version 0.8 - Version 0.7.1 + + Version 1.3 + + + + Version 1.2.1 + + + + Version 1.2 + + + + Version 1.1.1 + + + + Version 1.1 + + + + Version 1.0.1 + + + + Version 0.9.2 + + + + Version 0.9 + + + + Version 0.8 + + + + Version 0.7.1 + + - + \ No newline at end of file diff --git a/doc/release-notes-0.7.1.xsl b/doc/release-notes-0.7.1.xsl index 75158a02..1f2feeb0 100644 --- a/doc/release-notes-0.7.1.xsl +++ b/doc/release-notes-0.7.1.xsl @@ -8,42 +8,55 @@ Version 0.7.1 is the first release containing our new cross-platform Java-based + Receive and log telemetry from a connected TeleDongle device. All data received is saved to log files named with the current date and the connected rocket serial and flight numbers. There is no mode in which telemetry data will not be saved. - + + + Download logged data from TeleMetrum devices, either through a direct USB connection or over the air through a TeleDongle device. - + + + Configure a TeleMetrum device, setting the radio channel, callsign, apogee delay and main deploy height. This can be done through either a USB connection or over a radio link via a TeleDongle device. - + + + Replay a flight in real-time. This takes a saved telemetry log or eeprom download and replays it through the user interface so you can relive your favorite rocket flights. - + + + Reprogram Altus Metrum devices. Using an Altus Metrum device connected via USB, another Altus Metrum device can be reprogrammed using the supplied programming cable between the two devices. - + + + Export Flight data to a comma-separated-values file. This takes either telemetry or on-board flight data and generates data suitable for use in external applications. All data is exported using standard units so that no device-specific knowledge is needed to handle the data. - + + + Speak to you during the flight. Instead of spending the flight hunched over your laptop looking at the screen, enjoy the view while the computer tells you what’s going on up there. During @@ -52,6 +65,7 @@ Version 0.7.1 is the first release containing our new cross-platform Java-based range information to try and help you find your rocket in the air. Once on the ground, the direction and distance are reported. - + + diff --git a/doc/release-notes-0.8.xsl b/doc/release-notes-0.8.xsl index c54f97e9..df7ef32d 100644 --- a/doc/release-notes-0.8.xsl +++ b/doc/release-notes-0.8.xsl @@ -9,25 +9,32 @@ + Post-flight graphing tool. This lets you explore the behaviour of your rocket after flight with a scroll-able and zoom-able chart showing the altitude, speed and acceleration of the airframe along with events recorded by the flight computer. You can export graphs to PNG files, or print them directly. - + + + Real-time moving map which overlays the in-progress flight on satellite imagery fetched from Google Maps. This lets you see in pictures where your rocket has landed, allowing you to plan recovery activities more accurately. - + + + Wireless recovery system testing. Prep your rocket for flight and test fire the deployment charges to make sure things work as expected. All without threading wires through holes in your airframe. - + + + Optimized flight status displays. Each flight state now has it's own custom 'tab' in the flight monitoring window so you can focus on the most important details. Pre-flight, the system @@ -36,21 +43,28 @@ they're all green and your rocket is ready for flight. There are also tabs for ascent, descent and landing along with the original tabular view of the data. - + + + Monitor multiple flights simultaneously. If you have more than one TeleDongle, you can monitor a flight with each one on the same computer. - + + + Automatic flight monitoring at startup. Plug TeleDongle into the machine before starting AltosUI and it will automatically connect to it and prepare to monitor a flight. - + + + Exports Google Earth flight tracks. Using the Keyhole Markup Language (.kml) file format, this provides a 3D view of your rocket flight through the Google Earth program. - + + diff --git a/doc/release-notes-0.9.2.xsl b/doc/release-notes-0.9.2.xsl index e5f66c60..16ff989e 100644 --- a/doc/release-notes-0.9.2.xsl +++ b/doc/release-notes-0.9.2.xsl @@ -8,13 +8,19 @@ + Fix plotting problems due to missing file in the Mac OS install image. + + Always read whole eeprom blocks, mark empty records invalid, display parsing errors to user. + + Add software version to Configure AltosUI dialog + diff --git a/doc/release-notes-0.9.xsl b/doc/release-notes-0.9.xsl index 547f46b1..a5d6b3d7 100644 --- a/doc/release-notes-0.9.xsl +++ b/doc/release-notes-0.9.xsl @@ -9,23 +9,29 @@ + Support for TeleMetrum v1.1 hardware. Sources for the flash memory part used in v1.0 dried up, so v1.1 uses a different part which required a new driver and support for explicit flight log erasing. + + Multiple flight log support. This stores more than one flight log in the on-board flash memory. It also requires the user to explicitly erase flights so that you won't lose flight logs just because you fly the same board twice in one day. + + Telemetry support for devices with serial number >= 256. Previous versions used a telemetry packet format that provided only 8 bits for the device serial number. This change requires that both ends of the telemetry link be running the 0.9 firmware or they will not communicate. + diff --git a/doc/release-notes-1.0.1.xsl b/doc/release-notes-1.0.1.xsl index 1e9fcabc..8b66f7e0 100644 --- a/doc/release-notes-1.0.1.xsl +++ b/doc/release-notes-1.0.1.xsl @@ -11,28 +11,37 @@ AltOS Firmware Changes + Add TeleMini v1.0 support. Firmware images for TeleMini are included in AltOS releases. - + + + Change telemetry to be encoded in multiple 32-byte packets. This enables support for TeleMini and other devices without requiring further updates to the TeleDongle firmware. - + + + Support operation of TeleMetrum with the antenna pointing aft. Previous firmware versions required the antenna to be pointing upwards, now there is a configuration option allowing the antenna to point aft, to aid installation in some airframes. - + + + Ability to disable telemetry. For airframes where an antenna just isn't possible, or where radio transmissions might cause trouble with other electronics, there's a configuration option to disable all telemetry. Note that the board will still enable the radio link in idle mode. - + + + Arbitrary frequency selection. The radios in Altus Metrum devices can be programmed to a wide range of frequencies, so instead of limiting devices to 10 pre-selected 'channels', the @@ -40,8 +49,10 @@ 70cm band. Note that the RF matching circuit on the boards is tuned for around 435MHz, so frequencies far from that may reduce the available range. - + + + Kalman-filter based flight-tracking. The model based sensor fusion approach of a Kalman filter means that AltOS now computes apogee much more accurately than before, generally @@ -49,38 +60,48 @@ allows the baro-only TeleMini device to correctly identify Mach transitions, avoiding the error-prone selection of a Mach delay. - + + AltosUI Changes + Wait for altimeter when using packet mode. Instead of quicly timing out when trying to initialize a packet mode configuration connection, AltosUI now waits indefinitely for the remote device to appear, providing a cancel button should the user get bored. This is necessary as the TeleMini can only be placed in "Idle" mode if AltosUI is polling it. - + + + Add main/apogee voltage graphs to the data plot. This provides a visual indication if the igniters fail before being fired. - + + + Scan for altimeter devices by watching the defined telemetry frequencies. This avoids the problem of remembering what frequency a device was configured to use, which is especially important with TeleMini which does not include a USB connection. - + + + Monitor altimeter state in "Idle" mode. This provides much of the information presented in the "Pad" dialog from the Monitor Flight command, monitoring the igniters, battery and GPS status withing requiring the flight computer to be armed and ready for flight. - + + + Pre-load map images from home. For those launch sites which don't provide free Wi-Fi, this allows you to download the necessary satellite images given the location of the launch @@ -89,15 +110,18 @@ you've got a launch site not on that list, please send the name of it, latitude and longitude along with a link to the web site of the controlling club to the altusmetrum mailing list. - + + + Flight statistics are now displayed in the Graph data window. These include max height/speed/accel, average descent rates and a few other bits of information. The Graph Data window can now be reached from the 'Landed' tab in the Monitor Flight window so you can immediately see the results of a flight. - + + diff --git a/doc/release-notes-1.1.1.xsl b/doc/release-notes-1.1.1.xsl index 14984a2a..6f3a925d 100644 --- a/doc/release-notes-1.1.1.xsl +++ b/doc/release-notes-1.1.1.xsl @@ -14,6 +14,7 @@ AltOS Firmware Changes + TeleMetrum v1.0 boards use the AT45DB081D flash memory part to store flight data, which is different from later TeleMetrum boards. The AltOS v1.1 driver for this chip couldn't erase @@ -21,25 +22,31 @@ configuration values. This bug doesn't affect newer TeleMetrum boards, and it doesn't affect the safety of rockets flying version 1.1 firmware. - + + AltosUI Changes + Creating a Google Earth file (KML) from on-board flight data (EEPROM) would generate an empty file. The code responsible for reading the EEPROM file wasn't ever setting the GPS valid bits, and so the KML export code thought there was no GPS data in the file. - + + + The “Landed” tab was displaying all values in metric units, even when AltosUI was configured to display imperial units. Somehow I just missed this tab when doing the units stuff. - + + + The “Descent” tab displays the range to the rocket, which is a combination of the over-the-ground distance to the rockets current latitude/longitude and the height of the rocket. As @@ -48,14 +55,17 @@ eventually land. A new “Ground Distance” field has been added which displays the distance to a spot right underneath the rocket. - + + + Sensor data wasn't being displayed for TeleMini flight computers in Monitor Idle mode, including things like battery voltage. The code that picked which kinds of data to fetch from the flight computer was missing a check for TeleMini when deciding whether to fetch the analog sensor data. - + + diff --git a/doc/release-notes-1.1.xsl b/doc/release-notes-1.1.xsl index 519cd40c..0b2cce4e 100644 --- a/doc/release-notes-1.1.xsl +++ b/doc/release-notes-1.1.xsl @@ -11,89 +11,121 @@ AltOS Firmware Changes + Add apogee-lockout value. Overrides the apogee detection logic to prevent incorrect apogee charge firing. - + + + Fix a bug where the data reported in telemetry packets was from 320ms ago. - + + + Force the radio frequency to 434.550MHz when the debug clock pin is connected to ground at boot time. This provides a way to talk to a TeleMini which is configured to some unknown frequency. - + + + Provide RSSI values for Monitor Idle mode. This makes it easy to check radio range without needing to go to flight mode. - + + + Fix a bug which caused the old received telemetry packets to be retransmitted over the USB link when the radio was turned off and back on. - + + AltosUI Changes + Fix a bug that caused GPS ready to happen too quickly. The software was using every telemetry packet to signal new GPS data, which caused GPS ready to be signalled after 10 packets instead of 10 GPS updates. - + + + Fix Google Earth data export to work with recent versions. The google earth file loading code got a lot pickier, requiring some minor white space changes in the export code. - + + + Make the look-n-feel configurable, providing a choice from the available options. - + + + Add an 'Age' element to mark how long since a telemetry packet has been received. Useful to quickly gauge whether communications with the rocket are still active. - + + + Add 'Configure Ground Station' dialog to set the radio frequency used by a particular TeleDongle without having to go through the flight monitor UI. - + + + Add configuration for the new apogee-lockout value. A menu provides a list of reasonable values, or the value can be set by hand. - + + + Changed how flight data are downloaded. Now there's an initial dialog asking which flights to download, and after that finishes, a second dialog comes up asking which flights to delete. - + + + Re-compute time spent in each state for the flight graph; this figures out the actual boost and landing times instead of using the conservative values provide by the flight electronics. This improves the accuracy of the boost acceleration and main descent rate computations. - + + + Make AltosUI run on Mac OS Lion. The default Java heap space was dramatically reduced for this release causing much of the UI to fail randomly. This most often affected the satellite mapping download and displays. - + + + Change how data are displayed in the 'table' tab of the flight monitoring window. This eliminates entries duplicated from the header and adds both current altitude and pad altitude, which are useful in 'Monitor Idle' mode. - + + + Add Imperial units mode to present data in feet instead of meters. - + + diff --git a/doc/release-notes-1.2.1.xsl b/doc/release-notes-1.2.1.xsl index 5f9aef01..0f056954 100644 --- a/doc/release-notes-1.2.1.xsl +++ b/doc/release-notes-1.2.1.xsl @@ -12,72 +12,96 @@ AltOS Firmware Changes + Add support for TeleBT - + + + In TeleMini recovery mode (when booted with the outer two debug pins connected together), the radio parameters are also set back to defaults (434.550MHz, N0CALL, factory radio cal). - + + + Add support for reflashing the SkyTraq GPS chips. This requires special host-side code which currently only exists for Linux. - + + + Correct Kalman filter model error covariance matrix. The values used previously assumed continuous measurements instead of discrete measurements. - + + + Fix some bugs in the USB driver for TeleMetrum and TeleDongle that affected Windows users. - + + + Adjusted the automatic gain control parameters that affect receive performance for TeleDongle. Field tests indicate that this may improve receive performance somewhat. - + + AltosUI Changes + Handle missing GPS lock in 'Descent' tab. Previously, if the GPS position of the pad was unknown, an exception would be raised, breaking the Descent tab contents. - + + + Improve the graph, adding tool-tips to show values near the cursor and making the displayed set of values configurable, adding all of the flight data as options while leaving the default settings alone so that the graph starts by showing height, speed and acceleration. - + + + Make the initial position of the AltosUI top level window configurable. Along with this change, the other windows will pop up at 'sensible' places now, instead of on top of one another. - + + + Add callsign to Monitor idle window and connecting dialogs. This makes it clear which callsign is being used so that the operator will be aware that it must match the flight computer value or no communication will work. - + + + When downloading flight data, display the block number so that the user has some sense of progress. Unfortunately, we don't know how many blocks will need to be downloaded, but at least it isn't just sitting there doing nothing for a long time. - + + + Add GPS data and a map to the graph window. This lets you see a complete summary of the flight without needing to 'replay' the whole thing. - + + diff --git a/doc/release-notes-1.2.xsl b/doc/release-notes-1.2.xsl index 64ba46a9..f26480a1 100644 --- a/doc/release-notes-1.2.xsl +++ b/doc/release-notes-1.2.xsl @@ -11,33 +11,41 @@ AltOS Firmware Changes + Add MicroPeak support. This includes support for the ATtiny85 processor and adaptations to the core code to allow for devices too small to run the multi-tasking scheduler. - + + MicroPeak UI changes + Added this new application - + + Distribution Changes + Distribute Mac OS X packages in disk image ('.dmg') format to greatly simplify installation. - + + + Provide version numbers for the shared Java libraries to ensure that upgrades work properly, and to allow for multiple Altus Metrum software packages to be installed in the same directory at the same time. - + + diff --git a/doc/release-notes-1.3.xsl b/doc/release-notes-1.3.xsl index 149e024e..3bc4857f 100644 --- a/doc/release-notes-1.3.xsl +++ b/doc/release-notes-1.3.xsl @@ -11,29 +11,39 @@ AltOS Firmware Changes - Add STM32L processor support. This includes enhancements to - the scheduler to support products with many threads. + + Add STM32L processor support. This includes enhancements to + the scheduler to support products with many threads. + - Add NXP LPC11U14 processor support. + + Add NXP LPC11U14 processor support. + - Support additional pyro channels. These are configurable - through the UI to handle air starts, staging, additional - recovery events and external devices such as cameras. + + Support additional pyro channels. These are configurable + through the UI to handle air starts, staging, additional + recovery events and external devices such as cameras. + - Add 3-axis gyro support for orientation tracking. This - integrates the gyros to compute the angle from vertical during - flight, allowing the additional pyro events to be controlled - by this value. + + Add 3-axis gyro support for orientation tracking. This + integrates the gyros to compute the angle from vertical during + flight, allowing the additional pyro events to be controlled + by this value. + - Many more device drivers, including u-Blox Max 7Q GPS, - Freescale MMA6555 digital single-axis accelerometer, - Invensense MPU6000 3-axis accelerometer + 3 axis gyro, - Honeywell HMC5883 3-axis magnetic sensor and the TI CC1120 and - CC115L digital FM transceivers + + Many more device drivers, including u-Blox Max 7Q GPS, + Freescale MMA6555 digital single-axis accelerometer, + Invensense MPU6000 3-axis accelerometer + 3 axis gyro, + Honeywell HMC5883 3-axis magnetic sensor and the TI CC1120 and + CC115L digital FM transceivers + @@ -41,11 +51,15 @@ AltosUI changes - Support TeleMega, TeleMetrum v2.0, TeleMini v2.0 and EasyMini telemetry and log formats. + + Support TeleMega, TeleMetrum v2.0, TeleMini v2.0 and EasyMini telemetry and log formats. + - Use preferred units for main deployment height configuration, - instead of always doing configuration in meters. + + Use preferred units for main deployment height configuration, + instead of always doing configuration in meters. + @@ -53,10 +67,14 @@ MicroPeak UI changes - Add 'Download' button to menu bar. + + Add 'Download' button to menu bar. + - Save the last log directory and offer that as the default for new downloads + + Save the last log directory and offer that as the default for new downloads + -- 2.30.2