Working on a 2002 toyota MR2. It doesn't have a traditional can bus and the OBDII uses the older 9141 K line single wire. I'd like to use the legacy OBDII adapter to convert a few channels of information to traditional can. How does the legacy OBDII adapter work exactly? Would I be able to use it without the race capture pro and pull data out of the can stream coming from the OBDII adapter or does it require some kind of command to pull data off the OBD K line? If so, once the data comes from the K line, what defines the can channel it ends up on? Is there mapping built into the firmware of the adapter that directs this data?
I'm just getting into can a little more and would like some more info.
iso 9141 k line sniffing
Hi,
Here's the info page on the OBDII adapter: https://wiki.autosportlabs.com/OBD2CAN
It's operation is straightforward:
It makes a legacy OBDII interface appear as if it is a CAN bus OBDII interface. It will translate a CAN OBDII query into the appropriate legacy OBDII query, and then translate the legacy OBDII response back into a CAN OBDII response.
It will operate as fast as the legacy OBDII interface allows. RaceCapture will only query the next PID when the current PID is complete.
We have found that other systems, like MoTeC , will blindly query CAN OBDII at 50Hz, which will cause problems with the legacy OBDII adapter, since legacy ECUs are typically much slower (7-10hz).
Hope this helps!
Here's the info page on the OBDII adapter: https://wiki.autosportlabs.com/OBD2CAN
It's operation is straightforward:
It makes a legacy OBDII interface appear as if it is a CAN bus OBDII interface. It will translate a CAN OBDII query into the appropriate legacy OBDII query, and then translate the legacy OBDII response back into a CAN OBDII response.
It will operate as fast as the legacy OBDII interface allows. RaceCapture will only query the next PID when the current PID is complete.
We have found that other systems, like MoTeC , will blindly query CAN OBDII at 50Hz, which will cause problems with the legacy OBDII adapter, since legacy ECUs are typically much slower (7-10hz).
Hope this helps!
Yes, these are all SAE standard OBDII PIDs. You can see a reference for all standard PIDs here:
https://en.wikipedia.org/wiki/OBD-II_PIDs
Note, not all ECUs implement all standard PIDs, but RPM, EngineTemp, TPS and a few more are almost always present.
https://en.wikipedia.org/wiki/OBD-II_PIDs
Note, not all ECUs implement all standard PIDs, but RPM, EngineTemp, TPS and a few more are almost always present.