Difference between revisions of "Module/GPS UBlox UCenter"

From PaparazziUAV
Jump to navigation Jump to search
m (Fixed spelling error)
(Updated to document pull request #653)
Line 2: Line 2:
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 that indicates the firmware version in your GPS, the previously selected GPS baudrate and the current (38k4).
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 will configure the following settings:
It will configure the following settings:
* set baudrate to 38400
* set baudrate to GPS_BAUD (typically either 38400 or 57600)
* enable the NAV_POSLLH, NAV_VELNED, NAV_STATUS, NAV_SVINFO, NAV_SOL
* enable the NAV_POSLLH, NAV_VELNED, NAV_STATUS, NAV_SVINFO, NAV_SOL
* disable UTM on old Lea4P by not sending NAV_POSUTM
* disable UTM on old Lea4P by not sending NAV_POSUTM
* enable SBAS
* enable SBAS
* configure it to 3D only fix and Airborne 2G
* configure it to 3D only fix
* set the internal dyanmic model to Airborne 2G




Line 20: Line 21:
</source>
</source>


In some cases, you will need to specify which UART of the GPS you are using. The tiny/ppzgps use ublox_internal_port1 (the default) but if for instance you use a LS-SAM or I2C device you need to configure:
You can specify to a different dynamic model for the u-blox to use and to receive a DEBUG message over telemetry


<source lang="xml">
<source lang="xml">
Line 26: Line 27:
     ...
     ...
     <load name="gps_ubx_ucenter.xml">
     <load name="gps_ubx_ucenter.xml">
<define name="GPS_PORT_ID" value="GPS_PORT_UART2" />
<define name="GPS_UBX_NAV5_DYNAMICS" value="NAV5_DYN_PORTABLE" />
<define name="DEBUG_GPS_UBX_UCENTER" value="TRUE" />
     </load>
     </load>
   </modules>
   </modules>

Revision as of 17:01, 3 March 2014

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 file and select to receive that message in your telemetry file. See the example below for more details.

It will configure the following settings:

  • set baudrate to GPS_BAUD (typically either 38400 or 57600)
  • enable the NAV_POSLLH, NAV_VELNED, NAV_STATUS, NAV_SVINFO, NAV_SOL
  • disable UTM on old Lea4P by not sending NAV_POSUTM
  • enable SBAS
  • configure it to 3D only fix
  • set the internal dyanmic model to Airborne 2G


Add the gps_ubx_ucenter module to the "modules" section in your aircraft configuration file:

  <modules>
    ...
    <load name="gps_ubx_ucenter.xml"/>
  </modules>

You can specify to a different dynamic model for the u-blox to use and to receive a DEBUG message over telemetry

  <modules>
    ...
    <load name="gps_ubx_ucenter.xml">
	<define name="GPS_UBX_NAV5_DYNAMICS" value="NAV5_DYN_PORTABLE" />
	<define name="DEBUG_GPS_UBX_UCENTER" value="TRUE" />
    </load>
  </modules>