I have a device (and yes, it's a Chinese device) that is sending in GT06 format. The type of location data it's sending is 4G LTE (protocol type 42) but it's not being recognized by Traccar. When Traccar responds to some protocol 13 messages and shows a location received, Traccar always says that it's at latitude and longitude of 0, 0 and the default date/time from 1969. The documentation for the unit has a pretty clear listing of the data format that's being sent. I'm guessing that the protocol type 42 data is not recognized or a different data layout is expected by Traccar?
Here's some of the data from the Traccar log:
2022-04-29 14:27:42 INFO: [8c71efd0: gt06 < my_ip] HEX: 7878254216041d121b28cf046ad05809218450001c00013604b9ff00685b0d0000685b0d001a000b0d0a
2022-04-29 14:27:42 INFO: [8c71efd0: gt06 > my_ip] HEX: 78780542001a9e9c0d0a
2022-04-29 14:29:43 INFO: [8c71efd0: gt06 < my_ip] HEX: 7878254216041d121d29cf046ad05809218470001c00013604b9ff00685b0d0000685b0d001b19f20d0a
2022-04-29 14:29:43 INFO: [8c71efd0: gt06 > my_ip] HEX: 78780542001b8f150d0a
2022-04-29 14:30:02 INFO: [8c71efd0: gt06 < my_ip] HEX: 78780a138006030002001c68010d0a
2022-04-29 14:30:02 INFO: [8c71efd0: gt06 > my_ip] HEX: 78780513001c22950d0a
2022-04-29 14:30:02 INFO: [8c71efd0] id: 111111111111111, time: 1969-12-31 19:00:00, lat: 0.00000, lon: 0.00000, course: 0.0
2022-04-29 14:31:44 INFO: [8c71efd0: gt06 < my_ip] HEX: 7878254216041d121f2acf046ad158092184b0001c00013604b9ff00685b0d0000685b0d001d91610d0a
2022-04-29 14:31:44 INFO: [8c71efd0: gt06 > my_ip] HEX: 78780542001dea230d0a
2022-04-29 14:33:03 INFO: [8c71efd0: gt06 < my_ip] HEX: 78780a138006030002001e4b130d0a
2022-04-29 14:33:03 INFO: [8c71efd0: gt06 > my_ip] HEX: 78780513001e01870d0a
2022-04-29 14:33:03 INFO: [8c71efd0] id: 111111111111111, time: 1969-12-31 19:00:00, lat: 0.00000, lon: 0.00000, course: 0.0
2022-04-29 14:33:44 INFO: [8c71efd0: gt06 < my_ip] HEX: 7878254216041d12212ac8046ad158092184b0001c00013604b9ff00685b0d0000685b0d001f249e0d0a
2022-04-29 14:33:44 INFO: [8c71efd0: gt06 > my_ip] HEX: 78780542001fc9310d0a
The device shows up on the Traccar map, but again always at location 0, 0. I tried it on the demo server with the same result.
The manufacturer provides a layout of the protocol as follows:
- Start bit - 2 bytes - example 0x78 0x78
- Packet length - 1 byte - example 0x20
- Protocol number - 1 byte - 0x42
- GPS info:
- Date time - 6 bytes - example 0x0B 0x08 0x1D 0x11 0x2E 0x10
- Qty of GPS Satellites - 1 byte - example 0xCF
- Latitude - 4 bytes - example 0x02 0x7A 0xC7 0xEB
- Longitude - 4 bytes - example 0x0C 0x46 0x58 0x49
- Speed - 1 byte - example 0x00
- Course, Status - 2 bytes - example 0x14 0x8F
- LBS Information:
- MCC - 2 bytes - example 0x01 0xCC
- MNC - 1 byte - example 0x00
- LAC - 2 bytes - example 0x28 0x7D
- Cell ID - 4 bytes - example 0x00 0x00 0x1F 0xB8
- Serial Number - 2 bytes - example 0x00 0x03
- Error Check - 2 bytes - example 0x80 0x81
- Stop Bit - 2 bytes - example 0x0D 0x0A
Any suggestions for next steps that can be taken with it?
Thanks!
Does it mean Gt06 protocol is not supported or??
There's a million of different GT06 variations. This specific one is not fully supported.
Anton, thanks for the answer and clarification!
Hey, I am facing same situation like get allways lat, lon 0.0000. I am using GF60 Asset Tracker device and it will working correctly few days age, but suddenly it stop working and it will working correctly on their server.
There is my config :
<entry key='event.enable'>true</entry>
<entry key='event.overspeedHandler'>true</entry>
<entry key='event.overspeed.notRepeat'>true</entry>
<entry key='event.motionHandler'>true</entry>
<entry key='event.geofenceHandler'>true</entry>
<entry key='event.alertHandler'>true</entry>
<entry key='event.ignitionHandler'>true</entry>
<entry key='event.statusHandler'>true</entry>
<entry key='event.maintenanceHandler'>true</entry>
<entry key='processing.computedAttributes.enable'>true</entry>
<entry key='processing.engineHours.enable'>true</entry>
<entry key='processing.copyAttributes.enable'>true</entry>
<entry key='processing.copyAttributes'>battery,batterylevel,ignition,hours</entry>
<entry key='geocoder.enable'>true</entry>
<entry key='geolocation.enable'>true</entry>
<entry key='time.override'>serverTime</entry>
<entry key='time.protocols'>h02</entry>
<entry key='protocols.enable'>h02</entry>
<entry key='filter.enable'>true</entry>
<entry key='filter.invalid'>true</entry>
<entry key='filter.zero'>true</entry>
<entry key='filter.duplicate'>true</entry>
<entry key='coordinates.filter'>true</entry>
<entry key='coordinates.minError'>3</entry>
<entry key='coordinates.maxError'>500</entry>
Can you please help me to setup my device
I have a device (and yes, it's a Chinese device) that is sending in GT06 format. The type of location data it's sending is 4G LTE (protocol type 42) but it's not being recognized by Traccar. When Traccar responds to some protocol 13 messages and shows a location received, Traccar always says that it's at latitude and longitude of 0, 0 and the default date/time from 1969. The documentation for the unit has a pretty clear listing of the data format that's being sent. I'm guessing that the protocol type 42 data is not recognized or a different data layout is expected by Traccar?
Here's some of the data from the Traccar log:
The device shows up on the Traccar map, but again always at location 0, 0. I tried it on the demo server with the same result.
The manufacturer provides a layout of the protocol as follows:
Any suggestions for next steps that can be taken with it?
Thanks!