LBS Data decode for H02 Protocol
This specific message type is not supported.
Hi
After implementing the new updated protocol we have found that one GPS tracker is showing the perfect location but other did not .
One device with IMEI : 356327081001221 is showing 0.00 lat and 0.00 long for same cell id.
And other device with IMEI : 356327081001239 is showing my client office lat long for that same cell id.
Find below the log from the tarccar server
2019-01-24 12:52:21 INFO: [80d103dc] disconnected
2019-01-24 12:52:25 INFO: [3fd59045] connected
2019-01-24 12:52:25 INFO: [3fd59045] disconnected
2019-01-24 12:52:26 INFO: [979c5316] connected
2019-01-24 12:52:26 INFO: [979c5316] disconnected
2019-01-24 12:52:29 INFO: [67b5bb50: 5013 < 172.18.10.19] HEX: 2a68712c3335363332373038313030313232312c5650312c562c3437302c3030322c39322c333536352c305939322c313235382c33385939322c313334302c333523
2019-01-24 12:52:30 WARN: Geocoding failed - Empty address. Error: You must use an API key to authenticate each request to Google Maps Platform APIs. For additional information, please refer to http://g.co/dev/maps-no-account - GeocoderException (JsonGeocoder:69 < *:31 < *:97 < *:94 < ...)
2019-01-24 12:52:30 INFO: [67b5bb50] id: 356327081001221, time: 2019-01-17 06:00:00, lat: 22.48523, lon: 91.71990, speed: 0.8, course: 0.0
2019-01-24 12:52:30 INFO: [cc6f6978] connected
2019-01-24 12:52:30 INFO: [cc6f6978] disconnected
2019-01-24 12:52:31 INFO: [6773a418] connected
2019-01-24 12:52:31 INFO: [6773a418] disconnected
2019-01-24 12:52:35 INFO: [5bd795ea] connected
2019-01-24 12:52:35 INFO: [5bd795ea] disconnected
2019-01-24 12:52:36 INFO: [c641bcdc] connected
2019-01-24 12:52:36 INFO: [c641bcdc] disconnected
2019-01-24 12:52:37 INFO: [b7ccfbb6: 5013 < 172.18.10.17] HEX: 2a68712c3335363332373038313030313233392c5650312c562c3437302c3030322c39322c333536352c305939322c313334302c34305939322c31393433332c333323
2019-01-24 12:52:37 INFO: [b7ccfbb6] id: 356327081001239, time: 1970-01-01 06:00:00, lat: 0.00000, lon: 0.00000, course: 0.0
2019-01-24 12:52:40 INFO: [a7b3b0b5] connected
2019-01-24 12:52:40 INFO: [a7b3b0b5] disconnected
2019-01-24 12:52:41 INFO: [a275522e] connected
2019-01-24 12:52:41 INFO: [a275522e] disconnected
2019-01-24 12:52:45 INFO: [edc86216] connected
2019-01-24 12:52:45 INFO: [edc86216] disconnected
2019-01-24 12:52:46 INFO: [809cda06] connected
2019-01-24 12:52:46 INFO: [809cda06] disconnected
2019-01-24 12:52:50 INFO: [c0616c07] connected
2019-01-24 12:52:50 INFO: [c0616c07] disconnected
2019-01-24 12:52:51 INFO: [23ea78e5] connected
2019-01-24 12:52:51 INFO: [23ea78e5] disconnected
2019-01-24 12:52:55 INFO: [001c40ff] connected
2019-01-24 12:52:55 INFO: [001c40ff] disconnectedPlease can you let us know what is the reason.
Thank you
BR
Rabi
I think the error is pretty clear from the log.
Thank you Anton for quick response.
So it is for Google Authentication API. Please can you let me know where i can find this API to configure the geocoding.
Thank you
BR
Rabi
Geocoding is configured in the config file, not through API. Documentation is available on this website and there are a lot of forum threads about it.
Hi Anton,
My client has configured this geolocation for LBS please let me know is it okay
We configured traccar for LBS as per below:
<entry key='geolocation.enable'>true</entry>
<entry key='geolocation.key'>e70f32b7221c59</entry>
<entry key='geolocation.type'>opencellid</entry>
<entry key='geolocation.mcc'>470</entry>
<entry key='geolocation.mnc'>2</entry>
<entry key='geolocation.processInvalidPositions'>true</entry>I would recommend using Mozilla or Google providers.
Hi,
Can we us our own database of cell I'd physical address instead of Google.
No.
Hi Anton,
Need your suggestion and advise. If we go for paid version of Google reverse geocoding will the above mentioned "Geocoding failed - Empty address. Error:" resolve.
Thank you
BR
Rabi
It should, assuming that you configure it correctly.
Hi Anton,
Good day.
Today we have discover another issue. Please find the below data which we are receiving from Same type of school ID card GPS tracker.
HEX:
2a68712c3335363332373038313031363035342c56312c3031303330302c562c303030302e303030302c4e2c30303030302e303030302c452c3030302e30302c302c3031303131352c46464646464646462c34332c332c3437302c3030322c39322c333536352c302c39322c313235382c35362c39322c313230392c343423Decoded HEX :
*hq,356327081016054,V1,010300,V,0000.0000,N,00000.0000,E,000.00,0,010115,FFFFFFFF,43,3,470,002,92,3565,0,92,1258,56,92,1209,44#Now the issue is that this device is showing the location in the traccar server in Atlantic Ocean.
Please can you suggest us the resolution of it.
Thank you
BR
Rabi
It shows exactly what device sends.
Hi
But the device is inside the building and the place is located at Gulshan, Dhaka, Bangladesh. And at the end of the data there is a LBS location which is the lac and cell I'd of the place that I have mentioned. So the point is if the GPS data is invalid it should consider the LBS data and show the position.
Why it is happening in this case
Dear Concern,
I am using Chinese school ID card tracker device in traccar server and it is working fine for GPS location but when the tracker device is placed inside building, GPS is not working. The tracker device is sending LBS data as per below log.
i have configured traccar server for LBS as per below:
<entry key='geolocation.enable'>true</entry> <entry key='geolocation.key'>e70f32b7221c59</entry> <entry key='geolocation.type'>opencellid</entry> <entry key='geolocation.mcc'>470</entry> <entry key='geolocation.mnc'>2</entry> <entry key='geolocation.processInvalidPositions'>true</entry>We created account in opencellid and get the key. But LBS data is not decrypt by the traccar server.
Anyone please help me out to resolve the issue.
Thank you
BR
Rabi