Auto Code Readers

Holden EFI - Auto Repair Codes

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

The information below may apply to Holden Vectra and many other models

Step 4
Holden EFI Code Reading
Connector Diagram
Connector Location
Note: You may need the OBD2 / EOBD or UniPlug vehicle specific software.
Click here for more info.
Auto Repair Manual - How to read codes (No Special Tools Needed)
1 If possible run the engine to bring the oxygen sensor up to operating temperature then switch the engine off.
2 Connect the terminals using your own jumper wire, (Click here for details) , as shown in the diagram to your left.
3 Turn ignition ON, the Check Engine Light (CEL) should begin flashing.
4 Read codes as described in the Code Format Description below
5 Press the continue button to enter the code numbers and get the code description(s).
Code Format Diagram
Code Format Description
Read the code in one of the formats below.
Each code is made up of two groups of flashes.
The first group indicates the 'tens' digit.
The second group indicates the 'ones' digit.
A long pause separates each code.
A shorter pause separates the 'tens' and 'ones'.
Code sequence starts with code 12 and repeats each code 3 times. (if only code 12 is found, system is normal)
Upper Code Format Diagram shows code No. 32.
Or...
Each code is made up of four groups of flashes.
Each group represents 'thousands' 'hundreds', 'tens' and 'ones' respectively.
A long pause separates each code.
A shorter pause separates the each group.
A zero digit is represented by 10 flashes.
Bottom Code Format Diagram shows code No. 1232.
To move to the next screen click on the Continue button
 Continue > 

Note on Example Model(s): Holden Vectra
The example model(s) shown, Holden Vectra 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