Skip to main content

NMEA-Sentences

NMEA Sentences Overview​

Sentence Construction and Contents​

All Iridium PNT NMEA sentences start with the two character GS talker ID. All sentence headers follow the format An NMEA sentence consists of the following components:

1. A start delimiter of '$' 2. A sentence header, or tag 3. A sequence of comma-separated fields 4. The character '*' (ASCII 42) 5. A checksum 6. An end-of-line marker of <CR><LF>

Checksum​

Each NEMA message must contain a checksum as the final field. A sentence’s checksum is the 8-bit XOR of the sentence characters, excluding the "$", "I", or "*" characters; but including all "," and "^" characters. It is encoded as two hexadecimal characters (0-9, A-F), the most-significant-nibble being sent first. Sentences are terminated by a <CR><LF>

Some examples: $GSSET,2,101,2,4,1,1*52 $GSGET,2,101,2,6*44

Full List of Iridium PNT Specific NMEA Sentences​

Table 1: Supported NMEA Sentences​

Sentence HeaderSentence NameSentence DescriptionSentence VersionSentence Field Count*Input/OutputAutonomous SentencePriority
GSPPSPPS Info SentenceReport Pulse Per Second Timing Information626OutputXHigh
GSPARParameter Report SentenceReport Rx Parameters2VariableOutputNormal
GSSTAStatistics SentenceReport Burst Statistics315OutputXNormal
GSSYSSystem Status SentenceReport Rx System Status316OutputXNormal
GSRSPResponse SentenceReport Rx Error Codes36OutputNormal
GSREQRequest SentenceIssue Request To Rx2VariableInputNormal
GSSETSet Parameter SentenceProvide Rx Configuration Parameters2VariableInputNormal
GSGETGet Parameter SentenceRequest Rx Configuration Parameter26InputNormal
GSLOGLog/Debug SentenceReport Log/Debug sentence information2VariableOutputXNormal
GSPOSPosition Data SentenceReport Rx Current Position326OutputXNormal
GSSSVSatellites Information SentenceReport limited satellite location and statistic information3VariableOutputXNormal
GSSURSite Survey SentenceSite Survey Information316OutputXNormal
GSVELVelocity Data SentenceReport Rx Current Velocity Data220OutputXNormal
GSSVISpace Vehicle Information Data SentenceReport Satellite Ranging & State Data223OutputXNormal

*Field count includes the sentence checksum and the sentence header.

NMEA Sentence Frequency / Triggers​

All output sentences require a trigger to initiate transmission, some of these are autonomous based on time:

SentenceTriggering Event(s)
GSPPS1Hz, (1Hz, or synchronized to PPS Signal)
GSPARUpon reception of GSGET
GSRSPUpon reception of GSREQ, or GSSET
GSSTA1Hz, (1Hz, or synchronized to PPS Signal)
GSSYS1Hz, (1Hz, or synchronized to PPS Signal)
GSLOGUpon request
GSPOS1Hz, (1Hz, or synchronized to PPS Signal)
GSSSV0.1 Hz
GSSUR[1]0.1 Hz, when sentence is enabled
GSVEL1Hz, (1Hz, or synchronized to PPS Signal)
GSSVIUpdated for each valid burst processed by SDPM

[1] The first GSSUR sentence may take more than 10 seconds after initiating a survey.


NMEA Sentences Detail​

This section contains the field details of the key subset of NMEA sentences provided. If you require detail on sentences not documented here, contact Ground Control.

$GSPPS: PPS Information Sentence​

The PPS Information sentence structure is shown in Table 2. The GSPPS sentence contains a TFOM field, defined in Table 3.

Table 2: PPS Information Sentence Definition​

