Module/GPS UBlox UCenter - Revision history

Simmis: Be quick when you want to capture the debug message.

2015-10-10T16:40:14Z

Be quick when you want to capture the debug message.

← Older revision		Revision as of 10:40, 10 October 2015
Line 118:		Line 118:
	* [18] Success of saving configuration to ublox memory		* [18] Success of saving configuration to ublox memory

	If you get all zeroes then check cabling and try again. Make sure RX from the GPS is connected to TX on the autopilot.		The debug message is '''sent only once''' a few seconds after powering on. Make sure to have messages displayed before powering on to make sure to capture it. If you get all zeroes then check cabling and try again. Make sure RX from the GPS is connected to TX on the autopilot.


	[[Category:User_Documentation]] [[Category:Modules]]		[[Category:User_Documentation]] [[Category:Modules]]

2015-07-09T16:27:42Z

no need to enable the DEBUG message in the telemetry file

← Older revision		Revision as of 10:27, 9 July 2015
Line 3:		Line 3:
	If you use a µ-blox GPS without flash memory, this module will take over the task of initializing the GPS for you when you power your autopilot.		If you use a µ-blox GPS without flash memory, this module will take over the task of initializing the GPS for you when you power your autopilot.

	It has auto-baudrate to detect the current GPS baudrate, and configures all message rates and communication ports. The module will send a DEBUG message (ID 26) that indicates the firmware version in your GPS, the previous baudrate, and the reply for each configuration step. To enable and view the message, you will need to define DEBUG_GPS_UBX_UCENTER as TRUE in your [[Airframe_Configuration\|airframe configuration~~]] file and select to receive that message in your [[Telemetry\|telemetry~~]] file. See the example below for more details.		It has auto-baudrate to detect the current GPS baudrate, and configures all message rates and communication ports. The module will send a DEBUG message (ID 26) that indicates the firmware version in your GPS, the previous baudrate, and the reply for each configuration step. To enable and view the message, you will need to define DEBUG_GPS_UBX_UCENTER as TRUE in your [[Airframe_Configuration\|airframe configuration]] file. See the example below for more details.

	It will configure the following settings:		It will configure the following settings:

2015-07-07T13:06:32Z

Debug

← Older revision		Revision as of 07:06, 7 July 2015
Line 84:		Line 84:
	== Debug ==		== Debug ==

	You can specify to receive a DEBUG message over telemetry~~. Make changes to both the~~ airframe ~~and telemetry config files.~~		You can specify to receive a DEBUG message over telemetry by enabling it in your airframe file:
	{{Box Code\|conf/airframes/myplane.xml\|		{{Box Code\|conf/airframes/myplane.xml\|
	<source lang="xml">		<source lang="xml">

2015-07-07T13:04:21Z

Debug

← Older revision		Revision as of 07:04, 7 July 2015
Line 97:		Line 97:
	}}		}}

	~~{{Box Code\|conf/telemetry/myplane.xml\|~~		The DEBUG message has the following information:
	~~<source lang="xml">~~
	~~<mode name="default">~~
	~~...~~
	<message ~~name="DEBUG" period="0.5"/>~~
	~~</mode>~~
	~~</source>~~
	}}

	~~The debug messages~~ has the following information:
	* [0] Initial baudrate high		* [0] Initial baudrate high
	* [1] Initial baudrate low. For example if the baud rate is 9600 you will see 9,6		* [1] Initial baudrate low. For example if the baud rate is 9600 you will see 9,6

2014-06-03T02:52:01Z

Debug

← Older revision		Revision as of 20:52, 2 June 2014
Line 114:		Line 114:
	* [5] ublox hardware version low		* [5] ublox hardware version low
	* [6] Always 0		* [6] Always 0
	* [7] Success of setting CFG-NAV5		* [7] Success of setting CFG-NAV5. For all of these a value of 0 indicates no response, 1 is success and 2 is command rejected by GPS.
	* [8] Success of enable NAV-POSLLH		* [8] Success of enable NAV-POSLLH
	* [9] Success of enable NAV-VELNED		* [9] Success of enable NAV-VELNED

