Modify GT06 protocol?

Dawid6 years ago

I found the issue I think.
See https://tinyjpg.com/web/output/w9k8uuta2djmgq19a0efpmah4ymubjdf/alarm.jpg
It keeps showing low battery alarm, yet on logs it shows SOS alarm.
Logs says this:

2018-06-22 02:30:10  INFO: [8D6CFFBE] connected
2018-06-22 02:30:10 DEBUG: [8D6CFFBE: 5023 < 41.114.242.171] HEX: 78781101035873905210335630020c81002dd1660d0a
2018-06-22 02:30:10 DEBUG: [8D6CFFBE: 5023 > 41.114.242.171] HEX: 78780501002d32b20d0a
2018-06-22 02:30:11 DEBUG: [8D6CFFBE: 5023 < 41.114.242.171] HEX: 7878482c120616091b19028f0a29e1000edb2429e10036f11e29e1003b7f1a29e10036f21729e1000ed91629e1002e921529e100dc0713ff020004edb5fac92e00267549800d3e002cdede0d0a
2018-06-22 02:30:11 DEBUG: [8D6CFFBE: 5023 > 41.114.242.171] HEX: 7878052c002cdf7f0d0a
2018-06-22 02:30:11  INFO: [8D6CFFBE] id: 358739052103356, time: 2018-06-21 21:19:18, lat: -34.03980, lon: 24.91068, speed: 1.1, course: 227.0
2018-06-22 02:30:11 DEBUG: [8D6CFFBE: 5023 < 41.114.242.171] HEX: 78780a138406040002002e253a0d0a
2018-06-22 02:30:11 DEBUG: [8D6CFFBE: 5023 > 41.114.242.171] HEX: 78780513002e30040d0a
2018-06-22 02:30:11  INFO: [8D6CFFBE] id: 358739052103356, time: 2018-06-21 21:19:18, lat: -34.03980, lon: 24.91068, speed: 1.1, course: 227.0
2018-06-22 02:30:26 DEBUG: [8D6CFFBE: 5023 < 41.114.242.171] HEX: 7878482c120616091e19028f0a29e1000edb2529e10036f11c29e1000ed91929e1003b7f1629e10036f21129e100bb811029e100da990fff020004edb5fac92f00267549800d3f002fcbf00d0a
2018-06-22 02:30:26 DEBUG: [8D6CFFBE: 5023 > 41.114.242.171] HEX: 7878052c002fede40d0a
2018-06-22 02:30:26  INFO: [8D6CFFBE] id: 358739052103356, time: 2018-06-21 21:19:18, lat: -34.03980, lon: 24.91068, speed: 1.1, course: 227.0
2018-06-22 02:32:52 DEBUG: [8D6CFFBE: 5023 < 41.114.242.171] HEX: 78781219028f0a29e1000edb2406040102003054a20d0a
2018-06-22 02:32:52 DEBUG: [8D6CFFBE: 5023 > 41.114.242.171] HEX: 787805190030ba810d0a
2018-06-22 02:32:52  INFO: [8D6CFFBE] id: 358739052103356, time: 2018-06-21 21:19:18, lat: -34.03980, lon: 24.91068, speed: 1.1, course: 227.0
2018-06-22 02:33:11 DEBUG: [8D6CFFBE: 5023 < 41.114.242.171] HEX: 78780a1384060400020031cd4c0d0a
2018-06-22 02:33:11 DEBUG: [8D6CFFBE: 5023 > 41.114.242.171] HEX: 787805130031d8720d0a
2018-06-22 02:33:11  INFO: [8D6CFFBE] id: 358739052103356, time: 2018-06-21 21:19:18, lat: -34.03980, lon: 24.91068, speed: 1.1, course: 227.0
2018-06-22 02:33:27 DEBUG: [8D6CFFBE: 5023 < 41.114.242.171] HEX: 7878482c120616092119028f0a29e1000edb2529e10036f11e29e1000ed91829e1003b7f1529e10036f21329e100da9911000000000000ff020004edb5fac92e00267549800d3e00325bbf0d0a
2018-06-22 02:33:27 DEBUG: [8D6CFFBE: 5023 > 41.114.242.171] HEX: 7878052c003226800d0a
2018-06-22 02:33:27  INFO: [8D6CFFBE] id: 358739052103356, time: 2018-06-21 21:19:18, lat: -34.03980, lon: 24.91068, speed: 1.1, course: 227.0
Anton Tananaev6 years ago

Where exactly do you see SOS alarm?

Dawid6 years ago

I am speaking to someone from Concox on Skype.
According to them d3f50d0a is the SOS alarm.
I see the tracker rarely sends out d3f50d0a when I press the SOS.
Is it possible to change the low battery alarm to show as SOS also?
Not sure which part of code means low battery.
Thanks.

Anton Tananaev6 years ago

I don't see "d3f50d0a" in your log.

Dawid6 years ago

https://www.traccar.org/forums/topic/modify-gt06-protocol/#post-32044

But yes, it is not on my last log.
Problem is the tracker sends low battery alarm instead of SOS.
I only started with HEX earlier this week.
All I know is the information I get from Concox, and the bit I searched on Google.
I cannot understand which bit is the low battery alarm in HEX.
Is there any way to rename Event LowBattery Alarm?

Anton Tananaev6 years ago

You can use computed attributes to change alarm.

Dawid6 years ago
Dawid6 years ago

It seems to work.
Thank you.

Dawid6 years ago

One more question. Battery shows 6v.
Do you know the string to convert the 6v to percentage?
I assume 6 is 100%, 5 is 80%, 4 is 60%, 3 is 40%, 2 is 20% , and 1 is 0% ?