mjb/altos/ao_flight.c, branch sn4-flight2

Accelerometer-based velocity values are invalid after apogee

2009-05-13T18:00:43+00:00

Because the orientation of the flight computer relative to the ground is unknown after apogee, the accelerometer data cannot be integrated to compute velocity. Main deploy is now based purely on barometric altitude and landing detection no longer checks for a low velocity value. Signed-off-by: Keith Packard

Add velocity check for boost detect via accelerometer

2009-05-13T17:59:04+00:00

Bumping the rocket can cause a brief period of high acceleration, which may cause a mistaken boost detection. Require both a high acceleration and reasonable velocity to trigger boost phase. Signed-off-by: Keith Packard

Don't re-initialize the landing range data at each apogee detect sample

2009-05-11T06:01:16+00:00

The landing range values are used only after apogee detect, so we need only initialize them on the transition from apogee to drogue. Signed-off-by: Keith Packard

Initialize ao_min_vel with |ao_flight_vel|

2009-05-11T06:00:06+00:00

As ao_min_vel is stored as an absolute value, it's important to preserve that invariant, even though we don't expect ao_flight_vel to be negative at coast. Signed-off-by: Keith Packard

Decrease telemetry rate on the pad to 1/sec instead of 20/sec

2009-05-11T05:58:31+00:00

Transmitting telemetry through the radio consumes a significant amount of battery; reducing the rate to 1/sec will reduce power usage while waiting for launch. Signed-off-by: Keith Packard

Increase the initial accel/baro average to 1000 samples

2009-05-11T05:57:19+00:00

To get an accurate baseline of the launchpad state, take a longer average of the two sensors as the unit boots up. Signed-off-by: Keith Packard

Reset landing interval tests at apogee

2009-04-30T00:42:26+00:00

This moves all of the interval management into the landing test code and out of the main loop. The interval is reset at apogee to make sure the sensors produce a stable reading for at least 20 seconds

Make sure full log is written and flushed on landing.

2009-04-26T08:37:02+00:00

The final state change to landing is recorded in the logging thread, so have that turn off logging once it has recorded that state. Then make it go to sleep.

Add configuration support

2009-04-26T07:11:32+00:00

Current config variables: Main deploy altitude above launch (in meters) Acceleration zero g calibration (manual or automatic) Radio channel (freq = 435.550MHz + channel * 100kHz) Callsign (max 8 characters) Supporting this involved shuffling code around so that the non-telemetrum builds could include only the stuff they needed.

Allow for slower ADC operation. Add power saving code.

2009-04-25T21:44:33+00:00

This tries to make the flight computer use less power by disabling USB in flight mode, lowering the telemetry rate after ascent. It also disables the RDF beacon during ascent and re-enables it once descent has started.