Clarifications for CEL

[Alin]

So there is the sticky for the extended list of codes that can be caused from a CEL.

Well, in my past, I have experienced flashing CEL during WOT. It is some sort of limitation. No codes ever stored. So now, someone must know what happens during a CEL flash and what it means.

Looking forward to hearing what you guys have to say. :tup:

 

[Grinder34]

http://www.igotasti.com/vBforum/showthread.php?3767-ODBII-codes

Is that what you're looking for?

 

[Alin]

I read that, but it does not talk about what I am referring to. Maybe I did not write it correctly. At times when I woulg go WOT, the CEL would flash for a brief 2-3 seconds causing a limit somewhere and boost, fuel, or whatever would be cut. Does anyone know what I am talking about?

 

[Grinder34]

Some of the rom-raider guys talked about CEL flash when knock is detected, but that doesnt seem like what you're talking about. That's something you enable in an open-source tune.

Sorry I can't help more!

 

[Alin]

It cannot be knock. It is all based on the tunes I have received. But then again what do I know. I hope someone that has experience can clarify this!

Thanks for your input grinder! :tup:

 

[HolyCrapItsFast]

I have seen this in my own car when I had it. I noticed it happens when you start to approach fuel cut as defined by the Boost Target tables. You could be reaching the threshold long enough to flash the light but not generate a hard code. I believe for there to generate a hard code the condition must exist for a predetermined amount of time. They do this because sometimes the turbo spikes temporarily because of atmospheric conditions and if it were to generate a code every time you get a quick spike they would be inundated with service requests.

 

[Td_d]

I have seen this in my own car when I had it. I noticed it happens when you start to approach fuel cut as defined by the Boost Target tables. You could be reaching the threshold long enough to flash the light but not generate a hard code. I believe for there to generate a hard code the condition must exist for a predetermined amount of time. They do this because sometimes the turbo spikes temporarily because of atmospheric conditions and if it were to generate a code every time you get a quick spike they would be inundated with service requests.

Correct - there are counters (and many other conditions) that are used in conjunction with the CEL routines that are used to determine when a CEL is triggered. If you really want to give yourself a headache, go check out the diagnostic's criteria section of your service manual, you will see it has many parameters associated with specific CELs.

 

[Alin]

So in other words I am dealing with a bad tuner? Lol

 

[HolyCrapItsFast]

It is possible. But there are many factors that could cause the condition. They may not have existed at the time of the tune. :tup: