decoding error 0x69

A.B.7 years ago

Hi all,

In the new 3.15 version for gt06 there is a new function code, witch seems to not work properly. At least for my gt06. The problem is with 0x69 MSG_WIFI_2.

Here is the log:

2017-12-19 14:07:10  INFO: [F7A6A490] connected
2017-12-19 14:07:12 DEBUG: [F7A6A490: 5023 < 37.76.56.246] HEX: 78780d010351213141516606002a346f0d0a
2017-12-19 14:07:12 DEBUG: [F7A6A490: 5023 > 37.76.56.246] HEX: 787805010001d9dc0d0a
2017-12-19 14:07:14 DEBUG: [F7A6A490: 5023 < 37.76.56.246] HEX: 78780a134405040000002b8a490d0a
2017-12-19 14:07:14 DEBUG: [F7A6A490: 5023 > 37.76.56.246] HEX: 787805130002db6a0d0a
2017-12-19 14:07:14  INFO: [F7A6A490] id: 351213141516606, time: 1970-01-01 01:00:00, lat: 0.00000, lon: 0.00000, speed: 0.0, course: 0.0
2017-12-19 14:07:17 DEBUG: [F7A6A490: 5023 < 37.76.56.246] HEX: 78780c69110c130d070901002c8c950d0a
2017-12-19 14:07:17  WARN: [F7A6A490] error - Readable byte limit exceeded: 17 - IndexOutOfBoundsException (... < Gt06ProtocolDecoder:506 < *:475 < *:753 < ExtendedObjectDecoder:58 < ...)
2017-12-19 14:07:17  INFO: [F7A6A490] disconnected
Anton Tananaev7 years ago

Do you have protocol documentation for your device?

A.B.7 years ago

I don't have :( It is a chinese clone in fact, gt06ab is the exact type of device. The device calls itself as 61M-GT06_V3.3_171030

Anton Tananaev7 years ago

Without documentation it's not possible to decode it properly.

A.B.7 years ago

I understand, previous version (3.14) as i understand the source, skipped this(0x69) section. Just answered a standard indexed message and the terminal doesn't disconnected. Current version try to decode it, but the decoding algoritm mismatch for it and gives error. There is no answer to the terminal and this is why it disconnects every time.

I analized the 0x69 messages and as I can translate, it sends only the actual GMT+0 date and time, nothing more. It is like it try to ping the server if it is able to reach it or not.

7878 0c 69 110c13163b2b0000c3 b3e1 0d0a
11 0c 13 16 3b 2b 00 00 c3
year, months, day, hour, minute, sec, 00/01 changing, 00 always, sec again, running number

Anton Tananaev7 years ago

Not according to this documentation:

ZhongXun Topin Locator Communication Protocol.pdf

A.B.7 years ago

Ok, I'm gonna check it. May be it works differently when it is online/offline. The case when i tried to examin is when the terminal has GPS position.