The iPhone's accelerometer has opened up a whole new world for mobile games and applications. Fortunately, Apple has made reading the accelerometer's values an almost trivial task. The hard part is just up to you - how to actually use it. This tutorial will introduce you to the accelerometer, how to read it, and how to create a simple user interface to display its X, Y, and Z values.
For the purposes of this tutorial, I'm going to assume you know how to create a basic user interface. If you don't, I would recommend checking out our previous getting started tutorial. Below you can see an image and a quick video of the application we'll be building today.
The first thing you should notice is that we've got some UILabels and some UIProgressView objects that are used to display the accelerometer's values. I created a new UIViewController subclass called MainViewController and added these objects as properties. Here's my new header file:
// MainViewController.h
// AccelerometerTutorial
//
// Created by Brandon Cannaday on 8/5/09.
// Copyright 2009 Paranoid Ferret Productions. All rights reserved.
//
#import <UIKit/UIKit.h>
@interface MainViewController : UIViewController <UIAccelerometerDelegate> {
IBOutlet UILabel *labelX;
IBOutlet UILabel *labelY;
IBOutlet UILabel *labelZ;
IBOutlet UIProgressView *progressX;
IBOutlet UIProgressView *progressY;
IBOutlet UIProgressView *progressZ;
UIAccelerometer *accelerometer;
}
@property (nonatomic, retain) IBOutlet UILabel *labelX;
@property (nonatomic, retain) IBOutlet UILabel *labelY;
@property (nonatomic, retain) IBOutlet UILabel *labelZ;
@property (nonatomic, retain) IBOutlet UIProgressView *progressX;
@property (nonatomic, retain) IBOutlet UIProgressView *progressY;
@property (nonatomic, retain) IBOutlet UIProgressView *progressZ;
@property (nonatomic, retain) UIAccelerometer *accelerometer;
@end
A couple of things might jump out at you - first, I have another property for a UIAccelerometer object. This object is actually what's used to receive values from the accelerometer hardware. The UIAccelerometer sends updates through the use of the UIAccelerometerDelegate protocol, which is why I've marked my class as implementing this protocol.
All right, we've got the declarations out of the way. Let's now set up the UIAccelerometer object. I added code to my UIViewController's viewDidLoad method for this.
[super viewDidLoad];
self.accelerometer = [UIAccelerometer sharedAccelerometer];
self.accelerometer.updateInterval = .1;
self.accelerometer.delegate = self;
}
Instances of UIAccelerometer should never be created, they should only be acquired by getting the system's shared accelerometer object. The updateInterval property is used to instruct the UIAccelerometer object how often it should send updates to its delegate. In this case I set it to .1 seconds - so I'll get updates 10 times a second. Lastly, I simply set the delegate to the UIViewController.
We're actually pretty much done. All that's left to do is implement the delegate's method to receive accelerometer updates.
labelX.text = [NSString stringWithFormat:@"%@%f", @"X: ", acceleration.x];
labelY.text = [NSString stringWithFormat:@"%@%f", @"Y: ", acceleration.y];
labelZ.text = [NSString stringWithFormat:@"%@%f", @"Z: ", acceleration.z];
self.progressX.progress = ABS(acceleration.x);
self.progressY.progress = ABS(acceleration.y);
self.progressZ.progress = ABS(acceleration.z);
}
The raw acceleration values are stored in the UIAcceleration object passed into this message. The values are simply what the hardware is reading - where +1 is approximately equal to 1G of acceleration. I used a simple string format to update my labels, then take the absolute value of each reading for the progress bar - since progress bars can only be values between 0 and 1. Below is an image from Apple's documentation that explains the values returned for each axis.
And that's it! We now have a working application that uses the accelerometer and displays its values on the screen. The values returned are not filtered in any way, so Apple recommends doing some averaging on the data before using it in a real application. Now that you know how to use the accelerometer, it's completely up to you now to figure out inventive ways to use the data. The example application we created today can be downloaded below, and please don't hesitate to ask any questions.
09/28/2009 - 08:34
Just wanted to say thanks for a quick and simple tutorial that shows off something really cool!
10/20/2009 - 09:47
My Delegate and my View Controllers are instances of UIView so I keep getting the warning message: Does Not Implement UIAccelerometerDelegate
The examples I have looked at all are instances of NSObject... Which is not the case in my application. I am using a TabBar with 3 views. I only need the accelerometer in the one view.
Any Help?
05/09/2011 - 08:08
Cheers man . . . ,
me too got the same warning n i also fixed that by referring this example
10/20/2009 - 10:08
Hahahaha
After analyzing your example I fixed this by adding to my @interface
Thanks for your help!
Peace.
02/13/2010 - 04:19
Thank``s a lot, really usefull and simple!
GO ON WORKING LIKE THISSS!
02/20/2010 - 16:56
How can i test in simulator (i dont have iphone )
03/05/2010 - 15:38
Jooo, I don't think you can test accelerometer functions without a phone.
Thanks for the great code. I'm new to obj-c, do you have any hints on how I would store say 15 seconds of accelerometer data? Would I create an array and stick it in there?
03/05/2010 - 16:47
I'd create an NSMutableArray to hold the UIAcceleration objects. Whenever it's read, simply call addObject on the array and supply the object.
03/08/2010 - 10:10
Thanks The Reddest. I will try that out and for an encore I will try to email it as a message or attachment or ftp it out.
03/24/2010 - 18:05
Hey :)
Cool & simple tutorial.
One question though - I want to use my iphone to measure the direction which i am heading to.
How can i isolate the right coordinates from the accelerometer?
Thanks!!!
03/24/2010 - 18:22
You can't get direction from the accelerometer, you'll have to use the CoreLocation framework.
04/20/2010 - 22:55
does this concept work on samsung omnia accelerometer ? C# vs2008
08/27/2010 - 08:03
Thanks Buddy, Cool
01/19/2011 - 07:24
Thanks, it helped me a lot!
01/20/2011 - 03:19
Thanks for giving such a helpful project
01/20/2011 - 15:26
Anybody built a "black box" app for crash data logging?
02/01/2011 - 21:44
Thanks for your helpful codes. I just was wondering if any one knows how I would be able to record my accelerometer readings in a text file?
02/09/2011 - 08:35
how would you use this code to make a it count the steps you take?
03/04/2011 - 09:03
great man... inspiring.. thanks alot
03/08/2011 - 01:25
hi, thanks a lot, just to point out that to avoid warnings need to
@synthesize labelX, labelY, labelZ, progressX, progressY, progressZ, accelerometer;
(for noobs like me! haha)
thank you again
06/03/2011 - 09:41
Nice tutorial! Just add @synthesize labelX, labelY, labelZ, progressX, progressY, progressZ, accelerometer; under @implementation weatherZombieGameViewController inside of your view controller's .m file to get rid of those warnings.
06/17/2011 - 08:37
Thanks a lot, this was very helpful.
06/21/2011 - 04:22
How to get these values when the application is in sleeping mode also
07/11/2011 - 03:44
Thx for this tutorial,
But i've an error at this line :
self.accelerometer = [UIAccelerometer sharedAccelerometer];
-[CoreLocationDemoViewController setAccelerometer:]: unrecognized selector sent to instance 0x160350
2011-07-11 10:41:54.738 CoreLocationDemo[3956:607] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[CoreLocationDemoViewController setAccelerometer:]: unrecognized selector sent to instance 0x160350'
Do you have an idea for me ?
Thx again
07/18/2011 - 01:47
Hi all, ee are a non-profit organisation that aims to provide tools to the public to help save lives easier.
Our project involves using an everyday smartphone, eg iPhone, to take measurements of chest compressions during CPR training, and then locking the parameters into the phone, so that when the same person does refresher training or to use it on an actual life, the person will get valuable feedback to ensure that he does the chest compressions accurately.
What I am asking for is if you able to analyse the signal strength for me to see if the signal is 1. strong enough from smartphones ( a couple of models for example ), and 2. if there is "noise" to be cut out while using the smartphone to perform chest compressions. I presume the signals will come from the accelerometer or gyroscope in the smartphone.
If you are able to help us, we will publicise you as an important partner in our fight against sudden cardiac arrest death, just like our other partners. Our movement is current being partnered by people and across the world. You can read about our work at www.firstaidcorps.org.
We will appreciate your expertise.
Rgds
Dana Elliott
Founder
First Aid Corps
07/18/2011 - 01:48
My apologies, My contact email is at cocreate@firstaidcorps.org
07/27/2011 - 15:36
Thanks for this great tutorial.
11/03/2011 - 23:46
This is great, thanks so much!
11/30/2011 - 05:28
Sample code not extracted for me. So Please can you check or update sample code.
Thx
11/30/2011 - 09:27
I just tested it and the zip extracted without issues.
12/16/2011 - 11:57
cool tutorial! thank you...!
01/06/2012 - 06:05
it is very useful to me thank you
01/24/2012 - 21:19
Awesome, this is just what I was looking for. Thanks!