<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mjb/altos/src/kernel, branch branch-1.5</title>
<subtitle>AltOS - the operating system for Altus Metrum products
</subtitle>
<id>https://git.ethernal.org/mjb/altos/atom?h=branch-1.5</id>
<link rel='self' href='https://git.ethernal.org/mjb/altos/atom?h=branch-1.5'/>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/'/>
<updated>2014-09-13T17:26:21+00:00</updated>
<entry>
<title>altos: Make sure we don't beep out continuity twice in idle mode</title>
<updated>2014-09-13T17:26:21+00:00</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2014-09-12T02:56:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=e969172a81e24f70c349b10f429e69817900c307'/>
<id>urn:sha1:e969172a81e24f70c349b10f429e69817900c307</id>
<content type='text'>
If the battery voltage report takes longer than the initialiation
sequence, we could get to the state reporting after the state had
switched from startup to idle. This would result in continuity being
reported the first time through the loop. Then, as the state had
already changed, we'd pass through the while test and go back to
report continuity a second time.

Fixed by using the state remembered before beeping out the voltage to
decide whether to report the continuity.

Signed-off-by: Keith Packard &lt;keithp@keithp.com&gt;
</content>
</entry>
<entry>
<title>altos: Fix ability to disable telemetry by setting interval to 0</title>
<updated>2014-09-13T17:26:13+00:00</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2014-09-11T22:00:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=800f3377b1a374ad5cf826aa897efdcb08059040'/>
<id>urn:sha1:800f3377b1a374ad5cf826aa897efdcb08059040</id>
<content type='text'>
For non-zero telemetry intervals, the radio code limits the value
based on the data rate. However, a zero interval means that telemetry
should be entirely disabled, so that value should be left alone when
checking.

Signed-off-by: Keith Packard &lt;keithp@keithp.com&gt;
</content>
</entry>
<entry>
<title>altos: Allow negative values for pyro configuration data</title>
<updated>2014-09-04T05:58:22+00:00</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2014-09-04T05:58:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=be38fb88d11bda1ba1caca38220773d3abcede19'/>
<id>urn:sha1:be38fb88d11bda1ba1caca38220773d3abcede19</id>
<content type='text'>
All of the integer pyro configuration parameters may be negative, so
parse that correctly.

Signed-off-by: Keith Packard &lt;keithp@keithp.com&gt;
</content>
</entry>
<entry>
<title>altos: Don't add AO_LOG_FLIGHT to existing GPS logs</title>
<updated>2014-09-01T23:12:29+00:00</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2014-09-01T23:12:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=a4202b4180e77e2a39ca071d3b8b8256ff0fc7b5'/>
<id>urn:sha1:a4202b4180e77e2a39ca071d3b8b8256ff0fc7b5</id>
<content type='text'>
When appending to a TeleGPS log, don't stick another flight value into
the log. That just confuses the ground station software.

Signed-off-by: Keith Packard &lt;keithp@keithp.com&gt;
</content>
</entry>
<entry>
<title>altos: Make sure pyro remains valid during delay</title>
<updated>2014-08-29T20:12:38+00:00</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2014-08-29T20:12:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=5872bd10df14b47de0e541bff16d9220af0558aa'/>
<id>urn:sha1:5872bd10df14b47de0e541bff16d9220af0558aa</id>
<content type='text'>
Keep checking pyro status while waiting for delay to expire to make
sure nothing changes. Disable pyro channel if something does.

Signed-off-by: Keith Packard &lt;keithp@keithp.com&gt;
</content>
</entry>
<entry>
<title>altos: Add telerepeat-v1.0</title>
<updated>2014-08-18T04:03:12+00:00</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2014-08-18T04:03:12+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=44e389c31e5958c1a050fbe0dce5d7971a9d6a86'/>
<id>urn:sha1:44e389c31e5958c1a050fbe0dce5d7971a9d6a86</id>
<content type='text'>
This uses TeleBT hardware to provide a telemetry repeater, receiving
packets on one frequency and re-transmitting them on another.

Signed-off-by: Keith Packard &lt;keithp@keithp.com&gt;
</content>
</entry>
<entry>
<title>telegps-v1.0: Provide one log and append to it</title>
<updated>2014-08-18T03:59:45+00:00</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2014-08-18T03:59:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=bb7522acf040f41740ecd059e3d5d2480b652420'/>
<id>urn:sha1:bb7522acf040f41740ecd059e3d5d2480b652420</id>
<content type='text'>
Instead of creating per-flight logs, create a single log and append
data to it each time TeleGPS is powered on. This avoids potentially
running out of log space just because the device is powered off/on.

Signed-off-by: Keith Packard &lt;keithp@keithp.com&gt;
</content>
</entry>
<entry>
<title>altos: Report additional pyro channels via beeper</title>
<updated>2014-08-15T02:08:19+00:00</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2014-08-15T02:03:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=e935ebe55705cb0506aac0859583d54fd8e5ca46'/>
<id>urn:sha1:e935ebe55705cb0506aac0859583d54fd8e5ca46</id>
<content type='text'>
Send a beep for each additional pyro channel, low for no igniter, mid
for igniter. Does not change the reporting for the apogee/main channels.

Signed-off-by: Keith Packard &lt;keithp@keithp.com&gt;
</content>
</entry>
<entry>
<title>altos: Have MicroKite just start recording at startup</title>
<updated>2014-08-15T02:08:19+00:00</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2014-07-20T05:35:30+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=d8e2b661e895fc59ded002a02191dcccce75f548'/>
<id>urn:sha1:d8e2b661e895fc59ded002a02191dcccce75f548</id>
<content type='text'>
This avoids having MicroKite try to detect boost and has it just start
recording data immediately.

Signed-off-by: Keith Packard &lt;keithp@keithp.com&gt;
</content>
</entry>
<entry>
<title>altos: Make ao_gps_print deal with telem containing 32-bit altitude values</title>
<updated>2014-07-14T03:43:27+00:00</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2014-07-14T03:43:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=50aec54bdc35962145eff9b465f9cd7b3d9fea0b'/>
<id>urn:sha1:50aec54bdc35962145eff9b465f9cd7b3d9fea0b</id>
<content type='text'>
ao_gps_print is used with new telem packets from a few places; use
AO_TELEMETRY_LOCATION_ALTITUDE when necessary.

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