Field NumberSentence Field NameField DescriptionField FormatExample
1Sentence HeaderSentence Headerstring$GSPPS
2Sentence VersionSentence Version indicatorInt6
3GPS TimeNumber of whole seconds since GPS Epoch corresponding to the significant (rising) edge of the last PPS output pulseInt1362915962
4UTC GPS OffsetDifference between GPS and UTC Time, in seconds. Empty field indicates invalid data.Int18
5Leap SecondsAn indication of whether a leap second is coming, either positive or negativeInt0
6PPS StatusStatus of the PPS output signal. Coded: 0 = INIT, 1 = FREERUN, 2 = HOLDOVER, 3 = TRACKING ACTIVE, 4 = TRACKING LOCKABLECoded2
7PPS SourceSource of the PPS signal. Coded: 0 = NONE, 1 = Iridium PNT, 2 = RESERVED, 3 = RESERVEDCoded1
8PPS Accuracy Estimate (ns)One sigma estimate of PPS accuracy, in ns. _This field dictates the TFOM field value. See Table 3. _double133.3
9TFOMTime Figure of Merit. See Table 3 for value definitions.Variable4
10Forced Hard Correction ComingA forced hard correction, or PPS Slew Slam, is about to occur. Asserted 6 seconds prior to the correction.Int0
11Forced Hard Correction AppliedA forced hard correction, or PPS Slew Slam, has just occurred. Remains asserted for 10 seconds after the correction.Int0
12Iridium PNT PPS StatusStatus of the Iridium PNT PPS Signal. Coded: 0 = INIT, 1 = ACQUIRING, 2 = LOCKABLE, 3 = ACTIVECoded2
13Iridium PNT Burst AgeNumber of seconds since the previous burst. If no previous burst has been received, value is set to "-1"double0.6
14Iridium PNT PPS Difference (ns)Difference between PPS out and Iridium PNT PPS. Positive when PPS out is delayed relative to Iridium PNT PPS.double0.0
15Iridium PNT PPS Accuracy Estimate (ns)Estimation of Iridium PNT PPS accuracy, in nsdouble133.3
16ReservedReserved
17External PPS StatusStatus of the external PPS signal. Coded:
0 = INIT
1 = RESERVED
2 = RESERVED
3 = RESERVED
Coded0
18External PPS Difference (ns)Difference between PPS out and External PPS. Positive when PPS out is delayed relative to External PPS.double-44326586.5
19External PPS Accuracy Estimate (ns)Estimation of External PPS accuracy, in nsdouble
20 to 25ReservedReserved
26ChecksumN/ASee Sentence Construction and Contents*43

Table 3: GSPPS TFOM Field Description​

TFOMPPS Accuracy Estimate Range (µs)
1value ≤ 0.001
20.001 < value ≤ 0.01
30.01 < value ≤ 0.1
40.1 < value ≤ 1
51 < value ≤ 10
610 < value ≤ 100
7100 < value ≤ 1,000
81,000 < value ≤ 10,000
910,000 < value ≤ 100,000
10100,000 < value ≤ 1,000,000
111,000,000 < value ≤ 10,000,000
1210,000,000 < value ≤ 100,000,000
13100,000,000 < value ≤ 1,000,000,000
141,000,000,000 < value ≤ 10,000,000,000
1510,000,000,000 < value

Sentence Example​

$GSPPS,6,1362915962,18,0,2,1,133.3,4,0,0,2,0.6,0.0,133.3,,0, -44326586.5,,,,,,,*43

$GSPAR: Parameter Report Sentence​

The Parameter Report sentence allows Iridium PNT software to report its configuration. The field count varies with the "Argument Number" field. If Argument Number is greater than 1, the sentence must include additional fields equal to Argument Number minus 1. If Argument Number is 1, no additional fields are required.

Table 4: Parameter Sentence Definition​

Field NumberSentence Field NameField DescriptionField FormatExample
1Sentence HeaderSentence Headerstring$GSPAR
2Sentence VersionSentence Version indicatorInt2
3Parameter IDParameter identification number, defined in the Parameter ID Manual [2]Int
4Memory ClassCoded indicator of the memory type the argument will modify. 1 = Volatile (Current), 2 = Non-Volatile (Permanent)Coded
5Unique CountInteger counter that increments by one upon reception of a GSGET sentenceInt
6Argument NumberThe number of arguments that describe the parameter, 1 to NInt
7Argument 1Argument 1, from 1 to N, where N = "Argument Number" valuestring
...............
7+NArgument NFinal argument N, where N = "Argument Number" valuestring
8+NChecksumN/ASee Sentence Construction and Contents*xx

$GSSTA: Statistics Sentence​

The statistics sentence reports the prior minute's burst detection, measurement, and processing statistics. It reports key parameters that indicate the RF performance of the receiver.

Table 5: Burst Statistics Sentence Definition​

