From 1d421a43494cf2003ac23fb8cd21d6ae05edfac8 Mon Sep 17 00:00:00 2001 From: Bdale Garbee Date: Mon, 17 Feb 2014 00:10:05 -0700 Subject: update copyright year assertion in MicroPeak manual, remember during releases --- 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 66b04072..dafe3682 100644 --- a/doc/micropeak.xsl +++ b/doc/micropeak.xsl @@ -10,7 +10,7 @@ Packard - 2012 + 2014 Bdale Garbee and Keith Packard -- cgit v1.2.3 From 6e713f0a53d608a8855884b7a48e4e3423d8a3d2 Mon Sep 17 00:00:00 2001 From: Bdale Garbee Date: Mon, 17 Feb 2014 00:15:58 -0700 Subject: deliver images used in MicroPeak manual to web server, too --- doc/Makefile | 14 ++++++++++++++ 1 file changed, 14 insertions(+) (limited to 'doc') diff --git a/doc/Makefile b/doc/Makefile index 83731fbe..42a8e477 100644 --- a/doc/Makefile +++ b/doc/Makefile @@ -34,6 +34,19 @@ PICTURES=\ landed.png \ launch-pad.png \ load-maps.png \ + micropeak-app.png \ + micropeak-back.jpg \ + micropeak-device-dialog.png \ + micropeak-dime.jpg \ + micropeak-download.png \ + micropeak-graph-configure.png \ + micropeak-graph.png \ + micropeak-preferences.png \ + micropeak-raw-data.png \ + micropeak-save-dialog.png \ + micropeak-statistics.png \ + MicroPeakUSB-2.0-inuse.jpg \ + MicroPeakUSB-2.0.jpg \ scan-channels.png \ site-map.png \ table.png \ @@ -41,6 +54,7 @@ PICTURES=\ telemetrum-v1.1-thside.jpg \ telemini-v1-top.jpg \ telemini-v2-top.jpg + SVG=\ easymini-outline.svg \ telemega-outline.svg \ -- cgit v1.2.3 From 874d0065ecb066ee746a016876edebc7cc6e3d96 Mon Sep 17 00:00:00 2001 From: Keith Packard Date: Mon, 17 Feb 2014 21:27:57 -0800 Subject: Re-create drill templates Using inkscape, the drill templates weren't getting printed correctly. Switching to hand-generated svg fixes that. The .xsl file is also fixed to really encourage the images to be printed at exactly 100%. Signed-off-by: Keith Packard --- doc/Makefile | 4 +- doc/altusmetrum.xsl | 12 ++- doc/easymini-outline.svg | 219 ---------------------------------------- doc/easymini.svg | 33 ++++++ doc/telemega-outline.svg | 244 --------------------------------------------- doc/telemega.svg | 33 ++++++ doc/telemetrum-outline.svg | 207 -------------------------------------- doc/telemetrum.svg | 10 +- doc/telemini.svg | 22 ++-- 9 files changed, 92 insertions(+), 692 deletions(-) delete mode 100644 doc/easymini-outline.svg create mode 100644 doc/easymini.svg delete mode 100644 doc/telemega-outline.svg create mode 100644 doc/telemega.svg delete mode 100644 doc/telemetrum-outline.svg (limited to 'doc') diff --git a/doc/Makefile b/doc/Makefile index 42a8e477..d8879d47 100644 --- a/doc/Makefile +++ b/doc/Makefile @@ -56,8 +56,8 @@ PICTURES=\ telemini-v2-top.jpg SVG=\ - easymini-outline.svg \ - telemega-outline.svg \ + easymini.svg \ + telemega.svg \ telemetrum.svg \ telemini.svg diff --git a/doc/altusmetrum.xsl b/doc/altusmetrum.xsl index fb08f5c6..d3d1f72a 100644 --- a/doc/altusmetrum.xsl +++ b/doc/altusmetrum.xsl @@ -5127,7 +5127,8 @@ NAR #88757, TRA #12200 - + @@ -5141,7 +5142,8 @@ NAR #88757, TRA #12200 - + @@ -5155,7 +5157,8 @@ NAR #88757, TRA #12200 - + @@ -5169,7 +5172,8 @@ NAR #88757, TRA #12200 - + diff --git a/doc/easymini-outline.svg b/doc/easymini-outline.svg deleted file mode 100644 index 40faddb3..00000000 --- a/doc/easymini-outline.svg +++ /dev/null @@ -1,219 +0,0 @@ - - - - - - - - - - - - - - - - - image/svg+xml - - - - - - - - - - - - - - - - - - - - - - - - - - - - - UP - - diff --git a/doc/easymini.svg b/doc/easymini.svg new file mode 100644 index 00000000..8a9cba02 --- /dev/null +++ b/doc/easymini.svg @@ -0,0 +1,33 @@ + + + + + + + + + + + + + + + + EasyMini + + UP + + + \ No newline at end of file diff --git a/doc/telemega-outline.svg b/doc/telemega-outline.svg deleted file mode 100644 index e8d74d38..00000000 --- a/doc/telemega-outline.svg +++ /dev/null @@ -1,244 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - image/svg+xml - - - - - - - - - - - - - - - - - - - - - - - - - - - - - UP - - diff --git a/doc/telemega.svg b/doc/telemega.svg new file mode 100644 index 00000000..40edf696 --- /dev/null +++ b/doc/telemega.svg @@ -0,0 +1,33 @@ + + + + + + + + + + + + + + + + TeleMega + + UP + + + \ No newline at end of file diff --git a/doc/telemetrum-outline.svg b/doc/telemetrum-outline.svg deleted file mode 100644 index aee63ed2..00000000 --- a/doc/telemetrum-outline.svg +++ /dev/null @@ -1,207 +0,0 @@ - - - - - - - - - - - - - - - image/svg+xml - - - - - - - - - - - - - - - - - - - - - - - - - - - - - UP - - diff --git a/doc/telemetrum.svg b/doc/telemetrum.svg index 97c4e4a8..80ee182d 100644 --- a/doc/telemetrum.svg +++ b/doc/telemetrum.svg @@ -6,14 +6,14 @@ xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:svg="http://www.w3.org/2000/svg" xmlns="http://www.w3.org/2000/svg" - width="5in" - height="2.5in" - viewBox="0 0 500 250" + width="3in" + height="1.25in" + viewBox="0 0 300 125" preserveaspectratio="none" id="svg2" version="1.1"> - + diff --git a/doc/telemini.svg b/doc/telemini.svg index d07b4971..b2e21e3d 100644 --- a/doc/telemini.svg +++ b/doc/telemini.svg @@ -6,26 +6,26 @@ xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:svg="http://www.w3.org/2000/svg" xmlns="http://www.w3.org/2000/svg" - width="5in" - height="2in" - viewBox="0 0 500 200" + width="1.75in" + height=".75in" + viewBox="0 0 175 75" preserveaspectratio="none" id="svg2" version="1.1"> - + - - + + - - + + TeleMini - - UP + + UP \ No newline at end of file -- cgit v1.2.3 From 43b1797189095c402e1c35bdc317c4196e180e66 Mon Sep 17 00:00:00 2001 From: Keith Packard Date: Mon, 17 Feb 2014 21:30:28 -0800 Subject: doc: Need to publish .svg files as well The drill templates are all .svg files that are referenced by the generated html. 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 d8879d47..1477d325 100644 --- a/doc/Makefile +++ b/doc/Makefile @@ -69,7 +69,7 @@ FOSTYLE=xorg-fo.xsl TEMPLATES=titlepage.templates.xsl PDFSTYLE= IMAGES=$(PICTURES) $(SVG) -DOC=$(HTML) $(PDF) $(PICTURES) +DOC=$(HTML) $(PDF) $(IMAGES) .SUFFIXES: .xml .xsl .html .pdf -- cgit v1.2.3 From 3ef0cc28758c68e6076afa809e157a84ce3661fb Mon Sep 17 00:00:00 2001 From: Bdale Garbee Date: Thu, 20 Feb 2014 13:23:20 -0700 Subject: typo fixes from Matt Kraai --- doc/altos.xsl | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'doc') diff --git a/doc/altos.xsl b/doc/altos.xsl index 5b9e12e8..6092dfcb 100644 --- a/doc/altos.xsl +++ b/doc/altos.xsl @@ -413,7 +413,7 @@ __sfr, __sfr16, __sfr32, __sbit Access to physical registers in the device use this mode - which declares the variable name, it's type and the + which declares the variable name, its type and the address it lives at. No memory is allocated for these variables. @@ -809,7 +809,7 @@ ao_dma_abort(uint8_t id) - Terminate any in-progress DMA transation, marking its + Terminate any in-progress DMA transaction, marking its 'done' variable with the AO_DMA_ABORTED bit. @@ -894,7 +894,7 @@ ao_dma_abort(uint8_t id) - Terminate any in-progress DMA transation, marking its + Terminate any in-progress DMA transaction, marking its 'done' variable with the AO_DMA_ABORTED bit. @@ -904,7 +904,7 @@ Stdio interface AltOS offers a stdio interface over USB, serial and the RF - packet link. This provides for control of the device localy or + packet link. This provides for control of the device locally or remotely. This is hooked up to the stdio functions by providing the standard putchar/getchar/flush functions. These automatically multiplex the available communication channels; @@ -944,7 +944,7 @@ Flushes the current console device output buffer. Any pending characters will be delivered to the target device. - xo +
ao_add_stdio -- cgit v1.2.3 From 4c7da6d0ad568448c37761cd0c0108b9161a9345 Mon Sep 17 00:00:00 2001 From: Keith Packard Date: Fri, 7 Mar 2014 21:27:26 -0800 Subject: doc: Add separate outline pdf generation This generates one-page pdf files that contain just the outline of each product. Signed-off-by: Keith Packard --- doc/Makefile | 3 ++- doc/easymini-outline.pdf | Bin 4240 -> 7047 bytes doc/easymini-outline.xsl | 23 +++++++++++++++++++++++ doc/telemega-outline.pdf | Bin 4349 -> 7020 bytes doc/telemega-outline.xsl | 23 +++++++++++++++++++++++ doc/telemetrum-outline.pdf | Bin 2047 -> 7097 bytes doc/telemetrum-outline.xsl | 23 +++++++++++++++++++++++ 7 files changed, 71 insertions(+), 1 deletion(-) create mode 100644 doc/easymini-outline.xsl create mode 100644 doc/telemega-outline.xsl create mode 100644 doc/telemetrum-outline.xsl (limited to 'doc') diff --git a/doc/Makefile b/doc/Makefile index 1477d325..1f47076c 100644 --- a/doc/Makefile +++ b/doc/Makefile @@ -63,7 +63,8 @@ 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 +PDF=altusmetrum.pdf altos.pdf telemetry.pdf companion.pdf micropeak.pdf \ + telemetrum-outline.pdf telemega-outline.pdf easymini-outline.pdf HTMLSTYLE=/usr/share/xml/docbook/stylesheet/docbook-xsl/html/docbook.xsl FOSTYLE=xorg-fo.xsl TEMPLATES=titlepage.templates.xsl diff --git a/doc/easymini-outline.pdf b/doc/easymini-outline.pdf index a1a0b19d..76a09957 100644 Binary files a/doc/easymini-outline.pdf and b/doc/easymini-outline.pdf differ diff --git a/doc/easymini-outline.xsl b/doc/easymini-outline.xsl new file mode 100644 index 00000000..88125322 --- /dev/null +++ b/doc/easymini-outline.xsl @@ -0,0 +1,23 @@ + + +
+ EasyMini Outline and Hole Pattern + + This image, when printed, provides a precise template for the + mounting holes in EasyMini. EasyMini has overall dimensions + of 0.800 x 1.500 inches, and the mounting holes are sized for + use with 4-40 or M3 screws. + + + + + + + + +
+ + diff --git a/doc/telemega-outline.pdf b/doc/telemega-outline.pdf index f8fc26e2..2f20c62f 100644 Binary files a/doc/telemega-outline.pdf and b/doc/telemega-outline.pdf differ diff --git a/doc/telemega-outline.xsl b/doc/telemega-outline.xsl new file mode 100644 index 00000000..5d3411e9 --- /dev/null +++ b/doc/telemega-outline.xsl @@ -0,0 +1,23 @@ + + +
+ TeleMega Outline and Hole Pattern + + This image, when printed, provides a precise template for the + mounting holes in TeleMega. 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. + + + + + + + + +
+ + diff --git a/doc/telemetrum-outline.pdf b/doc/telemetrum-outline.pdf index 09ce5577..af913520 100644 Binary files a/doc/telemetrum-outline.pdf and b/doc/telemetrum-outline.pdf differ diff --git a/doc/telemetrum-outline.xsl b/doc/telemetrum-outline.xsl new file mode 100644 index 00000000..4a0ade47 --- /dev/null +++ b/doc/telemetrum-outline.xsl @@ -0,0 +1,23 @@ + + +
+ TeleMetrum Outline and Hole Pattern + + This image, when printed, provides a precise template for the + mounting holes in TeleMetrum. 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. + + + + + + + + +
+ + -- cgit v1.2.3 From 8bd732ac9cb816630f46dd269448ff8422620df8 Mon Sep 17 00:00:00 2001 From: Keith Packard Date: Fri, 4 Apr 2014 23:40:22 -0700 Subject: doc: Outline files are now generated, so don't put them in git Signed-off-by: Keith Packard --- doc/easymini-outline.pdf | Bin 7047 -> 0 bytes doc/telemega-outline.pdf | Bin 7020 -> 0 bytes doc/telemetrum-outline.pdf | Bin 7097 -> 0 bytes 3 files changed, 0 insertions(+), 0 deletions(-) delete mode 100644 doc/easymini-outline.pdf delete mode 100644 doc/telemega-outline.pdf delete mode 100644 doc/telemetrum-outline.pdf (limited to 'doc') diff --git a/doc/easymini-outline.pdf b/doc/easymini-outline.pdf deleted file mode 100644 index 76a09957..00000000 Binary files a/doc/easymini-outline.pdf and /dev/null differ diff --git a/doc/telemega-outline.pdf b/doc/telemega-outline.pdf deleted file mode 100644 index 2f20c62f..00000000 Binary files a/doc/telemega-outline.pdf and /dev/null differ diff --git a/doc/telemetrum-outline.pdf b/doc/telemetrum-outline.pdf deleted file mode 100644 index af913520..00000000 Binary files a/doc/telemetrum-outline.pdf and /dev/null differ -- cgit v1.2.3 From ca66a035edecd7feffcd22257d3413ce0e189c07 Mon Sep 17 00:00:00 2001 From: Keith Packard Date: Sat, 5 Apr 2014 00:28:13 -0700 Subject: doc: Document new voltage beeping at startup time --- doc/altusmetrum.xsl | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) (limited to 'doc') diff --git a/doc/altusmetrum.xsl b/doc/altusmetrum.xsl index d3d1f72a..885c573e 100644 --- a/doc/altusmetrum.xsl +++ b/doc/altusmetrum.xsl @@ -1539,10 +1539,13 @@ NAR #88757, TRA #12200 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 - the altimeter completes initialization and self test, and decides - which mode to enter next. + At power on, the altimeter will beep out the battery voltage + to the nearest tenth of a volt. 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. Then there will be a short pause while 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 @@ -1570,7 +1573,7 @@ NAR #88757, TRA #12200 Startup S - dit dit dit + battery voltage in decivolts Calibrating sensors, detecting orientation. -- cgit v1.2.3 From 0bf1c74e83fe49a11916b52596363f4dd56c522c Mon Sep 17 00:00:00 2001 From: Keith Packard Date: Thu, 15 May 2014 23:10:54 -0600 Subject: doc: Document the Apogee Lockout setting Signed-off-by: Keith Packard --- doc/altusmetrum.xsl | 14 ++++++++++++++ 1 file changed, 14 insertions(+) (limited to 'doc') diff --git a/doc/altusmetrum.xsl b/doc/altusmetrum.xsl index 885c573e..39b3998a 100644 --- a/doc/altusmetrum.xsl +++ b/doc/altusmetrum.xsl @@ -2183,6 +2183,20 @@ NAR #88757, TRA #12200 way quite happily, including Keith's successful L3 cert.
+
+ Apogee Lockout + + Apogee lockout is the number of seconds after boost where + the flight computer will not fire the apogee charge, even if + the rocket appears to be at apogee. This is often called + 'Mach Delay', as it is intended to prevent a flight computer + from unintentionally firing apogee charges due to the pressure + spike that occurrs across a mach transition. Altus Metrum + flight computers include a Kalman filter which is not fooled + by this sharp pressure increase, and so this setting should + be left at the default value of zero to disable it. + +
Main Deployment Altitude -- cgit v1.2.3 From 47ff6f7528e3984012e874f91ea4f5c1d68cb465 Mon Sep 17 00:00:00 2001 From: Keith Packard Date: Wed, 28 May 2014 19:45:01 -0700 Subject: doc: Add outline of TeleGPS doc No actual content, mostly a place holder to make the build work Signed-off-by: Keith Packard --- doc/Makefile | 4 +- doc/telegps.xsl | 126 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 128 insertions(+), 2 deletions(-) create mode 100644 doc/telegps.xsl (limited to 'doc') diff --git a/doc/Makefile b/doc/Makefile index 1f47076c..05a49927 100644 --- a/doc/Makefile +++ b/doc/Makefile @@ -62,8 +62,8 @@ 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 \ +HTML=altusmetrum.html altos.html telemetry.html companion.html micropeak.html telegps.html $(RELNOTES) +PDF=altusmetrum.pdf altos.pdf telemetry.pdf companion.pdf micropeak.pdf telegps.pdf \ telemetrum-outline.pdf telemega-outline.pdf easymini-outline.pdf HTMLSTYLE=/usr/share/xml/docbook/stylesheet/docbook-xsl/html/docbook.xsl FOSTYLE=xorg-fo.xsl diff --git a/doc/telegps.xsl b/doc/telegps.xsl new file mode 100644 index 00000000..534b39a1 --- /dev/null +++ b/doc/telegps.xsl @@ -0,0 +1,126 @@ + + + + TeleGPS Owner's Manual + A recording GPS tracker + + + Keith + Packard + + + 2014 + Bdale Garbee and Keith Packard + + + + + + + + + This document is released under the terms of the + + Creative Commons ShareAlike 3.0 + + license. + + + + + 1.0 + 28 May 2014 + + Initial release with preliminary hardware. + + + + + + Acknowledgements + + Have fun using these products, and we hope to meet all of you + out on the rocket flight line somewhere. + +Bdale Garbee, KB0G +NAR #87103, TRA #12201 + +Keith Packard, KD7SQG +NAR #88757, TRA #12200 + + + + + Quick Start Guide + + TeleGPS is designed to be easy to use. Requiring no external + components, flying takes just a few steps. + + + + Handling Precautions + + All Altus Metrum products are sophisticated electronic devices. + When handled gently and properly installed in an air-frame, they + will deliver impressive results. However, as with all electronic + devices, there are some precautions you must take. + + + The Lithium polymer batteries have an + extraordinary power density. This is great because we can fly with + much less battery mass... but if they are punctured + or their contacts are allowed to short, they can and will release their + energy very rapidly! + Thus we recommend that you take some care when handling TeleGPS + to keep conductive material from coming in contact with the exposed metal elements. + + + As with all other rocketry electronics, Altus Metrum devices must + be protected from exposure to corrosive motor exhaust and ejection + charge gasses. + + + + Technical Information +
+ GPS Receiver + + TeleGPS uses the u-Blox Max-7Q GPS receiver. + +
+
+ Micro-controller + + TeleGPS uses an NXP LPC11U14 micro-controller. This tiny + CPU contains 32kB of flash for the application and 4kB of RAM for + temporary data storage. + +
+
+ Lithium Polymer Battery + + Shipping restrictions may prevent us from including a battery + battery with TeleGPS. + +
+
+ Mechanical Considerations + + TeleGPS is designed to be rugged enough for typical rocketry + applications. + +
+
+ On-board data storage + + TeleGPS has some bytes of non-volatile storage, separate + from the code storage memory. The TeleGPS firmware uses this + to store information about the last completed + flight. + +
+ + + -- cgit v1.2.3 From f59d69064763cfad2b4b15fd9660fd5fa21dba5e Mon Sep 17 00:00:00 2001 From: Keith Packard Date: Mon, 2 Jun 2014 23:43:54 -0700 Subject: doc: Create release notes for version 1.4 Signed-off-by: Keith Packard --- doc/Makefile | 3 +- doc/altusmetrum.xsl | 7 ++ doc/release-notes-1.4.xsl | 180 ++++++++++++++++++++++++++++++++++++++++++++++ 3 files changed, 189 insertions(+), 1 deletion(-) create mode 100644 doc/release-notes-1.4.xsl (limited to 'doc') diff --git a/doc/Makefile b/doc/Makefile index 05a49927..254e63c4 100644 --- a/doc/Makefile +++ b/doc/Makefile @@ -14,7 +14,8 @@ RELNOTES=\ release-notes-1.2.1.html \ release-notes-1.3.html \ release-notes-1.3.1.html \ - release-notes-1.3.2.html + release-notes-1.3.2.html \ + release-notes-1.4.html PICTURES=\ altosui.png \ diff --git a/doc/altusmetrum.xsl b/doc/altusmetrum.xsl index 39b3998a..f91ac191 100644 --- a/doc/altusmetrum.xsl +++ b/doc/altusmetrum.xsl @@ -5298,6 +5298,13 @@ NAR #88757, TRA #12200 Release Notes + + Version 1.4 + + Version 1.3.2 + + +
+ + Version 1.4 is a major release. It includes support for our new + TeleGPS product, new features and bug fixes in in the flight + software for all our boards and the AltosUI ground station + + + AltOS Firmware Changes + + + + Add support for TeleGPS boards. + + + + + Replace the 'dit dit dit' tones at startup with the current + battery voltage, measured in tenths of a volt. This lets you + check the battery voltage without needing telemetry, which + is especially useful on EasyMini. + + + + + Change state beeping to "Farnsworth spacing", which means + they're quite a bit faster than before, and so they take + less time to send. + + + + + Make the beeper tone configurable, making it possible to + distinguish between two Altus Metrum products in the same ebay. + + + + + Fix bug preventing the selection of the 'Flight State After' + mode in pyro configuration. + + + + + + AltosUI new features + + + + Add zooming and new content types (terrain and road maps) to + map view. Change map storage format from PNG to Jpeg, which + saves a huge amount of disk space. You will need to + re-download all of your pre-loaded map images. + + + + + Add a distance measuring device to the maps view. Select + this by using any button other than the left one, or by + pressing shift or control on the keyboard while using the + left button. + + + + + Add new 'Ignitor' tab to the flight monitor display for + TeleMega's extra ignitors. + + + + + Increase the width of data lines in the graphs to make them + easier to read. + + + + + Add additional ignitor firing marks and voltages to the + graph so you can see when the ignitors fired, along with + the ignitor voltages. + + + + + Add GPS course, ground speed and climb rate as optional + graph elements. + + + + + + AltosUI fixes + + + + When flashing new firmware, re-try opening the device as + sometimes it takes a while for the underlying operating + system to recognize that the device has rebooted in + preparation for the flashing operation. + + + + + Hide Tilt Angle in ascent tab for devices that don't have a gyro. + + + + + Filter out speed and acceleration spikes caused by ejection + charge firing when computing the maximum values. This + provides a more accurate reading of those maximums. + + + + + Fix EasyMini voltage displays. Early EasyMini prototypes + used a 3.0V regulator, and AltosUI still used that value as + the basis of the computation. Production EasyMini boards + have always shipped with a 3.3V regulator. Also, purple + EasyMini boards sensed the battery voltage past the blocking + diode, resulting in a drop of about 150mV from the true + battery voltage. Compensate for that when displaying the + value. + + + + + Display error message when trying to configure maximum + flight log size while the flight computer still has flight + data stored. + + + + + Handle TeleMetrum and TeleMini eeprom files generated with + pre-1.0 firmware. Those ancient versions didn't report the + log format, so just use the product name instead. + + + + + + TeleGPS Application + + + + New application designed for use with TeleGPS boards. + + + + + Shares code with AltosUI, mostly just trimmed down to focus + on TeleGPS-related functions. + + + + + + Documentation changes + + + + Re-create the drill template images; they should print + correctly from Firefox at least. Ship these as individual + PDF files so they're easy to print. + + + + + Add a description of the 'Apogee Lockout' setting, which + prevents the apogee charge from firing for a configurable + amount of time after boost. + + + + +
-- cgit v1.2.3 From 2182c49298e0862a60dea104450d5f74dbeaeeb2 Mon Sep 17 00:00:00 2001 From: Keith Packard Date: Wed, 11 Jun 2014 19:57:24 -0700 Subject: doc: Update 1.4 release notes to include a few more changes pyro firing time. flight erase on TeleMega/TeleMetrum v2 Signed-off-by: Keith Packard --- doc/release-notes-1.4.xsl | 29 ++++++++++++++++++++++++++--- 1 file changed, 26 insertions(+), 3 deletions(-) (limited to 'doc') diff --git a/doc/release-notes-1.4.xsl b/doc/release-notes-1.4.xsl index 43944bbd..71027599 100644 --- a/doc/release-notes-1.4.xsl +++ b/doc/release-notes-1.4.xsl @@ -9,7 +9,7 @@ software for all our boards and the AltosUI ground station - AltOS Firmware Changes + AltOS New Features @@ -37,16 +37,39 @@ distinguish between two Altus Metrum products in the same ebay. + + + Make the firing time for extra pyro channels configurable, + allowing longer (or shorter) than the default 50ms. + + + + + + AltOS Fixes + Fix bug preventing the selection of the 'Flight State After' mode in pyro configuration. + + + Fix bug where erasing flights would reset the flight number + to 2 on TeleMega and TeleMetrum v2. + + + + + Fix u-Blox GPS driver to mark course and speed data as being + present. + + - AltosUI new features + AltosUI New Features @@ -92,7 +115,7 @@ - AltosUI fixes + AltosUI Fixes -- cgit v1.2.3 From c7774114f7bc62e2100c7575b1dcf3536ed56343 Mon Sep 17 00:00:00 2001 From: Keith Packard Date: Wed, 11 Jun 2014 23:28:36 -0700 Subject: doc: Update altusmetrum docs and screen shots for 1.4 Signed-off-by: Keith Packard --- doc/altusmetrum.xsl | 124 +++++++++++++++++++++++++++++++++++++++++--- doc/ascent.png | Bin 64038 -> 55389 bytes doc/configure-altimeter.png | Bin 47817 -> 44924 bytes doc/configure-pyro.png | Bin 58478 -> 63276 bytes doc/descent.png | Bin 63566 -> 55624 bytes doc/graph-configure.png | Bin 48907 -> 45370 bytes doc/graph-map.png | Bin 991681 -> 443560 bytes doc/ignitor.png | Bin 0 -> 51104 bytes doc/landed.png | Bin 54003 -> 45642 bytes doc/launch-pad.png | Bin 84008 -> 74702 bytes doc/load-maps.png | Bin 390139 -> 520872 bytes doc/site-map.png | Bin 619391 -> 615711 bytes 12 files changed, 116 insertions(+), 8 deletions(-) create mode 100644 doc/ignitor.png (limited to 'doc') diff --git a/doc/altusmetrum.xsl b/doc/altusmetrum.xsl index f91ac191..de541147 100644 --- a/doc/altusmetrum.xsl +++ b/doc/altusmetrum.xsl @@ -2772,10 +2772,19 @@ NAR #88757, TRA #12200 dark blue for main, and black for landed. - The map's scale is approximately 3m (10ft) per pixel. The map + The map's default scale is approximately 3m (10ft) per pixel. The map can be dragged using the left mouse button. The map will attempt to keep the rocket roughly centered while data is being received. + + You can adjust the style of map and the zoom level with + buttons on the right side of the map window. You can draw a + line on the map by moving the mouse over the map with a + button other than the left one pressed, or by pressing the + left button while also holding down the shift key. The + length of the line in real-world units will be shown at the + start of the line. + Images are fetched automatically via the Google Maps Static API, and cached on disk for reuse. If map images cannot be downloaded, @@ -2787,6 +2796,24 @@ NAR #88757, TRA #12200 before you leave home; check out the 'Preload Maps' section below.
+
+ Ignitor + + + + + + + + + TeleMega includes four additional programmable pyro + channels. The Ignitor tab shows whether each of them has + continuity. If an ignitor has a low resistance, then the + voltage measured here will be close to the pyro battery + voltage. A value greater than 3.2V is required for a 'GO' + status. + +
Save Flight Data @@ -3053,7 +3080,21 @@ NAR #88757, TRA #12200
- Radio Frequency + Apogee Lockoug + + Apogee lockout is the number of seconds after boost where + the flight computer will not fire the apogee charge, even if + the rocket appears to be at apogee. This is often called + 'Mach Delay', as it is intended to prevent a flight computer + from unintentionally firing apogee charges due to the pressure + spike that occurrs across a mach transition. Altus Metrum + flight computers include a Kalman filter which is not fooled + by this sharp pressure increase, and so this setting should + be left at the default value of zero to disable it. + +
+
+ Frequency This configures which of the frequencies to use for both telemetry and packet command mode. Note that if you set this @@ -3111,12 +3152,11 @@ NAR #88757, TRA #12200
- Ignite Mode + Ignitor Firing Mode - TeleMetrum and TeleMini provide two igniter channels as they - were originally designed as dual-deploy flight - computers. This configuration parameter allows the two - channels to be used in different configurations. + This configuration parameter allows the two standard ignitor + channels (Apogee and Main) to be used in different + configurations. @@ -3186,6 +3226,16 @@ NAR #88757, TRA #12200
+
+ Beeper Frequency + + The beeper on all Altus Metrum flight computers works best + at 4000Hz, however if you have more than one flight computer + in a single airframe, having all of them sound at the same + frequency can be confusing. This parameter lets you adjust + the base beeper frequency value. + +
Configure Pyro Channels @@ -3211,6 +3261,11 @@ NAR #88757, TRA #12200 configuration values, so you can use different values for the same condition with different channels. + + At the bottom of the window, the 'Pyro Firing Time' + configuration sets the length of time (in seconds) which + each of these pyro channels will fire for. + Once you have selected the appropriate configuration for all of the necessary pyro channels, you can save the pyro @@ -3498,9 +3553,62 @@ NAR #88757, TRA #12200 and name of the site. The contents of this list are actually 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 - If the launch site isn't in the list, you can manually enter the lat/lon values + There are four different kinds of maps you can view; you can + select which to download by selecting as many as you like from + the available types: + + + Hybrid + + + A combination of satellite imagery and road data. This + is the default view. + + + + + Satellite + + + Just the satellite imagery without any annotation. + + + + + Roadmap + + + Roads, political boundaries and a few geographic features. + + + + + Terrain + + + Contour intervals and shading that show hills and + valleys. + + + + + + + You can specify the range of zoom levels to download; smaller + numbers show more area with less resolution. The default + level, 0, shows about 3m/pixel. One zoom level change + doubles or halves that number. + + + The Tile Radius value sets how large an area around the center + point to download. Each tile is 512x512 pixels, and the + 'radius' value specifies how many tiles away from the center + will be downloaded. Specify a radius of 0 and you get only the + center tile. A radius of 1 loads a 3x3 grid, centered on the + specified location. Clicking the 'Load Map' button will fetch images from Google diff --git a/doc/ascent.png b/doc/ascent.png index d486d19c..2d62f06e 100644 Binary files a/doc/ascent.png and b/doc/ascent.png differ diff --git a/doc/configure-altimeter.png b/doc/configure-altimeter.png index afb19325..514db3ed 100644 Binary files a/doc/configure-altimeter.png and b/doc/configure-altimeter.png differ diff --git a/doc/configure-pyro.png b/doc/configure-pyro.png index 1c6ae066..599d45b5 100644 Binary files a/doc/configure-pyro.png and b/doc/configure-pyro.png differ diff --git a/doc/descent.png b/doc/descent.png index 4ac4b962..5a7baadd 100644 Binary files a/doc/descent.png and b/doc/descent.png differ diff --git a/doc/graph-configure.png b/doc/graph-configure.png index d3374ba8..ed0d5112 100644 Binary files a/doc/graph-configure.png and b/doc/graph-configure.png differ diff --git a/doc/graph-map.png b/doc/graph-map.png index fd0fb134..bcea5ff8 100644 Binary files a/doc/graph-map.png and b/doc/graph-map.png differ diff --git a/doc/ignitor.png b/doc/ignitor.png new file mode 100644 index 00000000..d1f5aebe Binary files /dev/null and b/doc/ignitor.png differ diff --git a/doc/landed.png b/doc/landed.png index 777d2445..a58cfbf4 100644 Binary files a/doc/landed.png and b/doc/landed.png differ diff --git a/doc/launch-pad.png b/doc/launch-pad.png index a7a05c08..f2c41e6b 100644 Binary files a/doc/launch-pad.png and b/doc/launch-pad.png differ diff --git a/doc/load-maps.png b/doc/load-maps.png index dc7ea64c..ae98c9a5 100644 Binary files a/doc/load-maps.png and b/doc/load-maps.png differ diff --git a/doc/site-map.png b/doc/site-map.png index 755e7361..ebac1dfb 100644 Binary files a/doc/site-map.png and b/doc/site-map.png differ -- cgit v1.2.3 From e00ffe6ab6197ab48ba8ce3cf71a197f7215649f Mon Sep 17 00:00:00 2001 From: Keith Packard Date: Wed, 11 Jun 2014 23:28:55 -0700 Subject: doc: Add TeleGPS screenshots Signed-off-by: Keith Packard --- doc/telegps-configure.png | Bin 0 -> 31381 bytes doc/telegps-graph-configure.png | Bin 0 -> 28349 bytes doc/telegps-graph-graph.png | Bin 0 -> 103749 bytes doc/telegps-graph-map.png | Bin 0 -> 616540 bytes doc/telegps-graph-stats.png | Bin 0 -> 43041 bytes doc/telegps-info.png | Bin 0 -> 47633 bytes doc/telegps-map.png | Bin 0 -> 179593 bytes doc/telegps-table.png | Bin 0 -> 50901 bytes 8 files changed, 0 insertions(+), 0 deletions(-) create mode 100644 doc/telegps-configure.png create mode 100644 doc/telegps-graph-configure.png create mode 100644 doc/telegps-graph-graph.png create mode 100644 doc/telegps-graph-map.png create mode 100644 doc/telegps-graph-stats.png create mode 100644 doc/telegps-info.png create mode 100644 doc/telegps-map.png create mode 100644 doc/telegps-table.png (limited to 'doc') diff --git a/doc/telegps-configure.png b/doc/telegps-configure.png new file mode 100644 index 00000000..234723f3 Binary files /dev/null and b/doc/telegps-configure.png differ diff --git a/doc/telegps-graph-configure.png b/doc/telegps-graph-configure.png new file mode 100644 index 00000000..9270b155 Binary files /dev/null and b/doc/telegps-graph-configure.png differ diff --git a/doc/telegps-graph-graph.png b/doc/telegps-graph-graph.png new file mode 100644 index 00000000..314c2fdf Binary files /dev/null and b/doc/telegps-graph-graph.png differ diff --git a/doc/telegps-graph-map.png b/doc/telegps-graph-map.png new file mode 100644 index 00000000..1117d560 Binary files /dev/null and b/doc/telegps-graph-map.png differ diff --git a/doc/telegps-graph-stats.png b/doc/telegps-graph-stats.png new file mode 100644 index 00000000..7d4212b4 Binary files /dev/null and b/doc/telegps-graph-stats.png differ diff --git a/doc/telegps-info.png b/doc/telegps-info.png new file mode 100644 index 00000000..cc279b8f Binary files /dev/null and b/doc/telegps-info.png differ diff --git a/doc/telegps-map.png b/doc/telegps-map.png new file mode 100644 index 00000000..b21fb1a2 Binary files /dev/null and b/doc/telegps-map.png differ diff --git a/doc/telegps-table.png b/doc/telegps-table.png new file mode 100644 index 00000000..c1d2272f Binary files /dev/null and b/doc/telegps-table.png differ -- cgit v1.2.3 From 536db8d03aedb45698c42418c50a46d609fc98ad Mon Sep 17 00:00:00 2001 From: Keith Packard Date: Fri, 13 Jun 2014 22:04:35 -0700 Subject: doc: Add a bunch more stuff to the telegps docs Signed-off-by: Keith Packard --- doc/telegps-graph-configure.png | Bin 28349 -> 29487 bytes doc/telegps-graph-graph.png | Bin 103749 -> 103746 bytes doc/telegps-graph-map.png | Bin 616540 -> 604619 bytes doc/telegps-graph-stats.png | Bin 43041 -> 42796 bytes doc/telegps-location.png | Bin 0 -> 49996 bytes doc/telegps-map.png | Bin 179593 -> 490858 bytes doc/telegps-preferences.png | Bin 0 -> 24290 bytes doc/telegps-status.png | Bin 0 -> 49827 bytes doc/telegps-table.png | Bin 50901 -> 58663 bytes doc/telegps-v1.0-top.jpg | Bin 0 -> 370086 bytes doc/telegps.xsl | 892 +++++++++++++++++++++++++++++++++++++++- 11 files changed, 884 insertions(+), 8 deletions(-) create mode 100644 doc/telegps-location.png create mode 100644 doc/telegps-preferences.png create mode 100644 doc/telegps-status.png create mode 100644 doc/telegps-v1.0-top.jpg (limited to 'doc') diff --git a/doc/telegps-graph-configure.png b/doc/telegps-graph-configure.png index 9270b155..67eb5d91 100644 Binary files a/doc/telegps-graph-configure.png and b/doc/telegps-graph-configure.png differ diff --git a/doc/telegps-graph-graph.png b/doc/telegps-graph-graph.png index 314c2fdf..443ada07 100644 Binary files a/doc/telegps-graph-graph.png and b/doc/telegps-graph-graph.png differ diff --git a/doc/telegps-graph-map.png b/doc/telegps-graph-map.png index 1117d560..dddea22a 100644 Binary files a/doc/telegps-graph-map.png and b/doc/telegps-graph-map.png differ diff --git a/doc/telegps-graph-stats.png b/doc/telegps-graph-stats.png index 7d4212b4..d181ce55 100644 Binary files a/doc/telegps-graph-stats.png and b/doc/telegps-graph-stats.png differ diff --git a/doc/telegps-location.png b/doc/telegps-location.png new file mode 100644 index 00000000..e32b14cd Binary files /dev/null and b/doc/telegps-location.png differ diff --git a/doc/telegps-map.png b/doc/telegps-map.png index b21fb1a2..f5557ded 100644 Binary files a/doc/telegps-map.png and b/doc/telegps-map.png differ diff --git a/doc/telegps-preferences.png b/doc/telegps-preferences.png new file mode 100644 index 00000000..ca638825 Binary files /dev/null and b/doc/telegps-preferences.png differ diff --git a/doc/telegps-status.png b/doc/telegps-status.png new file mode 100644 index 00000000..dc338f07 Binary files /dev/null and b/doc/telegps-status.png differ diff --git a/doc/telegps-table.png b/doc/telegps-table.png index c1d2272f..b3c82e8d 100644 Binary files a/doc/telegps-table.png and b/doc/telegps-table.png differ diff --git a/doc/telegps-v1.0-top.jpg b/doc/telegps-v1.0-top.jpg new file mode 100644 index 00000000..ac122f26 Binary files /dev/null and b/doc/telegps-v1.0-top.jpg differ diff --git a/doc/telegps.xsl b/doc/telegps.xsl index 534b39a1..4165065c 100644 --- a/doc/telegps.xsl +++ b/doc/telegps.xsl @@ -15,7 +15,7 @@ - + @@ -29,10 +29,10 @@ - 1.0 - 28 May 2014 + 1.4 + 13 June 2014 - Initial release with preliminary hardware. + Initial release @@ -57,6 +57,31 @@ NAR #88757, TRA #12200 TeleGPS is designed to be easy to use. Requiring no external components, flying takes just a few steps. + + First, download and install the software from . This will make sure that + you have the right device drivers installed. + + + Next, plug in the battery and USB cable and connect TeleGPS to + your computer. This will charge the battery and allow you to + configure the device. + + + Start the TeleGPS application and set the callsign and frequency + on your TeleGPS device; refer to the Configure TeleGPS section + in the TeleGPS Application chapter for instructions. + + + Unplug TeleGPS when the battery charger light goes green. This + will enable the radio and logging portions of the TeleGPS + firmware. + + + Connect TeleDongle to your computer and start TeleGPS or start + AltosDroid on your android device and connect to TeleBT. Set the + frequency to match the TeleGPS and you should be receiving telemetry. + Handling Precautions @@ -81,6 +106,858 @@ NAR #88757, TRA #12200 charge gasses. + + TeleGPS Hardware +
+ Hooking Up Lithium Polymer Batteries + + TeleGPS has a two pin JST PH series connector to connect up + a single-cell Lithium Polymer cell (3.7V nominal). You can + purchase matching batteries from the Altus Metrum store, or + other vendors, or you can make your own. Pin 1 of the + connector is positive, pin 2 is negative. Spark Fun sells a + cable with the connector attached, which they call a JST Jumper 2 + Wire Assembly. + + + Many RC vendors also sell lithium polymer batteries with + this same connector. All that we have found use the opposite + polarity, and if you use them that way, you will damage or + destroy TeleGPS. + +
+
+ On-board Data Recording + + TeleGPS logs GPS data at a user-configurable rate. Data are + logged to a 2MB on-board flash memory part, which can be + partitioned into several equal-sized blocks, one for each + flight. 64kB of this storage are reserved to hold + configuration data, leaving 1984kB for flight data. + + + 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. + + + To compute the amount of space needed for a single log, you + can divide the expected time (in seconds) by the sample period + (by default, 1 second per sample) and then multiply the result + by 32 bytes per sample. For instance, a sample period of 1 + second and a flight lasting one hour will take 32 * 3600 = + 115200 bytes. TeleGPS does try to reduce log space used by not + recording position information when it isn't moving, so actual + space consumed may be less than this. + + + The default size allows for four flights of 496kB each, which + provides over four hours of logging at 1 sample per second. + + + TeleGPS will not overwrite existing flight data, so be sure to + download flight data and erase it from the onboard flash + before it fills up. TeleGPS will still report telemetry even + if memory is full, so the only thing you will lose is the + on-board data log. + +
+
+ Installation + + 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. + + + TeleGPS uses an integrate GPS patch antenna and won't + receive GPS signals if installed inside a metal or carbon + fiber compartment. Test GPS reception and telemetry + transmission with the system installed and all other + electronics powered up to verify signal reception and make + sure there isn't any interference from other systems. + +
+ + + System Operation +
+ GFSK Telemetry + + TeleGPS's native telemetry system doesn't use a 'normal packet + radio' mode like APRS because it's not very efficient. 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. + +
+
+ APRS + + TeleGPS can send APRS if desired, and the + interval between APRS packets can be configured. As each APRS + packet takes a full second to transmit, we recommend an + interval of at least 5 seconds to avoid consuming too much + battery power or radio channel bandwidth. You can configure + the APRS interval using AltosUI; that process is described in + the Configure Altimeter section of the AltosUI chapter. + + + AltOS uses the APRS compressed position report data format, + which provides for higher position precision and shorter + packets than the original APRS format. It also includes + altitude data, which is invaluable when tracking rockets. We + haven't found a receiver which doesn't handle compressed + positions, but it's just possible that you have one, so if you + have an older device that can receive the raw packets but + isn't displaying position information, it's possible that this + is the cause. + + + The APRS packet format includes a comment field that can have + arbitrary text in it. AltOS uses this to send status + information about the flight computer. It sends four fields as + shown in the following table. + + + Altus Metrum APRS Comments + + + + + + + + Field + Example + Description + + + + + 1 + L + GPS Status U for unlocked, L for locked + + + 2 + 6 + Number of Satellites in View + + + 3 + B4.0 + Battery Voltage + + + +
+ + Here's an example of an APRS comment showing GPS lock with 6 + satellites in view and a battery at 4.0V. + + L6 B4.0 + + + + Make sure your primary battery is above 3.8V and GPS is locked + with at least 5 or 6 satellites in view before starting. If GPS + is switching between L and U regularly, then it doesn't have a + good lock and you should wait until it becomes stable. + + + If the GPS receiver loses lock, the APRS data transmitted will + contain the last position for which GPS lock was + available. You can tell that this has happened by noticing + that the GPS status character switches from 'L' to 'U'. Before + GPS has locked, APRS will transmit zero for latitude, + longitude and altitude. + +
+
+ Configurable Parameters + + Configuring TeleGPS is very + simple; the few configurable parameters can all be set + using the TeleGPS application over USB. Read + the Configure TeleGPS section in the TeleGPS Software chapter below + for more information. + +
+ Radio Frequency + + 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 + 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 + frequency will be used to avoid interference. And of course, both + TeleGPS and the receiver must be configured to the same + frequency to successfully communicate with each other. + +
+
+ Callsign + + This sets the callsign used for telemetry and APRS to + identify the device. + +
+
+ Telemetry/RDF/APRS Enable + + You can completely disable the radio, if necessary, leaving + TeleGPS only logging data to internal memory. + +
+
+ APRS Interval + + This selects how often APRS packets are transmitted. Set + this to zero to disable APRS without also disabling the + regular telemetry and RDF transmissions. As APRS takes a + full second to transmit a single position report, we + recommend sending packets no more than once every 5 seconds. + +
+
+ Maximum Flight Log + + 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. + +
+
+ Logging Trigger Motion + + If TeleGPS moves less than this distance over a long period + of time, it will not log that location, saving storage space. + +
+
+ Position Reporting Interval + + This sets how often TeleGPS reports position information via + telemetry and to the on-board log. Reducing this value will + save power and logging memory consumption. + +
+
+ + + TeleGPS Application + + The TeleGPS application provides a graphical user interface for + interacting with the Altus Metrum product family. TeleGPS can + monitor telemetry data, configure devices and many other + tasks. The primary interface window is for displaying data + received over the telemetry link. There are additional + tasks available from the main window menu bar. This chapter + is split into sections, each of which documents one of the tasks + provided from the top-level toolbar. + +
+ Telemetry Monitoring + + This is the window brought up when you start the + application. If you have a TeleDongle device connected to the + computer, it will automatically be selected for telemetry monitoring + + + All telemetry data received are automatically recorded in + suitable log files. The name of the files includes the current + date and TeleGPS serial and flight numbers. + + + The radio frequency being monitored by the TeleDongle device + is displayed at the top of the window. You can configure the + frequency by clicking on the frequency box and selecting the + desired frequency. The TeleGPS application remembers the last + frequency selected for each TeleDongle and selects that + automatically the next time you use that device. + + + Below the TeleDongle frequency selector, the window contains a few + significant pieces of information about the altimeter providing + the telemetry data stream: + + + + The configured call-sign + + + The device serial number + + + The flight number. TeleGPS remembers how many + times it has flown. + + + + + The Received Signal Strength Indicator value. This lets + you know how strong a signal TeleDongle is receiving. The + radio inside TeleDongle operates down to about -100dBm; + weaker signals may not be receivable. The packet link uses + error detection and correction techniques which prevent + incorrect data from being reported. + + + + + The age of the displayed data, in seconds since the last + successfully received telemetry packet. In normal operation + this will stay in the low single digits. If the number starts + counting up, then you are no longer receiving data over the radio + link from the flight computer. + + + + + Finally, the largest portion of the window contains a set of + tabs, each of which contain some information about the TeleGPS + board. The final 'table' tab displays many of the raw telemetry + values in one place in a spreadsheet-like format. + +
+ Map + + The Map tab shows the TeleGPS track over time on top of map + data making it easy to locate the device. + + + + + + + + + + The map's default scale is approximately 3m (10ft) per pixel. The map + can be dragged using the left mouse button. The map will attempt + to keep the rocket roughly centered while data is being received. + + + You can adjust the style of map and the zoom level with + buttons on the right side of the map window. You can draw a + line on the map by moving the mouse over the map with a + button other than the left one pressed, or by pressing the + left button while also holding down the shift key. The + length of the line in real-world units will be shown at the + start of the line. + + + Images are fetched automatically via the Google Maps Static API, + and cached on disk for reuse. If map images cannot be downloaded, + the rocket's path will be traced on a dark gray background + instead. + + + You can pre-load images for your favorite launch sites + before you leave home; check out the 'Preload Maps' section below. + +
+
+ Location + + The Location tab shows the raw GPS data received from TeleGPS. + + + + + + + + +
+
+ Status + + The Status tab shows data relative to the location of + TeleGPS when the application first received telemetry from + it. + + + + + + + + +
+
+ Table + + The Table tab shows detailed information about the GPS + receiver + + + + + + + + +
+
+ +
+ TeleGPS Menus + + TeleGPS has three or four menus at the top of the window: + + + File + + + New Window, Graph Data, Export Data, Load Maps, Preferences, Close and Exit + + + + + Monitor + + + Connect Device, Disconnect and Scan Channels + + + + + Device + + + Download Data, Configure Device and Flash Device + + + + + Frequency + + + This shows the current monitoring frequency with a + drop-down menu listing other configured + frequencies. You can change the set of frequencies + shown here from the Preferences dialog. This menu is + only shown when the TeleGPS application is connected + to a TeleDongle or TeleBT device. + + + + + +
+ New Window + + This creates another telemetry monitoring window, in case + you have multiple TeleDongle devices connected to the + computer. + +
+
+ Graph Data + + This brings up a file dialog to load a saved log, either + a .telem file of recorded telemetry or .eeprom of saved + data from on-board memory. It looks a bit like the flight + monitoring window, using a selection of tabs to show + different views of the saved data. + +
+ Graph + + The Graph tab shows a plot of the the GPS data + collected. The X axis is time in seconds; there are a + variety of Y axes available for different kinds of data. + + + + + + + + +
+
+ Configure Graph + + + + + + + + + This selects which graph elements to show, and, at the + bottom, lets you switch between metric and imperial units + +
+
+ Statistics + + + + + + + + + Shows overall data computed from the flight. + +
+
+ Map + + + + + + + + + Shows a map of the area overlaid with the GPS track. As with + the telemetry monitoring window, you can select the style + of map and zoom level using buttons along the side; + you can scroll the map by dragging within the map pressing + the left button and you can draw a line to measure + distances using either the left button with the shift key, + or any other button. + +
+
+
+ Export Data + + 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 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. + +
+ Comma Separated Value Format + + This is a text file containing the data in a form suitable for + import into a spreadsheet or other external data analysis + tool. The first few lines of the file contain the version and + configuration information from TeleGPS, then + there is a single header line which labels all of the + fields. All of these lines start with a '#' character which + many tools can be configured to skip over. + + + The remaining lines of the file contain the data, with each + field separated by a comma and at least one space. All of + the sensor values are converted to standard units, with the + barometric data reported in both pressure, altitude and + height above pad units. + +
+
+ Keyhole Markup Language (for Google Earth) + + This is the format used by Google Earth to provide an overlay + within that application. With this, you can use Google Earth to + see the whole flight path in 3D. + +
+
+
+ Load Maps + + + + + + + + + Before using TeleGPS, you can use Load Maps to load map data + in case you don't have access to the internet while + receiving telemetry. + + + There's a drop-down menu of rocket 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 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 + + + There are four different kinds of maps you can view; you can + select which to download by selecting as many as you like from + the available types: + + + Hybrid + + + A combination of satellite imagery and road data. This + is the default view. + + + + + Satellite + + + Just the satellite imagery without any annotation. + + + + + Roadmap + + + Roads, political boundaries and a few geographic features. + + + + + Terrain + + + Contour intervals and shading that show hills and + valleys. + + + + + + + You can specify the range of zoom levels to download; smaller + numbers show more area with less resolution. The default + level, 0, shows about 3m/pixel. One zoom level change + doubles or halves that number. + + + The Tile Radius value sets how large an area around the center + point to download. Each tile is 512x512 pixels, and the + 'radius' value specifies how many tiles away from the center + will be downloaded. Specify a radius of 0 and you get only the + center tile. A radius of 1 loads a 3x3 grid, centered on the + specified location. + + + Clicking the 'Load Map' button will fetch images from Google + Maps; note that Google limits how many images you can fetch at + once, so if you load more than one launch site, you may get + some gray areas in the map which indicate that Google is tired + of sending data to you. Try again later. + +
+
+ Preferences + + + + + + + +
+ Voice Settings + + AltosUI provides voice announcements during flight so that you + can keep your eyes on the sky and still get information about + 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 + + + + +
+
+ Log Directory + + AltosUI logs all telemetry data and saves all TeleMetrum flash + data to this directory. This directory is also used as the + staring point when selecting data files for display or export. + + + Click on the directory name to bring up a directory choosing + dialog, select a new directory and click 'Select Directory' to + change where AltosUI reads and writes data files. + +
+
+ Callsign + + This value is transmitted in each command packet sent from + TeleDongle and received from an altimeter. It is not used in + telemetry mode, as the callsign configured in the altimeter board + is included in all telemetry packets. Configure this + 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 + + This switches between metric units (meters) and imperial + units (feet and miles). This affects the display of values + 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. + +
+
+ Serial Debug + + This causes all communication with a connected device to be + dumped to the console from which AltosUI was started. If + you've started it from an icon or menu entry, the output + will simply be discarded. This mode can be useful to debug + various serial communication issues. + +
+
+ Font Size + + Selects the set of fonts used in the flight monitor + window. Choose between the small, medium and large sets. + +
+
+ Look & Feel + + Adjust the style of the windows. By default, the TeleGPS + application attempts to blend in with the native style. + +
+
+ Manage Frequencies + + This brings up a dialog where you can configure the set of + frequencies shown in the various frequency menus. You can + add as many as you like, or even reconfigure the default + set. Changing this list does not affect the frequency + settings of any devices, it only changes the set of + frequencies shown in the menus. + +
+
+
+ Close + + This closes the current window, leaving any other windows + open and the application running. + +
+
+ Exit + + This closes all TeleGPS windows and terminates the application. + +
+
+ Connect Device + + Selecting this item brings up a dialog box listing all of + the connected TeleDongle devices. When you choose one of + these, AltosUI will display telemetry data as received by + the selected TeleDongle device. + + + + + + + + +
+
+ Disconnect + + Disconnects the currently connected TeleDongle or TeleBT + +
+
+ Scan Channels + + +
+
+ Download Data + + + +
+
+ Configure Device + + + +
+
+ Flash Device + + + +
+
+ Technical Information
@@ -114,10 +991,9 @@ NAR #88757, TRA #12200
On-board data storage - TeleGPS has some bytes of non-volatile storage, separate - from the code storage memory. The TeleGPS firmware uses this - to store information about the last completed - flight. + TeleGPS has 2MB of non-volatile storage, separate from the + code storage memory. The TeleGPS firmware uses this to log + information during flight.
-- cgit v1.2.3 From ae7084f5199318dc6582e212492a50cfda1cebb8 Mon Sep 17 00:00:00 2001 From: Keith Packard Date: Fri, 13 Jun 2014 22:36:00 -0700 Subject: doc: TeleGPS docs are complete All TeleGPS features should now be documented to some degree Signed-off-by: Keith Packard --- doc/telegps-configure.png | Bin 31381 -> 32472 bytes doc/telegps-preferences.png | Bin 24290 -> 22445 bytes doc/telegps-scan.png | Bin 0 -> 9852 bytes doc/telegps.xsl | 303 +++++++++++++++++++++++++++++++++++++++++++- 4 files changed, 300 insertions(+), 3 deletions(-) create mode 100644 doc/telegps-scan.png (limited to 'doc') diff --git a/doc/telegps-configure.png b/doc/telegps-configure.png index 234723f3..56cb2031 100644 Binary files a/doc/telegps-configure.png and b/doc/telegps-configure.png differ diff --git a/doc/telegps-preferences.png b/doc/telegps-preferences.png index ca638825..ad14fd8d 100644 Binary files a/doc/telegps-preferences.png and b/doc/telegps-preferences.png differ diff --git a/doc/telegps-scan.png b/doc/telegps-scan.png new file mode 100644 index 00000000..9b19e685 Binary files /dev/null and b/doc/telegps-scan.png differ diff --git a/doc/telegps.xsl b/doc/telegps.xsl index 4165065c..4b6d8cae 100644 --- a/doc/telegps.xsl +++ b/doc/telegps.xsl @@ -936,26 +936,323 @@ NAR #88757, TRA #12200
Scan Channels + Scans the configured set of frequencies looking for + telemetry signals. A list of all of the discovered signals + is show; selecting one of those and clicking on 'Monitor' + will select that frequency in the associated TeleGPS + application window. + + + + + + +
Download Data - + TeleGPS records data to its internal flash memory. + On-board data is recorded at the same rate as telemetry + but is not subject to radio drop-outs. As + such, it generally provides a more complete and precise record. + The 'Download Data' menu entry allows you to read the + flash memory and write it to disk. + + + Select the 'Download Data' menu entry to bring up a list of + connected TeleGPS devices. After the device has been + selected, a dialog showing the data stored in the + device will be shown allowing you to select which entries to + download and which to delete. You must erase flights in order for the space they + consume to be reused by another track. This prevents + accidentally losing data if you neglect to download + data before starting TeleGPS again. Note that if there is no more + space available in the device, then no data will be recorded. + + + The file name for each data log is computed automatically + from the recorded date, altimeter serial number and flight + number information.
Configure Device + + + + + + + + + Select this button and then select any connected TeleGPS + device from the list provided. + + + The first few lines of the dialog provide information about the + connected device, including the product name, + software version and hardware serial number. Below that are the + individual configuration entries. + + + 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. This will restart logging for + a new flight number, if any log information has been + saved for the current flight. + + + + + Close + + + This closes the dialog. Any unsaved changes will be + lost. + + + + - + The rest of the dialog contains the parameters to be configured. +
+ Frequency + + 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, the TeleDongle frequency will + also be automatically reconfigured to match so that + communication will continue afterwards. + +
+
+ RF Calibration + + The radios in every Altus Metrum device are calibrated at the + factory to ensure that they transmit and receive on the + specified frequency. If you need to you can adjust the calibration + by changing this value. Do not do this without understanding what + the value means, read the appendix on calibration and/or the source + code for more information. To change a TeleDongle's calibration, + 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 (in + seconds). When set to zero, APRS transmission is + disabled. 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 + + This sets the call sign included in each telemetry packet. Set this + as needed to conform to your local radio regulations. + +
+
+ Maximum Log Size + + This sets the space (in kilobytes) allocated for each data + log. The available space will be divided into chunks of this + size. A smaller value will allow more logs to be stored, + a larger value will record data for longer times. + +
+
+ Logging Trigger Motion + + If TeleGPS moves less than this distance over a long period + of time, it will not log that location, saving storage space. + +
+
+ Position Reporting Interval + + This sets how often TeleGPS reports position information via + telemetry and to the on-board log. Reducing this value will + save power and logging memory consumption. + +
Flash Device - + This reprograms TeleGPS devices with new firmware. Please + read the directions for flashing devices in the Updating + Device Firmware chapter below. + +
+
+ + + Updating Device Firmware + + TeleGPS is programmed directly over its USB connectors. + + + You may wish to begin by ensuring you have current firmware images. + These are distributed as part of the TeleGPS software bundle that + also includes the TeleGPS ground station program. Newer ground + station versions typically work fine with older firmware versions, + so you don't need to update your devices just to try out new + software features. You can always download the most recent + version from . + +
+ + Updating TeleGPS 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 TeleGPS, and select 'Flash Device' from the Device menu. + + + + + Select the target device in the Device Selection dialog. + + + + + 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 TeleGPS-v1.0-1.4.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. + + + +
-- cgit v1.2.3 From 90e03dfc8534fc4fc25f6a5ee9ec109b98baa238 Mon Sep 17 00:00:00 2001 From: Bdale Garbee Date: Sun, 15 Jun 2014 17:28:02 -0600 Subject: document mounting hole size for TeleGPS --- doc/telegps.xsl | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'doc') diff --git a/doc/telegps.xsl b/doc/telegps.xsl index 4b6d8cae..836c3d9a 100644 --- a/doc/telegps.xsl +++ b/doc/telegps.xsl @@ -1282,7 +1282,8 @@ NAR #88757, TRA #12200 Mechanical Considerations TeleGPS is designed to be rugged enough for typical rocketry - applications. + applications. The 4 mounting holes on the board are sized for + use with 4-40 or M3 screws.
-- cgit v1.2.3 From 79c3dc334d79eacd63bbbbec046fc2c31266560c Mon Sep 17 00:00:00 2001 From: Bdale Garbee Date: Sun, 15 Jun 2014 17:40:27 -0600 Subject: tweaks --- doc/release-notes-1.4.xsl | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'doc') diff --git a/doc/release-notes-1.4.xsl b/doc/release-notes-1.4.xsl index 71027599..2893f1aa 100644 --- a/doc/release-notes-1.4.xsl +++ b/doc/release-notes-1.4.xsl @@ -40,7 +40,8 @@ Make the firing time for extra pyro channels configurable, - allowing longer (or shorter) than the default 50ms. + allowing longer (or shorter) than the default 50ms. Only relevant + for TeleMega at this time. -- cgit v1.2.3 From 97a7cbaee806965ca7c696fb02f6e1d24b026b9b Mon Sep 17 00:00:00 2001 From: Bdale Garbee Date: Sun, 15 Jun 2014 17:43:06 -0600 Subject: add release to revision history --- doc/altusmetrum.xsl | 7 +++++++ 1 file changed, 7 insertions(+) (limited to 'doc') diff --git a/doc/altusmetrum.xsl b/doc/altusmetrum.xsl index de541147..5ccbee9f 100644 --- a/doc/altusmetrum.xsl +++ b/doc/altusmetrum.xsl @@ -40,6 +40,13 @@ + + 1.4 + 15 June 2014 + + Major release adding TeleGPS support. + + 1.3.2 24 January 2014 -- cgit v1.2.3