GPS 0183 protocol GGA, GlL, GSA, GSV, RMC, Vtg, Zda, DTM Author: hiphopor

Source: Internet
Author: User
Tags in degrees time and date
Original article address:GPS 0183 protocol GGA, GlL, GSA, GSV, RMC, Vtg, Zda, DTM Author:Hiphopor
1. Standard nmea0183 statements (commonly used GPS statements)

$ Gpgga
Example: $ gpgga, 092204.999, 4250.5589, S, 14718.5084, E, 24.4, 19.7, 0000, M, * 1f
Field 0: $ gpgga, statement ID, indicating that the statement is Global Positioning System Fix Data (GGA) GPS location information
Field 1: UTC time, hhmmss. Sss, in the format of hour/minute/second
Field 2: latitude ddmm. Mmmm, degree score format (add 0 if the number of leading digits is insufficient)
Field 3: latitude N (north latitude) or S (south latitude)
Field 4: longitude dddmm. Mmmm, degree score format (add 0 if the number of leading digits is insufficient)
Field 5: longitude E (eastern longitude) or W (Western longitude)
Field 6: GPS status, 0 = undetermined, 1 = non-differential positioning, 2 = differential positioning, 3 = Invalid PPS, 6 = being estimated
Field 7: number of satellites in use (00-12) (0 if the number of leading digits is insufficient)
Field 8: hdop horizontal precision factor (0.5-99.9)
Field 9: altitude (-9999.9-99999.9)
Field 10: height of the earth's elliptical sphere relative to the geolevel
Field 11: differential time (the number of seconds from the last time the differential signal was received. If it is not a differential signal, it will be blank)
Field 12: ID of the differential substation: 0000-1023 (0 is added if the number of leading digits is insufficient. Otherwise, the differential positioning will be blank)
Field 13: Check Value

$ Gpgll
Example: $ gpgll, 4250.5589, S, 14718.5084, E, 092204.999, A * 2D
Field 0: $ gpgll, statement ID, indicating that the statement is geographic position (GlL) Location Information
Field 1: latitude ddmm. Mmmm, degree score format (add 0 if the number of leading digits is insufficient)
Field 2: latitude N (north latitude) or S (south latitude)
Field 3: longitude dddmm. Mmmm, degree score format (add 0 if the number of leading digits is insufficient)
Field 4: longitude E (eastern longitude) or W (Western longitude)
Field 5: UTC time, hhmmss. Sss format
Field 6: Status, A = positioning, V = uncertain
Field 7: Check Value

$ Gpgsa
Example: $ gpgsa, A, 40.4, 20, 19, 13, 24.4, 32.2 * 0a
Field 0: $ gpgsa, statement ID, indicating the current satellite information of gps dop and active satellites (GSA)
Field 1: positioning mode, a = automatic 2D/3d, M = manual 2D/3D
Field 2: positioning type, 1 = undetermined, 2 = 2D, 3 = 3D
Field 3: PRN code (Pseudo-Random Noise Code), number of the satellite PRN code used by the 1st channel (00) (0 if the number of leading digits is insufficient)
Field 4: PRN code (Pseudo-Random Noise Code), number of the satellite PRN code used by the 2nd channel (00) (0 if the number of leading digits is insufficient)
Field 5: PRN code (Pseudo-Random Noise Code), number of the satellite PRN code used by the 3rd channel (00) (0 if the number of leading digits is insufficient)
Field 6: PRN code (Pseudo-Random Noise Code), number of the satellite PRN code used by the 4th channel (00) (0 if the number of leading digits is insufficient)
Field 7: PRN code (Pseudo-Random Noise Code), number of the satellite PRN code used by the 5th channel (00) (0 if the number of leading digits is insufficient)
Field 8: PRN code (Pseudo-Random Noise Code), number of the satellite PRN code used by the 6th channel (00) (0 if the number of leading digits is insufficient)
Field 9: PRN code (Pseudo-Random Noise Code), number of the satellite PRN code used by the 7th channel (00) (0 if the number of leading digits is insufficient)
Field 10: PRN code (Pseudo-Random Noise Code), number of the satellite PRN code used by the 8th channel (00) (0 if the number of leading digits is insufficient)
Field 11: PRN code (Pseudo-Random Noise Code), number of the satellite PRN code used by the 9th channel (00) (0 if the number of leading digits is insufficient)
Field 12: PRN code (Pseudo-Random Noise Code), number of the satellite PRN code used by the 10th channel (00) (0 if the number of leading digits is insufficient)
Field 13: PRN code (Pseudo-Random Noise Code), number of the satellite PRN code used by the 11th channel (00) (0 if the number of leading digits is insufficient)
Field 14: PRN code (Pseudo-Random Noise Code), number of the satellite PRN code used by the 12th channel (00) (0 if the number of leading digits is insufficient)
Field 15: pdop comprehensive position precision factor (0.5-99.9)
Field 16: hdop horizontal precision factor (0.5-99.9)
Field 17: vdop vertical precision factor (0.5-99.9)
Field 18: Check Value

