HEX data parced correctly but server show wrong position

Yuriy R8 years ago

Hi

after update from 3.7 to 3.15 I got problem with display position of device.

here is example from server log

2018-01-17 10:50:56  INFO: [3B1A7389] id: 4208115320, time: 2018-01-17 10:50:52, lat: 49.98680, lon: 36.26013, speed: 0.0, course: 0.0
2018-01-17 10:51:57 DEBUG: [3B1A7389: 5013 < 46.133.1.185] HEX: 2442081153200851521701184959208006036156080e000000fffffbffff001a080000509500ff010000000004
2018-01-17 10:51:57  WARN: Geocoding failed - General SSLEngine problem - ConnectException (...)
2018-01-17 10:51:57  INFO: [3B1A7389] id: 4208115320, time: 2018-01-17 10:51:52, lat: 49.98680, lon: 36.26013, speed: 0.0, course: 0.0
2018-01-17 10:52:58 DEBUG: [3B1A7389: 5013 < 46.133.1.185] HEX: 2442081153200852521701184959208006036156080e000000fffffbffff001a070000509500ff010000000005
2018-01-17 10:52:58  WARN: Geocoding failed - General SSLEngine problem - ConnectException (...)
2018-01-17 10:52:58  INFO: [3B1A7389] id: 4208115320, time: 2018-01-17 10:52:52, lat: 49.98680, lon: 36.26013, speed: 0.0, course: 0.0

But in interface car show in ocean
Link

Protocol checked it is correct and server parsed with correct coordinates
Other devices show correctly on this server with different protocol.

Also Tracker return to me google link with correct location.

Please advice what can be wrong.
Thanks

Anton Tananaev8 years ago

Your device reported invalid data in the past. This is a very common issue and has been discussed many times on forum. Use search.