Wrong port. Correct is 5023. Please read documentation next time.
Thanks Anton
Anton, as a follow up:
I had previously used port 5023 with no response.
In trying it back just now, the following event was logged:
2020-03-13 12:17:11 INFO: [f811af82: gt06 < 173.225.243.138] HEX: 78780d01035231209064591500045b980d0a
2020-03-13 12:17:11 WARN: Unknown device - 352312090645915 (173.225.243.138)
2020-03-13 12:24:43 INFO: [a530af81] connected
2020-03-13 12:24:43 INFO: [a530af81: gt06 < 173.225.243.141] HEX: 78780d01035231209064591500010c350d0a
2020-03-13 12:24:43 INFO: [a530af81: gt06 > 173.225.243.141] HEX: 787805010001d9dc0d0a
Additionally, the Hex output for (78780d01035231209064591500010c350d0a) is as follows:
[binary data]
Could you shed some light as to possible cause?
Please stop trying to use HEX decoder for a binary protocol.
Hi, I'm having an issue with a tracker reporting to my windows based traccar server:
Hex Message Output:
[binary data]