HEXA EELINK protocol decoder

Hi Anton,

Finally I was able to connect the OBD tracker to the server using the eelink protocol

I can get results from just two commands I sent from the platform (PARAM # and STATUS #) from all the ones I read in the manual ...

But why can't I decode hex messages? (I emphasize that as an end user I have no idea of ​​the rules of the hexadecimal decoder at https://www.traccar.org/hex-decoder/)

LOGS (which could not be decoded):

2021-04-03 11:23:49  INFO: [b37ddc5c: eelink > 191.47.204.120] HEX: 676780000d00000100000000504152414d23
2021-04-03 11:23:51  INFO: [b37ddc5c: eelink < 191.47.204.120] HEX: 676780004b037d0100000000736f733d3939363535373437342c61706e3d2c6974763d32302c6865617274626561743d3132302c74696d657a6f6e653d313830
2021-04-03 11:23:51  INFO: [b37ddc5c: eelink < 191.47.204.120] HEX: 2c6770733d2d312c67736d3d36372c00
2021-04-03 11:23:51  INFO: [b37ddc5c: eelink > 191.47.204.120] HEX: 6767800002037d

RESULT OF COMMAND PARAM#:

2021-04-03 11:23:51  INFO: [b37ddc5c] id: 123456789101112, time: 2021-04-02 18:41:58, lat: -XX.XX530, lon: -XX.XX186, course: 173.0, result: sos=X9X5X7X7X,apn=,itv=20,heartbeat=120,timezone=180,gps=-1,gsm=67,

Because it's a binary protocol, not text.

I understand... Thanks.