ITS AIS140 data received at server but not decoding it

Manish Sharma5 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,

244c474e2c4d41524b2c3030303030303030302c3335383938303130303033353439332c56302e302e312c4149533134302c31392e3832343933342c4e2c37352e3232323930382c452a

Decoded hex via hex decoder:

$LGN,MARK,000000000,358980100035493,V0.0.1,AIS140,19.824934,N,75.222908,E*

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

Thanks in advance. Can you add support for this format.

Manish Sharma5 years ago
skyking5 years ago

Looks like data stream is missing the comma after $

Manish Sharma5 years ago

Yes solved it ! Thank you !

Sunil Haridas4 years ago

Hi Manish,

We are facing a similar problem with our login packet (ITS protocol) getting rejected. Tracking pack is compatible and if we send directly it will work. Did you bypass login packet in this case ? Can you please suggest how you bypassed logging packet. Thanks in advance..

Kunal Raut4 years ago

hi Minish, We are also facing the same issue with its protocol.please help, thanks in advance

Gps man4 years ago

Is there any update in this regard....

It seems that AIS140 requires response for Login, heartbeat and normal packets....

are we planning any resolution ?