GT06 protocol not decoded on TK206 OBDII hardware V2.0

Hello
I did set my TK206 V2.0 clone on 5023 port.
Unfortunately the protocol is not decoded.

2017-10-18 00:37:29 DEBUG: [261FE383: 5023 < 109.166.136.169] HEX: 78781f1204010100080bc004c2c34402cd77a600040000e20a006e006f7d00130dc60d0a
2017-10-18 00:37:32 DEBUG: [261FE383: 5023 < 109.166.136.169] HEX: 78781f12040101000829c004c2c34402cd77a600040000e20a006e006f7d0014d2db0d0a
2017-10-18 00:37:36 DEBUG: [261FE383: 5023 < 109.166.136.169] HEX: 78781f1204010100090bc004c2c34402cd77a600040000e20a006e006f7d001533b40d0a

I have another TK206 ODBII hardware 1.7 that has TK103 protocol running fine on 5002 port. This device has a different firmware.

Any idea why the GT06 protocol is not decoded?

Thank you.

It looks like GT06 protocol. Please provide full connection session, not just random log fragment.

Here it is:

2017-10-18 13:15:51  INFO: Operating system name: Windows 7 version: 6.1 architecture: amd64
2017-10-18 13:15:51  INFO: Java runtime name: Java HotSpot(TM) 64-Bit Server VM vendor: Oracle Corporation version: 25.144-b01
2017-10-18 13:15:51  INFO: Memory limit heap: 875mb non-heap: 0mb
2017-10-18 13:15:51  INFO: Character encoding: UTF-8 charset: UTF-8
2017-10-18 13:15:51  INFO: Version: 3.14-SNAPSHOT
2017-10-18 13:15:55  INFO: Starting server...
2017-10-18 13:16:02  INFO: [6A6C5282] connected
2017-10-18 13:16:03  INFO: [0283C27B] connected
2017-10-18 13:16:04 DEBUG: [6A6C5282: 5023 < 109.166.133.5] HEX: 78780d010352887075415723000f33890d0a
2017-10-18 13:16:04 DEBUG: [6A6C5282: 5023 > 109.166.133.5] HEX: 787805010001d9dc0d0a
2017-10-18 13:16:04 DEBUG: [0283C27B: 5023 < 109.166.138.52] HEX: 78780d010352887075416408006a44800d0a
2017-10-18 13:16:04 DEBUG: [0283C27B: 5023 > 109.166.138.52] HEX: 787805010001d9dc0d0a
2017-10-18 13:16:07 DEBUG: [6A6C5282: 5023 < 109.166.133.5] HEX: 78780a134405040000001005190d0a
2017-10-18 13:16:07 DEBUG: [6A6C5282: 5023 > 109.166.133.5] HEX: 787805130002db6a0d0a
2017-10-18 13:16:07  INFO: [6A6C5282] id: 352887075415723, time: 2017-10-18 14:01:40, lat: 22.67535, lon: 114.03920, speed: 0.0, course: 0.0
2017-10-18 13:16:07 DEBUG: [0283C27B: 5023 < 109.166.138.52] HEX: 78780a135c05040000006ba3680d0a
2017-10-18 13:16:07 DEBUG: [0283C27B: 5023 > 109.166.138.52] HEX: 787805130002db6a0d0a
2017-10-18 13:16:08  INFO: [0283C27B] id: 352887075416408, time: 2017-10-18 13:15:21, lat: 44.31099, lon: 22.56449, speed: 0.0, course: 0.0
2017-10-18 13:16:13 DEBUG: [6A6C5282: 5023 < 109.166.133.5] HEX: 78781f12110a120a1008c904c21a4602cc76fc00140000e20a006e0046ca001173ee0d0a
2017-10-18 13:16:13 DEBUG: [6A6C5282: 5023 > 109.166.133.5] HEX: 787805120003903f0d0a
2017-10-18 13:16:13  WARN: Geocoding failed - Empty address - GeocoderException (JsonGeocoder:74 < ...)
2017-10-18 13:16:13  INFO: [6A6C5282] id: 352887075415723, time: 2017-10-18 13:16:08, lat: 44.34976, lon: 26.08569, speed: 0.0, course: 0.0
2017-10-18 13:16:26 DEBUG: [0283C27B: 5023 < 109.166.138.52] HEX: 78781f12110a120a1015ca04c10991026bc09800140000e20a2e810082f5006cb16e0d0a
2017-10-18 13:16:26 DEBUG: [0283C27B: 5023 > 109.166.138.52] HEX: 787805120003903f0d0a
2017-10-18 13:16:26  WARN: Geocoding failed - Empty address - GeocoderException (JsonGeocoder:74 < ...)
2017-10-18 13:16:26  INFO: [0283C27B] id: 352887075416408, time: 2017-10-18 13:16:21, lat: 44.31098, lon: 22.56449, speed: 0.0, course: 0.0
2017-10-18 13:16:43 DEBUG: [6A6C5282: 5023 < 109.166.133.5] HEX: 78781f12110a120a1026ca04c21a7302cc772900140000e20a006e0046ca001286fc0d0a
2017-10-18 13:16:43 DEBUG: [6A6C5282: 5023 > 109.166.133.5] HEX: 787805120004e4800d0a
2017-10-18 13:16:43  INFO: [6A6C5282] id: 352887075415723, time: 2017-10-18 13:16:38, lat: 44.34979, lon: 26.08571, speed: 0.0, course: 0.0
2017-10-18 13:16:53 DEBUG: [6A6C5282: 5023 < 109.166.133.5] HEX: 78780a134405040000001337820d0a
2017-10-18 13:16:53 DEBUG: [6A6C5282: 5023 > 109.166.133.5] HEX: 787805130005afd50d0a
2017-10-18 13:16:53  INFO: [6A6C5282] id: 352887075415723, time: 2017-10-18 14:01:40, lat: 22.67535, lon: 114.03920, speed: 0.0, course: 0.0
2017-10-18 13:16:53 DEBUG: [0283C27B: 5023 < 109.166.138.52] HEX: 78780a135c05040000006dc65e0d0a
2017-10-18 13:16:53 DEBUG: [0283C27B: 5023 > 109.166.138.52] HEX: 787805130004be5c0d0a
2017-10-18 13:16:54  INFO: [0283C27B] id: 352887075416408, time: 2017-10-18 13:16:21, lat: 44.31098, lon: 22.56449, speed: 0.0, course: 0.0

