Chinese Clone: Receiving data but not getting processed by traccar

Hi Guys.

I got this DX.com chinese gps tracker that i have thought to identify by the H02 protocol.
I have enabled the protocol in the config, and data is coming in port 5013 but it seems traccar is not able to recognise it? The decoded message in the log is:

2017-09-25 07:50:15 DEBUG: [9C7B36DE: 5013 < 62.140.137.16] HEX: 2a48512c3335333530353232313236343530372c56322c3037353134382c302c353233382e32353930302c4e2c30303530372e33333432392c452c302e32372c302c3235303931372c46464646464646462c63632c32382c202064622c6437356223200d0a

It looks like the H02 protocol but there is some garbage at the end, maybe this is the cause?

Thanks for helping out!

Regards

Mike

Also, is it correct the identifier is 353505221264507 instead of 05221264507 (the imei)?

It's H02 protocol, port 5013, device id 353505221264507.

Hi Anton

Yes i have set it up like this, however traccar does not seem to decode it. My traccar.xml is like this:

<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE properties SYSTEM 'http://java.sun.com/dtd/properties.dtd'>
<properties>

    <entry key="config.default">./conf/default.xml</entry>
    <entry key='database.driver'>com.mysql.jdbc.Driver</entry>
    <entry key='database.url'>1234</entry>
    <entry key='database.user'>1234</entry>
    <entry key='database.password'>1234</entry>
    <entry key="h02.enable">true</entry>

</properties>

This should be sufficient right?

Assuming that database configuration is correct, it should work. You don't need to add h02.enable. All ports are enabled by default.

If still doesn't work, please provide logs.

yes i removed credentials of the db. here are the logs:

/opt/traccar/logs # cat tracker-server.log |grep 5013
2017-09-25 07:50:15 DEBUG: [9C7B36DE: 5013 < 62.140.137.16] HEX: 2a48512c3335333530353232313236343530372c5649312c3037353134362c302c353233382e32353930302c4e2c30303530372e33333432392c452c302e35342c302c3235303931372c46464646464646462c63632c32382c202064622c6437356223200d0a
2017-09-25 07:50:15 DEBUG: [9C7B36DE: 5013 < 62.140.137.16] HEX: 2a48512c3335333530353232313236343530372c56322c3037353134382c302c353233382e32353930302c4e2c30303530372e33333432392c452c302e32372c302c3235303931372c46464646464646462c63632c32382c202064622c6437356223200d0a
2017-09-25 09:45:44 DEBUG: [931AF2A3: 5013 < 62.140.137.83] HEX: 2a48512c3335333530353232313236343530372c5649312c3039343731342c302c353233382e32353830382c4e2c30303530372e33333936332c452c302e31302c302c3235303931372c46464646464646462c63632c32382c202064622c6437356223200d0a
2017-09-25 09:45:44 DEBUG: [931AF2A3: 5013 < 62.140.137.83] HEX: 2a48512c3335333530353232313236343530372c56322c3039343731372c302c353233382e32353830382c4e2c30303530372e33333936332c452c302e31342c302c3235303931372c46464646464646462c63632c32382c202064622c6437356223200d0a

Try cat tracker-server.log | grep 9C7B36DE.

/opt/traccar/logs # cat tracker-server.log | grep 9C7B36DE.
2017-09-25 07:50:15  INFO: [9C7B36DE] connected
2017-09-25 07:50:15 DEBUG: [9C7B36DE: 5013 < 62.140.137.16] HEX: 2a48512c3335333530353232313236343530372c5649312c3037353134362c302c353233382e32353930302c4e2c30303530372e33333432392c452c302e35342c302c3235303931372c46464646464646462c63632c32382c202064622c6437356223200d0a
2017-09-25 07:50:15 DEBUG: [9C7B36DE: 5013 < 62.140.137.16] HEX: 2a48512c3335333530353232313236343530372c56322c3037353134382c302c353233382e32353930302c4e2c30303530372e33333432392c452c302e32372c302c3235303931372c46464646464646462c63632c32382c202064622c6437356223200d0a
2017-09-25 07:51:11  INFO: [9C7B36DE] disconnected

Looks like message type VI1 is not supported yet. I would need protocol documentation to fix it.

Can't you decode it the same as V2? the rest of the data is the same?

*HQ,353505221264507,VI1,075146,0,5238.25900,N,00507.33429,E,0.54,0,250917,FFFFFFFF,cc,28,  db,d75b# 
*HQ,353505221264507,V2,075148,0,5238.25900,N,00507.33429,E,0.27,0,250917,FFFFFFFF,cc,28,  db,d75b# 

V2 is not supported either.

and V1? as i see other people have gotten it working with V1:
https://github.com/tananaev/traccar/issues/56

V1 format is different. It has letter V or A before coordinates.

I have sent a email to the sellers however i am afraid i will not hear anything. Is it possible to make a new protocol based on V1 without the V/A before the coordinates?