mazdeuce wrote: AIM SoloDL The software is free to download from AIM so you can take a peek at what is available for the different cars it supports. I ran the package for an RX8 (I think) and it grabbed just about everything perfectly on my 2. I need to get it back from my friend to see what I can pull off the Cadillac.
That's pretty cool! I predict that a certain FoMoCo engineer will be buying one any minute now. I'd buy one too, if I had an obd2 car to play with.
I learned something today.. took my mom's rendezvous through inspection. it has a MIL on due to a vacuum leak (small) and just for the fun of it, I cleared the code with Torque before driving the 20 minutes to the station.. car went right through inspection.. did not give a readiness error or anything.
I was truly surprised
Just as an FYI: when OBDII was first introduced, it was a big step up from OBDI. Through the training classes we at the dealer level had to take, one of the parameters was that there had to be a commonality across platforms/brands for emissions related items and that this information had to be readily available to the aftermarket to allow for repairs outside the manufacturers' shops/dealerships. For that reason, a lot of OBDII stuff can be pulled easily but it is somewhat limited, it's pretty well limited to engine control stuff. To the best of my knowledge it does not include GPS, accelerometer etc information although it does know TPS readings, i.e. it can tell you how far your boot was in the throttle body.
OBDII can and does run stuff outside of emissions related items but in many cases the codes and related repair information are considered 'proprietary' and the manufacturer does not have to provide no-cost support for those codes.
The latest CAN stuff does just damn near everything, but to the best of my knowledge does not include GPS readings but given how many cars have navigation in the dash I am going to guess that at least those cars do. It does include accelerometer etc data since the CAN system talks to things such as the airbag module, that's where it gets the info so it 'knows' if the car is sliding, yawing etc which is essential for traction and stability control.
OK, help me with my ignorance.
I understand the difference between OBDI and OBDII.
I also understand CAN is the newest version, and (of course) is better.
What are the major differences?
Does it use a similar port? Do all cars use it now? When did it begin?
I also understand the proprietary stuff. I am trying to get a basic overview of what generally can and can not be read.
So, pre 1981- no on board diagnostics.
1981- 1995 (+-)- OBDI- pretty much all proprietary, and no standardization between manufacturers.
1996- ?? OBDII- Standardized comm port for all manufacturers, Emissions data available to all, but perhaps not much else (depending on manufacturer). Improved diagnostics and engine monitoring. Warning to driver (check engine light).
Additional for CAN or other??
Is that expanded data mazdeuce described for the AIM SOLODL likely from a CAN port, or OBDII with (more open source) OEM data?
OBDI is fully proprietary, including the connector and the way it's "downloaded".
OBDII is a common system, including connectors and ID's so that anyone can read it with just one tool. Started in 1996.
CAN is just a vehicle network that the data can be accessed from, and is used to connect the various modules in the car. So with the the right too, a tech can question all of the modules in a car to check for problems. Not sure when that was introduced.
My understanding, from a data collection standpoint, is that CAN systems are capable of greater data speeds than OBDII ports. CAN really is just creating a network in the vehicle (from what I read) where all of the systems communicate. I think it's likely in the future, if it hasn't already happened, that the OBDII port will give out only the data that is mandated by law, and there will be a second port where all of the manufacturer specific stuff happens.
I think you guys might be mixing up OBD2 readings and data available over CANbus. For example I'd be really surprised if yaw/G and steering position were OBD2 readings.
GameboyRMH wrote: I think you guys might be mixing up OBD2 readings and data available over CANbus. For example I'd be really surprised if yaw/G and steering position were OBD2 readings.
How does canbus record yaw/g and steering position? It's a communication protocol/system. It neither records nor senses data.. It just allows things that record/store data to talk to each other.
http://en.wikipedia.org/wiki/CAN_bus
GameboyRMH wrote: I think you guys might be mixing up OBD2 readings and data available over CANbus. For example I'd be really surprised if yaw/G and steering position were OBD2 readings.
Count yourself surprised. Can do, have done. If the car has one port, I gaurantee you that every sensor on that car can be read through that port if you know how to ask for it. Modern ones anyway. After seeing what GM will tell me it can read real time through OnStar, I'd bet a nickel that they can do the same over the air.
You'll need to log in to post.
