Have you checked other threads before posting?
not yet
It probably makes sense to check existing topics before starting a new one.
hi anton,
so sorry, i try to find with keyword "gt06 timestamp" , "gt06 error time" not relate with my problem. maybe my keyword was wrong.
I just want share information from official concox, about the problem. I hope this information is useful for everyone. thank you
Dear Customers and Partners,
Recently, our company has detected abnormal GPS-related functions in some positioning devices. After technical investigation, it has been confirmed that this issue stems from the GPS week rollover problem of the MTK 2503D chip (with a built-in MT3333 positioning chip). The specific manifestations are as follows: the positioning time resets to start from January 1, 2006, and the positioning status cannot remain stable continuously.
It should be specially noted that this issue only affects 2G locator products equipped with the aforementioned chips, and 4G locators are not affected by this problem.
In response to the above situation, our company has activated an emergency response mechanism. Our R&D team is maintaining close communication with MTK's original factory and making every effort to promote the research and testing of firmware solutions. Once the OTA firmware patch is developed, we will notify all affected users as soon as possible and provide firmware update services for the problematic terminals to fundamentally solve the issue.
While waiting for the final solution, to minimize the impact on your use, our company provides the following temporary server-side correction scheme for your reference and implementation:
Method for correcting GPS time anomalies on the server side:
Trigger condition: When the positioning timestamp (UNIX format) reported by the device is less than 1451606400 (corresponding to 00:00:00 UTC on January 1, 2016), the correction mechanism will be activated; if the reported positioning timestamp (UNIX format) is 1451606400 or greater, no processing will be performed.
Correction algorithm: Corrected timestamp = Device-reported timestamp (UNIX format) + 619315200
Correction example: The data reported by the device is 78 78 26 22 06 01 01 10 33 05
CC 02 88 E6 04 09 B5 29 66 00 15 60 00 00 00 00 00 00 00 00 00 00 01 00 00 00 00 00 04 C6 0F 0D 0A
Parsed GPS timestamp: 2006/01/01 16:51:5 (1136105465 in UNIX format) Corrected GPS timestamp (UNIX format): 1136105465 + 619315200 = 1755420665
You don't need to search. You just open the forum and you will see something like 10 topics about this:
Hi All

i got problem that gt06 protocol received error time from device gt06n concox. it was back to Januari 2006 , and check to local community someone send formal letter that said device has bug. Could traccar has solution to correcting error time from device ? i send copy of letter. thank you