GT06 LBS information

Hi,

I installed traccar server and configured it to decode LBS information. The problem is that when I look at the log, the device is not sending the LBS information, only GPS coordinates. By SMS, I can receive all LBS information. Do you have any tips how to solve that?

Have you actually looked at the raw HEX data?

Hi,

Thanks for replying. Here is one of the hex samples:

78781311110819151c3102d41f07d100a8ad000506340d0a

Here is the other one:

78781f12110819150b03c802231fa104b66fcb0000000000000000000000000000000000

Both samples are from the same device.
Seems the first one is using protocol 0x11, and I didn't find it on the protocol documentation.
The second one seems to be using the 0x12, but missing the LBS information.

Both are supported by Traccar and you should be getting LBS information.

Hi,

Thanks for replying. I saw I forgot to put the <entry key='geolocation.enable'>true</entry> in the config file. Now that I put it, I am receiving this Warn message:

WARN: Unexpected char 60 at (line no=1, column no=1, offset=0) - JsonParsingException (... < OpenCellIdGeolocationProvider:52 < ...)

And still no tracking information. Any new tip about it?

You have some problem with OpenCellID provider.

Hi,

Thanks again for replying. I changed the provider to mozilla and now I am getting:

Not found - GeolocationException (UniversalGeolocationProvider:52 < ...)

Any other tip?

The error is pretty self-descriptive. Your cell information is not in their database.

Hi Anton,

Thanks for trying to help, but it still not working. I logged into my opencellid account and if I use the cell information I receive with the SMS command, I can get the correct location(using my online account). With traccar, I am still receiving the errors like that:

2017-09-08 21:52:10 DEBUG: [42F9A1B1: 5023 < 179.66.1.236] HEX: 7878131100000000000002d41f07d3009c6a009606900d0a
2017-09-08 21:52:10 DEBUG: [42F9A1B1: 5023 > 179.66.1.236] HEX: 7878051100477b7b0d0a
2017-09-08 21:52:10  WARN: Unexpected char 60 at (line no=1, column no=1, offset=0) - JsonParsingException (... < OpenCellIdGeolocationProvider:52 < ...)
2017-09-08 21:52:10  INFO: [42F9A1B1] id: 352887074976261, time: 1970-01-01 01:00:00, lat: 0.00000, lon: 0.00000, speed: 0.0, course: 0.0
2017-09-08 21:52:20 DEBUG: [42F9A1B1: 5023 < 179.66.1.236] HEX: 7878131100000000000002d41f07d3009c6a009706190d0a
2017-09-08 21:52:20 DEBUG: [42F9A1B1: 5023 > 179.66.1.236] HEX: 787805110048838c0d0a
2017-09-08 21:52:20  WARN: Unexpected char 60 at (line no=1, column no=1, offset=0) - JsonParsingException (... < OpenCellIdGeolocationProvider:52 < ...)
2017-09-08 21:52:20  INFO: [42F9A1B1] id: 352887074976261, time: 1970-01-01 01:00:00, lat: 0.00000, lon: 0.00000, speed: 0.0, course: 0.0
2017-09-08 21:52:30 DEBUG: [42F9A1B1: 5023 < 179.66.1.236] HEX: 7878131100000000000002d41f07d3009c6a009806ee0d0a
2017-09-08 21:52:30 DEBUG: [42F9A1B1: 5023 > 179.66.1.236] HEX: 78780511004992050d0a
2017-09-08 21:52:30  WARN: Unexpected char 60 at (line no=1, column no=1, offset=0) - JsonParsingException (... < OpenCellIdGeolocationProvider:52 < ...)
2017-09-08 21:52:30  INFO: [42F9A1B1] id: 352887074976261, time: 1970-01-01 01:00:00, lat: 0.00000, lon: 0.00000, speed: 0.0, course: 0.0

Are you sure it is not a protocol problem?

Here is the information I get from your messages:

cellId = 724
locationAreaCode = 0
mobileCountryCode = 0
mobileNetworkCode = 0

So, I guess there is some problem with device, or protocol has changed.

Thanks for replying Anton,

For what I see from the HEX(the relevant part is 2d41f07d3009c6a) I sent you it is:

02d4: decimal:724 means MCC:724

1f: decimal:31 means MNC:31

07d3: decimal:2003 means LAC:2003

009c6a: decimal:40042 means CellID:40042

And this is the correct data. Could you inform the file I can edit to fix the problem?

Do you have protocol documentation?

No,

But I figured it out by looking at the HEX as the SMS message for the LBS shows the same MCC, MNC, LAC and CellID. And they show the correct location.

You can fix it in Gt06ProtocolDecoder class, but without documentation we won't be able to include it in official version.

Thanks!!! If I find the documentation, I will let you know.

I have a question about LBS and TK103 clones, but I will create another thread to make it easier for people to search!!