Wrong speed at reports?

Speed at log is OK, at reports is higher (checked by testing route today). Correct speed si cca 60km/h. So speed is reported at km/h.

Using some china-made GPS "TK106" with xexun protocol.

Log at server:

root@gps:/opt/traccar/logs# cat tracker-server.log.20170402 | grep 17:57:48 -B 1
2017-04-02 17:57:50 DEBUG: [7EF73FF9: 5006 < 46.135.214.1] HEX: 313730343032313635372c2b3432303737353437333939342c4750524d432c3135353734382e3030302c412c343935392e323738302c4e2c313432322e333335302c452c35382e36302c33342e34322c3032303431372c30302c303030302e302c412a35322c462c2c696d65693a3335353638393031353636353639392c313236f6a0
2017-04-02 17:57:50  INFO: [7EF73FF9] id: 355689015665699, time: 2017-04-02 17:57:48, lat: 49.98797, lon: 14.37225, speed: 58.6, course: 34.4

Line at reports at same time shows 108,5 km/h

In the log the speed is in knots. If you convert it to km/h, you get exactly what you see in the report.

Sorry, edited. Correct speed at log is at km/h. Measuerd toady.

Device is supposed to send speed in knots and the value that it sends is 58.6. If it's not correct value then either there is an issue with the device or the protocol has changed.

Could this HEX be decoded as other protocol? Similar to XEXUN? I have foud XEXUN as first matched and stoped to find another...

It is Xexun protocol. Other ports won't work at all.

Its device issue, it sends speed at km/h. How to solve it? Create new protocol eg. XEXUN(kmh)?

Xexun protocol can be extended to support speed in km/h. See TK103 protocol for example.

I update protocol, create pull request, could you add it to master branch?

If I understand it well, than I add

<entry key='xexun.speed'>kmh</entry>

to traccar.xml?

Pull request updated. Erros fixed.