Receiving data frames from D7C Chinese GPS watch

Hey folks,

I configured correctly a D7C GPS watch in order to work with my Traccar server. But I am unable to know which port should I use. I used 5093 port as I have set it successfully for other GPS watches, but I receive these frames, already decoded Hex messages:

[3G*7809997356*0008*LK,0,0,2]
[3G*7809997356*0008*LK,0,0,2]
[3G*7809997356*007E*CONFIG,TY:g601x,UL:60,SY:0,CM:0,WT:0,HR:1,TB:3,CS:0,PP:0,AB:0,HH:1,TR:0,MO:1,FL:0,VD:0,DD:2,SD:1,XY:0,WF:0,WX:0,PH:0,RW:0,MT:1]
Data truncation: Incorrect datetime value: '1969-12-31 19:00:00' for column 'fixtime' at row 1 - MysqlDataTruncation (... < QueryBuilder:477 < DataManager:452 < DefaultDataHandler:27 < ...)
[3G*7809997356*007E*CONFIG,TY:g601x,UL:60,SY:0,CM:0,WT:0,HR:1,TB:3,CS:0,PP:0,AB:0,HH:1,TR:0,MO:1,FL:0,VD:0,DD:2,SD:1,XY:0,WF:0,WX:0,PH:0,RW:0,MT:1]
[3G*7809997356*001A*ICCID,89571015019120106536]

Later I tried with other devices as the troubleshooting guide, but now watch sends unknown data frames like:

ÿAQSH....

and throws several errors:

error - Connection reset by peer - IOException (...)
error - empty text - IllegalArgumentException (... < MainEventHandler:120 < *:109 < ... < GeocoderHandler:43 < ... < ExtendedObjectDecoder:52 < ...)

Can anyone help? Thanks in advance

Providing original unmodified Traccar logs would be more useful.

Here are some,

2019-03-03 21:27:56  INFO: [9ab2fab8: 5093 < 191.156.68.224] HEX: ff41515348002b0100000066e52eb5c73f66e11c4c1808299cea35e557eb43c16be747f1f8e99ce6b953835c7c8dd10c
2019-03-03 21:31:48  INFO: [79224c6e: 5093 < 191.156.65.58] HEX: ff41515348002b0100000066e52eb5c73f66e11c4c1808299cea35e557eb43c16be747f1f8e99ce6b953835c7c8e12cc
2019-03-03 21:33:03  INFO: [6b6bf28d] connected
2019-03-03 21:33:03  INFO: [6b6bf28d: 5093 < 191.156.8.99] HEX: ff41515348002b0100000066e52eb5c73f66e11c4c1808299cea35e557eb43c16be747f1f8e99ce6b953835c7c8e5d83
2019-03-03 21:33:03  WARN: [6b6bf28d] error - minimumReadableBytes: -5 (expected: >= 0) - IllegalArgumentException (... < WatchProtocolDecoder:188 < ExtendedObjectDecoder:51 < ... < WrapperContext:102 < ...)
2019-03-03 21:33:03  INFO: [6b6bf28d] disconnected
2019-03-03 21:34:30  INFO: [223a5b9a: 5093 < 191.156.40.115] HEX: ff41515348002b0100000066e52eb5c73f66e11c4c1808299cea35e557eb43c16be747f1f8e99ce6b953835c7c8eb56b
2019-03-03 21:35:49  INFO: [dcae7374] connected
2019-03-03 21:35:49  INFO: [dcae7374: 5093 < 190.130.72.145] HEX: ff41515348002b0100000066e52eb5c73f66e11c4c1808299cea35e557eb43c16be747f1f8e99ce6b953835c7c8f03dc
2019-03-03 21:36:17  INFO: [96bb867d] disconnected
2019-03-03 21:36:37  INFO: [dcae7374] disconnected
2019-03-03 21:37:08  INFO: [5cc9a581] connected
2019-03-03 21:37:08  INFO: [5cc9a581: 5093 < 191.156.34.156] HEX: ff41515348002b0100000066e52eb5c73f66e11c4c1808299cea35e557eb43c16be747f1f8e99ce6b953835c7c8f528d

