Device Protocol

hshah7 years ago

Getting following HEX Data to Server, however not able to identify the correct protocol to configure the device.

Using port 5023 (Device TK102)

DEBUG: [DD128034: 5023 < 42.109.38.104] HEX: 283032373034343431363734314252303030303030303756303030302e303030304e30303030302e30303030453030302e30303031343033393930303030303030304c303030303030303029

DEBUG: [DD128034: 5023 < 42.109.38.104] HEX: 283032373034343431363734314250303030303030323730343434313637343148534f29
dennisonm7 years ago

I have this device as well from China that I can't figure out if the protocol is supported in traccar. Unfortunately the seller don't want to provide the protocol documentation.

$$?x ??D????U161151.000,A,0119.0301,N,10351.1533,E,000.0,000.0,250217,,,A*67|0.8|89.6|0000|0005,0000|000034044|00000?????
Anton Tananaev7 years ago

@hshah, your device uses TK103 protocol, port 5002. Device id is 027044416741.

@dennisonm, next time you should provide HEX sample instead of unreadable text. It seems to be Meiligao protocol, port 5009.

dennisonm7 years ago

Thanks for quick reply Anton. This is the hex sample:

24240078201692449306ff99553230333435392e3030302c412c303131392e303438372c4e2c31303335312e313137382c452c3030302e302c3239382e382c3235303231372c2c2c442a36317c302e397c35362e357c303030307c303030362c303030307c3030303033343934377c3030303030d7ce0d0a.

You are correct it's using the meiligao protocol. Thank you very much!