GT06 position time issue

Parth5 years ago

Hello Anton,

Greeting for the Day !

We are using GT06 type of devices, and device send the data perfectly with the time when device is in motion, but when device is parked the device
is sending only the heartbeat kind of login package without any location and time info. Due to that the user get the device time as older one
when access the device and have feel that the device doesn't have any data from long time. How we can handle this issue?

Can we have server data insert time in this place?

Below is the Log for the problem:

2019-04-11 18:29:50  INFO: [5f332d85: 5023 < 106.77.28.94] HEX: 7878222213040b121d30cb027991a407cb84e91514300194183aac002e2f01000001e5ed660d0a
2019-04-11 18:29:50  INFO: [5f332d85: 5023 > 106.77.28.94] HEX: 7878052201e58d710d0a
2019-04-11 18:29:50  INFO: [5f332d85] id: 866551036222417, time: 2019-04-11 18:29:48, lat: 23.06754, lon: 72.65464, speed: 11.3, course: 48.0
2019-04-11 18:29:52  INFO: [5f332d85: 5023 < 106.77.28.94] HEX: 7878222213040b121d32cb0279922807cb85ad1914360194183aac002e2f01000001e652440d0a
2019-04-11 18:29:52  INFO: [5f332d85: 5023 > 106.77.28.94] HEX: 7878052201e6bfea0d0a
2019-04-11 18:29:52  INFO: [5f332d85] id: 866551036222417, time: 2019-04-11 18:29:50, lat: 23.06761, lon: 72.65475, speed: 13.5, course: 54.0
2019-04-11 18:30:00  INFO: [5f332d85: 5023 < 106.77.28.94] HEX: 7878222213040b121d3acb0279939307cb879c0714270194183aac002e2f01000001e713dc0d0a
2019-04-11 18:30:00  INFO: [5f332d85: 5023 > 106.77.28.94] HEX: 7878052201e7ae630d0a
2019-04-11 18:30:00  INFO: [5f332d85] id: 866551036222417, time: 2019-04-11 18:29:58, lat: 23.06782, lon: 72.65502, speed: 3.8, course: 39.0
2019-04-11 18:30:29  INFO: [5f332d85: 5023 < 106.77.28.94] HEX: 78780a1344f004870201e87cd50d0a
2019-04-11 18:30:29  INFO: [5f332d85: 5023 > 106.77.28.94] HEX: 7878051301e88ae60d0a
2019-04-11 18:30:29  INFO: [5f332d85] id: 866551036222417, time: 2019-04-11 18:29:58, lat: 23.06782, lon: 72.65502, speed: 3.8, course: 39.0
2019-04-11 18:35:29  INFO: [5f332d85: 5023 < 106.77.28.94] HEX: 78780a1305f0047f0201e9a77c0d0a
2019-04-11 18:35:29  INFO: [5f332d85: 5023 > 106.77.28.94] HEX: 7878051301e99b6f0d0a
2019-04-11 18:35:29  INFO: [5f332d85] id: 866551036222417, time: 2019-04-11 18:29:58, lat: 23.06782, lon: 72.65502, speed: 3.8, course: 39.0
2019-04-11 18:40:29  INFO: [5f332d85: 5023 < 106.77.28.94] HEX: 78780a1305f0047e0201ea895c0d0a
2019-04-11 18:40:29  INFO: [5f332d85: 5023 > 106.77.28.94] HEX: 7878051301eaa9f40d0a
2019-04-11 18:40:29  INFO: [5f332d85] id: 866551036222417, time: 2019-04-11 18:29:58, lat: 23.06782, lon: 72.65502, speed: 3.8, course: 39.0
2019-04-11 18:45:29  INFO: [5f332d85: 5023 < 106.77.28.94] HEX: 78780a1305f0047e0201eb98d50d0a
2019-04-11 18:45:29  INFO: [5f332d85: 5023 > 106.77.28.94] HEX: 7878051301ebb87d0d0a
2019-04-11 18:45:29  INFO: [5f332d85] id: 866551036222417, time: 2019-04-11 18:29:58, lat: 23.06782, lon: 72.65502, speed: 3.8, course: 39.0
2019-04-11 18:50:29  INFO: [5f332d85: 5023 < 106.77.28.94] HEX: 78780a1305f0047e0201ecec6a0d0a
2019-04-11 18:50:29  INFO: [5f332d85: 5023 > 106.77.28.94] HEX: 7878051301ecccc20d0a
2019-04-11 18:50:29  INFO: [5f332d85] id: 866551036222417, time: 2019-04-11 18:29:58, lat: 23.06782, lon: 72.65502, speed: 3.8, course: 39.0
2019-04-11 18:55:29  INFO: [5f332d85: 5023 < 106.77.28.94] HEX: 78780a1305f0047f0201ede1580d0a
2019-04-11 18:55:29  INFO: [5f332d85: 5023 > 106.77.28.94] HEX: 7878051301eddd4b0d0a
2019-04-11 18:55:29  INFO: [5f332d85] id: 866551036222417, time: 2019-04-11 18:29:58, lat: 23.06782, lon: 72.65502, speed: 3.8, course: 39.0
2019-04-11 19:00:29  INFO: [5f332d85: 5023 < 106.77.28.94] HEX: 78780a1305f0047f0201eed3c30d0a
2019-04-11 19:00:29  INFO: [5f332d85: 5023 > 106.77.28.94] HEX: 7878051301eeefd00d0a
Anton Tananaev5 years ago

If you are talking about the fix time, it doesn't make sense to change it.

Parth5 years ago

How to add change to front end to display the server time(Data insert time) as well in attributes with fix time so that the user can have the idea that the device is parked and last time it send the heartbeat is at this time.

Arvind5 years ago

You don't have to change any file, all just need to set correct device time. Check you command with manual and set UTC. If device is moving it will auto send correct time.