$ Gpgsv
Example: $ gpgsv, 78,331, 59,235, 41,069, * 70
Field 0: $ gpgsv, statement ID, indicating that the statement is GPS satellites in view (GSV) Visible satellite information
Field 1: Total number of GSV statements (1-3)
Field 2: The number of GSV statements in this GSV statement (1-3)
Field 3: Total number of visible satellites (00-12) (0 if the number of leading digits is insufficient)
Field 4: PRN code (Pseudo-Random Noise Code) (01-32) (add 0 if the number of leading digits is insufficient)
Field 5: Satellite elevation (00-90) degree (0 if the number of leading digits is insufficient)
Field 6: Satellite azimuth (00-359) degree (0 if the number of leading digits is insufficient)
Field 7: signal-to-noise ratio (00-99) dbhz
Field 8: PRN code (Pseudo-Random Noise Code) (01-32) (0 if the number of leading digits is insufficient)
Field 9: Satellite elevation (00-90) degree (0 if the number of leading digits is insufficient)
Field 10: Satellite azimuth (00-359) degree (0 if the number of leading digits is insufficient)
Field 11: signal-to-noise ratio (00-99) dbhz
Field 12: PRN code (Pseudo-Random Noise Code) (01-32) (add 0 if the number of leading digits is insufficient)
Field 13: Satellite elevation (00-90) degree (0 if the number of leading digits is insufficient)
Field 14: Satellite azimuth (00-359) degree (0 if the number of leading digits is insufficient)
Field 15: signal-to-noise ratio (00-99) dbhz
Field 16: Check Value

$ Uplmc
Example: $ gprs mc, 024813.640, A, 3158.4608, N, 11848.3737, E, 10.05, 324.27, 150706, A * 50
Field 0: $ uplmc, statement ID, indicating that the statement is the minimum location information recommended by recommended minimum specific GPS/transit data (RMC ).
Field 1: UTC time, hhmmss. Sss format
Field 2: Status, A = positioning, V = uncertain
Field 3: latitude ddmm. Mmmm, degree score format (add 0 if the number of leading digits is insufficient)
Field 4: latitude N (north latitude) or S (south latitude)
Field 5: longitude dddmm. Mmmm, degree score format (add 0 if the number of leading digits is insufficient)
Field 6: longitude E (eastern longitude) or W (Western longitude)
Field 7: speed, section, knots
Field 8: azimuth, Degree
Field 9: UTC date, in ddmmyy format
Field 10: Magnetic offset (180-) (0 if the number of leading digits is insufficient)
Field 11: Magnetic angle direction, E = east W = West
Field 16: Check Value

$ Gpvtg
Example: $ gpvtg, 89.68, T, M, 0.00, N, 0.0, K * 5f
Field 0: $ gpvtg, statement ID, indicating that the statement is track made good and ground speed (Vtg) ground speed information
Field 1: motion angle, 000-359 (0 if the number of leading digits is insufficient)
Field 2: t = zhenbei Reference System
Field 3: motion angle, 000-359 (0 if the number of leading digits is insufficient)
Field 4: M = magnetic north Frame
Field 5: horizontal speed (0.00) (0 if the number of leading digits is insufficient)
Field 6: N = Section, knots
Field 7: horizontal speed (0.00) (0 if the number of leading digits is insufficient)
Field 8: K = km/hour, km/h
Field 9: Check Value

Data and time (Zda) time and date information
$ Gpzda, <1 >,< 2 >,< 3 >,< 4 >,< 5> * hh <CR> <LF>
<1> UTC time, hhmmss (hour/minute/second) Format
<2> UTC date, Day
<3> UTC date, month
<4> UTC date, year <5> Time Zone

Datum (DTM) Coordinate System Information
$ Gpdtm, <1 >,< 2 >,< 3 >,< 4 >,< 5 >,< 6 >,< 7>, <8> * hh <CR> <LF>
<1> code of the local coordinate system w84
<2> the coordinate system subcode is empty.
<3> latitude offset
<4> latitude hemisphere N (northern hemisphere) or S (Southern Hemisphere)
<5> longitude offset
<6> longitude hemisphere E (eastern longitude) or W (Western longitude)
<7> height offset
<8> coordinate system code w84

