Identify t-06 avtoscan gps tracker protocol

Hi to all
Please help to identify the communication protocol of our gps trackers.
data captured from device is allwais start in 0x35 and have 16 bytes payload.
All value in hex is changed except first byte wich is allways 0x35
examples:

data.data == 35:a8:28:98:97:69:97:e3:b7:86:9d:15:13:0e:f9:de
data.data == 35:65:e5:55:5a:a4:5a:2e:7a:4b:50:d8:de:c3:34:13
data.data == 35:ec:6c:dc:d3:2d:d3:a7:f3:c2:d9:51:57:4a:bd:9a
......
data.data == 35:16:96:26:29:d7:29:5d:09:38:23:ab:ad:b0:47:60

thank you

Logs?

it can be configured only usind UDP, and I try all the UDP ports
logs:

2023-04-05 16:14:28  INFO: [U8733862e: techtlt < 94.139.152.186] 3539b90d06f8067226960c84827f684f
2023-04-05 16:14:49  INFO: [U8733862e: techtlt < 94.139.152.186] 3533b3170cf20c782c9c068e88756245
2023-04-05 16:15:38  INFO: [U56bf9148: starcom < 94.139.152.186] 357cfc4843bd433763d349c1c73a2d0a
2023-04-05 16:15:38  INFO: [U56bf9148] error - begin 2, end 1, length 16 - StringIndexOutOfBoundsException (... < Starc
omProtocolDecoder:38 < ExtendedObjectDecoder:72 < ... < WrapperContext:102 < ...)
2023-04-05 16:16:30  INFO: [U7ab5b1a6: mictrack < 94.139.152.186] 358909adb648b6c29626bc3432cfd8ff
2023-04-05 16:18:10  INFO: [U8509fe03: rst < 94.139.152.186] 35db5bffe41ae490c4e5ee66606d8aad
2023-04-05 16:19:02  INFO: [U2e74d705: pacifictrack < 94.139.152.186] 35f676c2c937c9bde9d8c34b4d50a780
2023-04-05 16:19:02  INFO: [U2e74d705] error - readerIndex: 7120, writerIndex: 16 (expected: 0 <= readerIndex <= writer
Index <= capacity(2048)) - IndexOutOfBoundsException (... < PacificTrackProtocolDecoder:203 < ExtendedObjectDecoder:72
< ... < StandardLoggingHandler:44 < ...)
2023-04-05 16:22:32  INFO: [U2e74d705: pacifictrack < 94.139.141.36] 3523a3131ce21c0c2e486a84a6c0525500
2023-04-05 16:22:32  INFO: [U2e74d705] error - readerIndex: 51, writerIndex: 17 (expected: 0 <= readerIndex <= writerIn
dex <= capacity(2048)) - IndexOutOfBoundsException (... < PacificTrackProtocolDecoder:203 < ExtendedObjectDecoder:72 <
... < StandardLoggingHandler:44 < ...)
2023-04-05 16:23:22  INFO: [Ub9576e85: pst < 94.139.141.36] 357cfc4c43bd4353711735dbf99f0d0a
2023-04-05 16:23:22  WARN: Unknown device - 897383500 (94.139.141.36)
2023-04-05 16:23:43  INFO: [Ub9576e85: pst < 94.139.141.36] 358808b8b749b7a785e3c12f0d6bf9fe
2023-04-05 16:23:43  WARN: Unknown device - 898107576 (94.139.141.36)
2023-04-05 16:24:06  INFO: [Ub9576e85: pst < 94.139.141.36] 35b030808f718f9fbddbf9173553c1c6
2023-04-05 16:24:06  WARN: Unknown device - 900739200 (94.139.141.36)
2023-04-05 16:24:27  INFO: [Ub9576e85: pst < 94.139.141.36] 3548c87877897767452301efcdab393e
2023-04-05 16:24:27  WARN: Unknown device - 893962360 (94.139.141.36)
2023-04-05 16:24:48  INFO: [Ub9576e85: pst < 94.139.141.36] 359b1baba45aa4b496f0d23c1e78eaed
2023-04-05 16:24:48  WARN: Unknown device - 899357611 (94.139.141.36)
2023-04-05 16:25:13  INFO: [Ub9576e85: pst < 94.139.141.36] 354aca7a758b7565472103edcfa93b3c
2023-04-05 16:25:13  WARN: Unknown device - 894093946 (94.139.141.36)
2023-04-05 16:25:52  INFO: [U7cbf413a: mavlink2 < 94.139.141.36] 3573f3574cb24c5c7e183ad4f6900205
2023-04-05 16:26:14  INFO: [U7cbf413a: mavlink2 < 94.139.141.36] 350484303bc53b2b096f4da381e77572
2023-04-05 16:26:55  INFO: [U703541a6: flexiblereport < 94.139.141.36] 358d0da8b24cb2a280e6c42a086efcfb
2023-04-05 16:26:55  WARN: Unknown device - da8b24cb2a280e6 (94.139.141.36)
2023-04-05 16:27:45  INFO: [U7e22813b: b2316 < 94.139.141.36] 350f8f3b30ce3020026446a88aec7e79
2023-04-05 16:27:45  INFO: [U7e22813b] error - JsonParser#getObject() or JsonParser#getObjectStream() is valid only for
 START_OBJECT parser state. But current parser state is VALUE_NUMBER - IllegalStateException (... < B2316ProtocolDecode
r:78 < ExtendedObjectDecoder:72 < ... < WrapperContext:102 < ...)
2023-04-05 16:28:35  INFO: [Uc3ef4081: dsf22 < 94.139.141.36] 35b030948f718f9fbddbf9173553c1c6
2023-04-05 16:28:35  WARN: Unknown device - 37936 (94.139.141.36)
2023-04-05 16:28:58  INFO: [Uc3ef4081: dsf22 < 94.139.141.36] 359616a2a957a9b99bfddf311375e7e0
2023-04-05 16:28:58  WARN: Unknown device - 41494 (94.139.141.36)
2023-04-05 16:29:19  INFO: [Uc3ef4081: dsf22 < 94.139.141.36] 3561e1455ea05e4e6c0a28c6e4821017
2023-04-05 16:29:19  WARN: Unknown device - 17889 (94.139.141.36)
2023-04-05 16:29:57  INFO: [Uc3ef4081: dsf22 < 94.139.141.36] 35b030848f718f9fbddbf9173553c1c6
2023-04-05 16:29:57  WARN: Unknown device - 33840 (94.139.141.36)
2023-04-05 16:30:20  INFO: [Uc3ef4081: dsf22 < 94.139.141.36] 354fcf6b708e7060422406e8caac3e39
2023-04-05 16:30:20  WARN: Unknown device - 27599 (94.139.141.36)
2023-04-05 16:30:46  INFO: [Uc3ef4081: dsf22 < 94.139.141.36] 3572f2464db34d5d7f193bd5f7910304
2023-04-05 16:30:46  WARN: Unknown device - 18162 (94.139.141.36)

device identifier is "063191"

programable comand for IP port is : 00000,U,"udp","***.***.***.***","4040"

info request: 00000,I

result:

ID-063191  3FBF
2022.4.13
MultiTrack-D-M
D-010,002
S-001,010+C
M-5 R+ A- B-
"internet"
"udp","***.***.***.***","4040"
005,200,010,OFF
0,1,0,0,1,0,0,0

I can't find any matching protocols. Do you have the protocol documentation?

That's the problem because we don't have documentation about the protocol.
The applications that come in the package have compatibility problems and the company that maintains them has problems with capable developers.
We want to add it to a new platform as a tracker.
we have a pdf with the programming commands only
thank you

Without any documentation or some existing code it won't be possible to implement support for it.

I understand, thank you for your support anyway

Perhaps you could contact the manufacturer for the docs?

I am afraid that they will refuse to present the documents for fear of losing us as clients