newbee with Traccar server

i have TK103 device in logs i have :

283836343736383031313436393238322c5a4330372c3233303731382c412c323233382e38353337324e2c31313430312e3933303139452c302e3030382c3035313532382c3030302e302c32312e36302c382c3029283836343736383031313436393238322c5a4332302c3233303731382c3035313532362c362c3431342c36353533352c32353529

After Traccar HEX decoder i have following output:

(864768011469282,ZC07,230718,A,2238.85372N,11401.93019E,0.008,051528,000.0,21.60,8,0)  

my question is, can Traccar server decode it self and will give output something like below in logs and show location on Web GUI:

2018-07-23 10:14:07  INFO: [2B983A3B] id: 864768011469282, time: 2018-07-23 10:14:07, lat: 22.64743, lon: 114.03216, course: 0.0

any one can guide please here?

It's TK103 protocol, port 5002.

Thanks Anton for your reply.

can you please confirm its direct hit from device or traccar gives it after decoding HEX

2018-07-23 10:14:07  INFO: [2B983A3B] id: 864768011469282, time: 2018-07-23 10:14:07, lat: 22.64743, lon: 114.03216, course: 0.0.

I don't get the question. Of course it decodes the data.

sorry Anoton.

please can you check log file from given below link. many times traccar does not decode HEX.

https://we.tl/jt6OLttPEG

I can see that after you registered device everything is decoded just fine.