I have looked through the list of supported Huasheng devices. I have tried 2 types that we have in stock at the moment, I believe both are the same protocol, as they connect to the same port on the current proprietary softwate.
The device I am looking at right now is an HS-600G connected to our server via port 5111.
I can see the device in the traccar log, but when I look at the translated hex code, it's gibberish. For example
2019-07-03 12:42:58 INFO: [6fa2bd55: huasheng > 41.13.212.26] HEX: c00100000c0003000000000003c0
2019-07-03 12:43:23 INFO: [6fa2bd55: huasheng < 41.13.212.26] HEX: c0010c00400002000000000004020014a0014f42445f4c54465f56312e30332e34540013a0043836373237333032303934313738320006a08700000006a0a104c2c0
I think I saw a post before from 2 years ago that Anton said was a binary protocol for the 3000G. Has anybody got one of these to work yet?
...gibberish.... OBD_LTF_V1.03.4T ..... gibberish.... 867273020941782 ...gibberish is what is translated from
HEX: c0010c00400002000000000004020014a0014f42445f4c54465f56312e30332e34540013a0043836373237333032303934313738320006a08700000006a0a104c2c0
The 867273020941782 is the IMEI number
It seems like your device doesn't accept server reply for some reason.
Thanks Anton. Will try to have a look at what's being sent.
I have looked through the list of supported Huasheng devices. I have tried 2 types that we have in stock at the moment, I believe both are the same protocol, as they connect to the same port on the current proprietary softwate.
The device I am looking at right now is an HS-600G connected to our server via port 5111.
I can see the device in the traccar log, but when I look at the translated hex code, it's gibberish. For example
I think I saw a post before from 2 years ago that Anton said was a binary protocol for the 3000G. Has anybody got one of these to work yet?