WARN: Data truncation: Incorrect datetime value: '1969-12-31

wbolivar6 years ago

Hi, I have a tk103 tracker and this works with the gt06 protocol, the traccar recognizes it, but it shows me the log errors with wrong date and incorrect position, via sms if it indicates the real unication of the device, I have read some more links I have not found the solution. I am using the latest version of traccar.

regards..

2018-10-08 15:03:15 DEBUG: [b158e321: 5023 < 186.185.129.61] HEX: 78780a134006640001004a60a20d0a
2018-10-08 15:03:15 DEBUG: [b158e321: 5023 > 186.185.129.61] HEX: 78780513004a15260d0a
2018-10-08 15:03:15  WARN: Data truncation: Incorrect datetime value: '1969-12-31 20:00:00' for column 'fixtime' at row 1 - MysqlDataTruncation (... < QueryBuilder:477 < DataManager:453 < DefaultDataHandler:27 < ...)
2018-10-08 15:03:15  INFO: [b158e321] id: 358688800531550, time: 1969-12-31 20:00:00, lat: 0.00000, lon: 0.00000, course: 0.0
2018-10-08 15:03:15  INFO: [b158e321] disconnected
2018-10-08 15:03:17  INFO: [8d915b15] connected
2018-10-08 15:03:17 DEBUG: [8d915b15: 5023 < 186.185.129.61] HEX: 78780d010358688800531550004bb1f40d0a
2018-10-08 15:03:17  WARN: Config parameter gt06.timezone is deprecated
2018-10-08 15:03:17 DEBUG: [8d915b15: 5023 > 186.185.129.61] HEX: 78780501004b34820d0a
Anton Tananaev6 years ago

That's because your device hasn't reported any location and time yet.

wbolivar6 years ago

thank you for answering, the sms via email if you report the location, if I register the same in http://www.gps903.net it shows me the data correctly, but when I register the same in traccar I get the same logs and the erroneous date ?. Any ideas or settings that I need to apply?

Anton Tananaev6 years ago

You need to wait for your device to report a valid location.

wbolivar6 years ago

[You need to wait for your device to report a valid location.] the device when calling it returns me via sms the correct location

Anton Tananaev6 years ago

You shouldn't assume that if device reports location via SMS, it also reports it via data connection. Often it's a wrong assumption.

wbolivar6 years ago

I have sent a reset and after that a fix030s030m *** n + pass and now the device is reporting gprs correctly, my error, the strange thing is because the logs behaved in that way, maybe for being a Chinese clone. thank you very much