0% found this document useful (0 votes)
101 views6 pages

Kingneed 2G Protocol Overview

This document outlines the Kingneed GPS data upload protocol and command formats. It describes: 1) The format for uploading various types of GPS and sensor data from trackers to the server, including location, battery, cell tower and WiFi data. 2) The format for commands sent from the server to the tracker, and whether the tracker should just operate the command, operate and reply to the server, or operate and reply via SMS. 3) The command format for the tracker to reply via SMS or GPRS, starting responses with "*check*1*" followed by "@GPRS" for GPRS replies.

Uploaded by

Aurélio Faria
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
101 views6 pages

Kingneed 2G Protocol Overview

This document outlines the Kingneed GPS data upload protocol and command formats. It describes: 1) The format for uploading various types of GPS and sensor data from trackers to the server, including location, battery, cell tower and WiFi data. 2) The format for commands sent from the server to the tracker, and whether the tracker should just operate the command, operate and reply to the server, or operate and reply via SMS. 3) The command format for the tracker to reply via SMS or GPRS, starting responses with "*check*1*" followed by "@GPRS" for GPRS replies.

Uploaded by

Aurélio Faria
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 6

Kingneed Protocol

Following this the GPS data upload protocol for Kingneed trackers
New Server Settings Command is *setip*192*168*1*1*8080* eg IP
192.168.1.1eg Port 8080

1.Upload Content (Device to Server)

1.1 Registration Content (ZC01)


(013632651491,ZC01,040613, 040137,123456,008613800000000)
or(013632651491,ZC01, 040613, 040137,123456,008613800000000,
008613800000001,…, 00861380000000N)

"("         stands for packet start


"013632651491" stands for tracker ID
" ZC01"       stands for data command
"040613"     stands for data, 04/June/2013
"040137"     stands for time,  04:01:37, UTC time
“123456” Password
"008613800000000" Master number

“008613800000001” Bounded number 1


“…” …
“008613800000003 ” Bounded number 3

")"         stands for packet end

1.2 LLC format: (BP05)


(013632651491,BP05,040613,A,2234.0297N,11405.9101E,000.0,040137,17
8.48,1.21,8,0,2.9000,7.6999)

"("         stands for packet start


"013632651491"   stands for tracker ID
"BP05"       stands for data command
"040613"     stands for data, 04/June/2013
"A"      stands for GPS valid data,  
"V" stands for GPS invalid data
"2234.0297"     stands for latitude, format is ddmm.mmmm
"N"         stands for north,
"S" stands for south
"11405.9101"    stands for longitude, format is dddmm.mmmm
"E"         stands for east,  
"W" stands for west
"000.0"      stands for speed, unit is  km/h
"040137"     stands for time,  04:01:37, UTC time
"178.48"      stands for direction
"1.21" stands for altitude
"8" stands for ranking
“0” stands for mileage //customized only
“2.9000” stands for gps hdop//customized only
“7.6999” stands for gps pdop//customized only
")"          stands for packet end

1.3Heartbeat Packet (ZC02)


(013632651491,ZC02, 040613, 040137)

"("         stands for packet start


"013632651491" stands for tracker ID
" ZC02"        stands for data command
"040613"     stands for data, 04/June/2013
"040137"     stands for time,  04:01:37, UTC time
")"        stands for packet end

1.4 Return SMS (ZC03)


(013632651491,ZC03, 040613, 040137,$…$)

"("         stands for packet start


"013632651491" stands for tracker ID
" ZC03"       stands for data command
"040613"     stands for date, 04/June/2013
"040137"     stands for time,  04:01:37, UTC time
“$…$” stands for return content
")"         stands for packet end

Example
Online sending SMS *about* to device number, server will receive return
content as follows
(013632651491,ZC03,040613,040137,$Notice: Device's serial number:
013632651491.Software version: V2.000,2013/06/03 17:10.$)

1.5 Power On (ZC04)


(013632651491,ZC04,040613,040137)

"("         stands for packet start


"013632651491" stands for tracker ID
" ZC04"       stands for power on status
"040613"     stands for date, 04/June/2013
"040137"     stands for time,  04:01:37, UTC time
")"         stands for packet end

1.5.1 Battery Level(ZC20)

(013632651491, ZC20,040613,040137,6,42,112,0)

"("         stands for packet start


"013632651491" stands for tracker ID
" ZC20"        stands for battery level command
"040613"     stands for data, 04/June/2013
"040137"     stands for time,  04:01:37, UTC time
"6" stands for battery level, range is 0-6,255 refers to invalid rate
“421” stands for battery voltage, eg 4.21V,65535 refers to invalid rate
“112” stands for battery inputvoltage, eg11.2V,65535 refers to invalid
rate
“0” stands for not installed(0) or installed(1), 255 refers to invalid rate
“0”, stands for digital inputs //customized only
“0”, stands for analog inputs //customized only
“0”, stands for analog inputs //customized only
")"        stands for packet end

