EELINK TK121 with UDP Protocol fails to connect
There is a response. Is it incorrect?
There should be a response from the server, but I receive only response on heartbeat packets on TCP protocol, not on UDP.
Logs?
Actually the device doesn't reach the server in UDP, it doesn't appear on logs. Look following line, are the device I'm testing, and what the server receivied when in TCP:
2021-02-03 16:43:22 INFO: [a7b266e8] connected
2021-02-03 16:43:24 INFO: [a7b266e8: 5064 < 34.230.244.239] HEX: 67670100180002035254407561261501f4020912090001044600779b5f
2021-02-03 16:43:24 INFO: [a7b266e8: 5064 > 34.230.244.239] HEX: 67670100020002
2021-02-03 16:43:26 INFO: [a7b266e8: 5064 < 34.230.244.239] HEX: 676715000a0001601ad2cb0002046a67671200340003601ad2aa0202d40005026600005a502a046a118604d70000000000010046004600000000
000000000000000000000000fce0676712003400046b64aa2a0202d40005026600005a502a046a118804df0000000000010046004600000000000000000000000000000000fce0
2021-02-03 16:43:26 INFO: [a7b266e8: 5064 > 34.230.244.239] HEX: 67671500020001
2021-02-03 16:43:26 INFO: [a7b266e8] id: 352544075612615, time: 1970-01-01 00:00:00, lat: 0.00000, lon: 0.00000, course: 0.0
2021-02-03 16:43:26 INFO: [a7b266e8: 5064 > 34.230.244.239] HEX: 67671200020003
2021-02-03 16:43:26 INFO: [a7b266e8] id: 352544075612615, time: 1970-01-01 00:00:00, lat: 0.00000, lon: 0.00000, course: 0.0
2021-02-03 16:43:26 INFO: [a7b266e8: 5064 > 34.230.244.239] HEX: 67671200020004
2021-02-03 16:43:26 INFO: [a7b266e8] id: 352544075612615, time: 1970-01-01 00:00:00, lat: 0.00000, lon: 0.00000, course: 0.0
2021-02-03 16:43:56 INFO: [a7b266e8: 5064 < 34.230.244.239] HEX: 67670300040005046a
2021-02-03 16:43:56 INFO: [a7b266e8: 5064 > 34.230.244.239] HEX: 67670300020005
2021-02-03 16:43:57 INFO: [a7b266e8] id: 352544075612615, time: 1970-01-01 00:00:00, lat: 0.00000, lon: 0.00000, course: 0.0
2021-02-03 16:44:26 INFO: [a7b266e8: 5064 < 34.230.244.239] HEX: 67670300040006046a
2021-02-03 16:44:26 INFO: [a7b266e8: 5064 > 34.230.244.239] HEX: 67670300020006
2021-02-03 16:44:26 INFO: [a7b266e8] id: 352544075612615, time: 1970-01-01 00:00:00, lat: 0.00000, lon: 0.00000, course: 0.0
2021-02-03 16:44:56 INFO: [a7b266e8: 5064 < 34.230.244.239] HEX: 67670300040007046a
2021-02-03 16:44:56 INFO: [a7b266e8: 5064 > 34.230.244.239] HEX: 67670300020007
2021-02-03 16:44:56 INFO: [a7b266e8] id: 352544075612615, time: 1970-01-01 00:00:00, lat: 0.00000, lon: 0.00000, course: 0.0
2021-02-03 16:45:17 INFO: [a7b266e8] disconnected
The date is wrong because I'm inside a buiding and it didn't updated with GNSS.
So, basically everything you said previously is incorrect?
Yes, you are right!
The problem is not the server doesn't answer, it is the device doesn't connect to the server on UDP, but I can't understand why.
I talked to the manufacturer, it said it don't connect because it on the side of the server, it goes right on TCP, but not in UDP! I thought you, or someone else, could've been trough this too. It's specificalli with eelink, coban TK303, worked very well on UDP.
But thanks for answering Anton!
Maybe you are using an outdated version? Or maybe firewall or some other network issue?
Hi Anton, thank you very much, and sorry for so basic question. That was the firewall.
Regards.
Hello, I'm trying to use the TK121 of EELINK with the UDP protocol.
With TCP it works very well, but I have an issue that it loses some packets because of the poor conection, and the device depends on miss 3 heartbeat packets (not the location packet) without server answer until it stops send data and start to store the data. Summing up, the connection between device and server rely only on the heartbeat packets.
So, looking at the protocol manual from eelink, I found that UDP protocol doesn't have heartbeat message, but the server must respond back for each location packet before the device sends the next package. It will make the information much more accurate.
The problem I'm having now is to connect the device with the server working with UDP. I use the 5064 port, that is the default for eelink, but no answer.
Anyone knows how to make this communication works? Is there some specific configuration on server side? Or is there another port to use? The server doesn't really supports UDP eelink protocol?
Thanks all.