GT06 Protocol help

Hi, I have a chinese clone gps device which uses binary data. Based on my search in the forums i have configured the device to send the data to traccar server (3.14) on port 5023, randomly i see that the device is detected as unknown device; however the imei of the device was parsed correctly. Based on whcih i assumed it should work fine. i added the device in traccar ui; after which the device remains offline even after i am receiving messages in tracker.log. sometimes after a device reboot the device comes online but no gps co-ordinates are received (tested this for 24 hours while on the way to home and back to office). Device has been set on 1 min updates.
i have the protocol document from the manufacturer. can you help or suggest the next step we can take to have these devices integrated with traccar.

Please provide protocol documentation and HEX message samples from your server.

Hi,

hex messages as follows

2017-10-09 15:22:45  INFO: [BCA6A0A4] connected
2017-10-09 15:22:45 DEBUG: [BCA6A0A4: 5023 < 110.224.38.31] HEX: 78780d010359339075604960300d0a
2017-10-09 15:22:58 DEBUG: [BCA6A0A4: 5023 < 110.224.38.31] HEX: 787801080d0a
2017-10-09 15:22:58 DEBUG: [BCA6A0A4: 5023 > 110.224.38.31] HEX: 787805010001d9dc0d0a
2017-10-09 15:22:59 DEBUG: [BCA6A0A4: 5023 < 110.224.38.31] HEX: 787801570d0a
2017-10-09 15:23:10 DEBUG: [BCA6A0A4: 5023 < 110.224.38.31] HEX: 787801300d0a
2017-10-09 15:23:20 DEBUG: [BCA6A0A4: 5023 < 110.224.38.31] HEX: 7878071340300819640d0a

document shared using dropbox link

https://www.dropbox.com/s/8o545eoya8l4e2y/ZhongXun%20Topin%20Locator%20Communication%20Protocol.pdf?dl=0

Some more hex messages; might help

2017-10-09 15:22:45  INFO: [BCA6A0A4] connected
2017-10-09 15:22:45 DEBUG: [BCA6A0A4: 5023 < 110.224.38.31] HEX: 78780d010359339075604960300d0a
2017-10-09 15:22:58 DEBUG: [BCA6A0A4: 5023 < 110.224.38.31] HEX: 787801080d0a
2017-10-09 15:22:58 DEBUG: [BCA6A0A4: 5023 > 110.224.38.31] HEX: 787805010001d9dc0d0a
2017-10-09 15:22:59 DEBUG: [BCA6A0A4: 5023 < 110.224.38.31] HEX: 787801570d0a
2017-10-09 15:23:10 DEBUG: [BCA6A0A4: 5023 < 110.224.38.31] HEX: 787801300d0a
2017-10-09 15:23:20 DEBUG: [BCA6A0A4: 5023 < 110.224.38.31] HEX: 7878071340300819640d0a
2017-10-09 15:23:40 DEBUG: [BCA6A0A4: 5023 < 110.224.38.31] HEX: 78780469171009095338d4ca6de221bd23109add8ce73d22c83a3554559054c8d3a331d45c590501945c056714513c056714535a0567878d5a04b23a1a5a056714525a0d0a
2017-10-09 15:25:40  INFO: [E589717B] connected
2017-10-09 15:25:40 DEBUG: [E589717B: 5023 < 106.209.149.54] HEX: 78780d010359339075604960300d0a
2017-10-09 15:26:18 DEBUG: [E589717B: 5023 < 106.209.149.54] HEX: 78780469171009095617d4ca6de221bd24109add8ce73d20c83a3554559055c8d3a331d45c5a0701945c056714514604b24f2f50056714535a056714525a04b24f315a0567b1005a04b24f305a0d0a
2017-10-09 15:26:18 DEBUG: [E589717B: 5023 > 106.209.149.54] HEX: 787805010001d9dc0d0a
2017-10-09 15:26:19 DEBUG: [E589717B: 5023 < 106.209.149.54] HEX: 787801570d0a
2017-10-09 15:26:31 DEBUG: [E589717B: 5023 < 106.209.149.54] HEX: 787801300d0a
2017-10-09 15:26:40 DEBUG: [E589717B: 5023 < 106.209.149.54] HEX: 7878071341300819640d0a
2017-10-09 15:26:52 DEBUG: [E589717B: 5023 < 106.209.149.54] HEX: 78780417171009095517d4ca6de221bd24c8d3a331d45c59c83a3554559056109add8ce73d210601945c0567145146056714514605671451460567145146056714514605671451460d0a
2017-10-09 15:27:22 DEBUG: [E589717B: 5023 < 106.209.149.54] HEX: 78780369171009095717d4ca6de221bd22109add8ce73d21c8d3a331d45c5b0601945c056714513c05671453500567878d5a04b24f315a056714525a0567b1005a0d0a
2017-10-09 15:27:55 DEBUG: [E589717B: 5023 < 106.209.149.54] HEX: 787801080d0a
2017-10-09 15:30:56 DEBUG: [E589717B: 5023 < 106.209.149.54] HEX: 787801080d0a
2017-10-09 15:33:57 DEBUG: [E589717B: 5023 < 106.209.149.54] HEX: 787801080d0a

There are some problems with message length field. There is already a workaround available on GitHub. You can wait for next release or build from source.

Understood; many thanks for the guidance and support. by any chance can you update when is the next release expected; this will help us take a call to build from source or wait for the next build.

Probably in about a month.

Thank you so much for the information; this will help us plan accordingly.