X-Git-Url: https://git.gag.com/?p=fw%2Faltos;a=blobdiff_plain;f=doc%2Faltusmetrum.xsl;h=d96e8f4fb585afb3eab3c4fea566479925a93d12;hp=dfe89438f99398eebbcaf35b3c0a18e7f9641e8b;hb=9c4674d90f9b111e1b47abb7aee714ed12fa3aa5;hpb=e44ce127ece149e7b07be49142bc0f9d50bbe97d diff --git a/doc/altusmetrum.xsl b/doc/altusmetrum.xsl index dfe89438..d96e8f4f 100644 --- a/doc/altusmetrum.xsl +++ b/doc/altusmetrum.xsl @@ -22,7 +22,7 @@ Towns - 2013 + 2014 Bdale Garbee and Keith Packard @@ -35,6 +35,21 @@ + + 1.3.2 + 24 January 2014 + + Bug fixes for TeleMega and AltosUI. + + + + 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 @@ -835,17 +850,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 +1004,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 @@ -1364,7 +1593,7 @@ NAR #88757, TRA #12200 - + @@ -1389,7 +1618,7 @@ NAR #88757, TRA #12200 - + @@ -1573,10 +1802,10 @@ NAR #88757, TRA #12200 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 @@ -1801,7 +2030,7 @@ NAR #88757, TRA #12200 - + @@ -1823,7 +2052,7 @@ NAR #88757, TRA #12200 - + @@ -1838,7 +2067,7 @@ NAR #88757, TRA #12200 - + @@ -1851,7 +2080,7 @@ NAR #88757, TRA #12200 - + @@ -1908,7 +2137,7 @@ NAR #88757, TRA #12200 - + @@ -2165,7 +2394,7 @@ NAR #88757, TRA #12200 - + @@ -2275,7 +2504,7 @@ NAR #88757, TRA #12200 - + @@ -2370,7 +2599,7 @@ NAR #88757, TRA #12200 - + @@ -2384,8 +2613,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 @@ -2404,7 +2633,7 @@ NAR #88757, TRA #12200 - + @@ -2422,7 +2651,7 @@ NAR #88757, TRA #12200 - + @@ -3972,11 +4201,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, @@ -4233,6 +4463,20 @@ NAR #88757, TRA #12200 Release Notes + + Version 1.3.2 + + + + Version 1.3.1 + + Version 1.3