I am currently working on this right now. I am also on 3si (SHiVeR-
91VR4) and have dataloggers for the first gen. The protocol isn't
perfectly OBDII compliant, but I have a MUT-II and a test car that I
am going to be using to pull codes and write the software. Short of
having both of those, I don't know how you would do it. I haven't
had much time to work on it yet, but I have a bunch of things I've
discovered. I think they're closer to OBDII cars than we think.
--- In opendiag@yahoogroups.com, "avsa242" <avsa242@y...> wrote:
> Hi folks, first let me introduce myself:
>
> My name is Jesse, I'm 23 and I'm an auto mechanic on Cape Cod,
Mass. I
> have some experience with electronics, and more with computers. I
am
> very interested in working on some sort of PC interface to my 95
> 3000GT. I became especially interested when I discovered this group
> and the program freediag. I realize that a 95 is not (entirely?)
OBDII
> compliant and with finding a newer OBDII compliant ECU and
associated
> hardware as an alternative, I would like to look into information
on
> communicating with my current ECU. I have been a member of 3SI
> (http://www.3si.org) for about three years now and so far haven't
been
> able to find much on this subject; most attention is given to
actual
> OBDII 3000GTs. Thus, I would just like to know if anyone can give
me
> any information on the protocol my GT speaks, or point me in a good
> direction. I have connected one scan tool to it which reported "NO
> DATA" but I realize that even with this standard, still not all
scan
> tools will read all cars. Thanks in advance for your help and my
> apologies if this post is very long.
>
> Jesse
Received on Fri Aug 15 12:23:48 2003
This archive was generated by hypermail 2.1.8 : Wed Jan 02 2008 - 00:56:00 CET