Traccar (3.7) odd position/time issue
It seems newer LKGPS devices have LBS enabled by default (i.e. LK109-3G). You can disable it by sending a SMS with "addjz=0", but specifying the messagelength is the best solution as they are more precise with LBS enabled.
It seems the patch for the autodetection of messsage lenght doesn't really work, I have got the same problem again.
Here is the debug log:
2016-11-13 13:46:17 DEBUG: [E958B5C8: 5013 < 213.137.13.4] HEX: 2441060116601245431311165035313006004318210e000000
fffffbffff00242a48512c343130363031313636302c56312c3132343535322c412c353033352e333132392c4e2c30303433312e383231312c
452c3030302e32302c3030302c3133313131362c464646464642464623
2016-11-13 13:46:17 INFO: [E958B5C8] id: 4106011660, time: 2033-07-31 09:30:36, lat: 36.60505, lon: -314.05221, speed: 353.0, course: 532.0
Hi everyone,
I do not know if this helps but I have seen in numerous occasions on our Hardware: GPS Devices, that when the devices are shipped from the factory and there is not store forwarded Location information, it will show in the middle of the ocean. It will remain there until the first Location is established.
I do not know what hardware you are using or if this is your issue but I wanted to explain my personal experience with many hardware manufacturers.
Sincerely,
JD
@renaund any solution for this problem? I am facing same kind of issue.
@renaud, I have implemented another solution. It should work in 99% of the cases.
Thanks Anton, I will test it ASAP.
This kinda seems weird to me as that particular device had addjz=0, so it was not using LBS. It's quite hard to reproduce tough as it's really random (or at least it looks like that).
@anton are you talking about setting length to 45 and using jar file which you uploaded in uploadbox? I tried that solution but still I was receiving some negative values in lati and longi. Then I changed my device upload frequency to 45s and sent this command to device addjz=0 and I guess this has fixed the issue. My reports are looking fine now and no negative values in db for lati and longi but still I would like to know what is your patch to fix this problem?
@malkitsingh
The patch is here: https://github.com/tananaev/traccar/commit/4066c24ed1ba8749a1a682acb5b027401d0df70f
@renaud where is build available with this patch? Do I have to clone and build this?
There is currently no official build with this patch in.
In general, Anton make snapshots here: https://www.dropbox.com/s/cgmlansv32j3ii0/tracker-server.jar?dl=0
But many things have changed since 3.7, so this won't run correctly if you only upgrade this file over a 3.7 installation.
I can share my unofficial build if you like, but you need to understand there might be issues running it as there are really huge differences between 3.7 and that snapshot. Also, you will need to make changes to your configuration file.
I would recommend to wait for version 3.8. It should be ready in a week or two.
oh, that's what I was writing when @Anton's reply came in :D
Actually, I copied jar from that link yesterday and my reports were broke after that, so I reverted back. My problem seems to be fixed after sending addz=0 command I haven't received any negative latis and longis since then.
I think I should wait for next release.
Thanks for all the help @Anton and @renaud
@Anton, version 3.8 is out now, is this issue fixed in this release?
Then we can configure message length per device.