I think a clear and concise thread covering these topics is well over due, the information is around, but not super easy to follow. So lets post it up, and cover the basics!
OBD refers to the plug connector and its pinout, that is all.
This exact connector and base pin assignment. Your car may not have all of these lines/pins connected.
There are a series of networks in any modern vehicle, they are just "plain old wires", used to transmit information rather than power supply or signal or ground. Data is sent as "coded" 1's and 0's that your ECU will decipher and share along the network. The network type/name determines how the 1's and 0's are sent/received, so most networks are NOT cross compatible. The idea is that some are faster than others, some carry more data than others, and some have redundancies, and some only serve to control a master/slave array.
Some networks are standardised types, some are manufacturer specific. There are only a few types of networks in Aus delivered Lancer/mirage, you will only ever find K-line and CANBUS year model dependent (see below).
From 1996 you will find the OBDII plug connector in almost every car, because it was standardised for the USA market. This does not mean your car is magically able to be scanned and programmed, it simply means that it has the plug. Manufacturers like to keep their secrets, so the plug is there but easy access to the data was not required to be shared with the public. CANBUS data for emissions purposes, is publically available information. Most manufacturers did not bother to hide any of their data that wasn't strictly required for emissions testing, and here is where all the world kind of opened up into easier diagnostics and access to a lot of data without being intrusive.
AROUND the time of 2008, the standard required use of CANBUS protocol for communication aswell as the OBDII plug. Fortunately Lancers changed year models in this date range, so it makes my job super easy.
CC Lancer = NO CANBUS
CE Lancer = NO CANBUS
CG Lancer = NO CANBUS
CH Lancer = NO CANBUS
CJ Lancer = CANBUS
So if you have a CH, a generic scanner is not guaranteed to do any magic, however there is a very good chance that a modern workshop level tool will have capabilities to read and clear codes, as well as perform actuator tests. On a CH this is done through K-Line communication, using ISO 9141-2 protocol (instead of CANBUS), and Mitsubishi's proprietary MUTII/MUTIII system. So if you look for a scan tool, ensure it can at least use this protocol, but it is not a guarantee of all the features you might desire.
IF you have a CJ Lancer, go for gold on anything CANBUS compliant, there is no reason why it shouldn't plug and play in that respect. Expect live data, actuation, reading codes and clearing codes with ease and simplicity.
I want to know more about K-Line!
Have a flick through this link to the Pico Website
Scan Tools
Arguably the most functional tool on the market is the tactrix 2.0 paired with a laptop. However it is not "easy" to use unless you're comfortable with a bit of computer knowledge and being careful not to just click things and "see what happens". The software EVOScan that I use with my tactrix doesn't contain the prettiest user interface, particularly compared with what you can get from supercheap for $99 at the moment.
Here is a list of tools, known to work with their features listed next to them. I will update this as people can feed me the info
Scan tools that work with CE
- tactrix 2.0 > Everything
Scan tools that work with CG/CH
- tactrix 2.0 > Everything
Scan tools that work with CJ
- tactrix 2.0 > Everything
- ELM32 Bluetooth (eBay special) > Clear and read codes, live data
Want a gauge that works with your K-Line equipped vehicle?
DIY Arduino based solution! This is definitely the cheapest method of getting that information out the ecu and onto a display. This person even used an LED output as a visual display of LOAD, pretty interesting use..
Just some extra info for anyone concerned about fault codes/engine lights
Engine light is to tell you about any emissions related issue. Not all fault codes bring on an engine light, however all causes of an engine light being on, can be linked to a code. (Unless you own a Volkswagen, in which case I HATE YOUR CAR)
A code is only set when the information from a sensor (or monitored actuator) that is sent back to the ECU does not meet the threshold that the ECU expects. For example, a pressure sensor is expected to have an output to the ECU between 0.5volts-4.5volts. If the ECU receives a voltage above or below this range, it will log a code corresponding. It may also log a code if it expects to see a change from that sensor and that does not happen.
A stored/active fault code DOES NOT INDICATE A FAULTY PART. It indicates a fault within the system. You must assess the system as a whole, and isolate the issue before parts replacement or repairs should be undertaken. Simply clearing a code, or changing a part because of a code does not guarantee the issue is resolved.
OBD refers to the plug connector and its pinout, that is all.
This exact connector and base pin assignment. Your car may not have all of these lines/pins connected.
There are a series of networks in any modern vehicle, they are just "plain old wires", used to transmit information rather than power supply or signal or ground. Data is sent as "coded" 1's and 0's that your ECU will decipher and share along the network. The network type/name determines how the 1's and 0's are sent/received, so most networks are NOT cross compatible. The idea is that some are faster than others, some carry more data than others, and some have redundancies, and some only serve to control a master/slave array.
Some networks are standardised types, some are manufacturer specific. There are only a few types of networks in Aus delivered Lancer/mirage, you will only ever find K-line and CANBUS year model dependent (see below).
From 1996 you will find the OBDII plug connector in almost every car, because it was standardised for the USA market. This does not mean your car is magically able to be scanned and programmed, it simply means that it has the plug. Manufacturers like to keep their secrets, so the plug is there but easy access to the data was not required to be shared with the public. CANBUS data for emissions purposes, is publically available information. Most manufacturers did not bother to hide any of their data that wasn't strictly required for emissions testing, and here is where all the world kind of opened up into easier diagnostics and access to a lot of data without being intrusive.
AROUND the time of 2008, the standard required use of CANBUS protocol for communication aswell as the OBDII plug. Fortunately Lancers changed year models in this date range, so it makes my job super easy.
CC Lancer = NO CANBUS
CE Lancer = NO CANBUS
CG Lancer = NO CANBUS
CH Lancer = NO CANBUS
CJ Lancer = CANBUS
So if you have a CH, a generic scanner is not guaranteed to do any magic, however there is a very good chance that a modern workshop level tool will have capabilities to read and clear codes, as well as perform actuator tests. On a CH this is done through K-Line communication, using ISO 9141-2 protocol (instead of CANBUS), and Mitsubishi's proprietary MUTII/MUTIII system. So if you look for a scan tool, ensure it can at least use this protocol, but it is not a guarantee of all the features you might desire.
IF you have a CJ Lancer, go for gold on anything CANBUS compliant, there is no reason why it shouldn't plug and play in that respect. Expect live data, actuation, reading codes and clearing codes with ease and simplicity.
I want to know more about K-Line!
Have a flick through this link to the Pico Website
Scan Tools
Arguably the most functional tool on the market is the tactrix 2.0 paired with a laptop. However it is not "easy" to use unless you're comfortable with a bit of computer knowledge and being careful not to just click things and "see what happens". The software EVOScan that I use with my tactrix doesn't contain the prettiest user interface, particularly compared with what you can get from supercheap for $99 at the moment.
Here is a list of tools, known to work with their features listed next to them. I will update this as people can feed me the info
Scan tools that work with CE
- tactrix 2.0 > Everything
Scan tools that work with CG/CH
- tactrix 2.0 > Everything
Scan tools that work with CJ
- tactrix 2.0 > Everything
- ELM32 Bluetooth (eBay special) > Clear and read codes, live data
Want a gauge that works with your K-Line equipped vehicle?
DIY Arduino based solution! This is definitely the cheapest method of getting that information out the ecu and onto a display. This person even used an LED output as a visual display of LOAD, pretty interesting use..
Just some extra info for anyone concerned about fault codes/engine lights
Engine light is to tell you about any emissions related issue. Not all fault codes bring on an engine light, however all causes of an engine light being on, can be linked to a code. (Unless you own a Volkswagen, in which case I HATE YOUR CAR)
A code is only set when the information from a sensor (or monitored actuator) that is sent back to the ECU does not meet the threshold that the ECU expects. For example, a pressure sensor is expected to have an output to the ECU between 0.5volts-4.5volts. If the ECU receives a voltage above or below this range, it will log a code corresponding. It may also log a code if it expects to see a change from that sensor and that does not happen.
A stored/active fault code DOES NOT INDICATE A FAULTY PART. It indicates a fault within the system. You must assess the system as a whole, and isolate the issue before parts replacement or repairs should be undertaken. Simply clearing a code, or changing a part because of a code does not guarantee the issue is resolved.
Last edited:
