I'm sending GPS-data to demo2.traccar.org:5039 via Wialon IPS rotocol (v1.0), and the server doesn't respond (in time) to #SD packet, though it does respond to #L packet.
Here is the debug log (UTC+3):
16:37:22.510 DEBUG #0 >6: #L#45411???;NA
16:37:22.698 DEBUG #0 >6: response: <Buffer 23 41 4c 23 31 0d 0a>
16:37:22.698 LOG #0 >6: logged in as cid 45411???
16:37:22.698 DEBUG #0 >6: #SD#180824;133700;5458.887300;N;07319.189860;E;0;25;0;11
16:37:29.699 ERROR #0 >6: timeout cid: 45411215
The timeout is set to 7 seconds, and I had to increase it from 3 seconds, which is usually enough for other servers.
Nevertheless the position is updated on the map, though it is inaccurate - 54.985066°;73.313600°, while it should be 54.981455,73.319831.
And the timestamp deviceTime: 18/08/2024, 19:07:54 is also inaccurate and in the future (I view it through the browser at UTC+5).
Same packets are processed correctly when sent via Wialon IPS to livegpstracks.com, so I guess it is a kind of issue with the Traccar Server instance (at demo2).
We don't provide support for demo servers, but if you have your own instance of Traccar, try on it and see what you get in the logs.
Thanks for the quick reply.
I thought the code is the same for all servers, so the issue may be relevant for any instance of Traccar Server.
The code is the same, but to see if it's a problem, we need to see the logs.
@AntonK
I wonder why still after six years you are still fiddling with demo servers. Isnt it time for the next step ?
I'm sending GPS-data to demo2.traccar.org:5039 via Wialon IPS rotocol (v1.0), and the server doesn't respond (in time) to
#SDpacket, though it does respond to#Lpacket.Here is the debug log (UTC+3):
The timeout is set to 7 seconds, and I had to increase it from 3 seconds, which is usually enough for other servers.
Nevertheless the position is updated on the map, though it is inaccurate -
54.985066°;73.313600°, while it should be54.981455,73.319831.And the timestamp
deviceTime: 18/08/2024, 19:07:54is also inaccurate and in the future (I view it through the browser at UTC+5).Same packets are processed correctly when sent via Wialon IPS to livegpstracks.com, so I guess it is a kind of issue with the Traccar Server instance (at demo2).