V680 working with LBS

gadilo9 years ago

Hi!
I have a tracker that don't have really gps only send gsm/lsb position (I think is K8).
The tracker use protocol v680 so I use port 5016 (I check hex conversor and protocols), also I activate cell identification on xml file.
Traccar receive the connection and data but don't iregister position.
I copy hex what tracker send:

233335333538383535303032353534362323312330303030234155542330312332313430303330383434323236612330303030302e303030302c452c303030302e303030302c4e2c302e30302c23303030303030233030303030302e30303023230d0a

Can somebody help me If I am doint something wrong?

Thank you.

Anton Tananaev9 years ago

You are right, it's using V680 protocol, but it doesn't send any valid information. Only zeroes. LBS is not supported for this protocol at the moment.

gadilo9 years ago

Thank you for your answer!

Anton Tananaev9 years ago

It's possibly to add support for LBS data if you have protocol documentation.

gadilo9 years ago

Hi Anton,

Is it possible to use the same documentation that use v680? I check documentation, and what my gps/lbs send match the info on document.

Example:

#353588550025XXX##1#0000#AUT#01#2140030844226a#00000.0000,E,0000.0000,N,0.00,#000000#000000.000##

LBS is 2140030844226a

214 is MMC
003 is MNC
844 (dec 2116) is LAC
226a (dec 8810) is CellID

I check on OpenCellID.org and match near my location.

Can work this?

Thank you.

Anton Tananaev9 years ago

Documentation that I have says:

8 byte, HEX, This string will be only LBS or V. If it is V, it means that the GPS data is valid. If it is LBS, then the current GPS data is LBS data.

So it doesn't match your message. I need documentation to know all possible values. For example my documentation says that instead of cell info, the field can contain only letter "V".