Auto Code Readers

Mitsubishi Engines - Auto Repair Codes

Scan Tool for Codes and Live Data for your Mitsubishi Engine from $199 USD

The information below may apply to Mitsubishi Starion and many other models

Step 4
Mitsubishi EFI Code Reading
Connector Diagram
Connector Location
Auto Repair Manual - How to read codes (No Special Tools Needed)
Note:Look at the connector in the vehicle and connect as per either diagram to your left.
1 If possible run the engine to bring it and the oxygen sensor up to operating temperature.
2 Switch engine off.
3 Connect an LED tester or Voltmeter to terminals 'A' & 'B'. (Click here for details) 
4 Turn ignition ON.
5 Read codes as described in the Code Format Description below.
6 Press the continue button to enter the code numbers and get the code description.
Code Format Diagrams
Code Format Description
The fault code will be in one of the following Code Formats below.
A long flash indicates the start of each code.
The code is made up of five flashes representing either a '0' or a '1'.
Short flashes indicate '0's, long flashes indicate '1's
Each code is separated by a long pause.
Upper Code Format Diagram shows Binary No. 00010 or code No. 2 as the flash is in the second position.
Or...
Each code is made up of two series of flashes.
The first series indicates the 'tens' digit.
The second series indicates the 'ones' digit.
A pause of approximately 1s separates the 'tens' and 'ones'.
A pause of approximately 3s separates each code.
Lower Code Format Diagram shows code No. 32.
To move to the next screen click on the Continue button
 Continue > 

Note on Example Model(s): Mitsubishi Starion
The example model(s) shown, Mitsubishi Starion for this auto repair service are only an indication to help you. There may be many other models that apply to this connector. Click above link to see the complete vehicle coverage list.



< Back
All content copyright Rennacs Limited, 2009. All products names mentioned herein should be considered registered trademarks of their respective owners.
For comments and feedback please email comments@rennacs.com

Disclaimer