We ran into a rather interesting issue:
Our FCM640 tracker was built into a car now. tracking so far is working as intended.
However, when the car stops and is idle for a while aka ignition is off then turn on ignition again and sends the next data hell breaks loose.
Timestamps differ by only a few seconds (most prominent case was 11 seconds) but the difference between the two gps points are a few kms with the last one being correct.
So basically the points in between are missing somehow.
This only happens in the scenario above.
Good day, did you check the device configuration, from the record settings kindly select Ater time sync so that records can be saved if the device already syncs its time to the NTP server or through NITZ you can also test the configuration file below:
For your reference, you can visit these links :
- Tim Synchronization FMC640 System settings - Wiki Knowledge Base | Teltonika GPS (teltonika-gps.com)
2.Record Settings FMC640 System settings - Wiki Knowledge Base | Teltonika GPS (teltonika-gps.com)
Note: If the issue goes any deeper and need further assistance from the engineers you can create a ticket through Helpdesk or contact your sales manager.
I applied your changes and so far it seems to work.
I only have one tested dataset so far and this included extremly bad connection (i sent an sms to retrieve a paramater and had to wait like 4 minutes to recieve an answer).
I got a gps coordinate like 5 kms away after but the missing points are trasmitted right now so the route gets populated still.
Still those 5kms difference seem to be a lot. Is there an option to send like the most current package and then fill up with the oldest ones?
Yes there is an option like that:
Select the Newest to prioritize sending the NEW records first followed by the OLD records.
Wiki page: FMC640 System settings - Wiki Knowledge Base | Teltonika GPS (teltonika-gps.com)