Subsystem/gps - Revision history

IHaveADrone: changed code to xml

2014-08-19T14:08:32Z

changed code to xml

← Older revision		Revision as of 08:08, 19 August 2014
Line 19:		Line 19:
	Just specify the appropriate subsystem in your firmware section.		Just specify the appropriate subsystem in your firmware section.
	{{Box Code\|conf/airframes/myplane.xml\|		{{Box Code\|conf/airframes/myplane.xml\|
	<~~pre~~>		<source lang="xml">
	<firmware name="fixedwing or rotorcraft">		<firmware name="fixedwing or rotorcraft">
	...		...
	<subsystem name="gps" type="ublox"/>		<subsystem name="gps" type="ublox"/>
	</firmware>		</firmware>
	</~~pre~~>		</source>
	}}		}}

Line 41:		Line 41:
	If you use different baud rates or UART set the according parameters, e.g.		If you use different baud rates or UART set the according parameters, e.g.
	{{Box Code\|conf/airframes/myplane.xml\|		{{Box Code\|conf/airframes/myplane.xml\|
	<~~pre~~>		<source lang="xml">
	<firmware name="fixedwing or rotorcraft">		<firmware name="fixedwing or rotorcraft">
	...		...
Line 50:		Line 50:
	</subsystem>		</subsystem>
	</firmware>		</firmware>
	</~~pre~~>		</source>
	}}		}}

Flixr: add sirf

2014-05-13T12:03:48Z

add sirf

← Older revision		Revision as of 06:03, 13 May 2014
Line 13:		Line 13:
	\|-		\|-
	\|''nmea'' \|\| stm32 \|\| all \|\| only basic position and fix information, see [https://github.com/paparazzi/paparazzi/issues/120 #120, fixed]		\|''nmea'' \|\| stm32 \|\| all \|\| only basic position and fix information, see [https://github.com/paparazzi/paparazzi/issues/120 #120, fixed]
			\|-
			\| ''sirf'' \|\| all \|\| rotorcraft \|\|
	\|}		\|}

AndrewChambers: Describing location to find default values

2014-02-25T19:38:26Z

Describing location to find default values

← Older revision		Revision as of 13:38, 25 February 2014
Line 26:		Line 26:

	=== Configure Options ===		=== Configure Options ===
	If a configure option is not specified the default is used.		If a configure option is not specified the default is used.

	* '''GPS_PORT''': ''UART0'', ''UART1'', etc.		* '''GPS_PORT''': ''UART0'', ''UART1'', etc.
	** default: The correct UART is already defined according to your board.		** default: The correct UART is already defined according to your board.
	* '''GPS_BAUD''': ''B4800'', ''B9600'', ''B38400'', ''B57600'', ''B115200''		* '''GPS_BAUD''': ''B4800'', ''B9600'', ''B38400'', ''B57600'', ''B115200''
	** default: ''B38400''		** default: Already defined according to your board (e.g. ''B38400'' for Lisa/M v2.0).
	* '''GPS_LED''': ''1'', ''2'', ''3'', ''none''		* '''GPS_LED''': ''1'', ''2'', ''3'', ''none''
	** default: Already defined according to your board (e.g. ''2'' for tiny2 or twog).		** default: Already defined according to your board (e.g. ''2'' for tiny2 or twog).

			Defaults can be found in the board makefile (e.g. conf/boards/ardrone2_raw.makefile).

	If you use different baud rates or UART set the according parameters, e.g.		If you use different baud rates or UART set the according parameters, e.g.

NeoFromMatrix at 15:10, 9 August 2013

2013-08-09T15:10:35Z

← Older revision		Revision as of 09:10, 9 August 2013
Line 8:		Line 8:
	\|''ublox_utm'' \|\| all \|\| fixedwing \|\| for the older ublox4 series that still have a UTM message		\|''ublox_utm'' \|\| all \|\| fixedwing \|\| for the older ublox4 series that still have a UTM message
	\|-		\|-
	\|''skytraq'' \|\| all \|\| rotorcraft \|\| some fields missing in the skytraq protocol for fixedwings, see [https://github.com/paparazzi/paparazzi/issues/167 #167]		\|''skytraq'' \|\| all \|\| rotorcraft \|\| some fields missing in the skytraq protocol for fixedwings, see [https://github.com/paparazzi/paparazzi/issues/167 #167, fixed]
	\|-		\|-
	\|''mediatek_diy '' \|\| all \|\| fixedwing \|\|		\|''mediatek_diy '' \|\| all \|\| fixedwing \|\|

NeoFromMatrix at 15:10, 9 August 2013

2013-08-09T15:10:03Z

← Older revision		Revision as of 09:10, 9 August 2013
Line 12:		Line 12:
	\|''mediatek_diy '' \|\| all \|\| fixedwing \|\|		\|''mediatek_diy '' \|\| all \|\| fixedwing \|\|
	\|-		\|-
	\|''nmea'' \|\| stm32 \|\| all \|\| only basic position and fix information, see [https://github.com/paparazzi/paparazzi/issues/120 #120]		\|''nmea'' \|\| stm32 \|\| all \|\| only basic position and fix information, see [https://github.com/paparazzi/paparazzi/issues/120 #120, fixed]
	\|}		\|}

