NMEA-0183 message: PTNL,PJK

Local coordinate position output

Some examples of the PTNL,PJK message string are:

$PTNL,PJK,202831.50,011112,+805083.350,N,+388997.346,E,10,09,1.5,GHT+25.478,M*77

$PTNL,PJK,010717.00,081796,+732646.511,N,+1731051.091,E,1,05,2.7,EHT+28.345,M*7C

PTNL,PJK message fields

Field

Meaning

0

Message ID $PTNL,PJK

1

UTC of position fix

2

Date

3

Northing, in meters

4

Direction of Northing will always be N (North)

5

Easting, in meters

6

Direction of Easting will always be E (East)

7

GPS Quality indicator:

0: Fix not available or invalid
1: Autonomous GPS fix
2: RTK float solution
3: RTK fix solution
4: Differential, code phase only solution (DGPS)
5: SBAS solution – WAAS/EGNOS/MSAS
6: RTK Float 3D network solution
7: RTK Fixed 3D network solution
8: RTK Float 2D network solution
9: RTK Fixed 2D network solution
10: OmniSTAR HP/XP solution
11: OmniSTAR VBS solution
12: Location RTK
13: Beacon DGPS
14: CenterPoint RTX, QZSS CLAS
15: xFill

8

Number of satellites in fix

9

DOP of fix

10

Height of Antenna Phase Center (see Note below)

11

M: height is measured in meters

12

The checksum data, always begins with *

NOTES –  

  • The PTNL,PJK message is longer than the NMEA-0183 standard of 80 characters.

  • If a user-defined geoid model, or an inclined plane is loaded into the receiver, then the NMEA PJK string will always report the orthometric height (the field starts with the letters GHT). If the latitude/longitude of the receiver is outside the user-defined geoid model bounds, then the height is shown as ellipsoidal height (the field starts with the letters EHT).

  • If the receiver does not have an application file, this string returns nothing in fields 3, 4, 5, 6, or 10.