Thanks for the help

All I can say is that it's not Watch protocol. And it doesn't even match original sample you provided.

I configured 5001 port and got these ones:

2019-03-03 22:52:06  INFO: [78507116: 5001 < 191.156.5.50] HEX: ff41515348002b010000002ae380347f7c28708c7dc2731025e303b7bbd02ae0dd305989a3c148a8b1cb325c7ca0e4e8
2019-03-03 22:52:06  WARN: [78507116] error - String index out of range: 23 - StringIndexOutOfBoundsException (... < Gps103ProtocolDecoder:411 < ExtendedObjectDecoder:51 < ... < WrapperContext:102 < ...)
2019-03-03 22:52:06  WARN: [78507116] error - String index out of range: 23 - StringIndexOutOfBoundsException (... < Gps103ProtocolDecoder:411 < ExtendedObjectDecoder:51 < ... < WrapperContext:102 < ...)
2019-03-03 22:52:06  INFO: [78507116] disconnected

Thanks in advance.

You would need to get protocol documentation for your device.

I got it from vendor, could you check it?

https://www.dropbox.com/s/kcavclp4atvesna/elec%20communicati-on%20protocolV1.7%EF%BC%8820150423%EF%BC%89%28D7%29.pdf?dl=0

Thanks so much.

It's Watch protocol, but what you have in your second and third comments doesn't match the format.

Hi, these are new logs:

Using 5001 port:

2019-03-11 09:32:27  INFO: [44381271] connected
2019-03-11 09:32:27  INFO: [44381271: 5001 < 191.156.64.158] HEX: ff41515348002b010000002ae380347f7c28708c7dc2731025e303b7bbd02ae0dd305989a3c148a8b1cb325c86717a5d
2019-03-11 09:32:27  WARN: [44381271] error - String index out of range: 23 - StringIndexOutOfBoundsException (... < Gps103ProtocolDecoder:411 < ExtendedObjectDecoder:51 < ... < WrapperContext:102 < ...)
2019-03-11 09:32:27  WARN: [44381271] error - String index out of range: 23 - StringIndexOutOfBoundsException (... < Gps103ProtocolDecoder:411 < ExtendedObjectDecoder:51 < ... < WrapperContext:102 < ...)
2019-03-11 09:32:27  INFO: [44381271] disconnected
2019-03-11 09:34:30  INFO: [2a5c3ed5] connected
2019-03-11 09:34:30  INFO: [2a5c3ed5: 5001 < 190.130.80.27] HEX: ff41515348002b010000002ae380347f7c28708c7dc2731025e303b7bbd02ae0dd305989a3c148a8b1cb325c8671f5d2
2019-03-11 09:34:30  WARN: [2a5c3ed5] error - String index out of range: 23 - StringIndexOutOfBoundsException (... < Gps103ProtocolDecoder:411 < ExtendedObjectDecoder:51 < ... < WrapperContext:102 < ...)
2019-03-11 09:34:30  WARN: [2a5c3ed5] error - String index out of range: 23 - StringIndexOutOfBoundsException (... < Gps103ProtocolDecoder:411 < ExtendedObjectDecoder:51 < ... < WrapperContext:102 < ...)
2019-03-11 09:34:30  INFO: [2a5c3ed5] disconnected

Using 5093 port:

