Have you followed troubleshooting guide? Is there anything in the logs?
yes. that i told. i followed step by step. i paste part of log. at the log don`t recognize the id (i think so).. im running a couple of trackers to discard hardware or sim problems, but its the same results on both.
the HEX its "similar but not equal" than tk103. may be its the problem..
2020-12-29 15:20:13 INFO: [0298f8b9: gt06 < 186.141.197.12] HEX: 78780a134406040000004278f30d0a
2020-12-29 15:20:13 INFO: [0298f8b9: gt06 > 186.141.197.12] HEX: 787805130042996e0d0a
2020-12-29 15:20:13 INFO: [0298f8b9] id: 352887079738948, time: 2020-12-29 15:19:19, lat: -26.82710, lon: -65.21191, course: 0.0
2020-12-29 15:20:19 INFO: [16b1bc1f: gps103 < 186.143.202.185] HEX: 283032373034343938323737354252303032303132323941323634382e383337385330363534332e33363430573030302e313138323031373030302e303030313030303030304c303030303030303029
2020-12-29 15:20:21 INFO: [0298f8b9: gt06 < 186.141.197.12] HEX: 78781f12140c1d121413c602e0d3fd06ff1a2500180002d2070c1d000b73004351630d0a
2020-12-29 15:20:21 INFO: [0298f8b9: gt06 > 186.141.197.12] HEX: 787805120043d23b0d0a
2020-12-29 15:20:21 INFO: [0298f8b9] id: 352887079738948, time: 2020-12-29 15:20:19, lat: -26.82709, lon: -65.21204, course: 0.0
2020-12-29 15:20:27 INFO: [16b1bc1f: gps103 < 186.143.202.185] HEX: 283032373034343938323737354250303033353532323730343439383237373548534f31393929
2020-12-29 15:21:05 INFO: [4328a67a: gps103 < 186.141.202.241] HEX: 283032383034323537333535384252303032303132323941323635302e303139315330363531322e39313935573030302e303138323130333139322e303330313030303030304c303030303030303029
2020-12-29 15:21:19 INFO: [16b1bc1f: gps103 < 186.143.202.185] HEX: 283032373034343938323737354252303032303132323941323634382e383337305330363534332e33363435573030302e303138323131373030302e303030313030303030304c303030303030303029
2020-12-29 15:21:21 INFO: [0298f8b9: gt06 < 186.141.197.12] HEX: 78781f12140c1d121513c602e0d3a906ff194301180002d2070c1d000b73004484d90d0a
2020-12-29 15:21:21 INFO: [0298f8b9: gt06 > 186.141.197.12] HEX: 787805120044a6840d0a
2020-12-29 15:21:21 INFO: [0298f8b9] id: 352887079738948, time: 2020-12-29 15:21:19, lat: -26.82705, lon: -65.21191, speed: 0.5, course: 0.0
2020-12-29 15:21:48 INFO: [4328a67a: gps103 < 186.141.202.241] HEX: 283032383034323537333535384250303033353532323830343235373335353848534f31393929
2020-12-29 15:22:05 INFO: [4328a67a: gps103 < 186.141.202.241] HEX: 283032383034323537333535384252303032303132323941323635302e303139305330363531322e39313934573030302e303138323230333139322e303330313030303030304c303030303030303029
2020-12-29 15:22:09 INFO: [4328a67a] disconnected
2020-12-29 15:22:09 INFO: [d9c06b02] connected
2020-12-29 15:22:09 INFO: [d9c06b02: gps103 < 186.141.202.241] HEX: 283032383034323537333535384250303533353532323830343235373335353832303132323941323635302e303139305330363531322e39313934573030302e303138323230333139322e303330313030303030304c303030303030303029
2020-12-29 15:22:19 INFO: [16b1bc1f: gps103 < 186.143.202.185] HEX: 283032373034343938323737354252303032303132323941323634382e383336395330363534332e33363533573030302e313138323231373030302e303030313030303030304c303030303030303029
2020-12-29 15:22:22 INFO: [0298f8b9: gt06 < 186.141.197.12] HEX: 78781f12140c1d121613c602e0d3cd06ff19bf00180002d2070c1d000b7300450b9d0d0a
2020-12-29 15:22:22 INFO: [0298f8b9: gt06 > 186.141.197.12] HEX: 787805120045b70d0d0a
2020-12-29 15:22:22 INFO: [0298f8b9] id: 352887079738948, time: 2020-12-29 15:22:19, lat: -26.82706, lon: -65.21198, course: 0.0
look a couple of gps103....
thanks in advance
So, you think it's similar to TK103 and yet you provide a log that uses completely different port. Makes no sense to me.
Hi!. (first..... i read a ..../clones and i tested all ports ...), and not work. following the instructions. i compared the HEX datagram, and its similar to:
but, when i use 5001, 5002, 5006,5013,5015,5023,5036,5093. nothing happends
any idea?
thanks!
Augusto