Rtcm Received Data - Holux GR-271 User Manual

Cf gps receiver
Hide thumbs Also See for GR-271:
Table of Contents

Advertisement

$GPGSV,2,1,07,07,79,048,42,02,51,062,43,26,36,256,42,27,27,138,42*71
$GPGSV,2,2,07,09,23,313,42,04,19,159,41,15,12,041,42*41
Name
Message ID
Number of Messages
Message Number
Satellites in View
Satellite ID
Elevation
Azimuth
SNR (C/No)
....
Satellite ID
Elevation
Azimuth
SNR (C/No)
Checksum
<CR> <LF>
NOTE: Items <4>,<5>,<6> and <7> repeat for each satellite in view to a maximum of four (4) satellites per sentence.
Additional satellites in view information must be sent in subsequent sentences. These fields will be null if unused.
2.2.1.4 Recommended Minimum Specific GNSS Data (RMC)
Table 2-8 contains the values for the following example:
$GPRMC,161229.487,A,3723.2475,N,12158.3416,W,0.13,309.62,120598, ,*10
Name
Message ID
UTC Time
Status
Latitude
N/S Indicator
Longitude
E/W Indicator
Speed Over Ground
Course Over Ground
Date
Magnetic Variation1
Checksum
<CR> <LF>
1.SiRF Technology Inc. does not support magnetic declination. All "course over ground" data are geodetic
WGS84 directions.

2.2.2 RTCM Received Data

The default communication parameters for DGPS Input are 9600 baud, 8 data bits, stop bit, and no parity. Position
accuracy of less than 5 meters can be achieved with the GR-271 by using Differential GPS (DGPS) real-time pseudo-range
correction data in RTCM SC-104 format, with message types 1,2, or 9. As using DGPS receiver with different
Table 2-7 GSV Data Format
Example
Units
$GPGSV
2
1
07
07
79
degrees
048
degrees
42
dBHz
....
27
27
degrees
138
degrees
42
dBHz
*71
Table 2-8 RMC Data Format
Example
Units
$GPRMC
161229.487
A
3723.2475
N
12158.3416
W
0.13
knots
309.62
degrees
120598
degrees
*10
Description
GSV protocol header
Range 1 to 3
Range 1 to 3
Channel 1 (Range 1 to 32)
Channel 1 (Maximum 90)
Channel 1 (True, Range 0 to 359)
Range 0 to 99, null when not tracking
Channel 4 (Range 1 to 32)
Channel 4 (Maximum 90)
Channel 4 (True, Range 0 to 359)
Range 0 to 99, null when not tracking
End of message termination
Description
RMC protocol header
hhmmss.sss
A=data valid or V=data not valid
ddmm.mmmm
N=north or S=south
dddmm.mmmm
E=east or W=west
True
ddmmyy
E=east or W=west
End of message termination
7

Advertisement

Table of Contents
loading

Table of Contents