AR Drone 2/Motor driver - Revision history

Flixr at 17:17, 30 September 2013

2013-09-30T17:17:18Z

← Older revision		Revision as of 11:17, 30 September 2013
Line 1:		Line 1:
	<categorytree style="float:right; clear:right; margin-left:1ex; border: 1px solid gray; padding: 0.7ex;" mode=pages>AR Drone 2</categorytree>		{\|align=right
			\|-
			\|<categorytree style="float:right; clear:right; margin-left:1ex; border: 1px solid gray; padding: 0.7ex;" mode=pages>AR Drone 2</categorytree>
			\|}

	== The motor driver ==		== The motor driver ==

Flixr at 17:14, 21 December 2012

2012-12-21T17:14:31Z

← Older revision		Revision as of 11:14, 21 December 2012
Line 1:		Line 1:
			<categorytree style="float:right; clear:right; margin-left:1ex; border: 1px solid gray; padding: 0.7ex;" mode=pages>AR Drone 2</categorytree>

	== The motor driver ==		== The motor driver ==
	Starting off with the project we first tried searching what had already been done for AR.Drone1 and we found a very good source: [http://blog.perquin.com/blog/2011/06/ Perquin blog]. This explained		Starting off with the project we first tried searching what had already been done for AR.Drone1 and we found a very good source: [http://blog.perquin.com/blog/2011/06/ Perquin blog]. This explained
Line 59:		Line 61:
	[[Category: Minor Team 1]]		[[Category: Minor Team 1]]
	[[Category: TU Delft - Autonomous Quadrotor]]		[[Category: TU Delft - Autonomous Quadrotor]]
			[[Category: AR Drone 2]]

Flixr: moved Motor driver AR.Drone2 to AR Drone 2/Motor driver

2012-12-21T17:07:49Z

moved Motor driver AR.Drone2 to AR Drone 2/Motor driver

← Older revision	Revision as of 11:07, 21 December 2012
(No difference)

Vincent van Hoek at 10:41, 13 December 2012

2012-12-13T10:41:29Z

← Older revision		Revision as of 04:41, 13 December 2012
Line 57:		Line 57:
	Having implemented this we can now control the motors using Pararazzi.		Having implemented this we can now control the motors using Pararazzi.

	[[Category: ~~Search and Rescue~~]]		[[Category: Minor Team 1]]
	[[Category: TU Delft - Autonomous Quadrotor]]		[[Category: TU Delft - Autonomous Quadrotor]]

Vincent van Hoek at 10:38, 13 December 2012

2012-12-13T10:38:13Z

← Older revision		Revision as of 04:38, 13 December 2012
Line 56:		Line 56:

	Having implemented this we can now control the motors using Pararazzi.		Having implemented this we can now control the motors using Pararazzi.

			[[Category: Search and Rescue]]
			[[Category: TU Delft - Autonomous Quadrotor]]

Vincent van Hoek at 10:35, 13 December 2012

2012-12-13T10:35:53Z

@@ 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 in the [Perquin blog|http://blog.perquin.com/blog/2011/06/] explaining
+== The motor driver ==
-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:
+Starting off with the project we first tried searching what had already been done for AR.Drone1 and we found a very good source: [http://blog.perquin.com/blog/2011/06/ Perquin blog]. This explained
-*/dev/ttyO0 : motor
+''*/dev/ttyPA1''
-After finding out what the correct device was, we could simply change the device name in the driver created by hugo[http://blog.perquin.com/blog/ar-drone-program-elf-replacement/].
+After initialization a PWM bit stream was sent to that device containing a 3 start bits, followed 9 bits for each motor and 1 stop bit. The data was send as a stream of five 8-bit unsigned integers. This means the data will look as follows:
 This gave us a working motor driver.

Vincent van Hoek at 08:52, 13 December 2012

2012-12-13T08:52:43Z

← Older revision		Revision as of 02:52, 13 December 2012
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:

Bdelrue: 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…"

2012-11-15T11:00:19Z

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…"

New page

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
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[http://blog.perquin.com/blog/ar-drone-program-elf-replacement/].
This gave us a working motor driver.