Topin G12p reports some default fix time and location

TN01a year ago

Hi,

I just got couple of Topin devices, one of them is this one (G12p):
https://www.aliexpress.com/item/32949344396.html

I could set my server's host and port (5023) to the correct one I believe with an SMS command but for some reason the device reports only some default time and location:

/opt/traccar/logs # cat tracker-server.log|grep "T93918b45"
2023-06-07 19:16:46  INFO: [T93918b45] connected
2023-06-07 19:16:46  INFO: [T93918b45: gt06 < MY_SIM_IP] 78780d0108612610242055325f0d0a
2023-06-07 19:16:46  INFO: [T93918b45: gt06 > MY_SIM_IP] 787805012055ee4e0d0a
2023-06-07 19:17:01  INFO: [T93918b45: gt06 < MY_SIM_IP] 787801080d0a
2023-06-07 19:17:01  INFO: [T93918b45: gt06 > MY_SIM_IP] 78780508787895800d0a
2023-06-07 19:17:07  INFO: [T93918b45: gt06 < MY_SIM_IP] 78780713645f08194b0d0a
2023-06-07 19:17:07  INFO: [T93918b45] id: 861261024205532, time: 1970-01-01 00:00:00, lat: 0.00000, lon: 0.00000, course: 0.0
2023-06-07 19:17:07  INFO: [T93918b45: gt06 > MY_SIM_IP] 787805135f08240f0d0a
2023-06-07 19:22:07  INFO: [T93918b45: gt06 < MY_SIM_IP] 787801080d0a
2023-06-07 19:22:07  INFO: [T93918b45: gt06 > MY_SIM_IP] 78780508787895800d0a
2023-06-07 19:27:07  INFO: [T93918b45: gt06 < MY_SIM_IP] 78780713645f0819550d0a
2023-06-07 19:27:07  INFO: [T93918b45] id: 861261024205532, time: 1970-01-01 00:00:00, lat: 0.00000, lon: 0.00000, course: 0.0
2023-06-07 19:27:07  INFO: [T93918b45: gt06 > MY_SIM_IP] 787805135f08240f0d0a

What could be the problem?

Many thanks,
TN

Anton Tananaeva year ago

Your device is not reporting a location. It's common for GT06-based devices to only send location when device is moving. Check for that.

TN01a year ago

Later on it sent in some additional data but got an error:

2023-06-07 19:42:08  INFO: [T93918b45: gt06 < MY_SIM_IP] 787801080d0a
2023-06-07 19:42:08  INFO: [T93918b45: gt06 > MY_SIM_IP] 78780508787895800d0a
2023-06-07 19:42:42  INFO: [T93918b45: gt06 < MY_SIM_IP] 7878081a2306071942409483c416edf2339683c416edf233342cc4eb6e214d905c449a016d4f342cc4d7541b50925c1479772854905c4479772855ec43f6c6d0685a0701100200004e840000c0415000004e840000c1455a00004e840000c34d5a00004e840000c03f6400004e840000bca96400004e840000be6c6400004e840000c06a64000d0a
2023-06-07 19:42:42  INFO: [T93918b45] error - Latitude out of range - IllegalArgumentException (Position:234 < Gt06ProtocolDecoder:309 < *:271 < *:803 < *:1420 < ExtendedObjectDecoder:75 < ...)
2023-06-07 19:42:42  INFO: [T93918b45] disconnected
TN01a year ago

Btw traccar version is 5.7.

Anton Tananaeva year ago

Try the latest version. If it still happens, there are probably some protocol changes that need to be implemented.

TN01a year ago

Just tried it with traccar/traccar:5.8-alpine from docker hub, same result:

2023-06-07 20:03:49  INFO: [Tedc65b25] connected
2023-06-07 20:03:49  INFO: [Tedc65b25: gt06 < MY_SIM_IP] 78780d0108612610242055325f0d0a
2023-06-07 20:03:49  INFO: [Tedc65b25: gt06 > MY_SIM_IP] 787805012055ee4e0d0a
2023-06-07 20:04:06  INFO: [Tedc65b25: gt06 < MY_SIM_IP] 7878051a2306072003049483c416edf2399683c416edf239905c4479772850925c1479772850ec43f6c6d068560701100200004e840000c0415000004e840000c34d5a00004e840000c1445a00004e840000c1455a00004e840000c03f6400004e840000c06a6400004e840000c14664000d0a
2023-06-07 20:04:06  INFO: [Tedc65b25] error - Latitude out of range - IllegalArgumentException (Position:236 < Gt06ProtocolDecoder:309 < *:271 < *:803 < *:1443 < ExtendedObjectDecoder:75 < ...)
2023-06-07 20:04:06  INFO: [Tedc65b25] disconnected
TN01a year ago

Tested my other Topin device which is this one:
https://www.aliexpress.com/item/32836242942.html

Got the same results:

2023-06-08 19:16:30  INFO: [T4207e51e] connected
2023-06-08 19:16:30  INFO: [T4207e51e: gt06 < MY_SIM_IP] 78780d010359339077262376060d0a
2023-06-08 19:16:30  INFO: [T4207e51e: gt06 > MY_SIM_IP] 787805012623ac2f0d0a
2023-06-08 19:16:51  INFO: [T4207e51e: gt06 < MY_SIM_IP] 787807135b060819640d0a
2023-06-08 19:16:51  INFO: [T4207e51e] id: 359339077262376, time: 1970-01-01 00:00:00, lat: 0.00000, lon: 0.00000, course: 0.0
2023-06-08 19:16:51  INFO: [T4207e51e: gt06 > MY_SIM_IP] 78780513060820e00d0a
2023-06-08 19:17:31  INFO: [T4207e51e: gt06 < MY_SIM_IP] 7878061a2306081915549483c416edf2419683c416edf241342cc4eb6e214c905c4479772853342cc4d7541b5986248f27866b5d0701100200004e840000c0414600004e840000c1444600004e840000b31d5000004e840000c2a25000004e840000c1455000004e840000bca95000004e840000c14650000d0a
2023-06-08 19:17:31  INFO: [T4207e51e] error - Latitude out of range - IllegalArgumentException (Position:236 < Gt06ProtocolDecoder:309 < *:271 < *:803 < *:1443 < ExtendedObjectDecoder:75 < ...)
2023-06-08 19:17:31  INFO: [T4207e51e] disconnected

Do you need anything else from me like more debug logs for the possible fix?

Anton Tananaeva year ago

If you want us to investigate and implement support, email us and provide the protocol documentation.

TN01a year ago

I will try to ask Topin for the protocol doc, however I realized that there is a separate port 5199 for Topin devices. I am now sending the data to that port and it looks like the server is not interpreting these longer packets which I believe should be the GPS coordinates and it is not responding to those packets:

