What device are you using? Most likely device didn't report any data in between, so you see a straight line.
I have identified the device from the Hex Decoder as
'h02' : '*HQ,123456789012345,V1,121300,A,6000.0000,N,13000.0000,E,0.00,0.00,010112,ffffffff,000000,000000,000000,000000#'
I am sure it's the problem with the device, it hasn't responded to the trial trip done as well.
Thanks,
Shankar.
You should look at the log files and check if all the messages from the device were decoded. If yes, it means that there is some problem with the device.
Here is the sample log output, the decoding is fine.
2017-01-19 08:30:06 DEBUG: [377C13AA: 5013 < 49.224.79.121] HEX: 2a48512c383136303839383639342c56312c3139333030372c412c333635322e323931312c532c31373434352e373538372c452c3030302e30302c3030302c3138303131372c46424646424246462c3533302c30312c30303033322c343134313223 2017-01-19 08:30:06 INFO: [377C13AA] id: 8160898694, time: 2017-01-19 08:30:07, lat: -36.87152, lon: 174.76265, speed: 0.0, course: 0.0 2017-01-19 08:30:07 DEBUG: [377C13AA: 5013 < 49.224.79.121] HEX: 2a48512c383136303839383639342c56312c3138353735332c412c333635322e323939362c532c31373434352e373535322c452c3030302e30342c3030302c3138303131372c46424646424246462c3533302c30312c30303033322c343134313223 2017-01-19 08:30:07 INFO: [377C13AA] id: 8160898694, time: 2017-01-19 07:57:53, lat: -36.87166, lon: 174.76259, speed: 0.0, course: 0.0 2017-01-19 08:30:07 DEBUG: [377C13AA: 5013 < 49.224.79.121] HEX: 2a48512c383136303839383639342c56312c3139333030392c412c333635322e323931302c532c31373434352e373538362c452c3030302e31302c3030302c3138303131372c46464646424246462c3533302c30312c30303033322c343134313223 2017-01-19 08:30:08 INFO: [377C13AA] id: 8160898694, time: 2017-01-19 08:30:09, lat: -36.87152, lon: 174.76264, speed: 0.1, course: 0.0 2017-01-19 08:30:08 DEBUG: [377C13AA: 5013 < 49.224.79.121] HEX: 2a48512c383136303839383639342c56312c3138353831332c412c333635322e323938382c532c31373434352e373534322c452c3030302e33302c3030302c3138303131372c46424646424246462c3533302c30312c30303033322c343134313223 2017-01-19 08:30:09 INFO: [377C13AA] id: 8160898694, time: 2017-01-19 07:58:13, lat: -36.87165, lon: 174.76257, speed: 0.3, course: 0.0
Thanks,
Shankar
Which means it's a device issue.
I'm facing the same problem. This started to happen after I formatted my cell phone.
I reinstated the Traccar and began to behave this way.
I even changed the device. Now I'm using a Samsung J5 and it continues the same thing, just a straight line between source and destination.
I noticed that on the web server there is no travel report, just a route report. If you choose to show Bookmarks, it shows only the source and the destination.
This issue definitely has nothing to do with formatting your cell phone. It must be a coincidence.
Exactly. But I have no idea what it is.
I definitely do not know what else to do. Traccar only appears on the web server if you are online.
Interesting is that it has the normal logs on the client.
I tested it by installing another tracking app and it's working fine.
The only "abnormality" is that the Traccar client logs appear with the time in 12h (am/pm) format and the android is set to 24h format. I do not know if there is any connection to the problem.
If you want some help I would recommend to start another thread and provide all the information you can (logs, screenshots etc etc). Without any information no one would be able to help you with the problem.
Hi, I have just installed traccar and trying to look at the route in the reports but it shows a direct line to the destination instead of the following the roads. Is there any settings to do or the device itself is in fault.
Thanks,
Shankar.