StrangeMan chol Yes, date and time in same interval (UTC), and next time every second unit transmitting and receiving data on/to service, until power off device at 2019-11-11 02:21 UTC. 27 kilometers trip. Device ID: 9139139126 , model Autoscan A-100 (3-wire connector, blue wire +12V and input 3 set to Ignition).
StrangeMan chol Today can’t bring up to online that tracker (Device ID: 9139139126 , model Autoscan A-100 , took for temporary use). But, another tracker model Автоскан-Трек Device ID: 359772036581529 , is still online. As I see it rarely sends GPS-data coordinates, although the connection to the server is established and regularly reconnected. Packet with GPS-data: Incorrect SDATE:
StrangeMan chol Yes, several packets with accumulated data were sent (1024 byte in this example). By the way, how to insert a picture normally? https://ibb.co/wr3WZvc In normal mode, the tracker sends packets more often and one position per packet: 36 bytes: https://ibb.co/d0RsXtc
StrangeMan In TOOLBOX-column “server.timestamp” date and time recived data started every day at 06:05. After a minute or two, the reception of data stops. The next day, the server again receives packets from the tracker at 06:05 and again stops. This is normal? The analysis of ip packets from the tracker to the server shows the regular sending and receiving of geoposition data (every 5…12 seconds when driving and 10…15 minutes in the parking lot). At the TCP-protocol level, communication works fine. Does the server not accept data until the parser is restarted daily at 06:00?
StrangeMan No: Track AutoScan5 15/11/2019 00:00 - 15/11/2019 14:11 Something went wrong while executing request. Retry load data. “TOOLBOX” also unavailable.
StrangeMan Track AutoScan5 15/11/2019 00:00 - 15/11/2019 14:11 No messages for the specified period. Change intrerval
StrangeMan Good work! Get small trip, track showed correctly! Thank you for support. On Monday I will continue testing. Hope my help was helpful. I wish you success with your project!