Chinese GT02A tracker not sending position data

Marco Pusceddu7 years ago

Hi.
First of all, thanks for your job.
We're runnibg a Traccar server and almost everything works fine as long as we connect phones and Android devices to the server.
Now we are trying to connct a Chinese tracjer device named GT02A. After some research and attempts (I've read the article about Chinese trackers), we found that the device uses tk103 protocol on port 5002.
Traccar's web interface reports device status ok, but no location data is sent.
I already tried to activate location update by sending via SMS the commands you suggested (fixxxx..., etc.), but the device doesn't respond to these commands.
On the other hand, device status reports location sending enabled with a time interval of 15s.

Does anyone have suggestions?
Thanks.

Here are some log lines:

2018-02-24 15:42:17 DEBUG: [E419FBD3: 5002 < 5.90.158.195] HEX: 283038373037333131353939344252303031383032323441333933342e323234334e30303835342e32363638453030312e363134343231353030302e303030313030303030304c303030343530414229

2018-02-24 15:42:32 DEBUG: [E419FBD3: 5002 < 5.90.158.195] HEX: 283038373037333131353939344252303031383032323441333933342e323235364e30303835342e32363538453030322e303134343233303030302e303030313030303030304c303030343530414229

2018-02-24 15:42:47 DEBUG: [E419FBD3: 5002 < 5.90.158.195] HEX: 283038373037333131353939344252303031383032323441333933342e323237314e30303835342e32363631453030332e383134343234353030302e303030313030303030304c303030343530414229

2018-02-24 15:43:02 DEBUG: [E419FBD3: 5002 < 5.90.158.195] HEX: 28303837303733313135393934425a30302c3232322c3031302c373935372c653537662c373935372c383232622c373935372c653538312c373935372c383232612c303130303030303029

2018-02-24 15:43:17 DEBUG: [E419FBD3: 5002 < 5.90.158.195] HEX: 28303837303733313135393934425a30302c3232322c3031302c373935372c653537662c373935372c653538312c373935372c383232622c373935372c383232612c303130303030303029
Anton Tananaev7 years ago

Why did you filter out logs? Without full logs I won't be able to help you.

Marco Pusceddu7 years ago

I'm sorry. Our log is a long one. We track other devices on port 5055: I just wanted to make things easier by sending only lines containing port 5002, the one our chinese tracker is using.
The following are the last 150 unfiltered lines of our log.
Thank you for your help.

...
2018-02-24 22:43:20 DEBUG: [42E85670: 5002 < 5.90.143.172] HEX: 283038373037333131353939344252303031383032323441333933342e323331384e30303835342e32353730453030322e303231343331383030302e303030313030303030304c303030343530414229
2018-02-24 22:43:20  INFO: [42E85670] id: 087073115994, time: 2018-02-24 22:43:18, lat: 39.57053, lon: 8.90428, speed: 1.1, course: 0.0
...
Anton Tananaev7 years ago

I can see that location is decoded correctly.

Marco Pusceddu7 years ago

You're right, now it seems ok.
After the last changes it started to send location data.
I didn't notice it.
Thank you.