2014-06-03T02:12:58Z

Debug: some clarifications and tips

← Older revision		Revision as of 20:12, 2 June 2014
Line 108:		Line 108:
	The debug messages has the following information:		The debug messages has the following information:
	* [0] Initial baudrate high		* [0] Initial baudrate high
	* [1] Initial baudrate low		* [1] Initial baudrate low. For example if the baud rate is 9600 you will see 9,6
	* [2] ublox software verision high		* [2] ublox software verision high
	* [3] ublox software version low		* [3] ublox software version low
Line 127:		Line 127:
	* [18] Success of saving configuration to ublox memory		* [18] Success of saving configuration to ublox memory

			If you get all zeroes then check cabling and try again. Make sure RX from the GPS is connected to TX on the autopilot.


	[[Category:User_Documentation]] [[Category:Modules]]		[[Category:User_Documentation]] [[Category:Modules]]

2014-03-20T16:53:52Z

Added table describing the dynamics models

@@ Line 40: / Line 40: @@
 </source>
 }}
 == Debug ==

2014-03-15T18:36:09Z

← Older revision		Revision as of 12:36, 15 March 2014
Line 1:		Line 1:
			__TOC__
	<categorytree style="float:right; clear:right; margin-left:1ex; border: 1px solid gray; padding: 0.7ex;" mode=pages>Modules</categorytree>		<categorytree style="float:right; clear:right; margin-left:1ex; border: 1px solid gray; padding: 0.7ex;" mode=pages>Modules</categorytree>
	If you use a µ-blox GPS without flash memory, this module will take over the task of initializing the GPS for you when you power your autopilot.		If you use a µ-blox GPS without flash memory, this module will take over the task of initializing the GPS for you when you power your autopilot.

2014-03-14T00:52:24Z

Debug

← Older revision		Revision as of 18:52, 13 March 2014
Line 71:		Line 71:
	* [4] ublox hardware version high		* [4] ublox hardware version high
	* [5] ublox hardware version low		* [5] ublox hardware version low
	* [6] Success of setting CFG-NAV5		* [6] Always 0
	* [7] Success of enable NAV-POSLLH		* [7] Success of setting CFG-NAV5
	* [8] Success of enable NAV-VELNED		* [8] Success of enable NAV-POSLLH
	* [9] Success of enable NAV-STATUS		* [9] Success of enable NAV-VELNED
	* [10] Success of enable NAV-SVINFO		* [10] Success of enable NAV-STATUS
	* [11] Success of enable NAV-SOL		* [11] Success of enable NAV-SVINFO
	* [12] Success of disabling NAV-POSUTM (typically fails to 0 for non LEA-4P modules)		* [12] Success of enable NAV-SOL
	* [13] Success of enable SBAS		* [13] Success of disabling NAV-POSUTM (typically fails to 0 for non LEA-4P modules)
	* [14] Success of setting CFG-RATE		* [14] Success of enable SBAS
	* [15] Success of setting RXM-RAW (typically disabled - see USE_GPS_UBX_RXM_RAW flag to enable)		* [15] Success of setting CFG-RATE
	* [16] Success of setting RXM-SFRB (typically disabled - see USE_GPS_UBX_RXM_SFRB flag to enable)		* [16] Success of setting RXM-RAW (typically disabled - see USE_GPS_UBX_RXM_RAW flag to enable)
	* [17] Success of saving configuration to ublox memory		* [17] Success of setting RXM-SFRB (typically disabled - see USE_GPS_UBX_RXM_SFRB flag to enable)
			* [18] Success of saving configuration to ublox memory

2014-03-14T00:47:54Z

Description of the DEBUG message

@@ Line 40: / Line 40: @@
 }}
 You can specify to receive a DEBUG message over telemetry. Make changes to both the airframe and telemetry config files.
@@ Line 62: / Line 63: @@
 </source>
 }}
 [[Category:User_Documentation]] [[Category:Modules]]