I seriously doubt it's a speed thing, but at least make sure you aren't logging items you don't need, that will seriously slow things down but even then it'll still capture knock sum. You have to keep in mind that in most cases knock doesn't show up for a split second and disappear, it hangs around for a bit.

 

I tried to reset my ECU but I get negative timings yet... Octane level is rock solid at 100, it seems like my ECU intepolates with low octane maps with no reason. Could it be a wrong map definition (like one of three high/low octane map swapped)???

 

Whats your afr look like? on my own car i noticed if its too lean itll just pull timing for some reason and not show any knock... Then i copied it to the low map and it showed the knock and ran the same timing.. i would start there and see if you have the same results...

If its only pulling 1-2 deg you shoudl see around 4-5 counts of knock.


Cheers!

 

No, I don't get so much knocks but 1-2 knocks depending on run, and not there.

Time is pulled at load peak with AFR at 11.0.

 

I think when load rapidly increases during spool up we often see:

Spikes of load
Sporadic knock sums
Brief reductions in timing below what it is mapped for.

I don't worry about it, but it would be interesting to look into it further.

 

I think it could be rear O2 related, in EDM 88840016 the periphery0 fix does not work (it throws a P0125), so I live with CEL on. Maybe some limitation from this...

 

Some news: I have found an additional ignition map that looks a little strange - like a protection map.



I'm pretty sure that my negative timings comes from here. In 88840016 has address 0x65B5.

 

Very interesting ...

 

Mmm... looking in asm code it seems to be a sort of "High Octane Ignition Map 4" used in some way from the ignition main subroutine, but I have to find when...

 

Has anyone mentioned already that you could be off the scale of the map at that point? The ecu could be calculating 320 load, throwing you off the end of the map. Happens a lot on VIII's due to the stocl scale maxing out at 260 load.

 

No, I'm logging 2-bytes load and I never get more than 290. Moreover I tried to rescale my maps to 320 with no success for negative timing, so I reverted to 300.

 

His logs show him around 240-280 load when the values are off.

 

I have had all four of my high octane ignition maps the same and this still happens.

 

Do you know when map #4 is used?

 

Anything new on this? Im experiencing the same problem. I was wondering the other day if it pulls timing the same way a dsm does for temperature.