Paparazzi vs X - Revision history

Dconger: added more comparison information and changed the layout to compare the two item by item

2012-08-17T07:06:37Z

added more comparison information and changed the layout to compare the two item by item

Esden at 18:19, 15 August 2012

2012-08-15T18:19:03Z

← Older revision		Revision as of 12:19, 15 August 2012
Line 1:		Line 1:
	This page aims to provide honest comparisons between paparazzi and other open source autopilot systems.		This page aims to provide honest comparisons between paparazzi and other open source autopilot systems.
	These comparisons can then be used for improving paparazzi, where there is something ~~a competitor~~ does which is 'better'.
			These comparisons can then be used for improving paparazzi, where there is something another platform does which is 'better'.

	== Paparazzi (fixed-wing) vs [http://diydrones.com/profiles/blogs/ardupilot-mega-home-page ArduPlane] ==		== Paparazzi (fixed-wing) vs [http://diydrones.com/profiles/blogs/ardupilot-mega-home-page ArduPlane] ==

G R: /* Airbourne Software */

2012-08-15T12:08:47Z

Airbourne Software

← Older revision		Revision as of 06:08, 15 August 2012
Line 71:		Line 71:
	Building the airside software requires the arduino IDE (which is cross-platform and open source). Most users of arduplane however are not expected to modify anything beyond the settings provided in the Mission Planner. The arduino environment is simpler for beginners to grasp than the embedded C of paparazzi. However, the current arduplane code is not particularly easy to read or modify due to the way it is written (may be due to the space constraints of the platform). Telemetry is via Mavlink, which is compatible with QGroundControl.		Building the airside software requires the arduino IDE (which is cross-platform and open source). Most users of arduplane however are not expected to modify anything beyond the settings provided in the Mission Planner. The arduino environment is simpler for beginners to grasp than the embedded C of paparazzi. However, the current arduplane code is not particularly easy to read or modify due to the way it is written (may be due to the space constraints of the platform). Telemetry is via Mavlink, which is compatible with QGroundControl.

	Extensibility is extremely limited compared to paparazzi - only peripherals sold by 3DR are supported (ultrasound, optical flow sensor etc). There is nothing compared to the paparazzi module ecosystem.		Extensibility is extremely limited compared to paparazzi - only peripherals sold by 3DR are supported (ultrasound, optical flow sensor etc). There is nothing compared to the paparazzi module ecosystem. This may be a function of the cathedral type development.

G R at 12:08, 15 August 2012

2012-08-15T12:08:16Z

← Older revision		Revision as of 06:08, 15 August 2012
Line 70:		Line 70:
	===Airbourne Software===		===Airbourne Software===
	Building the airside software requires the arduino IDE (which is cross-platform and open source). Most users of arduplane however are not expected to modify anything beyond the settings provided in the Mission Planner. The arduino environment is simpler for beginners to grasp than the embedded C of paparazzi. However, the current arduplane code is not particularly easy to read or modify due to the way it is written (may be due to the space constraints of the platform). Telemetry is via Mavlink, which is compatible with QGroundControl.		Building the airside software requires the arduino IDE (which is cross-platform and open source). Most users of arduplane however are not expected to modify anything beyond the settings provided in the Mission Planner. The arduino environment is simpler for beginners to grasp than the embedded C of paparazzi. However, the current arduplane code is not particularly easy to read or modify due to the way it is written (may be due to the space constraints of the platform). Telemetry is via Mavlink, which is compatible with QGroundControl.

			Extensibility is extremely limited compared to paparazzi - only peripherals sold by 3DR are supported (ultrasound, optical flow sensor etc). There is nothing compared to the paparazzi module ecosystem.

G R: /* Airbourne Software */

2012-08-15T12:04:13Z

Airbourne Software

← Older revision		Revision as of 06:04, 15 August 2012
Line 69:		Line 69:

	===Airbourne Software===		===Airbourne Software===
	Building the airside software requires the arduino IDE (which is cross-platform and open source). Most users of arduplane however are not expected to modify anything beyond the settings provided in the Mission Planner. ~~It could be argued that the~~ arduino environment is simpler than the embedded C of paparazzi. However, the current arduplane code is not particularly easy to read or modify due to the way it is written (may be due to the space constraints of the platform). Telemetry is via Mavlink, which is compatible with QGroundControl.		Building the airside software requires the arduino IDE (which is cross-platform and open source). Most users of arduplane however are not expected to modify anything beyond the settings provided in the Mission Planner. The arduino environment is simpler for beginners to grasp than the embedded C of paparazzi. However, the current arduplane code is not particularly easy to read or modify due to the way it is written (may be due to the space constraints of the platform). Telemetry is via Mavlink, which is compatible with QGroundControl.

G R: /* Ground Station */

2012-08-15T12:03:34Z

Ground Station

← Older revision		Revision as of 06:03, 15 August 2012
Line 60:		Line 60:

	At the top right hand of the application are two spinner buttons for serial port and baud rate, along with a connect button.		At the top right hand of the application are two spinner buttons for serial port and baud rate, along with a connect button.


	===Hardware===		===Hardware===

G R: /* Hardware */

2012-08-15T12:03:21Z

Hardware

← Older revision		Revision as of 06:03, 15 August 2012
Line 67:		Line 67:
	All board use full size servo headers, and also include RC input headers & a PPM encoder (PPM input is supported, but as an 'advanced' option).		All board use full size servo headers, and also include RC input headers & a PPM encoder (PPM input is supported, but as an 'advanced' option).
	All boards include an IMU. All boards connect to the host PC via USB, and use the arduino C++ preprocessor and uploader under the covers.		All boards include an IMU. All boards connect to the host PC via USB, and use the arduino C++ preprocessor and uploader under the covers.
			Hardware is tied to what the arduino ecosystem supports and therefore processors tend to be underpowered compared to virtually all competitors.

	===Airbourne Software===		===Airbourne Software===
	Building the airside software requires the arduino IDE (which is cross-platform and open source). Most users of arduplane however are not expected to modify anything beyond the settings provided in the Mission Planner. It could be argued that the arduino environment is simpler than the embedded C of paparazzi. However, the current arduplane code is not particularly easy to read or modify due to the way it is written (may be due to the space constraints of the platform). Telemetry is via Mavlink, which is compatible with QGroundControl.		Building the airside software requires the arduino IDE (which is cross-platform and open source). Most users of arduplane however are not expected to modify anything beyond the settings provided in the Mission Planner. It could be argued that the arduino environment is simpler than the embedded C of paparazzi. However, the current arduplane code is not particularly easy to read or modify due to the way it is written (may be due to the space constraints of the platform). Telemetry is via Mavlink, which is compatible with QGroundControl.

G R: /* Paparazzi (fixed-wing) vs ArduPlane */

2012-08-15T11:59:52Z

Paparazzi (fixed-wing) vs ArduPlane

← Older revision		Revision as of 05:59, 15 August 2012
Line 55:		Line 55:

	'Firmware' provides a window where we select the type of firmware to load onto the autopilot (fixed wing, quadrotor, hexrotor, okto, heli etc).		'Firmware' provides a window where we select the type of firmware to load onto the autopilot (fixed wing, quadrotor, hexrotor, okto, heli etc).
	The software downloads ~~a binary of~~ the latest firmware and uploads it to the autopilot.		The software downloads the latest firmware, compiles it and uploads it to the autopilot.

	'Terminal' provides a terminal (obviously) connected to the com port of the autopilot. In normal operation, it's full of garbage characters from mavlink.		'Terminal' provides a terminal (obviously) connected to the com port of the autopilot. In normal operation, it's full of garbage characters from mavlink.

	At the top right hand of the application are two spinner buttons for serial port and baud rate, along with a connect button.		At the top right hand of the application are two spinner buttons for serial port and baud rate, along with a connect button.


			===Hardware===
			Arduplane hardware is highly homogenised - only the current AP board generation and previous board are supported.
			Almost all AP boards are manufactured & sold by 3DR, who also lead development of arduplane. Obtaining prebuilt hardware is much easier than paparazzi - there are multiple distributors in most countries, plus the official 3DR store ships worldwide.
			All board use full size servo headers, and also include RC input headers & a PPM encoder (PPM input is supported, but as an 'advanced' option).
			All boards include an IMU. All boards connect to the host PC via USB, and use the arduino C++ preprocessor and uploader under the covers.

			===Airbourne Software===
			Building the airside software requires the arduino IDE (which is cross-platform and open source). Most users of arduplane however are not expected to modify anything beyond the settings provided in the Mission Planner. It could be argued that the arduino environment is simpler than the embedded C of paparazzi. However, the current arduplane code is not particularly easy to read or modify due to the way it is written (may be due to the space constraints of the platform). Telemetry is via Mavlink, which is compatible with QGroundControl.

G R: /* Ground Station */

2012-08-15T11:47:10Z

Ground Station

@@ Line 45: / Line 45: @@
 The ArduPlane 'Mission Planner' is an open source Microsoft .NET application. It handles flight monitoring, firmware loading & configuration, log file replays and video display. It is approximately a 15MB download, and also runs happily under mono on linux (other than video playback).
 and 64 bit installers are provided, along with a zip with the executables. Source code is provided via google code SVN.
 The 'Flight Data' tab shows current aircraft location on google maps on the right, along with a PFD and altitude, speed and battery data on a HUD on the left.

G R: /* First contact */

2012-08-15T11:38:57Z

First contact

← Older revision		Revision as of 05:38, 15 August 2012
Line 5:		Line 5:
	===First contact===		===First contact===
	The arduplane web presence is somewhat disjointed.		The arduplane web presence is somewhat disjointed.
	The 'official' home page (and first google result) is hosted on a subdomain of DIYDrones, but is basically a sales pitch. The call to action redirects to a google code wiki, which is the real home of arduplane.		The 'official' home page (and first google result) is hosted on a subdomain of DIYDrones, but is basically a sales pitch.

			The call to action redirects to a google code wiki, which is the real home of arduplane.
	The sidebar of the wiki contains the following:		The sidebar of the wiki contains the following: