pcmhacking.net

I was just going thru my 11P setup and noticed I didn't have the flag turned on for knock sensor failure. What I found was there are 4 flags for what I would have thought would only be one. They all look the same so I ticked all of them. Does anyone know why there is 4 flags and have I done the right thing turning them all on.

It gets even more confusing for me. I find 4 flags for every code I have looked at and some have only 1 ticked and others have 3 ticked. These are from the bins in the 11P package. I am very confused.

Doesn't it have to do with the twin tables setup that you can switch between, so one set of flags go with tables A and the 2nd set of flags go with tables B in the tune.

That kinda makes sense but there's noting to say that's the case. Why would you need 4 flags for code 14 engine temp high and have 3 of them ticked. What I did with the knock sensor flag was tick all 4 and the car ran like a sick dog with the check engine light on so I checked for codes and there aren't any so I am unticking 3 of the boxes and try again.

Yes this drove me nuts and hours of stuffing around to turn off all auto features.

It looks to me like this is XDF error. I'll flag it (no pun intended) with VL400 and point him to this thread. I believe the first one is to enable/disable the DTC, and the next one to enable/disable it triggering the check engine light (masking the error - probably the one you want). The last two look to be a bug in the definition.

Its actually correct and makes far more sense if you use category view as shown on page 2 of the 11P PDF.

There is a flag for processing the error and then a flag for enabling the CEL when the error occurs. There is a pair for the engine code and a pair for the transmission code. The PCM code allows you to mask an error for the engine but let it process for the transmission and vice versa.

It may have been that a case existed where the factory engineers wanted the engine code to handle/process a fault using default values but have the trans code ignore it and use whatever reading there is available. It could also have just been so they could do as they did and use the same software module for both trans and enigne code when checking what faults to process.

Ok cool, thanks for the update. In that case i'd recommend hitting F2 for details on each edit box so you can see which is which, and in most cases masking the flag for engine and trans would be the correct option, while leaving the faults enabled so the (lack of) sensors can be ignored.

Category view makes it much clearer what flag is for what function. It makes the whole xdf much clearer and easy to use actually.

Thanks for the info VL400. I have some time today so I will go thru it and see just what I have done wrong.