<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mjb/altos/src, branch 1.8.1</title>
<subtitle>AltOS - the operating system for Altus Metrum products
</subtitle>
<id>https://git.ethernal.org/mjb/altos/atom?h=1.8.1</id>
<link rel='self' href='https://git.ethernal.org/mjb/altos/atom?h=1.8.1'/>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/'/>
<updated>2017-08-28T07:22:43+00:00</updated>
<entry>
<title>altos: Don't compute filtered average of height error when HAS_ACCEL</title>
<updated>2017-08-28T07:22:43+00:00</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2017-08-28T07:15:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=4775b1d9b50a8732d66a0ad3b73ff74901a8cb7f'/>
<id>urn:sha1:4775b1d9b50a8732d66a0ad3b73ff74901a8cb7f</id>
<content type='text'>
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 &lt;keithp@keithp.com&gt;
</content>
</entry>
<entry>
<title>altos/test: Fake baro data for flight 12 serial 2093</title>
<updated>2017-08-28T00:40:53+00:00</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2017-08-28T00:32:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=f5642db4e03856b1f2ffeae6570fcf35fb7d93fb'/>
<id>urn:sha1:f5642db4e03856b1f2ffeae6570fcf35fb7d93fb</id>
<content type='text'>
This flight had a baro spike due to an accidental drogue charge firing
but is otherwise quite useful when testing for various mach delay
effects, so fake out the data during that spike.

Signed-off-by: Keith Packard &lt;keithp@keithp.com&gt;
</content>
</entry>
<entry>
<title>altos/test: Integrate raw accel to provide speed for comparison</title>
<updated>2017-08-28T00:40:53+00:00</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2017-08-28T00:30:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=bef7c37d1c986cd477367c0c015be61368a788d2'/>
<id>urn:sha1:bef7c37d1c986cd477367c0c015be61368a788d2</id>
<content type='text'>
This can provide a useful visualization of the 'true' vs 'kalman'
speed value, as the kalman is necessarily delayed due to the model
assuming constant acceleration.

Signed-off-by: Keith Packard &lt;keithp@keithp.com&gt;
</content>
</entry>
<entry>
<title>altos/test: telemetrum baro data is inverted before being written to eeprom</title>
<updated>2017-08-28T00:40:53+00:00</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2017-08-28T00:04:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=2dce02efd54ad4051f1ddb94048696e8677dd225'/>
<id>urn:sha1:2dce02efd54ad4051f1ddb94048696e8677dd225</id>
<content type='text'>
No need for the test code to invert it during replay

Signed-off-by: Keith Packard &lt;keithp@keithp.com&gt;
</content>
</entry>
<entry>
<title>altos: Don't eliminate baro above mach speed, just trust it less</title>
<updated>2017-08-28T00:40:40+00:00</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2017-08-27T02:16:47+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=ea6fe21d78744d7e6225a56c369d54f7cd956767'/>
<id>urn:sha1:ea6fe21d78744d7e6225a56c369d54f7cd956767</id>
<content type='text'>
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 &lt;keithp@keithp.com&gt;
</content>
</entry>
<entry>
<title>altos: Eliminate separate height error filter for accelerometer devices</title>
<updated>2017-08-28T00:40:40+00:00</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2017-08-27T23:57:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=12ef994a24eb996458092dc35c671d6b824b1576'/>
<id>urn:sha1:12ef994a24eb996458092dc35c671d6b824b1576</id>
<content type='text'>
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 &lt;keithp@keithp.com&gt;
</content>
</entry>
<entry>
<title>altos: Perform time comparisons using 16-bit arithmetic to handle wrap</title>
<updated>2017-08-28T00:38:58+00:00</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2017-08-24T23:45:54+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=cf20e213f39fb24f15e0ac94307c2d138fcadecb'/>
<id>urn:sha1:cf20e213f39fb24f15e0ac94307c2d138fcadecb</id>
<content type='text'>
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 &lt;keithp@keithp.com&gt;
</content>
</entry>
<entry>
<title>Merge remote-tracking branch 'origin/master'</title>
<updated>2017-08-12T03:45:25+00:00</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2017-08-12T03:45:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=5fdce5b4a70ae59f8ac1ca10d9fadbbbd62412f3'/>
<id>urn:sha1:5fdce5b4a70ae59f8ac1ca10d9fadbbbd62412f3</id>
<content type='text'>
</content>
</entry>
<entry>
<title>altos/test: Fix AES key format in test code</title>
<updated>2017-07-23T23:47:40+00:00</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2017-07-23T23:47:40+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=52bbfa9cd46ca27a4de937e89d48246a4e94c8a6'/>
<id>urn:sha1:52bbfa9cd46ca27a4de937e89d48246a4e94c8a6</id>
<content type='text'>
Use temp variable instead of stepping on the AES name.

Signed-off-by: Keith Packard &lt;keithp@keithp.com&gt;
</content>
</entry>
<entry>
<title>altos/test: Fix printf format for int64 arithmetic test</title>
<updated>2017-07-23T23:46:24+00:00</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2017-07-23T23:46:24+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=9eaf917707287af57c2dadfc82d6d415b0964329'/>
<id>urn:sha1:9eaf917707287af57c2dadfc82d6d415b0964329</id>
<content type='text'>
Use 'long long' and %lld for 64-bit values when printing.

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