GCS - Revision history

Fabien-B at 10:20, 15 October 2021

2021-10-15T10:20:37Z

← Older revision		Revision as of 04:20, 15 October 2021
Line 11:		Line 11:
	\|}		\|}

	!New: There is a new GCS available at [https://~~gihutb~~.com/Fabien-B/PprzGCS]!		!New: There is a new GCS available at https://github.com/Fabien-B/PprzGCS!

	= Introduction =		= Introduction =

Fabien-B at 10:19, 15 October 2021

2021-10-15T10:19:10Z

← Older revision		Revision as of 04:19, 15 October 2021
Line 10:		Line 10:
	[[Image:gcs.jpg\|frame\|left\|The Paparazzi Ground Control Station is the heart of the system and the user's primary interaction interface.]] [[Image:GCSParrotardroneandpaparazzi.jpg\|frame\|right\|The GCS is very flexible in the way you can change the look and add functionality. One only need to change a configuration file. For example, the look when using the configuration GCS setting for Paparazzi Parrot AR Drone 2]]		[[Image:gcs.jpg\|frame\|left\|The Paparazzi Ground Control Station is the heart of the system and the user's primary interaction interface.]] [[Image:GCSParrotardroneandpaparazzi.jpg\|frame\|right\|The GCS is very flexible in the way you can change the look and add functionality. One only need to change a configuration file. For example, the look when using the configuration GCS setting for Paparazzi Parrot AR Drone 2]]
	\|}		\|}

			!New: There is a new GCS available at [https://gihutb.com/Fabien-B/PprzGCS]!

	= Introduction =		= Introduction =

Rijesh: Added cam footprint link

2017-10-18T22:23:42Z

Added cam footprint link

← Older revision		Revision as of 16:23, 18 October 2017
Line 74:		Line 74:
	* The intended trajectory is shown as a green line, in this example a circle around waypoint 2.		* The intended trajectory is shown as a green line, in this example a circle around waypoint 2.
	* The default background is black. [[Maps\|Maps]] can be loaded to provide navigation reference.		* The default background is black. [[Maps\|Maps]] can be loaded to provide navigation reference.
	* The camera footprint (the grey polygon) is representative of the swath of land currently seen by the onboard camera. This option default is off. It can be activated with the ''Cam footprint'' option from the A/C menu. see also [[Pan_Tilt_Camera]]		* The camera footprint (the grey polygon) is representative of the swath of land currently seen by the onboard camera. This option default is off. It can be activated with the ''[[Cam_Footprint\|Cam footprint]]'' option from the A/C menu. see also [[Pan_Tilt_Camera]]
	* The WGS84 coordinates of the mouse cursor are displayed at the top right hand corner (43.462019 1.270474).		* The WGS84 coordinates of the mouse cursor are displayed at the top right hand corner (43.462019 1.270474).
	* A UTM kilometric grid can be added to the background ''via'' the ''UTM grid'' option from the ''Nav'' menu.		* A UTM kilometric grid can be added to the background ''via'' the ''UTM grid'' option from the ''Nav'' menu.

Earthpatrol at 19:44, 22 November 2015

2015-11-22T19:44:59Z

← Older revision		Revision as of 13:44, 22 November 2015
Line 336:		Line 336:
	== Airframe Specific GCS Customizations ==		== Airframe Specific GCS Customizations ==

	Items related to the aircraft icon, altitude ~~up/down~~ values, speech id, and the overall icon theme of the GCS can be customized in each aircraft's [[Airframe_Configuration#GCS\|airframe configuration file GCS section]].		Items related to the ''aircraft icon'', ''altitude shift values'', ''speech id'', and the overall ''icon theme'' of the GCS can be customized in each aircraft's [[Airframe_Configuration#GCS\|airframe configuration file GCS section]].

	=Related Links=		=Related Links=

Earthpatrol: /* Options */

2015-11-22T19:43:37Z

Options

← Older revision		Revision as of 13:43, 22 November 2015
Line 333:		Line 333:

	These alarms can be provided via the speaker using the [[speech]] function.		These alarms can be provided via the speaker using the [[speech]] function.

			== Airframe Specific GCS Customizations ==

			Items related to the aircraft icon, altitude up/down values, speech id, and the overall icon theme of the GCS can be customized in each aircraft's [[Airframe_Configuration#GCS\|airframe configuration file GCS section]].

	=Related Links=		=Related Links=

Openuas at 18:06, 18 August 2015

2015-08-18T18:06:35Z

← Older revision		Revision as of 12:06, 18 August 2015
Line 309:		Line 309:

	===Aircraft binding===		===Aircraft binding===
	~~Until~~ Paparazzi '''v5.4''', Papgets ~~are~~ not ~~bind~~ to a specific aircraft~~, which means~~ that it will work with any of them, ~~but that~~ when multiple aircraft are flying the display of messages is mixed and the buttons will send command or settings to all active aircraft.		Upto Paparazzi '''v5.4''', Papgets could not not bound to a specific aircraft. This had the effect that it will work with any of them, and when multiple aircraft are flying the display of messages is mixed and the buttons will send command or settings to all active aircraft.

	Since Paparazzi '''v5.6''', ~~drag-and-dropped~~ Papgets are ~~bind~~ to a single aircraft, which means that they can safely be used with several active aircraft. It is also possible to add a property to the GCS layout file to specify the aircraft ID:		Since Paparazzi '''v5.6''', Papgets are bound to a single aircraft, which means that they can safely be used with several active aircraft. It is also possible to add a property to the GCS layout file to specify the aircraft ID:
	<source lang="xml">		<source lang="xml">
	<property name="ac_id" value="10"/>		<property name="ac_id" value="10"/>
	</source>		</source>
	Valid IDs are from 1 to 255 (0 being reserved to GCS). When this property is not defined, the Papget will bind to any aircraft like before. This can be useful if you intent to build a generic layout. When saving a layout from the GCS, if their are some Papgets to save, a question box will prompt the user to ask if the <tt>ac_id</tt> property should be saved or not.
			Valid IDs are from 1 to 255 (0 being reserved to GCS). '''When''' this property is '''not''' defined, the Papget will bind to '''any aircraft like before'''. This can be useful if you intent to build a generic layout. When saving a layout from the GCS, if their are some Papgets to save, a question box will prompt the user to ask if the <tt>ac_id</tt> property should be saved or not.

	===Papget Development===		===Papget Development===

Openuas: version to PPRZ

2015-08-18T18:04:05Z

version to PPRZ

← Older revision		Revision as of 12:04, 18 August 2015
Line 309:		Line 309:

	===Aircraft binding===		===Aircraft binding===
	Until ~~version~~ '''v5.4''', Papgets are not bind to a specific aircraft, which means that it will work with any of them, but that when multiple aircraft are flying the display of messages is mixed and the buttons will send command or settings to all active aircraft.		Until Paparazzi '''v5.4''', Papgets are not bind to a specific aircraft, which means that it will work with any of them, but that when multiple aircraft are flying the display of messages is mixed and the buttons will send command or settings to all active aircraft.

	Since ~~version~~ '''v5.6''', drag-and-dropped Papgets are bind to a single aircraft, which means that they can safely be used with several active aircraft. It is also possible to add a property to the GCS layout file to specify the aircraft ID:		Since Paparazzi '''v5.6''', drag-and-dropped Papgets are bind to a single aircraft, which means that they can safely be used with several active aircraft. It is also possible to add a property to the GCS layout file to specify the aircraft ID:
	<source lang="xml">		<source lang="xml">
	<property name="ac_id" value="10"/>		<property name="ac_id" value="10"/>

Openuas: 5.5 is not a release version

2015-08-18T18:03:21Z

5.5 is not a release version

← Older revision		Revision as of 12:03, 18 August 2015
Line 311:		Line 311:
	Until version '''v5.4''', Papgets are not bind to a specific aircraft, which means that it will work with any of them, but that when multiple aircraft are flying the display of messages is mixed and the buttons will send command or settings to all active aircraft.		Until version '''v5.4''', Papgets are not bind to a specific aircraft, which means that it will work with any of them, but that when multiple aircraft are flying the display of messages is mixed and the buttons will send command or settings to all active aircraft.

	Since version '''v5.5''', drag-and-dropped Papgets are bind to a single aircraft, which means that they can safely be used with several active aircraft. It is also possible to add a property to the GCS layout file to specify the aircraft ID:		Since version '''v5.6''', drag-and-dropped Papgets are bind to a single aircraft, which means that they can safely be used with several active aircraft. It is also possible to add a property to the GCS layout file to specify the aircraft ID:
	<source lang="xml">		<source lang="xml">
	<property name="ac_id" value="10"/>		<property name="ac_id" value="10"/>

Openuas at 12:52, 4 February 2015

2015-02-04T12:52:08Z

← Older revision		Revision as of 06:52, 4 February 2015
Line 8:		Line 8:
	\|__TOC__		\|__TOC__
	\|		\|
	[[Image:gcs.jpg\|frame\|left\|The Paparazzi Ground Control Station is the heart of the system and the user's primary interaction interface.]] [[Image:GCSParrotardroneandpaparazzi.jpg\|right\|~~370px\| THe~~ GCS is very flexible in the way you can change the look and add functionality. One only need to change a configuration file. For example, the look when using the configuration GCS setting for Paparazzi Parrot AR Drone 2]]		[[Image:gcs.jpg\|frame\|left\|The Paparazzi Ground Control Station is the heart of the system and the user's primary interaction interface.]] [[Image:GCSParrotardroneandpaparazzi.jpg\|frame\|right\|The GCS is very flexible in the way you can change the look and add functionality. One only need to change a configuration file. For example, the look when using the configuration GCS setting for Paparazzi Parrot AR Drone 2]]
	\|}		\|}

Ghattenb: /* Papgets */

2015-01-22T22:17:07Z

Papgets

← Older revision		Revision as of 16:17, 22 January 2015
Line 307:		Line 307:
	</papget>		</papget>
	</source>		</source>

			===Aircraft binding===
			Until version '''v5.4''', Papgets are not bind to a specific aircraft, which means that it will work with any of them, but that when multiple aircraft are flying the display of messages is mixed and the buttons will send command or settings to all active aircraft.

			Since version '''v5.5''', drag-and-dropped Papgets are bind to a single aircraft, which means that they can safely be used with several active aircraft. It is also possible to add a property to the GCS layout file to specify the aircraft ID:
			<source lang="xml">
			<property name="ac_id" value="10"/>
			</source>
			Valid IDs are from 1 to 255 (0 being reserved to GCS). When this property is not defined, the Papget will bind to any aircraft like before. This can be useful if you intent to build a generic layout. When saving a layout from the GCS, if their are some Papgets to save, a question box will prompt the user to ask if the <tt>ac_id</tt> property should be saved or not.

	===Papget Development===		===Papget Development===