ITS AIS140 data received at server but not decoding it

nanva19896 years ago

Hi Anton,

I have configured AIS140 device with my traccar instance. I am getting data in log but somehow its not decoded.

Below is the hex received in logs,

242c46462c5a3137333632343131312c394330302c4e522c4c2c3836383434303033343135303537322c363338353135313932372c312c3138313232352c3134333535332c31322e39363233323930302c4e2c38302e32363232383330302c452c30303030302c30303030302c3030392c30303030342c3030312c3030303030303030302c41697254656c2020202020202c302c312c31323134332c30333730302c302c302c3031322c3430342c3034302c303166352c623761652c623761612c2020202020202020202020202020202020202020202020202c3030302c3030303138333239362c30303030302c30303030302c3030303030313535312c30303030302c30303030302c30303030302c30303034352c30303030302c30303030302c30303030302c3030303031343738312c4b0d0a

Decoded hex via hex decoder:

$,FF,Z173624111,9C00,NR,L,868440034150572,6385151927,1,181225,142641,12.96231400,N,80.26228300,E,00001,00000,010,00004,000,000000000,AirTel      ,0,1,12325,03700,0,0,011,404,040,01f5,b7ae,b7aa,                        ,000,000183296,00000,00000,000001534,00000,00000,00000,00045,00015,00000,00000,000014772,K

I have also added device in web interface with identifier "868440034150572". Can you please help me to understand why its not getting decoded? Is it something I missed in configuration?

Thanks in advance.

Anton Tananaev6 years ago

Most likely it's not supported because of some small difference in the protocol.

nanva19896 years ago

Ok. Any suggestion or solution ?

Anton Tananaev6 years ago

Someone needs to add support for this format. If you need help with it, send an email to support address.

Charmi Bansal6 years ago

How can we get this working. The device is not just getting active on traccar. Any guidance or help here