Last edited by T.Jackson; - 25th April 2007 at 10:44.
Actually communicating with one vehicle is the same as the next, because they all use the OBDII protocol. The SAE have the OBDII standard for purchase. While some of the more advanced functions like reprogramming are manufacturer specific the diagnostic items like speed and RPM are the same on every vehicle and outlined in their document(s).
I had the oppritunity to read through the OBDII standard while working on another project, needless to say its tedious to communicate on the buss. I ended up integrating an OBDII to serial IC into my design to simplify things, ELM electronics sells it (ELM327).
The following will give you a taste of the protocol and how it works. This document is geared to VPW but the concepts remain the same.
http://www.lightner.net/lightner/bruce/Lightner-183.pdf
That ELM327 chip rocks!
I'm about to order a 2nd load of PCBs anydays now. Almost can't keep enough on hand.
You said anything.Attached are code files that appear to be PBP.I downloaded them from somewhere about 6 years,but never used them.I do know they were for use with a can bus interface chip MCP2510 controlled thru the MSSP port of a 16F877 using SPI.
Thanks!
Maybe I can use some of that code.
The 18F6585 have an own ECAN modul so I think its a lot different than using the stand alone chip.
But I´m going to look at this.
Oboy!!! I have a lot to learn about CAN :-)
/JKBPower
CAN is nice, but not as easy as USART, SPI, I2C or some part of USB.
At least once you understand the concept, it's easy.
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
Bookmarks