Problem decoding HEX to find device ID

Hi anton I don't mean to disturb you but honestly I cannot decode the following HEX to get the ID all I'm getting is some unreadabled characters.

2018-12-09 22:50:51  INFO: [ab3baec9: 5002 < 190.167.227.170] HEX: 787813110000000000000172025a3d00f39e002c04050d0a
2018-12-09 22:51:21  INFO: [ab3baec9: 5002 < 190.167.227.170] HEX: 787813110000000000000172025a3d00f39e002d048c0d0a
2018-12-09 22:51:33  INFO: [ab3baec9: 5002 < 190.167.227.170] HEX: 78780a1300043f00010033733a0d0a
2018-12-09 22:51:42  INFO: [ab3baec9: 5002 < 190.167.227.170] HEX: 78780d010352887074213541003409260d0a
2018-12-09 22:51:51  INFO: [ab3baec9: 5002 < 190.167.227.170] HEX: 787813110000000000000172025a3d00f39e002e04170d0a
2018-12-09 22:52:21  INFO: [ab3baec9: 5002 < 190.167.227.170] HEX: 787813110000000000000172025a3d00f39e002f049e0d0a
2018-12-09 22:53:02  INFO: [ab3baec9: 5002 < 190.167.227.170] HEX: 787813110000000000000172025a3d00f39e003004e80d0a
2018-12-09 22:53:23  INFO: [ab3baec9: 5002 < 190.167.227.170] HEX: 7878131100000000000000000000000000000031040e0d0a
2018-12-09 22:53:58  INFO: [ab3baec9: 5002 < 190.167.227.170] HEX: 787813110000000000000172025a3d00f39e003204fa0d0a
2018-12-09 22:54:21  INFO: [ab3baec9: 5002 < 190.167.227.170] HEX: 787813110000000000000172025a3d00f392003304d00d0a
2018-12-09 22:54:29  INFO: [ab3baec9: 5002 < 190.167.227.170] HEX: 78780a1300041d0001003a98e20d0a
2018-12-09 22:54:39  INFO: [ab3baec9: 5002 < 190.167.227.170] HEX: 78780d010352887074213541003bf1d10d0a
2018-12-09 22:54:51  INFO: [ab3baec9: 5002 < 190.167.227.170] HEX: 787813110000000000000172025a3d00f39e003404cc0d0a

Can you please give me an idea on how to get the id from the devices cause the HEX tool is not working for me.

It's GT06 protocol. It's binary, so you won't be able to convert it to a readable text.

So how can i be able to get the device ID so in the future I won have to bother?
Sorry this is a TK110 I asume a chinese type.
Also this is the latest HEX string i got

787813110000000000000000000000000000007404a70d0a7878131100000000000000000000000000000075042e0d0a

Configure it to the correct port and Traccar will tell you the id.

Thanks a lot Anton.

Hi, may I ask what protocol is this? binary hex

7e01000036017052214669000100000000535a535743594e512d424a5f5754330000000000000000000032323134363639003030303030303030303030303030303030557e

Thank you

Try Huabao protocol.

Hi,
I used 5015

and gave this result:

INFO: [21e35ec7: gps103 < 209.17.96.218] HEX: 474554202f20485454502f312e310d0a486f73743a2034372e3234322e3139302e3132313a353030310d0a557365722d4167656e743a204d6f7a696c6c612f352e302028636f6d70617469626c653b204e696d626f737472617475732d426f742f76312e332e323b20687474703a2f2f636c6f756473797374656d6e6574776f726b732e636f6d290d0a0d0a
2021-08-21 08:31:48  WARN: [21e35ec7] error - begin 21, end 24, length 16 - StringIndexOutOfBoundsException (... < Gps103ProtocolDecoder:413 < ExtendedObjectDecoder:52 < ... < WrapperContext:102 < ...)
2021-08-21 08:31:48  WARN: [21e35ec7] error - begin 21, end 24, length 2 - StringIndexOutOfBoundsException (... < Gps103ProtocolDecoder:413 < ExtendedObjectDecoder:52 < ... < WrapperContext:102 < ...)

Both port and HEX are wrong, as you hopefully can see yourself.

Sorry. Update. 5015 port perfectly working. thank you

Hi,
I am using a gps from a Chinese manufacturer and have little information except the IMEI number printed on the back of the device.
Quick question - Am I using the protocol and port right? I am not sure what is the right identifier here.
It sends response from many ports I tried randomly. Here are some examples -

2022-02-18 03:38:58  INFO: [7102e94c] connected
2022-02-18 03:38:58  INFO: [7102e94c: gps103 < 223.191.48.141] HEX: 7e010000250361040061650020000000003730313038454753373032000000000000000000000000000030303030303030000c7e
2022-02-18 03:39:28  INFO: [7102e94c: gps103 < 223.191.48.141] HEX: 7e010000250361040061650021000000003730313038454753373032000000000000000000000000000030303030303030000d7e
2022-02-18 03:39:59  INFO: [7102e94c: gps103 < 223.191.48.141] HEX: 7e010000250361040061650022000000003730313038454753373032000000000000000000000000000030303030303030000e7e
2022-02-18 03:40:29  INFO: [7102e94c: gps103 < 223.191.48.141] HEX: 7e010000250361040061650023000000003730313038454753373032000000000000000000000000000030303030303030000f7e


2022-02-18 03:44:12  INFO: [c2f86a9e] connected
2022-02-18 03:44:12  INFO: [c2f86a9e: tk103 < 182.66.191.176] HEX: 7e01000025036104006165002800000000373031303845475337303200000000000000000000000000003030303030303000047e
2022-02-18 03:44:42  INFO: [c2f86a9e: tk103 < 182.66.191.176] HEX: 7e01000025036104006165002900000000373031303845475337303200000000000000000000000000003030303030303000057e
2022-02-18 03:45:13  INFO: [c2f86a9e: tk103 < 182.66.191.176] HEX: 7e01000025036104006165002a00000000373031303845475337303200000000000000000000000000003030303030303000067e
2022-02-18 03:45:42  INFO: [c2f86a9e: tk103 < 182.66.191.176] HEX: 7e01000025036104006165002b00000000373031303845475337303200000000000000000000000000003030303030303000077e

I can see the IMEI number in the HEX code but not sure how to get hold of the identifier.
You help and guidance is much appreciated.
Thanks in advance.

Wrong protocol/port. Please read documentation we provide.

Thanks Anton.
Huabao protocol (correct port 5015), I guess?

Really appreciate.

Hi,
how can I decode the HEX messages?

Sorry, I founded:
https://www.traccar.org/hex-decoder/