%HTTP_EQUIV_ON_VIEW%
PGMFI Logo
Library> CEL (r1.1 vs. r1.3) Destinations: Home | Library | Change Log | Index
Search | Go

 <<O>>  Difference Topic CEL (r1.3 - 22 Dec 2005 - Home.qwertyville)
Changed:
<
<

If the CEL is lit solid and does not blink (after jumping the connector on OBD1 ) and the car runs poorly the following could be the problem:

>
>

If the CEL is lit solid and does not blink (after jumping the service check connector on OBD1 ) and the car runs poorly the following could be the problem:

  • A faulty ECU (means any other component failure other than listed here)
Added:
>
>

"Phantom" Check Engine Light

Sometimes you may get a CEL that doesn't show up when you turn the car off. In order to check these, you must do the following:
  • DON'T turn the ignition off
  • Jump the service check connector just like normal
Now the CEL will turn off briefly and then start flashing the codes like normal.

 <<O>>  Difference Topic CEL (r1.2 - 20 Dec 2005 - Home.qwertyville)
Changed:
<
<

Check Engine Light

>
>

Check Engine Light

Changed:
<
<

On OBD0 cars, there is a window on the ECU through which a blinking LED can be seen to read codes.

>
>

  • On OBD0 cars, there is a window on the ECU through which a blinking LED can be seen to read codes.
Changed:
<
<

On OBD1 cars, there is a connector located under the dash by the passenger footwell that must be shorted. This will cause the dash CEL to blink, indicating which codes are being thrown.

>
>

  • On OBD1 cars, there is a connector located under the dash by the passenger footwell that must be shorted. This will cause the dash CEL to blink, indicating which codes are being thrown.
Changed:
<
<

If the CEL is lit solid and does not blink (after jumping the connector on OBD1 ) and the car runs poorly, in all likelyhood you have a bad ECU, a bad program/bad ROM, or a Check Sum error.

>
>

  • On OBD2 cars, there is a connector located under the dash by the passenger footwell that must be shorted. This will cause the dash CEL to blink, indicating which codes are being thrown. You can also use an OBD2 scan tool which connects to the plug by the driver's side footwell. It is a gray connector that should be easily identifiable.
Added:
>
>

Solid Check Engine Light

If the CEL is lit solid and does not blink (after jumping the connector on OBD1 ) and the car runs poorly the following could be the problem:
  • A faulty ECU
  • Poor soldering connections
  • Check Sum error
  • Faulty program stored in the ROM
  • Faulty ROM chip
  • Faulty 74HC373 chip
Changed:
<
<

See Honda Error Codes

>
>

See Troubleshooting Solid CEL

Added:
>
>

See Honda Error Codes


 <<O>>  Difference Topic CEL (r1.1 - 04 Aug 2005 - Home.phiz)
Added:
>
>

%META:TOPICINFO{author="phiz" date="1123128525" format="1.0" version="1.1"}% Check Engine Light

This indicator (usually on the dash) comes on to indicate that the ECU thinks something is wrong. The ECU will usually indicate an error code by flashing the CEL in some manner.

On OBD0 cars, there is a window on the ECU through which a blinking LED can be seen to read codes.

On OBD1 cars, there is a connector located under the dash by the passenger footwell that must be shorted. This will cause the dash CEL to blink, indicating which codes are being thrown.

If the CEL is lit solid and does not blink (after jumping the connector on OBD1 ) and the car runs poorly, in all likelyhood you have a bad ECU, a bad program/bad ROM, or a Check Sum error.

See Honda Error Codes


{ View | Diffs | r1.3 | > | r1.2 | > | r1.1 | More }
Copyright © 2002-present by the contributing authors. All material on this collaboration platform is the property of the
contributing authors, and is covered by the Non-Commercial Share-Alike License unless explicitly stated otherwise.
Ideas, requests, problems regarding the PGMFI TWiki?? E-Mail the WikiAdmin
Site Designed By: Digital Fusion   Need a website?

Revision r1.1 - 04 Aug 2005 - 04:08 GMT - Home.phiz
Revision r1.3 - 22 Dec 2005 - 08:58 GMT - Home.qwertyville
%WEBCOPYRIGHT%