2023-06-10 19:34:48  INFO: [T04b651f0] connected
2023-06-10 19:34:48  INFO: [T04b651f0: topin < MY_SIM_IP] 78780d010359339077262376060d0a
2023-06-10 19:34:48  INFO: [T04b651f0: topin > MY_SIM_IP] 78780d01010d0a
2023-06-10 19:34:48  INFO: [T04b651f0: topin > MY_SIM_IP] 7878073007e7060a1322300d0a
2023-06-10 19:34:49  INFO: [T04b651f0: topin < MY_SIM_IP] 787815b338393335333133303730303136363839303438460d0a
2023-06-10 19:35:09  INFO: [T04b651f0: topin < MY_SIM_IP] 787807133d0608195b0d0a
2023-06-10 19:35:09  INFO: [T04b651f0] id: 359339077262376, time: 1970-01-01 00:00:00, lat: 0.00000, lon: 0.00000, course: 0.0
2023-06-10 19:35:09  INFO: [T04b651f0: topin > MY_SIM_IP] 787807133d0608195b0d0a
2023-06-10 19:35:50  INFO: [T04b651f0: topin < MY_SIM_IP] 787807133d060819640d0a
2023-06-10 19:35:50  INFO: [T04b651f0] id: 359339077262376, time: 1970-01-01 00:00:00, lat: 0.00000, lon: 0.00000, course: 0.0
2023-06-10 19:35:50  INFO: [T04b651f0: topin > MY_SIM_IP] 787807133d060819640d0a
2023-06-10 19:36:22  INFO: [T04b651f0: topin < MY_SIM_IP] 7878041a2306101936209683c416edf2459483c416edf245342cc4eb6e2158905c447977285d0701100200004e840000c0415000004e840000c1445000004e840000c34d5a00004e840000c1455a00004e840000bca85a00004e840000bca95a00004e840000b9e75a000d0a
2023-06-10 19:37:22  INFO: [T04b651f0: topin < MY_SIM_IP] 7878041a2306101936209683c416edf2459483c416edf245342cc4eb6e2158905c447977285d0701100200004e840000c0415000004e840000c1445000004e840000c34d5a00004e840000c1455a00004e840000bca85a00004e840000bca95a00004e840000b9e75a000d0a
2023-06-10 19:37:32  INFO: [T04b651f0: topin < MY_SIM_IP] 7878041a2306101936209683c416edf2459483c416edf245342cc4eb6e2158905c447977285d0701100200004e840000c0415000004e840000c1445000004e840000c34d5a00004e840000c1455a00004e840000bca85a00004e840000bca95a00004e840000b9e75a000d0a
2023-06-10 19:37:42  INFO: [T04b651f0: topin < MY_SIM_IP] 7878041a2306101936209683c416edf2459483c416edf245342cc4eb6e2158905c447977285d0701100200004e840000c0415000004e840000c1445000004e840000c34d5a00004e840000c1455a00004e840000bca85a00004e840000bca95a00004e840000b9e75a000d0a
2023-06-10 19:39:43  INFO: [T04b651f0: topin < MY_SIM_IP] 787807133e060819600d0a
2023-06-10 19:39:43  INFO: [T04b651f0] id: 359339077262376, time: 1970-01-01 00:00:00, lat: 0.00000, lon: 0.00000, course: 0.0
2023-06-10 19:39:43  INFO: [T04b651f0: topin > MY_SIM_IP] 787807133e060819600d0a
2023-06-10 19:44:44  INFO: [T04b651f0: topin < MY_SIM_IP] 787801080d0a
2023-06-10 19:46:23  INFO: [T04b651f0: topin < MY_SIM_IP] 7878041a2306101946219483c416edf2489683c416edf24a342cc4eb6e2150905c44797728570701100200004e840000c1444600004e840000c0414600004e840000c34d5000004e840000c03d5000004e840000b9e75000004e840000c1455000004e840000bca950000d0a
2023-06-10 19:47:23  INFO: [T04b651f0: topin < MY_SIM_IP] 7878041a2306101946219483c416edf2489683c416edf24a342cc4eb6e2150905c44797728570701100200004e840000c1444600004e840000c0414600004e840000c34d5000004e840000c03d5000004e840000b9e75000004e840000c1455000004e840000bca950000d0a
2023-06-10 19:47:33  INFO: [T04b651f0: topin < MY_SIM_IP] 7878041a2306101946219483c416edf2489683c416edf24a342cc4eb6e2150905c44797728570701100200004e840000c1444600004e840000c0414600004e840000c34d5000004e840000c03d5000004e840000b9e75000004e840000c1455000004e840000bca950000d0a
2023-06-10 19:47:44  INFO: [T04b651f0: topin < MY_SIM_IP] 7878041a2306101946219483c416edf2489683c416edf24a342cc4eb6e2150905c44797728570701100200004e840000c1444600004e840000c0414600004e840000c34d5000004e840000c03d5000004e840000b9e75000004e840000c1455000004e840000bca950000d0a

What do you think?

Anton Tananaeva year ago

It does look more like Topin protocol.

TN0110 months ago

Just received the protocol doc from Topin. Sent it via email.

Jimmy Cheng2 days ago

Hi, came across a similar issue when testing with Topin devices, the device reports a GPS coordinate after powering on, but the coordinate doesn't change as expected afterward. What could be the problem? Does it need to be configured or initialized after logging in?