Field NumberSentence Field NameField DescriptionField FormatExample
1Sentence HeaderSentence Headerstring$GSSTA
2Sentence VersionSentence Version indicatorInt3
3 to 6ReservedReserved
7Processed Burst CountNumber of processed burstsInt29133
8Prior Minute Processed Burst CountNumber of processed bursts within the last 60 secondsInt53
9Prior Minute Average Burst CN0Average Carrier to Noise Density Ratio of all processed bursts received in the last 60 secondsdouble60.0
10Prior Minute Maximum Burst CN0Maximum Carrier to Noise Density Ratio of all processed bursts received in the last 60 secondsdouble70.0
11Prior Minute Minimum Burst CN0Minimum Carrier to Noise Density Ratio of all processed bursts received in the last 60 secondsdouble50.0
12 to 14ReservedReserved
15ChecksumN/ASee Sentence Construction and Contents*4A

Sentence Example​

$GSSTA,3,,,,,29133,53,60.0,70.0,50.0,,,*4A

$GSSYS: System Status Sentence​

The system status sentence reports key parameters and error codes that indicate the general health of the receiver. A bit value of 1 indicates the state is true.

Table 6: System Status Sentence Definition​

Field NumberSentence Field NameField DescriptionField FormatExample
1Sentence HeaderSentence Headerstring$GSSYS
2Sentence VersionSentence Version indicatorInt3
3System Up TimeNumber of seconds since system bootInt18194
4Main App Up TimeNumber of seconds since the main application startedInt18169
5Error†Error condition detected by the receiver, coded as a bit field. See the list below.Int0
6Subscription Configured†Bitfield of configured features. See the list below.Int0x003
7Subscription Enabled†Bitfield of enabled features, when the receiver knows time and can determine a configured feature can be enabled. See the list below.Int0x003
8Subscription Start DateStart timestamp of subscription, in seconds since the GPS EpochInt1356566417
9Subscription End DateEnd timestamp of subscription, in seconds since the GPS EpochInt1390780817
10Upgrade StatusUpgrade Status Indicator, _for future use _
11Extended Status†Coded bit field of extended status errors and conditions. See Table 7. Error descriptions defined in [3].Int0
12Receiver Application Software VersionVersion of the receiver application softwarestring1.1
13 to 15ReservedReserved
16ChecksumN/ASee Sentence Construction and Contents*6A

Error (Field 5) bit definitions:

  • Bit [0]: Missing Serial Number [1]
  • Bit [1]: Missing Subscription [2]
  • Bit [2]: Missing Model Number (value not set in NVM)
  • Bit [3]: Missing Manufacturer (value not set in NVM)
  • Bit [4]: Missing Subscription Key (value not set in NVM)
  • Bit [5]: Invalid BTFC. Receiver has not yet resolved BTFC.
  • Bit [6]: Operational Data Limits Exceeded. Enabled during receiver initialization, and remains enabled until receiver convergence and while the receiver is not in violation of operational limits.

Subscription Configured (Field 6) and Subscription Enabled (Field 7) bit definitions:

  • Bit [0]: Location
  • Bit [1]: Timing
  • Bit [2]: Reserved
  • Bit [3]: Reserved
  • Bit [4]: Dynamic
  • Bit [5]: Raw Measurement

Table 7: Extended Status Bit-field Definition​

Bit #Bit NameBit Description
0 to 21Reserved

Sentence Example​

$GSSYS,3,18194,18169,0,0x003,0x003,1356566417,1390780817, ,0,1.1,,,*6A

$GSRSP: Response Sentence​

The response sentence reports the result of the previous GSREQ, GSGET, or GSSET sentence sent to the receiver.

Table 8: Response Sentence Definition​

Field NumberSentence Field NameField DescriptionField FormatExample
1Sentence HeaderSentence Headerstring$GSRSP
2Sentence VersionSentence Version indicatorInt3
3Unique CountCounter provided in the initial Request, Set, or Get Parameter sentenceInt
4Result0 = NACK (Not Acknowledged), 1 = ACK (Acknowledged)Int
5Error CodeError code returned when result is NACK. See Table 9.Int
6ChecksumN/ASee Sentence Construction and Contents*xx

Table 9: Error Code Definition​

Error CodeError Description
1RESERVED
0NONE
-1INVALID_ARG_NB
-2UNSUPPORTED_PARAM_ID
-3UNSUPPORTED_MEMORY_CLASS
-4RESERVED
-5UNSUPPORTED_REQUEST_ID
-6PARAMETER_VALUE_TOO_LONG
-7PARAMETER_IS_UNSET
-8INVALID_ARG
-9CANNOT_CHANGE_OTP_PARAMETER
-10INVALID_OPERATION
-11UNSUPPORTED_SENTENCE_VERSION

