mjb/altos/src/kernel, branch 1.8.1.1

altos: Don't compute filtered average of height error when HAS_ACCEL

2017-08-28T07:22:43+00:00

We only use this for baro-only devices to avoid firing drogue charges at mach transitions; we trust the combination of accel+baro to do the right thing when available. Signed-off-by: Keith Packard

altos: Don't eliminate baro above mach speed, just trust it less

2017-08-28T00:40:40+00:00

Instead of completely eliminating the baro sensor above mach speed, just derate it a bit so that the accel will dominate for speed computation and keep the device from false-triggering across mach transitions. When we completely ignored the baro sensor above mach, and the flight spent considerable time in that speed range, then the estimated height could be far from the real value. When the estimated speed dropped back down and the baro values were brought back into the computation, then the resulting rapid shift in estimated speed could trigger accidental apogee detection. By mixing in a bit of baro data even above mach, we keep the estimated height closer to the baro value and prevent this error, at least in flights measured so far. The flight known to have this problem is: 2015-09-26-serial-2093-flight-0012.eeprom Signed-off-by: Keith Packard

altos: Eliminate separate height error filter for accelerometer devices

2017-08-28T00:40:40+00:00

We don't use the error value in flight for those models anyways; it's only useful on baro-only hardware. Signed-off-by: Keith Packard

altos: Perform time comparisons using 16-bit arithmetic to handle wrap

2017-08-28T00:38:58+00:00

Subtracting two 16-bit unsigned values to perform time comparisons yields mystic results unless we carefully cast that to int16_t. Signed-off-by: Keith Packard

Merge branch 'master' of ssh://git.gag.com/scm/git/fw/altos

2017-07-21T23:44:03+00:00

clean up telefireone name references

2017-07-21T23:43:38+00:00

altos: Create separate log format for EasyMini v2.0

2017-06-12T05:54:22+00:00

The ADC in the STM32F0 is different than the LPC, with a range of 0-4095 instead of 0-32767. Signed-off-by: Keith Packard

altos: HMC5883 output order is X Z Y

2017-06-12T05:54:22+00:00

Re-label everything to have the correct names. This doesn't actually change the code at all, so the eeprom and telemetry is all compatible. Matching changes on the host side will be required to actually process the data correctly, of course. Signed-off-by: Keith Packard

telefiretwo: don't try to record pre-burn sensor values in FLIGHT record

2017-05-11T15:58:46+00:00

altos: Move 'ao_force_freq' to ao_config.c

2017-05-05T05:10:36+00:00

Instead of having to add it to each product using this variable. Signed-off-by: Keith Packard