Difference between revisions of "Subsystem/gps"

From PaparazziUAV
Jump to navigation Jump to search
(added link to gps u-center module)
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.

Revision as of 16:21, 29 June 2012

Currently possible GPS subsystems are

type architectures firmwares notes
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 #167
mediatek_diy all fixedwing
nmea stm32 all only basic position and fix information, see #120

Just specify the appropriate subsystem in your firmware section.

File: conf/airframes/myplane.xml
  <firmware name="fixedwing or rotorcraft">
     ...
    <subsystem name="gps"               type="ublox"/>
  </firmware>

Configure Options

If a configure option is not specified the default is used.

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

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

File: conf/airframes/myplane.xml
  <firmware name="fixedwing or rotorcraft">
     ...
    <subsystem name="gps"               type="ublox">
      <configure name="GPS_BAUD"          value="B9600"/>
      <configure name="GPS_PORT"          value="UART0"/>
      <configure name="GPS_LED"           value="none"/>
    </subsystem>
  </firmware>

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 UART Tunnel and Configured with u-center
  • You can also use the GPS u-blox U-Center module to automatically configure baudrate and messages for your u-blox GPS on startup.