<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mjb/altos/src/kernel/ao_telemetry.h, branch telefire-4-no-addr</title>
<subtitle>AltOS - the operating system for Altus Metrum products
</subtitle>
<id>https://git.ethernal.org/mjb/altos/atom?h=telefire-4-no-addr</id>
<link rel='self' href='https://git.ethernal.org/mjb/altos/atom?h=telefire-4-no-addr'/>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/'/>
<updated>2017-06-12T05:54:22+00:00</updated>
<entry>
<title>altos: HMC5883 output order is X Z Y</title>
<updated>2017-06-12T05:54:22+00:00</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2017-06-12T05:34:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=2a05849c3bf8c1617409237be48802dd6fc6255b'/>
<id>urn:sha1:2a05849c3bf8c1617409237be48802dd6fc6255b</id>
<content type='text'>
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 &lt;keithp@keithp.com&gt;
</content>
</entry>
<entry>
<title>altos: Split out TeleMini v3 log/telem labeling</title>
<updated>2017-02-20T19:16:53+00:00</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2017-02-20T01:39:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=59ac667c4ae14e0fa699fb0f398d31763a237646'/>
<id>urn:sha1:59ac667c4ae14e0fa699fb0f398d31763a237646</id>
<content type='text'>
Allow the ground software to know which TeleMini version is in use,
even though they are very similar with only ADC values differing.

Signed-off-by: Keith Packard &lt;keithp@keithp.com&gt;
</content>
</entry>
<entry>
<title>Switch from GPLv2 to GPLv2+</title>
<updated>2016-07-12T22:41:41+00:00</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2016-07-05T16:03:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=1085ec5d57e0ed5d132f2bbdac1a0b6a32c0ab4a'/>
<id>urn:sha1:1085ec5d57e0ed5d132f2bbdac1a0b6a32c0ab4a</id>
<content type='text'>
Signed-off-by: Keith Packard &lt;keithp@keithp.com&gt;
</content>
</entry>
<entry>
<title>altos: Missing pad field in TMv2 data packet</title>
<updated>2015-03-03T05:16:06+00:00</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2015-03-03T05:16:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=bef7c89dac68956a94ae386fa6b87165ab6cb484'/>
<id>urn:sha1:bef7c89dac68956a94ae386fa6b87165ab6cb484</id>
<content type='text'>
The normal ARM padding would have filled this in correctly, but it's
best to be explicit about the structure.

This also adds a test to make sure the resulting telemetry declaration
is exactly 32 bytes,

Signed-off-by: Keith Packard &lt;keithp@keithp.com&gt;
</content>
</entry>
<entry>
<title>altos: Fix up telemetry delay computations</title>
<updated>2014-10-26T02:56:25+00:00</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2014-10-26T02:56:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=4d51570ed8776461d084726149923c5be43d622e'/>
<id>urn:sha1:4d51570ed8776461d084726149923c5be43d622e</id>
<content type='text'>
With RDF, APRS and telemetry all being sent at varying rates,
computing when to send the next radio data is not as simple as sending
telemetry and then figuring out whether to send RDF and/or APRS.

Fix this by computing times for the next telemetry/rdf/aprs packet,
and only sending each when that time has passed. Compute the delay
until the next radio activity as the minimum time to any transmission.

This also adds code to the config bits to reset the radio times
whenever something changes that might affect which radio data to send
next.

Signed-off-by: Keith Packard &lt;keithp@keithp.com&gt;
</content>
</entry>
<entry>
<title>altos: Expose telemetry altitude macros even without GPS</title>
<updated>2014-10-25T04:24:53+00:00</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2014-10-07T03:35:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=7fea8b245cdccc1ec77aa559433952f339676473'/>
<id>urn:sha1:7fea8b245cdccc1ec77aa559433952f339676473</id>
<content type='text'>
This allows for APRS testing in the new teledongle code

Signed-off-by: Keith Packard &lt;keithp@keithp.com&gt;
</content>
</entry>
<entry>
<title>altos: Extend GPS altitudes to at least 24 bits everywhere</title>
<updated>2014-07-11T00:35:44+00:00</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2014-07-11T00:07:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=34d5be68ca23e8beb05db9a480faef63ecc911d0'/>
<id>urn:sha1:34d5be68ca23e8beb05db9a480faef63ecc911d0</id>
<content type='text'>
Telemetry gets a special 'mode' flag indicating that 24-bit data is
present; log files get new data and log readers are expected to detect
that via the firmware version number.

Signed-off-by: Keith Packard &lt;keithp@keithp.com&gt;
</content>
</entry>
<entry>
<title>Revert adding state to GPS location packets</title>
<updated>2014-06-10T16:47:04+00:00</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2014-06-10T16:47:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=c5a7889a8da3da64deb0f118656784e0ee3fd511'/>
<id>urn:sha1:c5a7889a8da3da64deb0f118656784e0ee3fd511</id>
<content type='text'>
TeleGPS no longer has ao_flight_state

Signed-off-by: Keith Packard &lt;keithp@keithp.com&gt;
</content>
</entry>
<entry>
<title>altos: Use 0x80 to indicate valid state value in the GPS location packet</title>
<updated>2014-06-08T04:02:26+00:00</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2014-06-08T04:02:26+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=08550425fca3da73d8f16de567a2c956b85d676e'/>
<id>urn:sha1:08550425fca3da73d8f16de567a2c956b85d676e</id>
<content type='text'>
And only set this for tracker products; other products place state in
separate state packets

Signed-off-by: Keith Packard &lt;keithp@keithp.com&gt;
</content>
</entry>
<entry>
<title>altos: Stick flight state in GPS location packets</title>
<updated>2014-06-06T01:44:26+00:00</updated>
<author>
<name>Keith Packard</name>
<email>keithp@keithp.com</email>
</author>
<published>2014-06-06T01:44:26+00:00</published>
<link rel='alternate' type='text/html' href='https://git.ethernal.org/mjb/altos/commit/?id=97dac0f66bc938940e6b49409d950a1736c92655'/>
<id>urn:sha1:97dac0f66bc938940e6b49409d950a1736c92655</id>
<content type='text'>
Useful for TeleGPS

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