OBD device protocol doc

Hi,

A manufacturer sent me a protocol spec document for a device that has OBD diagnostic info + GPS. Could you please take a look and let me know if the protocol is supported?

https://s3.amazonaws.com/webserver-junk-us/OBD+Device+Protocol_V1.1.6_170105+(1).docx

Thank you for your help,
Mike

It looks like HuaSheng protocol, port 5111 in Traccar.

Thank you. Are vehicle diagnostics handled in the traccar implementation?

For this particular protocol only some basic data is decoded (location, ignition, odometer).

Hi this like does not seem to work above but does anyone know what this looks like ?

2017-01-23 11:00:53 DEBUG: [BA2B60A0: 5003 <- 118.148.149.85] - HEX: 2481608491842200522201174022802406175338802a000000ffffbbff000000000000000002121800d5726160
2017-01-23 11:01:12 DEBUG: [BA2B60A0: 5003 <- 118.148.149.85] - HEX: 2481608491842201112201174022802606175338800a000000ffffbbff000000000000000002121800d5726161
2017-01-23 11:01:47 DEBUG: [BA2B60A0: 5003 <- 118.148.149.85] - HEX: 2481608491842201302201174022802506175338797a000000ffffbbff000000000000000002121800d5726162
2017-01-23 11:01:51 DEBUG: [BA2B60A0: 5003 <- 118.148.149.85] - HEX: 2481608491842201502201174022802906175338794a000000ffffbbff000000000000000002121800d572a163
2017-01-23 11:02:10 DEBUG: [BA2B60A0: 5003 <- 118.148.149.85] - HEX: 2481608491842202092201174022803306175338783a000000ffffbbff000000000000000002121800d572a164
22017-01-23 11:02:30 DEBUG: [BA2B60A0: 5003 <- 118.148.149.85] - HEX: 2481608491842202292201174022803206175338772a000000ffffbbff000000000000000002121800d572a165
2017-01-23 11:02:49 DEBUG: [BA2B60A0: 5003 <- 118.148.149.85] - HEX: 2481608491842202482201174022803306175338768a000000ffffbbff000000000000000002121800d572a166

@asowry, how is it related to the topic? Please don't spam with unrelated questions.

@ Anton
Sorry it was a typo I was just commenting that the link on the first post did not work and i think this may be the protocol i have I will post a new topic