Problem with periodic reporting

rickymarley9 years ago

I think there's a bug with the periodic reporting. It doesn't matter if i choose Seconds, Minutes or Hours the unit is always seconds. For example when i setup the period to 5 minutes or 30 minutes i receive an update every 5 or 30 seconds. Does someone else has experienced this problem???

Anton Tananaev9 years ago

Please provide part of the tracker-server.log file where you send command to the device. It should include command in HEX format.

rickymarley9 years ago

There is the part of the tracker-server.log [Setting: 5 minutes]

But as you can see...

2015-10-08 12:53:19  INFO: [A530457F] connected
2015-10-08 12:53:19 DEBUG: [A530457F: 5001 < 190.102.86.243] HEX: 474554202f3f69643d3335333932323035373034333339382674696d657374616d703d31343434333236323937266c61743d31382e35313138383734266c6f6e3d2d37322e323835393336392673706565643d302e302662656172696e673d302e3026616c7469747564653d302e3026626174743d36342e3020485454502f312e310d0a557365722d4167656e743a2044616c76696b2f312e362e3020284c696e75783b20553b20416e64726f696420342e312e323b2047542d4939333030204275696c642f4a5a4f35344b290d0a486f73743a203130382e3137392e3230362e3135323a353030310d0a436f6e6e656374696f6e3a204b6565702d416c6976650d0a4163636570742d456e636f64696e673a20677a69700d0a0d0a
2015-10-08 13:01:10  INFO: [FE4C1CEA] connected
2015-10-08 13:01:10 DEBUG: [FE4C1CEA: 5001 < 200.113.238.35] HEX: 23232c696d65693a3335393731303034383030343230352c413b
2015-10-08 13:01:10 DEBUG: [FE4C1CEA: 5001 > 200.113.238.35] HEX: 4c4f4144
2015-10-08 13:01:19 DEBUG: [FE4C1CEA: 5001 > 200.113.238.35] HEX: 2a2a2c696d65693a3335393731303034383030343230352c432c30356d3b
2015-10-08 13:01:29 DEBUG: [FE4C1CEA: 5001 < 200.113.238.35] HEX: 696d65693a3335393731303034383030343230352c68656c70206d652c3135313030383133303131392c2c462c3138303131392e3030302c412c313833302e373036362c4e2c30373231372e313538322c572c302e30302c303b
2015-10-08 13:01:29 DEBUG: [FE4C1CEA: 5001 > 200.113.238.35] HEX: 2a2a2c696d65693a3335393731303034383030343230352c453b
2015-10-08 13:01:29  INFO: [FE4C1CEA] id: 4, time: Thu Oct 08 13:01:19 CDT 2015, lat: 18.511776666666666, lon: -72.28597, speed: 0.0, course: 0.0
2015-10-08 13:01:29 DEBUG: [FE4C1CEA: 5001 < 200.113.238.35] HEX: 696d65693a3335393731303034383030343230352c747261636b65722c3135313030383133303132302c2c462c3138303132312e3030302c412c313833302e373036362c4e2c30373231372e313538322c572c302e30302c303b
2015-10-08 13:01:29  INFO: [FE4C1CEA] id: 4, time: Thu Oct 08 13:01:21 CDT 2015, lat: 18.511776666666666, lon: -72.28597, speed: 0.0, course: 0.0
2015-10-08 13:01:29 DEBUG: [FE4C1CEA: 5001 < 200.113.238.35] HEX: 696d65693a3335393731303034383030343230352c747261636b65722c3135313030383133303132352c2c462c3138303132362e3030302c412c313833302e373036362c4e2c30373231372e313538322c572c302e30302c303b
Anton Tananaev9 years ago

This is the decoded command from your log:

**,imei:359710048004205,C,05m;

As you can see the command is correct. Interval is set to 5 minutes, so I guess there is some issue on the device side.

rickymarley9 years ago

Thanks man... i really appreciate your help.. I will try with another device and i'll let you know...

Great work by the way... Keep it up...