Mag's OSE 12P Thread

[Holden202T]

sounds like an AE issue to me, post up a log so we can see, need to see what the o2 is doing at the time!

[VL400]

What engine parameters are factored into the the knock retard equation or Is simply progressive incremental control driven by the duration of the output flag from the knock sensing circuitry.

Knock attack for pulling spark and knock recovery for adding it back in, more counts (longer duartion) = more spark pulled.

Once you get a log post that and your bin. You can also enable knock count logging and have it populate the table in the NVRAM. Suck out the cal and have a look at the table in TP5.

[mag]

Waiting to do a run with new O2 sensor fitted before posting log.

[mag]

Have fitted new O2 sensor & the zero cross counts now reach 50 even during very short steady state cruise condition , in past only ever saw 3-4 count on extended cruise condition.

Attached two short logs that illustrate improved O2 function & my knock retarding issue, not had opportunity to get longer ones yet. To my untrained eye looks like the knock triggering may be false caused by a noisy engine. This engine has been noisy since a rebuild about 40K ago. Particularly noticeable as thrashy on over-run between auto gear changes.

The knock retard occurs on sharp engine load (map) decreases when the engine noise would peak, amplified further if the auto change up at the same time.

Has my analysis any validity. Any suggestion on the cause of the thrashy engine noise, I was thinking cam chain/tensioner problem.

[VL400]

Have you played with the AE side of things at all? Seems to run a little lean at WOT too.

[mag]

May have but only to make them the same as AFTY valuess from my VN ecu. Simply modified the BLCD V6 bin to AFTY cal values.

[Jayme]

can you post up your current cal?

[mag]

Here is current cal. Should note that I regularly run E10. Why would incorrect AE values trigger knock retard on engine load decrease. Would expect AE issue to cause a problem on engine load increase.

[Jayme]

I have a feeling the knock on decel has something to do with your cal having 54 degrees advance at 30kpa theres a fair few shady settings in there, im wondering if you got some corruption?

try something ... use 12P_V110_APNX.cal, set its map sensor to 2 bar. leave everything else alone, then drive and take a log and report back. im sure you will be amazed, I used that cal on a VP recently and its the goods.

[mag]

Thanks Jayme have loaded APNX cal, will see how we go. Has look at original AFTY vs v110 values & there are some discrepancies. Corrupted data is a nice way to say stuff-up. Anyway have read cal back from ecu to make sure APNX is there "un-corrupted".