X-Git-Url: https://git.gag.com/?p=fw%2Faltos;a=blobdiff_plain;f=doc%2Faltusmetrum.xsl;h=a6d2ff12c415bae517a93c9a072c7060a31dbc1f;hp=8725da0447aed36f4fbc27ea37a90d798b2c4803;hb=63171339c03cf9bf3d691511889223bf43024124;hpb=e4b223df372348718b74d2ecad4957f3e30f8d79 diff --git a/doc/altusmetrum.xsl b/doc/altusmetrum.xsl index 8725da04..a6d2ff12 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 @@ -40,6 +35,14 @@ + + 1.3.1 + 21 January 2014 + + Bug fixes for TeleMega and TeleMetrum v2.0 along with a few + small UI improvements. + + 1.3 12 November 2013 @@ -551,11 +554,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 +576,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 +597,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 +614,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 +630,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, @@ -830,17 +843,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. @@ -857,6 +997,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 @@ -1356,6 +1583,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 +1599,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 +1608,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 +1683,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,16 +1782,23 @@ NAR #88757, TRA #12200
Ascent + + + + + + + This tab is shown during Boost, Fast and Coast phases. The information displayed here helps monitor the rocket as it heads towards apogee. - The height, speed and acceleration are shown along with the - maximum values for each of them. This allows you to quickly - answer the most commonly asked questions you'll hear during - flight. + The height, speed, acceleration and tilt are shown along + with the maximum values for each of them. This allows you to + quickly answer the most commonly asked questions you'll hear + during flight. The current latitude and longitude reported by the GPS are @@ -1565,6 +1815,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 +1858,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 +1900,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 +2009,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 +2039,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 +2127,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 +2350,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 +2384,13 @@ NAR #88757, TRA #12200
Configure AltosUI + + + + + + + This button presents a dialog so that you can configure the AltosUI global settings. @@ -2075,18 +2402,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 +2494,13 @@ NAR #88757, TRA #12200
Configure Groundstation + + + + + + + Select this button and then select a TeleDongle Device from the list provided. @@ -2246,46 +2586,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 @@ -2296,8 +2606,8 @@ NAR #88757, TRA #12200 Selecting the 'Fire Igniter' button brings up the usual device selection dialog. Pick the desired device. This brings up another - window which shows the current continuity test status for both - apogee and main charges. + window which shows the current continuity test status for all + of the pyro channels. Next, select the desired igniter to fire. This will enable the @@ -2313,6 +2623,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 +2641,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 @@ -3870,11 +4194,12 @@ NAR #88757, TRA #12200 Then, divide 434.550 MHz by the measured frequency and multiply by the current radio cal value show in the 'c s' command. For an unprogrammed board, the default value - is 1186611. Take the resulting integer and program it using the 'c f' + is 1186611 for cc1111 based products and 7119667 for cc1120 + based products. Take the resulting integer and program it using the 'c f' 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 configuration memory. Note that the 'reboot' command, which is very useful on the altimeters, @@ -3978,11 +4303,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 +4317,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 +4331,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 +4345,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. - - - - - + + + + + + +
@@ -4123,6 +4456,13 @@ NAR #88757, TRA #12200 Release Notes + + Version 1.3.1 + + Version 1.3