<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: accelerometer results while driving a robot in Sensors</title>
    <link>https://community.nxp.com/t5/Sensors/accelerometer-results-while-driving-a-robot/m-p/461388#M2571</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dror,&lt;/P&gt;&lt;P&gt;I hate to tell you this, but your basic premise is flawed.&amp;nbsp; Trying to get velocity/position by single/double integration is almost always a bad idea. &lt;/P&gt;&lt;P&gt;Problem #1 is that every sensor has noise, and when you integrate noise, you get a random walk over time.&amp;nbsp; See &lt;A href="https://community.nxp.com/thread/387210"&gt;Position Reckoning&lt;/A&gt; for more details.&lt;/P&gt;&lt;P&gt;Problem #2 is that one man's signal is another man's noise and vice versa.&amp;nbsp; I'm pretty sure you are seeing vibrations from your robot's motor and gear train.&lt;/P&gt;&lt;P&gt;You would be better off with a rotary encoder for this application to determine speed/distance.&amp;nbsp;&amp;nbsp; Fusion of accel/gyro data can give you your robot's orientation and linear acceleration, but if you need accuracy in velocity and position, you should look at other sensor types.&lt;/P&gt;&lt;P&gt;Mike&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 04 Apr 2016 18:40:44 GMT</pubDate>
    <dc:creator>michaelestanley</dc:creator>
    <dc:date>2016-04-04T18:40:44Z</dc:date>
    <item>
      <title>accelerometer results while driving a robot</title>
      <link>https://community.nxp.com/t5/Sensors/accelerometer-results-while-driving-a-robot/m-p/461387#M2570</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P style="direction: ltr;"&gt;Hello,&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px; direction: ltr;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="direction: ltr;"&gt;I've tried to calculate the speed of a robot while in movement, by measuring the acceleration(by using MMA7361LC).&lt;/P&gt;&lt;P style="direction: ltr;"&gt;I've tested the accelerometer and it gives good results when moving it (forward, backward) and when checking if it measures the gravity.&lt;/P&gt;&lt;P style="direction: ltr;"&gt;Even when it is fixed to the robot(tank), if I'm moving the robot by hand - works well.&lt;/P&gt;&lt;P style="direction: ltr;"&gt;The problem is that while driving the robot with it's wheel motors - I'm not able to get reasonable results at all.&lt;/P&gt;&lt;P style="direction: ltr;"&gt;From the beginning I'm getting the same oscillations until the robot stops - that I can very barely analyze where there was a positive or negative acceleration, and the noise is very high, even after a 70Hz simple LPF.&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px; direction: ltr;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="direction: ltr;"&gt;I don't understand why when the robot is in movement(by the wheel motors) I don't get something close to a straight line?&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px; direction: ltr;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="direction: ltr;"&gt;In the attached files:&lt;/P&gt;&lt;P style="direction: ltr;"&gt;Green - the positive driving axis, before the LPF.&lt;/P&gt;&lt;P style="direction: ltr;"&gt;Orange - the positive driving axis, after the LPF.&lt;/P&gt;&lt;P style="direction: ltr;"&gt;scope_3 - a low acceleration(for about 0.5 seconds), a fixed velocity, and then a low negative acceleration(for about 0.5 seconds).&lt;/P&gt;&lt;P style="direction: ltr;"&gt;scope_4 - same, with a higher acceleration in the start and in the end.&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px; direction: ltr;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P style="direction: ltr;"&gt;Please help.&lt;/P&gt;&lt;P style="direction: ltr;"&gt;Thanks, Dror.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 Feb 2026 23:45:59 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Sensors/accelerometer-results-while-driving-a-robot/m-p/461387#M2570</guid>
      <dc:creator>drorpopper</dc:creator>
      <dc:date>2026-02-03T23:45:59Z</dc:date>
    </item>
    <item>
      <title>Re: accelerometer results while driving a robot</title>
      <link>https://community.nxp.com/t5/Sensors/accelerometer-results-while-driving-a-robot/m-p/461388#M2571</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dror,&lt;/P&gt;&lt;P&gt;I hate to tell you this, but your basic premise is flawed.&amp;nbsp; Trying to get velocity/position by single/double integration is almost always a bad idea. &lt;/P&gt;&lt;P&gt;Problem #1 is that every sensor has noise, and when you integrate noise, you get a random walk over time.&amp;nbsp; See &lt;A href="https://community.nxp.com/thread/387210"&gt;Position Reckoning&lt;/A&gt; for more details.&lt;/P&gt;&lt;P&gt;Problem #2 is that one man's signal is another man's noise and vice versa.&amp;nbsp; I'm pretty sure you are seeing vibrations from your robot's motor and gear train.&lt;/P&gt;&lt;P&gt;You would be better off with a rotary encoder for this application to determine speed/distance.&amp;nbsp;&amp;nbsp; Fusion of accel/gyro data can give you your robot's orientation and linear acceleration, but if you need accuracy in velocity and position, you should look at other sensor types.&lt;/P&gt;&lt;P&gt;Mike&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 Apr 2016 18:40:44 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Sensors/accelerometer-results-while-driving-a-robot/m-p/461388#M2571</guid>
      <dc:creator>michaelestanley</dc:creator>
      <dc:date>2016-04-04T18:40:44Z</dc:date>
    </item>
  </channel>
</rss>

