Hello,
I would like to report an issue we're experiencing with trip reports related to Coban 311 devices.
The situation is as follows:
Several vehicles equipped with Coban 311 trackers are parked overnight in an underground parking lot. We’ve noticed that the Trip Reports are not accurately reflecting the first or last trips of the day, or in some cases, they are missing entirely.
Upon reviewing the Route Report, we observed that the fixTime field remains frozen — the timestamp, latitude, longitude, and speed are repeated across multiple records without any change. This continues until the vehicle exits the underground location the next day. However, the deviceTime field is updating correctly during this period.
This behavior appears to interfere with Traccar’s trip detection logic.
Questions:
Does the system rely strictly on fixTime for generating trip reports?
Could this frozen fixTime be the cause of incomplete or missing trips?
Is there any recommended solution, configuration adjustment, or workaround to handle this scenario?
Screenshots are attached for reference.
Thank you in advance for your support.
Does the system rely strictly on fixTime for generating trip reports?
Yes.
Could this frozen fixTime be the cause of incomplete or missing trips?
Yes.
Is there any recommended solution, configuration adjustment, or workaround to handle this scenario?
Ideal solution would depend on your device capabilities.
Hello,
I would like to report an issue we're experiencing with trip reports related to Coban 311 devices.
The situation is as follows:
Several vehicles equipped with Coban 311 trackers are parked overnight in an underground parking lot. We’ve noticed that the Trip Reports are not accurately reflecting the first or last trips of the day, or in some cases, they are missing entirely.
Upon reviewing the Route Report, we observed that the fixTime field remains frozen — the timestamp, latitude, longitude, and speed are repeated across multiple records without any change. This continues until the vehicle exits the underground location the next day. However, the deviceTime field is updating correctly during this period.
This behavior appears to interfere with Traccar’s trip detection logic.
Questions:
Does the system rely strictly on fixTime for generating trip reports?
Could this frozen fixTime be the cause of incomplete or missing trips?
Is there any recommended solution, configuration adjustment, or workaround to handle this scenario?
Screenshots are attached for reference.
Thank you in advance for your support.
