Hi Anton, how are you?
I have a GT06 protocol device and, this device is sending truncated position data, is this a gt06 traccar protocol bug or is a device bug ?
The start of the log is bellow, and the full log you cand download at: http://www.meuway.com/tracker-server_.rar
2018-05-07 06:14:56 INFO: Operating system name: Windows 10 version: 10.0 architecture: amd64
2018-05-07 06:14:56 INFO: Java runtime name: Java HotSpot(TM) 64-Bit Server VM vendor: Oracle Corporation version: 25.131-b11
2018-05-07 06:14:56 INFO: Memory limit heap: 1801mb non-heap: 0mb
2018-05-07 06:14:56 INFO: Character encoding: UTF-8 charset: UTF-8
2018-05-07 06:14:56 INFO: Version: 3.16-SNAPSHOT
2018-05-07 06:14:59 INFO: Starting server...
2018-05-07 07:05:21 INFO: [D78C3FEB] connected
2018-05-07 07:05:21 DEBUG: [D78C3FEB: 5023 < 177.79.224.108] HEX: 78780d010352312090194286000232800d0a
2018-05-07 07:05:21 DEBUG: [D78C3FEB: 5023 > 177.79.224.108] HEX: 787805010002eb470d0a
2018-05-07 07:06:41 DEBUG: [D78C3FEB: 5023 < 177.79.224.108] HEX: 78781f121205060c0d21c80207eb7c052e79b804181402d417561200b47000042a8b0d0a78781f121205060c0d23c80207eb50052e799005182002d417561200b470000543850d0a78781f121205060c0d25c80207eb2c052e796008183802d417561200b4700006cdb30d0a78781f121205060c0d2bc90207ea8c052e790808180c02d417561200b4700007098e0d0a78781f121205060c0d2dc90207ea54052e794808194b02d417561200b470000831e50d0a78781f121205060c0d2fc90207ea4c052e79d80e191702d417561200b470000921770d0a78781f121205060c0d31ca0207ea5c052e7a7813190802d417561200b470000a7ab30d0a78781f121205060c0d3bc90207eb2c052e7f801c190102d417561200b470000b4abc0d0a78781f121205060c0e06c80207eb78052e82c80c192802d417561200b470000c8e310d0a78781f121205060c0e08c90207eaec052e832012194502d417561200b470000d53fa0d0a78781f121205060c0e0ac90207e9d4052e83301e195e02d417561200b470000ef5b00d0a78781f121205060c0e14ca0207e530052e84180b194d02d417561200b470000f42d00d0a78781f121205060c0e16ca0207e530052e84c811191402d417561200b4710010d1060d0a78781f121205060c0e18c90207e55c052e85d01c190402d417561200b47100116cba0d0a78781f121205060c0e1eca0207e588052e88d810191602d417561200b4710012fd4b0d0a78781f121205060c0e20c90207e4f4052e891012194802d417561200b4710013eb9d0d0a78781f121205060c0e23ca0207e3f4052e89401d195c02d417561200b471001491d10d0a78781f121205060c0e2dca0207e0dc052e89e002195e02d417561200b471001582e30d0a78781f121205060c0e2eca0207e0d8052e89e000180002d417561200b4710016a20f0d0a78781f121205060c0e37ca0207e0cc052e89e004195d02d417561200b47100171db40d0a78781f121205060c0e3aca0207e03c052e89b00f181402d417561200b47100187f4c0d0a78781f121205060c0f00ca0207dfcc052e891014183402d417561200b471001917c80d0a78781f121205060c0f04ca0207df34052e889008180f02d417561200b471001aceb40d0a78781f121205060c0f06ca0207df04052e88d807193802d417561200b471001bf8650d0a78781f121205060c0f08ca0207df24052e89400d18fd02d417561200b471001c2ba10d0a78781f121205060c0f12ca0207e0f0052e8d001618f302d417561200b471001d55000d0a78781f121205060c0f18ca0207e114052e8e4805192702d417561200b471001e04f30d0a78781f121205060c0f1aca0207e0d4052e8e4807180502d417561200b471001f14170d0a78781f121205060c0f1cca0207e07805
2018-05-07 07:06:41 DEBUG: [D78C3FEB: 5023 > 177.79.224.108] HEX: 787805120004e4800d0a
2018-05-07 07:06:41 DEBUG: [D78C3FEB: 5023 > 177.79.224.108] HEX: 787805120005f5090d0a
2018-05-07 07:06:41 DEBUG: [D78C3FEB: 5023 > 177.79.224.108] HEX: 787805120006c7920d0a
2018-05-07 07:06:41 DEBUG: [D78C3FEB: 5023 > 177.79.224.108] HEX: 787805120007d61b0d0a
2018-05-07 07:06:41 DEBUG: [D78C3FEB: 5023 > 177.79.224.108] HEX: 7878051200082eec0d0a
2018-05-07 07:06:41 DEBUG: [D78C3FEB: 5023 > 177.79.224.108] HEX: 7878051200093f650d0a
I have tested it locally on the latest code and everything works perfectly.
Hi Anton, how are you?
I have a GT06 protocol device and, this device is sending truncated position data, is this a gt06 traccar protocol bug or is a device bug ?
The start of the log is bellow, and the full log you cand download at: http://www.meuway.com/tracker-server_.rar