wetrack2 issues in version 3.10

Alagappan Karthikeyan8 years ago

Hi
I am using wetrack2, was working fine in older version 3.6, but giving incorrect datetime error in version 3.10

Version 3.6


2017-03-07 00:00:19  INFO: [5DBF34E4] connected
2017-03-07 00:00:21 DEBUG: [5DBF34E4: 5023 < 27.62.44.48] HEX: 787811010867597010451059101c000202a96ba50d0a
2017-03-07 00:00:21 DEBUG: [5DBF34E4: 5023 > 27.62.44.48] HEX: 7878050102a9c32e0d0a
2017-03-07 00:00:24 DEBUG: [5DBF34E4: 5023 < 27.62.44.48] HEX: 78780a13000404000202aa359b0d0a
2017-03-07 00:00:24 DEBUG: [5DBF34E4: 5023 > 27.62.44.48] HEX: 7878051302aac1980d0a
2017-03-07 00:00:25  INFO: [5DBF34E4] id: 867597010451059, time: 2017-03-06 22:30:07, lat: 11.02683, lon: 77.02456, speed: 0.0, course: 0.0
2017-03-07 00:00:27 DEBUG: [5DBF34E4: 5023 < 27.62.44.48] HEX: 787845813d00000000534545464e26260056004900560045004b26263830313532353235333626260041004b0053004b26$
2017-03-07 00:00:30 DEBUG: [5DBF34E4: 5023 < 27.62.44.48] HEX: 78782a812200000000534545534f533a393039353236363831312c2c3930393532363639333323000202ac6cc50d0a
2017-03-07 00:00:32 DEBUG: [5DBF34E4: 5023 < 27.62.44.48] HEX: 78789a8194000000004354524c504152414d533a4754494d45523d313b54494d45523d31302c33303b5057524c494d4954$

version 3.10


2017-03-07 07:33:08  INFO: [AB1142FB] connected
2017-03-07 07:33:09 DEBUG: [AB1142FB: 5023 < 27.62.8.61] HEX: 787811010867597010451059101c000200c285c00d0a
2017-03-07 07:33:09 DEBUG: [AB1142FB: 5023 > 27.62.8.61] HEX: 7878050100c22d4b0d0a
2017-03-07 07:33:12 DEBUG: [AB1142FB: 5023 < 27.62.8.61] HEX: 78780a13000603000200c3c0660d0a
2017-03-07 07:33:12 DEBUG: [AB1142FB: 5023 > 27.62.8.61] HEX: 7878051300c30cef0d0a
2017-03-07 07:33:12  WARN: Data truncation: Incorrect datetime value: '1970-01-01 01:00:00' for column 'fixtime' at row 1 - MysqlDataTruncation (... < QueryBuild$
2017-03-07 07:33:12  INFO: [AB1142FB] id: 867597010451059, time: 1970-01-01 01:00:00, lat: 0.00000, lon: 0.00000, speed: 0.0, course: 0.0
Anton Tananaev8 years ago

Your device didn't send any GPS data, so Traccar uses zeroes for everything. MySQL doesn't support zeroes for timestamps. The problem has nothing to do with version of Traccar.