Zero coordinates

kostas1257 years ago

Hello

I have 2 trackers lk209. One of them it works just fine. The other one is connected to the server but the it reports always zero coordinates as you can see on log. I thought that the problem was on tracker but when I call him I receive an sms reporting the correct location. I use port 5013. Any thoughts? Thanks!!

2018-03-31 16:33:48  INFO: [C621AAFE] id: 4209156789, time: 2018-03-31 03:34:01, lat: 0.00000, lon: 0.00000, speed: 0.0, course: 0.0

2018-03-31 16:34:53 DEBUG: [471FFDAD: 5013 < 62.74.4.245] HEX: 2a48512c343230393039303631362c56312c3133333334372c412c333735332e343931332c4e2c30323334352e313439362c452c3030302e31302c3030302c3331303331382c42464646464246462c3230322c30352c302c302c3323
kostas1257 years ago
2a48512c343230393135363738392c56312c3030333430312c562c303030302e303030302c4e2c30303030302e303030302c452c3030302e30302c3030302c3331303331382c46464646464246442c3230322c30312c302c302c3623
Anton Tananaev7 years ago

You can decode HEX yourself to confirm that your device actually returns zeroes:

https://www.traccar.org/hex-decoder/

kostas1257 years ago

Hi Anton and thanks for the reply. At HEX decoder i see zeroes from the beginning for this device but not always. Some times it reports the same location for days. When i request manually for an SMS, the device reports the correct location. That's why i am looking if there is a problem.

The protocol is h02 and the device is LK209A. I attach the device log in case you can see something wrong. How ever i want to thank you again for your help

2018-04-02 09:57:57  INFO: Version: 3.16-SNAPSHOT
2018-04-02 09:58:02  INFO: Starting server...
2018-04-02 09:58:03  WARN: One of the protocols is disabled due to port conflict
2018-04-02 09:59:03  INFO: [CF27E699] connected
2018-04-02 09:59:07 DEBUG: [CF27E699: 5013 < 5.144.208.75] HEX: 2442091567890657570204180000000006000000000e000000fffff9ffff000d000000000000ca01000000000000002a48512c343230393135363738392c56312c3036353735382c412c303030302e303030302c4e2c30303030302e303030302c452c3030302e30302c3030302c3032303431382c46464646463946462c3230322c30312c302c302c3623
2018-04-02 09:59:08 DEBUG: [CF27E699: 5013 < 5.144.208.75] HEX: 2442091567890657590204180000000006000000000e000000fffff9ffff000f000000000000ca0100000000000001
2018-04-02 09:59:08  WARN: Geocoding failed - Empty address - GeocoderException (JsonGeocoder:69 < *:34 < *:96 < ...)
2018-04-02 09:59:08  WARN: Geocoding failed - Empty address - GeocoderException (JsonGeocoder:69 < *:34 < *:96 < ...)
2018-04-02 09:59:08  WARN: Geocoding failed - Empty address - GeocoderException (JsonGeocoder:69 < *:34 < *:96 < ...)
2018-04-02 09:59:08  INFO: [CF27E699] id: 4209156789, time: 2018-04-02 09:57:59, lat: 0.00000, lon: 0.00000, speed: 0.0, course: 0.0
2018-04-02 09:59:08  WARN: Empty address
2018-04-02 09:59:08  INFO: [CF27E699] id: 4209156789, time: 2018-04-02 09:57:57, lat: 0.00000, lon: 0.00000, speed: 0.0, course: 0.0
2018-04-02 09:59:08  WARN: Empty address
2018-04-02 09:59:08  INFO: [CF27E699] id: 4209156789, time: 2018-04-02 09:57:58, lat: 0.00000, lon: 0.00000, speed: 0.0, course: 0.0
2018-04-02 09:59:08  WARN: Empty address
2018-04-02 09:59:36 DEBUG: [CF27E699: 5013 < 5.144.208.75] HEX: 2a48512c343230393135363738392c23
2018-04-02 10:00:13 DEBUG: [CF27E699: 5013 < 5.144.208.75] HEX: 2a48512c343230393135363738392c23
2018-04-02 10:00:50 DEBUG: [CF27E699: 5013 < 5.144.208.75] HEX: 2a48512c343230393135363738392c23
2018-04-02 10:00:56  INFO: user: 1, action: login
2018-04-02 10:01:28 DEBUG: [CF27E699: 5013 < 5.144.208.75] HEX: 2a48512c343230393135363738392c23
2018-04-02 10:02:06 DEBUG: [CF27E699: 5013 < 5.144.208.75] HEX: 2a48512c343230393135363738392c56312c3037303035382c562c303030302e303030302c4e2c30303030302e303030302c452c3030302e30302c3030302c3032303431382c46464646463946462c3230322c30312c302c302c3623
2018-04-02 10:02:06  INFO: [CF27E699] id: 4209156789, time: 2018-04-02 10:00:58, lat: 0.00000, lon: 0.00000, speed: 0.0, course: 0.0