TK 905 (magnet car tracker) only sending 6 positions, then disconnects
By the way, here's the SQL output if it helps - I've selected the latest 7 messages, 6 recent and the oldest the one where there's a gap until I request for positional information:
select p.servertime, p.latitude, p.longitude, p.attributes from tc_positions p JOIN tc_devices d on p.deviceid = d.id order by p.id desc limit 7;
+---------------------+-----------+-----------+----------------------------------------------------------------------------------------------------------+
| servertime | latitude | longitude | attributes |
+---------------------+-----------+-----------+----------------------------------------------------------------------------------------------------------+
| 2020-01-28 12:04:14 | 52.401312 | -2.234308 | {"sat":5,"rssi":50,"batteryLevel":100,"steps":0,"distance":7.37,"totalDistance":1276.29,"motion":false} |
| 2020-01-28 12:03:14 | 52.40128 | -2.234213 | {"sat":5,"rssi":50,"batteryLevel":100,"steps":0,"distance":0.73,"totalDistance":1268.92,"motion":false} |
| 2020-01-28 12:03:09 | 52.401285 | -2.23422 | {"sat":5,"rssi":50,"batteryLevel":100,"steps":0,"distance":4.52,"totalDistance":1268.19,"motion":true} |
| 2020-01-28 12:02:14 | 52.401305 | -2.234278 | {"sat":5,"rssi":50,"batteryLevel":100,"steps":0,"distance":21.59,"totalDistance":1263.67,"motion":false} |
| 2020-01-28 12:01:15 | 52.40115 | -2.234087 | {"sat":5,"rssi":50,"batteryLevel":100,"steps":0,"distance":11.91,"totalDistance":1242.08,"motion":false} |
| 2020-01-28 12:00:16 | 52.4011 | -2.233932 | {"sat":4,"rssi":60,"batteryLevel":100,"steps":0,"distance":188.2,"totalDistance":1230.17,"motion":true} |
| 2020-01-28 11:38:33 | 52.402162 | -2.236088 | {"sat":6,"rssi":50,"batteryLevel":100,"steps":0,"distance":43.46,"totalDistance":1041.97,"motion":false} |
+---------------------+-----------+-----------+----------------------------------------------------------------------------------------------------------+
7 rows in set (0.01 sec)If you require further logs or information, feel free to ask.
Best,
Wulfrun
Problem solved: it turns out the device comes automatically configured to sleep after five minutes of no activity. This is the first device where I've encountered that sleep is set to on by default. Unless someone bought the device, returned it and I received the one that was sent back after someone had set it to sleep already.
For others encountering this issue, sending
Sleep[password] off... Where [password] is your password, for example 123456, will resolve the issue. I originally tried Nosleep[password], which works with a number of other trackers. I knew something was up when there was no (standard) reply of nosleep ok. That's when I turned to the internet for assistance. The other thing that roused my suspicions was that after five minutes, the updates stopped, and the manual explicitly states going to sleep for five minutes in the command to sleep but not that this was configured by default. With all previous trackers I've tested, sleep is off by default.
The problem came from the lack of documentation with the device - it didn't state how to switch sleep off; I found a more detailed manual - search for lekemi GPS Tracker User Manual For TK905 English - GTS4B on Google should give you the first result.
Dear Traccars,
I am using the TK 905 and, after some initial fumbling, by reading this thread: https://www.traccar.org/forums/topic/tk905/ and sage advice from here: https://www.traccar.org/clones/, got it working by sending the command
fix060s***n123456to the device.I am using port
5093and the identifier is showing9053120621which is the same identifier reported when I runCheck123456. If it helps, check also reportsXM_TK915_SW_6.2 2019/09/07 10:25.However, after 6 updates, the Traccar console output shows (note that I've converted all the HEX data to make it easier to understand) that it disconnects:
Is there a command I am missing to get continual updates? I have also tried
upload123456 60- same behaviour, 6 updates then disconnected.Before deciding that this is a device 'quirk' (read: manufacturer issue), I thought I'd try here any see if any of you knowledgeable Traccars could help me solve this issue.
Best,
Wulfrun