The GT06 protocol supports odometer information, but not all devices include it in the message. I'm not sure about GT06N. I can check if you have some message samples.
Will this help?
2015-09-26 13:42:35 DEBUG: [9BFE66A6: 5023 < 106.208.223.42] HEX: 78780d010358899054046423027a6c060d0a
2015-09-26 13:42:35 DEBUG: [9BFE66A6: 5023 > 106.208.223.42] HEX: 78780501027a27380d0a
2015-09-26 13:42:36 DEBUG: [9BFE66A6: 5023 < 106.208.223.42] HEX: 78780a134606040002027b65020d0a
2015-09-26 13:42:36 DEBUG: [9BFE66A6: 5023 > 106.208.223.42] HEX: 78780513027b069c0d0a
2015-09-26 13:42:39 DEBUG: [9BFE66A6: 5023 < 106.208.223.42] HEX: 78781f120f091a08011ac90147b5f8089000f018d45901945e007c0047b50250512b0d0a78781f120f091a08011fc90147b5e80890036019d45b01945e007c0047b502530d080d0a78781f120f091a080124c90147b5ca089005a019d45d01945e007c0047b502547d330d0a78781f120f091a080129c90147b5ec0890080015d45801945e007c0047b50255799e0d0a78781f120f091a08012ec80147b622089009e012d45201945e00210081c702565e930d0a78781f120f091a080133c90147b68808900b6014d44a01945e00210081c7025743870d0a78781f120f091a080138c90147b72608900cf00fd44301945e00210081c7025870fa0d0a78781f120f091a080201c90147b79608900e7013d44501945e00210081c702591a3d0d0a78781f120f091a080206c90147b83e0890104015d44201945e00210081c7025ac47e0d0a78781f120f091a08020bc90147b90e089012301ad44001945e00210081c7025bbba70d0a
2015-09-26 13:42:39 DEBUG: [9BFE66A6: 5023 > 106.208.223.42] HEX: 787805120250c3910d0a
2015-09-26 13:42:39 INFO: [9BFE66A6] id: 3, time: Sat Sep 26 13:31:26 IST 2015, lat: 11.931586666666666, lon: 79.80841777777778, speed: 12.958968, course: 89.0
2015-09-26 13:42:39 DEBUG: [9BFE66A6: 5023 > 106.208.223.42] HEX: 787805120253f10a0d0a
2015-09-26 13:42:39 INFO: [9BFE66A6] id: 3, time: Sat Sep 26 13:31:31 IST 2015, lat: 11.931577777777777, lon: 79.80876444444445, speed: 13.498925, course: 91.0
2015-09-26 13:42:39 DEBUG: [9BFE66A6: 5023 > 106.208.223.42] HEX: 78780512025485b50d0a
2015-09-26 13:42:39 INFO: [9BFE66A6] id: 3, time: Sat Sep 26 13:31:36 IST 2015, lat: 11.931561111111112, lon: 79.80908444444445, speed: 13.498925, course: 93.0
2015-09-26 13:42:39 DEBUG: [9BFE66A6: 5023 > 106.208.223.42] HEX: 787805120255943c0d0a
2015-09-26 13:42:39 INFO: [9BFE66A6] id: 3, time: Sat Sep 26 13:31:41 IST 2015, lat: 11.93158, lon: 79.80942222222222, speed: 11.339097, course: 88.0
2015-09-26 13:42:39 DEBUG: [9BFE66A6: 5023 > 106.208.223.42] HEX: 787805120256a6a70d0a
2015-09-26 13:42:39 INFO: [9BFE66A6] id: 3, time: Sat Sep 26 13:31:46 IST 2015, lat: 11.93161, lon: 79.80968888888889, speed: 9.719226, course: 82.0
2015-09-26 13:42:39 DEBUG: [9BFE66A6: 5023 > 106.208.223.42] HEX: 787805120257b72e0d0a
2015-09-26 13:42:39 INFO: [9BFE66A6] id: 3, time: Sat Sep 26 13:31:51 IST 2015, lat: 11.931666666666667, lon: 79.80990222222222, speed: 10.799140000000001, course: 74.0
2015-09-26 13:42:39 DEBUG: [9BFE66A6: 5023 > 106.208.223.42] HEX: 7878051202584fd90d0a
2015-09-26 13:42:39 INFO: [9BFE66A6] id: 3, time: Sat Sep 26 13:31:56 IST 2015, lat: 11.931754444444444, lon: 79.81012444444444, speed: 8.099355000000001, course: 67.0
2015-09-26 13:42:39 DEBUG: [9BFE66A6: 5023 > 106.208.223.42] HEX: 7878051202595e500d0a
2015-09-26 13:42:40 INFO: [9BFE66A6] id: 3, time: Sat Sep 26 13:32:01 IST 2015, lat: 11.931816666666666, lon: 79.81033777777778, speed: 10.259183, course: 69.0
2015-09-26 13:42:40 DEBUG: [9BFE66A6: 5023 > 106.208.223.42] HEX: 78780512025a6ccb0d0a
2015-09-26 13:42:40 INFO: [9BFE66A6] id: 3, time: Sat Sep 26 13:32:06 IST 2015, lat: 11.93191, lon: 79.81059555555555, speed: 11.339097, course: 66.0
2015-09-26 13:42:40 DEBUG: [9BFE66A6: 5023 > 106.208.223.42] HEX: 78780512025b7d420d0a
2015-09-26 13:42:40 INFO: [9BFE66A6] id: 3, time: Sat Sep 26 13:32:11 IST 2015, lat: 11.932025555555555, lon: 79.81087111111111, speed: 14.038882000000001, course: 64.0
2015-09-26 13:42:42 DEBUG: [9BFE66A6: 5023 < 106.208.223.42] HEX: 78781f120f091a080210c90147b9e20890142015d44001945e00210081c7025c1bb80d0a78781f120f091a080215c90147bab2089015b011d43401945e00210081c7025d33bc0d0a78781f120f091a08021ac90147bb840890167009d42a01945e00210081c7025e1a310d0a78781f120f091a08021fc90147bbf2089016c008d42c01945e00210081c7025f63e40d0a78781f120f091a080224c90147bcda089017b011d42d01945e00210081c702609fca0d0a78781f120f091a080229c90147bdea0890191015d43101945e00210081c7026191b90d0a78781f120f091a08022ec90147bf8a08901b5022d43101945e00210081c702622be50d0a78781f120f091a080233c90147c15a08901d701ad42f01945e00210081c70263dc4d0d0a78781f120f091a080238c90147c2aa08901ed00dd42c01945e00210081c5026446790d0a78781f120f091a080301c90147c36c08901f7010d42c01945e00210081c50265579b0d0a
2015-09-26 13:42:42 DEBUG: [9BFE66A6: 5023 > 106.208.223.42] HEX: 78780512025c09fd0d0a
2015-09-26 13:42:42 INFO: [9BFE66A6] id: 3, time: Sat Sep 26 13:32:16 IST 2015, lat: 11.932143333333334, lon: 79.81114666666667, speed: 11.339097, course: 64.0
2015-09-26 13:42:42 DEBUG: [9BFE66A6: 5023 > 106.208.223.42] HEX: 78780512025d18740d0a
2015-09-26 13:42:42 INFO: [9BFE66A6] id: 3, time: Sat Sep 26 13:32:21 IST 2015, lat: 11.932258888888889, lon: 79.8113688888889, speed: 9.179269, course: 52.0
2015-09-26 13:42:42 DEBUG: [9BFE66A6: 5023 > 106.208.223.42] HEX: 78780512025e2aef0d0a
2015-09-26 13:42:42 INFO: [9BFE66A6] id: 3, time: Sat Sep 26 13:32:26 IST 2015, lat: 11.932375555555556, lon: 79.81147555555556, speed: 4.859613, course: 42.0
2015-09-26 13:42:42 DEBUG: [9BFE66A6: 5023 > 106.208.223.42] HEX: 78780512025f3b660d0a
As far as I can tell your device doesn't send odometer information.
I tried decoding on the traccar decoder link however Unable to get a clear ouptut there its junk.
Could you please spare a moment to check if this message from log contains any valuable info to check if odometer value is being sent?
78781f120f0a02000223cb020becf007d1a7b035d53001950f3ac100a625204db4d40d0a78781f120f0a02000228cb020befb407d1a39037d53001950f3ac100a625204e783f0d0a78781f120f0a0200022dcb020bf27807d19f103bd52901950f3ac100a625204f26590d0a78781f120f0a02000232cb020bf40807d19a2038d51401950f3acb0059ed205062540d0a78781f120f0a02000237cb020bf35007d195203ad4fb01950f3acb0059ed205168730d0a78781f120f0a02000300cb020bf0f407d18ff83dd4f501950f3acb0059ed205229e50d0a78781f120f0a02000305cb020beebc07d18b103ad4f501950f3acb0059ed2053b1f40d0a78781f120f0a0200030acb020beca007d186483ad4f501950f3acb0059ed205499dd0d0a78781f120f0a0200030fcb020bea6807d181a833d4f201950f3acb0052d120550fa30d0a78781f120f0a02000314cb020be84c07d17d7834d4f401950f3acb0052d12056e1260d0a
or the one below
78781f120f0a02000319cb020be67407d179682dd4f601950f3acb0052d1205722730d0a78781f120f0a0200031ecb020be4e007d175482fd4f801950f3acb0052d120595f1e0d0a78781f120f0a02000323cb020be30c07d1710835d4f501950f3acb0052d2205bc0eb0d0a78781f120f0a02000328cb020be0f007d16c303dd4f501950f3acb0052d2205c8ede0d0a
GT06 protocol is binary, so there is no easy way to convert it to human-readable format.
No, unfortunately there is still no odometer value as far as I can tell.
In which table can I find the odometer values?
I've look in the positions-table, but there is no odometer or attribute column.
Thanks
Thomas
It should be in attributes column. If you don't have attributes column, it means that you are not using official version of Traccar... or possibly you are using very outdated version.
Dear Anton,
does Gt06n by any chance send odometer value?
Also if not, A feature that can be added into Traccar Server is.
Odometer update (right in the device table) an additional column. (This will be really great i believe)