Re: Can't read VIN

The big difference bewteen your approach and mine seems to be the
target addres, you seem to be using controller addressing whereas I
was using functional addressing. Maybe that's my problem!

Thanks for the help.

-Kenny

--- In opendiag@yahoogroups.com, tlist@w... wrote:
> 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

 
Received on Sat Oct 18 06:11:07 2003