$GSREQ: Request Sentence​

The request sentence provides coded commands to the receiver (e.g. Reset). The field count varies with the "Argument Number" field. If Argument Number is greater than 1, the sentence must include additional fields equal to Argument Number minus 1. If Argument Number is 1, no additional fields are required.

Table 10: Request Sentence Definition​

Field NumberSentence Field NameField DescriptionField FormatExample
1Sentence HeaderSentence Headerstring$GSREQ
2Sentence VersionSentence Version indicatorInt2
3Request IDRequest ID. See Table 11.
4Unique CountCounter used to identify the corresponding request when a Response sentence is returnedInt
5Argument NumberArgument number associated with the command, n out of NInt
6Argument 1The first parameter associated with the commandstring
...............
6+NArgument NFinal argument N, where N = "Argument Number" valuestring
7+NChecksumN/ASee Sentence Construction and Contents*xx

Table 11: Request Command Definitions​

Request IDCommand DescriptionOptional Argument Description
1ResetArgument 1: 1 = Reserved, 2 = Reserved, 3 = Reserved, 4 = System reboot
2RESERVED
3RESERVED
4RESERVED
5Clear a non-volatile parameterArgument 1: Parameter ID. Defined in the Parameter ID Manual [2].
6Clear All Non-OTP Non-Volatile Memory ParametersN/A

$GSSET: Set Parameter Sentence​

The set parameter sentence allows the user to change the receiver configuration. The field count varies with the "Argument Number" field, following the same rules as GSREQ.

Table 12: Set Parameter Sentence Definition​

Field NumberSentence Field NameField DescriptionField FormatExample
1Sentence HeaderSentence Headerstring$GSSET
2Sentence VersionSentence Version indicatorInt2
3Parameter IDParameter identification number, defined in the Parameter ID Manual [2]Int
4Memory ClassCoded indicator of the memory type the argument will modify. 1 = Volatile (Current), 2 = Non-Volatile (Permanent)Coded
5Unique CountCounter used to identify the corresponding request when a Response sentence is returnedInt
6Argument NumberArgument number associated with the command, n out of NInt
7Argument 1The first parameter associated with the commandstring
...............
7+NArgument NFinal argument N, where N = "Argument Number" valuestring
8+NChecksumN/ASee Sentence Construction and Contents*xx

$GSGET: Get Parameter Sentence​

The get parameter sentence allows the user to poll the receiver configuration.

Table 13: Get Parameter Sentence Definition​

Field NumberSentence Field NameField DescriptionField FormatExample
1Sentence HeaderSentence Headerstring$GSGET
2Sentence VersionSentence Version indicatorInt2
3Parameter IDParameter identification number, defined in the Parameter ID Manual [2]Int
4Memory ClassCoded indicator of the memory type. 1 = Volatile (Current), 2 = Non-Volatile (Permanent)Coded
5Unique CountCounter used to identify the corresponding request when a Response sentence is returnedInt
6ChecksumN/ASee Sentence Construction and Contents*xx

$GSLOG: Log/Debug Sentence​

The log/debug sentence contains an ASCII character array for logging and debugging. It is a free-form, length-limited string.

Table 14: Log Sentence Definition​

Field NumberSentence Field NameField DescriptionField FormatExample
1Sentence HeaderSentence Headerstring$GSLOG
2Sentence VersionSentence Version indicatorInt3
3Total Number of GSLOG SentencesSentences packaged in groupInt2
4Sentence NumberSentence Number within the groupInt1, 2
5SentenceASCII character arraystringVariable
6Log Level Identifier**Coded: 0 = ALWAYS, 1 = FATAL, 2 = ERROR, 3 = WARN, 4 = INFO, 5 = DEBUG, 6 = TRACECoded3
7 to 9ReservedReserved
10ChecksumN/ASee Sentence Construction and Contents*xx

** Value must be the same for all sentences within a transmission group. Default setting is 3 (WARN).


$GSPOS: Position Data Sentence​

The GSPOS sentence contains Iridium PNT position data output via the Signal Data Processing Module (SDPM).

‡ Altitude is relative to the WGS84 ellipsoid model. See Operational Limits Data Note for more information.

Table 15: Position Data Sentence Definition​

