<feed xmlns='http://www.w3.org/2005/Atom'>
<title>wasp-os.git/wasp/drivers/bma421.py, branch master</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.
</subtitle>
<link rel='alternate' type='text/html' href='http://cgit.tidal.blue/wasp-os.git/'/>
<entry>
<title>drivers: bma421: Switch over to reset_step_counter()</title>
<updated>2020-12-31T09:31:47Z</updated>
<author>
<name>Daniel Thompson</name>
<email>daniel@redfelineninja.org.uk</email>
</author>
<published>2020-12-31T09:31:47Z</published>
<link rel='alternate' type='text/html' href='http://cgit.tidal.blue/wasp-os.git/commit/?id=6212a6275a2678f9512656c450a7ffa9ef14c084'/>
<id>6212a6275a2678f9512656c450a7ffa9ef14c084</id>
<content type='text'>
Currently the bma421 driver simple re-initializes the sensor when asked
to set the step counter to zero. Switch over to the proper function
for this.

Signed-off-by: Daniel Thompson &lt;daniel@redfelineninja.org.uk&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Currently the bma421 driver simple re-initializes the sensor when asked
to set the step counter to zero. Switch over to the proper function
for this.

Signed-off-by: Daniel Thompson &lt;daniel@redfelineninja.org.uk&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>drivers: bma421: Reduce the post-reset delay</title>
<updated>2020-06-12T07:51:44Z</updated>
<author>
<name>Daniel Thompson</name>
<email>daniel@redfelineninja.org.uk</email>
</author>
<published>2020-06-12T07:51:37Z</published>
<link rel='alternate' type='text/html' href='http://cgit.tidal.blue/wasp-os.git/commit/?id=ab33027fff79d6de521201e5c594d5b8591c2cda'/>
<id>ab33027fff79d6de521201e5c594d5b8591c2cda</id>
<content type='text'>
There nothing in the docs to give the delay time required after a
reset. Currently we use 200ms because that appears on some older
code for BMA423 but is removed in more recent drivers. 50ms is still
a long time (for hardware) and has held up in testing.

Signed-off-by: Daniel Thompson &lt;daniel@redfelineninja.org.uk&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
There nothing in the docs to give the delay time required after a
reset. Currently we use 200ms because that appears on some older
code for BMA423 but is removed in more recent drivers. 50ms is still
a long time (for hardware) and has held up in testing.

Signed-off-by: Daniel Thompson &lt;daniel@redfelineninja.org.uk&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>wasp: apps: Step counter application</title>
<updated>2020-06-09T20:31:55Z</updated>
<author>
<name>Daniel Thompson</name>
<email>daniel@redfelineninja.org.uk</email>
</author>
<published>2020-06-09T20:29:00Z</published>
<link rel='alternate' type='text/html' href='http://cgit.tidal.blue/wasp-os.git/commit/?id=ccaf12750ba39fe0bc1fa6d2425ef2d1831ded9a'/>
<id>ccaf12750ba39fe0bc1fa6d2425ef2d1831ded9a</id>
<content type='text'>
Currently there's no fancy algorithms to estimate stride length. Just
pure simple step counting directly from the hardware's "intelligence
engine".

Signed-off-by: Daniel Thompson &lt;daniel@redfelineninja.org.uk&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Currently there's no fancy algorithms to estimate stride length. Just
pure simple step counting directly from the hardware's "intelligence
engine".

Signed-off-by: Daniel Thompson &lt;daniel@redfelineninja.org.uk&gt;
</pre>
</div>
</content>
</entry>
</feed>
