Does the TK905 has a store for positions?

samlinka year ago

Hello, today I noticed that my TK905, that has been operational since 2020, didn't showed up online in my traccar instance. After checking that the firewall was ok, I tried rebooting the tracker. This solved the problem, but I started receiving some very old positions.
Does this type of device store unsent positions? If yes, why it didn't sent it in the first place? The tracker has worked fine ever since the installation.

This is what the logs are writing:
2023-02-21 13:53:22 INFO: [T81a44cfa] id: [edited], time: 2019-01-01 01:00:31, lat: [edited], lon: [edited], course: 0.0

GUI View
GUI View

Some positions are older than the day I bought it, so I'm also thinking about the internal clock not being updated when it reboots.

Track-tracea year ago

How about setting the device time correctly by sending a command to your tracker ?

samlinka year ago

I never set the time for the tracker, it does automatically I think. The only command related to date is the set timezone.
When it booted up I started receiving a lot of positions, much faster than the 30 secs uplaod time I set. Almost as it stored some old data.

Track-tracea year ago

Ok, i dont know this model.

When i read here https://www.tk-star.com/download/TK905-Manual.html

there does not seem to be an option to set the time.

But i read you should be able to request the device time by sending: begin123456

Somehow the device must sync with some timeserver.

samlinka year ago

What I find strange is that I set 30sec update time on the tracker, but right after boot, in 30s, I received 10 updates:

2023-02-21 13:53:22  INFO: [T81a44cfa] id: [redacted], time: 2019-01-01 01:00:31, lat: [redacted], lon: [redacted], course: 0.0
2023-02-21 13:53:27  INFO: [T81a44cfa] id: [redacted], time: 2023-02-21 13:46:24, lat: [redacted], lon: [redacted], course: 0.0
2023-02-21 13:53:31  INFO: [T81a44cfa] id: [redacted], time: 2023-02-21 13:46:54, lat: [redacted], lon: [redacted], course: 0.0
2023-02-21 13:53:33  INFO: [T81a44cfa] id: [redacted], time: 2023-02-21 13:47:23, lat: [redacted], lon: [redacted], course: 0.0
2023-02-21 13:53:36  INFO: [T81a44cfa] id: [redacted], time: 2023-02-21 13:47:53, lat: [redacted], lon: [redacted], course: 0.0
2023-02-21 13:53:40  INFO: [T81a44cfa] id: [redacted], time: 2023-02-21 13:48:06, lat: [redacted], lon: [redacted], course: 0.0
2023-02-21 13:53:42  INFO: [T81a44cfa] id: [redacted], time: 2019-01-01 01:00:52, lat: [redacted], lon: [redacted], course: 0.0
2023-02-21 13:53:45  INFO: [T81a44cfa] id: [redacted], time: 2023-02-21 13:48:36, lat: [redacted], lon: [redacted], course: 0.0
2023-02-21 13:53:48  INFO: [T81a44cfa] id: [redacted], time: 2023-02-21 13:49:06, lat: [redacted], lon: [redacted], course: 0.0
2023-02-21 13:53:52  INFO: [T81a44cfa] id: [redacted], time: 2023-02-21 13:49:24, lat: [redacted], lon: [redacted], course: 0.0

Here some 2019 positions (line 1 and 7) are mixed with the right ones.
This is some strange behaviour from the tracker I guess.

Track-tracea year ago

How about filtering those message with past date out.

filter.past config
Filter records with fix time in the past. The value is specified in seconds. Records that have fix time more than the specified number of seconds before current server time would be filtered out.

https://www.traccar.org/configuration-file/