Data Vjoycar G28 tracker (GT06) not correct

Norberton2 years ago

I have a Vjoycar G28 tracker (protocol gt06). This tracker is listed. It works in traccar demo but not on my Synology NAS traccar (latest Synology version 4-012). The port is correct (55023 on Synology), The tracker is communicating with the server but data as time and location are not correct. I don't even recognize the ip address displayed in the tracker-server log (below). I can't translate the HEX lines because apparently it is binary data. So i can't check the data.

The next logical step for me is to try to update the traccar version but i'm stuck with this latest but slightly older Synology version. I can't install the docker solution because docker is not available for my NAS. So i'm looking for a solution to use this tracker with the traccar version i've got.

Is there any way?

Tracker-server log:

2022-07-31 13:40:29 DEBUG: [95830d8b: 55023 < 89.205.227.218] HEX: 78781101086516704027819528010c81000117340d0a
2022-07-31 13:40:30 DEBUG: [95830d8b: 55023 > 89.205.227.218] HEX: 787805010001d9dc0d0a
2022-07-31 13:40:30 DEBUG: [95830d8b: 55023 < 89.205.227.218] HEX: 78780a1304f00451010003a7500d0a
2022-07-31 13:40:30 DEBUG: [95830d8b: 55023 > 89.205.227.218] HEX: 787805130003cae30d0a
2022-07-31 13:40:31  INFO: [95830d8b] id: 865167040278195, time: 2022-02-28 02:24:00, lat: -9.35894, lon: 393.94720, course: 0.0
2022-07-31 13:40:31 DEBUG: [95830d8b: 55023 < 89.205.227.218] HEX: 79790020940a086516704027819520416474952345008931162111678881613f0004b6570d0a
2022-07-31 13:40:51 DEBUG: [95830d8b: 55023 < 89.205.227.218] HEX: 7878373416071f0b28320000cc001001010d052a441541000000000000000000000000000000000000000000000000000000000000000005db830d0a
2022-07-31 13:40:51  INFO: Position filtered by Future filters from device: 865167040278195
2022-07-31 13:41:24 DEBUG: [95830d8b: 55023 < 89.205.227.218] HEX: 7878243116071f0b2915cb059492ee007a325400140000cc0010010d052a44010000000006f5ed0d0a
2022-07-31 13:41:24 DEBUG: [95830d8b: 55023 > 89.205.227.218] HEX: 7878053100062bcd0d0a
2022-07-31 13:45:44 DEBUG: [95830d8b: 55023 < 89.205.227.218] HEX: 78780a1304f00352010007f4650d0a
2022-07-31 13:45:44 DEBUG: [95830d8b: 55023 > 89.205.227.218] HEX: 7878051300078cc70d0a
2022-07-31 13:45:44  INFO: [95830d8b] id: 865167040278195, time: 2022-02-28 02:24:00, lat: -9.35894, lon: 393.94720, course: 0.0
2022-07-31 13:45:45 DEBUG: [95830d8b: 55023 < 89.205.227.218] HEX: 79790020940a086516704027819520416474952345008931162111678881613f00087c3b0d0a
2022-07-31 13:50:56 DEBUG: [95830d8b: 55023 < 89.205.227.218] HEX: 78780a1304f0035101000938d60d0a
2022-07-31 13:50:56 DEBUG: [95830d8b: 55023 > 89.205.227.218] HEX: 78780513000965b90d0a
2022-07-31 13:50:56  INFO: [95830d8b] id: 865167040278195, time: 2022-02-28 02:24:00, lat: -9.35894, lon: 393.94720, course: 0.0
2022-07-31 13:50:57 DEBUG: [95830d8b: 55023 < 89.205.227.218] HEX: 79790020940a086516704027819520416474952345008931162111678881613f000a5f290d0a
Norberton2 years ago

After trying for days, i abandonned the idea of getting the tracker to work with the older not officially supported version of Traccar for Synology NAS. Got me another Synology NAS which supports Docker and installed the latest Traccar version. Everything works fine now.