pires/android-obd-reader

VIN - Binary result returned

KirbyJames opened this issue · 19 comments

Hi, I've rebuilt android-obd-reader-2.0-RC3 which I think contains obd-java-api-master 1.0-RC15 or RC14.

After looking at earlier VIN related prblems I've added ATH0 to the initialisation string. However I still get (a fixed) binary value displayed for the VIN (except on about 1 in 10 occsaions when it does display the correct value).

I'd be grateful for any pointers as to what I might be doing wrong.

vin

This is still an issue on my side as well. I am prepared to put up a $10 reward for a proper fix for the VIN.

Add $10 from me

Sent from my iPhone

On May 9, 2016, at 4:51 AM, Pho3niX90 notifications@github.com wrote:

This is still an issue on my side as well. I am prepared to put up a $10 reward for a proper fix for the VIN.


You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub

For all that are having this issue, please post your rawData vin here. I need to see what vins are being returned so that I can figure out one algorithm.

Many thanks for returning to this issue.

Below are two VINs shown as both raw and hex

eu¥¥£µ¤ #3s#                               
e…„Ô£ £ÂƒSs 

hex

Many thanks for returning to this issue.

Below are two VINs shown as both raw and hex

eu¥¥£µ¤ #3s#
e…„Ô£ £ÂƒSs
hex

@KirbyJames
Could you please post your raw response from the obd. So that I can do tests?

@KirbyJames Pleaes try this project: http://goo.gl/uAcCK3
Replace the result string with your raw response. See if it's giving you the correct output

Hi, I've added the code to VinCommand.java and rebuilt the app. Unfortunately it returns the same value ..

capture

@KirbyJames I will need your rawData response to rrsolve.

in calculated results. Instead of returning vin return rawData

@KirbyJames
Please add the following in you vin data
Log.d("VinCommand.java", "rawdata: " + rawData);

Like so:
image

Then find the raw response in your logcat.

Ah. I have realised that my build is using the github version of obd-java-api-master/. I have downloaded the obd-java-api-master library - but I don't know how to modify the gradle configuration to use it in the build.

@KirbyJames I have no idea to be honest. I have completely moved away from gradle.
@pires do you know the answer to the above question?

I've managed to re-build the app with the modified VinCommand.java
I've printed the rawdata value below ... and a valid 17-character Vin is returned :-)

rawdata: 0:4902015756571:5A5A5A314B5A422:57323233373237
Vin: WVWZZZ1KZBW223727

rawdata: 0:4902015756571:5A5A5A314B5A422:57323233373237
Vin: WVWZZZ1KZBW223727

@KirbyJames Awesome news! What vehicle was it used in, which country and what year model is the vehicle? This will help greatly in diagnosing further enchancements to the VIN.

WVWZZZ1KZBW223727 is a 2011 VW Golf registered in the UK.
Will the update be included in an updated obd-java-api?

Then it's most def a can. on same restriction as we here in south africa are, except no emissions.
Anyways, yes the changes will be added to the lib, pullrequest is located here -> pires/obd-java-api#113

pires commented

I'll be releasing library RC16 as soon as @Pho3niX90 finishes an open PR and will update this project.

pires commented

Done.