A7672 Gps Unicore
A7672 Gps Unicore
PROTOCOL
WWW.UNICORECOMM.COM
Standard Positioning
Products
Revision History
Version Revision History Date
Ver. 1.0.0
Initial release revision Jul, 2017
Primary
Ver.2.0.0
Perfect the NMEA protocol Aug, 2017
Alpha release
Ver.3.2.1 Beta
Mass production release Dec, 2017
release
i
Add CFGDYN, and revise the parameter description of
CFGMOD
R4.4 Update the field description of ANTSTAT1/ 2021-06-24
CFGLOWPOWER
Update NAVTIME
All rights, title and interest to this document and the information such as data, designs,
layouts contained in this manual are fully reserved, including but not limited to the
copyrights, patents, trademarks and other proprietary rights as relevant governing laws
may grant, and such rights may evolve and be approved, registered or granted from the
whole information aforesaid or any part(s) of it or any combination of those parts.
Unicore holds the trademarks of “和芯星通”, “UNICORECOMM” and other trade name,
trademark, icon, logo, brand name and/or service mark of Unicore products or their
product serial referred to in this manual (collectively “Unicore Trademarks”).
This manual or any part of it, shall not be deemed as, either expressly, implied, by
estoppel or any other form, the granting or transferring of Unicore rights and/or
ii
Standard Positioning Products Protocol Specification
interests (including but not limited to the aforementioned trademark rights), in whole or
in part.
Disclaimer
The information contained in this manual is provided “as is” and is believed to be true
and correct at the time of its publication or revision. This manual does not represent,
and in any case, shall not be construed as a commitments or warranty on the part of
Unicore with respect to the fitness for a particular purpose/use, the accuracy, reliability
and correctness of the information contained herein.
Information, such as product specifications, descriptions, features and user guide in this
manual, are subject to change by Unicore at any time without prior notice, which may
not be completely consistent with such information of the specific product you
purchase.
Should you purchase our product and encounter any inconsistency, please contact us or
our local authorized distributor for the most up-to-date version of this manual along with
any addenda or corrigenda.
iii
Contents
1 General Protocol..................................................................................... 1
1.1 Messages ......................................................................................................... 1
1.2 Checksum ......................................................................................................... 2
1.3 Formats ............................................................................................................ 2
1.4 Coordinates ...................................................................................................... 3
1.5 Message Definition ........................................................................................... 3
1.5.1 Common Message ................................................................................................... 3
1.5.1.1 PDTINFO ...................................................................................................3
1.5.1.2 RESET ........................................................................................................4
1.5.1.3 Command Echo(1) .....................................................................................5
1.5.1.4 OK ..............................................................................................................6
1.5.1.5 FAIL ...........................................................................................................6
1.5.2 Config Message ....................................................................................................... 7
1.5.2.1 CFGPRT .....................................................................................................7
1.5.2.2 CFGMSG ....................................................................................................8
1.5.2.3 CFGTP .................................................................................................... 11
1.5.2.4 CFGNMEA .............................................................................................. 13
1.5.2.5 CFGSYS .................................................................................................. 13
1.5.2.6 CFGDYN ................................................................................................. 14
1.5.2.7 CFGGEOID .............................................................................................. 16
1.5.2.8 CFGSAVE ................................................................................................ 16
1.5.2.9 CFGCLR .................................................................................................. 17
1.5.2.10 CFGCWOUT .......................................................................................... 17
1.5.2.11 AIDTIME ............................................................................................... 18
1.5.2.12 AIDPOS................................................................................................. 19
1.5.2.13 AIDINFO ............................................................................................... 19
1.5.2.14 CFGMOD .............................................................................................. 21
1.5.2.15 CFGNAV ............................................................................................... 22
1.5.3 NMEA Message ...................................................................................................... 23
1.5.3.1 NmeaVer h51 ......................................................................................... 23
1.5.3.2 NmeaVer h30 ......................................................................................... 36
1.5.4 Navigation Result Message .................................................................................. 48
1.5.4.1 NAVPOS ................................................................................................. 48
1.5.4.2 NAVVEL .................................................................................................. 49
1.5.4.3 NAVTIME ................................................................................................ 50
1.5.4.4 NAVACC.................................................................................................. 51
I
Standard Positioning Products Protocol Specification
II
1 General Protocol
1.1 Messages
In the Unicore protocol, input and output statements are collectively called messages.
Each message is a string of full ASCII characters.
$MSGNAME,data1,data2,data3,…[*CC]\r\n
The first data block is the message header, which starts with ‘$’ (0x24).
The second data block is the data field consisting of a number of parameters or data. The
message header and data field are separated by ‘,’ (0x2C).
The last data block is an optional checksum, which is separated from the previous data
with ‘*'(0x2A).
The input message ends with ‘\r' (0x0D) or ‘\n' (0x0A) or any combination of the two.
The output message ends with ‘\r\n'. The total length of each message does not exceed
128 bytes.
Message header and parameters, as well as letters in checksums are not case-sensitive.
Certain parameters of certain input commands can be omitted (marked as optional in the
command description). These parameters can be empty, that is, there is no character
between the two commas.
Then, if there is no special instruction, this parameter will be ignored and the options it
controls will remain unchanged.
Most of the message headers can be used for both input commands and output
messages. The same message header is used as input to set parameters or to query the
current configuration, and as output to output receiver information or configuration.
1
Standard Positioning Products Protocol Specification
1.2 Checksum
The two characters after ‘*'(0x2A) in the message are the checksum, which is calculated
as the xor of all characters (excluding ‘$' and ‘*') from ‘$' to ‘*', in hexadecimal (calculate
the checksum according to the uppercase letters corresponding to the input
information).
The checksum in the input command is optional. If the input statement contains ‘*'
followed by the two characters, the checksum is examined. If the examination result is
wrong, the command is not executed, and the receiver outputs the $fail message, in
which a checksum error is indicated. If the statement does not contain a checksum, the
command is executed directly.
If the parameters of the input message are empty and a checksum needs to be added, it
should be followed by ‘,'. It's not allowed to add an extra ‘,' when the parameter is not
null.
Example: $PDTINFO,*62
The output message always contains a checksum. The description of the checksum in
the Unicore protocol will be omitted in the following message definition.
1.3 Formats
In the Unicore protocol, the data in the message contains the following types:
String (STR)
The string consists of up to 32 ASCII characters except ‘\ r' and ‘\ n', such as GPSL1.
Unsigned Integer(UINT)
Unsigned integers range from 0 to 4294967295, and are defined in both decimal and
hexadecimal. A decimal unsigned integer consists of ASCII characters from 0 to 9. Such
as 123, 4291075193. A hexadecimal unsigned integer starts with the character h or H,
followed by a string of 0 to 9 and a-f (or A-F), with a maximum of 8 characters
(excluding the starting h or H). Such as hE10, hE41BA7C0.
Unsigned long integers range from 0~18446744073709551615, and are defined in both
decimal and hexadecimal. A decimal unsigned long integer consists of ASCII characters
from 0 to 9. Such as 123 and 4291075193. A hexadecimal unsigned long integer starts
2
with h, or H, or 0x, or 0X, followed by a string of characters from 0 to 9 and a-f (or A-F),
with a maximum of 16 characters (excluding the starting h, H, 0x, or 0X). Such as hE10
and hE41BA7C0, or 0xFFFFFF and 0XFFFFF.
Signed integers are composed of ASCII characters from 0 to 9 and a negative sign, with
a range of-2147483648 to 2147483647. Such as 123217754, -245278.
DOUBLE
1.4 Coordinates
The position value observed by the product is based on the WGS84 coordinate system.
If the position value of the output message is based on other coordinate system, it will
be noted in the message explanation of this documentation. If the user expects to use a
different reference coordinate, the position is very likely to be off by tens or even
hundreds of meters.
1.5.1.1 PDTINFO
Syntax $PDTINFO
Example $PDTINFO
Input/Output Input
No parameters
3
Standard Positioning Products Protocol Specification
Syntax $PDTINFO,pdtName,config,hwVer,fwVer,PN,SN
$PDTINFO,UM220,G1B1,V4.1,R3.0Build13260,080101000001,000101114
Example
303845
Input/Output Output
Parameter Definition
1.5.1.2 RESET
Syntax $RESET,type,clrMask
Input/Output Input
Parameter Definition
Reset type
2 - Board-level reset
4
3 - Receiver stopped
bit1 – Reserve0
bit3 – Reserve1
The parameter of the cold start reset command is hff, and the mismatch of the reset
parameters will cause the receiver to start in an incorrect state
When a leap second occurs, the receiver may take up to 25 minutes to sync to UTC time
after a cold start reset.
Example #CFGPRT,1,h0,115200,3,35
Input/Output Output
5
Standard Positioning Products Protocol Specification
No parameters
(1): This command is only supported by the firmware of R3.2.10.0, R3.2.20.0, R3.4.0.0 and
above.
1.5.1.4 OK
Syntax $OK
Example $OK
Input/Output Output
No parameters
1.5.1.5 FAIL
Syntax $FAIL,errorCode
Example $FAIL,0
Input/Output Output
Parameter Definition
Error code
1 –Checksum error
6
1.5.2 Config Message
1.5.2.1 CFGPRT
Syntax $CFGPRT,portID
Example $CFGPRT,1
Input/Output Input
Parameter Definition
Syntax $CFGPRT,portID,addr,baud,inProto,outProto
Example $CFGPRT,1,h0,115200,1,3
Input/Output Input/output
Parameter Definition
Port number:
UINT 1 – UART1
portID
(optional) 2 – UART2
addr UINT H0
7
Standard Positioning Products Protocol Specification
(optional) 9600/115200/230400/460800(1)
bit0 – UNICORE(2)
UINT
inProto bit5 - Reserve
(optional)
bit7 - RTCM3.2
bit9 - Reserve
bit10 - Reserve
(1) The baud rate of 460800 is only supported by specific versions of firmware.
(2) COM1 cannot disable the Unicore input protocol.
(3) Only supported by firmware R3.2.10.0, R3.2.20.0, R3.4.0.0 and above.
1.5.2.2 CFGMSG
Syntax $CFGMSG,msgClass,msgID
Example $CFGMSG,0,1
8
Input/Output input
Parameter Definition
Syntax $CFGMSG,msgClass,msgID,rate
Example $CFGMSG,0,1,1
Input/Output Input/output
Parameter Definition
UINT
msgID Message ID
(optional)
0 0 0: disable
GGA
1: enable
0 1 0: disable
GLL
1: enable
0 2 0: disable
GSA
1: enable
0 3 0: disable
GSV
1: enable
9
Standard Positioning Products Protocol Specification
0 4 0: disable
RMC
1: enable
0 5 0: disable
VTG
1: enable
0 6 0: disable
ZDA
1: enable
0 7 0: disable
GST
1: enable
1 0 0: disable
NAVPOS
1: enable
1 1 0: disable
NAVVEL
1: enable
1 2 0: disable
NAVTIME
1: enable
1 3 0: disable
NAVACC
1: enable
3 0 0: disable
LSF
1: enable
3 1 0: disable
ANTSTAT
1: enable
3 3 0: disable
ANTSTAT1
1: enable
5 1 0: disable
OSNMA(1)
1: enable
6 0 0: disable
NOTICE(2)
1: enable
6 4 0: disable
ABNORMAL(3)
5: enable
6 2 0: disable
EPHABNORMAL(4)
10: enable
10
(1): Only supported by customized firmware.
1.5.2.3 CFGTP
Syntax $CFGTP
Example $CFGTP
Read the current timing pulse configuration. The receiver outputs a CFGTP
Description
message after receiving this command.
Input/Output Input
No parameters
Syntax $CFGTP,interval,length,flag,antDelay,rfDelay,usrDelay
Example $CFGTP,1000000,500000,1,0,800,0
Input/Output Input/output
Parameter Definition
UINT
interval Timing pulse frequency, unit: μs; set to 1000000 by default
(optional)
UINT more than interval – 1 μs. (High-level width when the rising
length edge is aligned with the integral timing pulse frequency ,
(optional) and low-level width when the falling edge is aligned with
the integral timing pulse frequency )
11
Standard Positioning Products Protocol Specification
bit0
bit1
bit3
0 –Disable TIMTP
1 – Enable TIMTP
INT
antDelay Antenna delay, unit: ns; (-32768 ~ 32767)
(optional)
INT
rfDelay RF unit delay, unit: ns; (-32768~32767)
(optional)
12
1.5.2.4 CFGNMEA
Syntax $CFGNMEA
Example $CFGNMEA
Input/Output Input
No parameters
Syntax $CFGNMEA,nmeaVer
Example $CFGNMEA,h30
Input/Output Input/output
Parameter Definition
1.5.2.5 CFGSYS
Syntax $CFGSYS
Example $CFGSYS
Description Read the current satellite system configuration. The receiver outputs a
13
Standard Positioning Products Protocol Specification
Input/Output Input
No parameters
Syntax $CFGSYS,sysMask
Example $CFGSYS,H11
Description The receiver automatically reset while receiving the command, the
configuration of enabling the satellite system works after the reset.
Input/Output Input/output
Parameter Definition
H10 – BDS B1
(1): Firmware below R3.4.0.0 only supports GPS L1++QZSS joint positioning, R3.4.0.0 and
above support GPS L1 + SBAS + QZSS joint positioning
(2): Only supported by the firmware with the version of R3.4.0.0 and above
(3): Firmware below R3.4.0.0 only supports GPS L1+BDS B1+QZSS, R3.4.0 and above
support GPS+BDS+GALILEO+SBAS+QZSS joint positioning.
1.5.2.6 CFGDYN
Syntax $CFGDYN
Example $CFGDYN
14
Read the current dynamic configuration. The receiver outputs a
Description
CFGDYN message after receiving this command.
Input/Output Input
No parameters
Syntax $CFGDYN,mask,dynModel,staticHoldThresh
Example $CFGDYN,h01,0,1000
Input/Output Input/output
Parameter Definition
bit1 - staticHoldThresh
Dynamic model
0 – Portable
dynModel UINT
1 – Static
15
Standard Positioning Products Protocol Specification
1.5.2.7 CFGGEOID
Syntax $CFGGEOID
Example $CFGGEOID
Input/Output Input
No parameters
Syntax $CFGGEOID,Model
Example $CFGGEOID,0
Input/Output Input/output
Parameter Definition
1.5.2.8 CFGSAVE
Syntax $CFGSAVE
Example $CFGSAVE
Description Save the current receiver configuration, which is stored in NOR Flash
Input/Output Input
No parameters
Do NOT cut off the power within one second after inputting $cfgsave. Power off will
16
damage the configuration of the receiver, and the receiver will be restored to factory
settings.
1.5.2.9 CFGCLR
Syntax $CFGCLR
Example $CFGCLR
Input/Output Input
No parameters
The configuration modified by this command takes effect after resetting the receiver.
For R3.4.0.0, R3.4.20.0 and R3.4.21.0 versions, the configuration will not be cleared after
sending this command.
1.5.2.10 CFGCWOUT
Syntax $CFGCWOUT
Example $CFGCWOUT
Input/Output Input
No parameters
Syntax $CFGCWOUT,CWOutCtrl
Example $CFGCWOUT,1
17
Standard Positioning Products Protocol Specification
Input/Output Input/output
Parameter Definition
1.5.2.11 AIDTIME
Syntax $AIDTIME,year,month,day,hour,minute,second,millisecond
Example $AIDTIME,2018,4,9,17,41,36,200
Input/Output Input
Parameter Definition
The input information should be in accordance with the current time. Wrong input will
cause the function to fail.
18
1.5.2.12 AIDPOS
Syntax $AIDPOS,Latitude,N,Longitude,E,altitude
Example $AIDPOS,4002.229934,N,11618.096855,E,37.254
Input/Output Input
Parameter Definition
mm.mmmmmm - Minute
S - South latitude
mm.mmmmmm - Minute
W - West longitude
1.5.2.13 AIDINFO
Syntax $AIDINFO
Example $AIDINFO
19
Standard Positioning Products Protocol Specification
Input/Output Input
No parameters
Syntax $AIDINFO,GPSRS,GPSUS,BDSRS,BDSUS,GALRS,GALUS,GLORS,GLOUS,AType
Example $AIDINFO,0x0FF7FFFBFF,0x0FF7FFFBFF,,,,,,,0x0311*27
Input/Output Output
Parameter Definition
20
Receiving state of GLO ephemeris, as long as the received data
Bit10-15: reserve
1.5.2.14 CFGMOD
Example $CFGMOD,0
Input/Output Input
Parameter Definition
21
Standard Positioning Products Protocol Specification
Only supported by the firmware with the version of R3.2.10.100 and R3.2.20.100
This mode cannot be used in conjunction with dynamic speed threshold mode (CFGDYN)
1.5.2.15 CFGNAV
Syntax $CFGNAV
Example $CFGNAV
Input/Output Input
No parameters
Syntax $CFGNAV,measRate,navRate,correctionMask
Example $CFGNAV,200,1000,3
Input/Output Input/output
Parameter Definition
22
bit1 –tropospheric correction
The message format described in this section is for the versions shown as below:
The version of Beidou related messages extended on the basis of NMEA 3.0
(nmeaVer in CFGNMEA command is h30)
The version of Beidou related messages extended on the basis of standard NMEA
4.1 ($GBGSA, nmeaVer in CFGNMEA command is h51)
BD3 satellites are involved in NMEA4.1 to support BDS satellites with number of 1~37.
With the increasing of satellites, only output GGA, GSV, GSA and RMC messages by
default to prevent data loss at the rate of 9600. When the amount of data at 9600 baud
rate is allowed, the maximum number of satellites will be output, but it is limited to the
amount of output data at 9600 baud rate. Under the strong sky signal, there will be a
phenomenon of incomplete output of the number of satellites. If the user inputs other
commands, priority is given to ensuring the complete output of the message added by
the user. The number of satellites and satellite information in the GSV message will be
reduced accordingly.
The baud rate of 115200 is supported, which is able to output all satellite information,
and the default output messages include GGA, GSV, GSA and RMC after switching. If
other messages are required, send the command separately.
GGA
Syntax $--GGA,time,Lat,N,Lon,E,FS,NoSV,HDOP,msl,M,Altref,M,DiffAge,DiffStation*cs
Example $GPGGA,060845.00,4004.74005,N,11614.19613,E,1,10,0.85,53.5,M,,M,,*7B
Input/Output Output
23
Standard Positioning Products Protocol Specification
Parameter Definition
hh – Hour
time STR
mm – Minutes
ss.ss – Seconds
mm.mmmmm - Minutes
S - South latitude
mm.mmmmm - Minutes
W - West longitude
24
1-Point positioning
2-Differential positioning
6-Recursive positioning(2)
Reference station ID
DiffStation DOUBLE
Null for non-differential positioning
Checksum
(1): SBAS is only supported by firmware with the version of R3.4.0.0 or above.
GLL
Syntax $--GLL,Lat,N,Lon,E,time,Valid,Mode*cs
Example $GPGLL,4004.74005,N,11614.19613,E,060845.00,A,A*6F
25
Standard Positioning Products Protocol Specification
Input/Output Output
Parameter Definition
mm.mmmmm - Minutes
S – South latitude
mm.mmmmm - Minutes
W – West longitude
hh - Hours
time STR
mm - Minutes
ss.ss - Seconds
26
Position valid indicator
A – Valid
N – Not positioning
Mode STR
A – Point positioning
D – Differential positioning
Checksum
(1): SBAS is only supported by firmware with the version of R3.4.0.0 or above.
GSA
$--
Syntax GSA,Smode,FS,sv1,sv2,sv3,sv4,sv5,sv6,sv7,sv8,sv9,sv10,sv11,sv12,PDOP,H
DOP,VDOP,systemID*cs
Example $GPGSA,A,3,02,03,06,09,12,17,19,23,28,25,,,1.34,0.85,1.04,1*1E
Input/Output Output
Parameter Definition
27
Standard Positioning Products Protocol Specification
Positioning mode
1– Not positioning
FS UINT
2– 2D positioning
3– 3D positioning
Participating satellite ID
GPS satellite ID is 01 ~ 32
1 - GPS system ID
systemID UINT
2 - GLO system ID(5)
28
4 - BDS System ID
Checksum
(1): SBAS is only supported by firmware with the version of R3.4.0.0 or above.
(2) (3) (4) (5) (6): Only supported by firmware with the version of R3.4.0.0 or above.
GSV
$--
Syntax GSV,NoMsg,MsgNo,NoSv,sv1,elv1,az1,cn01,sv2,elv2,az2,cn02,sv3,elv3,az3,
cn03,sv4,elv4,az4,cn04, signalID*cs
$GPGSV,3,01,11,02,34,277,41,03,16,043,35,05,04,215,35,06,69,333,48,0*57
$GPGSV,3,02,11,09,25,110,41,12,31,305,43,17,55,116,46,19,76,088,46,0*56
$GPGSV,3,03,11,23,23,077,40,25,04,328,32,28,05,171,36,0*67
Example
$GBGSV,3,01,12,01,37,145,42,02,34,225,39,03,44,188,42,04,25,123,37,0*4C
$GBGSV,3,02,12,05,17,249,36,06,30,169,38,07,03,188,31,08,69,027,43,0*4E
$GBGSV,3,03,12,09,09,186,34,10,15,211,36,12,26,306,40,13,60,316,44,0*48
Description Each GSV message contains information for only 4 satellites. When the
number of satellites exceeds 4, the receiver sends multiple GSV messages
continuously
Input/Output Output
Parameter Definition
System identification
29
Standard Positioning Products Protocol Specification
Checksum
30
(1) (2) (3) (4) (5): Only supported by firmware with the version of R3.4.0.0 or above.
Due to the excessive number of satellites in GN mode, at 9600 baud rate, GSV will have
the problem of incomplete printing of satellite information. For complete satellite
information, please switch the baud rate to 115200
RMC
Syntax $--RMC,time,status,Lat,N,Lon,E,spd,cog,date,mv,mvE,mode,navStates*cs
Example $GPRMC,060845.00,A,4004.74005,N,11614.19613,E,,,180817,,,A,V*0B
Input/Output Output
Parameter Definition
hh - Hours
time STR
mm - Minutes
ss.ss - Seconds
A – Valid
31
Standard Positioning Products Protocol Specification
dd - Degrees
mm.mmmmm - Minutes
S – South latitude
mm.mmmmm - Minutes
W – West longitude
cog DOUBLE Calculated clockwise from north. If the speed measurement fails
or the static scene speed is extremely small, the output is empty.
dd - Day
date STR
mm - Month
yy - Year
Positioning mode
N – Not positioning
mode STR
A – Point positioning
D – Differential positioning
32
V-Device does not provide navigation state information
Checksum
(1): SBAS is only supported by firmware with the version of R3.4.0.0 or above.
VTG
Syntax $--VTG,cogt,T,cogm,M,sog,N,kph,K,mode*cs
Example $GPVTG,,T,,M,0.000,N,0.000,K,A*23
Input/Output Output
Parameter Definition
33
Standard Positioning Products Protocol Specification
Positioning mode
N – Not positioning
mode STR
A – Point positioning
D – Differential positioning
Checksum
(1): SBAS is only supported by firmware with the version of R3.4.0.0 or above.
ZDA
Syntax $--ZDA,time,day,mon,year,ltzh,ltzn*cs
Example $GPZDA,060845.00,18,08,2017,00,00*6C
Input/Output Output
Parameter Definition
34
hh - Hours
mm - Minutes
ss.ss - Seconds
Checksum
(1): SBAS is only supported by firmware with the version of R3.4.0.0 or above.
GST
Syntax $--GST,time,rngRMS,stdMajor,stdMinor,hdg,stdLat,stdLon,stdAlt*cs
Example $GPGST,060845.00,0.6,,,,0.07,0.09,0.09*47
Input/Output Output
Parameter Definition
35
Standard Positioning Products Protocol Specification
hh - Hours
time STR
mm - Minutes
ss.ss - Seconds
Checksum
(1): SBAS is only supported by firmware with the version of R3.4.0.0 or above.
GGA
$--
Syntax
GGA,time,Lat,N,Lon,E,FS,NoSV,HDOP,msl,M,Altref,M,DiffAge,DiffStation*cs
$GPGGA,063952.000,4002.229934,N,11618.096855,E,1,4,2.788,37.254,M,0
Example
,M,,*71
36
Input/Output Output
Parameter Definition
hh - Hours
time STR
mm - Minutes
ss.sss - Seconds
mm.mmmmmm - Minutes
S – South latitude
mm.mmmmmm - Minutes
W – West longitude
37
Standard Positioning Products Protocol Specification
0-Invalid
2-Differential positioning
6-Recursive positioning(2)
Reference station ID
DiffStation DOUBLE
Null for non-differential positioning
Checksum
(1): SBAS is only supported by firmware with the version of R3.4.0.0 or above.
38
GLL
Syntax $--GLL,Lat,N,Lon,E,time,Valid,Mode*cs
Example $GPGLL,4002.217867,N,11618.105743,E,123400.000,A,A*5B
Input/Output Output
Parameter Definition
mm.mmmmmm - Minutes
S – South latitude
mm.mmmmmm - Minutes
W – West longitude
39
Standard Positioning Products Protocol Specification
hh - Hours
time STR
mm - Minutes
ss.sss - Seconds
A – Valid
Positioning mode
N – Not positioning
Mode STR
A – Point positioning
D – Differential positioning
Checksum
(1): SBAS is only supported by firmware with the version of R3.4.0.0 or above.
GSA
$--
Syntax GSA,Smode,FS,sv1,sv2,sv3,sv4,sv5,sv6,sv7,sv8,sv9,sv10,sv11,sv12,PDOP,H
DOP,VDOP*cs
Example $GPGSA,A,3,14,22,18,31,,,,,,,,,5.572,2.788,4.824*36
Input/Output Output
Parameter Definition
40
BD - BDS system standalone positioning
Positioning mode
1– Not positioning
FS UINT
2– 2D positioning
3– 3D positioning
Participating satellite ID
GPS satellite ID is 1 ~ 32
Checksum
cs STR
A hexadecimal number obtained by calculating an XOR of all
41
Standard Positioning Products Protocol Specification
(1): SBAS is only supported by firmware with the version of R3.4.0.0 or above.
(2) (3) (4): Only supported by firmware with the version of R3.4.0.0 or above.
GSV
$--
Syntax GSV,NoMsg,MsgNo,NoSv,sv1,elv1,az1,cn01,sv2,elv2,az2,cn02,sv3,elv3,az3,
cn03,sv4,elv4,az4,cn04*cs
$GPGSV,3,1,11,3,82,133,50,6,70,73,50,7,21,311,45,13,46,275,50*75
$GPGSV,3,2,11,16,52,51,49,19,52,194,49,21,12,49,37,23,40,222,49*7C
Example $GPGSV,3,3,11,30,31,69,46,31,8,127,19,1,5,,44*77
$BDGSV,2,1,5,161,35,140,47,163,33,224,47,164,24,124,43,167,47,73,48*54
$BDGSV,2,2,5,168,5,,50*52
Description Each GSV message contains information for only 4 satellites. When the
number of satellites exceeds 4, the receiver sends multiple GSV messages
continuously
Input/Output Output
Parameter Definition
NoMsg UINT NoMsg is the total number of GSV messages in this system,
for example:
42
NoMsg in GPGSV is the total number of GPGSV messages,
excluding the number of BDGSV messages
MsgNo UINT MsgNo is the number of this GSV message in this system.
Continuous output GPGSV and BDGSV are numbered
separately
az1 ~ az4 UINT Azimuth of the first to fourth satellite (0 ~ 359 degrees)
Checksum
(1): SBAS is only supported by firmware with the version of R3.4.0.0 or above.
(2) (3) (4): Only supported by firmware with the version of R3.4.0.0 or above.
Due to the excessive number of satellites in GN mode, GSV at 9600 baud rate will have
the problem of incomplete printing of satellite information. For complete satellite
information, please switch the baud rate to 115200
43
Standard Positioning Products Protocol Specification
RMC
Syntax $--RMC,time,status,Lat,N,Lon,E,spd,cog,date,mv,mvE,mode*cs
$GPRMC,123400.000,A,4002.217821,N,11618.105743,E,0.026,181.631,180
Example
411,,E,A*2C
Input/Output Output
Parameter Definition
hh - Hours
time STR
mm - Minutes
ss.sss - Seconds
A – Valid
mm.mmmmmm - Minutes
44
S – South latitude
mm.mmmmmm - Minutes
W – West longitude
cog DOUBLE Calculated clockwise from north. If the speed measurement fails
or the static scene speed is extremely small, the output is empty.
dd - Day
mm - Month
date STR
yy - Year
If the exact year, month, and day are not parsed, the date part
appears blank
Positioning mode
N – Not positioning
mode STR
A – Point positioning
D – Differential positioning
Checksum
45
Standard Positioning Products Protocol Specification
(1): SBAS is only supported by firmware with the version of R3.4.0.0 or above.
VTG
Syntax $--VTG,cogt,T,cogm,M,sog,N,kph,K,mode*cs
Example $GNVTG,0.000,T,,M,0.000,N,0.000,K,A*13
Input/Output Output
Parameter Definition
46
N – Not positioning
A – Point positioning
Checksum
(1): SBAS is only supported by firmware with the version of R3.4.0.0 or above.
ZDA
Syntax $--ZDA,time,day,mon,year,ltzh,ltzn*cs
Example $GNZDA,083927.000,21,11,2013,00,00*4C
Input/Output Output
Parameter Definition
hh - Hours
time STR
mm - Minutes
ss.sss - Seconds
47
Standard Positioning Products Protocol Specification
Checksum
(1): SBAS is only supported by firmware with the version of R3.4.0.0 or above.
1.5.4.1 NAVPOS
Syntax $NAVPOS,time,system,quality,X,Y,Z,lat,lon,height*cs
$NAVPOS,282201000,5,3,-
Example 2160481.168,4383619.182,4084735.203,40.078998,116.236534,52.84384
7*1C
Input/Output Output
Parameter Definition
bit0-GPS
bit5-GAL
bit4-GLO
48
0 - Invalid
1 - External configuration
2 - Coarse
3 - Precise
Checksum
1.5.4.2 NAVVEL
Syntax $NAVVEL,time,system,quality,Vx,Vy,Vz,clockDrift*cs
Example $NAVVEL,282201000,5,3,0.000,0.000,0.000,31.785*2F
Input/Output Output
Parameter Definition
49
Standard Positioning Products Protocol Specification
Checksum
1.5.4.3 NAVTIME
$NAVTIME,GPSW,GPST,GPSQ,GLOY,GLOD,GLOT,GLOQ,BDW,BDT,BDQ,BDG
Syntax
PSDiff,GLOGPSDiff*cs
$NAVTIME,1848,282201.000291049,3,0,0,0.000000000,0,492,282187.00
Example
0291134,3,0.000000085,0.000000000*63
Input/Output Output
Parameter Definition
0 - Invalid
2 - Coarse
3 - Precise
50
GLONASS time quality, the definition is same as that of
GLOQ UINT
GPSQ
BDQ UINT BDS time quality, the definition is same as that of GPSQ
Checksum
1.5.4.4 NAVACC
Syntax $NAVACC,time,status,pAcc,vAcc,cAcc*cs
Input/Output Output
Parameter Definition
hh - Hours
time STR
mm - Minutes
ss.sss - Seconds
51
Standard Positioning Products Protocol Specification
A - Valid
Checksum
1.5.5.1 ANTSTAT
Syntax $ANTSTAT,antType
Example $ANTSTAT,1
antType:
Null: External
Type
0: External
1: Internal
No parameters
Syntax $ANTSTAT,status1,status2
Example $ANTSTAT,0,0
52
Input/Output Output
Parameter Definition
When the external antenna detection circuit does not exist, the information of the antenna
detection output (type: external) is invalid.
For the antenna detection circuit, please refer to the hardware reference design.
1.5.5.2 LSF
Syntax $LSF,system
Example $LSF,0
Input/Output Input
Parameter Definition
53
Standard Positioning Products Protocol Specification
0: GPS
system UINT
1: BDS
2: GLO
3: GAL
$LSF,system,flag,utcTLS,utcTLSF,utcTOT,utcWN,utcDN,utcWNLSF,
Syntax
utcA0,utcA1
Example $LSF,0,1,15,16,462836,82,6,86,7811626,14
Input/Output Input/output
Parameter Definition
1: Valid
54
UTC reference seconds of week, in seconds(BDS system
utcA0 INT in s
GPS Week (GPS Week) is the time system adopted in the GPS system. Time Zero is
defined as: 0 a.m. on January 6, 1980. Every 1024 weeks (7168 days) is a cycle. The first
GPS cycle point is 0000:00 and 000:00 on August 22, 1999. That is, from this moment
on, the number of weeks starts again from zero. The rule for counting the number of
weeks is: Sunday is 1, and in turn is 1-7.
The Beidou satellite navigation time system starts at 000:00 and 000:00 UTC ON 1
January 2006. Use Week and seconds into the week count. The rule for counting the
number of weeks is: Sunday is 0, and in turn is 0-6
utcWNLSF: A decimal number converted from the lower eight bits of the binary week
when a leap second occurs. For example: A leap second occurs in the 900th week
(binary: 1110000100) and it is broadcast in 132 (Binary: 10000100).
STEP1: Convert GPSW in Navtime to binary, set the lower eight bits to zero, and then
55
Standard Positioning Products Protocol Specification
convert to decimal.
STEP2: Add the number in STEP1 to utcWNLSF to get the week when a leap second
occurs.
STEP1: Convert the BDW in Navtime to binary, set the lower eight bits to zero, and then
convert to decimal.
STEP2: Add utcWNLSF to the number in STEP1 to get the week when a leap second
occurs.
UTCDN: Days of the week in which a leap seconds occurs: GPS: 1-7 from Sunday to
Saturday; BDS: 0-6 from Sunday to Saturday
1.5.5.3 CWOUT
Syntax $CWOUT,CWFlagOut,CWRatioOut
Example $CWOUT,1,0
Input/Output Output
Parameter Definition
Interference
1: No interference
CWFlagOut UINT
2: Interference detected
56
1.5.5.4 FCTATEST
Syntax $fctatest,Model
Example $fctatest,1
Input/Output Input
Parameter Definition
0: disable
Model UINT
1: enable
This test mode only supports carrier-to-noise ratio detection of signals modulated with
carrier and pseudo code, and the command can only be used for production line test. In
actual positioning application, abnormal positioning may occur when sending the
command, and power off the receiver or disable the command to recover
1.5.5.5 ABNORMAL
Syntax $CFGMSG,msgClass,msgID
Example $CFGMSG,6,4
Input/Output Input
No parameters
Syntax $ABNORMAL,DataLen,AbnLevel
Example $ABNORMAL,0,3*13
57
Standard Positioning Products Protocol Specification
Input/Output Output
Parameter Definition
DataLen INT Input data length from the serial port after starting up.
Note: This statement is output every 5s. If the satellite absence level is 0, it will not be
output. Only supported by R3.4.0.19 version.
1.5.5.6 EPHABNORMAL
Syntax $CFGMSG,msgClass,msgID
Example $CFGMSG,6,2
Input/Output Input
No parameters
Syntax $EPHABNORMAL,status
Example $EPHABNORMAL,1*50
Input/Output Output
Parameter Definition
58
Note: The value is fixed at 1. The output of the message indicates the incompleteness of
the ephemeris injection, and the default output frequency is once every 10s.
This command is only applicable to version R3.2.20.100, and only when the ephemeris
injection is incomplete will this message be output.
1.5.5.7 OSNMA
Output Galileo I/NAV Message
Syntax $PNAVMSG,svid,wordtype,x1,x2,x3,…,x30
Example $PNAVMSG,1,0,BE,DA,49,72,CB,C3,80,EA,AA,AA,4D,41,0A,3F,40
Input/Output Output
Parameter Definition
x1, x2, x3, …, x30 UINT Odd and even part of I/NAV message, range: -128~127
Raw observations are output via the RTCM MSM. The message number of each GNSS
MSM is defined as follows:
GPS 1075
59
Standard Positioning Products Protocol Specification
GAL 1095
BDS 1125
QZSS 1115
Raw ephemeris data are output via the RTCM EPH messages in RTCM version 3.3.
The following contents are excerpted from the RTCM STANDARD 10403.3 for your
reference.
Ephemerides
Differential data
60
No. Items Chapters in RTCM STANDARD 10403.3
12 Data Types 3.3 Data Types: Table 3.3-1 Data Type Table
13 Data Fields 3.4 Data Fields: Table 3.4-1 Data Field Table
Only supported by firmware R3.6.2.0 and R3.6.3.0. Output raw observations of GPS, BDS,
Galileo, and QZSS.
61
和芯星通科技(北京)有限公司
Unicore Communications, Inc.
北京市海淀区丰贤东路 7 号北斗星通大厦三层
F3, No.7, Fengxian East Road, Haidian, Beijing, P.R.China,
100094
www.unicorecomm.com
Phone: 86-10-69939800
Fax: 86-10-69939888
www.unicorecomm.com
62