<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: TapeMeasure &#8211; Another Android experiment</title>
	<atom:link href="http://connorhd.co.uk/2010/03/23/tapemeasure-another-android-experiment/feed/" rel="self" type="application/rss+xml" />
	<link>http://connorhd.co.uk/2010/03/23/tapemeasure-another-android-experiment/</link>
	<description>Interesting stuff.</description>
	<lastBuildDate>Sun, 03 Nov 2024 01:07:47 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: tb</title>
		<link>http://connorhd.co.uk/2010/03/23/tapemeasure-another-android-experiment/comment-page-1/#comment-73</link>
		<dc:creator>tb</dc:creator>
		<pubDate>Fri, 26 Aug 2011 06:09:00 +0000</pubDate>
		<guid isPermaLink="false">http://connorhd.co.uk/?p=158#comment-73</guid>
		<description>I know this is an old post, but I found out a junior engineer at my company was forced (by an idiot boss) to attempt this.  I actually have done a lot of work with MEMs accelerometers before they were ever put into phones, but was never asked.  Please don&#039;t get stuck like she did.  
To put it bluntly, it&#039;ll never work without correction from another sensor.  Here&#039;s why.  Assume that &#039;a&#039; is the true acceleration, but a real-world sensor measures error too.  This error is included in the equation to remove gravity. This means that you partially leave gravity as real acceleration.  This feeds back into the next step and the effect of that error increases as the square of time (due to double integration). So after say 10 seconds, it is multiplied by 100.  After 20, by 400.  And that is just the error from that ONE sample.  All the others are accumulating on top of it with the same increase.

A second sensor like a camera can be used to zero out the error periodically and may be a good solution.  Look up Kalman filters to see how this is done in inertial measurement units.

HTH, good luck.
t</description>
		<content:encoded><![CDATA[<p>I know this is an old post, but I found out a junior engineer at my company was forced (by an idiot boss) to attempt this.  I actually have done a lot of work with MEMs accelerometers before they were ever put into phones, but was never asked.  Please don&#8217;t get stuck like she did.  <br />
To put it bluntly, it&#8217;ll never work without correction from another sensor.  Here&#8217;s why.  Assume that &#8216;a&#8217; is the true acceleration, but a real-world sensor measures error too.  This error is included in the equation to remove gravity. This means that you partially leave gravity as real acceleration.  This feeds back into the next step and the effect of that error increases as the square of time (due to double integration). So after say 10 seconds, it is multiplied by 100.  After 20, by 400.  And that is just the error from that ONE sample.  All the others are accumulating on top of it with the same increase.</p>
<p>A second sensor like a camera can be used to zero out the error periodically and may be a good solution.  Look up Kalman filters to see how this is done in inertial measurement units.</p>
<p>HTH, good luck.<br />
t</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anilsharma Y</title>
		<link>http://connorhd.co.uk/2010/03/23/tapemeasure-another-android-experiment/comment-page-1/#comment-69</link>
		<dc:creator>Anilsharma Y</dc:creator>
		<pubDate>Mon, 11 Jul 2011 12:15:00 +0000</pubDate>
		<guid isPermaLink="false">http://connorhd.co.uk/?p=158#comment-69</guid>
		<description> All in all a bit of a waste of time
:))</description>
		<content:encoded><![CDATA[<p> All in all a bit of a waste of time <img src='http://connorhd.co.uk/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> )</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: CT</title>
		<link>http://connorhd.co.uk/2010/03/23/tapemeasure-another-android-experiment/comment-page-1/#comment-30</link>
		<dc:creator>CT</dc:creator>
		<pubDate>Sat, 27 Nov 2010 22:24:39 +0000</pubDate>
		<guid isPermaLink="false">http://connorhd.co.uk/?p=158#comment-30</guid>
		<description>I read buyer comments on Android that millimeters is not so good either.
Good exercise of exploration !</description>
		<content:encoded><![CDATA[<p>I read buyer comments on Android that millimeters is not so good either.<br />
Good exercise of exploration !</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stan</title>
		<link>http://connorhd.co.uk/2010/03/23/tapemeasure-another-android-experiment/comment-page-1/#comment-17</link>
		<dc:creator>Stan</dc:creator>
		<pubDate>Thu, 19 Aug 2010 19:18:39 +0000</pubDate>
		<guid isPermaLink="false">http://connorhd.co.uk/?p=158#comment-17</guid>
		<description>As oiok said Millimeters works fine: http://www.youtube.com/watch?v=iYpiVTdElPY

Stan</description>
		<content:encoded><![CDATA[<p>As oiok said Millimeters works fine: <a href="http://www.youtube.com/watch?v=iYpiVTdElPY" rel="nofollow">http://www.youtube.com/watch?v=iYpiVTdElPY</a></p>
<p>Stan</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Leo</title>
		<link>http://connorhd.co.uk/2010/03/23/tapemeasure-another-android-experiment/comment-page-1/#comment-16</link>
		<dc:creator>Leo</dc:creator>
		<pubDate>Thu, 24 Jun 2010 18:51:37 +0000</pubDate>
		<guid isPermaLink="false">http://connorhd.co.uk/?p=158#comment-16</guid>
		<description>Hi,
This is interesting, have been looking at doing something similar myself...
A few comments:
I don&#039;t know much about these sensors, but I don&#039;t think there&#039;s a need to subtract gravity as the accelerometer will only register if the phone accelerates (i.e. is dropped), in which case you want to know about it. This might be the reason you get a rapid distance increase. If the distance per second linearly increases, there&#039;s your culprit. Also you might consider implementing a improved Euler or Verlet numerical integration, the second one stops computation error-caused silly increases in displacement in my experience. You&#039;ll need one step of a simple numerical integration to get it started though.
Look forward to meeting you soon, Leo</description>
		<content:encoded><![CDATA[<p>Hi,<br />
This is interesting, have been looking at doing something similar myself&#8230;<br />
A few comments:<br />
I don&#8217;t know much about these sensors, but I don&#8217;t think there&#8217;s a need to subtract gravity as the accelerometer will only register if the phone accelerates (i.e. is dropped), in which case you want to know about it. This might be the reason you get a rapid distance increase. If the distance per second linearly increases, there&#8217;s your culprit. Also you might consider implementing a improved Euler or Verlet numerical integration, the second one stops computation error-caused silly increases in displacement in my experience. You&#8217;ll need one step of a simple numerical integration to get it started though.<br />
Look forward to meeting you soon, Leo</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: oiok</title>
		<link>http://connorhd.co.uk/2010/03/23/tapemeasure-another-android-experiment/comment-page-1/#comment-15</link>
		<dc:creator>oiok</dc:creator>
		<pubDate>Fri, 14 May 2010 21:05:12 +0000</pubDate>
		<guid isPermaLink="false">http://connorhd.co.uk/?p=158#comment-15</guid>
		<description>Maybe you should take a look at Millimeters ( available on the Market: market://search?q=pname:com.droideilhan.millimeters ).</description>
		<content:encoded><![CDATA[<p>Maybe you should take a look at Millimeters ( available on the Market: market://search?q=pname:com.droideilhan.millimeters ).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
