Device identification - OBD2 V20 GSM

Hi All, I tried to identify protocol for my device but with no luck.
So if someone can tell me what protocol my device is (which port I need to use) that would help me a lot.
Official name of a device is OBD2 V20 GSM. I bought it from aliexpress.

Here is a log dump:

2019-12-08 14:20:18  INFO: [73ec5228] connected
2019-12-08 14:20:18  INFO: [73ec5228: tk103 < 46.188.157.119] HEX: 7e000200000057044553860001c07e
2019-12-08 14:21:49  INFO: [73ec5228: tk103 < 46.188.157.119] HEX: 7e02000028005704455386000200000001000c00000000000000000000000000000000181231160200c97e
2019-12-08 14:21:50  INFO: [73ec5228: tk103 < 46.188.157.119] HEX: 7e0704002d0057044553860003000101001c00000000000c000202babbda00f2d677002a00000164181231161206007e
2019-12-08 14:23:02  INFO: [73ec5228: tk103 < 46.188.157.119] HEX: 7e02000028005704455386000400000000000c0000000000000000000000000004005e181231160300957e
2019-12-08 14:23:49  INFO: [73ec5228: tk103 < 46.188.157.119] HEX: 7e02000028005704455386000500000000000c00000000000000000000000000000000181231160400c97e
2019-12-08 14:24:49  INFO: [73ec5228: tk103 < 46.188.157.119] HEX: 7e000200000057044553860006c77e
2019-12-08 14:24:50  INFO: [73ec5228: tk103 < 46.188.157.119] HEX: 7e02000028005704455386000700000000000c00000000000000000000000000000000181231160500ca7e
2019-12-08 14:25:49  INFO: [73ec5228] disconnected
2019-12-08 14:25:50  INFO: [dffae597] connected
2019-12-08 14:25:50  INFO: [dffae597: tk103 < 46.188.157.119] HEX: 7e000200000057044553860008c97e
2019-12-08 14:26:50  INFO: [dffae597: tk103 < 46.188.157.119] HEX: 7e02000028005704455386000900000000000c0000000000000000000000000000013d181231160700fa7e
2019-12-08 14:26:51  INFO: [dffae597: tk103 < 46.188.157.119] HEX: 7e0704002d005704455386000a000101001c00000000000c00000000000000000000000000000000181231160600dc7e
2019-12-08 14:27:59  INFO: [3234b60d] connected
2019-12-08 14:27:59  INFO: [3234b60d: tk103 < 46.188.145.103] HEX: 7e000200000057044553860001c07e
2019-12-08 14:28:51  INFO: [dffae597] timed out
2019-12-08 14:28:51  INFO: [dffae597] disconnected
2019-12-08 14:29:32  INFO: [3234b60d: tk103 < 46.188.145.103] HEX: 7e02000028005704455386000200000001000c00000000000000000000000000010021181231160200e97e
2019-12-08 14:30:32  INFO: [3234b60d: tk103 < 46.188.145.103] HEX: 7e02000028005704455386000300000000000c00000000000000000000000000000000181231160300c87e
2019-12-08 14:31:32  INFO: [3234b60d: tk103 < 46.188.145.103] HEX: 7e02000028005704455386000400000000000c00000000000000000000000000000000181231160400c87e
2019-12-08 14:32:32  INFO: [3234b60d: tk103 < 46.188.145.103] HEX: 7e000200000057044553860005c47e
2019-12-08 14:32:33  INFO: [3234b60d: tk103 < 46.188.145.103] HEX: 7e02000028005704455386000600000000000c000000000000000000000000000000ac181231160500677e
2019-12-08 14:32:37  INFO: [3234b60d: tk103 < 46.188.145.103] HEX: 7e02000028005704455386000700000000000c000202bae0dd00f401ba002a000101471812311605046b7e
2019-12-08 14:34:37  INFO: [3234b60d] timed out
2019-12-08 14:34:37  INFO: [3234b60d] disconnected
2019-12-08 14:52:02  INFO: [ba949d1f] connected
2019-12-08 14:52:02  INFO: [ba949d1f: tk103 < 31.217.21.59] HEX: 7e000200000057044553860001c07e
2019-12-08 14:53:23  INFO: [ba949d1f: tk103 < 31.217.21.59] HEX: 7e02000028005704455386000200000001000c00000000000000000000000000000000181231160200c97e
2019-12-08 14:54:23  INFO: [ba949d1f: tk103 < 31.217.21.59] HEX: 7e02000028005704455386000300000000000c00000000000000000000000000000000181231160300c87e
2019-12-08 14:55:23  INFO: [ba949d1f: tk103 < 31.217.21.59] HEX: 7e02000028005704455386000400000000000c00000000000000000000000000000000181231160400c87e
2019-12-08 14:56:23  INFO: [ba949d1f: tk103 < 31.217.21.59] HEX: 7e000200000057044553860005c47e
2019-12-08 14:56:24  INFO: [ba949d1f: tk103 < 31.217.21.59] HEX: 7e02000028005704455386000600000000000c00000000000000000000000000000000181231160500cb7e
2019-12-08 14:57:23  INFO: [ba949d1f] disconnected
2019-12-08 14:57:24  INFO: [3c1876b7] connected
2019-12-08 14:57:24  INFO: [3c1876b7: tk103 < 31.217.21.59] HEX: 7e000200000057044553860007c67e
2019-12-08 14:58:23  INFO: [3c1876b7: tk103 < 31.217.21.59] HEX: 7e02000028005704455386000800000000000c00000000000000000000000000000000181231160700c77e
2019-12-08 14:58:24  INFO: [3c1876b7: tk103 < 31.217.21.59] HEX: 7e0704002d0057044553860009000101001c00000000000c00000000000000000000000000000000181231160600df7e
2019-12-08 14:59:23  INFO: [3c1876b7: tk103 < 31.217.21.59] HEX: 7e02000028005704455386000a00000000000c00000000000000000000000000000000181231160800ca7e
2019-12-08 15:00:23  INFO: [3c1876b7: tk103 < 31.217.21.59] HEX: 7e02000028005704455386000b00000000000c00000000000000000000000000000000181231160900ca7e
2019-12-08 15:01:23  INFO: [3c1876b7: tk103 < 31.217.21.59] HEX: 7e02000028005704455386000c00000000000c00000000000000000000000000000000181231161000d47e
2019-12-08 15:02:23  INFO: [3c1876b7: tk103 < 31.217.21.59] HEX: 7e00020000005704455386000dcc7e
2019-12-08 15:02:24  INFO: [3c1876b7: tk103 < 31.217.21.59] HEX: 7e02000028005704455386000e00000000000c00000000000000000000000000010001181231161100d77e
2019-12-08 15:03:23  INFO: [3c1876b7] disconnected
2019-12-08 15:03:24  INFO: [6a9c03a5] connected
2019-12-08 15:03:24  INFO: [6a9c03a5: tk103 < 31.217.21.59] HEX: 7e00020000005704455386000fce7e
2019-12-08 15:04:44  INFO: [82d73050] connected
2019-12-08 15:04:44  INFO: [82d73050: tk103 < 31.217.31.71] HEX: 7e000200000057044553860001c07e
2019-12-08 15:05:24  INFO: [6a9c03a5] timed out
2019-12-08 15:05:24  INFO: [6a9c03a5] disconnected
2019-12-08 15:06:23  INFO: [82d73050: tk103 < 31.217.31.71] HEX: 7e02000028005704455386000200000001000c0000000000000000000000000000002e181231161500f07e
2019-12-08 15:08:23  INFO: [82d73050] timed out
2019-12-08 15:08:23  INFO: [82d73050] disconnected

