Altitude, PDOP, HDOP, Operator, Power, Battery, Charging and Ignitition Parameters are not parsed and saved for ITS protocol

Paramvir5 years ago

Dear All,

I am facing an issue related to parsing of Power, Battery, Charging and Ignition values which are present in HEX String of ITS but are not saved in DB using latest version of Traccar.

Below is the HEX String recieved from device

2444502c5341464532302c3753303030312c4e522c312c4c2c3836393234373034353133333733302c4e412c312c32363034323032302c3139323335322c32332e3735313838392c4e2c38362e3338363037392c452c302e302c3331322e322c31352c3138362e302c312e392c302e382c494445412c302c312c32342e392c342e302c302c432c32312c3430352c37302c3746342c353731342c3745452c383136382c2d38362c3746342c353439442c2d38362c3746342c324143342c2d38372c3745452c353742462c2d38382c303030302c30342c332c313138392e362c302c2d31302c36363434312c28292c44304138463145442a

Snippet from above Hex String 3138362e302c312e392c302e382c494445412c302c312c32342e392c342e30 shows values of "altitude, PDOP, HDOP, operator, ignition , charging , power , battery " in respective order.

Further I have added below parameters in traccar.xml

<entry key='processing.copyAttributes.enable'>true</entry> 
<entry key='processing.copyAttributes'>power,ignition,battery</entry>

After decoding "satellites", reset of the parameters are not decoded or parsed.

Any help or suggestion will be highly appreciated.

Warm Regards.

Anton Tananaev5 years ago

How is copyAttributes related to the problem?

Paramvir5 years ago

Hello Anton,

Not related, just thought of sharing the configuration settings if required, so that I dont miss attributes just if device doesn't send some values in every message.

Any suggestions on what has gone wrong here. - Regards

Anton Tananaev5 years ago

I guess format is not decoded. I would recommend debugging the code. You might need to change regular expression.

Paramvir5 years ago

I already did just a walk through the code and initially looked in line with the regular expression in file "ItsProtocolDecoder.java" from line 69 to 79 & 189 to 215.
I will try to debug it futher, and possibly find the solution and till then if anyone has more inputs to this that might help. -- Thanks for recommendation and great software.