Interfacing a 2008 Toyota Corolla with a Microcontroller via CAN

  • Thread starter Thread starter ElectroPhysics
  • Start date Start date
  • Tags Tags
    Car
Click For Summary

Discussion Overview

The discussion revolves around interfacing a 2008 Toyota Corolla with a microcontroller using the CAN (Controller Area Network) protocol. Participants are seeking information on how to access and interpret data from the vehicle's onboard systems, particularly regarding the odometer readings and other diagnostic data.

Discussion Character

  • Exploratory
  • Technical explanation
  • Debate/contested
  • Experimental/applied

Main Points Raised

  • One participant inquires about the registers and data format for reading the mileage from the odometer via the DLC pins.
  • Another participant suggests that Toyota may keep this information proprietary and recommends searching Toyota performance forums for insights.
  • Some participants note that the CAN protocol is largely non-proprietary and question the necessity of a custom solution when existing products are available.
  • A participant mentions that mileage can be accessed from the ECU as diagnostic data, rather than directly from the instrument cluster.
  • Links to resources on onboard diagnostics and the ISO standards are provided as starting points for accessing vehicle data.
  • There is a mention of legal considerations regarding changing mileage, particularly in the UK.
  • Participants discuss the availability of standardized products that connect to the OBD port, while one expresses a desire to build a custom device and seeks binary data for the DLC3 connector.
  • A participant references a previous project involving CANBUS J1939 protocol and provides a link for further information.
  • Another participant suggests starting with a specific product link for software related to the project.

Areas of Agreement / Disagreement

Participants express differing views on the necessity of creating a custom device versus using existing solutions. There is no consensus on the best approach to access the required data from the vehicle.

Contextual Notes

Some limitations include the potential proprietary nature of certain vehicle data, the need for specific knowledge about the CAN protocol, and the legal implications of modifying vehicle mileage.

Who May Find This Useful

Individuals interested in automotive electronics, microcontroller interfacing, and those looking to develop custom diagnostic tools for vehicles may find this discussion relevant.

ElectroPhysics
Messages
115
Reaction score
2
hi,
i have to interface the toyota corrola 2008 car with microcontroller using CAN. can anybody tell me how and where to find out registers information and format. i mean e.g what is the mileage on odometer in binary format on dlc pins.
 
Engineering news on Phys.org
ElectroPhysics said:
hi,
i have to interface the toyota corrola 2008 car with microcontroller using CAN. can anybody tell me how and where to find out registers information and format. i mean e.g what is the mileage on odometer in binary format on dlc pins.


I would imagine that Toyota tries to keep that proprietary for monetary reasons. Have you tried searching on Toyota owners' performance forums?
 
CAN is specifically non proprietary (are at least a large component of it is). Any particular reason why you want to do this the hard way? there are cheap or freely available packages that can do this already...
 
On second reading - are you trying to read the mileage directly from the instrument cluster? if so - what berkeman said. If you just want to find the cars mileage - it's available from the ECU as diagnostic data.

If you're trying the change the value - check you local laws. It's illegal to change the mileage in order to sell it here in the U.K. I'm sure other countries have similar laws.
 
For reading data, pretty much everything you'll need to get started is here:

http://en.wikipedia.org/wiki/On-board_diagnostics

That gives you pinouts, links to the ISO standards, etc. It is a one-way link, used for reading diagnostic information out of the ECU (but not reprogramming it).
 
daveg360 said:
CAN is specifically non proprietary (are at least a large component of it is). Any particular reason why you want to do this the hard way? there are cheap or freely available packages that can do this already...


by the way, can u tell me what is that easy way. any web links...
 
"The easy way" is the link Mech_Engineer posted: there are lots of products that connect to the OBD port on a car and they are standardized. I use this one: http://www.scangauge.com/
 
russ_watters said:
"The easy way" is the link Mech_Engineer posted: there are lots of products that connect to the OBD port on a car and they are standardized. I use this one: http://www.scangauge.com/

but i have to make my own device. can anybody tell me from where to get the binary data of dlc3 connector CAN bus. i have searched the internet but it was not successful
 
ElectroPhysics said:
but i have to make my own device. can anybody tell me from where to get the binary data of dlc3 connector CAN bus. i have searched the internet but it was not successful

I was looking into building a controller for a dodge turbo that is controlled by canbus a while back, it was CANBUS J1939 protocol if I remember right. You can find out more http://www.SAE.org/standardsdev/groundvehicle/j1939a.htm"
 
Last edited by a moderator:

Similar threads

  • · Replies 11 ·
Replies
11
Views
8K
Replies
4
Views
5K
Replies
6
Views
5K
  • · Replies 37 ·
2
Replies
37
Views
3K
  • · Replies 3 ·
Replies
3
Views
3K
  • · Replies 4 ·
Replies
4
Views
3K
  • · Replies 2 ·
Replies
2
Views
2K
  • · Replies 3 ·
Replies
3
Views
2K
Replies
2
Views
2K
  • · Replies 2 ·
Replies
2
Views
2K