It seems that for the same device 352887075415723 the decoder has two distinct locations:

2017-10-18 13:16:43 DEBUG: [6A6C5282: 5023 < 109.166.133.5] HEX: 78781f12110a120a1026ca04c21a7302cc772900140000e20a006e0046ca001286fc0d0a
2017-10-18 13:16:43 DEBUG: [6A6C5282: 5023 > 109.166.133.5] HEX: 787805120004e4800d0a
2017-10-18 13:16:43  INFO: [6A6C5282] id: 352887075415723, time: 2017-10-18 13:16:38, lat: 44.34979, lon: 26.08571, speed: 0.0, course: 0.0
2017-10-18 13:16:53 DEBUG: [6A6C5282: 5023 < 109.166.133.5] HEX: 78780a134405040000001337820d0a
2017-10-18 13:16:53 DEBUG: [6A6C5282: 5023 > 109.166.133.5] HEX: 787805130005afd50d0a
2017-10-18 13:16:53  INFO: [6A6C5282] id: 352887075415723, time: 2017-10-18 14:01:40, lat: 22.67535, lon: 114.03920, speed: 0.0, course: 0.0

How is possible?

It seems that for the same device 352887075415723 the decoder has two distinct locations:

Same problem yesterday !! with my AH207 tracker
I had 2 locations (5km in distance)

maybe this commit (https://github.com/tananaev/traccar/commit/81e6d5825615fbe0be253e500b2c997f304349e6) will fix the problem in the next release ? (I've downloaded the master branch on my server and I will check soon if it's happening again)

The problem is with time in future. It has been discussed countless number of times. Use search.

It seems that the position that has the time in the future is the gps factory position lat: 22.67535, lon: 114.03920, speed: 0.0, course: 0.0 in my case.
I will try the filter for the future time.

<entry key='filter.enable'>true</entry>
<entry key='filter.future'>86400</entry>

Here https://www.traccar.org/forums/topic/configure-gt06-timezone/page/3/ they don't use filter.future but they get rid of this problem