Identifier of cheap Chinese GPS tracking unit?
Is there a reason you're not following documentation?
Hi Anton,
I have followed the documentation.
The last sentence is saying: If even that doesn't help, please contact support.
So I did.
I have created different devices with different identifiers including 11 last digits from IMEI plus leading zero.
None of the devices get updated.
I'm now getting this as HEX values in the log file:
2020-10-25 17:10:24 INFO: [da8aa9c7] connected
2020-10-25 17:10:24 INFO: [da8aa9c7: dmt < 109.139.211.153] HEX: 78780d010353929217034918000523000d0a
2020-10-25 17:10:25 INFO: [da8aa9c7: dmt < 109.139.211.153] HEX: 79790020940a035392921703491801230123012301238932002100221710546f000243dc0d0a
2020-10-25 17:10:44 INFO: user: 1, action: create, object: device, id: 5
2020-10-25 17:10:44 INFO: user: 1, action: link, owner: user, id: 1, property: device, id: 5
2020-10-25 17:11:09 INFO: [da8aa9c7: dmt < 109.139.211.153] HEX: 78781311140a19100b0800ce01238f00c0500005c5610d0a
2020-10-25 17:11:25 INFO: [da8aa9c7: dmt < 109.139.211.153] HEX: 78781f12140a19100b18c605755d0d005e24e901548800cece238f00c05000064e640d0a
2020-10-25 17:11:25 INFO: [da8aa9c7: dmt < 109.139.211.153] HEX: 78780f36400602000100270204cf0003bae30d0a
2020-10-25 17:11:47 INFO: user: 1, action: create, object: device, id: 6
2020-10-25 17:11:47 INFO: user: 1, action: link, owner: user, id: 1, property: device, id: 6
2020-10-25 17:12:25 INFO: [da8aa9c7: dmt < 109.139.211.153] HEX: 78780a1300050251000702d5000d0a
2020-10-25 17:13:25 INFO: [da8aa9c7: dmt < 109.139.211.153] HEX: 78780a130005025100081594000d0a
2020-10-25 17:14:00 INFO: user: 1, action: create, object: device, id: 7
2020-10-25 17:14:00 INFO: user: 1, action: link, owner: user, id: 1, property: device, id: 7
2020-10-25 17:14:25 INFO: [da8aa9c7: dmt < 109.139.211.153] HEX: 78780a130005025100090c4c000d0a
2020-10-25 17:14:45 INFO: user: 1, action: edit, object: device, id: 7
2020-10-25 17:15:25 INFO: [da8aa9c7] disconnected
2020-10-25 17:15:25 INFO: [aed3ed58] connected
2020-10-25 17:15:25 INFO: [aed3ed58: dmt < 109.139.211.153] HEX: 78780d010353929217034918000adbf70d0a
2020-10-25 17:15:26 INFO: [aed3ed58: dmt < 109.139.211.153] HEX: 79790020940a035392921703491801230123012301238932002100221710546f000426ea0d0a
2020-10-25 17:16:25 INFO: [aed3ed58: dmt < 109.139.211.153] HEX: 78781f12140a19101018c605755d0d005e24e901548800cece238f00c050000a3fd30d0a
2020-10-25 17:16:25 INFO: [aed3ed58: dmt < 109.139.211.153] HEX: 78780f36400602000100270204cf0005c9660d0a
2020-10-25 17:17:25 INFO: [aed3ed58: dmt < 109.139.211.153] HEX: 78780a1300050251000bab75000d0aI'm wondering what the "action: create" means.
I have also created different devices with id's 5, 6, 7 and even 8 but none of them get updated.
According to the specifications, this is the login packet:
78780d010353929217034918001acb760d0a
with
- 7878 = start of packet
- 0d = length (13 bytes)
- 01 = type of packet; in this case Login Information
- 0353929217034918 = Terminal ID
- 001a = information serial number (I guess they mean sequence number)
- cb76 = error check
- 0d0a = end of packet
So I guess that 0353929217034918 should be my identifier according to the protocol.
But also this identifier is not getting updated.
Can you help me out?
Best regards,
Kurt
I think you need to carefully read the link that I provided earlier.
Hi Anton,
I have read the link a couple of times now, and I'm not getting any wiser.
I have changed the ip + port. The (HEX) data is arriving and I can see the (HEX) data in the log file.
The device is sending status information and GPS coordinates. I can also see this information in the log file.
I have also tried different identifiers but none of them are getting updated.
I also tried the Hex Decoder / Encoder but I'm getting this result: Binary Hex can't be converted to Text
If you know the answer, can you please share it?
Best regards,
Kurt
Correct port for this device is 5023.
Hi,
I have a cheap Chinese GPS tracking unit including the specifications of the protocol (GT06N). Looking at the supported traccar devices I can see that GT06N is supported.
I was able to redirect the communication to my Traccar server and this is what I'm getting:
I also have a DART2 tracking device and the tracker-server.log reveiled an unknown device id which I could use to create a new device in the traccar web application.
This time I'm not getting an unknown device id with this cheap Chinese GPS tracking unit although I do get the HEX data in the tracker-server.log file. Looking at the protocol I can see that 0x78 0x78 is the start and 0x0D 0x0A is the end so that seems to match.
Can you help me out with this one? I want to create a new device in the traccar web application but I don't know what the identifier is. The log file is not reveiling this information.
Best regards,
Kurt