From e711c708b0d2c8d8c2d72e34a795ad8e9b5ab5de Mon Sep 17 00:00:00 2001 From: Keith Packard Date: Mon, 20 May 2013 21:37:20 -0700 Subject: Create release notes for 1.2.1 Move most of the 1.2 content to the 1.2.1 block Signed-off-by: Keith Packard --- doc/Makefile | 3 +- doc/altusmetrum.xsl | 15 ++++++-- doc/release-notes-1.2.1.xsl | 83 +++++++++++++++++++++++++++++++++++++++++++++ doc/release-notes-1.2.xsl | 59 +++----------------------------- 4 files changed, 101 insertions(+), 59 deletions(-) create mode 100644 doc/release-notes-1.2.1.xsl (limited to 'doc') diff --git a/doc/Makefile b/doc/Makefile index 7c4da29e..06346a2d 100644 --- a/doc/Makefile +++ b/doc/Makefile @@ -10,7 +10,8 @@ RELNOTES=\ release-notes-1.0.1.html \ release-notes-1.1.html \ release-notes-1.1.1.html \ - release-notes-1.2.html + release-notes-1.2.html \ + release-notes-1.2.1.html RELNOTES_XSL=$(RELNOTES:.html=.xsl) HTML=altusmetrum.html altos.html telemetry.html companion.html micropeak.html $(RELNOTES) diff --git a/doc/altusmetrum.xsl b/doc/altusmetrum.xsl index 294f30ac..558898cf 100644 --- a/doc/altusmetrum.xsl +++ b/doc/altusmetrum.xsl @@ -36,12 +36,20 @@ - 1.2 - 14 April 2013 + 1.2.1 + 21 May 2013 Updated for software version 1.2. Version 1.2 adds support for TeleBT and AltosDroid. It also adds a few minor features - and fixes a few minor bugs in AltosUI and the AltOS firmware. + and fixes bugs in AltosUI and the AltOS firmware. + + + + 1.2 + 18 April 2013 + + Updated for software version 1.2. Version 1.2 adds support + for MicroPeak and the MicroPeak USB interface. @@ -2851,6 +2859,7 @@ NAR #88757, TRA #12200 Release Notes + Version 1.21 Version 1.2 Version 1.1.1 Version 1.1 diff --git a/doc/release-notes-1.2.1.xsl b/doc/release-notes-1.2.1.xsl new file mode 100644 index 00000000..5f9aef01 --- /dev/null +++ b/doc/release-notes-1.2.1.xsl @@ -0,0 +1,83 @@ + + + +
+ + Version 1.2.1 is a minor release. It adds support for TeleBT and + the AltosDroid application, provides several new features in + AltosUI and fixes some bugs in the AltOS firmware. + + + AltOS 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 b254c7b5..64ba46a9 100644 --- a/doc/release-notes-1.2.xsl +++ b/doc/release-notes-1.2.xsl @@ -4,75 +4,24 @@
- Version 1.2 is a minor release. It provides a few new features in AltosUI - and the AltOS firmware and fixes bugs. + Version 1.2 is a major release. It adds support for MicroPeak and + the MicroPeak USB adapter. AltOS Firmware Changes - - 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. - 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. - - Correct Kalman filter model error covariance matrix. The - values used previously assumed continuous measurements instead - of discrete measurements. - - AltosUI Changes + MicroPeak UI 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. - - - Add preliminary TeleMega support, including configuration, - data download and analysis. - - - 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. + Added this new application -- cgit v1.2.3 From 013cba5ed1fde72240a68ec648bd14977f5e48a4 Mon Sep 17 00:00:00 2001 From: Keith Packard Date: Mon, 20 May 2013 21:41:01 -0700 Subject: doc: Update description of graph window to note new tabs (config and map) Signed-off-by: Keith Packard --- doc/altusmetrum.xsl | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) (limited to 'doc') diff --git a/doc/altusmetrum.xsl b/doc/altusmetrum.xsl index 558898cf..dfd72ab4 100644 --- a/doc/altusmetrum.xsl +++ b/doc/altusmetrum.xsl @@ -1113,14 +1113,15 @@ NAR #88757, TRA #12200 flash memory. - Once a flight record is selected, a window with two tabs is + Once a flight record is selected, a window with four tabs is opened. The first tab contains a graph with acceleration (blue), velocity (green) and altitude (red) of the flight, - measured in metric units. The - apogee(yellow) and main(magenta) igniter voltages are also - displayed; high voltages indicate continuity, low voltages - indicate open circuits. The second tab contains some basic - flight statistics. + measured in metric units. The apogee(yellow) and main(magenta) + igniter voltages are also displayed; high voltages indicate + continuity, low voltages indicate open circuits. The second + tab lets you configure which data to show in the graph. The + third contains some basic flight statistics while the fourth + has a map with the ground track of the flight displayed. The graph can be zoomed into a particular area by clicking and -- cgit v1.2.3 From e2ebe60adf061479a1259a5c68b9cd5f5bacf644 Mon Sep 17 00:00:00 2001 From: Bdale Garbee Date: Tue, 30 Jul 2013 00:14:41 -0600 Subject: add a note about callsign matching and case sensitivity to the manual --- doc/altusmetrum.xsl | 7 +++++++ 1 file changed, 7 insertions(+) (limited to 'doc') diff --git a/doc/altusmetrum.xsl b/doc/altusmetrum.xsl index dfd72ab4..98a98c19 100644 --- a/doc/altusmetrum.xsl +++ b/doc/altusmetrum.xsl @@ -1397,6 +1397,13 @@ NAR #88757, TRA #12200 with the AltosUI operators call sign as needed to comply with your local radio regulations. + + Note that to successfully command a flight computer over the radio + (to configure the altimeter, monitor idle, or fire pyro charges), + the callsign configured here must exactly match the callsign + configured in the flight computer. This matching is case + sensitive. +
Imperial Units -- cgit v1.2.3 From 18cb5f0b8f0917cbd4ff80f0920e8e5b35c822a1 Mon Sep 17 00:00:00 2001 From: Keith Packard Date: Wed, 9 Oct 2013 10:14:16 -0700 Subject: doc: Add EasyMini outline drawing Signed-off-by: Keith Packard --- doc/easymini-outline.pdf | Bin 0 -> 4240 bytes doc/easymini-outline.svg | 219 +++++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 219 insertions(+) create mode 100644 doc/easymini-outline.pdf create mode 100644 doc/easymini-outline.svg (limited to 'doc') diff --git a/doc/easymini-outline.pdf b/doc/easymini-outline.pdf new file mode 100644 index 00000000..a1a0b19d Binary files /dev/null and b/doc/easymini-outline.pdf differ diff --git a/doc/easymini-outline.svg b/doc/easymini-outline.svg new file mode 100644 index 00000000..40faddb3 --- /dev/null +++ b/doc/easymini-outline.svg @@ -0,0 +1,219 @@ + + + + + + + + + + + + + + + + + image/svg+xml + + + + + + + + + + + + + + + + + + + + + + + + + + + + + UP + + -- cgit v1.2.3 From 152d978dc4be49b6b764e5e1966bd860c46054ea Mon Sep 17 00:00:00 2001 From: Keith Packard Date: Mon, 18 Nov 2013 12:05:10 -0800 Subject: doc: Start work on 1.3 doc updates Add 1.3 release notes. Signed-off-by: Keith Packard --- doc/altusmetrum.xsl | 235 ++++++++++++++++++++++++++++++---------------- doc/release-notes-1.3.xsl | 63 +++++++++++++ 2 files changed, 217 insertions(+), 81 deletions(-) create mode 100644 doc/release-notes-1.3.xsl (limited to 'doc') diff --git a/doc/altusmetrum.xsl b/doc/altusmetrum.xsl index 98a98c19..1df270bc 100644 --- a/doc/altusmetrum.xsl +++ b/doc/altusmetrum.xsl @@ -35,6 +35,15 @@ + + 1.3 + 12 November 2013 + + Updated for software version 1.3. Version 1.3 adds support + for TeleMega, TeleMetrum v2.0, TeleMini v2.0 and EasyMini + and fixes bugs in AltosUI and the AltOS firmware. + + 1.2.1 21 May 2013 @@ -136,13 +145,27 @@ NAR #88757, TRA #12200 The first device created for our community was TeleMetrum, a dual deploy altimeter with fully integrated GPS and radio telemetry as standard features, and a "companion interface" that will - support optional capabilities in the future. + support optional capabilities in the future. The latest version + of TeleMetrum, v2.0, has all of the same features but with + improved sensors and radio to offer increased performance. Our second device was TeleMini, a dual deploy altimeter with - radio telemetry and radio direction finding. This device is only - 13mm by 38mm (½ inch by 1½ inches) and can fit easily in an 18mm - air-frame. + radio telemetry and radio direction finding. The first version + of this device was only 13mm by 38mm (½ inch by 1½ inches) and + could fit easily in an 18mm air-frame. The latest version, v2.0, + includes a beeper, USB data download and extended on-board + flight logging, along with an improved barometric sensor. + + + TeleMega is our most sophisticated device, including six pyro + channels (four of which are fully programmable), integrated GPS, + integrated gyroscopes for staging/air-start inhibit and high + performance telemetry. + + + EasyMini is a dual-deploy altimeter with logging and built-in + USB data download. TeleDongle was our first ground station, providing a USB to RF @@ -173,32 +196,48 @@ NAR #88757, TRA #12200 "starter kit" is to charge the battery. - The TeleMetrum battery can be charged by plugging it into the - corresponding socket of the TeleMetrum and then using the USB A to - mini B - cable to plug the TeleMetrum into your computer's USB socket. The - TeleMetrum circuitry will charge the battery whenever it is plugged - in, because the TeleMetrum's on-off switch does NOT control the + For TeleMetrum and TeleMega, the battery can be charged by plugging it into the + corresponding socket of the device and then using the USB + cable to plug the flight computer into your computer's USB socket. The + on-board circuitry will charge the battery whenever it is plugged + in, because the on-off switch does NOT control the charging circuitry. - When the GPS chip is initially searching for - satellites, TeleMetrum will consume more current than it can pull - from the USB port, so the battery must be attached in order to get - satellite lock. Once GPS is locked, the current consumption goes back - down enough to enable charging while - running. So it's a good idea to fully charge the battery as your - first item of business so there is no issue getting and maintaining - satellite lock. The yellow charge indicator led will go out when the - battery is nearly full and the charger goes to trickle charge. It - can take several hours to fully recharge a deeply discharged battery. + On TeleMetrum v1 boards, when the GPS chip is initially + searching for satellites, TeleMetrum will consume more current + than it can pull from the USB port, so the battery must be + attached in order to get satellite lock. Once GPS is locked, + the current consumption goes back down enough to enable charging + while running. So it's a good idea to fully charge the battery + as your first item of business so there is no issue getting and + maintaining satellite lock. The yellow charge indicator led + will go out when the battery is nearly full and the charger goes + to trickle charge. It can take several hours to fully recharge a + deeply discharged battery. + + + TeleMetrum v2.0 and TeleMega use a higher power battery charger, + allowing them to charge the battery while running the board at + maximum power. When the battery is charging, or when the board + is consuming a lot of power, the red LED will be lit. When the + battery is fully charged, the green LED will be lit. When the + battery is damaged or missing, both LEDs will be lit, which + appears yellow. - The TeleMini battery can be charged by disconnecting it from the - TeleMini board and plugging it into a standalone battery charger - such as the LipoCharger product included in TeleMini Starter Kits, - and connecting that via a USB cable to a laptop or other USB - power source. + The Lithium Polymer TeleMini and EasyMini battery can be charged by + disconnecting it from the board and plugging it into a + standalone battery charger such as the LipoCharger product + included in TeleMini Starter Kits, and connecting that via a USB + cable to a laptop or other USB power source. + + + You can also choose to use another battery with TeleMini v2.0 + and EasyMini, anything supplying between 4 and 12 volts should + work fine (like a standard 9V battery), but if you are planning + to fire pyro charges, ground testing is required to verify that + the battery supplies enough current. The other active device in the starter kit is the TeleDongle USB to @@ -212,13 +251,13 @@ NAR #88757, TRA #12200 ugly bugs in some earlier versions. - Next you should obtain and install the AltOS software. These include - the AltosUI ground station program, current firmware images for - TeleMetrum, TeleMini and TeleDongle, and a number of standalone - utilities that are rarely needed. Pre-built binary packages are - available for Linux, Microsoft Windows, and recent MacOSX versions. - Full source code and build instructions are also available. - The latest version may always be downloaded from + Next you should obtain and install the AltOS software. These + include the AltosUI ground station program, current firmware + images for all of the hardware, and a number of standalone + utilities that are rarely needed. Pre-built binary packages are + available for Linux, Microsoft Windows, and recent MacOSX + versions. Full source code and build instructions are also + available. The latest version may always be downloaded from . @@ -253,14 +292,14 @@ NAR #88757, TRA #12200 strapping them down, for example. - The barometric sensors used on both TeleMetrum and TeleMini are - sensitive to sunlight. In normal TeleMetrum mounting situations, it + The barometric sensors used on all of our flight computers are + sensitive to sunlight. In normal mounting situations, the baro sensor and all of the other surface mount components are "down" towards whatever the underlying mounting surface is, so this is not normally a problem. Please consider this, though, when designing an installation, for example, in an air-frame with a see-through plastic payload bay. It is particularly important to - consider this with TeleMini, both because the baro sensor is on the + consider this with TeleMini v1.0, both because the baro sensor is on the "top" of the board, and because many model rockets with payload bays use clear plastic for the payload bay! Replacing these with an opaque cardboard tube, painting them, or wrapping them with a layer of masking @@ -282,7 +321,7 @@ NAR #88757, TRA #12200 Hardware Overview - TeleMetrum is a 1 inch by 2.75 inch circuit board. It was designed to + TeleMetrum is a 1 inch by 2¾ inch circuit board. It was designed to fit inside coupler for 29mm air-frame tubing, but using it in a tube that small in diameter may require some creativity in mounting and wiring to succeed! The presence of an accelerometer means TeleMetrum should @@ -294,11 +333,11 @@ NAR #88757, TRA #12200 bay for TeleMetrum should have at least 10 inches of interior length. - TeleMini is a 0.5 inch by 1.5 inch circuit board. It was designed to + TeleMini v1.0 is a ½ inch by 1½ inch circuit board. It was designed to fit inside an 18mm air-frame tube, but using it in a tube that small in diameter may require some creativity in mounting and wiring to succeed! Since there is no accelerometer, TeleMini can be mounted - in any convenient orientation. The default 1/4 + in any convenient orientation. The default ¼ wave UHF wire antenna attached to the center of one end of the board is about 7 inches long, and wiring for a power switch and the e-matches for apogee and main ejection charges depart from the @@ -306,11 +345,31 @@ NAR #88757, TRA #12200 bay for TeleMini should have at least 9 inches of interior length. - A typical TeleMetrum or TeleMini installation involves attaching - only a suitable Lithium Polymer battery, a single pole switch for + TeleMini v2.0 and EasyMini are both built on a 0.8 inch by 1½ + inch circuit board. They're designed to fit in a 24mm coupler + tube. TeleMini has an antenna, which must be run straight out + fro the board. Bending or folding it will dramatically reduce RF + performance. For smaller rockets, it's often best to drill a + hole in the bulkhead forward of TeleMini and run the antenna + wire through that and alongside any recovery components + there. Be careful to seal the hole to prevent ejection gasses + from passing through the hole and damaging the electronics. + + + TeleMega is a 1¼ inch by 3¼ inch circuit board. It was + designed to easily fit in a 38mm coupler. Like TeleMetrum, + TeleMega has an accelerometer and so it must be mounted so that + the board is aligned with the flight axis. It can be mounted + either antenna up or down. + + + A typical installation involves attaching + only a suitable battery, a single pole switch for power on/off, and two pairs of wires connecting e-matches for the apogee and main ejection charges. All Altus Metrum products are - designed for use with single-cell batteries with 3.7 volts nominal. + designed for use with single-cell batteries with 3.7 volts + nominal. TeleMini v2.0 and EasyMini may also be used with other + batteries as long as they supply between 4 and 12 volts. The battery connectors are a standard 2-pin JST connector and @@ -326,7 +385,7 @@ NAR #88757, TRA #12200 from Altus Metrum or Spark Fun. - By default, we use the unregulated output of the Li-Po battery directly + By default, we use the unregulated output of the battery directly to fire ejection charges. This works marvelously with standard low-current e-matches like the J-Tek from MJG Technologies, and with Quest Q2G2 igniters. However, if you want or need to use a separate @@ -341,9 +400,10 @@ NAR #88757, TRA #12200 jeweler's screwdriver set. - TeleMetrum also uses the screw terminal block for the power - switch leads. On TeleMini, the power switch leads are soldered - directly to the board and can be connected directly to a switch. + Except for TeleMini v1.0, the flight computers also use the + screw terminal block for the power switch leads. On TeleMini v1.0, + the power switch leads are soldered directly to the board and + can be connected directly to a switch. For most air-frames, the integrated antennas are more than @@ -351,7 +411,7 @@ NAR #88757, TRA #12200 metal electronics bay which is opaque to RF signals, you may need to use off-board external antennas instead. In this case, you can order an altimeter with an SMA connector for the UHF antenna - connection, and, on TeleMetrum, you can unplug the integrated GPS + connection, and, on TeleMetrum v1, you can unplug the integrated GPS antenna and select an appropriate off-board GPS antenna with cable terminating in a U.FL connector. @@ -370,11 +430,12 @@ NAR #88757, TRA #12200 TeleMetrum assumes it's on a rail or rod being prepared for launch, so the firmware chooses flight mode. However, if the rocket is more or less horizontal, the firmware instead enters - idle mode. Since TeleMini doesn't have an accelerometer we can - use to determine orientation, "idle" mode is selected when the - board receives a command packet within the first five seconds - of operation; if no packet is received, the board enters - "flight" mode. + idle mode. Since TeleMini v2.0 and EasyMini don't have an + accelerometer we can use to determine orientation, "idle" mode + is selected if the board is connected via USB to a computer, + otherwise the board enters "flight" mode. TeleMini v1.0 + selects "idle" mode if it receives a command packet within the + first five seconds of operation. At power on, you will hear three beeps or see three flashes @@ -403,14 +464,14 @@ NAR #88757, TRA #12200 machine is disengaged, thus no ejection charges will fire. The altimeters also listen for the radio link when in idle mode for requests sent via TeleDongle. Commands can be issued - to a TeleMetrum in idle mode over either USB or the radio link - equivalently. TeleMini only has the radio link. Idle mode is - useful for configuring the altimeter, for extracting data from - the on-board storage chip after flight, and for ground testing - pyro charges. + in idle mode over either USB or the radio link + equivalently. TeleMini v1.0 only has the radio link. Idle + mode is useful for configuring the altimeter, for extracting + data from the on-board storage chip after flight, and for + ground testing pyro charges. - One "neat trick" of particular value when TeleMetrum is used with + One "neat trick" of particular value when TeleMetrum or TeleMega are used with very large air-frames, is that you can power the board up while the rocket is horizontal, such that it comes up in idle mode. Then you can raise the air-frame to launch position, and issue a 'reset' command @@ -421,10 +482,10 @@ NAR #88757, TRA #12200 installing igniters! - TeleMini is configured via the radio link. Of course, that + TeleMini v1.0 is configured solely via the radio link. Of course, that means you need to know the TeleMini radio configuration values or you won't be able to communicate with it. For situations - when you don't have the radio configuration values, TeleMini + when you don't have the radio configuration values, TeleMini v1.0 offers an 'emergency recovery' mode. In this mode, TeleMini is configured as follows: @@ -454,17 +515,17 @@ NAR #88757, TRA #12200
GPS - TeleMetrum includes a complete GPS receiver. A complete explanation - of how GPS works is beyond the scope of this manual, but the bottom - line is that the TeleMetrum GPS receiver needs to lock onto at least - four satellites to obtain a solid 3 dimensional position fix and know - what time it is. + TeleMetrum and TeleMega include a complete GPS receiver. A + complete explanation of how GPS works is beyond the scope of + this manual, but the bottom line is that the GPS receiver + needs to lock onto at least four satellites to obtain a solid + 3 dimensional position fix and know what time it is. - TeleMetrum provides backup power to the GPS chip any time a + The flight computers provide backup power to the GPS chip any time a battery is connected. This allows the receiver to "warm start" on the launch rail much faster than if every power-on were a GPS - "cold start". In typical operations, powering up TeleMetrum + "cold start". In typical operations, powering up on the flight line in idle mode while performing final air-frame preparation will be sufficient to allow the GPS receiver to cold start and acquire lock. Then the board can be powered down during @@ -485,10 +546,10 @@ NAR #88757, TRA #12200 computer. - Any operation which can be performed with TeleMetrum can - either be done with TeleMetrum directly connected to the + Any operation which can be performed with a flight computer can + either be done with the device directly connected to the computer via the USB cable, or through the radio - link. TeleMini doesn't provide a USB connector and so it is + link. TeleMini v1.0 doesn't provide a USB connector and so it is always communicated with over radio. Select the appropriate TeleDongle device when the list of devices is presented and AltosUI will interact with an altimeter over the radio link. @@ -514,10 +575,11 @@ NAR #88757, TRA #12200 - Configure altimeter apogee delays or main deploy heights + Configure altimeter apogee delays, main deploy heights + and additional pyro event conditions to respond to changing launch conditions. You can also 'reboot' the altimeter. Use this to remotely enable the - flight computer by turning TeleMetrum on in "idle" mode, + flight computer by turning TeleMetrum or TeleMega on in "idle" mode, then once the air-frame is oriented for launch, you can reboot the altimeter and have it restart in pad mode without having to climb the scary ladder. @@ -526,7 +588,7 @@ NAR #88757, TRA #12200 Fire Igniters—Test your deployment charges without snaking - wires out through holes in the air-frame. Simply assembly the + wires out through holes in the air-frame. Simply assemble the rocket as if for flight with the apogee and main charges loaded, then remotely command the altimeter to fire the igniters. @@ -541,9 +603,10 @@ NAR #88757, TRA #12200 close the window before performing other desired radio operations. - TeleMetrum only enables radio commanding in 'idle' mode, so - make sure you have TeleMetrum lying horizontally when you turn - it on. Otherwise, TeleMetrum will start in 'pad' mode ready for + The flight computers only enable radio commanding in 'idle' mode. + TeleMetrum and TeleMega use the accelerometer to detect which orientation they + start up in, so make sure you have the flight computer lying horizontally when you turn + it on. Otherwise, it will start in 'pad' mode ready for flight, and will not be listening for command packets from TeleDongle. @@ -570,14 +633,14 @@ NAR #88757, TRA #12200 An important aspect of preparing a rocket using electronic deployment for flight is ground testing the recovery system. Thanks to the bi-directional radio link central to the Altus Metrum system, - this can be accomplished in a TeleMetrum or TeleMini equipped rocket + this can be accomplished in a TeleMega, TeleMetrum or TeleMini equipped rocket with less work than you may be accustomed to with other systems. It can even be fun! Just prep the rocket for flight, then power up the altimeter - in "idle" mode (placing air-frame horizontal for TeleMetrum or - selected the Configure Altimeter tab for TeleMini). This will cause + in "idle" mode (placing air-frame horizontal for TeleMetrum or TeleMega, or + selecting the Configure Altimeter tab for TeleMini). This will cause the firmware to go into "idle" mode, in which the normal flight state machine is disabled and charges will not fire without manual command. You can now command the altimeter to fire the apogee @@ -607,7 +670,7 @@ NAR #88757, TRA #12200 data later... - We don't use a 'normal packet radio' mode like APRS because they're + We don't generally use a 'normal packet radio' mode like APRS because they're just too inefficient. The GFSK modulation we use is FSK with the base-band pulses passed through a Gaussian filter before they go into the modulator to limit the @@ -621,12 +684,18 @@ NAR #88757, TRA #12200 altitudes over time, and would of course appreciate customer feedback on performance in higher altitude flights! + + However, TeleMetrum v2.0 and TeleMega can send APRS if + desired, 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. +
Configurable Parameters Configuring an Altus Metrum altimeter for flight is very - simple. Even on our baro-only TeleMini board, the use of a Kalman + simple. Even on our baro-only TeleMini and EasyMini boards, the use of a Kalman filter means there is no need to set a "mach delay". The few configurable parameters can all be set using AltosUI over USB or or radio link via TeleDongle. @@ -689,6 +758,9 @@ NAR #88757, TRA #12200 (10 samples/second), there's plenty of space to store many flights worth of data. + + TeleMetrum v2.0 and TeleMega have 8MB of on-board flash stroage, enough to hold + The on-board flash is partitioned into separate flight logs, each of a fixed maximum size. Increase the maximum size of @@ -2867,7 +2939,8 @@ NAR #88757, TRA #12200 Release Notes - Version 1.21 + Version 1.3 + Version 1.2.1 Version 1.2 Version 1.1.1 Version 1.1 diff --git a/doc/release-notes-1.3.xsl b/doc/release-notes-1.3.xsl new file mode 100644 index 00000000..149e024e --- /dev/null +++ b/doc/release-notes-1.3.xsl @@ -0,0 +1,63 @@ + + + +
+ + Version 1.3 is a major release. It adds support for TeleMega, + TeleMetrum v2.0, TeleMini v2.0 and EasyMini. + + + AltOS Firmware Changes + + + Add STM32L processor support. This includes enhancements to + the scheduler to support products with many threads. + + + 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. + + + 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 + + + + + AltosUI changes + + + 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. + + + + + MicroPeak UI changes + + + Add 'Download' button to menu bar. + + + Save the last log directory and offer that as the default for new downloads + + + +
-- cgit v1.2.3 From 9953a5f0440b269dac5c675f120e6a31dde8ec69 Mon Sep 17 00:00:00 2001 From: Keith Packard Date: Mon, 18 Nov 2013 12:06:31 -0800 Subject: 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(-) (limited to 'doc') 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 + -- cgit v1.2.3 From 963a61986ea4b48fdca0989479e9c50acb0f1a9d Mon Sep 17 00:00:00 2001 From: Keith Packard Date: Mon, 18 Nov 2013 12:12:54 -0800 Subject: doc: Switch to xorg style to generate index This style sheet generates a nice PDF index Signed-off-by: Keith Packard --- doc/Makefile | 18 +++++------ doc/xorg-fo.xsl | 97 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 105 insertions(+), 10 deletions(-) create mode 100644 doc/xorg-fo.xsl (limited to 'doc') diff --git a/doc/Makefile b/doc/Makefile index 06346a2d..6e326ba5 100644 --- a/doc/Makefile +++ b/doc/Makefile @@ -11,29 +11,27 @@ RELNOTES=\ release-notes-1.1.html \ release-notes-1.1.1.html \ release-notes-1.2.html \ - release-notes-1.2.1.html + release-notes-1.2.1.html \ + release-notes-1.3.html RELNOTES_XSL=$(RELNOTES:.html=.xsl) HTML=altusmetrum.html altos.html telemetry.html companion.html micropeak.html $(RELNOTES) PDF=altusmetrum.pdf altos.pdf telemetry.pdf companion.pdf micropeak.pdf DOC=$(HTML) $(PDF) HTMLSTYLE=/usr/share/xml/docbook/stylesheet/docbook-xsl/html/docbook.xsl -FOSTYLE=/usr/share/xml/docbook/stylesheet/docbook-xsl/fo/docbook.xsl +FOSTYLE=./xorg-fo.xsl PDFSTYLE= IMAGES=telemetrum.svg telemini.svg -.SUFFIXES: .xsl .html .fo .pdf +.SUFFIXES: .xsl .html .pdf XSLTFLAGS=--stringparam section.autolabel 1 --xinclude .xsl.html: xsltproc $(XSLTFLAGS) -o $@ $(HTMLSTYLE) $*.xsl -.xsl.fo: - xsltproc $(XSLTFLAGS) -o $@ $(FOSTYLE) $*.xsl - -.fo.pdf: - fop -fo $*.fo -pdf $@ +.xsl.pdf: + xmlto -x $(FOSTYLE) --with-fop pdf $*.xsl all: $(HTML) $(PDF) @@ -48,10 +46,10 @@ publish: $(DOC) git push) clean: - rm -f $(HTML) $(PDF) *.fo + rm -f $(HTML) $(PDF) distclean: - rm -f $(HTML) $(PDF) *.fo + rm -f $(HTML) $(PDF) altusmetrum.html: $(RELNOTES_XSL) $(IMAGES) altusmetrum.fo: $(RELNOTES_XSL) $(IMAGES) diff --git a/doc/xorg-fo.xsl b/doc/xorg-fo.xsl new file mode 100644 index 00000000..896fcb6c --- /dev/null +++ b/doc/xorg-fo.xsl @@ -0,0 +1,97 @@ + + + + + + + + + + + + + + + + + + + + + new + + + + + + + + + + + page + page + + + + + + + + + + + + + + + + + blue + + + + + green + + + + + + + + + + DejaVu Serif + serif,Symbol,AR PL UMing CN,AR PL ShanHeiSun Uni,GNU Unifont + + -- cgit v1.2.3 From 87fbe12bdaf10c9ba7ba43608b1e980cdc09d496 Mon Sep 17 00:00:00 2001 From: Keith Packard Date: Mon, 18 Nov 2013 12:29:42 -0800 Subject: doc: Make altos.xsl validate Signed-off-by: Keith Packard --- doc/altos.xsl | 200 ++++++++++++++++++++++++++++++++-------------------------- 1 file changed, 109 insertions(+), 91 deletions(-) (limited to 'doc') diff --git a/doc/altos.xsl b/doc/altos.xsl index 5af94725..5b9e12e8 100644 --- a/doc/altos.xsl +++ b/doc/altos.xsl @@ -265,16 +265,22 @@ will fail to compile. + AO_EXTI_MODE_PULL_UP. Apply a pull-up to the pin; a disconnected pin will read as 1. + + AO_EXTI_MODE_PULL_DOWN. Apply a pull-down to the pin; a disconnected pin will read as 0. + + 0. Don't apply either a pull-up or pull-down. A disconnected pin will read an undetermined value. + @@ -1005,7 +1011,7 @@ variable with one of the following values: - ao_cmd_success + ao_cmd_success The command was parsed successfully. There is no @@ -1014,7 +1020,7 @@ - ao_cmd_lex_error + ao_cmd_lex_error A token in the line was invalid, such as a number @@ -1024,7 +1030,7 @@ - ao_syntax_error + ao_syntax_error The command line is invalid for some reason other @@ -1323,57 +1329,60 @@ CC1111 Radio peripheral - - The CC1111 radio transceiver sends and receives digital packets - with forward error correction and detection. The AltOS driver is - fairly specific to the needs of the TeleMetrum and TeleDongle - devices, using it for other tasks may require customization of - the driver itself. There are three basic modes of operation: - - - - Telemetry mode. In this mode, TeleMetrum transmits telemetry - frames at a fixed rate. The frames are of fixed size. This - is strictly a one-way communication from TeleMetrum to - TeleDongle. - - - - - Packet mode. In this mode, the radio is used to create a - reliable duplex byte stream between TeleDongle and - TeleMetrum. This is an asymmetrical protocol with - TeleMetrum only transmitting in response to a packet sent - from TeleDongle. Thus getting data from TeleMetrum to - TeleDongle requires polling. The polling rate is adaptive, - when no data has been received for a while, the rate slows - down. The packets are checked at both ends and invalid - data are ignored. - - - On the TeleMetrum side, the packet link is hooked into the - stdio mechanism, providing an alternate data path for the - command processor. It is enabled when the unit boots up in - 'idle' mode. - - - On the TeleDongle side, the packet link is enabled with a - command; data from the stdio package is forwarded over the - packet link providing a connection from the USB command - stream to the remote TeleMetrum device. - - - - - Radio Direction Finding mode. In this mode, TeleMetrum - constructs a special packet that sounds like an audio tone - when received by a conventional narrow-band FM - receiver. This is designed to provide a beacon to track - the device when other location mechanisms fail. - - - - +
+ Radio Introduction + + The CC1111 radio transceiver sends and receives digital packets + with forward error correction and detection. The AltOS driver is + fairly specific to the needs of the TeleMetrum and TeleDongle + devices, using it for other tasks may require customization of + the driver itself. There are three basic modes of operation: + + + + Telemetry mode. In this mode, TeleMetrum transmits telemetry + frames at a fixed rate. The frames are of fixed size. This + is strictly a one-way communication from TeleMetrum to + TeleDongle. + + + + + Packet mode. In this mode, the radio is used to create a + reliable duplex byte stream between TeleDongle and + TeleMetrum. This is an asymmetrical protocol with + TeleMetrum only transmitting in response to a packet sent + from TeleDongle. Thus getting data from TeleMetrum to + TeleDongle requires polling. The polling rate is adaptive, + when no data has been received for a while, the rate slows + down. The packets are checked at both ends and invalid + data are ignored. + + + On the TeleMetrum side, the packet link is hooked into the + stdio mechanism, providing an alternate data path for the + command processor. It is enabled when the unit boots up in + 'idle' mode. + + + On the TeleDongle side, the packet link is enabled with a + command; data from the stdio package is forwarded over the + packet link providing a connection from the USB command + stream to the remote TeleMetrum device. + + + + + Radio Direction Finding mode. In this mode, TeleMetrum + constructs a special packet that sounds like an audio tone + when received by a conventional narrow-band FM + receiver. This is designed to provide a beacon to track + the device when other location mechanisms fail. + + + + +
ao_radio_set_telemetry @@ -1463,14 +1472,16 @@ the radio operation.
- - In telemetry mode, you can send or receive a telemetry - packet. The data from receiving a packet also includes the RSSI - and status values supplied by the receiver. These are added - after the telemetry data. -
- ao_radio_send + Radio Telemetry + + In telemetry mode, you can send or receive a telemetry + packet. The data from receiving a packet also includes the RSSI + and status values supplied by the receiver. These are added + after the telemetry data. + +
+ ao_radio_send void ao_radio_send(__xdata struct ao_telemetry *telemetry); @@ -1482,9 +1493,9 @@ sending, and ao_radio_put() afterwards, to correctly serialize access to the radio device. -
-
- ao_radio_recv +
+
+ ao_radio_recv void ao_radio_recv(__xdata struct ao_radio_recv *radio); @@ -1498,13 +1509,16 @@ received, or zero if the operation was aborted (from some other task calling ao_radio_abort()). +
- - In radio direction finding mode, there's just one function to - use -
- ao_radio_rdf + Radio Direction Finding + + In radio direction finding mode, there's just one function to + use + +
+ ao_radio_rdf void ao_radio_rdf(int ms); @@ -1513,15 +1527,18 @@ This sends an RDF packet lasting for the specified amount of time. The maximum length is 1020 ms. +
- - Packet mode is asymmetrical and is configured at compile time - for either master or slave mode (but not both). The basic I/O - functions look the same at both ends, but the internals are - different, along with the initialization steps. -
- ao_packet_putchar + Radio Packet Mode + + Packet mode is asymmetrical and is configured at compile time + for either master or slave mode (but not both). The basic I/O + functions look the same at both ends, but the internals are + different, along with the initialization steps. + +
+ ao_packet_putchar void ao_packet_putchar(char c); @@ -1534,9 +1551,9 @@ slave side, any pending data will be sent the next time the master polls for data. -
-
- ao_packet_pollchar +
+
+ ao_packet_pollchar char ao_packet_pollchar(void); @@ -1546,9 +1563,9 @@ otherwise returns AO_READ_AGAIN. On the master side, if this empties the buffer, it triggers a poll for more data. -
-
- ao_packet_slave_start +
+
+ ao_packet_slave_start void ao_packet_slave_start(void); @@ -1557,9 +1574,9 @@ This is available only on the slave side and starts a task to listen for packet data. -
-
- ao_packet_slave_stop +
+
+ ao_packet_slave_stop void ao_packet_slave_stop(void); @@ -1567,9 +1584,9 @@ Disables the packet slave task, stopping the radio receiver. -
-
- ao_packet_slave_init +
+
+ ao_packet_slave_init void ao_packet_slave_init(void); @@ -1579,9 +1596,9 @@ that when packet slave mode is enabled, characters will get send and received through the stdio functions. -
-
- ao_packet_master_init +
+
+ ao_packet_master_init void ao_packet_master_init(void); @@ -1589,6 +1606,7 @@ Adds the 'p' packet forward command to start packet mode. +
-- cgit v1.2.3 From d212d782bff977d609a9da1b805de4a2615fb474 Mon Sep 17 00:00:00 2001 From: Keith Packard Date: Mon, 18 Nov 2013 12:37:23 -0800 Subject: doc: Make telemetry.xsl validate Signed-off-by: Keith Packard --- doc/telemetry.xsl | 19 ++++++++++++------- 1 file changed, 12 insertions(+), 7 deletions(-) (limited to 'doc') diff --git a/doc/telemetry.xsl b/doc/telemetry.xsl index fa66bff9..e4101507 100644 --- a/doc/telemetry.xsl +++ b/doc/telemetry.xsl @@ -1,5 +1,5 @@ -
@@ -57,8 +57,10 @@
Packet Formats - This section first defines the packet header common to all packets - and then the per-packet data layout. + + This section first defines the packet header common to all packets + and then the per-packet data layout. +
Packet Header @@ -621,9 +623,10 @@ resulting in the following signal parmeters:
+ Modulation Scheme - + @@ -663,14 +666,15 @@
+ 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. - Error Correction + Error Correction @@ -685,8 +689,8 @@ Error Correction - Convolutional coding FEC - 1/2 code, constraint length m=4 + Convolutional coding + 1/2 rate, constraint length m=4 Interleaving @@ -722,6 +726,7 @@ validate that the line was transmitted without any errors.
+ Packet Format -- cgit v1.2.3 From 0a3e27e3a392be4cfe03d200068a7e69bb2f3fdb Mon Sep 17 00:00:00 2001 From: Keith Packard Date: Mon, 18 Nov 2013 12:38:52 -0800 Subject: Make companion.xsl validate Signed-off-by: Keith Packard --- doc/companion.xsl | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) (limited to 'doc') diff --git a/doc/companion.xsl b/doc/companion.xsl index 1215d9af..14e2194e 100644 --- a/doc/companion.xsl +++ b/doc/companion.xsl @@ -1,5 +1,5 @@ -
@@ -44,18 +44,22 @@ The Companion Port provides two different functions: + Power. Both battery-level and 3.3V regulated power are available. Note that the amount of regulated power is not huge; TeleMetrum contains a 150mA regulator and uses, at peak, about 120mA or so. For applications needing more than a few dozen mA, placing a separate regulator on them and using the battery for power is probably a good idea. + + SPI. The flight computer operates as a SPI master, using a protocol defined in this document. Companion boards provide a matching SPI slave implementation which supplies telemetry information for the radio downlink during flight + @@ -85,9 +89,11 @@
SPI Message Formats + This section first defines the command message format sent from the flight computer to the companion board, and then the various reply message formats for each type of command message. +
Command Message
-- cgit v1.2.3 From f9bbca59a9034cf7e6df4577e627d7447f3a9d51 Mon Sep 17 00:00:00 2001 From: Keith Packard Date: Mon, 18 Nov 2013 12:42:20 -0800 Subject: doc: Make micropeak.xsl validate Signed-off-by: Keith Packard --- doc/micropeak.xsl | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'doc') diff --git a/doc/micropeak.xsl b/doc/micropeak.xsl index 96179d01..afa6fd15 100644 --- a/doc/micropeak.xsl +++ b/doc/micropeak.xsl @@ -55,7 +55,8 @@ - + + Acknowledgements Thanks to John Lyngdal for suggesting that we build something like this. @@ -70,7 +71,7 @@ Keith Packard, KD7SQG NAR #88757, TRA #12200 - + Quick Start Guide -- cgit v1.2.3 From 89fc38f2cf143bed1fe8c4a4972267b15c9aa467 Mon Sep 17 00:00:00 2001 From: Keith Packard Date: Mon, 18 Nov 2013 12:42:38 -0800 Subject: doc: Make pdf files depend on local stylesheet Now that we're using our own, rebuild the docs when it changes Signed-off-by: Keith Packard --- doc/Makefile | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) (limited to 'doc') diff --git a/doc/Makefile b/doc/Makefile index 6e326ba5..c45e084b 100644 --- a/doc/Makefile +++ b/doc/Makefile @@ -19,7 +19,7 @@ HTML=altusmetrum.html altos.html telemetry.html companion.html micropeak.html $( PDF=altusmetrum.pdf altos.pdf telemetry.pdf companion.pdf micropeak.pdf DOC=$(HTML) $(PDF) HTMLSTYLE=/usr/share/xml/docbook/stylesheet/docbook-xsl/html/docbook.xsl -FOSTYLE=./xorg-fo.xsl +FOSTYLE=xorg-fo.xsl PDFSTYLE= IMAGES=telemetrum.svg telemini.svg @@ -52,7 +52,9 @@ distclean: rm -f $(HTML) $(PDF) altusmetrum.html: $(RELNOTES_XSL) $(IMAGES) -altusmetrum.fo: $(RELNOTES_XSL) $(IMAGES) +altusmetrum.pdf: $(RELNOTES_XSL) $(IMAGES) + +$(PDF): $(FOSTYLE) indent: altusmetrum.xsl xmlindent -i 2 < altusmetrum.xsl > altusmetrum.new -- cgit v1.2.3 From 92753d4b8d6b17ebc7a9b65680abd46648726393 Mon Sep 17 00:00:00 2001 From: Keith Packard Date: Mon, 18 Nov 2013 12:43:33 -0800 Subject: doc: Use system fo docbool.xsl instead of network one Instead of reading the master stylesheet from the network, just use the one installed on the system. Signed-off-by: Keith Packard --- doc/xorg-fo.xsl | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'doc') diff --git a/doc/xorg-fo.xsl b/doc/xorg-fo.xsl index 896fcb6c..26728d50 100644 --- a/doc/xorg-fo.xsl +++ b/doc/xorg-fo.xsl @@ -8,7 +8,7 @@ --> - + -- cgit v1.2.3 From 3eaaefe6d746a2f53995a2470c5024f37c87c393 Mon Sep 17 00:00:00 2001 From: Keith Packard Date: Sun, 24 Nov 2013 20:05:52 -0800 Subject: Extend the hardware overview chapter. Edit System Operations Extend the overview chapter to include tables describing the electronic and physical board characteristics of each board. Finish most of the System Operation stuff, still need to add pyro channel configuration Signed-off-by: Keith Packard --- doc/altusmetrum.xsl | 675 +++++++++++++++++++++++++++++++++++++++++----------- 1 file changed, 531 insertions(+), 144 deletions(-) (limited to 'doc') diff --git a/doc/altusmetrum.xsl b/doc/altusmetrum.xsl index 5375e8c2..ec8a1a5a 100644 --- a/doc/altusmetrum.xsl +++ b/doc/altusmetrum.xsl @@ -320,102 +320,454 @@ NAR #88757, TRA #12200 - Hardware Overview - - TeleMetrum is a 1 inch by 2¾ inch circuit board. It was designed to - fit inside coupler for 29mm air-frame tubing, but using it in a tube that - small in diameter may require some creativity in mounting and wiring - to succeed! The presence of an accelerometer means TeleMetrum should - be aligned along the flight axis of the airframe, and by default the 1/4 - wave UHF wire antenna should be on the nose-cone end of the board. The - antenna wire is about 7 inches long, and wiring for a power switch and - the e-matches for apogee and main ejection charges depart from the - fin can end of the board, meaning an ideal "simple" avionics - bay for TeleMetrum should have at least 10 inches of interior length. - - - TeleMini v1.0 is a ½ inch by 1½ inch circuit board. It was designed to - fit inside an 18mm air-frame tube, but using it in a tube that - small in diameter may require some creativity in mounting and wiring - to succeed! Since there is no accelerometer, TeleMini can be mounted - in any convenient orientation. The default ¼ - wave UHF wire antenna attached to the center of one end of - the board is about 7 inches long, and wiring for a power switch and - the e-matches for apogee and main ejection charges depart from the - other end of the board, meaning an ideal "simple" avionics - bay for TeleMini should have at least 9 inches of interior length. - - - TeleMini v2.0 and EasyMini are both built on a 0.8 inch by 1½ - inch circuit board. They're designed to fit in a 24mm coupler - tube. TeleMini has an antenna, which must be run straight out - fro the board. Bending or folding it will dramatically reduce RF - performance. For smaller rockets, it's often best to drill a - hole in the bulkhead forward of TeleMini and run the antenna - wire through that and alongside any recovery components - there. Be careful to seal the hole to prevent ejection gasses - from passing through the hole and damaging the electronics. - - - TeleMega is a 1¼ inch by 3¼ inch circuit board. It was - designed to easily fit in a 38mm coupler. Like TeleMetrum, - TeleMega has an accelerometer and so it must be mounted so that - the board is aligned with the flight axis. It can be mounted - either antenna up or down. - - - A typical installation involves attaching - only a suitable battery, a single pole switch for - power on/off, and two pairs of wires connecting e-matches for the - apogee and main ejection charges. All Altus Metrum products are - designed for use with single-cell batteries with 3.7 volts - nominal. TeleMini v2.0 and EasyMini may also be used with other - batteries as long as they supply between 4 and 12 volts. - - - The battery connectors are a standard 2-pin JST connector and - match batteries sold by Spark Fun. These batteries are - single-cell Lithium Polymer batteries that nominally provide 3.7 - volts. Other vendors sell similar batteries for RC aircraft - using mating connectors, however the polarity for those is - generally reversed from the batteries used by Altus Metrum - products. In particular, the Tenergy batteries supplied for use - in Featherweight flight computers are not compatible with Altus - Metrum flight computers or battery chargers. Check - polarity and voltage before connecting any battery not purchased - from Altus Metrum or Spark Fun. - - - By default, we use the unregulated output of the battery directly - to fire ejection charges. This works marvelously with standard - low-current e-matches like the J-Tek from MJG Technologies, and with - Quest Q2G2 igniters. However, if you want or need to use a separate - pyro battery, check out the "External Pyro Battery" section in this - manual for instructions on how to wire that up. The altimeters are - designed to work with an external pyro battery of no more than 15 volts. - - - Ejection charges are wired directly to the screw terminal block - at the aft end of the altimeter. You'll need a very small straight - blade screwdriver for these screws, such as you might find in a - jeweler's screwdriver set. - - - Except for TeleMini v1.0, the flight computers also use the - screw terminal block for the power switch leads. On TeleMini v1.0, - the power switch leads are soldered directly to the board and - can be connected directly to a switch. - - - For most air-frames, the integrated antennas are more than - adequate. However, if you are installing in a carbon-fiber or - metal electronics bay which is opaque to RF signals, you may need to - use off-board external antennas instead. In this case, you can - order an altimeter with an SMA connector for the UHF antenna - connection, and, on TeleMetrum v1, you can unplug the integrated GPS - antenna and select an appropriate off-board GPS antenna with - cable terminating in a U.FL connector. - + Altus Metrum Hardware +
+ Overview + + Here's the full set of Altus Metrum products, both in + production and retired. + +
+ Altus Metrum Electronics + + + + + + + + + + + + Device + Barometer + Z-axis accelerometer + GPS + 3D sensors + Storage + RF Output + Battery + + + + + TeleMetrum v1.0 + MP3H6115 10km (33k') + MMA2202 50g + SkyTraq + - + 1MB + 10mW + 3.7V + + + TeleMetrum v1.1 + MP3H6115 10km (33k') + MMA2202 50g + SkyTraq + - + 2MB + 10mW + 3.7V + + + TeleMetrum v1.2 + MP3H6115 10km (33k') + ADXL78 70g + SkyTraq + - + 2MB + 10mW + 3.7V + + + TeleMetrum v2.0 + MS5607 30km (100k') + MMA6555 102g + uBlox Max-7Q + - + 8MB + 40mW + 3.7V + + + TeleMini v1.0 + MP3H6115 10km (33k') + - + - + - + 5kB + 10mW + 3.7V + + + TeleMini v2.0 + MS5607 30km (100k') + - + - + - + 1MB + 10mW + 3.7-12V + + + EasyMini v1.0 + MS5607 30km (100k') + - + - + - + 1MB + - + 3.7-12V + + + TeleMega v1.0 + MS5607 30km (100k') + MMA6555 102g + uBlox Max-7Q + MPU6000 HMC5883 + 8MB + 40mW + 3.7V + + + +
+ + Altus Metrum Boards + + + + + + + + + + Device + Connectors + Screw Terminals + Width + Length + Tube Size + + + + + TeleMetrum + + Antenna + Debug + Companion + USB + Battery + + Apogee pyro Main pyro Switch + 1 inch (2.54cm) + 2 ¾ inch (6.99cm) + 29mm coupler + + + TeleMini v1.0 + + Antenna + Debug + Battery + + + Apogee pyro + Main pyro + + ½ inch (1.27cm) + 1½ inch (3.81cm) + 18mm aiframe + + + TeleMini v2.0 + + Antenna + Debug + USB + Battery + + + Apogee pyro + Main pyro + Battery + Switch + + 0.8 inch (2.03cm) + 1½ inch (3.81cm) + 24mm coupler + + + EasyMini + + Debug + USB + Battery + + + Apogee pyro + Main pyro + Battery + Switch + + 0.8 inch (2.03cm) + 1½ inch (3.81cm) + 24mm coupler + + + TeleMega + + Antenna + Debug + Companion + USB + Battery + + + Apogee pyro + Main pyro + Pyro A-D + Switch + Pyro battery + + 1¼ inch (3.18cm) + 3¼ inch (8.26cm) + 38mm coupler + + + +
+
+
+ TeleMetrum + + TeleMetrum is a 1 inch by 2¾ inch circuit board. It was designed to + fit inside coupler for 29mm air-frame tubing, but using it in a tube that + small in diameter may require some creativity in mounting and wiring + to succeed! The presence of an accelerometer means TeleMetrum should + be aligned along the flight axis of the airframe, and by default the 1/4 + wave UHF wire antenna should be on the nose-cone end of the board. The + antenna wire is about 7 inches long, and wiring for a power switch and + the e-matches for apogee and main ejection charges depart from the + fin can end of the board, meaning an ideal "simple" avionics + bay for TeleMetrum should have at least 10 inches of interior length. + +
+
+ TeleMini + + TeleMini v1.0 is ½ inches by 1½ inches. It was + designed to fit inside an 18mm air-frame tube, but using it in + a tube that small in diameter may require some creativity in + mounting and wiring to succeed! Since there is no + accelerometer, TeleMini can be mounted in any convenient + orientation. The default ¼ wave UHF wire antenna attached to + the center of one end of the board is about 7 inches long. Two + wires for the power switch are connected to holes in the + middle of the board. Screw terminals for the e-matches for + apogee and main ejection charges depart from the other end of + the board, meaning an ideal "simple" avionics bay for TeleMini + should have at least 9 inches of interior length. + + + TeleMini v2.0 is 0.8 inches by 1½ inches. It adds more + on-board data logging memory, a built-in USB connector and + screw terminals for the battery and power switch. The larger + board fits in a 24mm coupler. There's also a battery connector + for a LiPo battery if you want to use one of those. + +
+
+ EasyMini + + EasyMini is built on a 0.8 inch by 1½ inch circuit board. It's + designed to fit in a 24mm coupler tube. The connectors and + screw terminals match TeleMini, so you can swap an EasyMini + with a TeleMini. + +
+
+ TeleMega + + TeleMega is a 1¼ inch by 3¼ inch circuit board. It was + designed to easily fit in a 38mm coupler. Like TeleMetrum, + TeleMega has an accelerometer and so it must be mounted so that + the board is aligned with the flight axis. It can be mounted + either antenna up or down. + +
+
+ Flight Data Recording + + Each flight computer logs data at 100 samples per second + during ascent and 10 samples per second during descent, except + for TeleMini v1.0, which records ascent at 10 samples per + second and descent at 1 sample per second. Data are logged to + an on-board flash memory part, which can be partitioned into + several equal-sized blocks, one for each flight. + + + Data Storage on Altus Metrum altimeters + + + + + + + + Device + Bytes per Sample + Total Storage + Minutes at Full Rate + + + + + TeleMetrum v1.0 + 8 + 1MB + 20 + + + TeleMetrum v1.1 v1.2 + 8 + 2MB + 40 + + + TeleMetrum v2.0 + 16 + 8MB + 80 + + + TeleMini v1.0 + 2 + 5kB + 4 + + + TeleMini v2.0 + 16 + 1MB + 10 + + + EasyMini + 16 + 1MB + 10 + + + TeleMega + 32 + 8MB + 40 + + + +
+ + The on-board flash is partitioned into separate flight logs, + each of a fixed maximum size. Increase the maximum size of + each log and you reduce the number of flights that can be + stored. Decrease the size and you can store more flights. + + + Configuration data is also stored in the flash memory on + TeleMetrum v1.x, TeleMini and EasyMini. This consumes 64kB + of flash space. This configuration space is not available + for storing flight log data. TeleMetrum v2.0 and TeleMega + store configuration data in a bit of eeprom available within + the processor chip, leaving that space available in flash for + more flight data. + + + To compute the amount of space needed for a single flight, you + can multiply the expected ascent time (in seconds) by 100 + times bytes-per-sample, multiply the expected descent time (in + seconds) by 10 times the bytes per sample and add the two + together. That will slightly under-estimate the storage (in + bytes) needed for the flight. For instance, a TeleMetrum v2.0 flight spending + 20 seconds in ascent and 150 seconds in descent will take + about (20 * 1600) + (150 * 160) = 56000 bytes of storage. You + could store dozens of these flights in the on-board flash. + + + The default size allows for several flights on each flight + computer, except for TeleMini v1.0, which only holds data for a + single flight. You can adjust the size. + + + Altus Metrum flight computers will not overwrite existing + flight data, so be sure to download flight data and erase it + from the flight computer before it fills up. The flight + computer will still successfully control the flight even if it + cannot log data, so the only thing you will lose is the data. + +
+
+ Installation + + A typical installation involves attaching + only a suitable battery, a single pole switch for + power on/off, and two pairs of wires connecting e-matches for the + apogee and main ejection charges. All Altus Metrum products are + designed for use with single-cell batteries with 3.7 volts + nominal. TeleMini v2.0 and EasyMini may also be used with other + batteries as long as they supply between 4 and 12 volts. + + + The battery connectors are a standard 2-pin JST connector and + match batteries sold by Spark Fun. These batteries are + single-cell Lithium Polymer batteries that nominally provide 3.7 + volts. Other vendors sell similar batteries for RC aircraft + using mating connectors, however the polarity for those is + generally reversed from the batteries used by Altus Metrum + products. In particular, the Tenergy batteries supplied for use + in Featherweight flight computers are not compatible with Altus + Metrum flight computers or battery chargers. Check + polarity and voltage before connecting any battery not purchased + from Altus Metrum or Spark Fun. + + + By default, we use the unregulated output of the battery directly + to fire ejection charges. This works marvelously with standard + low-current e-matches like the J-Tek from MJG Technologies, and with + Quest Q2G2 igniters. However, if you want or need to use a separate + pyro battery, check out the "External Pyro Battery" section in this + manual for instructions on how to wire that up. The altimeters are + designed to work with an external pyro battery of no more than 15 volts. + + + + Ejection charges are wired directly to the screw terminal block + at the aft end of the altimeter. You'll need a very small straight + blade screwdriver for these screws, such as you might find in a + jeweler's screwdriver set. + + + Except for TeleMini v1.0, the flight computers also use the + screw terminal block for the power switch leads. On TeleMini v1.0, + the power switch leads are soldered directly to the board and + can be connected directly to a switch. + + + For most air-frames, the integrated antennas are more than + adequate. However, if you are installing in a carbon-fiber or + metal electronics bay which is opaque to RF signals, you may need to + use off-board external antennas instead. In this case, you can + order an altimeter with an SMA connector for the UHF antenna + connection, and, on TeleMetrum v1, you can unplug the integrated GPS + antenna and select an appropriate off-board GPS antenna with + cable terminating in a U.FL connector. + +
System Operation @@ -679,25 +1031,28 @@ NAR #88757, TRA #12200 data later... - We don't generally use a 'normal packet radio' mode like APRS because they're - just too inefficient. The GFSK modulation we use is FSK with the - base-band pulses passed through a - Gaussian filter before they go into the modulator to limit the - transmitted bandwidth. When combined with the hardware forward error - correction support in the cc1111 chip, this allows us to have a very - robust 38.4 kilobit data link with only 10 milliwatts of transmit - power, a whip antenna in the rocket, and a hand-held Yagi on the - ground. We've had flights to above 21k feet AGL with great reception, - and calculations suggest we should be good to well over 40k feet AGL - with a 5-element yagi on the ground. We hope to fly boards to higher - altitudes over time, and would of course appreciate customer feedback - on performance in higher altitude flights! - - - However, TeleMetrum v2.0 and TeleMega can send APRS if - desired, 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. + We don't generally use a 'normal packet radio' mode like APRS + because they're just too inefficient. The GFSK modulation we + use is FSK with the base-band pulses passed through a Gaussian + filter before they go into the modulator to limit the + transmitted bandwidth. When combined with forward error + correction and interleaving, this allows us to have a very + robust 19.2 kilobit data link with only 10-40 milliwatts of + transmit power, a whip antenna in the rocket, and a hand-held + Yagi on the ground. We've had flights to above 21k feet AGL + with great reception, and calculations suggest we should be + good to well over 40k feet AGL with a 5-element yagi on the + ground with our 10mW units and over 100k feet AGL with the + 40mW devices. We hope to fly boards to higher altitudes over + time, and would of course appreciate customer feedback on + performance in higher altitude flights! + + + TeleMetrum v2.0 and TeleMega can send APRS if desired, 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.
@@ -760,16 +1115,38 @@ NAR #88757, TRA #12200
Maximum Flight Log - TeleMetrum version 1.1 and 1.2 have 2MB of on-board flash storage, - enough to hold over 40 minutes of data at full data rate - (100 samples/second). TeleMetrum 1.0 has 1MB of on-board - storage. As data are stored at a reduced rate during descent - (10 samples/second), there's plenty of space to store many - flights worth of data. - - - TeleMetrum v2.0 and TeleMega have 8MB of on-board flash stroage, enough to hold + Each flight computer logs data at 100 samples per second + during ascent and 10 samples per second during descent. Data + are logged to an on-board flash memory part, which can be + partitioned into several equal-sized blocks, one for each + flight. + + Data Storage on Altus Metrum altimeters + + + + + + + + Device + Bytes per Sample + Total Storage + Minutes at Full Rate + + + + + TeleMetrum v1.x + 8 + 2MB + 40 + + + +
The on-board flash is partitioned into separate flight logs, each of a fixed maximum size. Increase the maximum size of @@ -778,21 +1155,25 @@ NAR #88757, TRA #12200 flights. - All of the configuration data is also stored in the flash - memory, which consumes 64kB on TeleMetrum v1.1/v1.2 and 256B on - TeleMetrum v1.0. This configuration space is not available - for storing flight log data. + Configuration data is also stored in the flash memory on + TeleMetrum v1.x, TeleMini and EasyMini. This consumes 64kB + of flash space. This configuration space is not available + for storing flight log data. TeleMetrum v2.0 and TeleMega + store configuration data in a bit of eeprom available within + the processor chip. To compute the amount of space needed for a single flight, you can multiply the expected ascent time (in seconds) by - 800, multiply the expected descent time (in seconds) by 80 - and add the two together. That will slightly under-estimate - the storage (in bytes) needed for the flight. For instance, - a flight spending 20 seconds in ascent and 150 seconds in - descent will take about (20 * 800) + (150 * 80) = 28000 - bytes of storage. You could store dozens of these flights in - the on-board flash. + 100 times bytes-per-sample (8 for TeleMetrum v1.x, 16 for + TeleMetrum v2.0 and 32 for TeleMega), multiply the expected + descent time (in seconds) by 80 and add the two + together. That will slightly under-estimate the storage (in + bytes) needed for the flight. For instance, a flight + spending 20 seconds in ascent and 150 seconds in descent + will take about (20 * 800) + (150 * 80) = 28000 bytes of + storage. You could store dozens of these flights in the + on-board flash. The default size, 192kB, allows for 10 flights of storage on @@ -820,7 +1201,7 @@ NAR #88757, TRA #12200 a fixed height above the ground, you can configure the altimeter to fire both at apogee or both during descent. This was added to support an airframe that has two - TeleMetrum computers, one in the fin can and one in the + altimeters, one in the fin can and one in the nose. @@ -833,17 +1214,23 @@ NAR #88757, TRA #12200
Pad Orientation - TeleMetrum measures acceleration along the axis of the - board. Which way the board is oriented affects the sign of - the acceleration value. Instead of trying to guess which way - the board is mounted in the air frame, TeleMetrum must be - explicitly configured for either Antenna Up or Antenna - Down. The default, Antenna Up, expects the end of the - TeleMetrum board connected to the 70cm antenna to be nearest - the nose of the rocket, with the end containing the screw + TeleMetrum and TeleMega measure acceleration along the axis + of the board. Which way the board is oriented affects the + sign of the acceleration value. Instead of trying to guess + which way the board is mounted in the air frame, the + altimeter must be explicitly configured for either Antenna + Up or Antenna Down. The default, Antenna Up, expects the end + of the board connected to the 70cm antenna to be nearest the + nose of the rocket, with the end containing the screw terminals nearest the tail.
+
+ Pyro Channels + + TeleMega + +
-- cgit v1.2.3 From 96f33e780958adaaa4a9cc127caecaeb3f4c978c Mon Sep 17 00:00:00 2001 From: Keith Packard Date: Sun, 24 Nov 2013 21:25:06 -0800 Subject: Remove duplicate log description. Describe pyro config. Signed-off-by: Keith Packard --- doc/altusmetrum.xsl | 253 ++++++++++++++++++++++++++++++++++------------------ doc/xorg-fo.xsl | 22 ++++- 2 files changed, 188 insertions(+), 87 deletions(-) (limited to 'doc') diff --git a/doc/altusmetrum.xsl b/doc/altusmetrum.xsl index ec8a1a5a..9020881f 100644 --- a/doc/altusmetrum.xsl +++ b/doc/altusmetrum.xsl @@ -1115,83 +1115,13 @@ NAR #88757, TRA #12200
Maximum Flight Log - Each flight computer logs data at 100 samples per second - during ascent and 10 samples per second during descent. Data - are logged to an on-board flash memory part, which can be - partitioned into several equal-sized blocks, one for each - flight. - - - Data Storage on Altus Metrum altimeters - - - - - - - - Device - Bytes per Sample - Total Storage - Minutes at Full Rate - - - - - TeleMetrum v1.x - 8 - 2MB - 40 - - - -
- - The on-board flash is partitioned into separate flight logs, - each of a fixed maximum size. Increase the maximum size of - each log and you reduce the number of flights that can be - stored. Decrease the size and TeleMetrum can store more - flights. - - - Configuration data is also stored in the flash memory on - TeleMetrum v1.x, TeleMini and EasyMini. This consumes 64kB - of flash space. This configuration space is not available - for storing flight log data. TeleMetrum v2.0 and TeleMega - store configuration data in a bit of eeprom available within - the processor chip. - - - To compute the amount of space needed for a single flight, - you can multiply the expected ascent time (in seconds) by - 100 times bytes-per-sample (8 for TeleMetrum v1.x, 16 for - TeleMetrum v2.0 and 32 for TeleMega), multiply the expected - descent time (in seconds) by 80 and add the two - together. That will slightly under-estimate the storage (in - bytes) needed for the flight. For instance, a flight - spending 20 seconds in ascent and 150 seconds in descent - will take about (20 * 800) + (150 * 80) = 28000 bytes of - storage. You could store dozens of these flights in the - on-board flash. - - - The default size, 192kB, allows for 10 flights of storage on - TeleMetrum v1.1/v1.2 and 5 flights on TeleMetrum v1.0. This - ensures that you won't need to erase the memory before - flying each time while still allowing more than sufficient - storage for each flight. - - - As TeleMini does not contain an accelerometer, it stores - data at 10 samples per second during ascent and one sample - per second during descent. Each sample is a two byte reading - from the barometer. These are stored in 5kB of - on-chip flash memory which can hold 256 seconds at the - ascent rate or 2560 seconds at the descent rate. Because of - the limited storage, TeleMini cannot hold data for more than - one flight, and so must be erased after each flight or it - will not capture data for subsequent flights. + Changing this value will set the maximum amount of flight + log storage that an individual flight will use. The + available storage is divided into as many flights of the + specified size as can fit in the available space. You can + download and erase individual flight logs. If you fill up + the available storage, future flights will not get logged + until you erase some of the stored ones.
@@ -1228,8 +1158,160 @@ NAR #88757, TRA #12200
Pyro Channels - TeleMega + In addition to the usual Apogee and Main pyro channels, + TeleMega has four additional channels that can be configured + to activate when various flight conditions are + satisfied. You can select as many conditions as necessary; + all of them must be met in order to activate the + channel. The conditions available are: + + + + Acceleration away from the ground. Select a value, and + then choose whether acceleration should be above or + below that value. Acceleration is positive upwards, so + accelerating towards the ground would produce negative + numbers. Acceleration during descent is noisy and + inaccurate, so be careful when using it during these + phases of the flight. + + + + + Vertical speed. Select a value, and then choose whether + vertical speed should be above or below that + value. Speed is positive upwards, so moving towards the + ground would produce negative numbers. Speed during + descent is a bit noisy and so be careful when using it + during these phases of the flight. + + + + + Height. Select a value, and then choose whether the + height above the launch pad should be above or below + that value. + + + + + Orientation. TeleMega contains a 3-axis gyroscope and + accelerometer which is used to measure the current + angle. Note that this 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 launch pad and initialize the + system. Because this value is computed by integrating + rate gyros, it gets progressively less accurate as the + flight goes on. It should have an accumulated error of + less than .2°/second (after 10 seconds of flight, the + error should be less than 2°). + + + The usual use of the orientation configuration is to + ensure that the rocket is traveling mostly upwards when + deciding whether to ignite air starts or additional + stages. For that, choose a reasonable maximum angle + (like 20°) and set the motor igniter to require an angle + of less than that value. + + + + + Flight Time. Time since boost was detected. Select a + value and choose whether to activate the pyro channel + before or after that amount of time. + + + + + Ascending. A simple test saying whether the rocket is + going up or not. This is exactly equivalent to testing + whether the speed is > 0. + + + + + Descending. A simple test saying whether the rocket is + going down or not. This is exactly equivalent to testing + whether the speed is < 0. + + + + + 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. + + + + + Delay. This value doesn't perform any checks, instead it + inserts a delay between the time when the other + parameters become true and when the pyro channel is + activated. + + + + + Flight State. The flight software tracks the flight + through a sequence of states: + + + + Boost. The motor has lit and the rocket is + accelerating upwards. + + + + + Fast. The motor has burned out and the rocket is + descellerating, but it is going faster than 200m/s. + + + + + Coast. The rocket is still moving upwards and + decelerating, but the speed is less than 200m/s. + + + + + Drogue. The rocket has reached apogee and is heading + back down, but is above the configured Main + altitude. + + + + + Main. The rocket is still descending, and is blow + the Main altitude + + + + + Landed. The rocket is no longer moving. + + + + + + You can select a state to limit when the pyro channel + may activate; note that the check is based on when the + rocket transitions *into* the state, and so checking for + 'greater than Boost' means that the rocket is currently + in boost state. + + + When a motor burns out, the rocket enters either Fast or + Coast state (depending on how fast it is moving). If the + computer detects upwards acceleration again, it will + move back to Boost state. + + +
@@ -1239,9 +1321,8 @@ NAR #88757, TRA #12200 AltosUI The AltosUI program provides a graphical user interface for - interacting with the Altus Metrum product family, including - TeleMetrum, TeleMini and TeleDongle. AltosUI can monitor telemetry data, - configure TeleMetrum, TeleMini and TeleDongle devices and many other + interacting with the Altus Metrum product family. AltosUI can + monitor telemetry data, configure devices and many other tasks. The primary interface window provides a selection of buttons, one for each major activity in the system. This manual is split into chapters, each of which documents one of the tasks @@ -1792,11 +1873,11 @@ NAR #88757, TRA #12200
Pad Orientation - Because it includes an accelerometer, TeleMetrum is - sensitive to the orientation of the board. By default, it - expects the antenna end to point forward. This parameter - allows that default to be changed, permitting the board to - be mounted with the antenna pointing aft instead. + Because it includes an accelerometer, TeleMetrum and + TeleMega are sensitive to the orientation of the board. By + default, it expects the antenna end to point forward. This + parameter allows that default to be changed, permitting the + board to be mounted with the antenna pointing aft instead. diff --git a/doc/xorg-fo.xsl b/doc/xorg-fo.xsl index 26728d50..a02ad1ea 100644 --- a/doc/xorg-fo.xsl +++ b/doc/xorg-fo.xsl @@ -7,7 +7,11 @@ http://docbook.sourceforge.net/release/xsl/current/doc/fo/ --> - + @@ -94,4 +98,20 @@ DejaVu Serif serif,Symbol,AR PL UMing CN,AR PL ShanHeiSun Uni,GNU Unifont + + + + + + + + + + + + + + + + -- cgit v1.2.3 From 31a1c701bfaea97225e12ea0688b934790e3737e Mon Sep 17 00:00:00 2001 From: Keith Packard Date: Sun, 24 Nov 2013 21:28:26 -0800 Subject: Use more 1/4 single characters --- doc/altusmetrum.xsl | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'doc') diff --git a/doc/altusmetrum.xsl b/doc/altusmetrum.xsl index 9020881f..68cb22ec 100644 --- a/doc/altusmetrum.xsl +++ b/doc/altusmetrum.xsl @@ -549,7 +549,7 @@ NAR #88757, TRA #12200 fit inside coupler for 29mm air-frame tubing, but using it in a tube that small in diameter may require some creativity in mounting and wiring to succeed! The presence of an accelerometer means TeleMetrum should - be aligned along the flight axis of the airframe, and by default the 1/4 + be aligned along the flight axis of the airframe, and by default the ¼ wave UHF wire antenna should be on the nose-cone end of the board. The antenna wire is about 7 inches long, and wiring for a power switch and the e-matches for apogee and main ejection charges depart from the @@ -2657,7 +2657,7 @@ NAR #88757, TRA #12200 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 + simple ratio of that length; essentially any multiple of ¼ of the wavelength (17.5cm). -- cgit v1.2.3 From 6f4abc14065aebceaac9313e4dcd4300e19999cf Mon Sep 17 00:00:00 2001 From: Keith Packard Date: Sun, 24 Nov 2013 21:50:27 -0800 Subject: doc: "rocketry electronics" instead of listing products --- doc/altusmetrum.xsl | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'doc') diff --git a/doc/altusmetrum.xsl b/doc/altusmetrum.xsl index 68cb22ec..cb4af64b 100644 --- a/doc/altusmetrum.xsl +++ b/doc/altusmetrum.xsl @@ -3,7 +3,7 @@ "/usr/share/xml/docbook/schema/dtd/4.5/docbookx.dtd"> The Altus Metrum System - An Owner's Manual for TeleMetrum, TeleMini, TeleDongle and TeleBT Devices + An Owner's Manual for Altus Metrum Rocketry Electronics Bdale -- cgit v1.2.3 From f743934ebd1a7c7c8b6db0223f0309e590aa15cd Mon Sep 17 00:00:00 2001 From: Keith Packard Date: Sun, 24 Nov 2013 21:55:20 -0800 Subject: doc: use correct quotes in altusmetrum.xsl Signed-off-by: Keith Packard --- doc/altusmetrum.xsl | 116 ++++++++++++++++++++++++++-------------------------- 1 file changed, 58 insertions(+), 58 deletions(-) (limited to 'doc') diff --git a/doc/altusmetrum.xsl b/doc/altusmetrum.xsl index cb4af64b..0af2a5e8 100644 --- a/doc/altusmetrum.xsl +++ b/doc/altusmetrum.xsl @@ -106,9 +106,9 @@ Acknowledgements - Thanks to Bob Finch, W9YA, NAR 12965, TRA 12350 for writing "The + Thanks to Bob Finch, W9YA, NAR 12965, TRA 12350 for writing “The Mere-Mortals Quick Start/Usage Guide to the Altus Metrum Starter - Kit" which formed the basis of the original Getting Started chapter + Kit” which formed the basis of the original Getting Started chapter in this manual. Bob was one of our first customers for a production TeleMetrum, and his continued enthusiasm and contributions are immensely gratifying and highly appreciated! @@ -145,7 +145,7 @@ NAR #88757, TRA #12200 The first device created for our community was TeleMetrum, a dual deploy altimeter with fully integrated GPS and radio telemetry - as standard features, and a "companion interface" that will + as standard features, and a “companion interface” that will support optional capabilities in the future. The latest version of TeleMetrum, v2.0, has all of the same features but with improved sensors and radio to offer increased performance. @@ -194,7 +194,7 @@ NAR #88757, TRA #12200 Getting Started The first thing to do after you check the inventory of parts in your - "starter kit" is to charge the battery. + “starter kit” is to charge the battery. For TeleMetrum and TeleMega, the battery can be charged by plugging it into the @@ -243,7 +243,7 @@ NAR #88757, TRA #12200 The other active device in the starter kit is the TeleDongle USB to RF interface. If you plug it in to your Mac or Linux computer it should - "just work", showing up as a serial port device. Windows systems need + “just work”, showing up as a serial port device. Windows systems need driver information that is part of the AltOS download to know that the existing USB modem driver will work. We therefore recommend installing our software before plugging in TeleDongle if you are using a Windows @@ -296,19 +296,19 @@ NAR #88757, TRA #12200 The barometric sensors used on all of our flight computers are sensitive to sunlight. In normal mounting situations, the baro sensor and all of the other surface mount components - are "down" towards whatever the underlying mounting surface is, so + are “down” towards whatever the underlying mounting surface is, so this is not normally a problem. Please consider this, though, when designing an installation, for example, in an air-frame with a see-through plastic payload bay. It is particularly important to consider this with TeleMini v1.0, both because the baro sensor is on the - "top" of the board, and because many model rockets with payload bays + “top” of the board, and because many model rockets with payload bays use clear plastic for the payload bay! Replacing these with an opaque cardboard tube, painting them, or wrapping them with a layer of masking tape are all reasonable approaches to keep the sensor out of direct sunlight. - The barometric sensor sampling port must be able to "breathe", + The barometric sensor sampling port must be able to “breathe”, both by not being covered by foam or tape or other materials that might directly block the hole on the top of the sensor, and also by having a suitable static vent to outside air. @@ -553,7 +553,7 @@ NAR #88757, TRA #12200 wave UHF wire antenna should be on the nose-cone end of the board. The antenna wire is about 7 inches long, and wiring for a power switch and the e-matches for apogee and main ejection charges depart from the - fin can end of the board, meaning an ideal "simple" avionics + fin can end of the board, meaning an ideal “simple” avionics bay for TeleMetrum should have at least 10 inches of interior length.
@@ -570,7 +570,7 @@ NAR #88757, TRA #12200 wires for the power switch are connected to holes in the middle of the board. Screw terminals for the e-matches for apogee and main ejection charges depart from the other end of - the board, meaning an ideal "simple" avionics bay for TeleMini + the board, meaning an ideal “simple” avionics bay for TeleMini should have at least 9 inches of interior length. @@ -740,7 +740,7 @@ NAR #88757, TRA #12200 to fire ejection charges. This works marvelously with standard low-current e-matches like the J-Tek from MJG Technologies, and with Quest Q2G2 igniters. However, if you want or need to use a separate - pyro battery, check out the "External Pyro Battery" section in this + pyro battery, check out the “External Pyro Battery” section in this manual for instructions on how to wire that up. The altimeters are designed to work with an external pyro battery of no more than 15 volts. @@ -775,45 +775,45 @@ NAR #88757, TRA #12200 Firmware Modes The AltOS firmware build for the altimeters has two - fundamental modes, "idle" and "flight". Which of these modes + fundamental modes, “idle” and “flight”. Which of these modes the firmware operates in is determined at start up time. For TeleMetrum, 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 + power is switched on. If the rocket is “nose up”, then TeleMetrum assumes it's on a rail or rod being prepared for launch, so the firmware chooses flight mode. However, if the rocket is more or less horizontal, the firmware instead enters idle mode. Since TeleMini v2.0 and EasyMini don't have an - accelerometer we can use to determine orientation, "idle" mode + accelerometer we can use to determine orientation, “idle” mode is selected if the board is connected via USB to a computer, - otherwise the board enters "flight" mode. TeleMini v1.0 - selects "idle" mode if it receives a command packet within the + otherwise the board enters “flight” mode. TeleMini v1.0 + selects “idle” mode if it receives a command packet within the first five seconds of operation. At power on, you will hear three beeps or see three flashes - ("S" in Morse code for start up) and then a pause while + (“S” in Morse code for start up) and then a pause while the altimeter completes initialization and self test, and decides which mode to enter next. - In flight or "pad" mode, the altimeter engages the flight + In flight or “pad” mode, the altimeter engages the flight state machine, goes into transmit-only mode to send telemetry, and waits for launch to be detected. - Flight mode is indicated by an "di-dah-dah-dit" ("P" for pad) + Flight mode is indicated by an “di-dah-dah-dit” (“P” for pad) on the beeper or lights, followed by beeps or flashes indicating the state of the pyrotechnic igniter continuity. One beep/flash indicates apogee continuity, two beeps/flashes indicate main continuity, three beeps/flashes indicate both - apogee and main continuity, and one longer "brap" sound or + apogee and main continuity, and one longer “brap” sound or rapidly alternating lights indicates no continuity. For a dual deploy flight, make sure you're getting three beeps or flashes before launching! For apogee-only or motor eject flights, do what makes sense. - If idle mode is entered, you will hear an audible "di-dit" or - see two short flashes ("I" for idle), and the flight state + If idle mode is entered, you will hear an audible “di-dit” or + see two short flashes (“I” for idle), and the flight state machine is disengaged, thus no ejection charges will fire. The altimeters also listen for the radio link when in idle mode for requests sent via TeleDongle. Commands can be issued @@ -824,7 +824,7 @@ NAR #88757, TRA #12200 ground testing pyro charges. - One "neat trick" of particular value when TeleMetrum or TeleMega are used with + One “neat trick” of particular value when TeleMetrum or TeleMega are used with very large air-frames, is that you can power the board up while the rocket is horizontal, such that it comes up in idle mode. Then you can raise the air-frame to launch position, and issue a 'reset' command @@ -884,9 +884,9 @@ NAR #88757, TRA #12200 The flight computers provide backup power to the GPS chip any time a - battery is connected. This allows the receiver to "warm start" on + battery is connected. This allows the receiver to “warm start” on the launch rail much faster than if every power-on were a GPS - "cold start". In typical operations, powering up + “cold start”. In typical operations, powering up on the flight line in idle mode while performing final air-frame preparation will be sufficient to allow the GPS receiver to cold start and acquire lock. Then the board can be powered down during @@ -940,7 +940,7 @@ NAR #88757, TRA #12200 and additional pyro event conditions to respond to changing launch conditions. You can also 'reboot' the altimeter. Use this to remotely enable the - flight computer by turning TeleMetrum or TeleMega on in "idle" mode, + flight computer by turning TeleMetrum or TeleMega on in “idle” mode, then once the air-frame is oriented for launch, you can reboot the altimeter and have it restart in pad mode without having to climb the scary ladder. @@ -1000,9 +1000,9 @@ NAR #88757, TRA #12200 Just prep the rocket for flight, then power up the altimeter - in "idle" mode (placing air-frame horizontal for TeleMetrum or TeleMega, or + in “idle” mode (placing air-frame horizontal for TeleMetrum or TeleMega, or selecting the Configure Altimeter tab for TeleMini). This will cause - the firmware to go into "idle" mode, in which the normal flight + the firmware to go into “idle” mode, in which the normal flight state machine is disabled and charges will not fire without manual command. You can now command the altimeter to fire the apogee or main charges from a safe distance using your computer and @@ -1019,11 +1019,11 @@ NAR #88757, TRA #12200 By design, the altimeter firmware listens for the radio link when - it's in "idle mode", which + it's in “idle mode”, which allows us to use the radio link to configure the rocket, do things like ejection tests, and extract data after a flight without having to - crack open the air-frame. However, when the board is in "flight - mode", the altimeter only + crack open the air-frame. However, when the board is in “flight + mode”, the altimeter only transmits and doesn't listen at all. That's because we want to put ultimate priority on event detection and getting telemetry out of the rocket through @@ -1060,7 +1060,7 @@ NAR #88757, TRA #12200 Configuring an Altus Metrum altimeter for flight is very simple. Even on our baro-only TeleMini and EasyMini boards, the use of a Kalman - filter means there is no need to set a "mach delay". The few + filter means there is no need to set a “mach delay”. The few configurable parameters can all be set using AltosUI over USB or or radio link via TeleDongle. @@ -1069,7 +1069,7 @@ NAR #88757, TRA #12200 Altus Metrum boards support radio frequencies in the 70cm band. By default, the configuration interface provides a - list of 10 "standard" frequencies in 100kHz channels starting at + list of 10 “standard” frequencies in 100kHz channels starting at 434.550MHz. However, the firmware supports use of any 50kHz multiple within the 70cm band. At any given launch, we highly recommend coordinating when and by whom each @@ -2167,7 +2167,7 @@ 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 + except it works with the altimeter in “idle” mode by sending query commands to discover the current state rather than listening for telemetry packets. @@ -2193,8 +2193,8 @@ NAR #88757, TRA #12200 AltosDroid is included in the Google Play store. To install it on your Android device, open open the Google Play Store - application and search for "altosdroid". Make sure you don't - have a space between "altos" and "droid" or you probably won't + application and search for “altosdroid”. Make sure you don't + have a space between “altos” and “droid” or you probably won't find what you want. That should bring you to the right page from which you can download and install the application. @@ -2378,7 +2378,7 @@ NAR #88757, TRA #12200 Geo-Caching... just go to the way-point and look around starting from there. - You may also enjoy having a ham radio "HT" that covers the 70cm band... you + You may also enjoy having a ham radio “HT” that covers the 70cm band... you can use that with your antenna to direction-find the rocket on the ground the same way you can use a Walston or Beeline tracker. This can be handy if the rocket is hiding in sage brush or a tree, or if the last GPS position @@ -2451,7 +2451,7 @@ NAR #88757, TRA #12200
Future Plans - In the future, we intend to offer "companion boards" for the rocket + In the future, we intend to offer “companion boards” for the rocket that will plug in to TeleMetrum to collect additional data, provide more pyro channels, and so forth. @@ -2501,7 +2501,7 @@ NAR #88757, TRA #12200 securely fastened to the air-frame. For TeleMetrum, we use nylon standoffs and nylon screws; they're good to at least 50G and cannot cause any electrical issues on the board. For - TeleMini, we usually cut small pieces of 1/16" balsa to fit + TeleMini, we usually cut small pieces of 1/16 inch balsa to fit under the screw holes, and then take 2x56 nylon screws and screw them through the TeleMini mounting holes, through the balsa and into the underlying material. @@ -2896,7 +2896,7 @@ NAR #88757, TRA #12200 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. + letting it come up in “flight” mode and listening for telemetry. @@ -2923,7 +2923,7 @@ NAR #88757, TRA #12200 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. + plug the “mini” end in to the mating connector on TeleMetrum or TeleDongle. @@ -2977,7 +2977,7 @@ NAR #88757, TRA #12200 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 + 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. @@ -3135,15 +3135,15 @@ NAR #88757, TRA #12200 TeleMetrum seems to shut off when disconnected from the computer. Make sure the battery is adequately charged. Remember the unit will pull more power than the USB port can deliver before the - GPS enters "locked" mode. The battery charges best when TeleMetrum + GPS enters “locked” mode. The battery charges best when TeleMetrum is turned off. - It's impossible to stop the TeleDongle when it's in "p" mode, I have - to unplug the USB cable? Make sure you have tried to "escape out" of + It's impossible to stop the TeleDongle when it's in “p” mode, I have + to unplug the USB cable? Make sure you have tried to “escape out” of this mode. If this doesn't work the reboot procedure for the TeleDongle *is* to simply unplug it. 'cu' however will retain it's - outgoing buffer IF your "escape out" ('~~') does not work. + outgoing buffer IF your “escape out” ('~~') does not work. At this point using either 'ao-view' (or possibly 'cutemon') instead of 'cu' will 'clear' the issue and allow renewed communication. @@ -3156,11 +3156,11 @@ NAR #88757, TRA #12200 then the battery is being charged at a 'trickle' rate. - There are no "dit-dah-dah-dit" sound or lights like the manual mentions? - That's the "pad" mode. Weak batteries might be the problem. + There are no “dit-dah-dah-dit” sound or lights like the manual mentions? + That's the “pad” mode. Weak batteries might be the problem. It is also possible that the TeleMetrum is horizontal and the output - is instead a "dit-dit" meaning 'idle'. For TeleMini, it's possible that - it received a command packet which would have left it in "pad" mode. + is instead a “dit-dit” meaning 'idle'. For TeleMini, it's possible that + it received a command packet which would have left it in “pad” mode. How do I save flight data? @@ -3301,18 +3301,18 @@ NAR #88757, TRA #12200 Now might be a good time to take a break and read the rest of this - manual, particularly about the two "modes" that the altimeters + manual, particularly about the two “modes” that the altimeters can be placed in. TeleMetrum uses the position of the device when booting - up will determine whether the unit is in "pad" or "idle" mode. TeleMini - enters "idle" mode when it receives a command packet within the first 5 seconds - of being powered up, otherwise it enters "pad" mode. + up will determine whether the unit is in “pad” or “idle” mode. TeleMini + enters “idle” mode when it receives a command packet within the first 5 seconds + of being powered up, otherwise it enters “pad” mode. You can access an altimeter in idle mode from the TeleDongle's USB connection using the radio link by issuing a 'p' command to the TeleDongle. Practice connecting and disconnecting ('~~' while using 'cu') from the altimeter. If - you cannot escape out of the "p" command, (by using a '~~' when in + you cannot escape out of the “p” command, (by using a '~~' when in CU) then it is likely that your kernel has issues. Try a newer version. @@ -3322,7 +3322,7 @@ NAR #88757, TRA #12200 is in 'idle mode' and then place the rocket vertically on the launch pad, walk away and then issue a reboot command. The altimeter will reboot and start sending data - having changed to the "pad" mode. If the TeleDongle is not receiving + having changed to the “pad” mode. If the TeleDongle is not receiving this data, you can disconnect 'cu' from the TeleDongle using the procedures mentioned above and THEN connect to the TeleDongle from inside 'ao-view'. If this doesn't work, disconnect from the @@ -3492,8 +3492,8 @@ NAR #88757, TRA #12200 The +1g and -1g calibration points are included in each telemetry frame and are part of the header stored in onboard flash to be downloaded after flight. We always store and return raw ADC - samples for each sensor... so nothing is permanently "lost" or - "damaged" if the calibration is poor. + samples for each sensor... so nothing is permanently “lost” or + “damaged” if the calibration is poor. In the unlikely event an accel cal goes badly, it is possible -- cgit v1.2.3 From 8da565bbafa2925aa889cf9249497a709a814b7f Mon Sep 17 00:00:00 2001 From: Keith Packard Date: Mon, 25 Nov 2013 00:01:20 -0800 Subject: doc: Add telemetry enable and APRS interval config docs Also starts working on the pyro channel config window docs Signed-off-by: Keith Packard --- doc/altusmetrum.xsl | 48 ++++++++++++++++++++++++++++++++++++++++++------ 1 file changed, 42 insertions(+), 6 deletions(-) (limited to 'doc') diff --git a/doc/altusmetrum.xsl b/doc/altusmetrum.xsl index 0af2a5e8..ee809f08 100644 --- a/doc/altusmetrum.xsl +++ b/doc/altusmetrum.xsl @@ -1729,7 +1729,7 @@ NAR #88757, TRA #12200
Configure Altimeter - Select this button and then select either a TeleMetrum or + Select this button and then select either an altimeter or TeleDongle Device from the list provided. Selecting a TeleDongle device will use the radio link to configure a remote altimeter. @@ -1800,15 +1800,15 @@ NAR #88757, TRA #12200
Radio Frequency - This configures which of the configured frequencies to use for both + This configures which of the frequencies to use for both telemetry and packet command mode. Note that if you set this - value via packet command mode, you will have to reconfigure - the TeleDongle frequency before you will be able to use packet - command mode again. + value via packet command mode, the TeleDongle frequency will + also be automatically reconfigured to match so that + communication will continue afterwards.
- Radio Calibration + RF Calibration The radios in every Altus Metrum device are calibrated at the factory to ensure that they transmit and receive on the @@ -1819,6 +1819,25 @@ NAR #88757, TRA #12200 you must reprogram the unit completely.
+
+ Telemetry/RDF/APRS Enable + + Enables the radio for transmission during flight. When + disabled, the radio will not transmit anything during flight + at all. + +
+
+ APRS Interval + + How often to transmit GPS information via APRS. This option + is available on TeleMetrum v2 and TeleMega + boards. TeleMetrum v1 boards cannot transmit APRS + packets. Note that a single APRS packet takes nearly a full + second to transmit, so enabling this option will prevent + sending any other telemetry during that time. + +
Callsign @@ -1896,6 +1915,23 @@ NAR #88757, TRA #12200
+
+ Configure Pyro Channels + + This opens a separate window to configure the additional + pyro channels available on TeleMega. 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 fired. + + + + + + + + +
Configure AltosUI -- cgit v1.2.3 From 73b1a7e644e255558378ab66de6426a7dfd8a7dc Mon Sep 17 00:00:00 2001 From: Keith Packard Date: Mon, 25 Nov 2013 01:15:36 -0800 Subject: doc: Work on AltosUI Pyro config docs a bit more. Signed-off-by: Keith Packard --- doc/altusmetrum.xsl | 114 +++++++++++++++++++++++++++++++++++++++++++++++----- 1 file changed, 105 insertions(+), 9 deletions(-) (limited to 'doc') diff --git a/doc/altusmetrum.xsl b/doc/altusmetrum.xsl index ee809f08..0fb26e68 100644 --- a/doc/altusmetrum.xsl +++ b/doc/altusmetrum.xsl @@ -1919,18 +1919,109 @@ NAR #88757, TRA #12200 Configure Pyro Channels This opens a separate window to configure the additional - pyro channels available on TeleMega. 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 fired. + pyro channels available on TeleMega. 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 fired. - + Acceleration less than. + + + + + Acceleration greater than. + + + + + Speed less than. + + + + + Speed greater than. + + + + + Height less than. + + + + + Height greater than. + + + + + Angle from vertical less than. + + + + + Angle from vertical greater than. + + + + + Time since boost less than. + + + + + Time since boost greater than. + + + + + Ascending. This is exactly the same as setting a + condition for speed > 0. + + + + + Descending. This is exactly the same as setting a + condition for speed < 0. + + + + + After motor number. + + + + + Delay after other conditions. + + + + + Flight state before. + + + + + Flight state after. + + Select conditions and set the related value; the pyro + channel will be activated when all of the + conditions are met. Each pyro channel has a separate set of + configuration values, so you can use different values for + the same condition with different channels. + + + Once you have selected the appropriate configuration for all + of the necessary pyro channels, you can save the pyro + configuration along with the rest of the flight computer + configuration by pressing the 'Save' button in the main + Configure Flight Computer window. +
@@ -1995,9 +2086,10 @@ NAR #88757, TRA #12200 This switches between metric units (meters) and imperial units (feet and miles). This affects the display of values - use during flight monitoring, data graphing and all of the - voice announcements. It does not change the units used when - exporting to CSV files, those are always produced in metric units. + use during flight monitoring, configuration, data graphing + and all of the voice announcements. It does not change the + units used when exporting to CSV files, those are always + produced in metric units.
@@ -2205,7 +2297,11 @@ NAR #88757, TRA #12200 This brings up a dialog similar to the Monitor Flight UI, except it works with the altimeter in “idle” mode by sending query commands to discover the current state rather than - listening for telemetry packets. + listening for telemetry packets. Because this uses command + mode, it needs to have the TeleDongle and flight computer + callsigns match exactly. If you can receive telemetry, but + cannot manage to run Monitor Idle, then it's very likely that + your callsigns are different in some way.
-- cgit v1.2.3 From 473ae38ade0552c5ff3ca088b21345ed5dfad5d0 Mon Sep 17 00:00:00 2001 From: Keith Packard Date: Thu, 28 Nov 2013 15:21:26 -0800 Subject: doc: First pass for 1.3 finished; docs have most major sections updated. Final edits and corrections still required. Signed-off-by: Keith Packard --- doc/altusmetrum.xsl | 462 ++++++++++++++++++++++++++++++++++++++++++++-------- 1 file changed, 396 insertions(+), 66 deletions(-) (limited to 'doc') diff --git a/doc/altusmetrum.xsl b/doc/altusmetrum.xsl index 0fb26e68..302b8d60 100644 --- a/doc/altusmetrum.xsl +++ b/doc/altusmetrum.xsl @@ -2191,16 +2191,26 @@ NAR #88757, TRA #12200
Flash Image - This reprograms any Altus Metrum device by using a TeleMetrum - or TeleDongle as a programming dongle. Please read the - directions for flashing devices in the Updating Device - Firmware chapter below. + This reprograms Altus Metrum device with new + firmware. TeleMetrum v1.x, TeleDongle, TeleMini and TeleBT are + all reprogrammed by using another similar unit as a + programming dongle (pair programming). TeleMega, TeleMetrum v2 + and EasyMini are all programmed directly over their USB ports + (self programming). Please read the directions for flashing + devices in the Updating Device Firmware chapter below. - Once you have the programmer and target devices connected, - push the 'Flash Image' button. That will present a dialog box - listing all of the connected devices. Carefully select the - programmer device, not the device to be programmed. + For “self programming”, connect USB to the device to be + programmed and push the 'Flash Image' button. That will + present a dialog box listing all of the connected + devices. Carefully select the device to be programmed. + + + For “pair programming”, once you have the programmer and + target devices connected, push the 'Flash Image' button. That + will present a dialog box listing all of the connected + devices. Carefully select the programmer device, not the + device to be programmed. Next, select the image to flash to the device. These are named @@ -2221,10 +2231,10 @@ NAR #88757, TRA #12200 When programming is complete, the target device will - reboot. Note that if the target device is connected via USB, you - will have to unplug it and then plug it back in for the USB - connection to reset so that you can communicate with the device - again. + reboot. Note that if a pair programmed target device is + connected via USB, you will have to unplug it and then plug it + back in for the USB connection to reset so that you can + communicate with the device again.
@@ -2851,11 +2861,11 @@ NAR #88757, TRA #12200 Updating Device Firmware - The big concept to understand is that you have to use a - TeleDongle as a programmer to update a TeleMetrum or TeleMini, - and a TeleMetrum or other TeleDongle to program the TeleDongle - Due to limited memory resources in the cc1111, we don't support - programming directly over USB. + TeleMega, TeleMetrum v2 and EasMini are all programmed directly + over their USB connectors (self programming). TeleMetrum v1, TeleMini and + TeleDongle are all programmed by using another device as a + programmer (pair programming). It's important to recognize which + kind of devices you have before trying to reprogram them. You may wish to begin by ensuring you have current firmware images. @@ -2869,8 +2879,70 @@ NAR #88757, TRA #12200 We recommend updating the altimeter first, before updating TeleDongle. + + Self-programmable devices (TeleMega, TeleMetrum v2 and EasyMini) + are reprogrammed by connecting them to your computer over USB + + + The big concept to understand is that you have to use a + TeleMega, TeleMetrum or TeleDongle as a programmer to update a + pair programmed device. Due to limited memory resources in the + cc1111, we don't support programming directly over USB for these + devices. +
- Updating TeleMetrum Firmware + + Updating TeleMega, TeleMetrum v2 or EasyMini Firmware + + + + + Attach a battery and power switch to the target + device. Power up the device. + + + + + Using a Micro USB cable, connect the target device to your + computer's USB socket. + + + + + Run AltosUI, and select 'Flash Image' from the File menu. + + + + + Select the image you want to flash to the device, which + should have a name in the form + <product>-v<product-version>-<software-version>.ihx, such + as TeleMega-v1.0-1.3.0.ihx. + + + + + 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 device with new firmware, showing a progress bar. + + + + + Verify that the device is working by using the 'Configure + Altimeter' item to check over the configuration. + + + +
+
+ Updating TeleMetrum v1.x Firmware @@ -3148,7 +3220,141 @@ NAR #88757, TRA #12200 Hardware Specifications
- TeleMetrum Specifications + + TeleMega Specifications + + + + + Recording altimeter for model rocketry. + + + + + Supports dual deployment and four auxilary pyro channels (can initiate 6 events). + + + + + 70cm 40mW ham-band transceiver for telemetry down-link. + + + + + Barometric pressure sensor good to 100k feet MSL. + + + + + 1-axis high-g accelerometer for motor characterization, capable of + +/- 102g. + + + + + 9-axis IMU including integrated 3-axis accelerometer, + 3-axis gyroscope and 3-axis magnetometer. + + + + + On-board, integrated uBlox Max 7 GPS receiver with 5Hz update rate capability. + + + + + On-board 8 Megabyte non-volatile memory for flight data storage. + + + + + USB interface for battery charging, configuration, and data recovery. + + + + + Fully integrated support for Li-Po rechargeable batteries. + + + + + Uses Li-Po to fire e-matches, can be modified to support + optional separate pyro battery if needed. + + + + + 3.25 x 1.25 inch board designed to fit inside 38mm air-frame coupler tube. + + + +
+
+ + TeleMetrum v2 Specifications + + + + + Recording altimeter for model rocketry. + + + + + Supports dual deployment (can fire 2 ejection charges). + + + + + 70cm, 40mW ham-band transceiver for telemetry down-link. + + + + + Barometric pressure sensor good to 100k feet MSL. + + + + + 1-axis high-g accelerometer for motor characterization, capable of + +/- 102g. + + + + + On-board, integrated uBlox Max 7 GPS receiver with 5Hz update rate capability. + + + + + On-board 8 Megabyte non-volatile memory for flight data storage. + + + + + USB interface for battery charging, configuration, and data recovery. + + + + + Fully integrated support for Li-Po rechargeable batteries. + + + + + Uses Li-Po to fire e-matches, can be modified to support + optional separate pyro battery if needed. + + + + + 2.75 x 1 inch board designed to fit inside 29mm air-frame coupler tube. + + + +
+
+ TeleMetrum v1 Specifications @@ -3162,7 +3368,7 @@ NAR #88757, TRA #12200 - 70cm ham-band transceiver for telemetry down-link. + 70cm, 10mW ham-band transceiver for telemetry down-link. @@ -3210,7 +3416,9 @@ NAR #88757, TRA #12200
- TeleMini Specifications + + TeleMini v2.0 Specifications + @@ -3224,7 +3432,61 @@ NAR #88757, TRA #12200 - 70cm ham-band transceiver for telemetry down-link. + 70cm, 10mW ham-band transceiver for telemetry down-link. + + + + + Barometric pressure sensor good to 100k feet MSL. + + + + + On-board 1 megabyte non-volatile memory for flight data storage. + + + + + USB interface for configuration, and data recovery. + + + + + Support for Li-Po rechargeable batteries (using an + external charger), or any 3.7-15V external battery. + + + + + Uses Li-Po to fire e-matches, can be modified to support + optional separate pyro battery if needed. + + + + + 1.5 x .8 inch board designed to fit inside 24mm air-frame coupler tube. + + + +
+
+ + TeleMini v1.0 Specifications + + + + + Recording altimeter for model rocketry. + + + + + Supports dual deployment (can fire 2 ejection charges). + + + + + 70cm, 10mW ham-band transceiver for telemetry down-link. @@ -3260,6 +3522,55 @@ NAR #88757, TRA #12200
+
+ + EasyMini Specifications + + + + + Recording altimeter for model rocketry. + + + + + Supports dual deployment (can fire 2 ejection charges). + + + + + Barometric pressure sensor good to 100k feet MSL. + + + + + On-board 1 megabyte non-volatile memory for flight data storage. + + + + + USB interface for configuration, and data recovery. + + + + + Support for Li-Po rechargeable batteries (using an + external charger), or any 3.7-15V external battery. + + + + + Uses Li-Po to fire e-matches, can be modified to support + optional separate pyro battery if needed. + + + + + 1.5 x .8 inch board designed to fit inside 24mm air-frame coupler tube. + + + +
FAQ @@ -3515,6 +3826,18 @@ NAR #88757, TRA #12200 These images, when printed, provide precise templates for the mounting holes in Altus Metrum flight computers +
+ TeleMega template + + TeleMega has overall dimensions of 1.250 x 3.250 inches, and + the mounting holes are sized for use with 4-40 or M3 screws. + + + + + + +
TeleMetrum template @@ -3528,7 +3851,19 @@ NAR #88757, TRA #12200
- TeleMini template + TeleMini v2/EasyMini template + + TeleMini v2 and EasyMini have overall dimensions of 0.800 x 1.500 inches, and the + mounting holes are sized for use with 4-40 or M3 screws. + + + + + + +
+
+ TeleMini v1 template TeleMini has overall dimensions of 0.500 x 1.500 inches, and the mounting holes are sized for use with 2-56 or M2 screws. @@ -3543,18 +3878,19 @@ NAR #88757, TRA #12200 Calibration - There are only two calibrations required for a TeleMetrum board, and - only one for TeleDongle and TeleMini. All boards are shipped from - the factory pre-calibrated, but the procedures are documented here - in case they are ever needed. Re-calibration is not supported by - AltosUI, you must connect to the board with a serial terminal program - and interact directly with the on-board command interpreter to effect - calibration. + There are only two calibrations required for TeleMetrum and + TeleMega, and only one for TeleDongle, TeleMini and EasyMini. + All boards are shipped from the factory pre-calibrated, but + the procedures are documented here in case they are ever + needed. Re-calibration is not supported by AltosUI, you must + connect to the board with a serial terminal program and + interact directly with the on-board command interpreter to + effect calibration.
Radio Frequency - The radio frequency is synthesized from a clock based on the 48 MHz + The radio frequency is synthesized from a clock based on the crystal on the board. The actual frequency of this oscillator must be measured to generate a calibration constant. While our GFSK modulation @@ -3567,13 +3903,14 @@ NAR #88757, TRA #12200 should generally not be required. - To calibrate the radio frequency, connect the UHF antenna port to a - frequency counter, set the board to 434.550MHz, and use the 'C' - command in the on-board command interpreter to generate a CW - carrier. For TeleMetrum, this is best done over USB. For TeleMini, - note that the only way to escape the 'C' command is via power cycle - since the board will no longer be listening for commands once it - starts generating a CW carrier. + To calibrate the radio frequency, connect the UHF antenna + port to a frequency counter, set the board to 434.550MHz, + and use the 'C' command in the on-board command interpreter + to generate a CW carrier. For USB-enabled boards, this is + best done over USB. For TeleMini v1, note that the only way + to escape the 'C' command is via power cycle since the board + will no longer be listening for commands once it starts + generating a CW carrier. Wait for the transmitter temperature to stabilize and the frequency @@ -3584,7 +3921,7 @@ NAR #88757, TRA #12200 command. Testing with the 'C' command again should show a carrier within a few tens of Hertz of the intended frequency. As with all 'c' sub-commands, follow this with a 'c w' to write the - change to the parameter block in the on-board DataFlash chip. + change to the parameter block in the on-board storage chip. Note that any time you re-do the radio frequency calibration, the @@ -3594,21 +3931,13 @@ NAR #88757, TRA #12200
- TeleMetrum Accelerometer + TeleMetrum and TeleMega Accelerometers - The TeleMetrum accelerometer we use has its own 5 volt power - supply and - the output must be passed through a resistive voltage divider to match - the input of our 3.3 volt ADC. This means that unlike the barometric - sensor, the output of the acceleration sensor is not ratio-metric to - the ADC converter, and calibration is required. Explicitly - calibrating the accelerometers also allows us to load any device - from a Freescale family that includes at least +/- 40g, 50g, 100g, - and 200g parts. Using gravity, - a simple 2-point calibration yields acceptable results capturing both - the different sensitivities and ranges of the different accelerometer - parts and any variation in power supply voltages or resistor values - in the divider network. + While barometric sensors are factory-calibrated, + accelerometers are not, and so each must be calibrated once + installed in a flight computer. Explicitly calibrating the + accelerometers also allows us to load any compatible device. + We perform a two-point calibration using gravity. To calibrate the acceleration sensor, use the 'c a 0' command. You @@ -3629,19 +3958,20 @@ NAR #88757, TRA #12200 In the unlikely event an accel cal goes badly, it is possible - that TeleMetrum may always come up in 'pad mode' and as such not be - listening to either the USB or radio link. If that happens, - there is a special hook in the firmware to force the board back - in to 'idle mode' so you can re-do the cal. To use this hook, you - just need to ground the SPI clock pin at power-on. This pin is - available as pin 2 on the 8-pin companion connector, and pin 1 is - ground. So either carefully install a fine-gauge wire jumper - between the two pins closest to the index hole end of the 8-pin - connector, or plug in the programming cable to the 8-pin connector - and use a small screwdriver or similar to short the two pins closest - to the index post on the 4-pin end of the programming cable, and - power up the board. It should come up in 'idle mode' (two beeps), - allowing a re-cal. + that TeleMetrum or TeleMega may always come up in 'pad mode' + and as such not be listening to either the USB or radio link. + If that happens, there is a special hook in the firmware to + force the board back in to 'idle mode' so you can re-do the + cal. To use this hook, you just need to ground the SPI clock + pin at power-on. This pin is available as pin 2 on the 8-pin + companion connector, and pin 1 is ground. So either + carefully install a fine-gauge wire jumper between the two + pins closest to the index hole end of the 8-pin connector, or + plug in the programming cable to the 8-pin connector and use + a small screwdriver or similar to short the two pins closest + to the index post on the 4-pin end of the programming cable, + and power up the board. It should come up in 'idle mode' + (two beeps), allowing a re-cal.
-- cgit v1.2.3 From 54f7888dc65ffc27c6ee5ef93953bd9b8fc029ed Mon Sep 17 00:00:00 2001 From: Keith Packard Date: Tue, 10 Dec 2013 00:00:31 -0800 Subject: doc: More altusmetrum.xsl updates for 1.3 Spell checking even Signed-off-by: Keith Packard --- doc/altusmetrum.xsl | 432 ++++++++++++++++++++++++++-------------------------- 1 file changed, 213 insertions(+), 219 deletions(-) (limited to 'doc') diff --git a/doc/altusmetrum.xsl b/doc/altusmetrum.xsl index 302b8d60..eed6b7d7 100644 --- a/doc/altusmetrum.xsl +++ b/doc/altusmetrum.xsl @@ -104,7 +104,7 @@ - Acknowledgements + Acknowledgments Thanks to Bob Finch, W9YA, NAR 12965, TRA 12350 for writing “The Mere-Mortals Quick Start/Usage Guide to the Altus Metrum Starter @@ -481,7 +481,7 @@ NAR #88757, TRA #12200 ½ inch (1.27cm) 1½ inch (3.81cm) - 18mm aiframe + 18mm airframe TeleMini v2.0 @@ -1286,7 +1286,7 @@ NAR #88757, TRA #12200 - Main. The rocket is still descending, and is blow + Main. The rocket is still descending, and is below the Main altitude @@ -1300,9 +1300,9 @@ NAR #88757, TRA #12200 You can select a state to limit when the pyro channel may activate; note that the check is based on when the - rocket transitions *into* the state, and so checking for - 'greater than Boost' means that the rocket is currently - in boost state. + rocket transitions into the state, and so checking for + “greater than Boost” means that the rocket is currently + in boost or some later state. When a motor burns out, the rocket enters either Fast or @@ -1410,64 +1410,82 @@ NAR #88757, TRA #12200 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.7V 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 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 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. - - - + + + 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. + + + + The Launchpad tab also shows the computed launch pad position @@ -1662,15 +1680,48 @@ NAR #88757, TRA #12200 flash memory. - Once a flight record is selected, a window with four tabs is - opened. The first tab contains a graph with acceleration - (blue), velocity (green) and altitude (red) of the flight, - measured in metric units. The apogee(yellow) and main(magenta) - igniter voltages are also displayed; high voltages indicate - continuity, low voltages indicate open circuits. The second - tab lets you configure which data to show in the graph. The - third contains some basic flight statistics while the fourth - has a map with the ground track of the flight displayed. + Once a flight record is selected, a window with multiple tabs is + opened. + + + Flight Graph + + + By default, the graph contains acceleration (blue), + velocity (green) and altitude (red). + + + + + Configure Graph + + + This selects which graph elements to show, and, at the + very bottom, lets you switch between metric and + imperial units + + + + + Flight Statistics + + + Shows overall data computed from the 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. + + + + The graph can be zoomed into a particular area by clicking and @@ -1922,92 +1973,10 @@ NAR #88757, TRA #12200 pyro channels available on TeleMega. 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 fired. + test for the pyro channel to be fired. See the Pyro Channels + section in the System Operation chapter above for a + description of these parameters. - - - - Acceleration less than. - - - - - Acceleration greater than. - - - - - Speed less than. - - - - - Speed greater than. - - - - - Height less than. - - - - - Height greater than. - - - - - Angle from vertical less than. - - - - - Angle from vertical greater than. - - - - - Time since boost less than. - - - - - Time since boost greater than. - - - - - Ascending. This is exactly the same as setting a - condition for speed > 0. - - - - - Descending. This is exactly the same as setting a - condition for speed < 0. - - - - - After motor number. - - - - - Delay after other conditions. - - - - - Flight state before. - - - - - Flight state after. - - - Select conditions and set the related value; the pyro channel will be activated when all of the @@ -2382,64 +2351,82 @@ NAR #88757, TRA #12200 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.7V 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 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 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. - - - + + + 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. + + + + The Launchpad tab also shows the computed launch pad position @@ -2526,7 +2513,8 @@ NAR #88757, TRA #12200 if the rocket is hiding in sage brush or a tree, or if the last GPS position doesn't get you close enough because the rocket dropped into a canyon, or the wind is blowing it across a dry lake bed, or something like that... Keith - and Bdale both currently own and use the Yaesu VX-7R at launches. + currently uses a Yaesu VX-7R, Bdale has a Baofung UV-5R + which isn't as nice, but was a whole lot cheaper. So, to recap, on the ground the hardware you'll need includes: @@ -2861,7 +2849,7 @@ NAR #88757, TRA #12200 Updating Device Firmware - TeleMega, TeleMetrum v2 and EasMini are all programmed directly + TeleMega, TeleMetrum v2 and EasyMini are all programmed directly over their USB connectors (self programming). TeleMetrum v1, TeleMini and TeleDongle are all programmed by using another device as a programmer (pair programming). It's important to recognize which @@ -2912,6 +2900,11 @@ NAR #88757, TRA #12200 Run AltosUI, and select 'Flash Image' from the File menu. + + + Select the target device in the Device Selection dialog. + + Select the image you want to flash to the device, which @@ -3231,7 +3224,8 @@ NAR #88757, TRA #12200 - Supports dual deployment and four auxilary pyro channels (can initiate 6 events). + Supports dual deployment and four auxiliary pyro channels + (a total of 6 events). -- cgit v1.2.3 From 8bb6dd75a602792936d623713fb009fea25ef491 Mon Sep 17 00:00:00 2001 From: Keith Packard Date: Mon, 16 Dec 2013 21:21:24 -0800 Subject: Clean up reflashing section, include section on self-flash recovery Signed-off-by: Keith Packard --- doc/altusmetrum.xsl | 73 ++++++++++++++++++++++++++++++++++++++++++++++++----- 1 file changed, 66 insertions(+), 7 deletions(-) (limited to 'doc') diff --git a/doc/altusmetrum.xsl b/doc/altusmetrum.xsl index eed6b7d7..0430bc94 100644 --- a/doc/altusmetrum.xsl +++ b/doc/altusmetrum.xsl @@ -2871,13 +2871,6 @@ NAR #88757, TRA #12200 Self-programmable devices (TeleMega, TeleMetrum v2 and EasyMini) are reprogrammed by connecting them to your computer over USB - - The big concept to understand is that you have to use a - TeleMega, TeleMetrum or TeleDongle as a programmer to update a - pair programmed device. Due to limited memory resources in the - cc1111, we don't support programming directly over USB for these - devices. -
Updating TeleMega, TeleMetrum v2 or EasyMini Firmware @@ -2933,6 +2926,72 @@ NAR #88757, TRA #12200 </para> </listitem> </orderedlist> + <section> + <title>Recovering From Self-Flashing Failure + + If the firmware loading fails, it can leave the device + unable to boot. Not to worry, you can force the device to + start the boot loader instead, which will let you try to + flash the device again. + + + On each device, connecting two pins from one of the exposed + connectors will force the boot loader to start, even if the + regular operating system has been corrupted in some way. + + + + TeleMega + + + Connect pin 6 and pin 1 of the companion connector. Pin 1 + can be identified by the square pad around it, and then + the pins could sequentially across the board. Be very + careful to not short pin 8 to + anything as that is connected directly to the battery. Pin + 7 carries 3.3V and the board will crash if that is + connected to pin 1, but shouldn't damage the board. + + + + + TeleMetrum v2 + + + Connect pin 6 and pin 1 of the companion connector. Pin 1 + can be identified by the square pad around it, and then + the pins could sequentially across the board. Be very + careful to not short pin 8 to + anything as that is connected directly to the battery. Pin + 7 carries 3.3V and the board will crash if that is + connected to pin 1, but shouldn't damage the board. + + + + + EasyMini + + + Connect pin 6 and pin 1 of the debug connector, which is + the six holes next to the beeper. Pin 1 can be identified + by the square pad around it, and then the pins could + sequentially across the board, making Pin 6 the one on the + other end of the row. + + + + +
+
+
+ Pair Programming + + The big concept to understand is that you have to use a + TeleMega, TeleMetrum or TeleDongle as a programmer to update a + pair programmed device. Due to limited memory resources in the + cc1111, we don't support programming directly over USB for these + devices. +
Updating TeleMetrum v1.x Firmware -- cgit v1.2.3 From 7acd0cf17c5ca7a00893f35c7fe9c657389070e0 Mon Sep 17 00:00:00 2001 From: Keith Packard Date: Tue, 17 Dec 2013 10:33:29 -0800 Subject: doc: Convert several more itemizedlists to variablelists When defining a term, use variablelist to pull the term out to the left. Signed-off-by: Keith Packard --- doc/altusmetrum.xsl | 220 ++++++++++++++++++++++++++++++---------------------- 1 file changed, 128 insertions(+), 92 deletions(-) (limited to 'doc') diff --git a/doc/altusmetrum.xsl b/doc/altusmetrum.xsl index 0430bc94..3022b8e3 100644 --- a/doc/altusmetrum.xsl +++ b/doc/altusmetrum.xsl @@ -1793,35 +1793,47 @@ NAR #88757, TRA #12200 At the bottom of the dialog, there are four buttons: - - - - Save. This writes any changes to the - configuration parameter block in flash memory. If you don't - press this button, any changes you make will be lost. - - - - - Reset. This resets the dialog to the most recently saved values, - erasing any changes you have made. - - - - - Reboot. This reboots the device. Use this to - switch from idle to pad mode by rebooting once the rocket is - oriented for flight, or to confirm changes you think you saved - are really saved. - - - - - Close. This closes the dialog. Any unsaved changes will be - lost. - - - + + + Save + + + This writes any changes to the + configuration parameter block in flash memory. If you don't + press this button, any changes you make will be lost. + + + + + Reset + + + This resets the dialog to the most recently saved values, + erasing any changes you have made. + + + + + Reboot + + + This reboots the device. Use this to + switch from idle to pad mode by rebooting once the rocket is + oriented for flight, or to confirm changes you think you saved + are really saved. + + + + + Close + + + This closes the dialog. Any unsaved changes will be + lost. + + + + The rest of the dialog contains the parameters to be configured. @@ -1913,32 +1925,41 @@ NAR #88757, TRA #12200 computers. This configuration parameter allows the two channels to be used in different configurations. - - - - Dual Deploy. This is the usual mode of operation; the - 'apogee' channel is fired at apogee and the 'main' - channel at the height above ground specified by the - 'Main Deploy Altitude' during descent. - - - - - Redundant Apogee. This fires both channels at - apogee, the 'apogee' channel first followed after a two second - delay by the 'main' channel. - - - - - Redundant Main. This fires both channels at the - height above ground specified by the Main Deploy - Altitude setting during descent. The 'apogee' - channel is fired first, followed after a two second - delay by the 'main' channel. - - - + + + Dual Deploy + + + This is the usual mode of operation; the + 'apogee' channel is fired at apogee and the 'main' + channel at the height above ground specified by the + 'Main Deploy Altitude' during descent. + + + + + Redundant Apogee + + + This fires both channels at + apogee, the 'apogee' channel first followed after a two second + delay by the 'main' channel. + + + + + Redundant Main + + + This fires both channels at the + height above ground specified by the Main Deploy + Altitude setting during descent. The 'apogee' + channel is fired first, followed after a two second + delay by the 'main' channel. + + + +
Pad Orientation @@ -1949,22 +1970,28 @@ NAR #88757, TRA #12200 parameter allows that default to be changed, permitting the board to be mounted with the antenna pointing aft instead. - - - - Antenna Up. In this mode, the antenna end of the - TeleMetrum board must point forward, in line with the - expected flight path. - - - - - Antenna Down. In this mode, the antenna end of the - TeleMetrum board must point aft, in line with the - expected flight path. - - - + + + Antenna Up + + + In this mode, the antenna end of the + TeleMetrum board must point forward, in line with the + expected flight path. + + + + + Antenna Down + + + In this mode, the antenna end of the + TeleMetrum board must point aft, in line with the + expected flight path. + + + +
Configure Pyro Channels @@ -2111,27 +2138,36 @@ NAR #88757, TRA #12200 At the bottom of the dialog, there are three buttons: - - - - Save. This writes any changes to the - local Java preferences file. If you don't - press this button, any changes you make will be lost. - - - - - Reset. This resets the dialog to the most recently saved values, - erasing any changes you have made. - - - - - Close. This closes the dialog. Any unsaved changes will be - lost. - - - + + + Save + + + This writes any changes to the + local Java preferences file. If you don't + press this button, any changes you make will be lost. + + + + + Reset + + + This resets the dialog to the most recently saved values, + erasing any changes you have made. + + + + + Close + + + This closes the dialog. Any unsaved changes will be + lost. + + + + The rest of the dialog contains the parameters to be configured. -- cgit v1.2.3 From 9d8da4ef325171960e16fc027c6039cb63eae942 Mon Sep 17 00:00:00 2001 From: Keith Packard Date: Tue, 17 Dec 2013 11:19:54 -0800 Subject: Keep tables together on a page --- doc/altusmetrum.xsl | 3 +++ doc/xorg-fo.xsl | 3 +-- 2 files changed, 4 insertions(+), 2 deletions(-) (limited to 'doc') diff --git a/doc/altusmetrum.xsl b/doc/altusmetrum.xsl index 3022b8e3..659ea2f9 100644 --- a/doc/altusmetrum.xsl +++ b/doc/altusmetrum.xsl @@ -329,6 +329,7 @@ NAR #88757, TRA #12200 Altus Metrum Electronics + @@ -436,6 +437,7 @@ NAR #88757, TRA #12200
Altus Metrum Boards + @@ -612,6 +614,7 @@ NAR #88757, TRA #12200
Data Storage on Altus Metrum altimeters + diff --git a/doc/xorg-fo.xsl b/doc/xorg-fo.xsl index a02ad1ea..075a2d98 100644 --- a/doc/xorg-fo.xsl +++ b/doc/xorg-fo.xsl @@ -17,7 +17,7 @@ - + @@ -98,7 +98,6 @@ DejaVu Serif serif,Symbol,AR PL UMing CN,AR PL ShanHeiSun Uni,GNU Unifont - -- cgit v1.2.3 From dffbdd93d7a86a12d83a412de37dfd2a5f063995 Mon Sep 17 00:00:00 2001 From: Keith Packard Date: Tue, 17 Dec 2013 11:38:46 -0800 Subject: doc: Add product pictures to manual Signed-off-by: Keith Packard --- doc/altusmetrum.xsl | 25 +++++++++++++++++++++++++ doc/easymini-top.jpg | Bin 0 -> 680720 bytes doc/telemega-v1.0-top.jpg | Bin 0 -> 3212941 bytes doc/telemetrum-v1.1-thside.jpg | Bin 0 -> 1619135 bytes doc/telemini-v1-top.jpg | Bin 0 -> 1006003 bytes doc/telemini-v2-top.jpg | Bin 0 -> 579692 bytes 6 files changed, 25 insertions(+) create mode 100644 doc/easymini-top.jpg create mode 100644 doc/telemega-v1.0-top.jpg create mode 100644 doc/telemetrum-v1.1-thside.jpg create mode 100644 doc/telemini-v1-top.jpg create mode 100644 doc/telemini-v2-top.jpg (limited to 'doc') diff --git a/doc/altusmetrum.xsl b/doc/altusmetrum.xsl index 659ea2f9..61451f41 100644 --- a/doc/altusmetrum.xsl +++ b/doc/altusmetrum.xsl @@ -546,6 +546,11 @@ NAR #88757, TRA #12200
TeleMetrum + + + + + TeleMetrum is a 1 inch by 2¾ inch circuit board. It was designed to fit inside coupler for 29mm air-frame tubing, but using it in a tube that @@ -561,6 +566,11 @@ NAR #88757, TRA #12200
TeleMini + + + + + TeleMini v1.0 is ½ inches by 1½ inches. It was designed to fit inside an 18mm air-frame tube, but using it in @@ -575,6 +585,11 @@ NAR #88757, TRA #12200 the board, meaning an ideal “simple” avionics bay for TeleMini should have at least 9 inches of interior length. + + + + + TeleMini v2.0 is 0.8 inches by 1½ inches. It adds more on-board data logging memory, a built-in USB connector and @@ -585,6 +600,11 @@ NAR #88757, TRA #12200
EasyMini + + + + + EasyMini is built on a 0.8 inch by 1½ inch circuit board. It's designed to fit in a 24mm coupler tube. The connectors and @@ -594,6 +614,11 @@ NAR #88757, TRA #12200
TeleMega + + + + + TeleMega is a 1¼ inch by 3¼ inch circuit board. It was designed to easily fit in a 38mm coupler. Like TeleMetrum, diff --git a/doc/easymini-top.jpg b/doc/easymini-top.jpg new file mode 100644 index 00000000..2b9e0a37 Binary files /dev/null and b/doc/easymini-top.jpg differ diff --git a/doc/telemega-v1.0-top.jpg b/doc/telemega-v1.0-top.jpg new file mode 100644 index 00000000..709d59f1 Binary files /dev/null and b/doc/telemega-v1.0-top.jpg differ diff --git a/doc/telemetrum-v1.1-thside.jpg b/doc/telemetrum-v1.1-thside.jpg new file mode 100644 index 00000000..2ffbdbd8 Binary files /dev/null and b/doc/telemetrum-v1.1-thside.jpg differ diff --git a/doc/telemini-v1-top.jpg b/doc/telemini-v1-top.jpg new file mode 100644 index 00000000..f79714c4 Binary files /dev/null and b/doc/telemini-v1-top.jpg differ diff --git a/doc/telemini-v2-top.jpg b/doc/telemini-v2-top.jpg new file mode 100644 index 00000000..bc8ae45b Binary files /dev/null and b/doc/telemini-v2-top.jpg differ -- cgit v1.2.3 From d5d6d10ceb724081c7cf89a3885d7e6c3da14604 Mon Sep 17 00:00:00 2001 From: Bdale Garbee Date: Tue, 17 Dec 2013 14:08:12 -0700 Subject: capture my changes so far --- doc/altusmetrum.xsl | 145 +++++++++++++++++++++++++++------------------------- 1 file changed, 75 insertions(+), 70 deletions(-) (limited to 'doc') diff --git a/doc/altusmetrum.xsl b/doc/altusmetrum.xsl index 0430bc94..3e6b4025 100644 --- a/doc/altusmetrum.xsl +++ b/doc/altusmetrum.xsl @@ -180,8 +180,8 @@ NAR #88757, TRA #12200 For a slightly more portable ground station experience that also provides direct rocket recovery support, TeleBT offers flight - monitoring and data logging using a Bluetooth connection between - the receiver and an Android device that has the Altos Droid + monitoring and data logging using a Bluetooth™ connection between + the receiver and an Android device that has the AltosDroid application installed from the Google Play store. @@ -207,7 +207,7 @@ NAR #88757, TRA #12200 On TeleMetrum v1 boards, when the GPS chip is initially searching for satellites, TeleMetrum will consume more current - than it can pull from the USB port, so the battery must be + than it pulls from the USB port, so the battery must be attached in order to get satellite lock. Once GPS is locked, the current consumption goes back down enough to enable charging while running. So it's a good idea to fully charge the battery @@ -238,7 +238,7 @@ NAR #88757, TRA #12200 and EasyMini, anything supplying between 4 and 12 volts should work fine (like a standard 9V battery), but if you are planning to fire pyro charges, ground testing is required to verify that - the battery supplies enough current. + the battery supplies enough current to fire your chosen e-matches. The other active device in the starter kit is the TeleDongle USB to @@ -247,13 +247,13 @@ NAR #88757, TRA #12200 driver information that is part of the AltOS download to know that the existing USB modem driver will work. We therefore recommend installing our software before plugging in TeleDongle if you are using a Windows - computer. If you are using Linux and are having problems, try moving - to a fresher kernel (2.6.33 or newer), as the USB serial driver had - ugly bugs in some earlier versions. + computer. If you are using an older version of Linux and are having + problems, try moving to a fresher kernel (2.6.33 or newer). - Next you should obtain and install the AltOS software. These - include the AltosUI ground station program, current firmware + Next you should obtain and install the AltOS software. The AltOS + distribution includes the AltosUI ground station program, current + firmware images for all of the hardware, and a number of standalone utilities that are rarely needed. Pre-built binary packages are available for Linux, Microsoft Windows, and recent MacOSX @@ -262,9 +262,9 @@ NAR #88757, TRA #12200 . - If you're using a TeleBT instead of the TeleDongle, you'll want - to go install the Altos Droid application from the Google Play - store. You don't need a data plan to use Altos Droid, but + If you're using a TeleBT instead of the TeleDongle, you'll want to + install the AltosDroid application from the Google Play store on an + Android device. You don't need a data plan to use AltosDroid, but without network access, the Map view will be less useful as it won't contain any map data. You can also use TeleBT connected over USB with your laptop computer; it acts exactly like a @@ -297,9 +297,9 @@ NAR #88757, TRA #12200 sensitive to sunlight. In normal mounting situations, the baro sensor and all of the other surface mount components are “down” towards whatever the underlying mounting surface is, so - this is not normally a problem. Please consider this, though, when - designing an installation, for example, in an air-frame with a - see-through plastic payload bay. It is particularly important to + this is not normally a problem. Please consider this when designing an + installation in an air-frame with a see-through plastic payload bay. It + is particularly important to consider this with TeleMini v1.0, both because the baro sensor is on the “top” of the board, and because many model rockets with payload bays use clear plastic for the payload bay! Replacing these with an opaque @@ -481,7 +481,7 @@ NAR #88757, TRA #12200 ½ inch (1.27cm) 1½ inch (3.81cm) - 18mm airframe + 18mm coupler TeleMini v2.0 @@ -586,8 +586,8 @@ NAR #88757, TRA #12200 EasyMini is built on a 0.8 inch by 1½ inch circuit board. It's designed to fit in a 24mm coupler tube. The connectors and - screw terminals match TeleMini, so you can swap an EasyMini - with a TeleMini. + screw terminals match TeleMini v2.0, so you can easily swap between + EasyMini and TeleMini.
@@ -720,7 +720,7 @@ NAR #88757, TRA #12200 apogee and main ejection charges. All Altus Metrum products are designed for use with single-cell batteries with 3.7 volts nominal. TeleMini v2.0 and EasyMini may also be used with other - batteries as long as they supply between 4 and 12 volts. + batteries as long as they supply between 4 and 12 volts. The battery connectors are a standard 2-pin JST connector and @@ -762,8 +762,8 @@ NAR #88757, TRA #12200 adequate. However, if you are installing in a carbon-fiber or metal electronics bay which is opaque to RF signals, you may need to use off-board external antennas instead. In this case, you can - order an altimeter with an SMA connector for the UHF antenna - connection, and, on TeleMetrum v1, you can unplug the integrated GPS + replace the stock UHF antenna wire with an edge-launched SMA connector, + and, on TeleMetrum v1, you can unplug the integrated GPS antenna and select an appropriate off-board GPS antenna with cable terminating in a U.FL connector. @@ -777,10 +777,11 @@ NAR #88757, TRA #12200 The AltOS firmware build for the altimeters has two fundamental modes, “idle” and “flight”. Which of these modes the firmware operates in is determined at start up time. For - TeleMetrum, the mode is controlled by the orientation of the + TeleMetrum and TeleMega, 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 - TeleMetrum assumes it's on a rail or rod being prepared for + the flight computer assumes it's on a rail or rod being prepared for launch, so the firmware chooses flight mode. However, if the rocket is more or less horizontal, the firmware instead enters idle mode. Since TeleMini v2.0 and EasyMini don't have an @@ -1012,7 +1013,7 @@ NAR #88757, TRA #12200
Radio Link - The chip our boards are based on incorporates an RF transceiver, but + Our flight computers all incorporate an RF transceiver, but it's not a full duplex system... each end can only be transmitting or receiving at any given moment. So we had to decide how to manage the link. @@ -1048,7 +1049,7 @@ NAR #88757, TRA #12200 performance in higher altitude flights! - TeleMetrum v2.0 and TeleMega can send APRS if desired, the + 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 @@ -1123,6 +1124,11 @@ NAR #88757, TRA #12200 the available storage, future flights will not get logged until you erase some of the stored ones. + + Even though our flight computers (except TeleMini v1.0) can store + multiple flights, we strongly recommend downloading and saving + flight data after each flight. +
Ignite Mode @@ -1130,9 +1136,8 @@ NAR #88757, TRA #12200 Instead of firing one charge at apogee and another charge at a fixed height above the ground, you can configure the altimeter to fire both at apogee or both during - descent. This was added to support an airframe that has two - altimeters, one in the fin can and one in the - nose. + descent. This was added to support an airframe Bdale designed that + had two altimeters, one in the fin can and one in the nose. Providing the ability to use both igniters for apogee or @@ -1156,7 +1161,7 @@ NAR #88757, TRA #12200
- Pyro Channels + Configurable Pyro Channels In addition to the usual Apogee and Main pyro channels, TeleMega has four additional channels that can be configured @@ -1205,7 +1210,7 @@ NAR #88757, TRA #12200 system. Because this value is computed by integrating rate gyros, it gets progressively less accurate as the flight goes on. It should have an accumulated error of - less than .2°/second (after 10 seconds of flight, the + less than 0.2°/second (after 10 seconds of flight, the error should be less than 2°). @@ -1324,8 +1329,8 @@ NAR #88757, TRA #12200 interacting with the Altus Metrum product family. AltosUI can monitor telemetry data, configure devices and many other tasks. The primary interface window provides a selection of - buttons, one for each major activity in the system. This manual - is split into chapters, each of which documents one of the tasks + buttons, one for each major activity in the system. This chapter + is split into sections, each of which documents one of the tasks provided from the top-level toolbar.
@@ -1415,8 +1420,8 @@ NAR #88757, TRA #12200 Battery Voltage - This indicates whether the Li-Po battery - powering the TeleMetrum has sufficient charge to last for + This indicates whether the Li-Po battery powering the + flight computer has sufficient charge to last for the duration of the flight. A value of more than 3.8V is required for a 'GO' status. @@ -1454,13 +1459,15 @@ NAR #88757, TRA #12200 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 + left. Most of our flight computers can store multiple + flights, depending on the configured maximum flight log + size. TeleMini v1.0 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. + ejection charges at the proper times even if the flight + data storage is full. @@ -1507,7 +1514,7 @@ NAR #88757, TRA #12200 flight. - The current latitude and longitude reported by the TeleMetrum GPS are + The current latitude and longitude reported by the GPS are also shown. Note that under high acceleration, these values may not get updated as the GPS receiver loses position fix. Once the rocket starts coasting, the receiver should @@ -1535,7 +1542,7 @@ NAR #88757, TRA #12200 be below 10m/s when under the main parachute in a dual-deploy flight. - For TeleMetrum altimeters, you can locate the rocket in the + With GPS-equipped flight computers, you can locate the rocket in the sky using the elevation and bearing information to figure out where to look. Elevation is in degrees above the horizon. Bearing is reported in degrees relative to true @@ -1572,7 +1579,7 @@ NAR #88757, TRA #12200 unit and have that compute a track to the landing location. - Both TeleMini and TeleMetrum will continue to transmit RDF + Our flight computers will continue to transmit RDF tones after landing, allowing you to locate the rocket by following the radio signal if necessary. You may need to get away from the clutter of the flight line, or even get up on @@ -1583,7 +1590,7 @@ NAR #88757, TRA #12200 during the flight are displayed for your admiring observers. The accuracy of these immediate values depends on the quality of your radio link and how many packets were received. - Recovering the on-board data after flight will likely yield + Recovering the on-board data after flight may yield more precise results. @@ -1627,16 +1634,14 @@ NAR #88757, TRA #12200 system can handle, and is not subject to radio drop-outs. As such, it provides a more complete and precise record of the flight. The 'Save Flight Data' button allows you to read the - flash memory and write it to disk. As TeleMini has only a barometer, it - records data at the same rate as the telemetry signal, but there will be - no data lost due to telemetry drop-outs. + flash memory and write it to disk. Clicking on the 'Save Flight Data' button brings up a list of - connected TeleMetrum and TeleDongle devices. If you select a - TeleMetrum device, the flight data will be downloaded from that + connected flight computers and TeleDongle devices. If you select a + flight computer, the flight data will be downloaded from that device directly. If you select a TeleDongle device, flight data - will be downloaded from an altimeter over radio link via the + will be downloaded from a flight computer over radio link via the specified TeleDongle. See the chapter on Controlling An Altimeter Over The Radio Link for more information. @@ -1742,10 +1747,10 @@ NAR #88757, TRA #12200 This tool takes the raw data files and makes them available for external analysis. When you select this button, you are prompted to - select a flight - data file (either .eeprom or .telem will do, remember that - .eeprom files contain higher resolution and more continuous - data). Next, a second dialog appears which is used to select + select a flight data file, which can be either a .eeprom or .telem. + The .eeprom files contain higher resolution and more continuous data, + while .telem files contain receiver signal strength information. + Next, a second dialog appears which is used to select where to write the resulting file. It has a selector to choose between CSV and KML file formats. @@ -1943,9 +1948,9 @@ NAR #88757, TRA #12200
Pad Orientation - Because it includes an accelerometer, TeleMetrum and + Because they include accelerometers, TeleMetrum and TeleMega are sensitive to the orientation of the board. By - default, it expects the antenna end to point forward. This + default, they expect the antenna end to point forward. This parameter allows that default to be changed, permitting the board to be mounted with the antenna pointing aft instead. @@ -1953,14 +1958,14 @@ NAR #88757, TRA #12200 Antenna Up. In this mode, the antenna end of the - TeleMetrum board must point forward, in line with the + flight computer must point forward, in line with the expected flight path. Antenna Down. In this mode, the antenna end of the - TeleMetrum board must point aft, in line with the + flight computer must point aft, in line with the expected flight path. @@ -2160,7 +2165,7 @@ NAR #88757, TRA #12200
Flash Image - This reprograms Altus Metrum device with new + This reprograms Altus Metrum devices with new firmware. TeleMetrum v1.x, TeleDongle, TeleMini and TeleBT are all reprogrammed by using another similar unit as a programming dongle (pair programming). TeleMega, TeleMetrum v2 @@ -2209,17 +2214,17 @@ NAR #88757, TRA #12200
Fire Igniter - This activates the igniter circuits in TeleMetrum to help test - recovery systems deployment. Because this command can operate + This activates the igniter circuits in the flight computer to help + test recovery systems deployment. Because this command can operate over the Packet Command Link, you can prepare the rocket as for flight and then test the recovery system without needing to snake wires inside the air-frame. Selecting the 'Fire Igniter' button brings up the usual device - selection dialog. Pick the desired TeleDongle or TeleMetrum - device. This brings up another window which shows the current - continuity test status for both apogee and main charges. + selection dialog. Pick the desired device. This brings up another + window which shows the current continuity test status for both + apogee and main charges. Next, select the desired igniter to fire. This will enable the @@ -2256,8 +2261,8 @@ NAR #88757, TRA #12200 There's a drop-down menu of launch sites we know about; if your favorites aren't there, please let us know the lat/lon and name of the site. The contents of this list are actually - downloaded at run-time, so as new sites are sent in, they'll - get automatically added to this list. + downloaded from our server at run-time, so as new sites are sent + in, they'll get automatically added to this list. If the launch site isn't in the list, you can manually enter the lat/lon values @@ -2289,7 +2294,7 @@ NAR #88757, TRA #12200 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™. Altos Droid monitors + to a TeleBT receiver over Bluetooth™. 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. @@ -2336,9 +2341,9 @@ NAR #88757, TRA #12200
- Altos Droid Flight Monitoring + AltosDroid Flight Monitoring - Altos Droid is designed to mimic the AltosUI flight monitoring + AltosDroid is designed to mimic the AltosUI flight monitoring display, providing separate tabs for each stage of your rocket flight along with a tab containing a map of the local area with icons marking the current location of the altimeter and @@ -2438,7 +2443,7 @@ NAR #88757, TRA #12200
Downloading Flight Logs - Altos Droid always saves every bit of telemetry data it + 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 @@ -2598,7 +2603,7 @@ NAR #88757, TRA #12200 flight line. Particularly since it is so difficult to read most notebook screens in direct sunlight, we think this will be a great thing to have. We are also working on a TeleDongle variant with - Bluetooth that will work with Android phones and tablets. + Bluetooth™ that will work with Android phones and tablets. Because all of our work is open, both the hardware designs and the @@ -4104,4 +4109,4 @@ NAR #88757, TRA #12200 \ No newline at end of file +--> -- cgit v1.2.3 From 1d093383fe58fc8c8c11e1c7cd1cd929ae1bd9e4 Mon Sep 17 00:00:00 2001 From: Bdale Garbee Date: Tue, 17 Dec 2013 14:53:59 -0700 Subject: further documentation tweaks --- doc/altusmetrum.xsl | 149 +++++++++++++++++++++++++++++----------------------- 1 file changed, 82 insertions(+), 67 deletions(-) (limited to 'doc') diff --git a/doc/altusmetrum.xsl b/doc/altusmetrum.xsl index 1e9f04b4..da6ad02c 100644 --- a/doc/altusmetrum.xsl +++ b/doc/altusmetrum.xsl @@ -2371,8 +2371,8 @@ NAR #88757, TRA #12200
Installing AltosDroid - AltosDroid is included in the Google Play store. To install - it on your Android device, open open the Google Play Store + AltosDroid is available from the Google Play store. To install + it on your Android device, open the Google Play Store application and search for “altosdroid”. Make sure you don't have a space between “altos” and “droid” or you probably won't find what you want. That should bring you to the right page @@ -2529,20 +2529,22 @@ NAR #88757, TRA #12200
In the Rocket - In the rocket itself, you just need a TeleMetrum or - TeleMini board and + 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 for hours. - A 110mAh battery weighs less than a triple A battery and will run a TeleMetrum for - a few hours, or a TeleMini for much (much) longer. + run a TeleMetrum or TeleMega for hours. + A 110mAh battery weighs less than a triple A battery and is a good + choice for use with TeleMini. - By default, we ship the altimeters with a simple wire antenna. If your - electronics bay or the air-frame it resides within is made of carbon fiber, - which is opaque to RF signals, you may choose to have an SMA connector - installed so that you can run a coaxial cable to an antenna mounted - elsewhere in the rocket. + By default, we ship flight computers with a simple wire antenna. + If your electronics bay or the air-frame it resides within is made + of carbon fiber, which is opaque to RF signals, you may prefer to + install an SMA connector so that you can run a coaxial cable to an + antenna mounted elsewhere in the rocket. However, note that the + GPS antenna is fixed on all current products, so you really want + to install the flight computer in a bay made of RF-transparent + materials if at all possible.
@@ -2561,6 +2563,11 @@ NAR #88757, TRA #12200 Linux, Mac OS and Windows. There's also a suite of C tools for Linux which can perform most of the same tasks. + + Alternatively, a TeleBT attached with an SMA to BNC adapter at the + feed point of a hand-held yagi used in conjunction with an Android + device running AltosDroid makes an outstanding ground station. + After the flight, you can use the radio link to extract the more detailed data logged in either TeleMetrum or TeleMini devices, or you can use a mini USB cable to plug into the @@ -2570,10 +2577,12 @@ NAR #88757, TRA #12200 of digital cameras and other modern electronic stuff will work fine. - If your TeleMetrum-equipped rocket lands out of sight, you may enjoy having a hand-held GPS - receiver, so that you can put in a way-point for the last reported rocket - position before touch-down. This makes looking for your rocket a lot like - Geo-Caching... just go to the way-point and look around starting from there. + If your rocket lands out of sight, you may enjoy having a hand-held + GPS receiver, so that you can put in a way-point for the last + reported rocket position before touch-down. This makes looking for + your rocket a lot like Geo-Caching... just go to the way-point and + look around starting from there. AltosDroid on an Android device + with GPS receiver works great for this, too! You may also enjoy having a ham radio “HT” that covers the 70cm band... you @@ -2649,25 +2658,20 @@ NAR #88757, TRA #12200
Future Plans + + We've designed a simple GPS based radio tracker called TeleGPS. + If all goes well, we hope to introduce this in the first + half of 2014. + - In the future, we intend to offer “companion boards” for the rocket - that will plug in to TeleMetrum to collect additional data, provide - more pyro channels, and so forth. - - - Also under design is a new flight computer with more sensors, more - pyro channels, and a more powerful radio system designed for use - in multi-stage, complex, and extreme altitude projects. - - - We are also working on alternatives to TeleDongle. One is a - a stand-alone, hand-held ground terminal that will allow monitoring - the rocket's status, collecting data during flight, and logging data - after flight without the need for a notebook computer on the - flight line. Particularly since it is so difficult to read most - notebook screens in direct sunlight, we think this will be a great - thing to have. We are also working on a TeleDongle variant with - Bluetooth™ that will work with Android phones and tablets. + We have designed and prototyped several “companion boards” that + can attach to the companion connector on TeleMetrum and TeleMega + flight computers to collect more data, provide more pyro channels, + and so forth. We do not yet know if or when any of these boards + will be produced in enough quantity to sell. If you have specific + interests for data collection or control of events in your rockets + beyond the capabilities of our existing productions, please let + us know! Because all of our work is open, both the hardware designs and the @@ -2688,19 +2692,21 @@ NAR #88757, TRA #12200 Building high-power rockets that fly safely is hard enough. Mix in some sophisticated electronics and a bunch of radio energy - and oftentimes you find few perfect solutions. This chapter + and some creativity and/or compromise may be required. This chapter contains some suggestions about how to install Altus Metrum - products into the rocket air-frame, including how to safely and + products into a rocket air-frame, including how to safely and reliably mix a variety of electronics into the same air-frame.
Mounting the Altimeter The first consideration is to ensure that the altimeter is - securely fastened to the air-frame. For TeleMetrum, we use - nylon standoffs and nylon screws; they're good to at least 50G - and cannot cause any electrical issues on the board. For - TeleMini, we usually cut small pieces of 1/16 inch balsa to fit + securely fastened to the air-frame. For most of our products, we + prefer nylon standoffs and nylon screws; they're good to at least 50G + and cannot cause any electrical issues on the board. Metal screws + and standoffs are fine, too, just be careful to avoid electrical + shorts! For TeleMini v1.0, we usually cut small pieces of 1/16 inch + balsa to fit under the screw holes, and then take 2x56 nylon screws and screw them through the TeleMini mounting holes, through the balsa and into the underlying material. @@ -2708,7 +2714,8 @@ NAR #88757, TRA #12200 - Make sure TeleMetrum is aligned precisely along the axis of + Make sure accelerometer-equipped products like TeleMetrum and + TeleMega are aligned precisely along the axis of acceleration so that the accelerometer can accurately capture data during the flight. @@ -2746,7 +2753,7 @@ NAR #88757, TRA #12200 culprit here -- CF is a good conductor and will effectively shield the antenna, dramatically reducing signal strength and range. Metallic flake paint is another effective shielding - material which is to be avoided around any antennas. + material which should be avoided around any antennas. If the ebay is large enough, it can be convenient to simply @@ -2767,7 +2774,7 @@ NAR #88757, TRA #12200 consuming very little space. - If you need to place the antenna at a distance from the + If you need to place the UHF antenna at a distance from the altimeter, you can replace the antenna with an edge-mounted SMA connector, and then run 50Ω coax from the board to the antenna. Building a remote antenna is beyond the scope of this @@ -2777,11 +2784,11 @@ NAR #88757, TRA #12200
Preserving GPS Reception - The GPS antenna and receiver in TeleMetrum are highly - sensitive and normally have no trouble tracking enough + The GPS antenna and receiver used in TeleMetrum and TeleMega is + highly sensitive and normally have no trouble tracking enough satellites to provide accurate position information for - recovering the rocket. However, there are many ways to - attenuate the GPS signal. + recovering the rocket. However, there are many ways the GPS signal + can end up attenuated, negatively affecting GPS performance. @@ -2854,7 +2861,7 @@ NAR #88757, TRA #12200 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 + natural resonant length. Altus Metrum products transmit on the 70cm amateur band, so you should avoid lengths that are a simple ratio of that length; essentially any multiple of ¼ of the wavelength (17.5cm). @@ -2880,10 +2887,10 @@ NAR #88757, TRA #12200 decreasing pressure. - The barometric sensor in the altimeter is quite sensitive to - chemical damage from the products of APCP or BP combustion, so - make sure the ebay is carefully sealed from any compartment - which contains ejection charges or motors. + All barometric sensors are quite sensitive to chemical damage from + the products of APCP or BP combustion, so make sure the ebay is + carefully sealed from any compartment which contains ejection + charges or motors.
@@ -2934,7 +2941,11 @@ NAR #88757, TRA #12200 version from . - We recommend updating the altimeter first, before updating TeleDongle. + If you need to update the firmware on a TeleDongle, we recommend + updating the altimeter first, before updating TeleDongle. However, + note that TeleDongle rarely need to be updated. Any firmware version + 1.0.1 or later will work, version 1.2.1 may have improved receiver + performance slightly. Self-programmable devices (TeleMega, TeleMetrum v2 and EasyMini) @@ -3152,9 +3163,8 @@ NAR #88757, TRA #12200 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. + TeleMini. You can make your own using an 8-pin MicroMaTch + connector on one end and a set of four pins on the other. @@ -3400,8 +3410,8 @@ NAR #88757, TRA #12200 - Uses Li-Po to fire e-matches, can be modified to support - optional separate pyro battery if needed. + Can use either main system Li-Po or optional separate pyro battery + to fire e-matches. @@ -3697,15 +3707,17 @@ NAR #88757, TRA #12200 FAQ - TeleMetrum seems to shut off when disconnected from the - computer. Make sure the battery is adequately charged. Remember the + TeleMetrum seems to shut off when disconnected from the + computer. + Make sure the battery is adequately charged. Remember the unit will pull more power than the USB port can deliver before the GPS enters “locked” mode. The battery charges best when TeleMetrum is turned off. - It's impossible to stop the TeleDongle when it's in “p” mode, I have - to unplug the USB cable? Make sure you have tried to “escape out” of + It's impossible to stop the TeleDongle when it's in “p” mode, I have + to unplug the USB cable? + Make sure you have tried to “escape out” of this mode. If this doesn't work the reboot procedure for the TeleDongle *is* to simply unplug it. 'cu' however will retain it's outgoing buffer IF your “escape out” ('~~') does not work. @@ -3714,21 +3726,24 @@ NAR #88757, TRA #12200 communication. - The amber LED (on the TeleMetrum) lights up when both - battery and USB are connected. Does this mean it's charging? + The amber LED (on the TeleMetrum) lights up when both + battery and USB are connected. Does this mean it's charging? + Yes, the yellow LED indicates the charging at the 'regular' rate. If the led is out but the unit is still plugged into a USB port, then the battery is being charged at a 'trickle' rate. - There are no “dit-dah-dah-dit” sound or lights like the manual mentions? + There are no “dit-dah-dah-dit” sound or lights like the manual + mentions? That's the “pad” mode. Weak batteries might be the problem. - It is also possible that the TeleMetrum is horizontal and the output + It is also possible that the flight computer is horizontal and the + output is instead a “dit-dit” meaning 'idle'. For TeleMini, it's possible that it received a command packet which would have left it in “pad” mode. - How do I save flight data? + How do I save flight data? Live telemetry is written to file(s) whenever AltosUI is connected to the TeleDongle. The file area defaults to ~/TeleMetrum but is easily changed using the menus in AltosUI. The files that -- cgit v1.2.3 From e4b223df372348718b74d2ecad4957f3e30f8d79 Mon Sep 17 00:00:00 2001 From: Keith Packard Date: Tue, 17 Dec 2013 17:37:39 -0800 Subject: Add altosui image and attempt to add launch photo to title --- doc/altusmetrum.xsl | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) (limited to 'doc') diff --git a/doc/altusmetrum.xsl b/doc/altusmetrum.xsl index da6ad02c..8725da04 100644 --- a/doc/altusmetrum.xsl +++ b/doc/altusmetrum.xsl @@ -5,6 +5,11 @@ The Altus Metrum System An Owner's Manual for Altus Metrum Rocketry Electronics + + + + + Bdale Garbee @@ -1350,7 +1355,6 @@ NAR #88757, TRA #12200 - AltosUI The AltosUI program provides a graphical user interface for @@ -1361,6 +1365,11 @@ NAR #88757, TRA #12200 is split into sections, each of which documents one of the tasks provided from the top-level toolbar. + + + + +
Monitor Flight Receive, Record and Display Telemetry Data -- cgit v1.2.3 From e44ce127ece149e7b07be49142bc0f9d50bbe97d Mon Sep 17 00:00:00 2001 From: Keith Packard Date: Tue, 17 Dec 2013 20:05:12 -0800 Subject: doc: Add screen shots everywhere This has screen shots of every dialog in altosui Signed-off-by: Keith Packard --- doc/Makefile | 33 +++- doc/altosui.png | Bin 0 -> 14132 bytes doc/altusmetrum.xsl | 408 +++++++++++++++++++++++++--------------- doc/ascent.png | Bin 0 -> 63675 bytes doc/configure-altimeter.png | Bin 0 -> 47817 bytes doc/configure-altosui.png | Bin 0 -> 30958 bytes doc/configure-groundstation.png | Bin 0 -> 17329 bytes doc/configure-pyro.png | Bin 0 -> 59805 bytes doc/descent.png | Bin 0 -> 63689 bytes doc/device-selection.png | Bin 0 -> 14482 bytes doc/fire-igniter.png | Bin 0 -> 6979 bytes doc/graph-configure.png | Bin 0 -> 44367 bytes doc/graph-map.png | Bin 0 -> 991681 bytes doc/graph-stats.png | Bin 0 -> 73620 bytes doc/graph.png | Bin 0 -> 85178 bytes doc/landed.png | Bin 0 -> 53215 bytes doc/launch-pad.png | Bin 0 -> 84611 bytes doc/load-maps.png | Bin 0 -> 390139 bytes doc/scan-channels.png | Bin 0 -> 18787 bytes doc/site-map.png | Bin 0 -> 618430 bytes doc/table.png | Bin 0 -> 71556 bytes doc/xorg-fo.xsl | 4 + 22 files changed, 295 insertions(+), 150 deletions(-) create mode 100644 doc/altosui.png create mode 100644 doc/ascent.png create mode 100644 doc/configure-altimeter.png create mode 100644 doc/configure-altosui.png create mode 100644 doc/configure-groundstation.png create mode 100644 doc/configure-pyro.png create mode 100644 doc/descent.png create mode 100644 doc/device-selection.png create mode 100644 doc/fire-igniter.png create mode 100644 doc/graph-configure.png create mode 100644 doc/graph-map.png create mode 100644 doc/graph-stats.png create mode 100644 doc/graph.png create mode 100644 doc/landed.png create mode 100644 doc/launch-pad.png create mode 100644 doc/load-maps.png create mode 100644 doc/scan-channels.png create mode 100644 doc/site-map.png create mode 100644 doc/table.png (limited to 'doc') diff --git a/doc/Makefile b/doc/Makefile index c45e084b..f586ad17 100644 --- a/doc/Makefile +++ b/doc/Makefile @@ -14,6 +14,37 @@ RELNOTES=\ release-notes-1.2.1.html \ release-notes-1.3.html +PICTURES=\ + altosui.png \ + ascent.png \ + configure-altimeter.png \ + configure-altosui.png \ + configure-groundstation.png \ + configure-pyro.png \ + descent.png \ + device-selection.png \ + easymini-top.jpg \ + fire-igniter.png \ + graph-configure.png \ + graph-map.png \ + graph.png \ + graph-stats.png \ + landed.png \ + launch-pad.png \ + load-maps.png \ + scan-channels.png \ + site-map.png \ + table.png \ + telemega-v1.0-top.jpg \ + telemetrum-v1.1-thside.jpg \ + telemini-v1-top.jpg \ + telemini-v2-top.jpg +SVG=\ + easymini-outline.svg \ + telemega-outline.svg \ + telemetrum.svg \ + telemini.svg + RELNOTES_XSL=$(RELNOTES:.html=.xsl) HTML=altusmetrum.html altos.html telemetry.html companion.html micropeak.html $(RELNOTES) PDF=altusmetrum.pdf altos.pdf telemetry.pdf companion.pdf micropeak.pdf @@ -21,7 +52,7 @@ DOC=$(HTML) $(PDF) HTMLSTYLE=/usr/share/xml/docbook/stylesheet/docbook-xsl/html/docbook.xsl FOSTYLE=xorg-fo.xsl PDFSTYLE= -IMAGES=telemetrum.svg telemini.svg +IMAGES=$(PICTURES) $(SVG) .SUFFIXES: .xsl .html .pdf diff --git a/doc/altosui.png b/doc/altosui.png new file mode 100644 index 00000000..3dd28de4 Binary files /dev/null and b/doc/altosui.png differ diff --git a/doc/altusmetrum.xsl b/doc/altusmetrum.xsl index 8725da04..dfe89438 100644 --- a/doc/altusmetrum.xsl +++ b/doc/altusmetrum.xsl @@ -5,11 +5,6 @@ The Altus Metrum System An Owner's Manual for Altus Metrum Rocketry Electronics - - - - - Bdale Garbee @@ -551,11 +546,13 @@ NAR #88757, TRA #12200
TeleMetrum - - - - - + + + + + + + TeleMetrum is a 1 inch by 2¾ inch circuit board. It was designed to fit inside coupler for 29mm air-frame tubing, but using it in a tube that @@ -571,11 +568,13 @@ NAR #88757, TRA #12200
TeleMini - - - - - + + + + + + + TeleMini v1.0 is ½ inches by 1½ inches. It was designed to fit inside an 18mm air-frame tube, but using it in @@ -590,11 +589,13 @@ NAR #88757, TRA #12200 the board, meaning an ideal “simple” avionics bay for TeleMini should have at least 9 inches of interior length. - - - - - + + + + + + + TeleMini v2.0 is 0.8 inches by 1½ inches. It adds more on-board data logging memory, a built-in USB connector and @@ -605,11 +606,13 @@ NAR #88757, TRA #12200
EasyMini - - - - - + + + + + + + EasyMini is built on a 0.8 inch by 1½ inch circuit board. It's designed to fit in a 24mm coupler tube. The connectors and @@ -619,11 +622,13 @@ NAR #88757, TRA #12200
TeleMega - - - - - + + + + + + + TeleMega is a 1¼ inch by 3¼ inch circuit board. It was designed to easily fit in a 38mm coupler. Like TeleMetrum, @@ -1356,6 +1361,13 @@ NAR #88757, TRA #12200 AltosUI + + + + + + + The AltosUI program provides a graphical user interface for interacting with the Altus Metrum product family. AltosUI can @@ -1365,11 +1377,6 @@ NAR #88757, TRA #12200 is split into sections, each of which documents one of the tasks provided from the top-level toolbar. - - - - -
Monitor Flight Receive, Record and Display Telemetry Data @@ -1379,6 +1386,13 @@ NAR #88757, TRA #12200 AltosUI will create a window to display telemetry data as received by the selected TeleDongle device. + + + + + + + All telemetry data received are automatically recorded in suitable log files. The name of the files includes the current @@ -1447,6 +1461,13 @@ NAR #88757, TRA #12200
Launch Pad + + + + + + + The 'Launch Pad' tab shows information used to decide when the rocket is ready for flight. The first elements include red/green @@ -1539,6 +1560,13 @@ NAR #88757, TRA #12200
Ascent + + + + + + + This tab is shown during Boost, Fast and Coast phases. The information displayed here helps monitor the @@ -1565,6 +1593,13 @@ NAR #88757, TRA #12200
Descent + + + + + + + Once the rocket has reached apogee and (we hope) activated the apogee charge, attention switches to tracking the rocket on @@ -1601,6 +1636,13 @@ NAR #88757, TRA #12200
Landed + + + + + + + Once the rocket is on the ground, attention switches to recovery. While the radio signal is often lost once the @@ -1636,8 +1678,32 @@ NAR #88757, TRA #12200 graph window for the current flight.
+
+ Table + + + + + + + + + The table view shows all of the data available from the + flight computer. Probably the most useful data on + this tab is the detailed GPS information, which includes + horizontal dilution of precision information, and + information about the signal being received from the satellites. + +
Site Map + + + + + + + When the TeleMetrum has a GPS fix, the Site Map tab will map the rocket's position to make it easier for you to locate the @@ -1721,50 +1787,28 @@ NAR #88757, TRA #12200 .eeprom file containing flight data saved from flash memory. + + Note that telemetry files will generally produce poor graphs + due to the lower sampling rate and missed telemetry packets. + Use saved flight data in .eeprom files for graphing where possible. + Once a flight record is selected, a window with multiple tabs is opened. - - - Flight Graph - - - By default, the graph contains acceleration (blue), - velocity (green) and altitude (red). - - - - - Configure Graph - - - This selects which graph elements to show, and, at the - very bottom, lets you switch between metric and - imperial units - - - - - Flight Statistics - - - Shows overall data computed from the 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. - - - - +
+ Flight Graph + + + + + + + + + By default, the graph contains acceleration (blue), + velocity (green) and altitude (red). + The graph can be zoomed into a particular area by clicking and dragging down and to the right. Once zoomed, the graph can be @@ -1773,11 +1817,51 @@ NAR #88757, TRA #12200 The right mouse button causes a pop-up menu to be displayed, giving you the option save or print the plot. - - Note that telemetry files will generally produce poor graphs - due to the lower sampling rate and missed telemetry packets. - Use saved flight data in .eeprom files for graphing where possible. - +
+
+ Configure Graph + + + + + + + + + This selects which graph elements to show, and, at the + very bottom, lets you switch between metric and + imperial units + +
+
+ Flight Statistics + + + + + + + + + Shows overall data computed from the 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. + +
Export Data @@ -1821,6 +1905,13 @@ NAR #88757, TRA #12200
Configure Altimeter + + + + + + + Select this button and then select either an altimeter or TeleDongle Device from the list provided. Selecting a TeleDongle @@ -2037,6 +2128,13 @@ NAR #88757, TRA #12200
Configure Pyro Channels + + + + + + + This opens a separate window to configure the additional pyro channels available on TeleMega. One column is @@ -2064,6 +2162,13 @@ NAR #88757, TRA #12200
Configure AltosUI + + + + + + + This button presents a dialog so that you can configure the AltosUI global settings. @@ -2075,18 +2180,24 @@ NAR #88757, TRA #12200 the current flight status. However, sometimes you don't want to hear them. - - - Enable—turns all voice announcements on and off - - - - Test Voice—Plays a short message allowing you to verify - that the audio system is working and the volume settings - are reasonable - - - + + + Enable + + Turns all voice announcements on and off + + + + Test Voice + + + Plays a short message allowing you to verify + that the audio system is working and the volume settings + are reasonable + + + +
Log Directory @@ -2161,6 +2272,13 @@ NAR #88757, TRA #12200
Configure Groundstation + + + + + + + Select this button and then select a TeleDongle Device from the list provided. @@ -2246,46 +2364,16 @@ NAR #88757, TRA #12200 (self programming). Please read the directions for flashing devices in the Updating Device Firmware chapter below. - - For “self programming”, connect USB to the device to be - programmed and push the 'Flash Image' button. That will - present a dialog box listing all of the connected - devices. Carefully select the device to be programmed. - - - For “pair programming”, once you have the programmer and - target devices connected, push the 'Flash Image' button. That - will present a dialog box listing all of the connected - devices. Carefully select the programmer device, not the - device to be programmed. - - - Next, select the image to flash to the device. These are named - with the product name and firmware version. The file selector - will start in the directory containing the firmware included - with the AltosUI package. Navigate to the directory containing - the desired firmware if it isn't there. - - - Next, a small dialog containing the device serial number and - RF calibration values should appear. If these values are - incorrect (possibly due to a corrupted image in the device), - enter the correct values here. - - - Finally, a dialog containing a progress bar will follow the - programming process. - - - When programming is complete, the target device will - reboot. Note that if a pair programmed target device is - connected via USB, you will have to unplug it and then plug it - back in for the USB connection to reset so that you can - communicate with the device again. -
Fire Igniter + + + + + + + This activates the igniter circuits in the flight computer to help test recovery systems deployment. Because this command can operate @@ -2313,6 +2401,13 @@ NAR #88757, TRA #12200
Scan Channels + + + + + + + This listens for telemetry packets on all of the configured frequencies, displaying information about each device it @@ -2324,6 +2419,13 @@ NAR #88757, TRA #12200
Load Maps + + + + + + + Before heading out to a new launch site, you can use this to load satellite images in case you don't have internet @@ -3978,11 +4080,13 @@ NAR #88757, TRA #12200 TeleMega has overall dimensions of 1.250 x 3.250 inches, and the mounting holes are sized for use with 4-40 or M3 screws. - - - - - + + + + + + +
TeleMetrum template @@ -3990,11 +4094,13 @@ NAR #88757, TRA #12200 TeleMetrum has overall dimensions of 1.000 x 2.750 inches, and the mounting holes are sized for use with 4-40 or M3 screws. - - - - - + + + + + + +
TeleMini v2/EasyMini template @@ -4002,11 +4108,13 @@ NAR #88757, TRA #12200 TeleMini v2 and EasyMini have overall dimensions of 0.800 x 1.500 inches, and the mounting holes are sized for use with 4-40 or M3 screws. - - - - - + + + + + + +
TeleMini v1 template @@ -4014,11 +4122,13 @@ NAR #88757, TRA #12200 TeleMini has overall dimensions of 0.500 x 1.500 inches, and the mounting holes are sized for use with 2-56 or M2 screws. - - - - - + + + + + + +
diff --git a/doc/ascent.png b/doc/ascent.png new file mode 100644 index 00000000..fd1cd09a Binary files /dev/null and b/doc/ascent.png differ diff --git a/doc/configure-altimeter.png b/doc/configure-altimeter.png new file mode 100644 index 00000000..afb19325 Binary files /dev/null and b/doc/configure-altimeter.png differ diff --git a/doc/configure-altosui.png b/doc/configure-altosui.png new file mode 100644 index 00000000..43fd400f Binary files /dev/null and b/doc/configure-altosui.png differ diff --git a/doc/configure-groundstation.png b/doc/configure-groundstation.png new file mode 100644 index 00000000..9f836e71 Binary files /dev/null and b/doc/configure-groundstation.png differ diff --git a/doc/configure-pyro.png b/doc/configure-pyro.png new file mode 100644 index 00000000..4f03c0a5 Binary files /dev/null and b/doc/configure-pyro.png differ diff --git a/doc/descent.png b/doc/descent.png new file mode 100644 index 00000000..0c479e72 Binary files /dev/null and b/doc/descent.png differ diff --git a/doc/device-selection.png b/doc/device-selection.png new file mode 100644 index 00000000..ffd067d7 Binary files /dev/null and b/doc/device-selection.png differ diff --git a/doc/fire-igniter.png b/doc/fire-igniter.png new file mode 100644 index 00000000..85804573 Binary files /dev/null and b/doc/fire-igniter.png differ diff --git a/doc/graph-configure.png b/doc/graph-configure.png new file mode 100644 index 00000000..b5888338 Binary files /dev/null and b/doc/graph-configure.png differ diff --git a/doc/graph-map.png b/doc/graph-map.png new file mode 100644 index 00000000..fd0fb134 Binary files /dev/null and b/doc/graph-map.png differ diff --git a/doc/graph-stats.png b/doc/graph-stats.png new file mode 100644 index 00000000..6f5c9791 Binary files /dev/null and b/doc/graph-stats.png differ diff --git a/doc/graph.png b/doc/graph.png new file mode 100644 index 00000000..c7c7b7d7 Binary files /dev/null and b/doc/graph.png differ diff --git a/doc/landed.png b/doc/landed.png new file mode 100644 index 00000000..7b4f3177 Binary files /dev/null and b/doc/landed.png differ diff --git a/doc/launch-pad.png b/doc/launch-pad.png new file mode 100644 index 00000000..a6f142dd Binary files /dev/null and b/doc/launch-pad.png differ diff --git a/doc/load-maps.png b/doc/load-maps.png new file mode 100644 index 00000000..dc7ea64c Binary files /dev/null and b/doc/load-maps.png differ diff --git a/doc/scan-channels.png b/doc/scan-channels.png new file mode 100644 index 00000000..bf6b6e53 Binary files /dev/null and b/doc/scan-channels.png differ diff --git a/doc/site-map.png b/doc/site-map.png new file mode 100644 index 00000000..a6d3f78b Binary files /dev/null and b/doc/site-map.png differ diff --git a/doc/table.png b/doc/table.png new file mode 100644 index 00000000..86cb9881 Binary files /dev/null and b/doc/table.png differ diff --git a/doc/xorg-fo.xsl b/doc/xorg-fo.xsl index 075a2d98..a36b88f3 100644 --- a/doc/xorg-fo.xsl +++ b/doc/xorg-fo.xsl @@ -113,4 +113,8 @@ + + center + + -- cgit v1.2.3 From 212a1b66ae04317b7b42ba57573b910fde09ca6c Mon Sep 17 00:00:00 2001 From: Keith Packard Date: Tue, 17 Dec 2013 20:24:19 -0800 Subject: doc: Publish images with HTML bits Otherwise the html won't render right. Signed-off-by: Keith Packard --- doc/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'doc') diff --git a/doc/Makefile b/doc/Makefile index f586ad17..bc8dc2a2 100644 --- a/doc/Makefile +++ b/doc/Makefile @@ -48,11 +48,11 @@ SVG=\ RELNOTES_XSL=$(RELNOTES:.html=.xsl) HTML=altusmetrum.html altos.html telemetry.html companion.html micropeak.html $(RELNOTES) PDF=altusmetrum.pdf altos.pdf telemetry.pdf companion.pdf micropeak.pdf -DOC=$(HTML) $(PDF) HTMLSTYLE=/usr/share/xml/docbook/stylesheet/docbook-xsl/html/docbook.xsl FOSTYLE=xorg-fo.xsl PDFSTYLE= IMAGES=$(PICTURES) $(SVG) +DOC=$(HTML) $(PDF) $(PICTURES) .SUFFIXES: .xsl .html .pdf -- cgit v1.2.3 From 6827961c002757f8e74de44f6eb9c9029d099ebc Mon Sep 17 00:00:00 2001 From: Keith Packard Date: Wed, 18 Dec 2013 14:25:41 -0800 Subject: doc: Update micropeak quick start guide to note new boost detect Now waits for one minute and 30m of altitude change to avoid false detections. Signed-off-by: Keith Packard --- doc/micropeak.xsl | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'doc') diff --git a/doc/micropeak.xsl b/doc/micropeak.xsl index afa6fd15..cd9452c8 100644 --- a/doc/micropeak.xsl +++ b/doc/micropeak.xsl @@ -115,20 +115,20 @@ NAR #88757, TRA #12200 Finish preparing the rocket for flight. After the previous flight data have been reported, MicroPeak waits for - 30 seconds before starting to check for launch. This gives + one minute before starting to check for launch. This gives you time to finish assembling the rocket. As those activities might cause pressure changes inside the airframe, MicroPeak might accidentally detect boost. If you need to do - anything to the airframe after the 30 second window passes, + anything to the airframe after the one minute window passes, make sure to be careful not to disturb the altimeter. The - LED will remain dark during the 30 second delay, but after + LED will remain dark during the one minute delay, but after that, it will start blinking once every 3 seconds. - Fly the rocket. Once the rocket passes about 10m in height - (32 feet), the micro-controller will record the ground + Fly the rocket. Once the rocket passes about 30m in height + (100 feet), the micro-controller will record the ground pressure and track the pressure seen during the flight. In this mode, the LED flickers rapidly. When the rocket lands, and the pressure stabilizes, the micro-controller will record -- cgit v1.2.3 From b63fc05481bf6d57e6385704ce53c1c19afa9c2e Mon Sep 17 00:00:00 2001 From: Keith Packard Date: Wed, 18 Dec 2013 14:34:31 -0800 Subject: doc: typo in micropeak doc hole->hold --- doc/micropeak.xsl | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'doc') diff --git a/doc/micropeak.xsl b/doc/micropeak.xsl index cd9452c8..8c487e5d 100644 --- a/doc/micropeak.xsl +++ b/doc/micropeak.xsl @@ -401,7 +401,7 @@ NAR #88757, TRA #12200
Lithium Battery - The CR1025 battery used by MicroPeak holes 30mAh of power, + The CR1025 battery used by MicroPeak holds 30mAh of power, which is sufficient to run for over 40 hours. Because MicroPeak powers down on landing, run time includes only time sitting on the launch pad or during flight. -- cgit v1.2.3 From 1bf84ec28a41f7bd1b11ba45b4639856266227bc Mon Sep 17 00:00:00 2001 From: Keith Packard Date: Wed, 18 Dec 2013 20:30:58 -0800 Subject: doc: Add tables describing AltOS beeps and flashes Provide a convenient place to reference when listening to the device. Signed-off-by: Keith Packard --- doc/altusmetrum.xsl | 232 ++++++++++++++++++++++++++++++++++++++++++++++++++-- 1 file changed, 223 insertions(+), 9 deletions(-) (limited to 'doc') diff --git a/doc/altusmetrum.xsl b/doc/altusmetrum.xsl index dfe89438..c71e08a7 100644 --- a/doc/altusmetrum.xsl +++ b/doc/altusmetrum.xsl @@ -835,17 +835,144 @@ NAR #88757, TRA #12200 the altimeter completes initialization and self test, and decides which mode to enter next. + + Here's a short summary of all of the modes and the beeping (or + flashing, in the case of TeleMini v1) that accompanies each + mode. In the description of the beeping pattern, “dit” means a + short beep while "dah" means a long beep (three times as + long). “Brap” means a long dissonant tone. +
+ AltOS Modes + + + + + + + + + Mode Name + Abbreviation + Beeps + Description + + + + + Startup + S + dit dit dit + + + Calibrating sensors, detecting orientation. + + + + + Idle + I + dit dit + + + Ready to accept commands over USB or radio link. + + + + + Pad + P + dit dah dah dit + + + Waiting for launch. Not listening for commands. + + + + + Boost + B + dah dit dit dit + + + Accelerating upwards. + + + + + Fast + F + dit dit dah dit + + + Decellerating, but moving faster than 200m/s. + + + + + Coast + C + dah dit dah dit + + + Decellerating, moving slower than 200m/s + + + + + Drogue + D + dah dit dit + + + Descending after apogee. Above main height. + + + + + Main + M + dah dah + + + Descending. Below main height. + + + + + Landed + L + dit dah dit dit + + + Stable altitude for at least ten seconds. + + + + + Sensor error + X + dah dit dit dah + + + Error detected during sensor calibration. + + + + + +
+ In flight or “pad” mode, the altimeter engages the flight - state machine, goes into transmit-only mode to - send telemetry, and waits for launch to be detected. - Flight mode is indicated by an “di-dah-dah-dit” (“P” for pad) - on the beeper or lights, followed by beeps or flashes - indicating the state of the pyrotechnic igniter continuity. - One beep/flash indicates apogee continuity, two beeps/flashes - indicate main continuity, three beeps/flashes indicate both - apogee and main continuity, and one longer “brap” sound or - rapidly alternating lights indicates no continuity. For a + state machine, goes into transmit-only mode to send telemetry, + and waits for launch to be detected. Flight mode is indicated + by an “di-dah-dah-dit” (“P” for pad) on the beeper or lights, + followed by beeps or flashes indicating the state of the + pyrotechnic igniter continuity. One beep/flash indicates + apogee continuity, two beeps/flashes indicate main continuity, + three beeps/flashes indicate both apogee and main continuity, + and one longer “brap” sound which is made by rapidly + alternating between two tones indicates no continuity. For a dual deploy flight, make sure you're getting three beeps or flashes before launching! For apogee-only or motor eject flights, do what makes sense. @@ -862,6 +989,93 @@ NAR #88757, TRA #12200 data from the on-board storage chip after flight, and for ground testing pyro charges. + + In “Idle” and “Pad” modes, once the mode indication + beeps/flashes and continuity indication has been sent, if + there is no space available to log the flight in on-board + memory, the flight computer will emit a warbling tone (much + slower than the “no continuity tone”) + + + Here's a summary of all of the “pad” and “idle” mode indications. + + Pad/Idle Indications + + + + + + + + Name + Beeps + Description + + + + + Neither + brap + + + No continuity detected on either apogee or main + igniters. + + + + + Apogee + dit + + + Continuity detected only on apogee igniter. + + + + + Main + dit dit + + + Continuity detected only on main igniter. + + + + + Both + dit dit dit + + + Continuity detected on both igniters. + + + + + Storage Full + warble + + + On-board data logging storage is full. This will + not prevent the flight computer from safely + controlling the flight or transmitting telemetry + signals, but no record of the flight will be + stored in on-board flash. + + + + + +
+ + + Once landed, the flight computer will signal that by emitting + the “Landed” sound described above, after which it will beep + out the apogee height (in meters). Each digit is represented + by a sequence of short “dit” beeps, with a pause between + digits. A zero digit is represented with one long “dah” + beep. The flight computer will continue to report landed mode + and beep out the maximum height until turned off. + One “neat trick” of particular value when TeleMetrum or TeleMega are used with very large air-frames, is that you can power the board up while the -- cgit v1.2.3