Difference between revisions of "AR Drone 2/Motor driver"
Jump to navigation
Jump to search
(Created page with "Starting off with the project we first tried searching what had allready been done for AR.Drone1 and we found a very good source[http://blog.perquin.com/blog/2011/06/] explaining…") |
|||
| Line 1: | Line 1: | ||
Starting off with the project we first tried searching what had allready been done for AR.Drone1 and we found a very good source[http://blog.perquin.com/blog/2011/06/] explaining | Starting off with the project we first tried searching what had allready been done for AR.Drone1 and we found a very good source in the [Perquin blog|http://blog.perquin.com/blog/2011/06/] explaining | ||
how to control the motors. We soon noticed that the device name is different on the AR.Drone2. We found out by using dmesg and trace functions that the devices are as follows: | how to control the motors. We soon noticed that the device name is different on the AR.Drone2. We found out by using dmesg and trace functions that the devices are as follows: | ||
Revision as of 01:52, 13 December 2012
Starting off with the project we first tried searching what had allready been done for AR.Drone1 and we found a very good source in the [Perquin blog|http://blog.perquin.com/blog/2011/06/] explaining how to control the motors. We soon noticed that the device name is different on the AR.Drone2. We found out by using dmesg and trace functions that the devices are as follows:
- /dev/ttyO0 : motor
After finding out what the correct device was, we could simply change the device name in the driver created by hugo[1]. This gave us a working motor driver.