Modify GT06 protocol?
Is it not working out of the box? If not, please provide HEX message samples from Traccar logs and protocol documentation.
The tracker connects, but the LBS is causing issues.
I need the tracker to support LBS and GPS, but the LBS shows about 200km away.
Will send logs soon.
I want to try changing to gt06.Alternative , but I am not sure which file to modify.
Or of the file location.
That parameter won't help you. It's only for commands from server to device.
There is the protocol documentation
Is that any help?
Possibly, but I still need logs.
For some reason the SOS only works with GPS signal. It will not pick up with LBS
Spoke to them now.
Apparently packet 19 needs to be integrated into the GT06 protocol.
Not sure what that means.
There are no message types 19 in your log, which means that your device doesn't send it.
2018-06-21 23:27:49 DEBUG: [AF226705: 5023 < 41.114.209.66] HEX: 797900a59404414c4d313d34353b414c4d323d34353b414c4d333d35353b535441313d34303b4459443d30313b534f533d303631323033363532312c2c3b43454e5445523d3b46454e43453d46656e63652c4f46462c302c302e3030303030302c302e3030303030302c3330302c494e206f72204f55542c303b49434349443d38393237303030303035313637323736323430463b4d4f44453d4d4f44452c312c3138303b00084cb00d0a
2018-06-21 23:27:50 DEBUG: [AF226705: 5023 < 41.114.209.66] HEX: 78781219028f0a29e1000edb20060201020009ac0e0d0a
2018-06-21 23:27:50 DEBUG: [AF226705: 5023 > 41.114.209.66] HEX: 78780519000916c30d0a
2018-06-21 23:27:50 INFO: [AF226705] id: 358739052103356, time: 2018-06-21 21:19:18, lat: -34.03980, lon: 24.91068, speed: 1.1, course: 227.0
2018-06-21 23:28:18 DEBUG: [AF226705: 5023 < 41.114.209.66] HEX: 78781219028f0a29e1000edb2006030102000a95d10d0a
2018-06-21 23:28:18 DEBUG: [AF226705: 5023 > 41.114.209.66] HEX: 78780519000a24580d0a
2018-06-21 23:28:18 INFO: [AF226705] id: 358739052103356, time: 2018-06-21 21:19:18, lat: -34.03980, lon: 24.91068, speed: 1.1, course: 227.0
2018-06-21 23:29:48 DEBUG: [AF226705: 5023 < 41.114.209.66] HEX: 78780a138006020002000b077b0d0a
2018-06-21 23:29:48 DEBUG: [AF226705: 5023 > 41.114.209.66] HEX: 78780513000b46ab0d0a
2018-06-21 23:29:48 INFO: [AF226705] id: 358739052103356, time: 2018-06-21 21:19:18, lat: -34.03980, lon: 24.91068, speed: 1.1, course: 227.0
2018-06-21 23:29:51 DEBUG: [AF226705: 5023 < 41.114.209.66] HEX: 7878482c120616061d33028f0a29e1000edb1129e100da991829e10036f11729e1000ed913000000000000000000000000000000000000ff0200267549800d410004edb5fac94f000cb07e0d0a
2018-06-21 23:29:51 DEBUG: [AF226705: 5023 > 41.114.209.66] HEX: 7878052c000cfe7d0d0a
2018-06-21 23:29:51 INFO: [AF226705] id: 358739052103356, time: 2018-06-21 21:19:18, lat: -34.03980, lon: 24.91068, speed: 1.1, course: 227.0
2018-06-21 23:30:13 DEBUG: [AF226705: 5023 < 41.114.209.66] HEX: 78781219028f0a29e1000edb2006030102000de16e0d0a
2018-06-21 23:30:13 DEBUG: [AF226705: 5023 > 41.114.209.66] HEX: 78780519000d50e70d0a
2018-06-21 23:30:13 INFO: [AF226705] id: 358739052103356, time: 2018-06-21 21:19:18, lat: -34.03980, lon: 24.91068, speed: 1.1, course: 227.0
2018-06-21 23:31:51 DEBUG: [AF226705: 5023 < 41.114.209.66] HEX: 78781219028f0a29e1000edb2006030102000ed3f50d0a
2018-06-21 23:31:51 DEBUG: [AF226705: 5023 > 41.114.209.66] HEX: 78780519000e627c0d0a
2018-06-21 23:31:51 INFO: [AF226705] id: 358739052103356, time: 2018-06-21 21:19:18, lat: -34.03980, lon: 24.91068, speed: 1.1, course: 227.0
I think that might help?
The hex there does not decode on traccar decoder.
From the log it looks like all those messages are decoded.
I will send a full log soon.
Unfortunately I do not understand the logs well.
Hi, I want to filter out low battery alarm also.
Can I use:
<entry key='filter.skipAlarm'>true</entry>
Or is there a different code I must use?
Thanks
Hi,
I purchased some of these: http://www.iconcox.com/products/q2-mini-portable-gps-tracker.html
According to them there needs to be modifications made to the GT06 protocol.
They sent me a documentation pdf, but I am not sure how to do it.
Anyone know how I can do this?
Thanks.