identify obdii protocol

stuart4 years ago

Hi

im struggling to identify the protocol of a device..... cheap chinese i think.

ive tried all the ones in the documentation for chinese, with no joy.

2019-12-19 22:36:10  INFO: [9ebdb15f: watch < 82.132.234.238] HEX: 283038373037333139373033344250303533353238383730373331393730333431393132313941353134382e363839374e30303030392e34303138453030302e303232333630353030302e303031313030303030304c303030343530414229
2019-12-19 22:37:15  INFO: [9ebdb15f: watch < 82.132.234.238] HEX: 283038373037333139373033344250303033353238383730373331393730333448534f3031383529
2019-12-19 22:40:16  INFO: [9ebdb15f: watch < 82.132.234.238] HEX: 283038373037333139373033344250303033353238383730373331393730333448534f3031383429

any help much appreciated.

thanks

stuart

Anton Tananaev4 years ago

Port 5002.

stuart4 years ago

thanks...... i just set to that and now its working. thank you so much.......

odd because that was the very first port i tried, but for some reason it didnt work?

2019-12-19 22:16:13  INFO: [71c4b8c1: tk103 < 82.132.222.187] HEX: 283038373037333139373033344250303033353238383730373331393730333448534f3031383529
2019-12-19 22:16:13  INFO: [71c4b8c1: tk103 > 82.132.222.187] HEX: 283038373037333139373033344150303148534f29
2019-12-19 22:19:13  INFO: [71c4b8c1: tk103 < 82.132.222.187] HEX: 283038373037333139373033344250303033353238383730373331393730333448534f3031383529
2019-12-19 22:19:13  INFO: [71c4b8c1: tk103 > 82.132.222.187] HEX: 283038373037333139373033344150303148534f29
Anton Tananaev4 years ago

It works just fine. Your device just doesn't report location.

stuart4 years ago

any idea why it isnt reporting the location?

i can see its communicating but not the location.

if it text it, i get the right location back?