user13605: I've bought this module
Kootek GY-521 MPU-6050 MPU6050 Module 3 Axis analog gyro sensors+ 3 Axis Accelerometer Module
My project will involve affixing this to a moving object, moving at velocities varying from 0.1 to 1.0 meters per second. 
From what I understand, this module will allow me to infer rotation and acceleration, will I be able to derive velocity? 
How much accuracy can I expect?

user14766: I don't think that will be possible. If my understanding of accelerometers is correct, they measure acceleration. Then you have a situation when the speed is constant. Acceleration = 0, according to Newton's laws. 
You would have to keep track of changes in acceleration then perform math to maintain the state. As @Chris Stratton suggest, that will lead to keep integrating the error to the very likely situation of getting a meaningless value. 
However, I have never worked with an accelerometer before, so it can be possible at a certain extent. 
It would be great to hear from someone who actually tried this.

user19900: I work with Arduino-based autopilot modules, which usually use similar sensors in addition to GPS data to maintain a reasonable estimate of its position/velocity/acceleration.  If you were to add other sensors (i.e. a GPS) to your project, it might be worth looking into Extended Kalman Filters (https://github.com/simondlevy/TinyEKF), which are usually able to provide fairly accurate results.
If you're only using an accelerometer, EKF would probably be overkill, so you could look into other noise-reduction techniques.  For example, using a weighted average of the last two readings:
// alpha is value between 0 and 1
acceleration = alpha * readAccelerationSensor() + (1 - alpha) * lastSensorReading

Another strategy to filter out noise would be to take multiple sensor readings at each time step and use the median value to integrate for velocity.

user18473: The sensor in itself can't provide you the velocity. I have used it accelerometers in a couple of projects the easiest way to get the velocity is to constantly monitor acceleration changes and calculate velocity instantaneaously.
In order to do so follow these instruction. Pleas note that this is only 1 axis reading in actual case you will have to perform this for all three axis i.e. x,y and z.
I hope you are aware of the equation of motion (V = Vo + at)... The sensor will provide you value of acceleration at any given time. But acceleration can vary quite significantly during a huge time intervals so keep the time intervals 't' small. Lets say t = 10ms (depends on you). So calculate V after every 10ms intervale and this will give you current velocity at any given time. But what about Vo? As you know it is refered to as initial velocity so in the beginning it will be 0. Immediately after first reading when you are about to take second reading the Vo will change to the previous V calculated and hence forth.
This means Vo at any given interval is actually the V calculated in the previous interval.
I tried this method in my project when using accelerometer. hope it helps you as well.

13605: <p>I've bought this module</p>

<p><a href="http://rads.stackoverflow.com/amzn/click/B008BOPN40" rel="noreferrer">Kootek GY-521 MPU-6050 MPU6050 Module 3 Axis analog gyro sensors+ 3 Axis Accelerometer Module</a></p>

<p>My project will involve affixing this to a moving object, moving at velocities varying from 0.1 to 1.0 meters per second. </p>

<p>From what I understand, this module will allow me to infer rotation and acceleration, will I be able to derive velocity? </p>

<p>How much accuracy can I expect?</p>
 14766: <p>I don't think that will be possible. If my understanding of accelerometers is correct, they measure acceleration. Then you have a situation when the speed is constant. Acceleration = 0, according to Newton's laws. </p>

<p>You would have to keep track of changes in acceleration then perform math to maintain the state. As @Chris Stratton suggest, that will lead to keep integrating the error to the very likely situation of getting a meaningless value. </p>

<p>However, I have never worked with an accelerometer before, so it can be possible at a certain extent. </p>

<p>It would be great to hear from someone who actually tried this.</p>
 19900: <p>I work with Arduino-based autopilot modules, which usually use similar sensors in addition to GPS data to maintain a reasonable estimate of its position/velocity/acceleration.  If you were to add other sensors (i.e. a GPS) to your project, it might be worth looking into Extended Kalman Filters (<a href="https://github.com/simondlevy/TinyEKF" rel="nofollow">https://github.com/simondlevy/TinyEKF</a>), which are usually able to provide fairly accurate results.</p>

<p>If you're only using an accelerometer, EKF would probably be overkill, so you could look into other noise-reduction techniques.  For example, using a weighted average of the last two readings:</p>

<pre><code>// alpha is value between 0 and 1
acceleration = alpha * readAccelerationSensor() + (1 - alpha) * lastSensorReading
</code></pre>

<p>Another strategy to filter out noise would be to take multiple sensor readings at each time step and use the median value to integrate for velocity.</p>
 18473: <p>The sensor in itself can't provide you the velocity. I have used it accelerometers in a couple of projects the easiest way to get the velocity is to constantly monitor acceleration changes and calculate velocity instantaneaously.</p>

<p>In order to do so follow these instruction. Pleas note that this is only 1 axis reading in actual case you will have to perform this for all three axis i.e. x,y and z.</p>

<p>I hope you are aware of the equation of motion (V = Vo + at)... The sensor will provide you value of acceleration at any given time. But acceleration can vary quite significantly during a huge time intervals so keep the time intervals 't' small. Lets say t = 10ms (depends on you). So calculate V after every 10ms intervale and this will give you current velocity at any given time. But what about Vo? As you know it is refered to as initial velocity so in the beginning it will be 0. Immediately after first reading when you are about to take second reading the Vo will change to the previous V calculated and hence forth.</p>

<p>This means Vo at any given interval is actually the V calculated in the previous interval.</p>

<p>I tried this method in my project when using accelerometer. hope it helps you as well.</p>