Field NumberSentence Field NameField DescriptionField FormatExample
1Sentence HeaderCustom Iridium PNT Headerstring$GSPOS
2Sentence VersionSentence Version indicatorInt3
3Current TimeCurrent time, formatted according to the Time Format fieldPer Time Format1324335956.0
4Time FormatFormat of Current Time. Coded: 0 = GPS TimeCoded0
5LatitudeLatitude, decimal degree notationdouble40.1516018
6LongitudeLongitude, decimal degree notationdouble-105.116483
7Altitude‡Altitude, in metersdouble1523.37
8X PositionECEF X position, in metersdouble-1273340.09
9Y PositionECEF Y position, in metersdouble-4714088.78
10Z PositionECEF Z position, in metersdouble4091848.56
11East Position VarianceEast position estimate variance, in meters squareddouble132.724
12North Position VarianceNorth position estimate variance, in meters squareddouble70.551
13Up Position VarianceUp position estimate variance, in meters squareddouble686.893
14East-North Position CovarianceEast-North position covariance estimate, in meters squareddouble-31.190
15East-Up Position CovarianceEast-Up position covariance estimate, in meters squareddouble118.094
16North-Up Position CovarianceNorth-Up position covariance estimate, in meters squareddouble-31.190
17Burst Age of DataAge of position, in seconds, since the previous Iridium PNT burstdouble0
18ReservedReserved
19Kalman Filter Update Age of DataAge of position, in seconds, since the previous Kalman Filter updatedouble1
20ReservedReserved
21PFOMPosition Figure of Merit. See Table 16.Variable
22Receiver Position ModeCoded: 0 = Static Known Position**, 1 = Static Unknown Position**, 2 = Reserved, 3 = Dynamic, 4 = ReservedCoded0
23 to 25ReservedReserved
26ChecksumN/ASee Sentence Construction and Contents*72

** "Static known" mode refers to a surveyed position hold. "Static unknown" mode refers to a guessed position.

Table 16: PFOM Field Definition​

PFOMRMS Estimated Position Error (m)
1value < 25
225 ≤ value < 50
350 ≤ value < 75
475 ≤ value < 100
5100 ≤ value < 200
6200 ≤ value < 500
7500 ≤ value < 1000
81000 ≤ value < 5000
95000 ≤ value

Sentence Example​

$GSPOS,3,1324335956.0,0,40.1516018,-105.1156483,1523.37,-1273340.09, -4714088.78,4091848.56,132.724,70.551,686.893,-31.190,118.094,-31.190,0,,1,,,0,,,*72

$GSSSV: Satellites Information Sentence​

The GSSSV sentence contains satellite information output via the Signal Data Processing Module (SDPM). Sentences are typically packaged in a group of 2 or 3. The "Total Number of Sentences to be Transmitted" and "Total Number of Satellites" fields dictate the size of the package. If the sentence count is greater than 1, the "Total Number of Sentences", "Sentence Number", and "Total Number of Satellites" fields repeat at the start of each sentence. The Satellite ID, Elevation, Azimuth, and CN0 fields are output only once per satellite within the package.

See Operational Limits Data Note for more information.

Table 17: Satellite Information Sentence Definition​

Field NumberSentence Field NameField DescriptionField FormatExample
1Sentence HeaderASCII (Delimiter + Talker ID + Type Code)string$GSSSV
2Sentence VersionSentence Version indicatorInt3
3Total Number of GSSSV SentencesSentences packaged in groupInt4
4Sentence NumberSentence Number within the current groupInt1 to 4
5Total Number of SatellitesNumber of satellites within field of view, with leading zerosInt4
6Satellite IDSatellite Identification NumberIntMultiple values
7ElevationElevation angle in degreesInt [0, 90]30
8AzimuthAzimuth angle in degreesInt [0, 359]278
9Minimum CN0Minimum Carrier to Noise Density Ratio, in dB-Hzdouble40.0
10Maximum CN0Maximum Carrier to Noise Density Ratio, in dB-Hzdouble76.7
11 to 13ReservedReserved
14ChecksumN/ASee Sentence Construction and Contents*7B

Sentence Examples​

$GSSSV,3,4,1,4,30,16,278,40.0,76.7,,,*7B
$GSSSV,3,4,2,4,40,10,27,37.8,77.8,,,*47
$GSSSV,3,4,3,4,29,,,39.9,70.9,,,*44
$GSSSV,3,4,4,4,41,9,148,40.8,73.8,,,*44

$GSSUR: Site Survey Sentence​

The GSSUR sentence content is reserved for future use.


$GSVEL: Velocity Data Sentence​

The GSVEL sentence contains Iridium PNT velocity data output via the Signal Data Processing Module (SDPM).

