Tus neeg siv phau ntawv
Table Of Contents
- Disclaimer
- 1 Product overview
- 2 Specification and parameters
- 3 Size and pins definition
- 4 Recommended circuit diagram
- 5 Hardware design
- 6 E108-Product test
- 7 Command format
- 7.1 GKC interface data format
- 7.2 GKC command
- 7.2. Response message
- 7.2.2 System reboot
- 7.2.3 Erase auxiliary information
- 7.2.4 Low power mode
- 7.2.5 Message interval configuration
- 7.2.6 Periodic low power mode
- 7.2.7 Set star search mode
- 7.2.8 Save star search mode
- 7.2.9 Serial port parameter setting
- 7.2.10 Set NMEA output
- 7.2.11 GPD document delete
- 7.2.12 Set NMEA serial port parameter
- 7.2.13 PPS configuration
- 7.2.14 Query message interval
- 7.2.15 Return message interval
- 7.2.16 Set NMEA output frequency
- 7.2.17 Query NMEA output frequency
- 7.2.18 Return the NMEA output frequency
- 7.2.19 Set reference coordinates
- 7.2.20 Query Reference Coordinate System
- 7.2.21 Return Reference Coordinate System
- 7.2.22 Query RTC time
- 7.2.23 Return RTC time
- 7.2.24 Set the speed threshold
- 7.2.25 Set HDOP Threshold
- 7.2.26 Get HDOP Threshold
- 7.2.27 Version number query
- 7.2.28 Return the current version number
- 7.2.29 Set location and time information
- 7.2.30 Set positioning mode
- 7.2.31 Query ID information
- 7.2.32 Return ID information
- 7.3 Support NMEA0183 protocol
- 8 GDP User Guidance
- 9 FAQ
- 10 Welding instruction
- 11 E108 Series
- 12 Packing for batch order
- Revision history
- About us
Chengdu Ebyte Electronic Technology Co.,Ltd. E108-GN User Manual
Copyright ©2012–2021
，
Chengdu Ebyte Electronic Technology Co.,Ltd.
2
30
can clear the GPD data in the chip by sending serial commands. Of course, every time new GPD data is uploaded, the original old GPD data
will be cleared first.
Delete GPD data command: Enter "PGKC047" in the command input box of the naviTrack navigation tool.
8.5 The effect after using GPD
Since the ephemeris data of the currently visible satellites have been acquired, the positioning time can be effectively
reduced. After using GPD, the cold start positioning time can be improved by about 10~15 seconds. Especially in the case of
weak signal, it is possible to improve the positioning speed even more.
8.6 Assisted localization methods to accelerate GPD
Since pure GPD assistance also needs to rely on the GPS time information of the search sky, sometimes when the signal is poor, it still
consumes too much time. Setting the current time information and rough coordinate information through the PGKC639 command can
achieve faster positioning time.
Note: When setting by the 639 command, the range of latitude and longitude should be within 20km of the actual position, and the time
deviation should not exceed 5 minutes.
Command: 639
Set approximate location and time information for faster positioning.
Arguments:
Arg1: Latitude, eg: 28.166450
Arg2: Longitude, for example: 120.389700
Arg3: height, eg: 0 Arg4: year
Arg5: month
Arg6: day
Arg7: Hour, time is UTC time
Arg8: points
Arg9: seconds
Example:
$PGKC639,28.166450,120.389700,0,2017,3,15,12,0,0*33<CR><LF>
After the 639 command is successfully executed, GK9501 will return the following format:
$PGKC001,639,3*21
8.7 GPD communication
Mainly through serial communication to transmit GPD data to the chip in blocks. The main process is as follows:
8.7.1 Switch NMEA reception to BINARY reception mode
(For the command format, please refer to GK9501 Input and Output Format.pdf)
Send: message type + toggle mode + baud rate + CheckSum
Data: $PGKC149,1,115200*15
(Message type 149 for GPD transport)
Receive: packet header (2B) + packet length (2B) + ACK type (2B) + message type (2B) + valid flag (1B) + CheckSum (1B) + packet
tail (2B)
Data: 0xaa, 0xf0, 0x0c, 0x00, 0x01, 0x00, 0x95, 0x00, 0x03, (chk), 0x0d, 0x0a
(checksum is a byte-by-byte XOR from the start of the packet length field to the field before the checksum)