Technical:Accelerometer Fundamentals

From Openmoko

(Redirected from Accelerometer Fundamentals)
Jump to: navigation, search


What an Accelerometer is

An accelerometer simply measures acceleration, either due to motion or due to gravity.

Acceleration is measured in m/s2.

The acceleration at near the surface of the earth is around 9.8m/s2 (or 32ft/s2), which can be an unwieldy number, so 9.8m/s2 is often labeled 1G.

This means that if you drop an object from some height (assuming a vacuum), after 1 second it will be falling at 9.8m/s, a speed of 19.6m/s after 2 seconds, and so on.


  • Displacement after movement at an initial speed for a given time
    • s=u * t + 1/2 a * t2
    • initial speed * time + 1/2 * acceleration * time squared
  • Speed after Acceleration from rest
    • v=a * t
    • Speed = Acceleration * time

What one three-axis accelerometer can do

  • If the orientation of the phone is held constant - for example, clamped into a car holder, then you can make pretty good guesses about the correlation of acceleration and position.
    • In normal driving, any lateral accelerations mean that the car is turning at a rate which can be computed if the speed of the car is known.
    • Accelerations in line with the course mean that the car is slowing up or down, and any vertical accelerations mean that there is a bump, or a rise or fall in the road.
    • Errors build up, but it's not bad for short periods, 1cm/s^2 of error, with a car going in a straight line at 20m/s, takes a bit over a minute to move from a true direction of northeast - say, to a false direction of northnortheast. (the position is off after this period by a hundred metres or two)
  • When hand-held, and stationary, the phone has quite accurate (better than a degree) knowledge of where 'down' is.
    • Tilt in two directions can easily be calculated
    • Roll about the 'down' axis cannot.

What two three axis accelerometers can do

What can be done with absolutely perfect devices?

Imagine two three axis accelerometers rigidly placed on each end of an arrow.

How much information do you get out of these?

A few moments thought should reveal that the orientation of the sensors does not matter. You can resolve the three signals into one direction and size. This does not change however the devices are oriented - there is no benefit in for example skewing one 45 degrees.

Neglecting gravity

Considering the case in deep-space - the maths are simpler.

Holding the orientation steady, you can do perfect inertial navigation, and determine exactly where you are at all times.

  • What happens when we vary the orientation?
    • You can subtract any common acceleration that's measured by both sensors - this does not change the orientation.
  • Remembering that we can skew the sensors against each other, and this has no effect, let's specify that they are oriented with X and Y lined up, and Z pointing in the direction of the arrow.
  • This reveals a problem.
  • Spin the arrow on its axis, and none of the accelerometers measure anything at all - they do not move, so they do not accelerate.
    • (you can't get round this by moving them off-axis, as you can draw an imaginary arrow between the two accelerometers which has the same problem)
  • Spin the arrow around its centre (it must spin around its centre logically if you've subtracted the overall acceleration) you can pick up pitch and yaw.

With Gravity

Now, what if we add gravity in?

With perfect accelerometers again, with Z axes pointing to the arrow tip.

  • As long as the Z axes does not point in the same direction as gravity + current acceleration, then you can determine roll, pitch, yaw, and XYZ acceleration.
  • If the Z axes do point to the acceleration vector, then you lose track of roll.
    • In theory - with perfect accelerometers, this does not matter because you can never line it up perfectly.
      • In practice, with real ones, it gets more complex.
      • Roll signal/noise will drop as the acceleration vector closes on the Z axes, and be useless once it gets within the noise.


I'm assuming specs similar to the ADXL330 - simplified a little. (The accelerometer mentioned on the mailing list as being included in GTA02 is significantly worse than this - some 20 times more noise)


  • The Neo is a rigid object, and the accelerometers are rigidly fixed to it.
  • A/D has no noise and infinite bits.
  • Accelerometer only has
    • A noise of 300uG/sqrt(Hz)
    • Temperature sensitivity of +-.1mG/C.
      • I'm neglecting cross-axis sensitivity - which will need calibrated out, and non-linearity.

For interactive use. High-pass filtering the accelerometer with a bandwidth of 10Hz - you can't filter it much more than that or you lose important 'wobbles', because you need to integrate them to come up with a position - leads to a noise floor of 300uG/sqrt(Hz) *sqrt(10Hz) = 1mG. (RMS)

Neglecting roll for the moment.

1mG is an acceleration of 1cm/s^2.

If the accelerometers are spaced 10cm apart, then the radius between each and the center is 5cm, meaning the circumference of the circle is 30cm. Integrating over 1s, noise is around 3cm/s^2.

After 1s, if you happen to hit an average noise peak in each accelerometer at the opposite point - something that'll happen once every 5-10 seconds or so, (absolute peaks are much worse) what happens to the pointing?

Well - the velocity reads out as 6cm/s^2 wrong, which means that the position is now out by 3cm, or 10 degrees.


What does this mean though?

For gentle twisting and turning, the differential accelerations are impossible to tell from noise.

There are broadly two regimens where they may be of use.

When more or less stationary:

  • Picking up turning about the gravity axis - if you are looking at the phone with it in front of you at chest level, with accelerometers at top and bottom for example, this will let you pick up sharp rotations of the phone around the vertical axis - keeping the angle the screen keeps with the floor constant.
  • Roll signal-noise drops as the phone long axis approaches vertical, becoming useless well before it is vertical.
  • Movements have to be sharp and fairly large.
  • It will probably not be good enough for keeping a map aligned when you turn in place.
    • It may be adequate for some games, but again, the movements have to be sharp, it will false signal as you decrease the wanted signal.
    • The difference in acceleration when the device is swung like a baseball bat is fairly pronounced, and the speed of the swing can be accurately measured. Its exact path however cannot.

When in motion:

  • Improving the positioning of the GPS, it may give enough information to resolve sharp turns.
  • It can fill in _short_ - 3-5s gaps in GPS coverage, if the orientation of the phone is known.
    • In the best case - phone on its back, acceleration vector down, and turning in a vehicle, you may be able to tell sharp turns.
      • This is only useful if the phone is handheld, or not fixed in position to the vehicle, or if the vehicle does not go where it points.

In any condition:

  • Eliminating impossible points from the GPS data, if the maximum possible distance moved by the accelerometer over a time is under the difference between two GPS readings, then the GPS must be incorrect.
  • Recording taps on the device - the output will be broadly an intensity of tap, and the relative distance between the accelerometers and the tap.

And this is completely neglecting the temperature sensitivity.

What it can't do.

Inertial navigation or rotation over more than several seconds. For big movements the GPS could be used, for smaller movements in the Z direction (> 25 cm) a pressure sensor could be added, see Wish List - Hardware - Atmospheric, and for inertial rotation a magnetometer (digital compass) can be used, see Wishlist - Hardware: Digital compass.


Personal tools