help to identify protocol

Tracker5 years ago

help to identify the port of this slimtrack pt50 device, add fragments of my logs

root@Rodar:/opt/traccar/logs# tail tracker-server.log
2020-01-07 23:53:58  INFO: [356f62d4] id: 027029108990, time: 2020-01-07 23:53:58, lat: -34.59416, lon: -58.41650, speed: 7.0, course: 186.5
2020-01-07 23:54:01  INFO: [9a771655: tk103 < 181.117.224.101] HEX: 28303237303238313039393332425230303030303532334a316330667c373535667c3732323331307c3030303030303030303032303534303030303030303030313030303030304c303030303030303029
2020-01-07 23:54:07  INFO: [356f62d4: tk103 < 181.117.228.196] HEX: 283032373032393130383939304250303033353333323730323931303839393048534f31396429
2020-01-07 23:54:07  INFO: [356f62d4: tk103 > 181.117.228.196] HEX: 283032373032393130383939304150303148534f29
2020-01-07 23:54:08  INFO: [fdc9dc61: huabao < 181.117.228.115] HEX: 7e01000021014145446243001d002c012f37303131314135452d385720203030303030303001d4c1423838383838447e
2020-01-07 23:54:08  WARN: Unknown device - 014145446243 (181.117.228.115)
2020-01-07 23:54:18  INFO: [fdc9dc61: huabao < 181.117.228.115] HEX: 7e00030000014145446243001e7d017e
2020-01-07 23:54:18  WARN: Unknown device - 014145446243 (181.117.228.115)
2020-01-07 23:54:21  INFO: [356f62d4: tk103 < 181.117.228.196] HEX: 283032373032393130383939304252303032303031303741333433352e373230305330353832352e30303737573031382e323233353431383139362e393130303030303030314c303030303030303029
2020-01-07 23:54:21  INFO: [356f62d4] id: 027029108990, time: 2020-01-07 23:54:21, lat: -34.59533, lon: -58.41680, speed: 9.8, course: 196.9
root@Rodar:/opt/traccar/logs#
Anton Tananaev5 years ago

I would recommend you to read documentation, especially troubleshooting guide.

Tracker5 years ago

is already added to traccar with this identifier: 14145446243 but I can't make it connect

This is what generates me when using the HEX decoder: [binary data]

Anton Tananaev5 years ago

The identifier you used is incorrect, as you can clearly see from the log.