It means that your timeout value is too low.
As for decoding issue, it's because you are using wrong port. Correct port for your device is 5002; device id - 027045193026.
The device ID is correct.
I change the port. I hope it will be good. :)
Thank you very very much!!! :)
Already Online. :)
2018-04-25 10:22:33 INFO: [EFF0DC7B] connected
2018-04-25 10:22:34 DEBUG: [EFF0DC7B: 5002 < 37.76.67.98] HEX: 283032373034353139333032364252303030303030303756303030302e303030304e30303030302e30303030453030302e30303031343033393930303030303030304c303030303030303029
2018-04-25 10:22:34 INFO: [EFF0DC7B] id: 027045193026, time: 1999-12-07 01:14:03, lat: 0.00000, lon: 0.00000, speed: 0.0, course: 9900000000.0
2018-04-25 10:22:35 DEBUG: [EFF0DC7B: 5002 < 37.76.67.98] HEX: 283032373034353139333032364250303030303030323730343531393330323648534f29
2018-04-25 10:22:35 DEBUG: [EFF0DC7B: 5002 > 37.76.67.98] HEX: 283032373034353139333032364150303148534f29
2018-04-25 10:27:33 DEBUG: [EFF0DC7B: 5002 < 37.76.67.98] HEX: 283032373034353139333032364250303030303030323730343531393330323648534f29
2018-04-25 10:27:33 DEBUG: [EFF0DC7B: 5002 > 37.76.67.98] HEX: 283032373034353139333032364150303148534f29
2018-04-25 10:32:33 DEBUG: [EFF0DC7B: 5002 < 37.76.67.98] HEX: 283032373034353139333032364250303030303030323730343531393330323648534f29
2018-04-25 10:32:33 DEBUG: [EFF0DC7B: 5002 > 37.76.67.98] HEX: 283032373034353139333032364150303148534f29
2018-04-25 10:37:34 DEBUG: [EFF0DC7B: 5002 < 37.76.67.98] HEX: 283032373034353139333032364250303030303030323730343531393330323648534f29
2018-04-25 10:37:34 DEBUG: [EFF0DC7B: 5002 > 37.76.67.98] HEX: 283032373034353139333032364150303148534f29
2018-04-25 10:37:36 INFO: [9C18E97C] connected
2018-04-25 10:37:37 DEBUG: [9C18E97C: 5002 < 37.76.67.98] HEX: 283032373034353139333032364252303030303030303756303030302e303030304e30303030302e30303030453030302e30303031343033393930303030303030304c303030303030303029
2018-04-25 10:37:37 INFO: [9C18E97C] id: 027045193026, time: 1999-12-07 01:14:03, lat: 0.00000, lon: 0.00000, speed: 0.0, course: 9900000000.0
2018-04-25 10:37:37 DEBUG: [9C18E97C: 5002 < 37.76.67.98] HEX: 283032373034353139333032364250303030303030323730343531393330323648534f29
2018-04-25 10:37:37 DEBUG: [9C18E97C: 5002 > 37.76.67.98] HEX: 283032373034353139333032364150303148534f29
How did you know I used a bad port?
This is not in the list.
You should carefully read text at the top. Specifically about cheap Chinese devices.
hi @anton tananaev, do you know what's happaning with my gps tk103B?, I have configurated with port 5023. Thank you very much again friend!
2019-10-25 16:52:55 INFO: [ea4018b6] connected
2019-10-25 16:53:04 INFO: [ea4018b6: gt06 < 200.68.140.21] HEX: 78780d0103578570450535940004c8a80d0a
2019-10-25 16:53:04 INFO: [ea4018b6: gt06 > 200.68.140.21] HEX: 7878050100048e710d0a
2019-10-25 16:53:05 INFO: [ea4018b6: gt06 < 200.68.140.21] HEX: 78780d0103578570450535940004c8a80d0a
2019-10-25 16:53:05 INFO: [ea4018b6: gt06 > 200.68.140.21] HEX: 7878050100048e710d0a
2019-10-25 16:53:07 INFO: [fd7afb09] timed out
2019-10-25 16:53:07 INFO: [fd7afb09] disconnected
2019-10-25 16:55:05 INFO: [ea4018b6] timed out
2019-10-25 16:55:05 INFO: [ea4018b6] disconnected
2019-10-25 16:55:22 INFO: [928b0f39] connected
2019-10-25 16:55:24 INFO: [928b0f39: stl060 < 104.206.128.38] HEX: 4f5054494f4e53207369703a6361726f6c406368696361676f2e636f6d205349502f322e300d0a5669613a205349502f322e302f55445020706333332e61746c616e74612e636f6d3b6272616e63683d7a39684734624b686a6873386173733837370d0a4d61782d466f7277617264733a2037300d0a546f3a203c7369703a6361726f6c406368696361676f2e636f6d3e0d0a46726f6d3a20416c696365203c7369703a616c6963654061746c616e74612e636f6d3e3b7461673d313932383330313737340d0a43616c6c2d49443a2061383462346337366536363731300d0a435365713a203633313034204f5054494f4e530d0a436f6e746163743a203c7369703a616c69636540706333332e61746c616e74612e636f6d3e0d0a4163636570743a206170706c69636174696f6e2f7364700d0a436f6e74656e742d4c656e6774683a20300d0a0d0a
2019-10-25 16:55:51 INFO: [b63219ae] connected
2019-10-25 16:55:54 WARN: [928b0f39] error - Connection reset by peer - IOException (...)
2019-10-25 16:55:54 INFO: [928b0f39] disconnected
2019-10-25 16:56:00 INFO: [b63219ae: gt06 < 200.68.140.26] HEX: 78780d0103578570450535940005d9210d0a
2019-10-25 16:56:00 INFO: [b63219ae: gt06 > 200.68.140.26] HEX: 7878050100059ff80d0a
2019-10-25 16:56:01 INFO: [b63219ae: gt06 < 200.68.140.26] HEX: 78780d0103578570450535940005d9210d0a
2019-10-25 16:56:01 INFO: [b63219ae: gt06 > 200.68.140.26] HEX: 7878050100059ff80d0a
2019-10-25 16:58:01 INFO: [b63219ae] timed out
2019-10-25 16:58:01 INFO: [b63219ae] disconnected
2019-10-25 16:58:49 INFO: [d659891b] connected
2019-10-25 16:59:01 INFO: [d659891b: gt06 < 200.68.140.40] HEX: 78780d0103578570450535940006ebba0d0a78780d0103578570450535940006ebba0d0a
2019-10-25 16:59:01 INFO: [d659891b: gt06 > 200.68.140.40] HEX: 787805010006ad630d0a
2019-10-25 16:59:01 INFO: [d659891b: gt06 > 200.68.140.40] HEX: 787805010006ad630d0a
2019-10-25 16:59:34 INFO: [d659891b] disconnected
2019-10-25 16:59:48 INFO: [61bbd1d6] connected
2019-10-25 17:00:09 INFO: [61bbd1d6: stl060 < 200.68.141.14] HEX: 78780d0103578570450535940007fa330d0a78781f12130a19103b20c902c359c00ac22412003c00014e140535007e9d00011ab40d0a78781f12130a19103b2fc902c359c00ac22412003c00014e140535007e9d0002e36f0d0a
2019-10-25 17:01:36 INFO: [61bbd1d6: stl060 < 200.68.141.14] HEX: 78780a1340065f0001000892890d0a
2019-10-25 17:01:45 INFO: [61bbd1d6: stl060 < 200.68.141.14] HEX: 78780d0103578570450535940009134d0d0a
2019-10-25 17:02:54 INFO: [61bbd1d6] disconnected
2019-10-25 17:04:22 INFO: [d0fb8cc3] connected
2019-10-25 17:04:31 INFO: [d0fb8cc3: gt06 < 200.68.140.32] HEX: 78780d010357857045053594000b305f0d0a78781f12130a19110235c902c359c00ac22412003c00014e14053500578e00037ea30d0a78780d010357857045053594000b305f0d0a
2019-10-25 17:04:31 INFO: [d0fb8cc3: gt06 > 200.68.140.32] HEX: 78780501000b76860d0a
2019-10-25 17:04:31 INFO: [d0fb8cc3: gt06 > 200.68.140.32] HEX: 787805120003903f0d0a
2019-10-25 17:04:31 INFO: [d0fb8cc3] id: 357857045053594, time: 2019-10-25 17:02:53, lat: 25.75385, lon: -100.27521, course: 0.0
2019-10-25 17:04:31 INFO: [d0fb8cc3: gt06 > 200.68.140.32] HEX: 78780501000b76860d0a
2019-10-25 17:04:32 INFO: [d0fb8cc3: gt06 < 200.68.140.32] HEX: 78780a134006610001000b157b0d0a
2019-10-25 17:04:32 INFO: [d0fb8cc3: gt06 > 200.68.140.32] HEX: 78780513000b46ab0d0a
2019-10-25 17:04:32 INFO: [d0fb8cc3] id: 357857045053594, time: 2019-10-25 17:02:53, lat: 25.75385, lon: -100.27521, course: 0.0
2019-10-25 17:04:35 INFO: [d0fb8cc3: gt06 < 200.68.140.32] HEX: 78781f12130a1911040dc802c359c00ac22412003c00014e14053500578e000472fd0d0a
2019-10-25 17:04:35 INFO: [d0fb8cc3: gt06 > 200.68.140.32] HEX: 787805120004e4800d0a
2019-10-25 17:04:35 INFO: [d0fb8cc3] id: 357857045053594, time: 2019-10-25 17:04:13, lat: 25.75385, lon: -100.27521, course: 0.0
2019-10-25 17:06:35 INFO: [d0fb8cc3] timed out
2019-10-25 17:06:35 INFO: [d0fb8cc3] disconnected
2019-10-25 17:07:33 INFO: [3dea3816] connected
2019-10-25 17:07:43 INFO: [3dea3816: gt06 < 200.68.141.35] HEX: 78780d010357857045053594000d55690d0a
2019-10-25 17:07:43 INFO: [3dea3816: gt06 > 200.68.141.35] HEX: 78780501000d13b00d0a
2019-10-25 17:09:43 INFO: [3dea3816] timed out
2019-10-25 17:09:43 INFO: [3dea3816] disconnected
I would like to ask for your help.
The log is full of data but can not process it. The TK106 is showing OFFLINE. :-(
What could be the problem? What do I do to see the TK106?