Thanks a lot!

Try Huabao protocol.

Great, thanks. You are right that is correct protocol. Do you have documentation for that protocol? If yes, please feel free to send me, maybe I can contribute to a project by implementing some new features.

@Anonime
Hello
Have you tested the device you mention ?
Does it show data from the OBD2 bus as specified in it's technical description ?
Thanks.

Hi, sorry for slow response. Yes, I test it and I am receiving data. But data that I am receiving from OBD2 bus (e.g. milage) is not correct. I did not have some extra time to investigate more. I am very experienced developer so that will not be a problem for me. First step that I need is to get a document for a protocol to see if there is a problem in data parsing or it is a problem with device and reading data from OBD.

Also I am receiving some alarm: sos, but I don't know why.
See here: https://ibb.co/GngLc7c

Hello
Check if the supported OBD2 protocols from your car are the same as the supported OBD2 protocols of the device. Also maybe is sending milage in kilometers and your system is set in miles...
Regarding SOS alarm check your device setting over SMS... maybe you have to disable some alarms (eg. vibration) depending on your setup.
It's better to have no alarm than having false one...

Hi Anonime,
I bought this same device from Aliexpress with the idea of improving over the TK306, with the ODB vehicle data. I was very disappointed with this V20: https://www.aliexpress.com/item/4000087520915.html?spm=a2g0s.9042311.0.0.27424c4dYrsNhD

I have many issues:

• It would only come on when I turned the ignition state On/Off, when lucky for just long enough to be able to grab GPS and GSM data in time to report to the server.
• No information at all from the manufacturer/seller on protocols or SMS control to use with cloud service others than theirs.
• Once the device goes to sleep, it goes completely of the grid and will not respond to calls or texts.

Did you have the same experience? Are we both referring to the same device?
Mine is total garbage and I do not recommend wasting your money on this.

Hello,

I experience the same issues as Manny. At least, I have a little booklet with very few SMS controls. However, I don't see, how to check the current settings. So my fear is, that I can not set the original setting if I am not happy with the connection to traccar. Don't get me wrong, I use traccar for my other trackers and I am quite happy with it. The benefit of the OBD tracker is the additional OBD data I can receive. And I wonder, if I can access this data also within traccar? Also, if somebody found some more information about this tracker, I would be happy if this was shared.
Regards, Dieter

Hi @Anonime
Are you able to provide us with some information on how you were able to change settings on the V20 so as to be able to configure more than just the URL where it reports to, but also security settings, time to sleep, etc?
Thank you.