iStartek VT600

Ramon R2 years ago

I have one iStartek VT600 gps device and next is extracted logs from the traccar-server.log file for this specific gps device:

2023-11-07 13:13:00  INFO: [T0a827337: startek < 200.68.141.65] 24240011121141207845ff50002bbb0d0a
2023-11-07 13:16:42  INFO: [T0a827337: startek < 200.68.141.65] 2424007e121141207845ff99553139313634312e3030302c412c323534362e373230302c4e2c31303031312e373032342c572c302e30302c34382c3037313132332c2c2a32357c312e347c3433337c323030307c303030302c303030307c303134453030313430353342373834397c31347c3045384233333741ec750d0a
2023-11-07 13:16:52  INFO: [T0a827337: startek < 200.68.141.65] 00
2023-11-07 13:30:15  INFO: [Ta5932afa: startek < 200.68.165.46] 24240011121141207845ff50002bbb0d0a
2023-11-07 13:32:02  INFO: [Ta5932afa: startek < 200.68.165.46] 00
2023-11-07 13:38:13  INFO: [Tdd9d7d0a: startek < 200.68.140.17] 00
2023-11-07 13:38:42  INFO: [Tdd9d7d0a: startek < 200.68.140.17] 24240011121141207845ff50002bbb0d0a
2023-11-07 13:39:44  INFO: [T81741015: startek < 200.68.165.2] 24240011121141207845ff50002bbb0d0a
2023-11-07 13:40:44  INFO: [T924e9b34: startek < 200.68.164.23] 24240011121141207845ff50002bbb0d0a
2023-11-07 13:42:09  INFO: [T924e9b34: startek < 200.68.164.23] 00

According to the documentation, from the gps manufacturer iStartek, the gprs communication seems to be working correctly, but for someone reason I can't see the gps device in the user account as online. Unfortunately I don't have idea how to check if the frame is sending correct data like date/time, latitude, longitude, etc

iStartek GPRS Protocol Between GPS Tracker and Server

any idea why is this occurring?

Ramon R2 years ago

I found a way to convert the data encoded in HEX to ASCII as follows:

root@mail:~/scripts# echo 2424007e121141207845ff99553139313634312e3030302c412c323534362e373230302c4e2c31303031312e373032342c572c302e30302c34382c3037313132332c2c2a32357c312e347c3433337c323030307c303030302c303030307c303134453030313430353342373834397c31347c3045384233333741ec750d0a | xxd -r -p && echo ''
$$~A xE▒▒U191641.000,A,2546.7200,N,10011.7024,W,0.00,48,071123,,*25|1.4|433|2000|0000,0000|014E0014053B7849|14|0E8B337A▒u

So seems like the gps frame contains a valid gps position according to the iStartek GPRS Protocol document.

Any idea why then the traccar platform is not updating the gps device in the list of devices (map). I have another device with "osmand" protocol and is working fine.

Anton Tananaev2 years ago

What ports have you tried? Have you tried 5009?

Ramon R2 years ago

I have tried the port 5222 for iStartek VT600 recommended by Supported Devices, but I'll try this port 5009. Thanks!

Ramon R2 years ago

from tracker-server.log

2023-11-07 15:32:52  INFO: [T0fb05bc7: meiligao < 200.68.141.7] 24240011121141207845ff50002bbb0d0a
2023-11-07 15:32:52  INFO: [T0fb05bc7: meiligao > 200.68.141.7] 40400012121141207845ff4000013c710d0a
2023-11-07 15:33:22  INFO: [T0fb05bc7: meiligao < 200.68.141.7] 00
2023-11-07 15:35:44  INFO: [T0fb05bc7: meiligao < 200.68.141.7] 24240080121141207845ff9999633231333534352e3030302c412c323534362e373133312c4e2c31303031312e373130382c572c302e32302c3130362c3037313132332c2c2a31437c312e337c3430387c323030307c303030312c303030307c303134453030313430353342373834397c31357c304538423334374154fa0d0a

root@mail:/var/log# echo 24240080121141207845ff9999633231333534352e3030302c412c323534362e373133312c4e2c31303031312e373130382c572c302e32302c3130362c3037313132332c2c2a31437c312e337c3430387c323030307c303030312c303030307c303134453030313430353342373834397c31357c304538423334374154fa0d0a | xxd -r -p && echo ''
$$▒A xE▒▒▒c213545.000,A,2546.7131,N,10011.7108,W,0.20,106,071123,,*1C|1.3|408|2000|0001,0000|014E0014053B7849|15|0E8B347AT▒

The port recognized the protocol but still is not showing as online in the Traccar platform.

Ramon R2 years ago

It worked!

2023-11-07 15:35:44  INFO: [T0fb05bc7] id: 121141207845, time: 2023-11-07 15:35:45, lat: 25.77855, lon: -100.19518, speed: 0.2, course: 106.0

I can see the device online now. So, the port 5222 is not the correct one or the 5009 is a default for a common Chinese protocol?

Anton Tananaev2 years ago

Looks like 5222 is not the right one for your device.