Cool...looks like you need to program the PIC though...
check out this from hackaday: http://www.hackaday.com/2007/11/07/i...d-2-interface/
some guy built his own OBD-II scanner and shows you the basics on how to build it, or he can ship you a development board for around $6 (you still have to assemble however.)
very interesting - it is actually http://www.obddiag.net/index.html . The website details everything very well. Should be very easy to get one up and running pretty quickly!
I wonder what the difference is between this and a typical $100 ELM type OBD2 reader ?
I am also curious what the refresh rate of this reader is ? Looks promising...
I ordered one of these from this guy and it works great on most of the protocols. It is quick and accurate with all of the software he has linked on his site. I even tried it with some other software and it works. If anyone has specific questions about it I will try to answer.
software allows you to query single or multiple PIDS. The fewer the PIDS the faster the refresh. If only one PID is selected then it is so fast it looks like real time changes, especially if you are looking at a PID that is easy to change like the TPS or RPM.
its encouraging to know that it is fast but would you be able to give me an approximate number in hertz "Hz" or times per second ? You could give me an idea for either one pid or several pids.
The thing is that I already have an interface and I need to log 4 pids at a time to make a timing map, and that interface doesn't refresh that fast, so the information you can provide will really help me determine if it would be worth the effort to go after this one or not.