Flixr at 15:39, 7 February 2013

2013-02-07T15:39:27Z

← Older revision		Revision as of 09:39, 7 February 2013
Line 50:		Line 50:

	'''Notes:'''		'''Notes:'''
	* u-blox GPS modules are factory configured for 9600 baud, 38,400 baud is recommended along with the other required changes. The GPS can be accessed directly thrugh the [[~~Compiling#USB_flashing~~\|UART Tunnel]] and [[GPS#GPS_configuration_using_U-Center\|Configured with u-center]]		* u-blox GPS modules are factory configured for 9600 baud, 38,400 baud is recommended along with the other required changes. The GPS can be accessed directly thrugh the [[tunnel\|UART Tunnel]] and [[GPS#GPS_configuration_using_U-Center\|Configured with u-center]]
	* You can also use the [[Module/GPS_UBlox_UCenter\|GPS u-blox U-Center module]] to automatically configure baudrate and messages for your u-blox GPS on startup.		* You can also use the [[Module/GPS_UBlox_UCenter\|GPS u-blox U-Center module]] to automatically configure baudrate and messages for your u-blox GPS on startup.


	[[Category:User_Documentation]] [[Category:Subsystems]]		[[Category:User_Documentation]] [[Category:Subsystems]]

Flixr at 22:21, 29 June 2012

2012-06-29T22:21:38Z

← Older revision		Revision as of 16:21, 29 June 2012
Line 1:		Line 1:
	<categorytree style="float:right; clear:right; margin-left:1ex; border: 1px solid gray; padding: 0.7ex;" mode=pages hideprefix=always>Subsystems</categorytree>		<categorytree style="float:right; clear:right; margin-left:1ex; border: 1px solid gray; padding: 0.7ex;" mode=pages hideprefix=always>Subsystems</categorytree>
	Currently possible GPS subsystems are		Currently possible GPS subsystems are
	* ''ublox''		{\| class="wikitable" style="text-align:center" border="1"
	* ''ublox_utm'' for the older ublox4 series that still have a UTM message		! type !! architectures !! firmwares !! notes
	* ''skytraq''		\|-
	* ''mediatek_diy ''		\|''ublox'' \|\| all \|\| all \|\| recommended
			\|-
			\|''ublox_utm'' \|\| all \|\| fixedwing \|\| for the older ublox4 series that still have a UTM message
			\|-
			\|''skytraq'' \|\| all \|\| rotorcraft \|\| some fields missing in the skytraq protocol for fixedwings, see [https://github.com/paparazzi/paparazzi/issues/167 #167]
			\|-
			\|''mediatek_diy '' \|\| all \|\| fixedwing \|\|
			\|-
			\|''nmea'' \|\| stm32 \|\| all \|\| only basic position and fix information, see [https://github.com/paparazzi/paparazzi/issues/120 #120]
			\|}

	Just specify the appropriate subsystem in your firmware section.		Just specify the appropriate subsystem in your firmware section.

Flixr: added link to gps u-center module

2012-04-05T08:27:57Z

added link to gps u-center module

← Older revision		Revision as of 02:27, 5 April 2012
Line 40:		Line 40:
	}}		}}

	'''~~Note~~:'''		'''Notes:'''
	* u-blox GPS modules are factory configured for 9600 baud, 38,400 baud is recommended along with the other required changes. The GPS can be accessed directly thrugh the [[Compiling#USB_flashing\|UART Tunnel]] and [[GPS#GPS_configuration_using_U-Center\|Configured with u-center]]		* u-blox GPS modules are factory configured for 9600 baud, 38,400 baud is recommended along with the other required changes. The GPS can be accessed directly thrugh the [[Compiling#USB_flashing\|UART Tunnel]] and [[GPS#GPS_configuration_using_U-Center\|Configured with u-center]]
			* You can also use the [[Module/GPS_UBlox_UCenter\|GPS u-blox U-Center module]] to automatically configure baudrate and messages for your u-blox GPS on startup.


	[[Category:User_Documentation]] [[Category:Subsystems]]		[[Category:User_Documentation]] [[Category:Subsystems]]

Flixr at 22:05, 4 March 2012

2012-03-04T22:05:26Z

← Older revision		Revision as of 16:05, 4 March 2012
Line 1:		Line 1:
			<categorytree style="float:right; clear:right; margin-left:1ex; border: 1px solid gray; padding: 0.7ex;" mode=pages hideprefix=always>Subsystems</categorytree>
	Currently possible GPS subsystems are		Currently possible GPS subsystems are
	* ''ublox''		* ''ublox''

Flixr: removed software category, as modules is a subcategory of software

2012-03-01T22:30:48Z

removed software category, as modules is a subcategory of software

← Older revision		Revision as of 16:30, 1 March 2012
Line 43:		Line 43:


	~~[[Category:Software]]~~ [[Category:User_Documentation]] [[Category:Subsystems]]		[[Category:User_Documentation]] [[Category:Subsystems]]