GPS unit HEX identified but not working on TRACCAR Server

rdentandt8 years ago

Hi All

I have the following HEX:

2a48512c3335353438383032303533333236332c56332c3132313533362c36353530312c30342c3030303135322c3031343030312c3135362c2d36342c3030303136312c3031303634322c3133382c2c3030303135322c3031343030332c3132392c2c3030303135322c3031333937332c3132362c2c303245342c302c582c3037313131362c4646464646424646230d0a

Which translates to:

*HQ,355488020533263,V3,121536,65501,04,000152,014001,156,-64,000161,010642,138,,000152,014003,129,,000152,013973,126,,02E4,0,X,071116,FFFFFBFF#

According to the list of devices and protocals on github it points to h2o V3. This is not read by TRACCAR. Is it possible to add this or provide me a way to add this protocol?

Thank You

Anton Tananaev8 years ago

It's H02 protocol, port 5013 in Traccar.

The problem is that the message sample that you provided doesn't include any GPS data, so it will be ignored by Traccar.