<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mjb/altos/src/ao_kalman.c, branch debian/1.0</title>
<subtitle>AltOS - the operating system for Altus Metrum products
</subtitle>
<id>https://git.ethernal.org/mjb/altos/atom?h=debian%2F1.0</id>
<link rel='self' href='https://git.ethernal.org/mjb/altos/atom?h=debian%2F1.0'/>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/'/>
<updated>2011-08-14T06:58:03+00:00</updated>
<entry>
<title>altos: use raw height while waiting for landing</title>
<updated>2011-08-14T06:58:03+00:00</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2011-08-14T06:58:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=709485f20fb039f8dd087c8491c5f5a76718ae53'/>
<id>urn:sha1:709485f20fb039f8dd087c8491c5f5a76718ae53</id>
<content type='text'>
This avoids any noise introduced by the kalman filter, making landing
detection much more reliable. This patch also changes the interval to
10s so that the height bounds can be increased to 4m.

Signed-off-by: Keith Packard &lt;keithp@keithp.com&gt;
</content>
</entry>
<entry>
<title>altos: Reduce height averaging filter time constant</title>
<updated>2011-08-02T08:53:33+00:00</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2011-08-02T08:49:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=6c55bf35b11ae3ddae152795072d69e98184bac1'/>
<id>urn:sha1:6c55bf35b11ae3ddae152795072d69e98184bac1</id>
<content type='text'>
Using the longer time constant could lead to false landing detection
just after apogee, which is definitely not a good idea.

Signed-off-by: Keith Packard &lt;keithp@keithp.com&gt;
</content>
</entry>
<entry>
<title>altos: Average height values for landing detection</title>
<updated>2011-08-02T07:30:08+00:00</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2011-08-02T05:33:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=e19a117b99e8374ca0e8e35948e23bc672ad1a32'/>
<id>urn:sha1:e19a117b99e8374ca0e8e35948e23bc672ad1a32</id>
<content type='text'>
Instead of using the direct output of the kalman filter and hoping
that is quiet enough to detect landing, filter that with a long
exponential decay filter and then check to make sure that doesn't
change more than 2m in 5 seconds as a trigger for landing detection.

Tested with existing telemetrum flight logs and it correctly detects
landing in all cases.

Signed-off-by: Keith Packard &lt;keithp@keithp.com&gt;
</content>
</entry>
<entry>
<title>altos: Add ability to read new TELEM files to ao_flight_test</title>
<updated>2011-07-18T01:49:55+00:00</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2011-07-18T01:49:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=146a0ab223e8d9b376125d1e59f597f6d7851a9b'/>
<id>urn:sha1:146a0ab223e8d9b376125d1e59f597f6d7851a9b</id>
<content type='text'>
Not that telem files are currently very useful as the kalman filter
gets completly confused by the variable steps caused by missing data, but...

Signed-off-by: Keith Packard &lt;keithp@keithp.com&gt;
</content>
</entry>
<entry>
<title>altos: Baro useful ceiling is MSL, not AGL</title>
<updated>2011-04-01T03:53:12+00:00</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2011-04-01T03:53:12+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=8a14142e7b37031a51409f121b913fe793bf3603'/>
<id>urn:sha1:8a14142e7b37031a51409f121b913fe793bf3603</id>
<content type='text'>
Use MSL instead of AGL for detecting over-range baro sensor values.
Always trust baro sensor during descent; it'll get there eventually.

Signed-off-by: Keith Packard &lt;keithp@keithp.com&gt;
</content>
</entry>
<entry>
<title>altos: Split up flight code into separate flight/sample/kalman bits</title>
<updated>2011-03-29T00:54:44+00:00</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2011-03-29T00:54:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=c754759a2d503633d527da4ebb20eb859cd506fd'/>
<id>urn:sha1:c754759a2d503633d527da4ebb20eb859cd506fd</id>
<content type='text'>
The flight code mashed together data processing, filtering and actual
flight managament into one giant pile. Split things up so that we
have:

 ao_sample.c: Sensor data processing. Reads the ring, handles calibration
 ao_kalman.c: Filter the data to track the accel/speed/height values
 ao_flight.c: Flight state management, specific to rocketry.

The plan is to re-use ao_sample.c and ao_kalman.c for hardware not
specifically designed for rocketry, like TeleNano.

Signed-off-by: Keith Packard &lt;keithp@keithp.com&gt;
</content>
</entry>
</feed>
