SL28 (GT06 - GPS-WIFI-LBS) Incorrect Locations

Alcaldejau4 months ago

Dear friends,
I just spoke with Sucre (the manufacturer of the Sl28).
I have a bunch of his devices running on 5.9 version but the location data is spread crazy into the map, not correct route is provided, as it seems the server is mixing the LBS location with the GPS locations and making huge flyovers. The decide is not in a rural area so it should not be lack of GPS for the device to upload LBS too often.

He mentioned I should deactivate LSB function on the server side since there is no way to do it on the device, but I can seem to have it running.
He also mentioned he was the one responsible to deal with you guys to add the "so called protocol" into traccar and that It should work fine, but I cant seem to find what os the problem is....

Track-trace4 months ago

Did you try to set filter.approximate to true in the /conf/traccar.xml file and restart the server to Filter cell and wifi locations that are coming from geolocation provider?

[https://www.traccar.org/configuration-file/[(https://www.traccar.org/configuration-file/)

Alcaldejau4 months ago

Not really, I want even aware there was such function, I will dig into it right now and keep you posted! Thank you!

Track-trace4 months ago

just add <entry key='filter.approximate'>true</entry> to your /conf/traccar.xml file and restart the server.

Alcaldejau4 months ago

Thank you Track-Trace.
I was wondering if I should add the filer.aproximate and also the filter.accuracy but I believe this should be enough, I will test it right away!

Track-trace4 months ago

You better test each step separately which makes it easier to note the difference which each modification makes.

With filter.aproximate you filter out ALL LBS/WIFI responses from the geolocation server.
Filter.accuracy will filter out positions based on the Accuracy that the position has (Accuracy 500 means that the position is within a 500 meter range which is rather big).

But if i would have such a tracker i would check the position from the server log to see what the tracker actually reports. And you would only get a geolocation server reply is the position of the tracker is reported as invalid (not a valid gps position). So if if you state that the tracker is outside in the open you would wonder why it doesnt report a Valid GPS location. Thus you would need to look at the log for that. But in your case you can first test with these filters.

Alcaldejau4 months ago

Awesome, very valid suggestions.
I set the filter and restarted it.
Now I need to collect some data and see if the results come to be what we expect, if not will move further.
The problem with the protocol is that even with a valid GPS location, on every alarm upload it also send the LBS information and that where I believe the server is getting all mixed up, since - for example. at 07:01:02 I got a fixed gps location and at 07:01:05 I got a LBS location 150m away, and that is why the maps are so messed up. Excluding the LBS information should fix the problem.
Thanks again to you all!

Alcaldejau4 months ago

Well, the battle is not lost but it did not work!

I am still having flyovers, absurd flyovers, impossible to match!
The manufacturer garantees there is nothing wrong with the devices.
Traccar has listed the device as compatible and I am still lost!

By the way, again: Devices are SL28 with gt06 protocol

Please check what I am getting:

2024-01-04 09:18:47  INFO: [T6947bfdd] connected
2024-01-04 09:18:49  INFO: [T6947bfdd: gt06 < 177.69.143.153] 7878110108671110608288750000000a0724f4040d0a
2024-01-04 09:18:49  INFO: [T6947bfdd: gt06 > 177.69.143.153] 787805010724e27b0d0a
2024-01-04 09:18:51  INFO: [T6947bfdd: gt06 < 177.69.143.153] 78782222180103140907cc02658b17054307823719020000000000000000010001071c34b60d0a
2024-01-04 09:18:51  INFO: [T6947bfdd] error - unknown protocol: htts - MalformedURLException (... < HttpSmsClient:97 < NotificatorSms:51 < NotificationManager:110 < ...)
2024-01-04 09:18:51  INFO: [T6947bfdd] disconnected
2024-01-04 09:18:51  INFO: [T6947bfdd] error - unknown protocol: htts - MalformedURLException (... < HttpSmsClient:97 < NotificatorSms:51 < NotificationManager:110 < ...)
Anton Tananaev4 months ago

Have you checked the data to see what the device is actually sending?

Alcaldejau4 months ago

Anton, I dont know what you mean by checked the data, isn´t it the data I just sent you or you mean the raw data?

Anton Tananaev4 months ago

What you have in logs is the raw data. It is what I'm talking about. But have you checked it against the documentation to see what it actually includes? That's the way to verify where the problem is.

Just so you know, when you work with most Chinese device vendors, they will always say "there is nothing wrong with the devices" immediately without even checking anything. So that statement usually has very little value.

Alcaldejau4 months ago

Anton, yes!
You are right, I believe that would be the case, but in the mean time I don´t know what to make out of it, not that well experienced yet!
I will see what I cam come up with!