CAN is OBD2Originally Posted by techy101
Hey, I was wondering if anyone here knows of a cheep PC interface for a vehicle with the CAN Bus protocol instead of the OBD-II. (2005 Lincoln Navigator)
according to the person on obddiagnostics it's a completley different protocol. (which would explain why the pinouts on the plug were all different, and it wouldn't even think about communicating with the OBD-II interface. Also as far as my searches have come up, although they may use the same connector, they are completley different protocols.
I have been digging around the net, and i found this http://www.aeswave.com/products/Prod...p?i=455&tsw=su
but it's still a bit high priced for my taste. looking for something more in the $100 range (like the product from http://www.obddiagnostics.com/
CAN is brilliant, if you can get an interface in theory you can control anything in the car - from the headlights to the windows!
there are plenty of CAN USB interfaces around.
CAN is a communications architecture. OBDII is a government regulation. OBDII regulation can be met on CAN vehicles using several different protocols (CAN or other). You are confusing existing scan tools that don't support CAN (yet) with OBDII regulation. So, a newer "OBDII" scan tool - that supports CAN - can connect to a CAN protocol vehicle via the same standard diagnostic connector. The pins are different within the connector that CAN has implemented.
"Controller Area Network (CAN)
Is a high-integrity serial data communications bus for real-time applications
Operates at data rates of up to 1 Megabits per second
Has excellent error detection and confinement capabilities
Was originally developed by Bosch for use in cars
Is now being used in many other industrial automation and control applications
Is an international standard: ISO 11898" http://www.can.bosch.com/index.html
There is not necessarily any additional support for controlling vehicle features with CAN vs. any other protocol. Support of features is up to the scan tool implementation of how much OEM proprietary attributes are supported and how many different modules (engine usually, transmission sometimes, body control module hardly ever outside of OEM scan tools, air bag module once in a while, other modules only with OEM scan tools typically). This limitation is not a limitation of a protocol but that OEMs are not regulated to provide uniform methodology for accessing this data on the vehicle like some of the primary engine controller attributes are mandated by OBDII regulation.
Generally speaking CAN vehicles have more discrete modules which is what makes CAN a popular protocol for newer vehicles to support for it's ability to handle more data traffic to more modules with less error. This would make you think that you can control these modules offboard, but not necessarily true.
Mods - Can you enhance this forum's sticky for CAN to reduce amount of common posts asking same questions?.
so lemme get this straight... you went out and bought a brand-spankin-new luxury suv, and you're worried about the cost of an interface adapter?Originally Posted by techy101
DavidL: Thank you for all the info. It helps to clear stuff up a lot.
nottastocker: I WISH . There is no way on this earth that i could ever afford a Navigator. It's for a friend. (I tried to convince him to give it to me, but his terms were a bit steep for me)
that is incorrectOriginally Posted by techy101
PHY layer is different
upper layer conforms to J1979 (OBD2) via ISO15765
Arise!! My old thread......muahahahahahah
Does anyone know where I can find a copy of ISO 11519 (low speed CAN), ISO 11898 (High speed CAN) without spending a fortune?
An up to date (4/30/02) SAE J1979 would be nice too, but I can live without...
It's been a while...