Auto Code Readers

Ford EFI - Auto Repair Codes

Scan Tool for Codes and Live Data for your Ford Engine from $149.95

The information below may apply to Ford Falcon / Fairmont ED and many other models

Step 5
Ford EFI Code Reading
Connector Diagram
Connector Location
Tips:
Single pin connector is grey in colour.
Auto Repair Manual - How to read codes (No Special Tools Needed)
1 Ensure the engine and oxygen sensor is up to operating temperature.
2 Turn the ignition OFF.
3 Connect an LED tester or Voltmeter to terminals 'A' & 'B'. (Click here for details) 
4 Use your own wire link to connect terminals as shown on the diagram.
5 Turn ignition ON.
6 Read codes as described in the Code Format Description below.
7 Press the continue button to enter the code numbers and get the code description(s).
Code Format Diagram
2 Digit
3 Digit
Code Format Description
Ford displays Hard Codes first then displays a single separator flash before displaying Memory Codes. Disregard any quick flashes preceding the code sequence that may occur.
The fault code will either be 2 digit (up to 99) or 3 digit (up to 999).
For more information on the KOEO code format, click here 
Each series of flashes represents a digit.
A 2 second pause separates each digit.
A 4 second pause separates each code.
Each fault code is repeated 2 times before next code is displayed.
Ignore any quick flashes that may occur before both Hard Codes and Memory Codes.
Code Format Diagram shows code No. 132.
To move to the next screen click on the Continue button
 Continue > 

Note on Example Model(s): Ford Falcon / Fairmont ED
The example model(s) shown, Ford Falcon / Fairmont ED 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