RE: [opendiag] Re: Can't read VIN

I've tried this on an Elmscan ISO interface, but the current Elm323 chip does not support the ATSH command, so there's no way that I've found to change the address. I've emailed Elm about this and they hope to have a new version of the ELM323 ready for testing in November which supports ATSH and MA.

John

-----Original Message-----
From: tlist@... [mailto:tlist@...]
Sent: 14 October 2003 22:19
To: opendiag@yahoogroups.com
Subject: [opendiag] Re: Can't read VIN

Kenny wrote:
>
> OK,
>
> I tried to request the supported values using :-
> $68,$6a,$F1,$09,$00,CS
>
> But again I got no reply at all.
>
> Just to confirm: I am connecting using address 33h and other
> requests (mode $01 etc) are working fine.
>
> -Kenny.

I get the same response on my Elm VPW interface for $68 $6a $f1 $09 $00 (or
for that matter, any $09 mode pid)

For what it is worth, I have retrieved the VIN by using
atsh6c10f1
3c01
3c02
3c03

which translated to generic is:
$6c $10 $f1 $3c $01 cs -> returns first 6 chars ascii values (1st one is 00)
$6c $10 $f1 $3c $02 cs -> next 6
$6c $10 $f1 $3c $03 cs -> final 6

Have not tested this on anything but a GM Blazer using an Elm VPW interface,
suspect it is specific to at least the VPW interface. Once I get a decent
map, I am going to move to attempt an ISO...

I am currently writing a mode/pid scanner to look for stuff outside of the generic
OBD2 mode/pids, would appreciate anyone's insights.

Todd

To unsubscribe from this group, send an email to:
opendiag-unsubscribe@egroups.com

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/

 
Received on Wed Oct 15 07:05:54 2003