1.6 LLC format: (DW30)


(013632651491,DW30,040613,A,2234.0297N,11405.9101E,000.0,040137,17
8.48,1.21,8,0,2.9000,7.6999)

"("         stands for packet start


"013632651491"   stands for tracker ID
"DW30"       stands for data command
"040613"     stands for data, 04/June/2013
"A"      stands for GPS valid data,  
"V" stands for GPS invalid data
"2234.0297"     stands for latitude, format is ddmm.mmmm
"N"         stands for north,
"S" stands for south
"11405.9101"    stands for longitude, format is dddmm.mmmm
"E"         stands for east,  
"W" stands for west
"000.0"      stands for speed, unit is  km/h
"040137"     stands for time,  04:01:37, UTC time
"178.48"      stands for direction
"1.21" stands for altitude
"8" stands for ranking
“0” stands for mileage //customized only
“2.9000” stands for gps hdop//customized only
“7.6999” stands for gps pdop//customized only
")"          stands for packet end

1.6.1 Cell Tower & WIFI format: (DW50)


(013632651491,DW50,460,0,0,6,0,040613,040137)
(013632651491,DW50,460,0,0,6,2,aa*bb*cc*dd*ee*ff:-8:0,aa*bb*cc*dd*ee*ff:-
8:0,040613,040137)

"("          stands for packet start


"013632651491"  stands for tracker ID
"DW50"        stands for data command
"460"        mcc
"1"        mnc
"0"        lac
"6"        cid
“0” wifi number
"040613"     stands for data, 04/June/2013
"040137"     stands for time,  04:01:37, UTC time
")"          stands for packet end

"("          stands for packet start


"013632651491"  stands for tracker ID
"DW50"        stands for data command
"460"        mcc
"1"        mnc
"0"        lac
"6"        cid
“2” wifi number
“aa*bb*cc*dd*ee*ff:-8:0” wifi string(mac:rssi:channel_number)
“aa*bb*cc*dd*ee*ff:-8:0” wifi string(mac:rssi:channel_number)
"040613"     stands for data, 04/June/2013
"040137"     stands for time,  04:01:37, UTC time
")"          stands for packet end

Note: The following format is the same as (DW30)(DW50).


1.7 Motion Alert with Location: (DW31)(DW51)
1.8 Low Battery Alert with Location: (DW32)(DW52)
1.9 Power Cut Alert with Location: (DW33)(DW53)
1.10 Dismounting Alert with Location: (DW37)(DW57)
1.11 Check format: (DW3B)(DW5B)
1.12 SOS format: (DW3E)(DW5E)
1.13 Open Alert format: (DW3F)(DW5F)
1.14 Low Voltage Alert format: (DW40)(DW60)
1.15 Bad Battery Alert format: (DW41)(DW61)
1.16 Ignition Alert format: (DW42)(DW62)
1.17 ACC On Alert format: (DW35)(DW55)
1.18 ACC Off Alert format: (DW36)(DW56)
1.19 Fuel Cut On format: (DW43)(DW63)
1.20 Fuel Cut Off format: (DW44)(DW64)
1.21 Fuel Cut Alert format: (DW45)(DW65)
1.22 Human Alert format: (DW46)(DW66)
1.23 Light Alert format: (DW47)(DW67)
1.24 Stamp Alert format: (DW48)(DW68)
1.25 Cover Open Alert format: (DW49)(DW69)
1.26 fingerprint Up format: (DW4A)(DW6A)
1.27 Mileage Report with Location: (DW4B)(DW6B)

2. Return Content (Server to Device)

1. Upload succeeded
Sever will reply ok when command is received.
2. GPRS command process on Server. There are 3 ways for devices to
respond the command:
(1) Device operates the commands and do nothing else.
(2) Device operates the commands and upload replies to server
(3) Device operates command and send replies to master number via SMS.

You can follow the below format as needed.

(1) Operate command only, without sending acknowledge.

Eg Send Command from server to device through


GPRS  [begin]sms1,*locate*,*alertoff*,*routetrackoff*,[end]   

System will operate *locate*,*alertoff*,*routetrackoff*commands, and


there won't be any replies to the user’s phone or to server.

(2) Send acknowledge to server after operating command. 

Eg Send Command from server to device through


GPRS [begin]sms2,*locate*,*alertoff*,*routetrackoff*,[end]

System will operate ,*locate*,*alertoff*,*routetrackoff* commands,


and replies will be uploaded to server through GPRS.
(3) Send acknowledge to master number after operating command

Eg Send Command from server to device through


GPR [begin]sms3,*locate*,*alertoff*,*routetrackoff*,[end]

System will operate ,*locate*,*alertoff*,*routetrackoff* command


and replies will be sent to user's phone  through SMS. 

3. Command format

3.1 Device will return SMS to master phone number by sending command as
follow format: *check*1*

3.2 Device will send the response via gprs channel. (TCP)


*check*1*@GPRS*

Note: This is incorporated into every current SMS command.

You might also like