HS3000-g showing in log, but not in UI (wrong identifier?)

Hello,

I am running into some trouble with the HS3000-g device :(

I have my HS3000-g OBD2 device connecting to the server on port 5111.
In the logs i can see the device talking to the server, but nothing is appearing in the traccar ui.

Status is reporting Offline

HEX code in log is

c0010c003c0002000000000011020010a0014f42445f3347315f56322e320013a0043335353835353035313032303536360006a08700000006a0a105c7c0

Converted is

... some binary data ...

IMEI number is '355855051020566' which i am using as the identifier..

This is the only entry in the log

2017-11-29 15:08:01 DEBUG: [01C7532C: 5111 < 185.3.54.12] HEX: c0010c003c0002000000000044020010a0014f42445f3347315f56322e320013a0043335353835353035313032303536360006a08700000006a0a105c9c0

No additional information of errors..

Any help would be greatly appreciated!

Thanks
Beau

Looks like message type that your device sends (0x010c) is not supported yet.

Thanks Anton..

The device i am using Is listed in the supported devices page...

HS-3000G huasheng 5111

Is it possible i am doing something incorrect? How did you decode the HEX to get that code out of it?
I am using a basic hex to string converter, but it is returning a bunch of ascii characters.

Thanks in advance.

It's a binary protocol, so HEX converter won't help. Message type is 2nd and 3rd bytes. In your example it's 010c. This specific message type is not supported yet, as you can see here in the code:

https://github.com/tananaev/traccar/blob/master/src/org/traccar/protocol/HuaShengProtocolDecoder.java#L37

Thanks Anton,

I am going to attempt to get this working, if possible can you point me into the direction on how to decode the string correctly?
Is it a big task to get it working?

Thanks mate
Beau

It's not a string; it's a byte buffer. You need to understand how to binary decoding is working in Traccar if you want to fix it. Research the code.

Hi @beau,
Did you manage to fix this issue. I know it's 4 years ago but I'm facing the same problem now.

Thanks.