2019-03-11 09:35:53  INFO: [a92ec242] connected
2019-03-11 09:35:53  INFO: [a92ec242: 5093 < 190.130.81.37] HEX: ff41515348002b010000002ae380347f7c28708c7dc2731025e303b7bbd02ae0dd305989a3c148a8b1cb325c8672486c
2019-03-11 09:36:41  INFO: [a92ec242] disconnected
2019-03-11 09:39:55  INFO: [42872dbc] connected
2019-03-11 09:39:55  INFO: [42872dbc: 5093 < 190.130.72.251] HEX: ff41515348002b010000002ae380347f7c28708c7dc2731025e303b7bbd02ae0dd305989a3c148a8b1cb325c86733a1f
2019-03-11 09:40:41  INFO: [42872dbc] disconnected
2019-03-11 09:42:33  INFO: [8a1df120] connected
2019-03-11 09:42:33  INFO: [8a1df120: 5093 < 191.156.45.111] HEX: ff41515348002b010000002ae380347f7c28708c7dc2731025e303b7bbd02ae0dd305989a3c148a8b1cb325c8673d8fd
2019-03-11 09:43:21  INFO: [8a1df120] disconnected

Thanks for your help.

Same problem. Format doesn't match documentation that you provided.

I have the exact same problem. I have a chinese Q750 watch. It works good with SeTracker app.
If I set the IP to my Traccar server and look at the log file (tracker-server.log), I'm always receiveng HEX values that with the Hex Decoder translate to ÿAQSH (even if the last 5 values are different).
I'm using port 5093. I'm assuming it is using the watch protocol, as the watch is very similar to Q50 and others (it accepts the same SMS codes).

Here is an excerpt of the log:

2019-03-29 14:03:06  INFO: [d029e26d] connected
2019-03-29 14:03:06  INFO: [d029e26d: 5093 < 31.4.243.178] HEX: ff41515348002b01000000356a72692880181a1b738376e5e41673bebbd9d11998a23f776a590abee3756c5c9e2599ac
2019-03-29 14:03:54  INFO: [d029e26d] disconnected
2019-03-29 14:04:27  INFO: [60149d9a] connected
2019-03-29 14:04:28  INFO: [60149d9a: 5093 < 31.4.243.189] HEX: ff41515348002b01000000356a72692880181a1b738376e5e41673bebbd9d11998a23f776a590abee3756c5c9e25eadf
2019-03-29 14:05:15  INFO: [60149d9a] disconnected
2019-03-29 14:05:48  INFO: [3efd5d3c] connected
2019-03-29 14:05:48  INFO: [3efd5d3c: 5093 < 31.4.243.206] HEX: ff41515348002b01000000356a72692880181a1b738376e5e41673bebbd9d11998a23f776a590abee3756c5c9e263b0d
2019-03-29 14:06:35  INFO: [3efd5d3c] disconnected
2019-03-29 14:07:07  INFO: [3de0fef4] connected
2019-03-29 14:07:07  INFO: [3de0fef4: 5093 < 31.4.243.41] HEX: ff41515348002b01000000356a72692880181a1b738376e5e41673bebbd9d11998a23f776a590abee3756c5c9e268abc
2019-03-29 14:07:55  INFO: [3de0fef4] disconnected
2019-03-29 14:08:28  INFO: [7dacf26f] connected
2019-03-29 14:08:28  INFO: [7dacf26f: 5093 < 31.4.243.113] HEX: ff41515348002b01000000356a72692880181a1b738376e5e41673bebbd9d11998a23f776a590abee3756c5c9e26dbed
2019-03-29 14:09:16  INFO: [7dacf26f] disconnected
2019-03-29 14:09:49  INFO: [1a91bdc6] connected
2019-03-29 14:09:49  INFO: [1a91bdc6: 5093 < 31.4.243.230] HEX: ff41515348002b01000000356a72692880181a1b738376e5e41673bebbd9d11998a23f776a590abee3756c5c9e272b1c
2019-03-29 14:10:37  INFO: [1a91bdc6] disconnected 

Any help will be appreciated. Thanks in advance.

Marc, have you read comments above?

Yes. So, if I understand it correctly, it is not using the watch protocol, nor any other that can be used with traccar, isn't it?

It is not Watch protocol. To answer your question, we need protocol documentation.

Ok. I understand.
I'll search for the protocol documentation or use another type of watch.
Thank you.