◊ See GPS Timestamp Format for more information. See Operational Limits Data Note for more information.

Table 18: Velocity Data Sentence Definition​

Field NumberSentence Field NameField DescriptionField FormatExample
1Sentence HeaderCustom Sentence HeaderASCII$GSVEL
2Sentence VersionSentence Version indicatorInt2
3GPS Time◊Timestamp of message containing whole and fractional seconds since GPS Epochdouble83560.10000000
4East VelocityVelocity EE, in meters per seconddouble0.1
5North VelocityVelocity NN, in meters per seconddouble0.2
6Up VelocityVelocity UU, in meters per seconddouble0.3
7East Velocity VarianceEast velocity estimate variance, in m²/s²double0.0
8North Velocity VarianceNorth velocity estimate variance, in m²/s²double0.0
9Up Velocity VarianceUp velocity estimate variance, in m²/s²double0.0
10East North Velocity CovarianceEast-North velocity estimate covariance, in m²/s²double0.0
11East Up Velocity CovarianceEast-Up velocity estimate covariance, in m²/s²double0.0
12North Up Velocity CovarianceNorth-Up velocity estimate covariance, in m²/s²double0.0
13Burst Update Age of DataAge of data, in seconds, since the previous Iridium burstdouble0
14Sensor Measurement Update Age ofAge of data, in seconds, since the previous sensor updatedouble0
15Kalman Filter Update Age of DataAge of data, in seconds, since the previous Kalman Filter updatedouble1
16PVT Validation StateValidation state of the Kalman Filter. Coded: 0 = Not Available, 1 = Initializing, 2 = Pending, 3 = Usable, 4 = Reserved, 5 = ReservedCoded3
17 to 19ReservedReserved
20ChecksumN/ASee Sentence Construction and Contents*46

Sentence Example​

$GSVEL,2,83560.10000000,0.1,0.2,0.3,0.0,0.0,0.0,0.0,0.0,0.0,0,0,1, ,,,*46

$GSSVI: Space Vehicle Information Data Sentence​

The GSSVI sentence contains satellite vehicle information output via the Signal Data Processing Module (SDPM).

◊ See GPS Timestamp Format for more information. See Operational Limits Data Note for more information.

Table 19: Space Vehicle Information Sentence Definition​

Field NumberSentence Field NameField DescriptionField FormatExample
1Sentence HeaderCustom Sentence HeaderASCII$GSSVI
2Sentence VersionSentence Version indicatorInt1
3SV IDSpace Vehicle ID. Any value NOT inclusively between 1 and 66 indicates the ASIC firmware could not confidently detect the SVID. Negative SV IDs are provided for logging and visibility only and are not used to generate a Navigation Solution.Int1
4Time Of Validity◊Timestamp of message containing whole and fractional seconds since GPS Epochdouble1324771537.08116000
5Time Of Arrival◊Timestamp of the underlying burst in receiver time (time since receiver initialization). Formatted according to GPS Timestamp Format.double1830.96981100
6Burst CounterA monotonically increasing counter used to uniquely identify received burstsint10
7PseudorangePseudorange estimate from the satellite to the receiver, in metersdouble
8Pseudorange RatePseudorange rate estimate from the satellite to the receiver, in meters per seconddouble
9CN0Carrier to Noise Density Ratio, in dB-Hzdouble58.2
10DopplerDoppler, in Hzdouble2611.354248
11SV X PositionX coordinate ECEF position, in metersdouble-1766791.0
12SV Y PositionY coordinate ECEF position, in metersdouble-5132087.0
13SV Z PositionZ coordinate ECEF position, in metersdouble4656373.6
14SV X VelocityX coordinate ECEF velocity, in meters per seconddouble1790.4
15SV Y VelocityY coordinate ECEF velocity, in meters per seconddouble4516.3
16SV Z VelocityZ coordinate ECEF velocity, in meters per seconddouble5641.2
17SV Validation StatusSpace Vehicle Validation State. Coded: 0 = Not Available, 1 = Initializing, 2 = Pending, 3 = Usable, 4 = Reserved, 5 = ReservedCoded3
18 to 20ReservedReserved
21ChecksumN/ASee Sentence Construction and Contents*45

Sentence Example​

$GSSVI,1,1,1324771537.08116000,1830.96981100,10,,,58.2,2611.354248,-1766791.0,-5132087.0,4656373.6,1790.4,4516.3,5641.2, ,,,*45