Ii. Garmin-defined statements
1. Estimated Error information (pgrme) estimation error information
$ Pgrme, <1>, M, <2>, M, <3>, M * hh <CR> <LF>
<1> HPE (horizontal estimation error), 0.0 ~ 999.9 meters
<2> VPE (vertical estimation error), 0.0 ~ 999.9 meters
<3> EPE (location estimation error), 0.0 ~ 999.9 meters
2. GPS fix data sentence (pgrmf) GPS Positioning Information
$ Pgrmf, <1 >,< 2 >,< 3 >,< 4 >,< 5 >,< 6 >,< 7 >,< 8 >,< 9>, <10>, <11>, <12>, <13>, <14>, <15> * hh <CR> <LF

>
<1> Number of GPS weeks (0 ~ 1023)
<2> GPS seconds (0 ~ 604799)
<3> UTC date, in ddmmyy format
<4> UTC time, hhmmss (hour/minute/second) Format
<5> GPS jump seconds
<6> latitude ddmm. Mmmm (degree) format (the preceding 0 will also be transmitted)
<7> latitude hemisphere N (northern hemisphere) or S (Southern Hemisphere)
<8> longitude dddmm. Mmmm (degree) format (the preceding 0 will also be transmitted)
<9> longitude hemisphere E (eastern longitude) or W (Western longitude)
<10> mode, M = manual, a = automatic
<11> positioning type, 0 = No positioning, 1 = 2D positioning, 2 = 3D Positioning
<12> ground speed (0 ~ 1851/hour)
<13> ground heading (000 ~ 359 degrees, with zhenbei as the reference)
<14> position precision factor of pdop (0 ~ 9, rounded to an integer)
<15> tdop time precision factor (0 ~ 9, rounded to an integer)
3. Map datum (pgrmm) Coordinate System Information
$ Pgrmm, <1> * hh <CR> <LF>
<1> name of the currently used coordinate system (variable data length, for example, "WGS 84 ")
Note: This information is used for real-time connection with mapsource.
4. Sensor status information (pgrmt) working status information
$ Pgrmt, <1 >,< 2 >,< 3 >,< 4 >,< 5 >,< 6 >,< 7 >,< 8>, <9> * hh <CR> <LF>
<1> product model and software version (variable data length, for example, "GPS 15l/15 h ver 2.05 ")
<2> Rom verification test, P = passed, F = failed
<3> receiver discontinuous fault, P = pass, F = fail
<4> storage data, r = persistence, L = loss
<5> clock information, r = keep, L = Lost
<6> non-continuous oscillator drift, P = pass, F = over-drift Detected
<7> data is not collected consecutively. c = the data is being collected. It is null if no data is collected.
<8> GPS receiver temperature, in degrees Celsius
<9> GPS receiver configuration data, r = maintained, L = Lost
Note: This statement is sent once per minute, regardless of the selected baud rate.
5. 3D velocity information (pgrmv) 3D speed information
$ Pgrmv, <1 >,< 2 >,< 3> * hh <CR> <LF>
<1> easterly speed, 514.4 ~ 514.4 meters/second
<2> North speed, 514.4 ~ 514.4 meters/second
<3> uplink speed: 999.9 ~ 9999.9 meters/second
6. DGPS beacon information (pgrmb) Beacon difference Information
$ Pgrmb, <1>, <2>, <3>, <4>, <5>, K, <6>, <7>, <8> * hh <CR> <LF>
<1> beacon station frequency (0.0, 283.5 ~ 325.0 kHz, interval: 0.5 kHz)
<2> beacon bit rate (50,100, or BPS)
<3> SNR signal-to-noise ratio (0 ~ 31)
<4> beacon data quality (0 ~ 100)
<5> distance from the beacon station, measured in kilometers
<6> beacon receiver communication status, 0 = check wiring, 1 = no signal, 2 = tuning, 3 = Receiving, 4 = Scanning
<7> differential source, r = RTCM, W = WAAS, n = non-differential location
<8> differential status, A = automatic, W = only WAAS, r = only RTCM, n = no differential signal received

Iii. Text format description:

   Region description:            Length:  Note:
   ------------------------------------------------------
   Period start character            1     Always '@'
   ------------------------------------------------------
  /Year                    2     The last two digits of UTC
| ------------------------------------------------------
| Month                    2     UTC month, "01"... "12"
T | ------------------------------------------------------
I | day                    2     UTC, "01" .. "31"
M | ------------------------------------------------------
E | hour                    2     UTC, "00"... "23"
| ------------------------------------------------------
| Minute                    2     UTC, "00" .. "59"
| ------------------------------------------------------
  Seconds                    2     UTC seconds, "00" .. "59"
   ------------------------------------------------------
  /Latitude hemisphere              1 

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.