I have a device from "Entrack" that uses the "Huabao" protocol.
I'm connecting a concrete mixer sensor to the RS232 port to detect which direction the truck is turning and its speed.
When the sensor is activated, the device sends this message:
7e0900000d671075428217020140000a415303210420000000dc507e
Analyzing the Huabao protocol, the message body would be: 40000a415303210420000000dc
Decoding this part of the message, everything is correct, according to the sensor manual.
However, analyzing the "HuabaoProtocolDecoder.java" file, line 1118, only messages that begin with "GTSL" are considered, which is not the case.
Wouldn't it be interesting to save this data in another field, even if in HEXADECIMAL, so that we can perform the processing at another point?
Sure, it would be nice to support this as well.
What do we need to have this information in a future version?
It could go in a "hexData" field, for example.
Someone needs to implement this. Pull requests are always welcome.
I have a device from "Entrack" that uses the "Huabao" protocol.
I'm connecting a concrete mixer sensor to the RS232 port to detect which direction the truck is turning and its speed.
When the sensor is activated, the device sends this message:
Analyzing the Huabao protocol, the message body would be: 40000a415303210420000000dc
Decoding this part of the message, everything is correct, according to the sensor manual.
However, analyzing the "HuabaoProtocolDecoder.java" file, line 1118, only messages that begin with "GTSL" are considered, which is not the case.
Wouldn't it be interesting to save this data in another field, even if in HEXADECIMAL, so that we can perform the processing at another point?
