GPS location does not update

Universal Track 21 days ago

Title: GT06 device connects but GPS location does not update – Traccar 6.16.0

Hello Traccar team,

I am using Traccar version 6.16.0 with a GT06 GPS tracker.

The device connects successfully and sends packets every 5 minutes, but its location is not updating. Traccar keeps reporting the same old position and timestamp.

Device details:

  • Protocol: GT06
  • Device ID / IMEI: `8699250xxxxxxxxx
  • Traccar version: 6.16.0
  • Server timezone: Asia/Kolkata

Repeated position log:

id: 869925075267805
time: 2026-10-17 22:09:38
lat: 26.21645
lon: 85.28920
course: 0.0

Received packets:

78780a1304060400020049b49e0d0a
79790008940004e3004b62df0d0a

These packets continue arriving, but the reported GPS timestamp and coordinates remain unchanged.

Could someone help me identify these packets and explain why the device is not sending updated GPS positions? Is this a tracker configuration issue or a GT06 protocol compatibility issue in Traccar 6.16.0?

I can provide additional debug logs if needed.

Thank you.

Anton Tananaev 21 days ago

Your device is not sending any location data.

Universal Track 21 days ago

Thank you for your reply.

Here are the exact logs from my GT06 device connected to Traccar 6.16.0.

Device ID: 8699250xxxxxxxx

1. Repeated position logs:

2026-10-18 01:00:09 INFO: [T033df11b] id: xxxxxxxxxxxxxxx, time: 2026-10-17 22:09:38, lat: 26.21645, lon: 85.28920, course: 0.0
2026-10-18 01:05:06 INFO: [T033df11b] id: xxxxxxxxxxxxxxx, time: 2026-10-17 22:09:38, lat: 26.21645, lon: 85.28920, course: 0.0
2026-10-18 01:10:09 INFO: [T033df11b] id: xxxxxxxxxxxxxxx, time: 2026-10-17 22:09:38, lat: 26.21645, lon: 85.28920, course: 0.0
2026-10-18 01:15:06 INFO: [T033df11b] id: xxxxxxxxxxxxxxx, time: 2026-10-17 22:09:38, lat: 26.21645, lon: 85.28920, course: 0.0
2026-10-18 01:20:09 INFO: [T033df11b] id: xxxxxxxxxxxxxxx, time: 2026-10-17 22:09:38, lat: 26.21645, lon: 85.28920, course: 0.0
2026-10-18 01:25:06 INFO: [T033df11b] id: xxxxxxxxxxxxxxx, time: 2026-10-17 22:09:38, lat: 26.21645, lon: 85.28920, course: 0.0
2026-10-18 01:30:09 INFO: [T033df11b] id: xxxxxxxxxxxxxxx, time: 2026-10-17 22:09:38, lat: 26.21645, lon: 85.28920, course: 0.0
2026-10-18 01:35:06 INFO: [T033df11b] id: xxxxxxxxxxxxxxx, time: 2026-10-17 22:09:38, lat: 26.21645, lon: 85.28920, course: 0.0
2026-10-18 01:40:09 INFO: [T033df11b] id: xxxxxxxxxxxxxxx, time: 2026-10-17 22:09:38, lat: 26.21645, lon: 85.28920, course: 0.0
2026-10-18 01:45:06 INFO: [T033df11b] id: xxxxxxxxxxxxxxx, time: 2026-10-17 22:09:38, lat: 26.21645, lon: 85.28920, course: 0.0

2. Exact packets received from the device:

2026-10-18 01:30:06 INFO: [T033df11b: gt06 < 106.222.240.82] 79790008940004e3004850440d0a
2026-10-18 01:35:03 INFO: [T033df11b: gt06 < 106.222.240.82] 78780a1304060400020049b49e0d0a
2026-10-18 01:40:03 INFO: [T033df11b: gt06 < 106.222.240.82] 78780a130406040002004a86050d0a
2026-10-18 01:40:06 INFO: [T033df11b: gt06 < 106.222.240.82] 79790008940004e3004b62df0d0a
2026-10-18 01:45:03 INFO: [T033df11b: gt06 < 106.222.240.82] 78780a130406040002004ce3330d0a

The device continues connecting and sending packets, but Traccar keeps reporting the same coordinates and old GPS timestamp.

Could you please confirm whether these packets contain GPS location data? If not, is there a way to determine why the tracker is not sending location packets?

Thank you for your help.

Anton Tananaev 21 days ago

Your device is not sending any location data!!!

Universal Track 21 days ago

I understand. The device is connected and sending data packets every 5 minutes, but no new GPS location is being received.

Could you please help me identify the packets and confirm whether the tracker is sending only heartbeat/status data? How can I troubleshoot this issue further?

Thank you.

Universal Track 20 days ago

I am experiencing a GPS tracking issue with a new batch of Concox V5 devices.

I have installed and used thousands of GPS tracking devices. Our older devices continue to work correctly in the same vehicles and installation locations, including areas with extensive vehicle wiring. However, the newly supplied Concox V5 devices exhibit the following behavior:

  • When the vehicle is stationary, the GPS location becomes FIXED.
  • When the vehicle starts moving, the GPS location becomes UNFIXED after approximately 10–20 seconds.
  • When the device is taken outside the vehicle, GPS FIX is acquired again.
  • When the device is placed near the windshield, GPS FIX is available.
  • When installed inside the dashboard, the problem occurs again.
  • The older devices work correctly under the same conditions.

This issue appears to be associated with the new batch, but I would like to investigate it further rather than assume the cause.

Full Traccar Server Logs

The device identifier has been replaced with xxxxxx for privacy. All timestamps, coordinates, speeds, courses, events, and log messages are retained as provided.

2026-10-19 21:18:15  INFO: [Tb28adf28] id: xxxxxx, time: 2026-10-19 21:16:19, lat: 26.21966, lon: 85.21307, speed: 31.3, course: 314.0
2026-10-19 21:19:31  INFO: Position filtered by Duplicate filters from device: xxxxxx
2026-10-19 21:19:35  INFO: Position filtered by Invalid filters from device: xxxxxx
2026-10-19 21:19:41  INFO: Position filtered by Invalid filters from device: xxxxxx
2026-10-19 21:20:11  INFO: Event id: xxxxxx, time: 2026-10-19 21:20:07, type: ignitionOff, notifications: 2
2026-10-19 21:20:11  INFO: [Tb28adf28] id: xxxxxx, time: 2026-10-19 21:20:07, lat: 26.22623, lon: 85.19713, course: 128.0
2026-10-19 21:20:37  INFO: [Tb28adf28] id: xxxxxx, time: 2026-10-19 21:20:33, lat: 26.22624, lon: 85.19713, course: 128.0
2026-10-19 21:24:31  INFO: [Tb28adf28] id: xxxxxx, time: 2026-10-19 21:20:33, lat: 26.22624, lon: 85.19713, course: 128.0
2026-10-19 21:25:52  INFO: [Tb28adf28] id: xxxxxx, time: 2026-10-19 21:20:33, lat: 26.22624, lon: 85.19713, course: 128.0
2026-10-19 21:29:31  INFO: [Tb28adf28] id: xxxxxx, time: 2026-10-19 21:20:33, lat: 26.22624, lon: 85.19713, course: 128.0
2026-10-19 21:34:31  INFO: Position filtered by Duplicate filters from device: xxxxxx
2026-10-19 21:35:51  INFO: [Tb28adf28] id: xxxxxx, time: 2026-10-19 21:20:33, lat: 26.22624, lon: 85.19713, course: 128.0
2026-10-19 21:39:31  INFO: [Tb28adf28] id: xxxxxx, time: 2026-10-19 21:20:33, lat: 26.22624, lon: 85.19713, course: 128.0
2026-10-19 21:44:31  INFO: Position filtered by Duplicate filters from device: xxxxxx
2026-10-19 21:45:02  INFO: Position filtered by Duplicate filters from device: xxxxxx
2026-10-19 21:45:05  INFO: Position filtered by Invalid filters from device: xxxxxx
2026-10-19 21:45:12  INFO: Position filtered by Invalid filters from device: xxxxxx
2026-10-19 21:45:51  INFO: [Tb28adf28] id: xxxxxx, time: 2026-10-19 21:20:33, lat: 26.22624, lon: 85.19713, course: 128.0
2026-10-19 21:48:02  INFO: Event id: xxxxxx, time: 2026-10-19 21:47:59, type: ignitionOn, notifications: 2
2026-10-19 21:48:02  INFO: [Tb28adf28] id: xxxxxx, time: 2026-10-19 21:20:33, lat: 26.22624, lon: 85.19713, course: 128.0
2026-10-19 21:51:02  INFO: Position filtered by Duplicate filters from device: xxxxxx
2026-10-19 21:54:03  INFO: Position filtered by Duplicate filters from device: xxxxxx
2026-10-19 21:55:51  INFO: [Tb28adf28] id: xxxxxx, time: 2026-10-19 21:20:33, lat: 26.22624, lon: 85.19713, course: 128.0
2026-10-19 21:57:02  INFO: [Tb28adf28] id: xxxxxx, time: 2026-10-19 21:20:33, lat: 26.22624, lon: 85.19713, course: 128.0
2026-10-19 21:58:35  INFO: Position filtered by Duplicate filters from device: xxxxxx
2026-10-19 21:58:39  INFO: Position filtered by Invalid filters from device: xxxxxx
2026-10-19 21:58:45  INFO: Position filtered by Invalid filters from device: xxxxxx
2026-10-19 21:59:25  INFO: Event id: xxxxxx, time: 2026-10-19 21:59:21, type: ignitionOff, notifications: 2
2026-10-19 21:59:25  INFO: [Tb28adf28] id: xxxxxx, time: 2026-10-19 21:59:21, lat: 26.20061, lon: 85.18405, course: 0.0
2026-10-19 22:03:35  INFO: [Tb28adf28] id: xxxxxx, time: 2026-10-19 21:59:21, lat: 26.20061, lon: 85.18405, course: 0.0
2026-10-19 22:05:52  INFO: [Tb28adf28] id: xxxxxx, time: 2026-10-19 21:59:21, lat: 26.20061, lon: 85.18405, course: 0.0
2026-10-19 22:08:35  INFO: [Tb28adf28] id: xxxxxx, time: 2026-10-19 21:59:21, lat: 26.20061, lon: 85.18405, course: 0.0

Questions for the Traccar Community

  1. Why do the new Concox V5 devices appear to lose GPS fix when the vehicle starts moving but regain it when the vehicle is stationary or when the device is taken outside the vehicle?
  2. Could this behavior be related to GPS receiver sensitivity, internal antenna performance, firmware, or a hardware revision in the new batch?
  3. What do the Duplicate and Invalid filter messages indicate in this case?
  4. How can I determine whether the tracker is actually losing GPS fix or repeatedly sending stale GPS positions?
  5. Which additional Traccar DEBUG logs or raw protocol packets should I collect to identify the root cause?

The same installation locations work correctly with our older devices. I would appreciate any technical guidance to help identify the cause.

Thank you.

Deepak Kumar Mahto 17 days ago

Look closely at your server logs:
INFO: Position filtered by Invalid filters from device: xxxxxx

This is why your map is not updating when the vehicle moves!

Here is what is happening:

  1. When the vehicle is stationary, the GPS antenna manages to get a solid satellite lock (valid = true).
  2. As soon as the vehicle starts moving inside the dashboard, vehicle alternator noise and dashboard framing cause the satellite count or HDOP to degrade slightly.
  3. The new Concox V5 batch sends the position packet with valid = false (GPS unfixed).
  4. Because your traccar.xml has <entry key='filter.invalid'>true</entry>, Traccar silently drops every single moving packet!

How to fix it:

A. Server-side fix:
In your traccar.xml, change or remove the invalid filter:
<entry key='filter.invalid'>false</entry>
This will allow Traccar to record the position even if the GPS receiver reports an approximate or unfixed state, instead of throwing it away.

B. Hardware installation fix:
The newer Concox V5 batches use a smaller ceramic patch antenna with lower dB gain than older models. Make sure the side with "THIS SIDE FACE SKY" is strictly facing upwards toward the windshield plastic, away from thick wiring harnesses and metal support beams that cause RF interference when the alternator is running.