Help with TK119
It means that you haven't added the device. Make sure there are no typos in the unique id.
Hi Anton,
Thank you for your reply.
Understood about the unknown device, I have already added the device in the web interface with the identifier set as the IMEI, I directly copied and pasted from the log to the input field and saved to avoid any typos.
I tried both formats, just the IMEI and IMEI (IP ADDRESS) format as illustrated in the log file. Both did not work unfortunately.
Just to make sense of the data coming through, though, I cannot match up a protocol using the methods suggested. Still assuming "eelink" protocol is correct through port 5064.
Thank you
Hi,
It eventually came good. I don't really have much of an explanation but now it shows the device "Last Update" date and time.
However, still not pin pointing on the map. And not making much sense of the data the GPS is sending to the server.
Any assistances greatly appreciated!
2016-11-03 20:42:44 INFO: Operating system name: Windows 2003 version: 5.2 architecture: x86
2016-11-03 20:42:44 INFO: Java runtime name: Java HotSpot(TM) Client VM vendor: Oracle Corporation version: 24.80-b11
2016-11-03 20:42:44 INFO: Memory limit heap: 247mb non-heap: 118mb
2016-11-03 20:42:44 INFO: Character encoding: UTF-8 charset: UTF-8
2016-11-03 20:42:44 INFO: Version: 3.7-SNAPSHOT
2016-11-03 20:42:46 INFO: Starting server...
2016-11-03 20:42:50 INFO: [C0D7AE09] connected
2016-11-03 20:42:51 DEBUG: [C0D7AE09: 5064 < 1.152.97.97] HEX: 676701000c00700352544072185102012c
2016-11-03 20:42:51 DEBUG: [C0D7AE09: 5064 > 1.152.97.97] HEX: 67670100020070
2016-11-03 20:45:52 DEBUG: [C0D7AE09: 5064 < 1.152.97.97] HEX: 67670300040071006b
2016-11-03 20:45:52 DEBUG: [C0D7AE09: 5064 > 1.152.97.97] HEX: 67670300020071
2016-11-03 20:48:52 DEBUG: [C0D7AE09: 5064 < 1.152.97.97] HEX: 67670300040072006b
2016-11-03 20:48:52 DEBUG: [C0D7AE09: 5064 > 1.152.97.97] HEX: 67670300020072
2016-11-03 20:51:52 DEBUG: [C0D7AE09: 5064 < 1.152.97.97] HEX: 67670300040073006b
2016-11-03 20:51:52 DEBUG: [C0D7AE09: 5064 > 1.152.97.97] HEX: 67670300020073
2016-11-03 20:54:52 DEBUG: [C0D7AE09: 5064 < 1.152.97.97] HEX: 67670300040074006b
2016-11-03 20:54:52 DEBUG: [C0D7AE09: 5064 > 1.152.97.97] HEX: 67670300020074
2016-11-03 20:57:52 DEBUG: [C0D7AE09: 5064 < 1.152.97.97] HEX: 67670300040075006b
2016-11-03 20:57:52 DEBUG: [C0D7AE09: 5064 > 1.152.97.97] HEX: 67670300020075
2016-11-03 21:00:52 DEBUG: [C0D7AE09: 5064 < 1.152.97.97] HEX: 67670300040076006b
2016-11-03 21:00:52 DEBUG: [C0D7AE09: 5064 > 1.152.97.97] HEX: 67670300020076
2016-11-03 21:03:52 DEBUG: [C0D7AE09: 5064 < 1.152.97.97] HEX: 67670300040077006b
2016-11-03 21:03:52 DEBUG: [C0D7AE09: 5064 > 1.152.97.97] HEX: 67670300020077
2016-11-03 21:06:52 DEBUG: [C0D7AE09: 5064 < 1.152.97.97] HEX: 67670300040078006b
2016-11-03 21:06:52 DEBUG: [C0D7AE09: 5064 > 1.152.97.97] HEX: 67670300020078
2016-11-03 21:09:52 DEBUG: [C0D7AE09: 5064 < 1.152.97.97] HEX: 67670300040079006b
2016-11-03 21:09:52 DEBUG: [C0D7AE09: 5064 > 1.152.97.97] HEX: 67670300020079
2016-11-03 21:12:53 DEBUG: [C0D7AE09: 5064 < 1.152.97.97] HEX: 6767030004007a006b
2016-11-03 21:12:53 DEBUG: [C0D7AE09: 5064 > 1.152.97.97] HEX: 6767030002007a
2016-11-03 21:15:53 DEBUG: [C0D7AE09: 5064 < 1.152.97.97] HEX: 6767030004007b006b
2016-11-03 21:15:53 DEBUG: [C0D7AE09: 5064 > 1.152.97.97] HEX: 6767030002007b
2016-11-03 21:18:53 DEBUG: [C0D7AE09: 5064 < 1.152.97.97] HEX: 6767030004007c006b
2016-11-03 21:18:53 DEBUG: [C0D7AE09: 5064 > 1.152.97.97] HEX: 6767030002007c
2016-11-03 21:21:53 DEBUG: [C0D7AE09: 5064 < 1.152.97.97] HEX: 6767030004007d006b
2016-11-03 21:21:53 DEBUG: [C0D7AE09: 5064 > 1.152.97.97] HEX: 6767030002007d
2016-11-03 21:24:53 DEBUG: [C0D7AE09: 5064 < 1.152.97.97] HEX: 6767030004007e006b
2016-11-03 21:24:53 DEBUG: [C0D7AE09: 5064 > 1.152.97.97] HEX: 6767030002007e
2016-11-03 21:27:53 DEBUG: [C0D7AE09: 5064 < 1.152.97.97] HEX: 6767030004007f006b
2016-11-03 21:27:53 DEBUG: [C0D7AE09: 5064 > 1.152.97.97] HEX: 6767030002007f
2016-11-03 21:30:53 DEBUG: [C0D7AE09: 5064 < 1.152.97.97] HEX: 67670300040080006b
2016-11-03 21:30:53 DEBUG: [C0D7AE09: 5064 > 1.152.97.97] HEX: 67670300020080
2016-11-03 21:33:53 DEBUG: [C0D7AE09: 5064 < 1.152.97.97] HEX: 67670300040081006b
2016-11-03 21:33:53 DEBUG: [C0D7AE09: 5064 > 1.152.97.97] HEX: 67670300020081
2016-11-03 21:36:54 DEBUG: [C0D7AE09: 5064 < 1.152.97.97] HEX: 67670300040082006b
2016-11-03 21:36:54 DEBUG: [C0D7AE09: 5064 > 1.152.97.97] HEX: 67670300020082
2016-11-03 21:39:55 DEBUG: [C0D7AE09: 5064 < 1.152.97.97] HEX: 67670300040083006b
2016-11-03 21:39:55 DEBUG: [C0D7AE09: 5064 > 1.152.97.97] HEX: 67670300020083
2016-11-03 21:42:55 DEBUG: [C0D7AE09: 5064 < 1.152.97.97] HEX: 67670300040084006b
2016-11-03 21:42:55 DEBUG: [C0D7AE09: 5064 > 1.152.97.97] HEX: 67670300020084As far as I can tell, your device doesn't send any GPS data. It's just heartbeat messages.
Hi Anton,
All sorted, seems the device needed a soft reset after changing server address. It is now sending localisation data.
Thank you
Recently purchased a TK119w, which works well with GPSWOX for testing, it identifies the device as "eelink" protocol, however I just recently setup Traccar server, and I receive the following response from log.
Unsure about the unknown device, I have tried adding the IMEI to the web interface however in the log file it is showing as: WARN: Unknown device - IMEI NUMBER OF DEVICE (1.136.96.194). I also tried to convert some of the data using the HEX decoder but its mostly gibberish?
Thank you!