AR Drone 2/GPS - Revision history

Flixr: move info from AR_Drone_2/GPS_Driver to here

2015-08-04T20:17:34Z

move info from AR_Drone_2/GPS_Driver to here

← Older revision		Revision as of 14:17, 4 August 2015
Line 61:		Line 61:

	Use the <tt>sirf</tt> gps subsystem.		Use the <tt>sirf</tt> gps subsystem.

			=== Connecting the Parrot GPS Dongle ===
			When we connected the GPS Receiver (GPS) to the AR Drone 2.0 (Drone) and searched on the Drone, we found out that nothing happened. After some research we found out that there was no USB serial driver available on the Drone to recognize the GPS. From USGlobalstat, the manufacturer of the GPS, we found out that we needed an pl2303 driver. On the internet another [http://www.drone-rk.org/wiki/ARDrone project] was reported and there they were installing drivers for the Drone. We followed these steps but some errors occurred because we are using an AR Drone 2.0.

			Once we found out that the Drone is running another version of Linux we have to change that. We had also some troubles with finding the right .config file to use. Finally we were able to make the modules, including the usbserial and pl2303, for the Drone.

			From the make step we were getting 2 files, usbserial.ko and pl2303.ko. We put those files on the Drone by using FTP. Once the files are on the Drone we connected to the Drone by Telnet and went to the /data/video folder were the files we located. By insmodding the .ko files we installed the drivers on the linux system and we were able to connect the GPS to the Drone.
			After connecting the GPS was recognized and was mounted to /dev/ttyUSB0.


	== Links ==		== Links ==

	~~IMPORTANT LINK:~~		* http://forum.parrot.com/ardrone/en/viewtopic.php?id=5331
	http://forum.parrot.com/ardrone/en/viewtopic.php?id=5331		* http://www.dronetec.co.uk/quadmod.html
	http://www.dronetec.co.uk/quadmod.html


	[[Category:AR Drone 2]]		[[Category:AR Drone 2]]

Flixr: add pic for gps dongle

2015-08-04T20:10:03Z

add pic for gps dongle

← Older revision		Revision as of 14:10, 4 August 2015
Line 58:		Line 58:

	== Parrot GPS Dongle ==		== Parrot GPS Dongle ==
			[[File:ParrotGPSOrangeFlightRecorderDongle.jpg\|left\|thumbnail\|Parrot GPS Dongle]]

	Use the <tt>sirf</tt> gps subsystem.		Use the <tt>sirf</tt> gps subsystem.

Flixr: move gps info from main AR Drone 2 page here and delete old useless stuff

2015-08-04T20:06:23Z

move gps info from main AR Drone 2 page here and delete old useless stuff

@@ Line 4: / Line 4: @@
 |}
-That way we could extract the received data from the GPS and output it in our preferred format.
+To fly autonomous to a certain geo coordinate a GPS is needed. Although it is theoretically possible to use the original orange Parrot GPS dongle it is not advised, the performance is just not good enough for great autonomous flights. The solution that '''is advised''' is to use an '''uBlox GPS''' module.
-To create our own driver, we first needed to know how to retrieve the data from the GPS. We downloaded the [http://www.usglobalsat.com/s-122-bu-353-support.aspx Linux USB Driver] and learned from the readme that you could use the GPS with the following commando:
- su root
+== uBlox ==
- stty -F /dev/ttyUSB0 ispeed 4800 && cat < /dev/ttyUSB0
+[[file:Ublox_gps_lea6q_top.jpg|200px]]
-With this we found out that we needed to create a program that opens the /dev/ttyUSB0 device and reads it at a baud rate of 4800. We had to pick a datatype since working with several datatypes at the same time would be confusing. Therefore we had to extract the right datatype string from the data strings output by the GPS and format that string into useful information.
+=== uBlox via serial ===
 [[Category:AR Drone 2]]

Flixr: add AR Drone 2 category and tree

2013-03-18T17:22:47Z

add AR Drone 2 category and tree

@@ Line 1: / Line 1: @@
 That way we could extract the received data from the GPS and output it in our preferred format.
 To create our own driver, we first needed to know how to retrieve the data from the GPS. We downloaded the [http://www.usglobalsat.com/s-122-bu-353-support.aspx Linux USB Driver] and learned from the readme that you could use the GPS with the following commando:
@@ Line 7: / Line 12: @@
 Later, when we were trying to integrate the GPS with paparazzi, we found out that there was already a parser for the protocol of the GPS: the NMEA. This parser (altough stated to be incomplete) provides most of the necassary data we wanted to use. We therefore ceased working on our own parser.

Flixr: moved GPS AR.Drone2 to AR Drone 2/GPS

2013-03-18T17:21:32Z

moved GPS AR.Drone2 to AR Drone 2/GPS

← Older revision	Revision as of 11:21, 18 March 2013
(No difference)

Bdelrue: Created page with "That way we could extract the received data from the GPS and output it in our preferred format. To create our own driver, we first needed to know how to retrieve the data from …"

2012-11-15T11:22:18Z

Created page with "That way we could extract the received data from the GPS and output it in our preferred format. To create our own driver, we first needed to know how to retrieve the data from …"

New page

That way we could extract the received data from the GPS and output it in our preferred format.
To create our own driver, we first needed to know how to retrieve the data from the GPS. We downloaded the [http://www.usglobalsat.com/s-122-bu-353-support.aspx Linux USB Driver] and learned from the readme that you could use the GPS with the following commando:
su root

stty -F /dev/ttyUSB0 ispeed 4800 && cat < /dev/ttyUSB0
With this we found out that we needed to create a program that opens the /dev/ttyUSB0 device and reads it at a baud rate of 4800. We had to pick a datatype since working with several datatypes at the same time would be confusing. Therefore we had to extract the right datatype string from the data strings output by the GPS and format that string into useful information.

Later, when we were trying to integrate the GPS with paparazzi, we found out that there was already a parser for the protocol of the GPS: the NMEA. This parser (altough stated to be incomplete) provides most of the necassary data we wanted to use. We therefore ceased working on our own parser.