@symapptest, please don't spam everywhere with same question. Your device is using H02 protocol, not TK103, so correct port is 5013. Also, it looks like it's broken. See github comment.
Hi, I know this is a really really old post, but I wanted to find out the protocol of my TK102B clone. I tried converting the HEX and look the code up in the file, but i couldn't find anything. Can someone please help. The log details are below.
2017-11-27 23:18:33 DEBUG: [0FE23E22: 5023 < 78.95.65.87] HEX: 717569740d0a
2017-11-27 23:18:33 DEBUG: [0FE23E22: 5023 < 78.95.65.87] HEX: 0d0a
2017-11-27 23:18:34 DEBUG: [0FE23E22: 5023 < 78.95.65.87] HEX: 0d0a0d0a
2017-11-27 23:18:34 DEBUG: [0FE23E22: 5023 < 78.95.65.87] HEX: 0d0a
2017-11-27 23:18:36 INFO: [0FE23E22] disconnected
2017-11-27 23:21:46 INFO: [B78D4062] connected
2017-11-27 23:21:47 DEBUG: [B78D4062: 5023 < 37.224.255.242] HEX: 283038373037353537353533344252303031373131323756323631372e323136324e30353031312e35303937453030312e333230303533393030302e30302c30303030303030304c303030303030303029
2017-11-27 23:21:48 DEBUG: [B78D4062: 5023 < 37.224.255.242] HEX: 283038373037353537353533344250303048534f29
2017-11-27 23:21:53 DEBUG: [B78D4062: 5023 < 37.224.255.242] HEX: 283038373037353537353533344252303031373131323756323631372e323136324e30353031312e35303937453030312e333230303533393030302e30302c30303030303030304c303030303030303029
2017-11-27 23:22:53 DEBUG: [B78D4062: 5023 < 37.224.255.242] HEX: 283038373037353537353533344252303031373131323756323631372e323136324e30353031312e35303937453030312e333230303533393030302e30302c30303030303030304c303030303030303029
2017-11-27 23:23:53 DEBUG: [B78D4062: 5023 < 37.224.255.242] HEX: 283038373037353537353533344252303031373131323756323631372e323136324e30353031312e35303937453030312e333230303533393030302e30302c30303030303030304c303030303030303029
2017-11-27 23:24:53 DEBUG: [B78D4062: 5023 < 37.224.255.242] HEX: 283038373037353537353533344252303031373131323756323631372e323136324e30353031312e35303937453030312e333230303533393030302e30302c30303030303030304c303030303030303029
2017-11-27 23:25:53 DEBUG: [B78D4062: 5023 < 37.224.255.242] HEX: 283038373037353537353533344252303031373131323741323631372e323131384e30353031312e35313932453030302e343230323432323030302e30302c30303030303030304c303030303030303029
2017-11-27 23:26:46 INFO: [B78D4062] disconnected
2017-11-27 23:26:48 INFO: [5DE6160A] connected
2017-11-27 23:26:49 DEBUG: [5DE6160A: 5023 < 37.224.180.12] HEX: 283038373037353537353533344250303048534f29
2017-11-27 23:26:53 DEBUG: [5DE6160A: 5023 < 37.224.180.12] HEX: 283038373037353537353533344252303031373131323741323631372e323133334e30353031312e35313939453030302e333230323532323030302e30302c30303030303030304c303030303030303029
2017-11-27 23:27:53 DEBUG: [5DE6160A: 5023 < 37.224.180.12] HEX: 283038373037353537353533344252303031373131323741323631372e323134384e30353031312e35313338453030302e373230323632323030302e30302c30303030303030304c303030303030303029
2017-11-27 23:28:53 DEBUG: [5DE6160A: 5023 < 37.224.180.12] HEX: 283038373037353537353533344252303031373131323741323631372e323135314e30353031312e35313139453030302e373230323732323030302e30302c30303030303030304c303030303030303029
2017-11-27 23:29:53 DEBUG: [5DE6160A: 5023 < 37.224.180.12] HEX: 283038373037353537353533344252303031373131323741323631372e323134374e30353031312e35313534453030302e323230323832323030302e30302c30303030303030304c303030303030303029
2017-11-27 23:30:53 DEBUG: [5DE6160A: 5023 < 37.224.180.12] HEX: 283038373037353537353533344252303031373131323741323631372e323134364e30353031312e35313536453030302e303230323932323030302e30302c30303030303030304c303030303030303029
2017-11-27 23:31:48 INFO: [5DE6160A] disconnected
2017-11-27 23:31:50 INFO: [D028DEB8] connected
2017-11-27 23:31:52 DEBUG: [D028DEB8: 5023 < 178.86.9.217] HEX: 283038373037353537353533344250303048534f29
2017-11-27 23:31:53 DEBUG: [D028DEB8: 5023 < 178.86.9.217] HEX: 283038373037353537353533344252303031373131323741323631372e323134394e30353031312e35313638453030302e313230333032323030302e30302c30303030303030304c303030303030303029
2017-11-27 23:32:53 DEBUG: [D028DEB8: 5023 < 178.86.9.217] HEX: 283038373037353537353533344252303031373131323741323631372e323135314e30353031312e35313833453030302e313230333132303030302e30302c30303030303030304c303030303030303029
2017-11-27 23:33:54 DEBUG: [D028DEB8: 5023 < 178.86.9.217] HEX: 283038373037353537353533344252303031373131323741323631372e323135314e30353031312e35313539453030312e323230333232303030302e30302c30303030303030304c303030303030303029
2017-11-27 23:34:53 DEBUG: [D028DEB8: 5023 < 178.86.9.217] HEX: 283038373037353537353533344252303031373131323741323631372e323135334e30353031312e35313535453030302e333230333332303030302e30302c30303030303030304c303030303030303029
2017-11-27 23:35:53 DEBUG: [D028DEB8: 5023 < 178.86.9.217] HEX: 283038373037353537353533344252303031373131323741323631372e323135324e30353031312e35313839453030302e363230333432303030302e30302c30303030303030304c303030303030303029
Your device is using TK103 protocol, port 5002. Device id is 087075575534.
For everyone else, please read this before asking anything:
Thank you so very much Anton, that worked like a charm. Can you please guide me on how you were able to get the protocol from the HEX, as i tried converting the HEX but failed. Just so fill my knowledge bank.
Thanks again.
Aj.
This is how I do it:
That's what I'm saying, that I followed that and when I searched the decoded HEX in the result file, I couldn't get anything.
Is this what you search to decode ?
(087075575534BR00171127A2617.2152N05011.5189E000.6203420000.00,00000000L00000000)
Your assistance is highly appreciated.
Thanks,
Aj.
Yes, it matches TK103 format if you look at it. Obviously you can't just search for that exact message.
I followed the procedure where it asked to decode the hex and search for the result in the result file. But no result. Just so I learn, how do I pull out the protocol ? If you don't mind spending a min to explain.
Thank you for your great effort.
Aj.
Explain me how do you search for the result?
I decoded this HEX :
283038373037353537353533344252303031373131323741323631372e323135324e30353031312e35313839453030302e363230333432303030302e30302c30303030303030304c303030303030303029
Got this result :
(087075575534BR00171127A2617.2152N05011.5189E000.6203420000.00,00000000L00000000)
And searched for the result in the result file.
Thanks,
Aj.
What result file are you talking about? Integration test? Are you expecting to find a message there with your device id and your current coordinates? I hope you realise that it makes no sense.
On this link : https://www.traccar.org/identify-protocol/
There are two things to do :
That's what i'm doing, and of course, I do not expect to be a piece of cake. That is why i'm trying to understand how it's done, when there are steps given and i'm not able to either follow them or doing something wrong.
After I decode the HEX, what result am I supposed to look for in the step 2 file above.
Aj.
Find matching protocol means that you need to look through all the examples in the file and find the one that looks SIMILAR. You will never find exact match because your message will contain different id, coordinates etc.
Alrighto, thank you for your assistance, I was going crazy over this, I just wish I knew what to look for in the decoded file. Just for my knowledge, I tried again, but couldn't match anything.
Well my trackers are up, I'll be making a step by step on it on my youtube channel so others can benefit.
Thanks and have a good day.
Aj.
i have set up port 5002 for TK102 but it's not working
My hex is this