SOS loop from GT06 device

Hi everybody, I am using with a ZX612 tracker a typical GT06 protocol device with which I am running into a problem. While the device updates OK in the traccar server (v4.9) i get every 2 minutes a SOS email from this device and have no idea how to stop this. Is this a device problem or a protocol problem?
Here is the raw data from this that is logged:

2020-07-09 15:18:36  INFO: [4831779c: gt06 < 89.204.155.157] HEX: 787801080d0a
2020-07-09 15:18:36  INFO: [4831779c: gt06 > 89.204.155.157] HEX: 78780508787895800d0a
2020-07-09 15:18:56  INFO: [4831779c: gt06 < 89.204.155.157] HEX: 7878151114070909240c9705859a5f00d55d5a0d3547007d000d0a
2020-07-09 15:18:56  INFO: [4831779c: gt06 > 89.204.155.157] HEX: 78780511470046ae0d0a
2020-07-09 15:18:56  INFO: [4831779c] id: 359339075033589, time: 2020-07-09 14:09:59, lat: 51.47916, lon: 7.76419, speed: 1.6, course: 0.0
2020-07-09 15:19:25  INFO: [4831779c: gt06 < 89.204.155.157] HEX: 7878071364460819410d0a
2020-07-09 15:19:25  INFO: [4831779c: gt06 > 89.204.155.157] HEX: 78780513460866860d0a
2020-07-09 15:19:25  INFO: [4831779c] id: 359339075033589, time: 2020-07-09 14:09:59, lat: 51.47916, lon: 7.76419, speed: 1.6, course: 0.0
2020-07-09 15:19:45  INFO: [4831779c: gt06 < 89.204.155.157] HEX: 7878151114070909240c9705859a5f00d55d5a0d3547007d000d0a
2020-07-09 15:19:45  INFO: [4831779c: gt06 > 89.204.155.157] HEX: 78780511470046ae0d0a
2020-07-09 15:19:45  INFO: [4831779c] id: 359339075033589, time: 2020-07-09 14:09:59, lat: 51.47916, lon: 7.76419, speed: 1.6, course: 0.0
2020-07-09 15:20:35  INFO: [4831779c: gt06 < 89.204.155.157] HEX: 787801080d0a
2020-07-09 15:20:35  INFO: [4831779c: gt06 > 89.204.155.157] HEX: 78780508787895800d0a
2020-07-09 15:20:59  INFO: [4831779c: gt06 < 89.204.155.157] HEX: 7878151114070909240c9705859a5f00d55d5a0d3547007d000d0a
2020-07-09 15:20:59  INFO: [4831779c: gt06 > 89.204.155.157] HEX: 78780511470046ae0d0a
2020-07-09 15:20:59  INFO: [4831779c] id: 359339075033589, time: 2020-07-09 14:09:59, lat: 51.47916, lon: 7.76419, speed: 1.6, course: 0.0
2020-07-09 15:21:25  INFO: [4831779c: gt06 < 89.204.155.157] HEX: 78780713644608193f0d0a
2020-07-09 15:21:25  INFO: [4831779c: gt06 > 89.204.155.157] HEX: 78780513460866860d0a
2020-07-09 15:21:25  INFO: [4831779c] id: 359339075033589, time: 2020-07-09 14:09:59, lat: 51.47916, lon: 7.76419, speed: 1.6, course: 0.0
2020-07-09 15:21:45  INFO: [4831779c: gt06 < 89.204.155.157] HEX: 7878151114070909240c9705859a5f00d55d5a0d3547007d000d0a
2020-07-09 15:21:45  INFO: [4831779c: gt06 > 89.204.155.157] HEX: 78780511470046ae0d0a
2020-07-09 15:21:45  INFO: [4831779c] id: 359339075033589, time: 2020-07-09 14:09:59, lat: 51.47916, lon: 7.76419, speed: 1.6, course: 0.0
2020-07-09 15:22:35  INFO: [4831779c: gt06 < 89.204.155.157] HEX: 787801080d0a
2020-07-09 15:22:35  INFO: [4831779c: gt06 > 89.204.155.157] HEX: 78780508787895800d0a

some packets are repeating every 15 seconds and some or more rare. Anybody an idea where to look?

thanx, Mike

Could be either device or protocol. You have to check against protocol documentation.

Hey Anton, right I did.
The problem is the status paket send every 2 minutes - so this fits. This is the paket in question:

gt06 < 2.247.241.153] HEX: 7878071364460819640d0a

7878-start bytes 07-prototcol version 13-status paket

now it gets interesting:
64- battery status. Here we must have a protocol problem in GT06 driver in traccar, because the server reports battery status is 1166% (!) it should be around 95% regarding my protocol documentation interpretation.

46-software version
08-east area (correct)

now it gets weird. Protocol tells there is one byte more plus leadout (0D0A)
But in fact there are two bytes (0x1964). And something here tells traccar there is an ongoing SOS. I guess this is a protocol misinterpretation. No idea why. Anton?

source for protocol: ZhongXun Topin Locator Communication Protocol.pdf in traccar protocol documentation

device is a ZX612 from Topin

You should get documentation from your vendor.

I thought the documentation I mentioned above is the right one since it is a Topin device. Moreover it is officially supported my Traccar. Is the GT06 protocol not consistent amoung different devices? At least it looks so to me?

There is a countless number of GT06-like protocols with various modifications.

Hello Anton, I was able to get the latest protocol documentation from Topin and it seams there is a protocol change as assumed. Here the right chapter:
Increased signal strength
Start bit 2byte Packet length 1byte Protocol number 1byte Battery power 1byte Software version 1byte Time zone 1byte Status packet upload interval 1byte Device signal strength 1byte End bit 2byte
Eg.7878 07 13 55 23 08 03 64 0D0A
0x55 indicates that the battery level is 85. 0x64 indicates device signal strength 100

As you can see it fits the received data package. But however what can I do now? I guess there is an update necessary in Traccar?

Here is a link for downloading the updated protocol dokument: https://we.tl/t-hbIL7wRJRI
I hope it helps

Mike

It looks like you are using wrong port for your device. You should be using Topin port.

I will try. But in this case there's a flaw in your device list. It says ZX612 device is GT06 protocol. ZX612 (and ZX303) is a Topin product.

You should probably read this:

https://www.traccar.org/clones/

@MikeRD03 how did you resolve this problem what port did you use