Live tracking ok, but no history on server

Maxen 3 years ago

Hi there,
I'm using a TK102 clone which is working fine on port 5036.
The tracker is connected and showing the correct position.

But if I want to check tracker history, I get the message "no data"
Screenshot here: https://ibb.co/xjxVGHB

An other TK102 running on port 5002 at the same time works fine.
I'm using the demo server #3 for my tests.

Any idea what's going wrong with the device history?

Best regards
Maxen

Anton Tananaev 3 years ago

Have you checked if the device is reporting the right time?

Maxen 3 years ago

Good hint. Tracker is currently online, but how can I see the currently reported time from the device?

Anton Tananaev 3 years ago

Configure popup to show it or click more details.

Maxen 3 years ago

Ok, I set the reporting period from 1970 to 2023 and now some events are popping up with date 2002...
I will follow your hint and try to te-time the tracker.

Will come back if it's working.
Thanks so far.

Anton Tananaev 3 years ago

If you're getting nonsense data like that, it could mean that you're not using the right port.

Maxen 3 years ago

Tracker is reporting a live time of:
Device Time
2003-01-03 00:58:09

So your suggestion is correct.
Struggling how to fix it, since I can only configure the time zone following TK102 manual...

Maxen 3 years ago

"could mean that you're not using the right port."

To be honest: I went through all the Tk102 clone ports and was so happy to finally find 5036 replying a position at all ;-)

I may try again, but I don't expect any other port to work.

Thanks so much for the right hint. Using a shifted date let me at least show the history.

Maxen 3 years ago

I went to all the known clone ports once more. (5001,5002, 5006, 5013, 5015, 5023, 5036, 5093)

The only one replying from the list at all is 5036 - With a corrupt date & time information.

So seems like my clone uses a not yet known protocol.

Nevertheless, topic understood!
Thanks again, Anton

x688399 3 years ago

Could be your tracker not taking week-roll-over into account:
https://www.cisa.gov/gps-week-number-roll-over
I guess if our device is quite old.