LBS Data decode for H02 Protocol

I suspect it's either not decoded or not used because there is already GPS location in the message.

Hi,

As per the protocol documentation in the given link of traccar site https://www.traccar.org/protocols i found one document under H02 protocol which is name "document.pdf" . There in the page no 3 under the heading "Packet Definition" they have define the following data format of H02

*XX,YYYYYYYYYY,cmd,HHmmss,S,latitude,D,longitude,G,speed,direction,DDMMYY,vehicle_status, pw ,3,mcc,mnc,lac,cid, lac,cid, lac,cid #

which match with the device data that we are receiving from the device as follows

*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#

However in the traccar server protocol decoder file the given format is following

*HQ,123456789012345,V1,121300,A,6000.0000,N,13000.0000,E,0.00,0.00,010112,ffffffff,000000,000000,000000,000000#',

So now my point of suspect is that will it be the reason of packet format mismatch.

Need your expert opinion. Is there any thing we need to modify in the decoder?

It's not a mismatch. You are using correct protocol.

Hi Anton

I have found some same issue related to the H02 protocol data length in the below link where you have provide the resolution.

https://www.traccar.org/forums/topic/traccar-3-7-odd-position-issue/page/2/#post-8339
https://www.traccar.org/forums/topic/h02-protocol-parsing-issue/

However but the drop box link that you have provided is not valid

https://www.dropbox.com/s/cgmlansv32j3ii0/tracker-server.jar?dl=0

Appreciate to let us know whether this is already implemented in current version of traccar server 4.2 or if you can provide us it to resolve the issue that we are facing now.

Those issues have nothing to do with your problem. Also, all fixes are always included in the closest release.

Dear Mohammad Rabiul Hossain,

I have the same problem as you. Can you help me?